DCT

1:24-cv-00084

Samsara Inc v. Motive Tech Inc

Log In
Key Events
Amended Complaint
complaint Intelligence

I. Executive Summary and Procedural Information

  • Parties & Counsel:
  • Case Identification: 1:24-cv-00084, D. Del., 03/20/2024
  • Venue Allegations: Venue is alleged to be proper in the District of Delaware because Defendant Motive Technologies, Inc. is a Delaware corporation and therefore resides in the state.
  • Core Dispute: Plaintiff alleges that Defendant's vehicle telematics and video safety products infringe three patents related to fleet fuel efficiency analysis, machine vision systems, and event detection.
  • Technical Context: The lawsuit concerns the Internet of Things (IoT) fleet management industry, where hardware sensors in vehicles collect operational data that is analyzed by cloud-based software to improve safety, efficiency, and sustainability.
  • Key Procedural History: The complaint alleges that Samsara informed Motive of its patent portfolio on September 26, 2023. On January 23, 2024, Samsara allegedly provided Motive with claim charts detailing its infringement theories. The original complaint in this action was filed on January 24, 2024. These allegations of pre-suit and post-filing knowledge may be relevant to potential claims of willful infringement.

Case Timeline

Date Event
2018-06-01 Motive launches its "Smart Dashcam"
2019-01-01 Motive releases its "Vehicle Gateway"
2019-04-09 Priority Date for '130 Patent
2019-04-26 Priority Date for '621 Patent
2020-05-01 Priority Date for '373 Patent
2021-08-01 Motive launches its "AI Dashcam"
2021-09-21 '130 Patent Issued
2021-11-30 '373 Patent Issued
2023-03-21 '621 Patent Issued
2023-09-26 Samsara allegedly informs Motive of its patent portfolio
2024-01-23 Samsara allegedly provides claim charts to Motive
2024-01-24 Original Complaint Filed
2024-03-20 Amended Complaint Filed

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

U.S. Patent No. 11,190,373 - "Vehicle Gateway Device and Interactive Graphical User Interfaces Associated Therewith"

The Invention Explained

  • Problem Addressed: The patent describes the difficulty for commercial fleet operators in determining precisely how and why fuel and energy are used, as well as the technical challenges of collecting and processing the voluminous data generated by vehicles in transit Compl. ¶108 '373 Patent, col. 1:64-2:5 It also notes that operators historically lacked information to compare their own fleet's efficiency against others '373 Patent, col. 3:27-4:13
  • The Patented Solution: The invention is a system that uses a vehicle gateway device to gather metrics from a vehicle and a computing device to analyze that data across a fleet. The computing device determines fuel/energy usage, identifies "correlations" between that usage and other vehicle metrics (like driving behaviors), establishes "weightings" for those metrics based on the correlations, and then calculates a "fuel/energy efficiency score" for an individual vehicle, which can be displayed to the user Compl. ¶109 This provides a single, actionable score reflecting complex data.
  • Technical Importance: The technology provides a standardized, data-driven method to measure and benchmark fuel efficiency that goes beyond simple miles-per-gallon, enabling more nuanced fleet management and driver coaching Compl. ¶¶109-110

Key Claims at a Glance

  • The complaint asserts independent claim 15 Compl. ¶129
  • Essential elements of claim 15 include:
    • A first vehicle gateway device to gather and transmit vehicle metric data from a first vehicle.
    • A computing device with instructions to:
    • Receive vehicle metric data from a plurality of vehicle gateway devices.
    • Determine fuel/energy usage of the plurality of vehicles over time.
    • Determine correlations among other vehicle metrics and the fuel/energy usage.
    • Determine weightings of the other vehicle metrics based on the correlations.
    • Receive the first vehicle metric data from the first vehicle gateway device.
    • Determine a fuel/energy efficiency score for the first vehicle based on the weightings and its metric data.
    • Cause the score to be provided in an alert, report, or interactive graphical user interface.
  • The complaint reserves the right to assert additional claims Compl. ¶129

U.S. Patent No. 11,127,130 - "Machine Vision System and Interactive Graphical User Interfaces Related Thereto"

The Invention Explained

  • Problem Addressed: The patent identifies challenges with conventional "smart cameras" or machine vision systems, including the difficulty of configuring them, gathering data efficiently for real-time analysis, and handling device failures or updates Compl. ¶115 '130 Patent, col. 2:1-17
  • The Patented Solution: The patent describes a machine vision system that performs several key functions. It acquires an image, processes it locally to identify features, determines an "evaluation" of the image locally, and stores both the image and evaluation locally. The system also transmits the image and evaluation for remote storage and includes a "web server" to provide secure remote access to the locally stored data Compl. ¶116 '130 Patent, claim 1 This architecture combines the speed of local processing with the scalability of cloud connectivity and remote management.
  • Technical Importance: This approach makes automated inspection systems more affordable and faster to deploy by integrating on-device processing with centralized management and reporting capabilities, reducing downtime and complexity '130 Patent, col. 3:50-62

