Fleet Connect Solutions v. Rivian Automotive: 7-Patent Fleet Telematics Dispute Dismissed With Prejudice
Fleet Connect Solutions, LLC asserted seven patents covering fleet telematics and wireless vehicle communication against Rivian Automotive’s R1T, R1S, RCV, and EDV vehicles and associated software stack. Filed in the Western District of Texas before Judge Alan Albright, the case closed after 453 days via a joint stipulation of dismissal with prejudice — extinguishing Fleet Connect’s claims permanently.
Seven Telematics Patents, One EV Fleet Stack, One Permanent Dismissal
Fleet Connect Solutions, LLC filed suit against Rivian Automotive, Inc. on 23 August 2023 in the Western District of Texas (Case No. 6:23-cv-00623), asserting infringement of seven U.S. patents covering fleet telematics, wireless vehicle communication, and connected fleet management. The accused products spanned Rivian’s full commercial and consumer electric vehicle lineup — the R1T pickup, R1S SUV, RCV commercial van, and EDV delivery vehicle — along with Fleet OS, the Rivian Vehicle Care System, Driver+, Rivian Cloud, and Rivian’s mobile applications.
The case closed on 18 November 2024 via a joint stipulation of dismissal filed under Federal Rule of Civil Procedure 41(a)(1)(A)(ii). Critically, Fleet Connect dismissed all of its claims with prejudice, meaning those specific claims against Rivian on these patents cannot be re-filed. Rivian had filed no counterclaims, so no cross-claims survived the dismissal. The with-prejudice designation is a meaningful legal boundary for Fleet Connect’s enforcement posture on these seven patents against this defendant.
The 453-day duration — spanning from filing through dismissal — suggests the parties engaged in substantive litigation activity before reaching resolution, consistent with a negotiated outcome rather than an early procedural exit. The public record does not disclose whether a financial settlement accompanied the dismissal. The absence of counterclaims from Rivian, combined with a bilateral stipulation, typically signals a negotiated resolution, though that cannot be confirmed from publicly available documents alone.
Filing to Dismissed with Prejudice in 453 days
453 days — above the W.D. Texas median for patent cases resolved without trial
Dismissed with prejudice: what the Rule 41 stipulation means for both parties
Rule 41(a)(1)(A)(ii): joint stipulation, not a court order
A dismissal under FRCP 41(a)(1)(A)(ii) requires the written consent of all parties and takes effect without a court order. Because Fleet Connect dismissed with prejudice, the dismissal operates as a final adjudication on the merits for res judicata purposes — Fleet Connect is barred from asserting these same claims against Rivian in a future action. Rivian’s lack of counterclaims means no cross-claims survived.
Final — no re-filing against RivianWith-prejudice dismissal forecloses re-filing against Rivian
Fleet Connect’s agreement to dismiss with prejudice extinguishes its ability to reassert these seven patents against Rivian for the same accused products and conduct. This is a materially stronger outcome for Rivian than a without-prejudice dismissal. Fleet Connect retains ownership of the patents and may still enforce them against other parties, but its litigation path against Rivian on these specific claims is permanently closed.
Claims permanently extinguishedRivian secures permanent closure on all seven asserted patents
Rivian obtains the strongest available dismissal outcome short of a full invalidity judgment. The with-prejudice designation provides Rivian with res judicata protection against Fleet Connect on these patents and these accused products. Having filed no counterclaims, Rivian also avoided any risk of an adverse ruling on invalidity or non-infringement — which may have been a deliberate strategic choice.
Res judicata protection securedSeven fleet telematics patents remain active and enforceable against others
The dismissal resolves only Fleet Connect’s claims against Rivian. All seven asserted patents remain in force and could be asserted against other EV manufacturers, fleet software providers, or telematics platform operators. Companies deploying connected vehicle systems, fleet OS platforms, or OTA-enabled commercial EV fleets should assess their exposure to this patent portfolio, which spans wireless communication, fleet management, and vehicle data protocols.
Portfolio still active — broader industry riskFull party and counsel information
| Role | Name | Type | Detail |
|---|---|---|---|
| Plaintiff | Fleet Connect Solutions, LLC | Company | Fleet telematics patent licensing entity — holder of US7058040B2 and 6 related patentsSearch in Eureka ↗ |
| Defendant | Rivian Automotive, Inc. | Company | Rivian Automotive, Inc. — electric vehicle manufacturer, R1T/R1S/RCV/EDV platformSearch in Eureka ↗ |
| Plaintiff counsel | C. Matthew Rozier | Attorney | Counsel for Fleet Connect Solutions, LLCSearch in Eureka ↗ |
| Plaintiff counsel | James F. McDonough | Attorney | Counsel for Fleet Connect Solutions, LLCSearch in Eureka ↗ |
| Plaintiff counsel | Jonathan L. Hardt | Attorney | Counsel for Fleet Connect Solutions, LLCSearch in Eureka ↗ |
| Plaintiff counsel | Jonathan R. Miller | Attorney | Counsel for Fleet Connect Solutions, LLCSearch in Eureka ↗ |
| Plaintiff counsel | Robert Daniel Garza | Attorney | Counsel for Fleet Connect Solutions, LLCSearch in Eureka ↗ |
| Plaintiff counsel | Travis E. Lynch | Attorney | Counsel for Fleet Connect Solutions, LLCSearch in Eureka ↗ |
| Plaintiff law firm | Rozier Hardt McDonough PLLC | Law Firm | Representing Fleet Connect Solutions, LLCSearch in Eureka ↗ |
| Defendant counsel | Andrew T. Jones | Attorney | Counsel for Rivian Automotive, Inc.Search in Eureka ↗ |
| Defendant counsel | Bethany D. Bengfort | Attorney | Counsel for Rivian Automotive, Inc.Search in Eureka ↗ |
| Defendant counsel | Brian Christopher Nash | Attorney | Counsel for Rivian Automotive, Inc.Search in Eureka ↗ |
| Defendant counsel | Ian A. Bennett | Attorney | Counsel for Rivian Automotive, Inc.Search in Eureka ↗ |
| Defendant counsel | Timothy C. Saulsbury | Attorney | Counsel for Rivian Automotive, Inc.Search in Eureka ↗ |
| Defendant law firm | Morrison & Foerster, LLP | Law Firm | Representing Rivian Automotive, Inc.Search in Eureka ↗ |
| Presiding judge | Judge Alan D Albright | Judge | Texas Western District CourtSearch in Eureka ↗ |
Official order — verbatim text
The stipulation language is precise: Fleet Connect dismisses ‘all of its claims in this action with prejudice’ under Rule 41(a)(1)(A)(ii), and the filing explicitly notes Rivian filed no counterclaims. The with-prejudice designation carries res judicata effect, barring any future action by Fleet Connect against Rivian on these claims. The joint nature of the filing — both parties acting through counsel — suggests a negotiated endpoint, though the public record is silent on any accompanying financial or licensing terms.
US7058040B2 and Six Further Patents — Fleet Telematics & Wireless Vehicle Communication
The seven asserted patents — US7058040B2, US8494581B2, US7206837B2, US7656845B2, US6941223B2, US7742388B2, and US7260153B2 — originate from application filings spanning 2001 to 2005, placing them squarely in the foundational era of commercial fleet telematics. The portfolio covers wireless vehicle communication protocols, fleet data management architectures, vehicle location and tracking systems, and methods for transmitting operational data between vehicles and fleet management platforms. These are not narrow continuation patents — they represent broad foundational claims in the connected vehicle communications space.
For the EV industry, the strategic significance of this portfolio lies in the convergence of legacy telematics IP with modern fleet software stacks. Systems like Rivian’s Fleet OS, Driver+, and Rivian Cloud perform the precise functions — wireless data exchange, real-time vehicle monitoring, fleet scheduling, and mobile app integration — that these patents were originally written to cover. Any OEM or fleet software provider deploying a connected vehicle platform with cloud-based management and mobile access should treat this portfolio as a live enforcement risk, particularly given the plaintiff’s demonstrated willingness to litigate at scale in a pro-patentee venue.
Should you run an FTO against US7058040B2 and the Fleet Connect telematics portfolio?
If your organisation develops or deploys fleet management software, connected vehicle platforms, OTA-enabled commercial EVs, or vehicle-cloud communication systems, this seven-patent portfolio warrants a structured freedom-to-operate assessment. The application dates (2001–2005) mean many claims may be approaching or past expiry, but issued patents remain enforceable until their expiration date, and continuation claims can extend effective protection. R&D and product teams building Fleet OS-type architectures, driver assistance integrations, or mobile fleet apps should not assume prior art availability without a formal claim-level analysis.
PatSnap Eureka’s FTO Search Agent enables product and IP teams to run structured claim mapping against this portfolio in hours rather than weeks. Upload your technical specification, and Eureka maps each independent claim against your product’s architecture — flagging high-risk overlaps and identifying prior art that may support design-around strategies. For teams monitoring Fleet Connect’s enforcement activity across the EV sector, Eureka’s litigation monitoring tools provide real-time alerts on new filings citing these patent numbers.
Run a freedom-to-operate analysis on US7058040B2 to assess your product’s exposure
Run FTO in Eureka →Similar Fleet Telematics & Connected Vehicle Patent Cases in W.D. Texas
Cases involving fleet telematics, wireless vehicle communication, and connected fleet management patents litigated in the Western District of Texas before Judge Albright.
What this case signals for the connected EV fleet IP landscape
A seven-patent telematics dispute against a major EV OEM, resolved with prejudice in under 15 months, carries meaningful signals for fleet tech IP strategy.
W.D. Texas remains a high-stakes venue for EV and fleet telematics cases
Judge Albright’s docket continues to attract patent plaintiffs asserting connected vehicle and telematics IP. The 453-day lifecycle here is consistent with W.D. Texas cases that progress through claim construction before settling. EV OEMs with fleet software stacks should treat this venue as a live enforcement risk and ensure their IP counsel monitors filings proactively.
Fleet OS and cloud-connected vehicle platforms are a growing assertion target
The accused products here — Fleet OS, Rivian Cloud, Driver+, and mobile apps — represent the full connected vehicle software stack. Patent holders are increasingly targeting this layer rather than hardware alone. R&D teams building fleet management, OTA update, or vehicle-cloud communication systems should prioritise FTO analysis against pre-2010 telematics patent families, where much of this portfolio originates.
Fleet v Rivian — key questions answered
The case was dismissed with prejudice on 18 November 2024 via a joint stipulation under FRCP 41(a)(1)(A)(ii). Fleet Connect dismissed all claims against Rivian with prejudice, meaning those claims cannot be re-filed. Rivian had filed no counterclaims. The case ran for 453 days from filing.
Fleet Connect asserted seven patents: US7058040B2, US8494581B2, US7206837B2, US7656845B2, US6941223B2, US7742388B2, and US7260153B2. These cover fleet telematics, wireless vehicle communication, and fleet data management systems, with application dates ranging from approximately 2001 to 2005.
The accused products included Rivian’s R1T, R1S, RCV, and EDV vehicles (including all predecessor and successor models), along with Fleet OS, the Rivian Vehicle Care System, Driver+, Rivian Cloud, and Rivian’s mobile applications — effectively Rivian’s full connected vehicle hardware and software stack.
A dismissal with prejudice operates as a final adjudication on the merits for res judicata purposes. Fleet Connect is permanently barred from asserting these same claims against Rivian for the same accused products and conduct. Fleet Connect retains ownership of the patents and may still enforce them against third parties, but its litigation path against Rivian on these specific claims is closed.
The dismissal binds only Fleet Connect and Rivian. All seven asserted patents remain in force and could be asserted against other EV manufacturers, commercial fleet operators, or fleet software platform providers. Companies deploying connected vehicle systems with cloud management and mobile integration should assess their FTO position against this portfolio, particularly given Fleet Connect’s demonstrated enforcement activity.
PatSnap Eureka searches patents and litigation data to answer instantly.