Escapex Ip, LLC v. Google LLC

CourtCourt of Appeals for the Federal Circuit
DecidedNovember 25, 2025
Docket24-1201
StatusPublished

This text of Escapex Ip, LLC v. Google LLC (Escapex Ip, LLC v. Google LLC) is published on Counsel Stack Legal Research, covering Court of Appeals for the Federal Circuit primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Escapex Ip, LLC v. Google LLC, (Fed. Cir. 2025).

Opinion

Case: 24-1201 Document: 43 Page: 1 Filed: 11/25/2025

United States Court of Appeals for the Federal Circuit ______________________

ESCAPEX IP, LLC, Plaintiff-Appellant

v.

GOOGLE LLC, Defendant-Appellee ______________________

2024-1201 ______________________

Appeal from the United States District Court for the Northern District of California in No. 3:22-cv-08711-VC, Judge Vince Chhabria. ______________________

Decided: November 25, 2025 ______________________

WILLIAM PETERSON RAMEY, III, Ramey LLP, Houston, TX, argued for plaintiff-appellant.

JONATHAN IRVIN TIETZ, Perkins Coie LLP, Washington, DC, argued for defendant-appellee. Also represented by DAN L. BAGATELL, Hanover, NH. ______________________

Before TARANTO, STOLL, and STARK, Circuit Judges. STARK, Circuit Judge. Case: 24-1201 Document: 43 Page: 2 Filed: 11/25/2025

EscapeX IP, LLC (“EscapeX”) appeals an award to Google LLC (“Google”) of attorneys’ fees as well as the de- nial of EscapeX’s motion to amend a judgment. We affirm. I EscapeX sued Google in the United States District Court for the Western District of Texas, asserting that Google’s YouTube Music product infringed U.S. Patent No. 9,009,113 (“System and Method for Generating Artist- Specified Dynamic Albums”) (the “’113 patent”). Google in- itially responded to the suit by sending a letter to EscapeX, stating, among other things, that EscapeX could not have conducted an adequate pre-suit investigation, since the features accused of infringing the ’113 patent were not pre- sent in the accused YouTube Music product. EscapeX then filed an amended complaint in which it changed the ac- cused product to YouTube Video with Auto-Add. Google responded in several subsequent letters, stating that inter- net searches would have revealed that this accused product existed before the priority date of the ’113 patent – mean- ing that if it infringed the ’113 patent then it also antici- pated and invalidated it. EscapeX did not to respond to Google’s request that EscapeX voluntarily dismiss the law- suit. In other correspondence, Google informed EscapeX that Google planned to file a motion to transfer the action to the Northern District of California and again requested confirmation that EscapeX would dismiss the case. Again EscapeX did not respond. Google then filed its transfer mo- tion and supporting brief. When EscapeX failed to file a response, Google notified the court, which then noted Es- capeX’s “troublesome” and “repeated failure to file in a timely manner.” J.A. 134-36. The court also granted Google’s motion and transferred the case. Shortly thereafter, in a separate case in which EscapeX was asserting the same ’113 patent, a judge in the South- ern District of New York found all claims of the ’113 patent Case: 24-1201 Document: 43 Page: 3 Filed: 11/25/2025

ESCAPEX IP, LLC v. GOOGLE LLC 3

to be directed to subject matter not eligible for a patent un- der 35 U.S.C. § 101. See EscapeX IP LLC v. Block, Inc., 652 F. Supp. 3d 396, 408 (S.D.N.Y. 2023). EscapeX did not ap- peal this ruling. After Google again asked EscapeX to dis- miss its suit, EscapeX filed what purported to be a “joint stipulation of dismissal,” which represented that the par- ties “jointly stipulate to the dismissal of this action” and “further jointly stipulate and agree that each party shall bear its own costs, expenses, and attorneys’ fees.” J.A. 137- 38. EscapeX’s attorney attested in the stipulation that “concurrence in the filing of this document has been ob- tained from [Google’s] counsel.” J.A. 139. In fact, however, as EscapeX later acknowledged, EscapeX had not shared the stipulation with Google before its filing, had not ob- tained Google’s consent to file it, and mistakenly repre- sented to the court that Google had agreed to bear its own attorneys’ fees. See J.A. 438 ¶¶ 5-6. Google demanded that EscapeX “immediately withdraw this stipulation[] and no- tify the Court that it was filed without Google’s permis- sion.” J.A. 267. EscapeX withdrew the stipulation of dismissal that same day. J.A. 141-42. Several days later, with Google’s consent, EscapeX filed a second “joint stipu- lation of dismissal,” which made no representation that the parties had agreed to bear their own fees. J.A. 143-44. Google then moved for attorneys’ fees under 35 U.S.C. § 285, arguing EscapeX had advanced frivolous claims and unreasonably prolonged the litigation. EscapeX did not contest the facts alleged by Google; rather, EscapeX argued that Google was not a prevailing party 1 and that the case was not exceptional. Following oral argument, the district court granted Google’s motion and ordered EscapeX to pay $191,302.18 to Google for attorneys’ fees and costs it had incurred in the course of this case.

