Perrone Robotics Inc v. Nissan North America Inc

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Perrone Robotics, Inc. and Perrone Robotics Innovations, LLC (Delaware / Virginia)
  • Defendant: Nissan North America, Inc. (Delaware / Tennessee) and Nissan Motor Co., Ltd. (Japan)
  • Plaintiff's Counsel: Bunsow De Mory LLP
• Case Identification: 3:25-cv-00982, E.D. Va., 11/25/2025
• Venue Allegations: Plaintiff alleges venue is proper in the Eastern District of Virginia because Defendants have regular and established places of business in the District, including a training center in Sterling, Virginia, and offer the accused vehicles for sale at numerous dealerships within the District, thereby committing acts of infringement in the jurisdiction.
• Core Dispute: Plaintiff alleges that Defendants' vehicles equipped with the ProPILOT Assist Advanced Driver-Assistance System (ADAS) infringe five U.S. patents related to a general purpose robotics operating system.
• Technical Context: The technology concerns a hardware-independent software framework for controlling autonomous and robotic systems, a foundational component in the rapidly growing market for ADAS in consumer and commercial vehicles.
• Key Procedural History: The complaint notes Plaintiff's participation in the 2005 DARPA Grand Challenge, which it alleges reinforced the need for a reusable, general-purpose robotics operating system, contrasting with the vehicle-specific hardware and software used by other participants. No prior litigation or post-grant proceedings are mentioned.

Case Timeline

II. Technology and Patent(s)-in-Suit Analysis

U.S. Patent No. 12,181,877 - "General Purpose Robotics Operating System with Unmanned and Autonomous Vehicle Extensions"

• Patent Identification: U.S. Patent No. 12,181,877, issued December 31, 2024 Compl. ¶11

The Invention Explained

• Problem Addressed: The complaint asserts that prior to the invention, creating a new robot or automated device required starting from scratch, developing specific hardware and software for each unique application Compl. ¶17 This "rigid, vertically integrated" approach was inefficient, created barriers to interoperability, and prevented widespread, scalable deployment of robotic systems Compl. ¶21
• The Patented Solution: The invention is a "general purpose robotics operating system" (GPROS) that provides a standardized, hardware-independent software platform Compl. ¶¶18, 25 It uses a novel layer of generic abstractions and configurable application services, allowing developers to build complex robotics applications that can be deployed across different hardware platforms (e.g., different vehicles, sensors, and actuators) without rewriting core logic Compl. ¶¶21, 28 For example, the related '251 Patent describes this as a "standardized, full service platform upon which the various and widely divergent robotics and automation applications may sit" '251 Patent, col. 1:63-66
• Technical Importance: The complaint alleges that the GPROS architecture was a "significant technological advancement" that solved the long-standing problem of hardware heterogeneity in robotics, enabling the scalable deployment of automated vehicle fleets Compl. ¶¶21, 23

Key Claims at a Glance

• The complaint asserts at least independent claim 1 Compl. ¶41
• The essential elements of independent claim 1 include:
  • A vehicle comprising: a steering mechanism, a brake, and a throttle;
  • An operating system with a set of application services for managing an obstacle service and using a movement plan;
  • The application services are independent of an underlying hardware platform and configurable for communication and operational tasks;
  • The application services are configurable via a configuration service, adaptable both statically and dynamically, and access data using a generic abstraction;
  • A graphical user interface;
  • The vehicle is adapted to receive configuration data over a network; and
  • The vehicle is adapted to avoid obstacles.
• The complaint also asserts dependent claims 2-6, 8, 10-21 Compl. ¶40

U.S. Patent No. 11,782,442 - "General Purpose Robotics Operating System with Unmanned and Autonomous Vehicle Extensions"

• Patent Identification: U.S. Patent No. 11,782,442, issued October 10, 2023 Compl. ¶12

The Invention Explained

• Problem Addressed: As with the '877 Patent, this patent addresses the inefficiency of creating custom, hardware-specific software for each new robotic or automated device, which inhibited scalability and interoperability Compl. ¶17 Compl. ¶21
• The Patented Solution: The patent describes a GPROS that provides a hardware-independent abstraction layer to manage services and coordinate tasks across different hardware platforms Compl. ¶25 A core inventive concept is a thread management system for coordinating synchronous, asynchronous, and real-time tasks like sensor processing, decision-making, and actuator control, which is crucial for real-time vehicle operation Compl. ¶25
• Technical Importance: The complaint alleges the patented technology was a "non-conventional" solution that enabled hardware independence while maintaining the tight timing requirements for real-time vehicle control, a problem previously solved with non-portable, hardware-specific code Compl. ¶21 Compl. ¶26

Key Claims at a Glance

