Perrone Robotics Inc v. Mazda Motor Of America Inc

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Perrone Robotics, Inc. and Perrone Robotics Innovations, LLC (Delaware)
  • Defendant: Mazda Motor of America, Inc. (California) and Mazda Motor Corporation (Japan)
  • Plaintiff's Counsel: BUNSOW De MORY LLP; Susman Godfrey LLP.
• Case Identification: 3:25-cv-00983, E.D. Va., 11/25/2025
• Venue Allegations: Venue is alleged to be proper in the Eastern District of Virginia because Mazda has regular and established places of business, including showrooms and dealerships, within the district, is registered to do business in Virginia, and has committed acts of infringement by selling the accused products in the district.
• Core Dispute: Plaintiff alleges that Defendant's vehicles equipped with the i-ACTIVSENSE driver-assistance suite infringe five U.S. patents related to a general purpose robotics operating system for autonomous vehicles.
• Technical Context: The technology at issue is a hardware-independent software platform designed to manage and control robotics and automation applications, which is significant in the automotive industry's development of Advanced Driver-Assistance Systems (ADAS) and autonomous driving capabilities.
• Key Procedural History: The complaint contextualizes the invention with reference to the 2005 DARPA Grand Challenge, noting that the inventor's work on a general purpose robotics operating system was a departure from the vehicle-specific approaches used by other participants. The asserted patents claim priority back to an application filed in February 2006.

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, "General Purpose Robotics Operating System with Unmanned and Autonomous Vehicle Extensions," issued December 31, 2024 Compl. ¶11

The Invention Explained

• Problem Addressed: The complaint asserts that prior to the invention, creating robotic or automated devices required building custom, hardware-specific software from scratch for each new device, an approach that was inefficient, rigid, and a barrier to scalability and interoperability Compl. ¶¶17, 21
• The Patented Solution: The patents describe a "general purpose robotics operating system" (GPROS) that provides a hardware-independent software platform Compl. ¶¶18, 25 This platform uses a layer of generic abstractions and configurable services to manage robotics applications, allowing the same software architecture to be deployed across different vehicles and hardware configurations Compl. ¶21 '442 Patent, col. 1:11-24
• Technical Importance: This architectural approach allegedly solved a key computing problem in robotics by decoupling application software from specific hardware, which was not a well-understood or routine solution at the time and enabled the large-scale deployment of automated vehicle fleets Compl. ¶¶21, 23

Key Claims at a Glance

• The complaint asserts independent claim 1 Compl. ¶39 Compl. ¶40
• Claim 1 of the '877 Patent recites a vehicle comprising the following essential elements:
  • A steering mechanism, a brake, and a throttle.
  • An operating system with a set of application services for managing an obstacle service, where the services are hardware-independent and configurable for communication and operational tasks.
  • The application services are further defined as: (i) configurable using a configuration service, (ii) configurable to be adapted both statically and dynamically, and (iii) configurable to access configuration data using a generic abstraction.
  • A graphical user interface.
  • The vehicle is adapted to receive configuration data over a network and to avoid obstacles.
• The complaint reserves the right to assert other claims, including dependent claims 2-6, 8, 10, 12, and 14-21 Compl. ¶39

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, "General Purpose Robotics Operating System with Unmanned and Autonomous Vehicle Extensions," issued October 10, 2023 Compl. ¶12

The Invention Explained

• The technology described is substantively the same as that detailed for the '877 Patent, focusing on a hardware-independent GPROS for managing autonomous vehicle functions Compl. ¶¶17-28

Key Claims at a Glance

• The complaint asserts independent claim 8 Compl. ¶59 Compl. ¶60
• Claim 8 of the '442 Patent recites an autonomous vehicle comprising the following essential elements:
  • A vehicle having a steering mechanism, a brake, and a throttle.
  • A general purpose robotics operating system (GPROS) with application services configured to manage synchronous, asynchronous, or real-time application threads, where the services are hardware-independent 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.
  • A throttle servomechanism to control the throttle based on the movement plan.
• The complaint reserves the right to assert other claims, including claims 1-4, 6, 7, 9, 11, 12, 15, and 17-20 Compl. ¶59

