throbber
Case 6:22-cv-00031-ADA Document 127 Filed 08/18/23 Page 1 of 11
`
`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 OPPOSED MOTION TO STAY
`PENDING INTER PARTES REVIEW
`
`
`
`
`
`
`
`

`

`Case 6:22-cv-00031-ADA Document 127 Filed 08/18/23 Page 2 of 11
`
`I.
`
`INTRODUCTION
`In July and August of this year, inter partes review proceedings were instituted as to all
`
`asserted claims of all Asserted Patents. Given that the final written decisions in these IPRs will
`
`result either in invalidity of all asserted claims or in substantial narrowing and clarification of the
`
`invalidity issues requiring resolution in this action, Defendant Google LLC moves to stay this case
`
`at the conclusion of fact discovery (scheduled for August 22, 2023) pending final resolution of the
`
`instituted IPRs, including any resulting appeals.
`
`Because Google proposes staying this case at the conclusion of fact discovery, which is
`
`imminent, Plaintiff Flyp will not be damaged or prejudiced by the requested stay, as evidence will
`
`not become stale. And the most important factor in the stay analysis–simplification of the issues–
`
`weighs heavily in favor of a stay. There is no doubt that pausing expert discovery, dispositive and
`
`Daubert motion practice, pre-trial practice and trial until after the core invalidity issues raised by
`
`the instituted IPRs are resolved will prevent the parties and the Court from expending significant
`
`time, money and effort addressing issues that necessarily will be settled by the Patent Office.
`
`Indeed, there is a strong possibility that the instituted IPRs will result in invalidity of all asserted
`
`claims and patents, thus ending this case and rendering all further actions by the Court and the
`
`parties a wasteful nullity. Accordingly, a stay pending completion of the instituted IPRs is
`
`warranted in this case.1
`
`II.
`
`STATEMENT OF FACTS
`
`
`
`Plaintiff filed the complaint in this action on January 10, 2022, asserting five patents:
`
`U.S. Patent Nos. 9,667,770 (“’770 Patent”); 10,051,105 (“’105 Patent”); 10,334,094 (“’094
`
`
`1 The parties met and conferred concerning Google’s request for a stay, and Flyp indicated that it
`opposes Google’s request.
`
`1
`
`

`

`Case 6:22-cv-00031-ADA Document 127 Filed 08/18/23 Page 3 of 11
`
`Patent”); 11,012,554 (“’554 Patent”); and 11,218,585 (“’585 Patent”) (collectively the “Asserted
`
`Patents”).
`
`
`
`On January 10, 2023, Google petitioned for IPR of all asserted claims of all five patents.
`
`See Declaration of John Cotiguala (“Cotiguala Decl.”) ¶¶ 2-6; Exs. 1-5. Every IPR was instituted
`
`as follows:
`
`●
`
`’770 Patent: IPR2023-00360 was granted institution on August 2, 2023 on all claims
`
`asserted in this case (claims 1-6). See Cotiguala Decl. ¶ 2; Ex. 1.
`
`●
`
`’105 Patent: IPR2023-00361 was granted institution on July 31, 2023 on all claims
`
`asserted in this case (claims 1-11). See Cotiguala Decl. ¶ 3; Ex. 2.
`
`●
`
`’094 Patent: IPR2023-00358 was granted institution on July 31, 2023 on all claims
`
`asserted in this case (claims 1-4). See Cotiguala Decl. ¶ 4; Ex. 3.
`
`●
`
`’554 Patent: IPR2023-00359 was granted institution on July 31, 2023 on all claims
`
`asserted in this case (claims 1-4). See Cotiguala Decl. ¶ 5; Ex. 4.
`
`●
`
`’585 Patent: IPR2023-00357 was granted institution on July 31, 2023 on all claims
`
`asserted in this case (claims 1-4). See Cotiguala Decl. ¶ 6; Ex. 5.
`
`Because all claims asserted in this case are at issue in the IPRs, the outcome of the IPRs has the
`
`potential to resolve all issues in this case. Final written decisions are expected within one-year of
`
`the institution dates, around August 2024.
`
`
`
`Trial in this case is presently set for February 19, 2024. Dkt. 112. Claim construction is
`
`complete and the parties are currently completing fact discovery, which is set to close on August
`
`22, 2023. Id.
`
`
`
`
`
`2
`
`

