Book a demo

Cut patent&paper research from weeks to hours with PatSnap Eureka AI!

Try now
Perrone Robotics v. Nissan Motor — Autonomous Vehicle Patent Suit | PatSnap
Explore in Eureka
Case ID1:25-cv-02181
FiledNov 2025
ClosedDec 2025
Patent Litigation

Perrone Robotics v. Nissan Motor: Five-Patent AV Suit Transferred in 6 Days

Perrone Robotics Innovations, LLC brought a five-patent infringement action against Nissan Motor Co., Ltd. in the Virginia Eastern District Court, targeting Nissan’s ProPILOT Assist system with claims spanning a general-purpose robotics OS and autonomous vehicle extensions. The case resolved procedurally in just six days — transferred intradistrict to the Richmond Division before substantive litigation could begin.

Resolution time
6days
6 days — resolved by intradistrict transfer before any merits ruling
Patents asserted
5
US11314251B2 and 4 further patents asserted — autonomous vehicle and robotics OS technology
Outcome
Case Transferred
Case reassigned intradistrict to Richmond Division (3:25cv982); litigation continues
Cost ruling
Not decided
No costs ruling — case transferred before any substantive hearing
Published by PatSnap Insights Team · Verified by PatSnap Eureka Data
Case overview

Five AV Patents, One ProPILOT Target, Six Days Before Transfer

On 25 November 2025, Perrone Robotics Innovations, LLC filed suit against Nissan Motor Co., Ltd. in the Virginia Eastern District Court, asserting five US patents: US11314251B2, US9833901B2, US9195233B2, US12181877B2, and US11782442B2. The asserted technology covers a general-purpose robotics operating system with unmanned and autonomous vehicle extensions, and the accused product is Nissan’s ProPILOT Assist driver-assistance system. Perrone was represented by Bunsow DeMory LLP.

Within six days of filing, on 1 December 2025, the court ordered an intradistrict transfer to the Eastern District of Virginia, Richmond Division, where the case continues under docket number 3:25cv982. A transfer rather than dismissal means the litigation survives fully intact — all claims, parties, and patents carry over to Richmond. No substantive rulings, claim construction orders, or cost decisions were issued in the originating docket.

The six-day turnaround is consistent with a routine divisional assignment or a judge-initiated venue correction within the same district, rather than a contested transfer motion. The public record does not reveal whether either party moved for transfer or whether it was sua sponte. For Perrone and Nissan alike, the substantive fight over ProPILOT Assist and the five robotics-OS patents now begins in earnest before the Richmond Division.

Case at a glance
Case no.1:25-cv-02181
CourtVirginia Eastern
JudgeN/A
FiledNovember 25, 2025
ClosedDecember 1, 2025
Duration6 days
OutcomeCase Transferred
Verdict causeInfringement Action
BasisCase Transferred
Prior Art Intelligence
See what prior art exists on this patent.
Eureka scans millions of patents and papers to surface prior art that may have invalidated these claims before costly litigation begins.
Check Prior Art
Case data sourced from PACER / Virginia Eastern District Court via PatSnap Eureka Litigation Intelligence Explore similar cases ↗
Case timeline

Filing to Case Transferred in 6 days

6 days — resolved by intradistrict transfer before any merits ruling

Case timeline: Complaint filed NOV 25 2025, NOV–DEC — 6 days total Horizontal timeline showing the three key events in Perrone Robotics Innovations, LLC v Nissan Motor Co., Ltd. from filing to resolution. Source: PACER, Virginia Eastern District Court. NOV 25 2025 Complaint filed Pre-trial proceedings DEC 1 2025 Case Transferred 6 DAYS TOTAL
Transfer terms

Intradistrict transfer: what moving to Richmond Division means

Legal mechanism

Intradistrict transfer keeps the case fully alive

An intradistrict transfer reassigns a case between divisions of the same federal district court — here from the general Eastern District of Virginia docket to the Richmond Division (3:25cv982). Unlike a dismissal, the transfer preserves every claim, patent, and party. No merits ruling was issued; the substantive infringement dispute over ProPILOT Assist and the five robotics-OS patents begins fresh before a Richmond judge.

No dismissal — litigation continues
Plaintiff outlook

Perrone’s claims survive — venue shift is procedural, not adverse

