throbber
Case 6:22-cv-00031-ADA Document 57 Filed 09/28/22 Page 1 of 11
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE WESTERN DISTRICT OF TEXAS
`WACO DIVISION
`
`
`
`
`
` Civil Action No. 6:22-cv-31-ADA
`
`
`
` JURY TRIAL DEMANDED
`
`FLYPSI, INC. (D/B/A FLYP),
`
` Plaintiff,
`
` vs.
`
`GOOGLE LLC,
`
` Defendant.
`
`
`
`
`
`PLAINTIFF FLYPSI, INC.’S SUR-REPLY CLAIM CONSTRUCTION BRIEF
`
`
`
`
`
`

`

`Case 6:22-cv-00031-ADA Document 57 Filed 09/28/22 Page 2 of 11
`
`I.
`
`INTRODUCTION
`
`Google’s position ignores the “bedrock principle” of claim construction—that “the claims
`
`of a patent define the invention to which the patentee is entitled the right to exclude.” Phillips v.
`
`AWH Corp., 415 F.3d 1303, 1312 (Fed. Cir. 2005) (en banc). Contrary to this now well-established
`
`axiom, Google divorces the terms “primary telephone number” and “secondary telephone number”
`
`from the surrounding context of the claims in which they appear. Even though it was invited to
`
`do so by Flyp, Google’s Reply Brief (Dkt. No. 52) fails to include any discussion of the claim
`
`language in which the terms “primary telephone number” and “secondary telephone number” are
`
`found. When these terms are properly considered in context of the surrounding claim language,
`
`they are readily understood with reasonable certainty and should be afforded their plain and
`
`ordinary meanings. Google’s self-serving expert declaration, which lacks any technical merit and
`
`provides only basic linguistic opinions, cannot overcome the plain language of the claims
`
`themselves, which is unambiguous and definite.
`
`II.
`
`ARGUMENT
`
`As an initial matter, Google ignores settled principles of claim construction. Here, the
`
`analysis can begin and end with the claims themselves, which Google ignores.
`
`Google’s arguments in Reply do not salvage its position and should be rejected. Google
`
`first argues that Flyp is attempting to re-write the claims. This argument ignores Flyp’s actual
`
`position—that the claims should be given their plain and ordinary meaning. Second, Google
`
`attempts to analogize the terms “primary telephone number” and “secondary telephone number”
`
`to inapposite caselaw considering subjective terms or terms of degree—like “high pressure” or
`
`“aesthetically pleasing.” Google’s analogies are ineffective. The terms in dispute here are not
`
`subjective and are not terms of degree—they are readily understandable terms delineating two
`
`1
`
`
`

`

`Case 6:22-cv-00031-ADA Document 57 Filed 09/28/22 Page 3 of 11
`
`subjects that the remainder of the claim language properly contextualizes. Third, Google attempts
`
`to sidestep this Court’s prior consideration of the term “primary telephone number.” Google,
`
`however, fails to address the substance of this Court’s reasoning—that the term primary telephone
`
`number “is not difficult or too technical in nature” and that “[i]t is not necessary to distinguish
`
`primary and secondary telephone numbers through construction because these phrases will likely
`
`be understood by a person of ordinary skill in the art and the jury will likely not be confused by
`
`the terms.” Dkt. No. 49, Ex. A at 5.
`
`A.
`
`Google Ignores the Intrinsic Records and Rests Its Argument on the
`Declaration of Its Paid Expert.
`
`Google’s approach separates the claim terms from all intrinsic evidence, rejecting the most
`
`basic principle of claim construction. When read within the context of the rest of the claim and
`
`the dependent claims, it is exceedingly clear that “primary” and “secondary” are terms used to
`
`distinguish between two “telephone number” elements without conflating them with other
`
`“bridge” telephone numbers and “contact” telephone numbers.
`
`Looking just at claim 1 of the ’770 Patent (directed to receiving inbound calls to the
`
`secondary number) and claim 1 of the ’094 Patent (directed to placing outbound calls from a
`
`secondary number), the following claim limitations provide context for the difference between the
`
`claimed primary and secondary numbers:
`
`• “associating a secondary telephone number with a primary telephone number in at
`least one computer memory device, the primary telephone number being assigned
`to a handset,” (’770 Patent, cl. 1);
`
`• “the first digital information indicating primary call processing rules for handling
`calls directed to the primary telephone number,” (id.);
`
`• “the second digital information indicating secondary call processing rules for
`handling calls directed to the secondary telephone number,” (id.);
`
`2
`
`
`