`

`Case 6:22-cv-00031-ADA Document 127 Filed 08/18/23 Page 4 of 11
`
`III. LEGAL AUTHORITY
`
`“[T]he power to stay proceedings is incidental to the power inherent in every court to
`
`control the disposition of the causes on its docket with economy of time and effort for itself, for
`
`counsel, and for litigants.” Landis v. N. Am. Co., 299 U.S. 248, 254 (1936). Courts generally
`
`consider three factors when determining whether to stay patent litigation in light of IPR
`
`proceedings: “(1) whether the stay will unduly prejudice the nonmoving party, (2) whether the
`
`proceedings before the court have reached an advanced stage, including whether discovery is
`
`complete and a trial date has been set, and (3) whether the stay will likely result in simplifying the
`
`case before the court.” NFC Tech. LLC v. HTC Am., Inc., No. 2:13-cv-1058, 2015 WL 1069111,
`
`at *2 (E.D. Tex. Mar. 11, 2015); see also Nobots, LLC v. Google, LLC, No. 1:22-cv-00585-RP,
`
`Dkt. 53, at 1 (W.D. Tex. July 13, 2022).
`
`Based on those factors, courts determine whether the benefits of a stay outweigh the
`
`inherent costs of postponing resolution of the litigation. CyWee Grp. Ltd. v. Samsung Elecs. Co.,
`
`No. 2:17-cv-00140-WCB, 2019 WL 11023976, at *2 (E.D. Tex. Feb. 14, 2019). A stay is
`
`“particularly justified” when the outcome of a Patent Office proceeding is likely to assist the court
`
`in determining patent validity or eliminate the need to try infringement issues. Id. at *1. Indeed,
`
`the “most important” factor in the stay analysis is whether the issues will be simplified. NFC Tech.,
`
`2015 WL 1069111, at *4.
`
`IV. ARGUMENT
`
`
`
`A. The stay will result in simplifying the case and may dispose of the case.
`
`The “most important” factor in the stay analysis–simplification of the issues–weighs
`
`heavily in favor of a stay. Google’s instituted IPR petitions challenge the validity of every claim
`
`3
`
`

`

`Case 6:22-cv-00031-ADA Document 127 Filed 08/18/23 Page 5 of 11
`
`of every Asserted Patent. Favorable resolution of Google’s IPRs would thus eliminate the need for
`
`this Court to decide any issues of validity or infringement.
`
`Even if the Patent Trial and Appeal Board (“PTAB”) does not determine that all claims of
`
`the Asserted Patents are unpatentable, the issues in this case will be significantly narrowed and
`
`clarified by final written decisions in the IPRs. If the PTAB determines some claims are not
`
`unpatentable, then the scope of the case necessarily will be narrowed to those claims that survive
`
`the IPRs. Moreover, as to any surviving claims, estoppel under 35 U.S.C. § 315(e)(2) will apply,
`
`significantly reducing and focusing the invalidity grounds that can be addressed by experts, in
`
`dispositive motions and at trial in this action. Staying this case pending completion of the IPRs
`
`also will permit the Court and the parties to benefit from the rulings of the PTAB judges who will
`
`evaluate the prior art grounds cited in Google’s petitions and determine the validity of Plaintiff’s
`
`patents in light of those grounds. See CyWee, 2019 WL 11023976, at *10; E-Watch, Inc. v. Lorex
`
`Can., Inc., No. H-12-3314, 2013 WL 5425298, at *2 (S.D. Tex. Sept. 26, 2013) (“At a minimum,
`
`even assuming that all the patents-in-suit survive the reexamination intact, the USPTO’s insight
`
`and expertise regarding the validity of the patents would be of invaluable assistance to this court.”).
`
`It is inevitable that the IPR rulings will thus focus the parties’ post-fact discovery efforts in this
`
`litigation. It would make no sense for experts (infringement, validity, and damages) to address in
`
`reports and at depositions, and for the Court to consider in dispositive motions or at trial, (a)
`
`asserted claims that may be declared invalid by the instituted IPRs, (b) invalidity grounds that may
`
`be estopped by a final written decision in the IPRs, and (c) arguments as to claim scope that likely
`
`will be impacted by the positions taken and decisions issued in the instituted IPRs.
`
`This Court has indicated that it will weigh (1) the scope of estoppel the movant is bound
`
`by and (2) the strength of the relevant IPR petitions in the context of the asserted claims. Lone Star
`
`4
`
`

