throbber
Case 6:22-cv-00031-ADA Document 52 Filed 09/14/22 Page 1 of 10
`
`
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE WESTERN DISTRICT OF TEXAS
`WACO DIVISION
`
`FLYPSI, INC., (D/B/A FLYP),
`
`Plaintiff,
`
`v.
`
`GOOGLE LLC,
`
`Defendant.
`
`
`
`CIVIL ACTION NO. 6:22-cv-00031-ADA
`
`JURY TRIAL DEMANDED
`










`
`
`
`DEFENDANT GOOGLE LLC’S REPLY CLAIM CONSTRUCTION BRIEF
`
`
`
`

`

`Case 6:22-cv-00031-ADA Document 52 Filed 09/14/22 Page 2 of 10
`
`
`
`Flyp implicitly admits that the patents-in-suit provide no criteria (objective or otherwise)
`
`for a POSITA to distinguish between the claimed primary and secondary telephone numbers. To
`
`avoid this fatal defect, Flyp argues that the explicit limitations “primary telephone number” and
`
`“secondary telephone number” do not mean what they say, and instead mean nothing more than
`
`“first telephone number” and “second telephone number.” This argument ignores the patents’
`
`intentional use of “first” and “second” only where those simple modifiers were appropriate, and
`
`the deliberate use of the more specific modifiers “primary” and “secondary” for describing
`
`different types of telephone numbers. Flyp cannot avoid indefiniteness by rewriting claim
`
`elements, or by rendering meaningless the words “primary” and “secondary,” which the patentee
`
`expressly included in the claims. Because even Flyp recognizes that a POSITA cannot ascertain
`
`with reasonable certainty when a telephone number is primary, secondary, neither or both, the
`
`challenged claim terms are indefinite.
`
`I.
`
`The “Primary Telephone Number” and “Secondary Telephone Number” Are
`Different Types of Numbers in the Claimed Invention
`
`Flyp drafted the Asserted Patents to include and require at least four different types of
`
`telephone numbers: (i) primary telephone number; (ii) secondary telephone number; (iii) bridge
`
`telephone number; and (iv) contact telephone number. Dkt. 47 at 2. Flyp purposefully selected the
`
`claim language to differentiate these separately required telephone numbers from each other. See
`
`Innova/Pure Water, Inc. v. Safari Water Filtration Sys., Inc., 381 F.3d 1111, 1119 (Fed. Cir. 2004)
`
`(“[W]hen an applicant uses different terms in a claim it is permissible to infer that he intended his
`
`choice of different terms to reflect a differentiation in the meaning of those terms.”). Flyp now
`
`asks the Court to turn a blind eye to the drafting decisions it made nearly a decade ago. The Court
`
`should decline this invitation. The claims, specification, and prosecution history of the Asserted
`
`Patents demonstrate that the “primary telephone number” is a different type of number than the
`
`-1-
`
`

`