`

`Case 6:22-cv-00031-ADA Document 57 Filed 09/28/22 Page 4 of 11
`
`• “receiving an incoming call . . . the incoming call being directed to a handset-
`associated telephone number, the handset-associated telephone number being the
`primary telephone number or the secondary telephone number,” (id.);
`
`• “transmitting pre-call information to the handset over the at least one data channel
`the pre-call information including the bridge telephone number and the handset-
`associated telephone number, such that the handset is capable of displaying the
`handset-associated telephone number to a user,” (id.);
`
`• “automatically storing electronic information that indicates an association of a
`secondary telephone number and a primary telephone number with a telephone
`handset,” (’094 Patent, cl. 1);
`
`• “automatically associating each primary telephone number and bridge or access
`telephone number pairing with a corresponding secondary telephone number and
`contact telephone number pairing,” (id.);
`
`• “receiving, at the server, information from the switch indicating the outgoing call
`is being made to the bridge or access telephone number from the primary telephone
`number,” (id.); and
`
`• “receiving, at the switch, information from the server directing the switch to: (a)
`connect the outgoing call to a contact telephone number associated with the primary
`telephone number and bridge or access telephone number pairing, and (b) identify
`a telephone number from which the outgoing call is being made as the secondary
`telephone number,” (id.).
`
`Google’s briefs in this case fail to account for any of this context (not to mention similar
`
`context in the dependent claims of the ’770 and ’094 Patents, and all claims of the ’105 Patent, the
`
`’554 Patent, and the ’585 Patent). Rather than account for this claim language, Google relies on
`
`its expert’s declaration, parading James Bress’s purported technical qualifications within electrical
`
`engineering, telecommunications systems, and software design. Dkt. No. 52 at 6. Mr. Bress’s
`
`declaration, however, presents a purely linguistic and conclusory statement about the meaning of
`
`“primary” and “secondary,” without expressing a technical opinion as to “primary telephone
`
`number” and “secondary telephone number.” See Dkt. No. 47-1 at 10–11. Bress does not so much
`
`as point to English or technical dictionary definitions of the words “primary” and “secondary,” but
`
`3
`
`
`

`

`Case 6:22-cv-00031-ADA Document 57 Filed 09/28/22 Page 5 of 11
`
`rather expects that supposed technical expertise is a functional stand-in for linguistic knowledge
`
`without leveraging such expertise for his opinion.
`
`Google’s approach thus separates the claim terms from all intrinsic evidence, rejecting the
`
`most basic principle of claim construction. The general rule is that claim terms are given their
`
`plain and ordinary meaning. Phillips, 415 F.3d at 1312. Extrinsic evidence is “less significant
`
`than the intrinsic record in determining the legally operative meaning of claim language.” Id. at
`
`1317 (quoting C.R. Bard, Inc. v. U.S. Surgical Corp., 388 F.3d 858, 862 (Fed. Cir. 2004)). An
`
`expert’s conclusory or unsupported assertions as to the meaning of a term are not helpful. Id.
`
`The plain and ordinary meanings of primary and secondary telephone numbers naturally
`
`contrast with each other—especially when considered in the full context of the claim in which they
`
`appear. Google has not shown how a person of ordinary skill in the art would be unable to ascertain
`
`the meaning of these terms within the context of the claims. Google also has not shown how a
`
`person of ordinary skill in the art would be unable to ascertain the meaning of these terms within
`
`the context of the rest of the intrinsic record—including portions of the specification providing
`
`explanations of these terms within the preferred embodiment. E.g., ’770 Patent at 5:2-4 (“The
`
`primary telephone number, preferably, may be a SIM number or ESN which is assigned to the
`
`handset 340 at the time of activation.”) and 5:4-14 (“Once selected, the handset 340 may
`
`automatically transmit information which to the server 100 over the data channel which requests
`
`that the secondary telephone numbers be associated with the primary telephone number. In
`
`response, the server 100 may store (i.e., reference) information indicating the association of the
`
`one or more selected secondary telephone numbers in computer memory associated with the server
`
`such as the database 120. In an alternative embodiment, the server 100 may automatically assign
`
`one or more secondary telephone numbers to the handset 340, as opposed to them being selected.”).
`
`4
`
`
`

`