`

`Case 6:22-cv-00031-ADA Document 127 Filed 08/18/23 Page 6 of 11
`
`SCM Systems, Ltd. v. Zebra Technologies Corporation, No. 6:21-cv-00842-ADA, 2023 WL
`
`4923962, at *3 (W.D. Tex. July 31, 2023). As noted, Google is the petitioner in each of the
`
`instituted IPRs, such that the estoppel provisions of 35 U.S.C. § 315(e)(2) apply to the only
`
`defendant in this action. As to the strength of the relevant IPR petitions, the PTAB is likely to find
`
`all asserted claims unpatentable.
`
`Indeed, in each institution decision, the PTAB determined that Google sufficiently
`
`demonstrated multiple claims of each Flyp patent are unpatentable, exceeding the statutory
`
`requirement of finding a single claim unpatentable to warrant institution. 35 U.S.C § 314 (“a
`
`reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims
`
`challenged in the petition.”); see also, e.g., Ex. 4 at 25 (Finding that “Petitioner has sufficiently
`
`demonstrated that the information presented in the Petition anticipates claim 1, and we institute on
`
`all challenges raised in the Petition. . . . Still, we. . . determine that Petitioner has sufficiently
`
`demonstrated, at this stage of the proceeding, that [the prior art] anticipates dependent claims 2
`
`and 4[.]”).
`
`The PTAB instituted an IPR proceeding against all asserted claims 1-4 of the ’585 patent
`
`on all four unpatentability grounds. Ex. 5 at 2, 6. For Ground 1, the PTAB determined that there
`
`is a reasonable likelihood that Google would prevail in establishing that claims 1, 2, and 4 are
`
`anticipated by the prior art, where the PTAB provided an element-by-element analysis, resolving
`
`all disputes in Google’s favor. Id. at 13-19 (finding that Google sufficiently showed the prior art
`
`anticipates claims 1, 2, and 4 and Flyp’s arguments are “unavailing”). As to Ground 2, the PTAB
`
`likewise determined that Google demonstrated a reasonable likelihood of prevailing on claim 3.
`
`Id. at 19-20. Additionally, the PTAB determined that Google demonstrated a reasonable likelihood
`
`of prevailing on claims 1-4 under Grounds 3-4. Id. at 20-21. The PTAB also instituted IPR
`
`5
`
`

`

`Case 6:22-cv-00031-ADA Document 127 Filed 08/18/23 Page 7 of 11
`
`proceedings against all asserted claims for each of the ’094, ’554, ’770, and ’105 patents, where
`
`the PTAB provided an element-by-element analysis, resolving essentially all disputes in Google’s
`
`favor. Ex. 3 at 2, 6, 14-24; Ex. 4 at 2, 6, 13-27; Ex. 1 at 2, 7, 15-32; Ex. 2 at 2, 5-6, 17-35.
`
`
`
`B. The stay will not unduly prejudice Plaintiff.
`
`Plaintiff will suffer no prejudice if a post-fact discovery stay is implemented and expert
`
`reports, dispositive motions, and trial are delayed until after the IPRs are complete. Because the
`
`stay would take effect after conclusion of fact discovery, there is no concern for staleness of
`
`evidence or for disruption or delay of the fact discovery process. Critically, “[a] stay will not
`
`diminish the monetary damages to which [plaintiff] will be entitled if it succeeds in its
`
`infringement suit—it only delays realization of those damages.” VirtualAgility Inc. v.
`
`Salesforce.com, Inc., 759 F.3d 1307, 1318 (Fed. Cir. 2014). A “mere delay in collecting . . .
`
`damages does not constitute undue prejudice.” Crossroads Sys., Inc. v. Dot Hill Sys. Corp., No.
`
`A-13-ca-800, 2015 WL 3773014, at *2 (W.D. Tex. June 16, 2015). Although Plaintiff is also
`
`seeking an injunction, Plaintiff has not sought a preliminary injunction to date. This undercuts any
`
`argument that a stay will prejudice Plaintiff. See VirtualAgility, 759 F.3d at 1319 (“VA’s
`
`arguments are rational reasons for not pursuing a preliminary injunction, but the fact that it was
`
`not worth the expense to ask for this remedy contradicts VA’s assertion that it needs injunctive
`
`relief as soon as possible.”)
`
`C. While the case is not in early stages, a stay would save the parties and Court
`significant resources.
`
`Although this case is not in its infancy, significant and burdensome milestones lie ahead.
`
`Expert discovery has yet to begin. Dkt. 112. Dispositive and Daubert motion deadlines are at the
`
`end of October. Id. The pretrial conference is set for January 26, 2024, and jury selection is
`
`scheduled for February 19, 2024. These events will impose “significant expenses on the parties
`
`6
`
`

`

