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










`
`
`DEFENDANT GOOGLE LLC’S CORRECTED REPLY IN SUPPORT OF ITS MOTION
`FOR SUMMARY JUDGMENT OF NONINFRINGEMENT OF U.S. PATENT NOS.
`9,667,770 AND 10,051,105
`
`
`
`
`
`
`
`
`
`
`

`

`Case 6:22-cv-00031-ADA Document 218 Filed 12/12/23 Page 2 of 12
`
`TABLE OF CONTENTS
`
`
`Page(s)
`INTRODUCTION ............................................................................................................. 1
`GOOGLE IS ENTITLED TO SUMMARY JUDGMENT BECAUSE
`
`DOES
`NOT USE A “BRIDGE TELEPHONE NUMBER” ......................................................... 2
`A.
`Google’s Motion Properly Applies the Plain and Ordinary Meaning of
`“Bridge Telephone Number” ................................................................................. 2
`It Is Undisputed that the “Bridge Telephone Number” Limitations Were
`Added to the Claims to Overcome the Examiner’s Rejection ............................... 4
`There Is No Genuine Factual Dispute Material to Literal Infringement of
`the “Bridge Telephone Number” Limitations ........................................................ 6
`Flyp Cannot Resort to Doctrine of Equivalents ..................................................... 6
`D.
`CONCLUSION .................................................................................................................. 7
`
`B.
`
`C.
`
`I.
`II.
`
`III.
`
`-i-
`
`

`

`Case 6:22-cv-00031-ADA Document 218 Filed 12/12/23 Page 3 of 12
`
`TABLE OF AUTHORITIES
`
`
`Page(s)
`
`Cases
`
`Advanced Steel Recovery, LLC v. X-Body Equip., Inc.,
`808 F.3d 1313 (Fed. Cir. 2015)..................................................................................................7
`
`Festo Corp. v. Shoketsu Kinzoku Kogyo Kabushiki Co.,
`535 U.S. 722 (2002) ...................................................................................................................7
`
`Lighthouse Consulting Grp. v. BB&T Corp.,
`476 F. Supp. 3d 532 (W.D. Tex. 2020) ......................................................................................7
`
`VLSI Tech. LLC v. Intel Corp.,
`No. 2022-1906, 2023 WL 8360083 (Fed. Cir. Dec. 4, 2023) ....................................................7
`
`
`
`-ii-
`
`

`

`Case 6:22-cv-00031-ADA Document 218 Filed 12/12/23 Page 4 of 12
`Case 6:22-cv-00031-ADA Document 218 Filed 12/12/23 Page 4 of 12
`
`L
`
`INTRODUCTION
`
`Google’s motion for summary judgment of non-infringement of the Incoming Call Patents
`
`(Dkt. 145) presents a clear case for non-infringement. The asserted claims expressly require that a
`
`“bridge telephone number”be sent to a handset and used to connect the handset to an incoming
`
`call. It is undisputed that a “telephone number,”as used in the asserted patents and as conceded by
`
`Flyp, hasits plain and ordinarycnn,
`
`
`
`Dkt. 172-2 § 349 (quoting GOOG-FLYP-00003214). No reasonable juror could understand a
`Po to be or include a bridge telephone number, ifthat term is truly givenits
`plain and ordinary meaning. Indeed, Flyp’s own infringement expert, Dr. Nettles, admits that [ill
`
`PE 2c. at 12.
`
`Flyp’s Opposition raises a numberofissuesto distract the Court from the straight-forward,
`
`fundamental point raised by Google’s Motion—thatPe
`P simply does not transmit or use a bridge telephone number, as required by all the
`
`asserted claims. Ruling on this basis requires no additional claim construction because it is
`
`undisputed and already confirmed that “telephone number,” as used in the asserted claims,hasits
`
`-|-
`
`