`Case 6:22-cv-00031-ADA Document 52 Filed 09/14/22 Page 3 of 10
`
`
`
`“secondary telephone number.” Flyp is mistaken that these two telephone numbers are “no
`
`different than a ‘first telephone number’ and a ‘second telephone number.’” Dkt. 49 at 3.
`
`To begin, the claims use the words “first” and “second” to describe multiple “bridge”
`
`telephone numbers and “contact” telephone numbers. For example, the ’105 Patent recites “a first
`
`bridge telephone number” and a “second bridge telephone number.” ’105 Patent, Claims 2, 8; id.
`
`Claims 8, 12 (“first contact telephone number”; “second contact telephone number”). It is therefore
`
`incorrect to suggest that the words “primary” and “secondary” differentiate two telephone numbers
`
`“in much the same way the words ‘first’ or ‘second’ would.” See Dkt. 49 at 2. Claim 1 of the ’770
`
`Patent further demonstrates how Flyp intentionally chose “different terms to reflect a
`
`differentiation in the meaning of those terms.” Innova/Pure Water, Inc., 381 F.3d at 1119. There,
`
`Flyp used the words “first” and “second” to refer to two sets of digital information that a handset
`
`acquires in the claimed invention, but the words “primary,” “secondary,” and “bridge” to refer to
`
`the different types of telephone numbers in the claim. In sum, had Flyp wanted to claim merely a
`
`“first telephone number” and “second telephone number,” it would have done so. It did not.
`
`Next, the specification suggests that there is only one “primary telephone number.” See,
`
`e.g., ’105 Patent, Col. 5:21–25 (“the primary telephone number and the one or more secondary
`
`telephone numbers”). But the specification describes embodiments using multiple “secondary
`
`telephone numbers.” See ’770 Patent, Abstract; id., Col. 4:67–5:2 (“one or more secondary
`
`telephone numbers”); id., Col. 5:35–39 (“activation of additional secondary telephone numbers”).
`
`Flyp’s argument that the primary and secondary telephone numbers are nothing more than a “first”
`
`and “second” telephone number makes no sense in this context: like the bridge or contact telephone
`
`numbers, there can be multiple secondary telephone numbers (i.e., a “first” secondary telephone
`
`number; a “second” secondary telephone number).
`
`-2-
`
`

`

`Case 6:22-cv-00031-ADA Document 52 Filed 09/14/22 Page 4 of 10
`
`
`
`Finally, the prosecution history confirms that the “primary” and “secondary” telephone
`
`numbers are different types of numbers in the claimed invention. U.S Application No. 13/944,853
`
`(“’853 Application”)—to which the Asserted Patents claim priority—refers to the “primary
`
`telephone number” as a “user telephone number” and the “secondary telephone number” as an
`
`“alternative telephone number.” Compare ’853 Application with ’770 Patent application (Ex. 8).
`
`The prosecution history thus makes clear that one telephone number in the claimed invention is
`
`“primary,” (i.e., the “user telephone number”) and at least one (but perhaps multiple) telephone
`
`number in the claimed invention is “secondary” (i.e., “alternative”).
`
`Flyp’s argument that “primary” and “secondary” are synonymous with “first” and “second”
`
`should thus be rejected. See Dkt. 49 at 1. As used in the Asserted Patents, a primary telephone
`
`number and secondary telephone number “are distinct terms that are not interchangeable” with a
`
`first telephone number and second telephone number. See Digital Retail Apps, Inc. v. H-E-B, LP,
`
`No. 6:19-cv-00167-ADA, 2020 WL 376664, at *8 (W.D. Tex. Jan. 23, 2020). Simply put,
`
`“primary” and “secondary” cannot be substituted with “first” and “second,” as Flyp urges. Doing
`
`so would not only ignore the patentee’s deliberate selection and emphasis of the words “primary”
`
`and “secondary” (as opposed to “first” and “second,” which were selected for use in other
`
`limitations), it would render the express “primary telephone number” and “secondary telephone
`
`number” terms effectively meaningless.
`
`II.
`
`The Asserted Patents Provide No Objective Criteria to Determine When a
`Telephone Number Is “Primary” or “Secondary”
`
`Nothing in the intrinsic record provides an objective standard for a POSITA to determine
`
`when a telephone number is “primary” or “secondary.” Dkt. 47 at 3–4. The present dispute is
`
`strikingly similar to that in U.S. Well Services. There, the defendant argued that the term “high
`
`pressure” was indefinite because what might be considered “high pressure” to one POSITA may
`
`-3-
`
`