1 EscapeX no longer challenges the district court’s determination that Google was the prevailing party. Case: 24-1201 Document: 43 Page: 4 Filed: 11/25/2025

EscapeX subsequently moved, pursuant to Federal Rule of Civil Procedure 59(e), to amend the judgment, “based on newly discovered evidence” EscapeX asserted had been unavailable at the time of the district court’s or- der granting attorneys’ fees. J.A. 505. The “new evidence” consisted of two short declarations: one from EscapeX’s president and the other from an engineer who had per- formed EscapeX’s pre-suit investigation and prepared the claim charts that were attached to its amended complaint. J.A. 505-16. These declarations, according to EscapeX, showed that “meticulous steps were undertaken” prior to filing suit. J.A. 505. Google sought to meet and confer with EscapeX before going to the expense of briefing its response to EscapeX’s Rule 59(e) motion, which Google viewed as frivolous and had asked EscapeX to withdraw. Despite several follow- ups, EscapeX did not respond until weeks later, by which time Google had already had to file its response to the mo- tion. J.A. 571-72. In that response, Google argued that the declarations violated a court order (that had rejected Es- capeX’s request for leave to file a declaration in opposition to Google’s motion for attorneys’ fees) and, in any event, they did not comprise “newly discovered evidence.” J.A. 526-33. The district court agreed. Finding that EscapeX “wholly failed to meet the Rule 59(e) standard for amend- ing a judgment,” it denied the motion. J.A. 3. Google then moved under 28 U.S.C. § 1927, 35 U.S.C. § 285, and the court’s inherent powers to recover the fees and costs it incurred in opposing EscapeX’s Rule 59(e) mo- tion. Google argued that EscapeX’s motion was frivolous and increased litigation costs, and further that EscapeX’s counsel had acted recklessly or in bad faith. In opposition, EscapeX suggested that the basis for its motion had been to eliminate the “manifest injustice” of the court’s attor- neys’ fees award. At a hearing on Google’s motion, the dis- trict court made clear that it believed EscapeX’s Rule 59(e) motion had been frivolous. It granted Google’s motion, Case: 24-1201 Document: 43 Page: 5 Filed: 11/25/2025

ESCAPEX IP, LLC v. GOOGLE LLC 5

awarding an additional $63,525.30 in attorneys’ fees and costs, and held that EscapeX and its attorneys were jointly and severally liable for this amount. EscapeX timely appealed. The district court had juris- diction under 28 U.S.C.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

In Re Girardi
611 F.3d 1027 (Ninth Circuit, 2010)
Smithkline Beecham Corp. v. Apotex [Corrected Date]
439 F.3d 1312 (Federal Circuit, 2006)
Julien v. Zeringue
864 F.2d 1572 (Federal Circuit, 1989)
Zimmerman v. City Of Oakland
255 F.3d 734 (Ninth Circuit, 2001)
Highmark Inc. v. Allcare Health Management System, Inc.
134 S. Ct. 1744 (Supreme Court, 2014)
Sfa Systems, LLC v. Newegg Inc.
793 F.3d 1344 (Federal Circuit, 2015)
Lumen View Technology LLC v. Findthebest.com, Inc.
811 F.3d 479 (Federal Circuit, 2016)
Bayer Cropscience Ag v. Dow Agrosciences LLC
851 F.3d 1302 (Federal Circuit, 2017)
Coda Dev. S.R.O. v. Goodyear Tire & Rubber Co.
916 F.3d 1350 (Federal Circuit, 2019)
Thermolife International LLC v. Gnc Corporation
922 F.3d 1347 (Federal Circuit, 2019)
Blackbird Tech LLC v. Health in Motion LLC
944 F.3d 910 (Federal Circuit, 2019)
Jody Kaufmann v. Kilolo Kijakazi
32 F.4th 843 (Ninth Circuit, 2022)
Sekri, Inc. v. United States
34 F.4th 1063 (Federal Circuit, 2022)
Trulis v. Barton
107 F.3d 685 (Ninth Circuit, 1995)
Octane Fitness, LLC v. Icon Health
134 S. Ct. 1749 (Supreme Court, 2014)

Cite This Page — Counsel Stack

Bluebook (online)
Escapex Ip, LLC v. Google LLC, Counsel Stack Legal Research, https://law.counselstack.com/opinion/escapex-ip-llc-v-google-llc-cafc-2025.