For Perrone Robotics, the intradistrict transfer is a neutral procedural step. All five patent assertions against Nissan’s ProPILOT Assist system remain intact. The Richmond Division of the Eastern District of Virginia is a well-established patent litigation venue, and Perrone retains full standing to pursue infringement claims, damages, and injunctive relief on the same factual record.

All five patents still asserted
Defendant outlook

Nissan faces the same five-patent exposure in Richmond

Nissan Motor Co., Ltd. has not obtained any substantive relief. The transfer does not limit, narrow, or resolve any of Perrone’s infringement allegations concerning ProPILOT Assist. Nissan must now engage on the merits in Richmond — including any invalidity defences, claim construction arguments, and non-infringement positions — across five asserted patents spanning autonomous vehicle and robotics operating system technology.

Merits defence begins in Richmond
Commercial implications

ProPILOT Assist at risk pending full Richmond adjudication

Nissan’s ProPILOT Assist is a commercially deployed ADAS feature across multiple vehicle lines. With five patents now active in Richmond, the case presents meaningful exposure for Nissan if any claims survive invalidity challenge. Suppliers and OEMs deploying similar robotics-OS-based autonomous vehicle extensions should monitor Richmond docket 3:25cv982 closely — the outcome could set licence or design-around precedent for the sector.

Monitor Richmond docket 3:25cv982
Legal analysis based on PACER docket records for case 1:25-cv-02181 and PatSnap Eureka litigation intelligence Search PatSnap Eureka ↗
Parties and representation

Full party and counsel information

RoleNameTypeDetail
PlaintiffPerrone Robotics Innovations, LLCCompanyAutonomous vehicle and robotics OS IP licensor — holder of US11314251B2 and four related patentsSearch in Eureka ↗
DefendantNissan Motor Co., Ltd.CompanyNissan Motor Co., Ltd. — global automotive OEM, maker of ProPILOT Assist ADAS systemSearch in Eureka ↗
Plaintiff counselTara Lynn Renee Zurawski.AttorneyCounsel for Perrone Robotics Innovations, LLCSearch in Eureka ↗
Plaintiff law firmBunsow DeMory LLPLaw FirmRepresenting Perrone Robotics Innovations, LLCSearch in Eureka ↗
Presiding judgeJudge N/AJudgeVirginia Eastern District CourtSearch in Eureka ↗
Official verdict

Official order — verbatim text

“Intradistrict Transfer to EasternDistrict ofVirginia, Richmond Division (3:25cv982).”
Source: PACER Docket, Case 1:25-cv-02181, Virginia Eastern District Court

The transfer order — ‘Intradistrict Transfer to Eastern District of Virginia, Richmond Division (3:25cv982)’ — is a purely procedural disposition. It carries no finding on infringement, validity, or claim scope across any of the five asserted patents. The Richmond docket inherits the case in full, and the substantive record is a blank slate. Practitioners should note that no claim construction, 12(b)(6) ruling, or scheduling order was entered before transfer, preserving maximum strategic flexibility for both Perrone and Nissan.

PACER case 1:25-cv-02181 · Public docket record Explore in Eureka ↗
Patent at issue

US11314251B2 and four further patents — autonomous vehicle robotics OS

Publication No.US11314251B2
Application No.US16/451491
Patent details
ProductAutonomous vehicle robotics operating system control and navigation
Cited in actionNovember 25, 2025

Publication No.US9833901B2
Application No.US14/949752
Patent details
ProductRobotics OS architecture for unmanned and autonomous vehicle platforms
Cited in actionNovember 25, 2025

Publication No.US9195233B2
Application No.US11/361974
Patent details
ProductGeneral-purpose autonomous vehicle software system — foundational methods
Cited in actionNovember 25, 2025

Publication No.US12181877B2
Application No.US18/236626
Patent details
ProductAutonomous vehicle operating system — next-generation extensions
Cited in actionNovember 25, 2025

Publication No.US11782442B2
Application No.US17/656505
Patent details
ProductRobotics operating system with advanced autonomous vehicle integration
Cited in actionNovember 25, 2025

The five asserted patents — US11314251B2, US9833901B2, US9195233B2, US12181877B2, and US11782442B2 — collectively cover a general-purpose robotics operating system with specific extensions for unmanned and autonomous vehicle applications. Application dates span from as early as US11/361974 (2006-era) through US18/236626 (filed 2023), indicating a portfolio architected to protect both foundational methods and more recent autonomous-vehicle-specific implementations across multiple patent generations.