Multi-Patent Capsule: U.S. Patent No. 11,314,251

• Patent Identification: U.S. Patent No. 11,314,251, "General Purpose Robotics Operating System with Unmanned and Autonomous Vehicle Extensions," issued April 26, 2022 Compl. ¶13
• Technology Synopsis: The patent addresses the inefficiency of creating custom hardware-specific software for each new robotic device Compl. ¶17 It proposes a GPROS that provides a standardized, hardware-independent platform with configurable application services to manage autonomous vehicle functions, such as controlling servomechanisms based on a movement plan (Compl. ¶18, Compl. ¶24; '251 Patent, Compl. ¶abstract).
• Asserted Claims: The complaint asserts independent claim 2 Compl. ¶¶78-79
• Accused Features: The i-ACTIVSENSE system in Mazda vehicles is accused of being an autonomous vehicle equipped with a GPROS that manages application threads and is configurable both statically and dynamically, and uses servomechanisms to control steering, braking, and throttle based on a movement plan Compl. ¶¶80-87

Multi-Patent Capsule: U.S. Patent No. 9,833,901

• Patent Identification: U.S. Patent No. 9,833,901, "General Purpose Robotics Operating System with Unmanned and Autonomous Vehicle Extensions," issued December 5, 2017 Compl. ¶14
• Technology Synopsis: This patent claims a method performed within a GPROS to manage autonomous vehicle functions. The method involves using configurable, hardware-independent application services to manage application threads and at least one autonomous vehicle or movement planning service Compl. ¶100
• Asserted Claims: The complaint asserts independent method claim 1 Compl. ¶¶99-100
• Accused Features: Mazda is accused of performing the claimed method when testing and using its i-ACTIVSENSE-equipped vehicles Compl. ¶101 The infringement allegation centers on the i-ACTIVSENSE GPROS executing on an ECU to manage ADAS applications like Lane Keep Assist Compl. ¶¶102-104

Multi-Patent Capsule: U.S. Patent No. 9,195,233

• Patent Identification: U.S. Patent No. 9,195,233, "General Purpose Robotics Operating System," issued November 24, 2015 Compl. ¶15
• Technology Synopsis: This patent claims a non-transitory medium that encodes a GPROS. The claimed GPROS comprises a set of application services that are hardware-independent, configurable, and include services for peripherals, sensors, actuators, and thread management Compl. ¶119
• Asserted Claims: The complaint asserts independent claim 1 Compl. ¶¶118-119
• Accused Features: The non-transitory media in Mazda vehicles, such as memory within an ECU, are accused of encoding the claimed GPROS Compl. ¶121 This GPROS allegedly provides automation services such as Mazda Radar Cruise Control and Lane Keep Assist Compl. ¶122

III. The Accused Instrumentality

Product Identification

• The accused instrumentalities are Mazda vehicles that include any version of the Mazda i-ACTIVSENSE system Compl. ¶31 Compl. ¶39 The Mazda CX-5 is identified as a non-limiting example Compl. ¶41

Functionality and Market Context

• The complaint describes i-ACTIVSENSE as a "driver assistance suite that utilizes technology like cameras, radar, and collision mitigation features" Compl. ¶31 Specific functionalities cited include Mazda Lane Keep Assist System, Mazda Radar Cruise Control, and Smart City Brake Support Compl. ¶33 A diagram in the complaint illustrates how the Lane-keep Assist System uses a Forward Sensing Camera to detect lane lines and provide steering assistance Compl. p. 12 Another diagram shows the Advanced Smart City Brake Support using the same camera to detect vehicles or pedestrians and automatically apply brakes Compl. p. 12
• Plaintiff alleges on information and belief that i-ACTIVSENSE relies on a GPROS based on Arene and an AUTOSAR-based GPROS to facilitate the deployment of these automated features across Mazda's fleet Compl. ¶30 Compl. ¶43 The complaint positions these features as a response to consumer demand and regulatory pressure for increased vehicle safety and automation Compl. ¶29

IV. Analysis of Infringement Allegations

'877 Patent Infringement Allegations

'442 Patent Infringement Allegations

Identified Points of Contention

• Scope Questions: A central dispute may concern whether Mazda's i-ACTIVSENSE, an integrated system for production vehicles, constitutes a "general purpose robotics operating system" as that term is used in the patents, which describe a technology arising from general robotics and applicable to a wide range of platforms (UGVs, UAVs, etc.). The infringement case may turn on whether this term can be construed to read on a specialized automotive architecture like AUTOSAR.
• Technical Questions: The complaint's allegation that i-ACTIVSENSE is "independent of the underlying platform" will likely be a point of contention. The analysis may focus on what level of abstraction and portability is required by the claims and what level is actually present in the accused system, which, while used across different models, may be tied to a specific family of Mazda-proprietary hardware.

V. Key Claim Terms for Construction

• The Term: "general purpose robotics operating system (GPROS)"

  • Context and Importance: This term is the foundation of the asserted patents. Its construction is critical because the infringement case depends on categorizing Mazda's specialized automotive software suite as a GPROS. Mazda may argue its system is a bespoke, domain-specific implementation, not a "general purpose" system.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The specification suggests a broad scope, defining a GPROS as a platform to "rapidly develop, configure, assemble, deploy, and extend robotics and automation applications compared to conventional technologies" and noting its applicability to unmanned ground, aerial, and underwater vehicles '251 Patent, col. 2:19-24 '251 Patent, col. 4:13-18
    • Evidence for a Narrower Interpretation: The background focuses heavily on the specific problem of creating bespoke software for each new robot, and the detailed embodiments are situated in the context of autonomous vehicles, which could support a narrower construction tied to modular, platform-agnostic robotics rather than integrated automotive systems '251 Patent, col. 1:39-58

• The Term: "independent of an underlying hardware platform"

  • Context and Importance: This limitation defines a key technical characteristic of the claimed invention. Practitioners may focus on this term because the degree to which i-ACTIVSENSE is truly hardware-agnostic, versus merely being deployed across a range of similar, proprietary Mazda ECUs, will be a central factual dispute.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The patent states that an objective is to "isolate 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," suggesting a high degree of independence '251 Patent, col. 4:50-54
    • Evidence for a Narrower Interpretation: The specification describes "plug-and-play" of various components like sensors and actuators within the GPROS framework '251 Patent, col. 3:1-10 This could be interpreted to mean independence in the context of swapping compatible components within the system's architecture, not portability of the entire system to a fundamentally different hardware environment.

VI. Other Allegations

• Indirect Infringement: The complaint alleges inducement to infringe all five patents. The stated basis for inducement is that Mazda provides instructional, marketing, and sales materials to its customers and dealers that describe and encourage the use of the accused i-ACTIVSENSE features, thereby knowingly inducing infringing use of the vehicles Compl. ¶50 Compl. ¶69 Compl. ¶89 Compl. ¶108 Compl. ¶128
• Willful Infringement: The complaint does not use the term "willful infringement." However, for each count of indirect infringement, it alleges that Mazda has had knowledge of the patents "at least since being served with this Complaint," which lays a foundation for a claim of post-filing willfulness or enhanced damages Compl. ¶50 Compl. ¶69 Compl. ¶89 Compl. ¶108 Compl. ¶128

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

• A core issue will be one of definitional scope: can the term "general purpose robotics operating system," rooted in the context of modular and platform-agnostic robotics, be construed to cover a highly integrated, domain-specific automotive software architecture like Mazda's i-ACTIVSENSE?
• A key evidentiary question will be one of technical equivalence: does the accused i-ACTIVSENSE system, which is deployed across a proprietary fleet of vehicles, meet the claimed limitation of being "independent of an underlying hardware platform" in the manner contemplated by the patents, or is there a fundamental mismatch in the level of hardware abstraction?
• A central factual dispute will likely be whether the accused system practices the specific three-part configurability recited in the claims (via a config service, static/dynamic adaptation, and generic abstraction), and what evidence demonstrates the presence and operation of these distinct software-architectural features within Mazda's product.