`

`Case 6:22-cv-00031-ADA Document 52 Filed 09/14/22 Page 5 of 10
`
`
`
`not be “high” enough to another POSITA. U.S. Well Servs., Inc. v. Halliburton Co., No. 6:21-cv-
`
`00367-ADA, 2022 WL 819548, at *5 (W.D. Tex. Jan. 17, 2022). Similarly here, a telephone
`
`number that one user (or POSITA) considers “primary” might be considered “secondary” or
`
`“alternative” to another user (or POSITA). In U.S. Well Services, this Court held that the intrinsic
`
`and extrinsic record did not enable a POSITA to differentiate “‘high pressure’ from non-high
`
`pressure.” Id. at *6. Here, too, the record provides no “objective baseline” for a POSITA to
`
`differentiate a primary telephone number from a secondary number. Finally, the plaintiff in U.S.
`
`Well Services sought a plain and ordinary meaning construction that wholly ignored the disputed
`
`claim term. Id. at *9 (“The overarching problem with USWS’s understanding of the plain and
`
`ordinary meaning of the term is that it completely reads the term ‘high pressure’ out of the
`
`claims.”). So too here. Flyp’s argument that the disputed limitations are “no different than a ‘first
`
`telephone number’ and a ‘second telephone number’” render the asserted claim language wholly
`
`superfluous. See also Versata Software, Inc. v. Zoho Corp., 213 F. Supp. 3d 829, 837 (W.D. Tex.
`
`2016) (“”[M]eaning must be separately given to ‘space-constrained display.’”); Datamize, LLC v.
`
`Plumtree Software, Inc., 417 F.3d 1342, 1346 (Fed. Cir. 2005) (affirming district court’s
`
`conclusion that the disputed term “must be given meaning and cannot be read out of the claim”).
`
`Just like the limitations at issue in U.S. Well Services, “primary telephone number” and “secondary
`
`telephone number” are indefinite.
`
`Flyp’s attempt to distinguish Datamize falls short. Dkt. 49 at 5–6. Under Datamize, this
`
`Court may properly conclude that the “ordinary and customary meaning” of the limitations is
`
`“quite subjective”—one telephone number is more important or relevant (“primary”) than the other
`
`one (“secondary” or “alternative”). See Datamize, 417 F.3d at 1346. Like the plaintiff in Datamize,
`
`Flyp cannot point to anything in the intrinsic record that removes these limitations from “a matter
`
`-4-
`
`

`

`Case 6:22-cv-00031-ADA Document 52 Filed 09/14/22 Page 6 of 10
`
`
`
`of subjective opinion.” Dkt. 49 at 6. There is simply no way to objectively determine whether a
`
`telephone number is primary or secondary. Datamize, 417 F.3d at 1352 (“[N]either these
`
`statements nor any others in the written description set forth an objective way to determine whether
`
`an interface screen is ‘aesthetically pleasing.’”).
`
`Rather than address the subjective nature of these limitations, Flyp resorts to ad hominem
`
`attacks on Google expert James Bress’s “purported technical qualifications.” Dkt. 49 at 4. But,
`
`with an M.S. in electrical engineering and over 35 years of experience in telecommunications
`
`systems and software design, Mr. Bress is well-positioned to attest to the “subjective and relative”
`
`nature of the limitations. Dkt. 47 at 3. Further, contrary to Flyp’s assertion, Mr. Bress did not
`
`“divorce[]” the limitations from the asserted claims, or discuss the limitations “in the abstract.”
`
`Dkt. 49 at 4. Instead, he reviewed the limitations in the context of the Asserted Patents and their
`
`prosecution histories. Dkt. 47-1, ¶ 23. After that review, he determined that, to a POSITA
`
`analyzing the asserted claims, “it is impossible to know, as between a personal telephone number
`
`and a business telephone number utilized by a user, which might be the ‘primary telephone
`
`number’ and which might be the ‘secondary telephone number’ . . . .” Id., ¶ 37.
`
`Ultimately, Flyp’s Response does not actually contend that the patents provide a POSITA
`
`with any standards or criteria to use in determining when a particular telephone number is primary,
`
`secondary, or both. Dkt. 49 at 3 (conceding that “either” telephone number performs the same
`
`function).1 Indeed, other than suggesting that the claims be rewritten—to replace “primary” and
`
`“secondary” with the words “first” and “second”—Flyp offers no evidence whatsoever to dispute
`
`
`1 Flyp’s failure to raise any distinction between the “primary telephone number” and “secondary
`telephone number” forecloses its right to do so on sur-reply. See Liberty Mut. Fire Ins. Co. v.
`Fowlkes Plumbing, LLC, 850 F. App’x 213, 217 (5th Cir. 2021) (holding “arguments raised in a
`sur-reply are not properly preserved” when not articulated in the opposition brief).
`
`-5-
`
`