This multi-generational portfolio structure presents significant competitive risk for automotive OEMs and Tier-1 ADAS suppliers. Nissan’s ProPILOT Assist — a commercially deployed Level 2 autonomy feature — is the named accused product, but the breadth of the Perrone claims suggests applicability to any system running autonomous vehicle logic on a generalised robotics OS framework. Companies developing or licensing similar architectures should assess whether their implementations fall within the literal or equivalents scope of any of the five patents now pending in Richmond.

Patent data sourced from USPTO via PatSnap Eureka patent database Search patent records in Eureka ↗
Freedom to operate

Should you run an FTO against the Perrone Robotics AV patent portfolio?

Any OEM, Tier-1 supplier, or AV software vendor deploying a robotics operating system with autonomous or unmanned vehicle functionality should treat this five-patent assertion against ProPILOT Assist as a direct signal. The Perrone portfolio spans nearly two decades of application priority, meaning products built on both legacy and current AV software stacks may carry exposure. An FTO analysis scoped to US11314251B2, US9833901B2, US9195233B2, US12181877B2, and US11782442B2 is advisable before any new product launch or licensing negotiation.

PatSnap Eureka’s FTO Search Agent can map your autonomous vehicle software architecture against the full claim scope of all five Perrone patents simultaneously, flagging overlapping independent and dependent claims, identifying relevant prior art that could support invalidity arguments, and surfacing design-around options before Richmond reaches claim construction. With Markman proceedings still ahead, there is a narrow window to position strategically — either through prior art submission, IPR petitioning, or design modification.

PatSnap Eureka FTO Search

Run a freedom-to-operate analysis on US11314251B2 to assess your product’s exposure

Run FTO in Eureka →
Related litigation

Similar autonomous vehicle and robotics OS patent cases in E.D. Virginia

Explore comparable multi-patent infringement actions targeting ADAS and autonomous vehicle software systems filed in the Eastern District of Virginia.

🔍
Access 40+ similar cases in PatSnap Eureka
Perrone Robotics Innovations, LLC patent enforcement history, Virginia Eastern case history, Perrone Robotics Innovations, LLC’s full IP portfolio, and comparable case analysis
AV patent cases vs OEMsRobotics OS litigation historyE.D. Virginia ADAS filingsProPILOT Assist prior art
Unlock similar cases in Eureka →
Strategic implications

What this transfer signals for the autonomous vehicle IP landscape

A six-day intradistrict transfer is rarely the story — the five-patent robotics-OS assertion against a major OEM is.

Broad robotics-OS patent portfolios are becoming OEM litigation tools

Perrone’s five-patent stack spans application dates from 2006 (US9195233B2 via app US11/361974) to 2023 (US12181877B2 via app US18/236626), suggesting a deliberately layered portfolio built to cover multiple generations of autonomous vehicle software architecture. OEMs fielding ADAS products should audit exposure across the full claim landscape, not just the most recent filings.

ProPILOT Assist is now a named accused product — design-around risk is live

With ProPILOT Assist explicitly named across five patents, Nissan’s engineering and legal teams face concurrent invalidity and design-around analyses. Other OEMs offering comparable Level 2 autonomy features on similar software architectures should treat this filing as a signal to review their own freedom-to-operate positions against the Perrone portfolio before the Richmond case produces claim constructions.

🔒
Full strategic analysis in PatSnap Eureka
Unlock claim construction forecasts, licensing risk scoring, and OEM exposure analysis for this E.D. Virginia autonomous vehicle patent dispute.
Richmond judge assignmentLicensing strategy signalsOEM design-around cost
Unlock full analysis →
Analysis powered by PatSnap Eureka Litigation Intelligence Explore in Eureka ↗
Frequently asked questions

Perrone v Nissan — key questions answered

Still have questions? PatSnap Eureka can answer them instantly from patent and litigation data. Ask Eureka ↗
PatSnap Eureka

Stay ahead of Perrone v. Nissan as Richmond proceedings begin

With five robotics-OS patents now active in the Richmond Division, claim construction and IPR filings could reshape the autonomous vehicle IP landscape. Run an FTO or set up docket monitoring in PatSnap Eureka before key pre-trial orders are entered.

Ask anything about this case.
PatSnap Eureka searches patents and litigation data to answer instantly.
Powered by PatSnap Eureka
Link copied to clipboard

Related Litigation Cases

Help us improve this page

Found incorrect or outdated information? Let us know and we'll get it fixed.