`

`Case 6:22-cv-00031-ADA Document 218 Filed 12/12/23 Page 5 of 12
`Case 6:22-cv-00031-ADA Document 218 Filed 12/12/23 Page 5 of 12
`
`ordinary meaning. Any reference to the prosecution history merely confirms that the terms
`
`“telephone number”and “bridge telephone number”are used in the Incoming Call Patents in their
`
`plain and ordinary way.Pe
`
`Flyp’s Opposition suggests that a “telephone number” doesn’t really mean a telephone
`
`number, as any reasonable juror would understand that term, and instead meansP|
`
`I 1228.potence specifically added
`
`the “bridge telephone number”limitations during prosecution to overcomepriorart that expressly
`
`recognized thatP| are “other types of addresses” and not telephone numbers. Dkt. 145 at
`
`7. Had Flyp wanted to construe “bridge telephone number” to mean something other than an
`
`ordinary telephonebe
`a it could have proposed such a construction. It did not. Instead, Flyp and its experts
`
`consistently contendedthat “telephone number”has its plain meaning. Dkt. 145 at 5, n.6.
`
`Resolving Google’s motion simply requires examining[ia
`a. applying the ordinary meaning of “telephone number,” and recognizing thatp
`I is»2° tclepnone number”
`
`Summary judgment of non-infringementis warranted.
`
`Il.
`
`GOOGLEIS ENTITLED TO SUMMARY JUDGMENT BECAUSE
`
`DOES NOT
`
`USE A “BRIDGE TELEPHONE NUMBER”
`
`A.
`
`Google’s Motion Properly Applies the Plain and Ordinary Meaning of
`“Bridge Telephone Number”
`
`Google’s Motion does not propose untimely claim construction, as Flyp suggests. Dkt. 172
`
`at S—7. The motion applies the plain and ordinary meaning ofthe terms “telephone number” and
`
`“bridge telephone number.” Dkt. 145 at 5—6. There is no dispute that these terms have their
`
`

`

`Case 6:22-cv-00031-ADA Document 218 Filed 12/12/23 Page 6 of 12
`Case 6:22-cv-00031-ADA Document 218 Filed 12/12/23 Page 6 of 12
`
`ordinary meanings. Flyp took that position during claim construction,ad
`Dkt. 145, at 5, n. 7. Dr. Nettles’ affirmation that ________
`
`Po (Dkt. 145 at 5, n. 6) was not an answer to a “gotcha question” that fails to
`
`capture the understanding of a person ofskill in the art. Dkt. 172 at 8. It aligns with how any person
`
`(skilled in the art or otherwise) would understand the term “telephone number.” Ex. 17 § 68; Dkt.
`
`152-3; Ex. 18 at 232:15—24, 233:13—234:2, 236:22—237:22, 242:11—23, 243:15—244:10.
`
`Recognizing:
`ee. and not any ordinary telephone number, Flyp now suggests that
`
`“telephone number” means something more than a typical ten-digit dialable number(in the US),
`
`it meansee Dkt. 172 at 8. No matter how much Flyp’s
`
`Opposition tries to suggest that the meaning of “telephone number”to a person of skill in the art
`
`reading the Incoming Call Patents includesPe
`ee. this suggestion clearly requires a definition
`
`of “telephone number”that differs from that term’s plain and ordinary meaning.! Yet, Flyp did not
`
`offer such a contrary definition during claim construction, and instead consistently agreed until
`
`now that “telephone number”did not have any special or unusual meaning as used in the asserted
`
`claims. Dkt. 145 at 5, n.7; Dkt. 172 at 5, 8, 11. Flyp, not Google, seeks untimely construction.
`
`Google’s expert did not testify that the term “telephone number” can mean any unique
`
`identifier for a destination. Dkt. 172 at 9. Dr. Gottesmantestified thatPo
`
`SS172 00
`
`1 Tfyour neighborasks your“telephone number,” youdo not think to provide aa
`
`-3-
`
`

`

`Case 6:22-cv-00031-ADA Document 218 Filed 12/12/23 Page 7 of 12
`
`
` In any event, the specification’s discussion of an
`
`“ESN,” and whatever was meant to be referred to by that term with reference to a primary
`
`telephone number has nothing to do with the relevant, and explicit, “bridge telephone number”
`
`claim element, which the parties and all experts agree has its plain and ordinary meaning. Nothing
`
`in the specification or the claims suggests that an ESN or
`
` can be a bridge telephone number.
`
`B.
`
`It Is Undisputed that the “Bridge Telephone Number” Limitations Were
`Added to the Claims to Overcome the Examiner’s Rejection
`
`Flyp does not deny that it added the term “bridge telephone number” to the asserted claims
`
`of the ’770 patent to overcome the Examiner’s rejection of pending claims that did not originally
`
`include that term. Dkt. 145 at 8–9. Flyp does not deny that it added “bridge telephone number”
`
`three times in that claim amendment: “the switch being associated with a bridge telephone
`
`number,” “including the bridge telephone number,” and “using the bridge telephone number.” Id.
`
`Flyp does not deny that the amendment was made in response to the Examiner’s rejection based
`
`on Black. Dkt. 172 at 4. Flyp does not deny that its amendment was meant to differentiate Black’s
`
`teachings from the amended claims. Dkt. 172 at 3. Flyp does not deny that Black expressly taught
`
`that a telephone number was distinguished from “other types of addresses, such as a
`
`
`
`Dkt. 145 at 7. The prosecution history confirms that the claim term “bridge telephone number”
`
`was used in accord with its ordinary meaning, which is different from a
`
` The Black
`
`reference makes explicit the understanding in the art at the time of the alleged invention that a
`
`
`
` is one of the “other types of addresses,” different than a telephone number. Dkt. 145 at 7.
`
`Flyp argues that when rejecting the pending claims (that did not include “bridge telephone
`
`number”) as anticipated by Black, the Examiner “understood the term ‘telephone number’ to be
`
`broader than a U.S. ten-digit number.” Dkt. 172 at 3. Flyp further argues that Flyp’s remarks
`
`accompanying the claim amendments that included “bridge telephone number” responsive to the
`
`-4-
`
`

`

`Case 6:22-cv-00031-ADA Document 218 Filed 12/12/23 Page 8 of 12
`
`
`rejection over Black merely “confirmed that the amendment was directed to differentiating Black
`
`[] on how the relevant telephone numbers are used . . . without distinguishing the telephone
`
`numbers in the claims in any way from the ‘alias addresses’ that the Examiner [supposedly]
`
`identified as telephone numbers in Black.” Dkt. 172 at 3–4. Here, again, is an attempt by Flyp to
`
`deflect the simple question of non-infringement by creating complexities where there are none.
`
`Flyp’s remarks to the Examiner plainly show that the bridge telephone number limitation was
`
`added to the pending claims because Black did not a teach “bridge telephone number” (Dkt. 145
`
`at 8–9, Dkt. 172 at 4), and Black undeniably taught that telephone numbers were understood to be
`
`different types of addresses from
`
` (“that the addresses of the communications devices are
`
`not limited to telephone numbers, but can include other types of addresses, such as, for example,
`
`” Dkt. 145 at 7 (emphasis
`
`added). It is irrelevant that the Examiner did not point to this particular paragraph of Black’s
`
`teaching in the rejection. Flyp distinguished that teaching (“Black fails to disclose or suggest”)
`
`when seeking allowance of the amended claim that added “bridge telephone number” as a
`
`limitation three times to the claim. Id. at 8–9.
`
`Though Flyp argues that there was no mention of
`
` or any distinction between
`
`telephone numbers and addresses in the Examiner’s initial rejection of the pending claim over
`
`Black, the Examiner cited paragraphs 58 and 61 of the Black reference when rejecting the
`
`“transmitting” and “processing” terms, which were thereafter amended by Flyp to include the three
`
`recitations of “bridge telephone number.” Paragraph 58 of Black states that “the alias service
`
`provider 180 provides a notification to the telephone (such as voice or text message) that provides
`
`an indication regarding which alias number the inbound call is associated with.” Dkt. 145 at 7;
`
`Dkt. 146-5 (“Black”) ¶ 58. Flyp amended claim 1 to recite a “bridge telephone number,” rather
`
`-5-
`
`

`

`Case 6:22-cv-00031-ADA Document 218 Filed 12/12/23 Page 9 of 12
`
`
`than a “bridge address” or “bridge number,” to overcome Black’s teaching of pre-call information
`
`in the form of an alias address using
`
` Flyp’s amendment adding bridge telephone number
`
`thus distinguished a telephone number from a mere “alias number.” In short, the prosecution
`
`history confirms that “bridge telephone number” was added to overcome a prior art rejection, and
`
`that the term was used in accord with its plain meaning, which does not include a
`
`
`
`C.
`
`There Is No Genuine Factual Dispute Material to Literal Infringement of the
`“Bridge Telephone Number” Limitations
`
`Ultimately, Flyp raises no factual dispute material to whether
`
`
`
` includes transmission and use of the required “bridge telephone
`
`number.”
`
`
`
`
`
` And Flyp
`
`and its expert identify
`
` as allegedly containing the bridge
`
`telephone number. Supra, Introduction; Dkt. 145 at 11.
`
` Dkt. 172 at 12.
`
` Id. Flyp’s Opposition argues that because Dr. Nettles opined that
`
`
`
`
`
`
`
`
`
`
`
` Id. That is not a factual dispute, it is
`
`an untimely attempt to give bridge telephone number something other than its ordinary meaning.
`
`D.
`
`Flyp Cannot Resort to Doctrine of Equivalents
`
`The amendment to the claims that added the “bridge telephone number” limitations was
`
`directly related to the Examiner’s rejection based on Black, which expressly distinguished
`
`telephone numbers from “other types of addresses, such as a
`
` See supra § II.B. The
`
`-6-
`
`

`

`Case 6:22-cv-00031-ADA Document 218 Filed 12/12/23 Page 10 of 12
`
`
`claims that Flyp amended to add the “bridge telephone number” elements had been rejected based
`
`on Black’s teaching in paragraph 58 of “alias numbers.” Id. Flyp suggests that the applicant and
`
`the Examiner both understood that “alias numbers” in Black encompassed telephone numbers, i.e.,
`
`that an “alias number” is a broader term than a “telephone number” and a telephone number falls
`
`within the meaning of an alias number. Dkt 172 at 3, 13–14. This conjecture is not supported by
`
`the record of the rejection, amendment, and related arguments. And it is irrelevant anyway because
`
`the amendment adding the “bridge telephone number” limitations to the claims was made to
`
`overcome the rejection based on Black. This creates the legal presumption that prosecution history
`
`estoppel applies. Festo Corp. v. Shoketsu Kinzoku Kogyo Kabushiki Co., 535 U.S. 722, 740 (2002);
`
`Lighthouse Consulting Grp. v. BB&T Corp., 476 F. Supp. 3d 532, 537–38 (W.D. Tex. 2020). Flyp
`
`has not rebutted, and cannot rebut, the presumption.
`
`Furthermore, Flyp did not respond in any way to Google’s showing that even if Flyp could
`
`pursue a DOE theory, Flyp failed to present evidence that
`
`
`
` is not done in the same way, and does not achieve the same result, as using the
`
`required bridge telephone number. Dkt. 145 at 15–17. Summary judgment of noninfringement is
`
`thus warranted even if Flyp could invoke the doctrine of equivalents. See Advanced Steel Recovery,
`
`LLC v. X-Body Equip., Inc., 808 F.3d 1313, 1320 (Fed. Cir. 2015) (dismissing DOE claim on
`
`summary judgment because Plaintiff failed to satisfy the “way” portion of the function-way-result
`
`test); VLSI Tech. LLC v. Intel Corp., No. 2022-1906, 2023 WL 8360083, at *7 (Fed. Cir. Dec. 4,
`
`2023) (finding expert’s opinion insufficient as containing “no meaningful explanation of why the
`
`way in which the request is made is substantially the same as what the claim prescribes.”).
`
`III. CONCLUSION
`
`The Court should grant Google’s motion for partial summary judgment of noninfringement
`
`of the Incoming Call Patents.
`
`-7-
`
`

`

`Case 6:22-cv-00031-ADA Document 218 Filed 12/12/23 Page 11 of 12
`
`
`DATED: December 6, 2023
`
`
`
`
`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
`
`Elizabeth Brann (Pro Hac Vice)
`elizabethbrann@paulhastings.com
`Ariell N. Bratton (Pro Hac Vice)
`ariellbratton@paulhastings.com
`PAUL HASTINGS LLP
`4655 Executive Drive, Suite 350
`San Diego, CA 92121
`Telephone: (858) 458-3000
`Facsimile: (858) 458-3005
`
`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
`
`Joshua Yin (Pro Hac Vice)
`joshuayin@paulhastings.com
`PAUL HASTINGS LLP
`1117 S. California Avenue
`Palo Alto, CA 94304
`Telephone: (650) 320-1800
`Facsimile: (650) 320-1900
`
`Dan L. Bagatell (Pro Hac Vice)
`dbagatell@perkinscoie.com
`PERKINS COIE LLP
`
`-8-
`
`

`

`Case 6:22-cv-00031-ADA Document 218 Filed 12/12/23 Page 12 of 12
`
`
`3 Weatherby Road
`Hanover, NH 03755
`Telephone: (602) 351-8250
`Facsimile: (602) 648-7150
`
`Andrew T. Dufresne (Pro Hac Vice)
`adufresne@perkinscoie.com
`PERKINS COIE LLP
`33 E. Main St. Ste. 201
`Madison, WI 53703
`Telephone: (608) 663-7460
`Facsimile: (608) 663-7499
`
`Paige Arnette Amstutz
`State Bar No.: 00796136
`pamstutz@scottdoug.com
`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 6th day of December, 2023, 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 and by email.
`
`/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