`Case 6:22-cv-00031-ADA Document 57 Filed 09/28/22 Page 6 of 11
`
`As the Court previously found with respect to “primary telephone number,” these terms
`
`are not difficult or too technical in nature such that a construction would aid the jury in
`
`understanding. Kroy IP Holdings, LLC v. Safeway, Inc., No. 2:12-cv-800-WCB, 2014 WL
`
`3735222, at *2 (E.D. Tex., July 28, 2014). Similarly, these terms do not fit within any of the
`
`exceptions of lexicography or disclaimer to warrant a departure from the plain and ordinary
`
`meaning. See Thorner v. Sony Comput. Entm’t Am. LLC, 669 F.3d 1362, 1365 (Fed. Cir. 2012).
`
`As long as one understands the meaning of “telephone number,” which is not in dispute here, the
`
`meanings of “primary telephone number” and “secondary telephone number” are simple to
`
`understand. These phrases will be easily understood by a person of ordinary skill in the art and
`
`the jury will not be confused by the terms.
`
`When read within the context of the claims and the specification, it is exceedingly clear
`
`that “primary” and “secondary” are terms used to distinguish between two “telephone number”
`
`elements without conflating them with the plural and numbered “bridge” telephone numbers and
`
`“contact” telephone numbers. Accordingly, the Court should reject Google’s request that the terms
`
`“primary telephone number” and “secondary telephone number” be found indefinite.
`
`B.
`
`Google’s Reply Misrepresents Flyp’s Position
`
`In its reply, Google spends a significant amount of time misrepresenting Flyp’s position.
`
`Google misrepresents Flyp’s position by asserting that Flyp argued that “primary” means “first”
`
`and “secondary” means “second.” See Dkt. No. 52 at 2. Flyp’s position is more nuanced. As Flyp
`
`stated in its response, “the ‘primary’ and ‘secondary’ terms merely distinguish two ‘telephone
`
`number’ elements that appear in subsequent limitations, like their respective synonyms ‘first’ and
`
`‘second.’” Dkt. No. 49 at 2. In doing so, Flyp did not equate primary with first and secondary
`
`with second. Instead, Flyp correctly illustrated that the use of primary and secondary within the
`
`5
`
`
`

