Updated on Dec. 10, 2025 | Written by Patsnap Team
A patent infringement suit against Toyota Motor, Corp. was dismissed with prejudice after the sole asserted claim was invalidated on appeal. The U.S. District Court for the Eastern District of Texas closed the case in April 2025, following a Federal Circuit mandate that found claim 8 of U.S. Patent No. 8,265,096 (‘096 Patent) obvious. Brought by the University of New Mexico’s technology transfer arm, UNM Rainforest Innovations, the lawsuit alleged that a wide range of Toyota and Lexus hybrid vehicles infringed. This automotive patent infringement case analysis highlights the risks of single-claim litigation and the power of appellate invalidity defenses.

| Field | Details |
|---|---|
| Case Name | UNM Rainforest Innovations v. Toyota Motor, Corp. et al. |
| Case Number | 2:23-cv-00424 |
| Court | U.S. District Court for the Eastern District of Texas |
| Filing/Closure | Filed Sept. 18, 2023 – Closed April 3, 2025 (563 days) |
| Outcome | Dismissed with prejudice. Each side bears its own costs. |
| Patents | U.S. Patent No. 8,265,096 (“Control apparatus for hybrid vehicle”) |
| Products | Toyota & Lexus hybrid, plug-in hybrid, and electric models (2017-2024 model years), including the Tundra Hybrid, RAV4 Prime, Prius, and Highlander Hybrid. |
| Plaintiff Counsel | Parker Bunt & Ainsworth PC; The Shore Firm LLP; Offor Evans PLLC. (Agents: Ainsworth, Offor, Evans, Shore, Bunt, Della Porta) |
| Defendant Counsel | Findlay Craft PC; Orrick, Herrington & Sutcliffe LLP. (Agents: Findlay, Craft, Routh) |
| Termination Basis | Dismissed with prejudice after Federal Circuit invalidated the sole asserted claim (Claim 8) as obvious. |
The plaintiff, UNM Rainforest Innovations, manages the University of New Mexico’s intellectual property. The defendants were Toyota Motor, Corp., Toyota Motor Sales USA, Inc., and Toyota Motor Engineering & Manufacturing North America, Inc.
The case rested on Claim 8 of U.S. Patent No. 8,265,096, relating to hybrid vehicle motor control. Asserting only one dependent claim was a strategic choice that created a single point of failure. To build a more resilient litigation position, parties often research patent families for broader claim support.
💡 Key Insight: A single-claim assertion strategy simplifies litigation but poses a high risk. Invalidation of that claim terminates the entire case. A robust portfolio with multiple claims is strategically safer.
The case was filed on September 18, 2023, in the Eastern District of Texas, a court with deep expertise in patent matters, before Chief Judge Rodney Gilstrap. The pivotal event was the Federal Circuit’s mandate on October 29, 2024, invalidating Claim 8. The district court then dismissed the case sua sponte on April 3, 2025, after 563 days.
Judge Gilstrap dismissed the case with prejudice after the Federal Circuit's ruling. The order stated that with Claim 8 invalidated, “no live issues remain before the Court.” All pending motions were denied as moot.
The core of the dismissal was the Federal Circuit's finding that Claim 8 was invalid for obviousness under 35 U.S.C. § 103. This underscores how a successful patent validity challenge in a parallel appellate proceeding can decisively end district court litigation.
For the automotive industry, this result demonstrates that broad patent assertions can be defeated on validity grounds. For university tech transfer offices, it emphasizes the need for robust, well-prosecuted patents and cautious litigation strategy.
The ruling reinforces the Federal Circuit’s central role as the final arbiter of patent validity. For companies, proactive monitoring of such rulings is a key component of IP risk management. To stay ahead, professionals can track litigation trends with Patsnap Eureka IP.
Disclaimer: This article is for informational purposes only and does not constitute legal advice. You should consult with qualified legal counsel for any specific legal matters concerning patent litigation or intellectual property strategy.
Help us improve
Something wrong, out of date, or missing on this page? Tell us and it goes straight to the team that maintains it.
This page