• The complaint asserts at least independent claim 8 Compl. ¶61
• The essential elements of independent claim 8 include:
  • An autonomous vehicle comprising a steering mechanism, a brake, and a throttle;
  • A general purpose robotics operating system with application services to manage synchronous, asynchronous, or real time application threads;
  • The application services are independent of an underlying hardware platform and configurable for communication and operational tasks;
  • A steering servomechanism to control the steering mechanism based on a movement plan;
  • A brake servomechanism to control the brake based on the movement plan; and
  • A throttle servomechanism to control the throttle based on the movement plan.
• The complaint also asserts claims 1-4, 6, 7, 9, 11-13, 15, and 17-20 Compl. ¶60

U.S. Patent No. 11,314,251 - "General Purpose Robotics Operating System with Unmanned and Autonomous Vehicle Extensions"

• Patent Identification: U.S. Patent No. 11,314,251, issued April 26, 2022 Compl. ¶13
• Technology Synopsis: This patent, part of the same family, is also directed to a GPROS for autonomous vehicles. It describes a system with configurable application services that are independent of the underlying hardware, can be adapted statically and dynamically, and can access configuration data through a generic abstraction, enabling deployment across various platforms Compl. ¶¶78, 80
• Asserted Claims: Claims 1-8, 10-19 Compl. ¶79 The complaint details infringement allegations for independent claim 2 Compl. ¶80
• Accused Features: The accused features include the overall ProPILOT Assist system, its use of a GPROS, its hardware independence across different vehicle models, its configurable ADAS settings, and its use of servomechanisms for steering, braking, and throttle control based on a movement plan Compl. ¶¶84-88

U.S. Patent No. 9,833,901 - "General Purpose Robotics Operating System with Unmanned and Autonomous Vehicle Extensions"

• Patent Identification: U.S. Patent No. 9,833,901, issued December 5, 2017 Compl. ¶14
• Technology Synopsis: This patent claims a method for using a GPROS. The method involves managing application threads, managing autonomous vehicle and movement planning services, and using application services that are configurable, adaptable, and hardware-independent Compl. ¶¶99, 101
• Asserted Claims: All claims (1-20) Compl. ¶100 The complaint details infringement allegations for independent claim 1 Compl. ¶101
• Accused Features: The accused features include the method of operating the ProPILOT Assist system, which allegedly uses a GPROS to manage application threads from sensors, perform autonomous movement planning for functions like lane centering, and uses a hardware-independent set of configurable application services Compl. ¶¶103-107

U.S. Patent No. 9,195,233 - "General Purpose Robotics Operating System"

• Patent Identification: U.S. Patent No. 9,195,233, issued November 24, 2015 Compl. ¶15
• Technology Synopsis: This foundational patent claims a non-transitory medium encoding a GPROS. The GPROS comprises a set of application services that are completely configurable, adaptable, hardware-independent, and include services for peripherals (sensors, actuators) and for managing application threads Compl. ¶¶118, 120
• Asserted Claims: Claims 1-16, 20-24, and 27 Compl. ¶119 The complaint details infringement allegations for independent claim 1 Compl. ¶120
• Accused Features: The accused features are the non-transitory media (e.g., firmware) in Nissan vehicles encoding the ProPILOT Assist GPROS. This includes its hardware-independent architecture, its configurable and adaptable application services (e.g., intelligent cruise control, lane centering), and its use of sensor, actuator, and peripheral services Compl. ¶¶122-127

III. The Accused Instrumentality

Product Identification

• The accused instrumentalities are Nissan and Infiniti vehicles equipped with any version of the ProPILOT Assist system, including ProPILOT Assist 1.1, 2.0, 2.1, and ProPILOT Assist with Navilink Compl. ¶31 Compl. ¶31, fn. 6

Functionality and Market Context

• ProPILOT Assist is an Advanced Driver-Assistance System (ADAS) that provides "hands-on driver assist" functionalities Compl. ¶31 These include Intelligent Cruise Control, which manages speed and distance to other vehicles; Steering Assist for lane centering; and a stop-and-hold function for traffic Compl. ¶31 The complaint contains a marketing screenshot from Nissan describing these features Compl. p. 11
• More advanced versions, such as ProPILOT Assist 2.0, are alleged to offer "hands-off single-lane driving" and "hands-on guided lane changing abilities" on mapped highways Compl. ¶32 A descriptive text box in the complaint outlines the evolution from version 1.1's lane-keeping to version 2.1's more advanced overtaking capabilities Compl. p. 11
• The complaint alleges that to deploy these features across their vehicle fleets, Defendants rely on a GPROS with configurable applications, including systems based on Linux, MICROSAR, and AUTOSAR architectures Compl. ¶30

IV. Analysis of Infringement Allegations

U.S. Patent No. 12,181,877 Infringement Allegations

U.S. Patent No. 11,782,442 Infringement Allegations

Identified Points of Contention