Key Claims at a Glance

  • The complaint asserts independent claim 1 Compl. ¶155
  • Essential elements of claim 1 include:
    • An image sensor.
    • A computer readable storage medium with program instructions, including at least a web server.
    • One or more processors configured to execute instructions to:
    • Acquire an image via the image sensor.
    • Process the image to identify features.
    • Determine an evaluation of the image based on the features.
    • Locally store the image and evaluation.
    • Transmit the image and evaluation for remote storage.
    • Execute the web server to provide secure remote access to the image and evaluation.
  • The complaint reserves the right to assert additional claims Compl. ¶155

U.S. Patent No. 11,611,621 - "Event Detection System"

  • Patent Identification: U.S. Patent No. 11,611,621 ("the '621 Patent"), titled "Event Detection System," issued on March 21, 2023.
  • Technology Synopsis: The patent addresses the inefficiency of prior art event data recorders (EDRs) in detecting safety events in real-time Compl. ¶123 The invention is a method for event detection that uses data from two distinct sensor devices. A feature detected by a first sensor (e.g., a camera identifying a traffic sign) triggers the selection and use of data from a second sensor (e.g., a vehicle's GPS or accelerometer) to augment the initial data and confirm the event Compl. ¶124
  • Asserted Claims: At least claim 8 is asserted Compl. ¶174
  • Accused Features: The complaint alleges that Motive's safety event detection service, which is used to identify driving events, infringes the '621 Patent Compl. ¶174 Compl. ¶175

III. The Accused Instrumentality

Product Identification

  • The accused instrumentalities are the Motive Vehicle Gateway, Motive AI Dashcam, Motive AI Omnicam, and the associated cloud-based software services, including the Motive Dashboard, Motive Safety Hub, and Motive Driver Fuel Score Compl. ¶125

Functionality and Market Context

  • The complaint alleges the accused system operates as an integrated platform. The Motive Vehicle Gateway is described as a hardware device that connects to a vehicle to collect and transmit metric data such as speed, fuel, and engine load Compl. ¶132 The Motive AI Dashcam and AI Omnicam are camera systems that detect unsafe driving events using computer vision algorithms and provide connectivity to a cloud platform Compl. ¶¶157-158
  • These hardware components allegedly work with Motive's cloud platform, which comprises a "Motive Data Platform" and "Motive AI-Powered Applications" Compl. ¶131 This platform is alleged to receive, aggregate, and analyze the data to provide services like a "Fuel Score" for drivers Compl. ¶136 and a "Safety Hub" for reviewing safety events Compl. ¶125 The complaint includes a "Motive System Overview" diagram to illustrate this three-tiered architecture of IoT Devices, a Data Platform, and AI-Powered Applications Compl. p. 59, Ex. 9
  • The complaint positions Motive as a "copyist" that entered the market pioneered by Samsara and modeled its products, platform structure, and even marketing on Samsara's offerings Compl. ¶¶42-45

IV. Analysis of Infringement Allegations

'373 Patent Infringement Allegations

Claim Element (from Independent Claim 15) Alleged Infringing Functionality Complaint Citation Patent Citation
a first vehicle gateway device configured to gather and transmit first vehicle metric data associated with a first vehicle The Motive Vehicle Gateway is a device configured to collect and transmit vehicle metric data (e.g., speed, fuel, fault codes) from a vehicle. ¶132 col. 21:28-33
a computing device comprising: a computer readable storage medium having program instructions embodied therewith; and one or more processors configured to execute the program instructions to cause the computing device to: Motive's suite of cloud-based AI-Powered Applications runs on computing devices (cloud computers) that include computer-readable storage and processors. ¶¶133-134 col. 3:6-10
receive vehicle metric data from a plurality of vehicle gateway devices associated with a plurality of vehicles Motive's Data Platform and AI-Powered Applications receive vehicle metric data from multiple Motive Vehicle Gateways associated with multiple vehicles in a customer's fleet. ¶135 col. 3:10-14
determine, from the vehicle metric data, fuel/energy usage of the plurality of vehicles over various periods of time Motive's Data Platform and AI-Powered Applications determine a "Fuel Score" based on fuel efficiency calculations, which involves determining fuel/energy usage from collected vehicle metric data over time. ¶136 col. 3:14-17
determine correlations among one or more other vehicle metrics and the fuel/energy usage of the plurality of vehicles over the various periods of time Motive's AI-Powered Applications allegedly compute the Fuel Score by correlating a driver's performance with that of other drivers, which involves normalizing for variables outside a driver's control (e.g., vehicle model, load state), a process that allegedly involves determining correlations. ¶140 col. 3:17-21
determine weightings of the one or more other vehicle metrics based at least in part on the determined correlations The complaint alleges that determining the Fuel Score entails determining weightings of vehicle metrics (e.g., RPM profile, idling duration) in the calculation after accounting for the determined correlations. ¶142 col. 3:21-24
receive, from the first vehicle gateway device, the first vehicle metric data associated with the first vehicle Motive's Data Platform and AI-Powered Applications receive vehicle metric data (e.g., average MPG, total distance, fuel cost) associated with an individual vehicle/driver. ¶¶143-144 col. 3:24-27
determine, based on the determined weightings and the first vehicle metric data, a fuel/energy efficiency score associated with the first vehicle Motive's Data Platform and AI-Powered Applications allegedly determine a fuel/energy efficiency score (the Fuel Score) based on the determined weightings and individual vehicle metric data. ¶146 col. 3:27-31
cause the fuel/energy efficiency score to be provided in an alert, report, or interactive graphical user interface. Motive's Data Platform and AI-Powered Applications cause the Fuel Score to be provided in an interactive graphical user interface, the Motive Fleet Dashboard. ¶147 col. 3:31-34
  • Identified Points of Contention:
    • Scope Questions: The dispute may center on whether Motive's "Fuel Score" calculation, which involves "normalizing" driver performance against a network of similar vehicles Compl. ¶140, meets the claim requirements of first determining "correlations" across a plurality of vehicles and then determining "weightings" based on those correlations. The construction of "correlations" and "weightings" will be critical.
    • Technical Questions: A key question for the court will be one of functional operation: what technical evidence supports the allegation that Motive's system calculates a score for a specific vehicle by using weightings derived from correlations determined across a plurality of other vehicles, as opposed to using a more generalized or pre-set scoring model?

'130 Patent Infringement Allegations

Claim Element (from Independent Claim 1) Alleged Infringing Functionality Complaint Citation Patent Citation
an image sensor The Motive AI Dashcam has two image sensors (road-facing and driver-facing), and the AI Omnicam has one image sensor. ¶158 col. 1:49-50
a computer readable storage medium having program instructions embodied therewith, the program instructions including at least a web server configured to provide communication with other computer devices The Motive system includes computer-readable storage (e.g., processor RAM) and software that constitutes a "web server" by providing secure connectivity and communication between the dashcams and the Motive cloud platform. ¶159 col. 1:51-55
one or more processors configured to execute the program instructions to cause the system to: The Motive system has processors in its dashcams, Vehicle Gateway, and cloud platform that are configured to perform the claimed functions. ¶160 col. 1:56-58
acquire an image via the image sensor The processors in the Motive AI Dashcam and AI Omnicam execute instructions to acquire digital images using their cameras. ¶161 col. 1:59-60
process the image to identify one or more features in the image The software in the AI Dashcam and AI Omnicam processes captured images to identify features related to unsafe driving, such as distracted driving, hard brakes, or unsafe lane changes. The complaint provides a screenshot showing the AI Dashcam identifying a "Hard Brake Detected" event Compl. p. 75 ¶162 col. 1:61-62
determine an evaluation of the image based at least in part on the one or more features The AI Dashcam and AI Omnicam determine evaluations of images, identifying them as "unsafe driving events" or "distracted driver events" based on the identified features. ¶163 col. 1:63-65
locally store the image and the evaluation The AI Dashcam and AI Omnicam allegedly locally store images and evaluations that may contain significant events, which Motive refers to as saving videos of Driver Performance Events ("DPEs"). ¶164 col. 2:1-2
transmit the image and evaluation for remote storage The AI Dashcam and AI Omnicam transmit images and their evaluations (e.g., DPE logic) to the Motive cloud for remote storage, at least via the Vehicle Gateway. ¶165 col. 2:3-4
execute the web server to provide secure remote access to the image and evaluation. The Motive Vehicle Gateway provides a means for the Motive cloud to "fetch" videos stored on the dashcams, and the system subsequently provides this data to fleet customers, thereby providing secure remote access. ¶166 col. 2:5-7
  • Identified Points of Contention:
    • Scope Questions: A central dispute may be the definition of "web server." The question will be whether the combination of firmware on the Motive dashcam providing 4G connectivity and the remote Motive cloud platform, which provides access to the data, constitutes the claimed "web server."
    • Technical Questions: The analysis may turn on the sequence and location of operations. Does the accused system perform a distinct step of "locally" storing the "evaluation" before transmission, or are features/evaluations generated as part of a continuous stream for immediate or near-immediate cloud processing? The distinction between local buffering and the claimed "locally store" step could be a focal point.

V. Key Claim Terms for Construction

  • '373 Patent

    • The Term: "determine correlations" (claim 15)
    • Context and Importance: This term is central to the analytical core of the invention. The infringement case for the '373 patent depends on whether Motive's "normalization" process Compl. ¶140, used to create its Fuel Score, falls within the scope of "determining correlations." Practitioners may focus on this term because it distinguishes the claimed invention from a simple, predefined scoring algorithm.
    • Intrinsic Evidence for Interpretation:
      • Evidence for a Broader Interpretation: The specification may support a broader definition if it discusses analyzing "trends" or other general relationships between vehicle metrics and fuel usage across a fleet (e.g.,'373 Patent, col. 3:14-21).
      • Evidence for a Narrower Interpretation: The patent may support a narrower definition if the detailed description provides specific mathematical or statistical methods for calculating correlations, which could limit the term to those specific methods '373 Patent, col. 4:1-13

  • '130 Patent

    • The Term: "a web server configured to provide communication with other computer devices" (claim 1)
    • Context and Importance: This is a key structural limitation. The case may hinge on whether Motive's distributed architecture, which connects an in-vehicle device to a remote cloud platform, meets the definition of a system comprising "a web server."
    • Intrinsic Evidence for Interpretation:
      • Evidence for a Broader Interpretation: The patent's description of "built-in wireless and/or wired communications capabilities" '130 Patent, col. 3:19-20 and the goal of connecting to a "remote management server" '130 Patent, col. 2:50-51 may support a broader interpretation where any component facilitating network communication qualifies.
      • Evidence for a Narrower Interpretation: The claim language requires the "program instructions" on the "computer readable storage medium" to include the web server. This could be interpreted to mean the web server software must reside on the local device itself, potentially excluding a system where the primary access and communication logic resides in a remote cloud.

VI. Other Allegations

  • Indirect Infringement: The complaint alleges both induced and contributory infringement for all three patents-in-suit. The inducement allegations are supported by claims that Motive provides instructional materials, such as help center articles, product documentation, and instructional e-books, that allegedly instruct customers on how to use the accused products in an infringing manner Compl. ¶148 Compl. ¶167 Compl. ¶185 The contributory infringement allegations are based on the assertion that the accused products are especially made or adapted for infringing the patents and are not staple articles of commerce with substantial non-infringing uses Compl. ¶149 Compl. ¶168 Compl. ¶186
  • Willful Infringement: The complaint alleges that Motive had knowledge of the patents-in-suit since at least the filing of the original complaint on January 24, 2024, and was specifically notified with claim charts on January 23, 2024 Compl. ¶126 It also alleges pre-suit knowledge based on a September 26, 2023 letter regarding Samsara's patent portfolio Compl. ¶126 These allegations are supplemented by extensive factual claims of intentional copying and fraudulent access to Samsara's platform to reverse-engineer its technology, which may be used to argue Motive acted with "willful, intentional, and conscious disregard" of Samsara's patent rights Compl. ¶152 Compl. ¶171 Compl. ¶189

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

This case appears to present several intertwined questions of technical function, claim scope, and alleged business practices. The key issues for judicial determination will likely include:

  • A core issue will be one of functional scope: does Motive's "Fuel Score," which allegedly normalizes driver performance by comparing them to a network of similar vehicles, perform the specific, multi-step process required by the '373 patent of first "determining correlations" and then "determining weightings" based on those correlations to generate a score?
  • A second central issue will be one of structural definition: can the term "web server" in the '130 patent, which describes a component of a "machine vision system," be construed to encompass the distributed architecture of Motive's AI Dashcam and its connectivity to a remote cloud platform, or is the claim limited to a system where the web server resides on the local device itself?
  • A key evidentiary question for the '621 patent will be whether Motive's safety event detection service, in practice, uses a feature from a first sensor (e.g., a camera detecting a stop sign) to trigger the selection and use of data from a separate, second sensor (e.g., a vehicle gateway providing speed data) to confirm a safety event, as required by the patent's two-sensor detection method.
Loading Amended Complaint