`

`Case 6:22-cv-00031-ADA Document 57 Filed 09/28/22 Page 7 of 11
`
`full context of the claims are “objective terms of differentiation, not unlike common patent
`
`constructs that describe a ‘first’ element and a ‘second’ element.” Id. at 5. Contrary to Google’s
`
`suggestion, Flyp is not rewriting the claims here and is instead merely requesting that the claim
`
`terms be given their plain and ordinary meaning. The Court need not engage with Google’s straw
`
`man regarding “first” and “second.”
`
`C.
`
`Google’s Attempt to Analogize This Case to Terms of Degree or Subjective
`Terms Fails.
`
`Next, Google attempts to analogize the disputed terms to other subjective terms or terms
`
`of degree. Google stretches to compare the terms “high pressure” in U.S. Well Services and
`
`“aesthetically pleasing” in Datamize to “primary telephone number” and “secondary telephone
`
`number.” See Dkt. No. 52 at 4–6 (citing U.S. Well Services, Inc. v. Halliburton Company, No.
`
`6:21-cv-00367-ADA, 2022 WL 819548 (W.D. Tex. Jan. 17, 2022), and citing Datamize, LLC v.
`
`Plumtree Software, Inc., 417 F.3d 1342 (Fed. Cir. 2005)). Google’s analogies are inapposite.
`
`Neither “high pressure” nor “aesthetically pleasing” are used to distinguish between numbers of
`
`subjects like the disputed terms do. “High pressure” is a term of degree, while “aesthetically
`
`pleasing” is plainly subjective. Both refer to a single subject and are incomparable to the terms in
`
`dispute.
`
`In U.S. Well Services, the term “high pressure” was found indefinite for failing to inform,
`
`with reasonable certainty, those skilled in the art about the scope of the invention. U.S. Well
`
`Services, 2022 WL 819548, at *9. In U.S. Well Services, the Court made its reasoning clear:
`
`The Court finds that the intrinsic and extrinsic evidence does not
`provide any “objective baseline”
`to enable a POSITA
`to
`differentiate “high pressure” from non-high pressure. “Terms of
`degree are problematic if their baseline is unclear to those of
`ordinary skill in the art.” See Liberty Ammunition, Inc. v. United
`States, 835 F.3d 1388, 1395 (Fed. Cir. 2016) (explaining that a term
`of degree “necessarily calls for a comparison against some
`baseline,” but finding the claim term “reduced area of contact” not
`6
`
`
`

`

`Case 6:22-cv-00031-ADA Document 57 Filed 09/28/22 Page 8 of 11
`
`indefinite because the specification identified two examples to
`compare with one another. The specifications of the Asserted
`USWS Patents do not provide guidance that would clarify the
`meaning of the term “high pressure,” or provide a baseline of
`comparison to allow skilled artisans to differentiate a pump that is
`“high pressure” from a pump that is “not high pressure.”
`
`U.S. Well Services, Inc. at *6–7.
`
`“[P]rimary telephone number” and “secondary telephone number” are plainly not terms of
`
`degree. Google has not presented any argument that the terms “primary telephone number” and
`
`“secondary telephone number” are terms of degree, only that a “primary telephone number” and
`
`“secondary telephone number” are not differentiated from each other. See Dkt. No. 52 at 4–5.
`
`Indeed, Google dances right around the core point: “primary” and “secondary” are the very words
`
`that distinguish between the “primary telephone number” and “secondary telephone number.”
`
`Google’s analogy conflates this concept of distinction with terms of degree.
`
`Google, in its reply, attempts to defend its analogy of the terms in the present case to the
`
`term “aesthetically pleasing” in Datamize. See Dkt. No. 52 at 5–6. Google repeats its assertion
`
`that the “ordinary and customary meaning” of the limitations is “quite subjective” and contends a
`
`need to “remove these limitations from ‘a matter of subjective opinion.’” Id. But Google’s
`
`premise that the terms are “inherently subjective” is unsupported, flawed, and contrary to the plain
`
`language of the claims. As discussed in Flyp’s response, the only support that Google provides
`
`for this proposition is the declaration of Mr. Bress, which is conclusory and contrary to well-settled
`
`claim construction principles. See, e.g., Allergan Sales, LLC v. Teva Pharm. USA, Inc., No. 2:15-
`
`cv-01471-JRG-RSP, 2017 WL 4800734, at *6 (E.D. Tex. Sept. 28, 2017) (“Whether in the context
`
`of claim construction or summary judgment, conclusory expert testimony is not entitled weight.”)
`
`In the Datamize case, “aesthetically pleasing” meant “‘having beauty that gives pleasure
`
`or enjoyment’, or in other words, ‘beautiful.’” Datamize., 417 F.3d at 1348. In the same opinion,
`
`7
`
`
`

`

`Case 6:22-cv-00031-ADA Document 57 Filed 09/28/22 Page 9 of 11
`
`the Federal Circuit confirmed that the phrase “should be considered in the context of [the asserted]
`
`claim.” Id. Google has done no such thing here, instead opting to segregate the terms “primary”
`
`and “secondary.” The Datamize court explicitly differentiated this from other terms that may
`
`sound subjective in the abstract (e.g., “desired”), but that “do not depend on a particular person’s
`
`unfettered, subjective opinion” when read within the context of the claim. Id. at 1352.
`
`“[P]rimary telephone number” and “secondary telephone number” do not depend on a
`
`particular person’s unfettered, subjective opinion. Rather, the phrases distinguish those telephone
`
`numbers from each other in the succeeding claim limitations. Once properly taken within the
`
`context of the claims, rather than pulled into a vacuum, it is plainly clear that whether any given
`
`accused product has both a primary and a secondary telephone number does not depend on a
`
`subjective opinion but rather on objective claim application. Accordingly, like the other terms in
`
`Datamize, “primary telephone number” and “secondary telephone number” are not subjective, but
`
`rather reflect their plain and ordinary meaning.
`
`D.
`
`Google Fails to Engage With the Substance of This Court’s Prior Ruling.
`
`Finally, Google attempts to sidestep this Court’s prior consideration of the term “primary
`
`telephone number.” Google relies on the fact that indefiniteness was not previously raised for this
`
`term in the earlier Dialpad claim construction. In doing so, Google fails to engage whatsoever
`
`with the substance of this Court’s prior ruling.
`
`While this Court admittedly did not consider whether the term is indefinite, the Court very
`
`much did consider whether the term (a) required construction or (b) was readily understood by
`
`persons of ordinary skill within the context of the intrinsic record. Google’s present argument
`
`cannot be squared with the Court’s prior reasoning that the term “is not difficult or too technical
`
`in nature” and that “[i]t is not necessary to distinguish primary and secondary telephone numbers
`
`through construction because these phrases will likely be understood by a person of ordinary skill
`8
`
`
`

`

`Case 6:22-cv-00031-ADA Document 57 Filed 09/28/22 Page 10 of 11
`
`in the art and the jury will likely not be confused by the terms.” Dkt. No. 49, Ex. A at 5. The
`
`Court’s consideration of these issues and the Court’s ultimate conclusion is fatal to Google’s
`
`current argument.
`
`III. CONCLUSION
`
`For the foregoing reasons, Flyp respectfully requests the Court apply to “primary telephone
`
`number” and “secondary telephone number” their plain and ordinary meanings.
`
`
`
`DATED: September 28, 2022
`
`Respectfully submitted,
`
`/s/ Michael A. Bittner
`Thomas M. Melsheimer
`Texas Bar No. 13922550
`tmelsheimer@winston.com
`M. Brett Johnson
`Texas Bar No. 00790975
`mbjohnson@winston.com
`Michael A. Bittner
`Texas Bar No. 24064905
`mbittner@winston.com
`Steven R. Laxton
`Texas Bar No. 24120639
`slaxton@winston.com
`WINSTON & STRAWN LLP
`2121 North Pearl Street, Suite 900
`Dallas, TX 75201
`Telephone: (214) 453-6500
`
`Matthew R. McCullough
`California Bar No. 301330
`mrmccullough@winston.com
`WINSTON & STRAWN LLP
`275 Middlefield Road, Suite 205
`Menlo Park, CA 94025
`Telephone: (650) 858-6500
`
`William M. Logan
`Texas Bar No. 24106214
`wlogan@winston.com
`WINSTON & STRAWN LLP
`
`9
`
`
`

`

`Case 6:22-cv-00031-ADA Document 57 Filed 09/28/22 Page 11 of 11
`
`800 Capitol Street, Suite 2400
`Houston, TX 77002
`Telephone: (713) 651-2766
`
`ATTORNEYS FOR PLAINTIFF
`
`CERTIFICATE OF SERVICE
`
`I hereby certify that a copy of the foregoing document was filed electronically in
`compliance with Local Rule CV-5. Therefore, this document was served on all counsel who are
`deemed to have consented to electronic service. Administrative Policies and Procedures for
`Electronic Filing in Civil and Criminal Cases, Western District of Texas, Section 14.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`/s/ Michael A. Bittner
`Michael A. Bittner
`
`
`
`10
`
`
`

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