• Scope Questions: A central dispute may revolve around whether an ADAS like ProPILOT Assist, which assists a human driver, qualifies as a "general purpose robotics operating system" for an "autonomous vehicle" under the patents' claim language. The complaint alleges ProPILOT provides "autonomous vehicle functions" Compl. ¶63, but the scope of these terms will likely be contested.
• Technical Questions: The infringement theory hinges on the allegation that ProPILOT Assist is "independent of an underlying hardware platform" Compl. ¶46 Compl. ¶67 A key question for the court will be what level of hardware abstraction is required by this limitation and whether the accused system, while deployed across multiple Nissan/Infiniti models, meets that standard or is still considered tightly coupled to a proprietary hardware ecosystem.
• Another technical question may arise regarding the term "servomechanism" as used in the '442 Patent. The court may need to determine if Nissan's modern electronic control units for steering, braking, and throttle perform the functions of the claimed "servomechanisms" in a manner that constitutes infringement.

V. Key Claim Terms for Construction

"general purpose robotics operating system (GPROS)"

• Context and Importance: This term is the foundation of all asserted patents. The entire dispute may turn on whether Nissan's ProPILOT Assist system, an ADAS, falls within the scope of a "GPROS." Practitioners may focus on this term because it appears to be a neologism defined by the patentee, and its construction will determine whether the patents read on the accused technology class at all.
• Intrinsic Evidence for a Broader Interpretation: The '251 Patent specification describes a GPROS as providing "generic and general purposes software services for use by any robotics or automation application" '251 Patent, col. 2:11-13 and enabling the "plug-in" of various services like sensors and actuators '251 Patent, col. 3:3-20 This language may support a broad construction that includes sophisticated, service-based ADAS.
• Intrinsic Evidence for a Narrower Interpretation: The background section of the related '251 Patent focuses on the problem of building distinct physical robots for different needs '251 Patent, col. 1:39-43 This context, along with references to unmanned ground, aerial, and underwater vehicles (UGVs, UAVs, UUVs) '251 Patent, col. 4:15-16, may support an argument that "robotics" as used in the patent implies fully unmanned, mobile platforms, rather than driver-assistance systems in a consumer vehicle.

"independent of an underlying hardware platform"

• Context and Importance: This limitation is critical to the patent's claimed advance over prior art systems that were allegedly tied to specific hardware. Infringement requires showing that ProPILOT Assist possesses this characteristic.
• Intrinsic Evidence for a Broader Interpretation: The specification describes the benefit as isolating "the robotic software from the robotic hardware, such that the abstraction of the robot can be performed without full knowledge of the actual robot (or bot) configuration" '251 Patent, col. 4:50-54 This could be interpreted to mean that as long as the core software can operate with different hardware components (e.g., sensors, actuators) via a generic interface, it meets the limitation, which the complaint alleges by pointing to its use across different vehicle models Compl. ¶46
• Evidence for a Narrower Interpretation: A defendant may argue that this term requires portability across fundamentally different computing architectures from different manufacturers, not just variations within a single company's ecosystem. The patent's goal of creating a "standardized, full service platform" '251 Patent, col. 1:64 could suggest a level of universal interoperability beyond what is implemented in the accused system.

VI. Other Allegations

• Indirect Infringement: The complaint alleges active inducement of infringement under 35 U.S.C. § 271(b). The basis for this allegation is that Defendants provide "instructional, marketing, and sales materials" that instruct customers and dealers on how to use ProPILOT Assist and promote its advantages, with the specific intent that they use the vehicles in an infringing manner Compl. ¶51 Compl. ¶70 Compl. ¶90 Compl. ¶109 Compl. ¶129
• Willful Infringement: The complaint does not use the term "willful" but alleges that Defendants have had notice of the patents "at least as of the date of this Complaint" Compl. ¶53 Compl. ¶72 Compl. ¶92 Compl. ¶111 Compl. ¶131 These allegations appear to lay the groundwork for a claim of post-suit infringement damages enhancement, but do not allege pre-suit knowledge.

VII. Analyst's Conclusion: Key Questions for the Case

This case presents several fundamental questions regarding the application of patent claims rooted in general robotics to the specific domain of automotive Advanced Driver-Assistance Systems. The outcome will likely depend on the court's resolution of these key issues:

• Definitional Scope: The central issue will be one of claim construction: Can the term "general purpose robotics operating system (GPROS)," disclosed in the context of creating a universal platform for disparate robots, be construed to cover a specialized, integrated ADAS like Nissan's ProPILOT Assist?
• Technical Scope: A key evidentiary question will be one of hardware independence: Does the ProPILOT Assist software architecture meet the claimed limitation of being "independent of an underlying hardware platform," or will evidence show it is fundamentally integrated with Nissan's proprietary vehicle electronics in a way that falls outside the claim's scope?
• Functional Equivalence: A third question will be whether the specific software and hardware components of the ProPILOT Assist system perform the functions recited in the claims. For example, does the system's management of sensor data and driver alerts constitute the claimed management of "synchronous, asynchronous, and real time application threads," or is there a functional mismatch between the accused product and the patented invention?