`Case 6:22-cv-00031-ADA Document 127 Filed 08/18/23 Page 8 of 11
`
`that might be avoided if the stay results in the simplification (or obviation) of further court
`
`proceedings.” NFC Tech., 2015 WL 1069111, at * 3.
`
`The proximity to trial is not dispositive. For example, the Eastern District of Texas stayed
`
`a case pending IPR when the case was just two months away from trial. SSL Servs., LLC v. Cisco
`
`Sys., Inc, No. 2:15-CV-433-JRG-RSP, 2016 WL 3523871, at *3 (E.D. Tex. June 28, 2016).
`
`Although the case was at a late stage, it was “not yet on the eve of trial,” and the Court noted that
`
`“expert discovery is ongoing and the deadline to file dispositive motions and motions to strike has
`
`not yet passed.” Id. at *2. While noting the relatively advanced stage of the case, the EDTX Court
`
`nonetheless granted a stay because “there is a high likelihood of issue simplification.” Id. at *3.
`
`Here, as in SSL, expert discovery is not complete (in fact, it has not even begun), and the deadlines
`
`for dispositive motions, motions to strike, pre-trial submissions, and trial are upcoming. Also as in
`
`SSL, the issues are highly likely to be simplified by the instituted IPRs as to all asserted claims,
`
`which tips the scales in favor of a stay. Notably, this case is further from trial than was SSL when
`
`the stay was issued in that case (six months here versus two months in SSL).
`
`As yet another example, in CyWee, the Court stayed the case pending IPRs where “claim
`
`construction had been conducted and discovery was nearly complete. . . [h]owever, the most
`
`burdensome parts of the case—filing and responding to pretrial motions, preparing for trial, going
`
`through the trial process, and engaging in post-trial motions practice—all lie in the future.” See
`
`CyWee, 2019 WL 11023976 at *6-7 (listing cases where stays were granted mere weeks or months
`
`before trial). Here, even more “burdensome parts of the case” remain, as expert discovery has not
`
`even begun.
`
`Google has been diligent. Once the PTAB instituted the final IPR on August 2, 2023,
`
`Google acted quickly to meet and confer with opposing counsel about a potential stay and to
`
`7
`
`

`

`Case 6:22-cv-00031-ADA Document 127 Filed 08/18/23 Page 9 of 11
`
`prepare and file the present motion. Given the significant burdens and expenses of expert
`
`discovery, dispositive and Daubert motion practice, pre-trial practice and trial yet to be imposed
`
`on the parties and the Court, and in light of the fact that the instituted IPRs will very likely simplify
`
`the issues in this case, the requested stay should be granted.
`
`V. CONCLUSION
`
`For the foregoing reasons, Google respectfully requests that the case be stayed at the
`
`conclusion of fact discovery and until the IPRs and any resulting appeals are finally resolved.
`
`DATED: August 18, 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
`PAUL HASTINGS LLP
`4747 Executive Drive, 12th Floor
`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
`
`
`8
`
`

`

`Case 6:22-cv-00031-ADA Document 127 Filed 08/18/23 Page 10 of 11
`
`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
`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 18th day of August 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.
`
`
`
`/s/ Robert W. Unikel
`Robert W. Unikel
`
`
`
`9
`
`

`

`Case 6:22-cv-00031-ADA Document 127 Filed 08/18/23 Page 11 of 11
`
`
`
`CERTIFICATE OF CONFERENCE
`
`Pursuant to Local Rule CV-7(g), counsel for the parties to this motion conferred in a good-
`
`
`
`faith effort on August 14, 2023 to resolve the matter presented herein. Counsel for Plaintiff opposes
`
`the instant motion.
`
`
`
`/s/ Robert W. Unikel
`Robert W. Unikel
`
`
`
`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