`

`Case 6:22-cv-00031-ADA Document 52 Filed 09/14/22 Page 7 of 10
`
`
`
`the reality that a POSITA, reading the claim elements in the context of the intrinsic record, would
`
`not be able to determine with reasonable certainty whether or not a particular telephone number
`
`was “primary” or not, or “secondary” or not. Dkt. 49 at 5 (asking Court to treat the disputed
`
`limitations like the “common patent constructs that describe a ‘first’ element and a ‘second’
`
`element”). The claim terms “primary telephone number” and “secondary telephone number” are
`
`thus indefinite. See Infinity Comput. Prods., Inc. v. OKI Data Ams., Inc., 987 F.3d 1053, 1062
`
`(Fed. Cir. 2021) (“[T]he indefiniteness here does not reside in the term ‘passive link’ or ‘computer’
`
`on its own but rather in the relationship between the two in the context of these claims.”); TEVA
`
`Pharms. USA, Inc. v. Sandoz, Inc., 789 F.3d 1335, 1341 (Fed. Cir. 2015) (holding limitation
`
`indefinite where “the claim on its face offers no guidance” and where “[t]here is no express
`
`definition [of the disputed limitation] in the ’808 patent specification”); Interval Licensing LLC v.
`
`AOL, Inc., 766 F.3d 1364, 1371 (Fed. Cir. 2014) (“The claims, when read in light of the
`
`specification and the prosecution history, must provide objective boundaries for those of skill in
`
`the art.”).
`
`III. The Court’s Claim Construction Ruling in the Dialpad Case Does Not Support Flyp
`
`Faced with Google’s indefiniteness arguments, Flyp relies heavily on an earlier case where
`
`the indefiniteness of the “primary” and “secondary” limitations was not even at issue. Dkt. 49 at
`
`2–3 (discussing Flypsi, Inc. v. Dialpad, Inc., No. 6:21-cv-00642-ADA, Dkt. 73 (W.D. Tex. Aug.
`
`22, 2022) (“Dialpad Markman”). In that case, Dialpad sought a particular construction of “primary
`
`telephone number,” and did not allege indefiniteness of that term. Here, both the primary and
`
`secondary telephone number limitations are at issue, and Google has demonstrated the
`
`indefiniteness of those terms in the context of the Asserted Patents. Additionally, while Dialpad
`
`argued for a specific construction of “primary telephone number,” namely that it is a “telephone
`
`number or identifier that is assigned to a handset or mobile device” (Dialpad Markman at 3–4),
`
`-6-
`
`

`

`Case 6:22-cv-00031-ADA Document 52 Filed 09/14/22 Page 8 of 10
`
`
`
`here, Google points out that the intrinsic evidence discloses that both the primary and secondary
`
`telephone numbers can be assigned to a handset or mobile device. Dkt. 47 at 5.
`
`At bottom, the questions presented here were neither raised nor resolved in the Dialpad
`
`Markman. As such, this Court is not bound by the inapposite (and interim) construction proposed
`
`by Dialpad, and may alter “its interpretation of the claim terms as its understanding of the [Asserted
`
`Patents] evolves.” Pfizer, Inc. v. Teva Pharms., USA, Inc., 429 F.3d 1364, 1377 (Fed. Cir. 2005)
`
`(citation omitted) (“Indeed, a conclusion of law such as claim construction is subject to change
`
`upon the development of the record”). And a plain and ordinary meaning construction is simply
`
`not a workable solution. Cf. O2 Micro Int’l Ltd. v. Beyond Innovation Tech. Co., 521 F.3d 1351,
`
`1360 (Fed. Cir. 2008). As discussed above, Flyp’s proposed understanding of the plain and
`
`ordinary meaning (a first and second telephone number) runs contrary to the intrinsic record.
`
`Moreover, the typical meaning of “primary” suggests greater importance or relevance for some
`
`reason or purpose; while the typical meaning of “secondary” implies lesser importance or
`
`relevance for some rationale. But, the determination of a telephone number’s primacy (i.e., its
`
`relative importance or relevance to a user) is necessarily subjective and unguided by any criteria
`
`in the Asserted Patents. The Dialpad claim construction does not resolve the core issue here.
`
`IV. Conclusion
`
`For the foregoing reasons, Google respectfully requests that the Court find “primary
`
`telephone number” and “secondary telephone number” indefinite.
`
`
`
`-7-
`
`

`

`Case 6:22-cv-00031-ADA Document 52 Filed 09/14/22 Page 9 of 10
`
`
`
`DATED: September 14, 2022
`
`
`
`
`Respectfully Submitted,
`
`/s/ Robert W. Unikel
`Robert W. Unikel (Pro Hac Vice)
`robertunikel@paulhastings.com
`John A. Cotiguala (Pro Hac Vice)
`johncotiguala@paulhastings.com
`Daniel J. Blake (Pro Hac Vice)
`danielblake@paulhastings.com
`Grayson S. Cornwell (Pro Hac Vice)
`graysoncornwell@paulhastings.com
`PAUL HASTINGS LLP
`71 South Wacker Drive, Suite 4500
`Chicago, IL 60606
`Telephone: (312) 499-6000
`Facsimile: (312) 499-6100
`
`Robert R. Laurenzi (Pro Hac Vice)
`robertlaurenzi@paulhastings.com
`PAUL HASTINGS LLP
`200 Park Avenue
`New York, NY 10166
`Telephone: (212) 318-6000
`Facsimile: (212) 319-4090
`
`Elizabeth Brann (Pro Hac Vice)
`elizabethbrann@paulhastings.com
`PAUL HASTINGS LLP
`4747 Executive Drive, 12th Floor
`San Diego, CA 92121
`Telephone: (858) 458-3000
`Facsimile: (858) 458-3005
`
`Joshua Yin (Pro Hac Vice)
`joshuayin@paulhastings.com
`David M. Fox (Pro Hac Vice)
`davidfox@paulhastings.com
`PAUL HASTINGS LLP
`1117 S. California Avenue
`Palo Alto, CA 94304
`Telephone: (650) 320-1800
`Facsimile: (650) 320-1900
`
`Paige Arnette Amstutz
`State Bar No.: 00796136
`pamstutz@scottdoug.com
`
`-8-
`
`

`

`
`
`
`
`Case 6:22-cv-00031-ADA Document 52 Filed 09/14/22 Page 10 of 10
`
`SCOTT, DOUGLASS & MCCONNICO, LLP
`303 Colorado Street, Suite 2400
`Austin, TX 78701
`Telephone: (512) 495-6300
`Facsimile: (512) 495-6399
`
`Attorneys for Defendant Google LLC
`
`
`CERTIFICATE OF SERVICE
`
`I hereby certify that on the 14th day of September, 2022, a true and correct copy of the
`
`foregoing document was filed electronically with the Clerk of Court using the CM/ECF system.
`
`As of this date, all counsel of record have consented to electronic service and are being served
`
`with a copy of this document through the Court’s CM/ECF system.
`
`/s/ Robert W. Unikel
`Robert W. Unikel
`
`
`
`-9-
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket