DCT
3:24-cv-06049
Samsara Inc v. Motive Tech Inc
Key Events
Amended Complaint
Table of Contents
complaint Intelligence
I. Executive Summary and Procedural Information
- Parties & Counsel:
- Plaintiff: Samsara Inc. (Delaware)
- Defendant: Motive Technologies, Inc. (Delaware)
- Plaintiff's Counsel: Shaw Keller LLP
- Case Identification: 3:24-cv-06049, D. Del., 03/20/2024
- Venue Allegations: Venue is alleged to be proper in the District of Delaware because the 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, and further alleges a years-long campaign of fraudulent access to Plaintiff's platform, misappropriation of technology, and false advertising.
- Technical Context: The lawsuit is in the field of Internet of Things (IoT) data platforms for physical operations, specifically focusing on AI-driven vehicle fleet management, telematics, and video-based driver safety systems.
- Key Procedural History: The complaint alleges an extensive pre-litigation history, including that Defendant's senior executives created fictitious customer accounts to surreptitiously access and study Plaintiff's platform, copied product designs and marketing strategies, and commissioned flawed benchmarking studies to falsely disparage Plaintiff's products. Plaintiff also states it informed Defendant of the patents-in-suit prior to filing the initial complaint.
Case Timeline
| Date | Event |
|---|---|
| 2015-01-01 | Samsara is founded |
| 2016-01-01 | Samsara releases its Vehicle Gateway product |
| 2017-01-01 | Samsara introduces the CM11 webcam |
| 2018-01-01 | Motive's alleged fraudulent access to Samsara's technology begins |
| 2018-06-01 | Motive (as KeepTruckin) releases its "Smart Dashcam" |
| 2019-01-01 | Motive releases its Vehicle Gateway product |
| 2019-04-09 | Priority Date for '130 Patent |
| 2020-05-01 | Priority Date for '373 Patent |
| 2021-08-01 | Motive introduces its "AI Dashcam" |
| 2021-09-21 | '130 Patent is issued |
| 2021-11-30 | '373 Patent is issued |
| 2021-12-01 | Samsara holds its Initial Public Offering (IPO) |
| 2022-01-01 | Motive rebrands from KeepTruckin |
| 2023-03-21 | '621 Patent is issued |
| 2023-09-26 | Samsara informs Motive of its patent portfolio |
| 2024-01-23 | Samsara informs Motive of the Patents-in-Suit with claim charts |
| 2024-03-20 | Amended Complaint is 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"
- Patent Identification: U.S. Patent No. 11,190,373 ("the '373 Patent"), "Vehicle Gateway Device and Interactive Graphical User Interfaces Associated Therewith," issued November 30, 2021.
The Invention Explained
- Problem Addressed: The patent's background section describes the difficulty in analyzing the voluminous and complex data from commercial vehicle fleets to understand and improve fuel and energy efficiency Compl. Ex. 1, col. 1:64-2:5 Fleet operators often could not compile information across different fleets, limiting their ability to compare their own efficiency against others Compl. Ex. 1, col. 3:27-4:13
- The Patented Solution: The invention provides a system where vehicle gateway devices collect and transmit vehicle metric data to a central computing device Compl. Ex. 1, abstract This central device analyzes data from a plurality of vehicles to determine correlations between various vehicle metrics (e.g., idling, speeding, RPM) and overall fuel/energy usage Compl. ¶109 It then uses these correlations to generate a "fuel/energy efficiency score" for a specific vehicle, which can be displayed to the user Compl. ¶109 Compl. Ex. 1, FIG. 5B
- Technical Importance: This approach provided a standardized, data-driven method for benchmarking and improving fuel efficiency across large, diverse fleets, moving beyond simple metrics like miles-per-gallon to a more nuanced, weighted score.
Key Claims at a Glance
- The complaint asserts independent claim 15 Compl. ¶129
- Claim 15 is a system claim comprising:
- A first vehicle gateway device to gather and transmit vehicle metric data.
- 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;
- determine correlations between 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; and
- cause the score to be provided in a user interface Compl. ¶107
- The complaint does not explicitly reserve the right to assert other claims but states infringement of "one or more claims" Compl. ¶129
U.S. Patent No. 11,127,130 - "Machine Vision System and Interactive Graphical User Interfaces Related Thereto"
- Patent Identification: U.S. Patent No. 11,127,130 ("the '130 Patent"), "Machine Vision System and Interactive Graphical User Interfaces Related Thereto," issued September 21, 2021.
The Invention Explained
- Problem Addressed: The patent background notes that configuring and gathering data from machine vision systems ("smart cameras") was often time-consuming, laborious, and difficult, especially for non-technical users, making real-time analysis across multiple devices impractical Compl. Ex. 2, col. 2:1-12
- The Patented Solution: The invention describes a machine vision system that can acquire an image, process it locally to identify features and determine an evaluation, locally store the image and evaluation, and transmit them for remote storage Compl. Ex. 2, abstract A key feature is an integrated web server that provides secure remote access to the stored images and evaluations, facilitating easier configuration and monitoring Compl. ¶116 Compl. Ex. 2, col. 4:5-13
- Technical Importance: This architecture combines local processing with centralized, web-based remote access, aiming to make automated inspection systems more affordable, easier to deploy, and faster to monitor across many sites Compl. Ex. 2, col. 3:51-55
Key Claims at a Glance
- The complaint asserts independent claim 1 Compl. ¶155
- Claim 1 is a system claim comprising:
- An image sensor.
- A computer-readable storage medium with instructions including a web server.
- One or more processors configured to:
- acquire an image via the 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; and
- execute the web server to provide secure remote access to the image and evaluation Compl. ¶114
- The complaint states infringement of "one or more claims," including at least claim 1 Compl. ¶155
U.S. Patent No. 11,611,621 - "Event Detection System"
- Patent Identification: U.S. Patent No. 11,611,621 ("the '621 Patent"), "Event Detection System," issued March 21, 2023.
- Technology Synopsis: The patent addresses the lack of functionality in prior art event data recorders (EDRs) to efficiently detect and monitor safety events in real-time Compl. ¶123 The patented method uses data from a first sensor (e.g., a camera) to detect an image feature corresponding to an event type (e.g., a traffic sign), which then triggers the use of a second sensor device to access a second data stream (e.g., GPS or speed data) to augment the event detection and present a notification Compl. ¶124
- Asserted Claims: The complaint asserts method claim 8 Compl. ¶174
- Accused Features: The complaint alleges that Motive's safety event detection service, which uses a dashcam (first sensor) to detect an event like a rolling stop and then uses data from the Vehicle Gateway (second sensor) such as speed to confirm the event, infringes the '621 Patent Compl. ¶¶175-183
III. The Accused Instrumentality
Product Identification
- The accused instrumentalities are the Motive Vehicle Gateway, the Motive AI Dashcam, the Motive AI Omnicam, and associated cloud-based software services, including the Motive Dashboard, the Motive Safety Hub, and the Motive Driver Fuel Score Compl. ¶125
Functionality and Market Context
- The complaint alleges that Motive's products form an "integrated platform" for fleet management Compl. ¶44 The Vehicle Gateway is a hardware device that connects to a vehicle to collect and transmit telematics data such as speed, fuel, and engine load Compl. ¶132 The AI Dashcam and AI Omnicam are camera systems that detect unsafe driving events using computer vision and can provide in-cab alerts Compl. ¶42 Compl. ¶157
- This hardware connects to Motive's cloud platform, which includes a Data Platform for aggregation and AI-Powered Applications for analysis Compl. ¶131 The complaint provides a diagram of Motive's "AI-Powered Applications" to illustrate this architecture Compl. p. 59 Specific accused software features include the "Fuel Score," which is alleged to be determined from vehicle metric data Compl. ¶136, and a "safety event detection service" that identifies driving events Compl. ¶175
- The complaint frames Motive as a "follower and a consummate copyist" that entered the market pioneered by Samsara and imitated its products and platform structure to stay competitive Compl. ¶42 Compl. ¶44
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 | Motive's Vehicle Gateway is a device that collects and transmits vehicle metric data such as speed, fuel, and engine load. | ¶132 | col. 2:9-15 |
| a computing device comprising: [a] a computer readable storage medium... and [b] one or more processors... | Motive's suite of AI-Powered Applications run on the cloud, which includes computer-readable storage and processors. | ¶133; ¶134 | col. 3:5-8 |
| 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 vehicle gateway devices. The complaint includes a screenshot of Motive's "Fuel Hub Driver Details" page showing data from multiple vehicles Compl. p. 61 | ¶135 | col. 3:9-11 |
| 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 are alleged to determine a Fuel Score based on fuel efficiency calculations, considering variables like idling, speeding, and RPM over time. | ¶136 | col. 3:11-13 |
| 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 | The Motive AI-Powered Applications allegedly compute the Fuel Score by correlating a driver's performance with that of other drivers, which involves normalizing for variables that affect fuel economy (e.g., environmental conditions, load state), thereby determining correlations. | ¶140 | col. 3:13-18 |
| 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 requires determining weightings of vehicle metrics (such as RPM and idling duration) after removing the effect of other variables on fuel usage. | ¶142 | col. 3:18-21 |
| 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, driving fuel) from an individual vehicle. | ¶143 | col. 3:21-24 |
| determine, based on the determined weightings and the first vehicle metric data, a fuel/energy efficiency score associated with the first vehicle | Motive's applications are alleged to determine a "fuel/energy efficiency score" (the "Fuel Score") based on the weightings and individual vehicle metric data. | ¶146 | col. 3:24-27 |
| cause the fuel/energy efficiency score to be provided in an alert, report, or interactive graphical user interface | The Fuel Score is allegedly provided in a report or interactive graphical user interface, such as the Motive Fleet Dashboard. The complaint provides a screenshot of the "What is Fuel Hub?" interface showing a fuel score Compl. p. 71 | ¶147 | col. 3:27-30 |
- Identified Points of Contention:
- Scope Questions: A central question may be whether Motive's "Fuel Score" constitutes a "fuel/energy efficiency score" as claimed. The analysis may explore whether Motive's alleged process of comparing a driver to a network of other drivers to "normalize variables" Compl. ¶140 meets the claim's requirement of determining "correlations" and then applying "weightings" based on those correlations to calculate a score.
- Technical Questions: The case may require evidence showing that Motive's system actually performs the multi-step analytical process of determining correlations across a fleet and then using those specific correlations to derive weightings for a score calculation, as opposed to using a different or more generalized 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 (a road-facing and a driver-facing digital camera), and the AI Omnicam has one image sensor. | ¶158 | col. 1:50-51 |
| a computer readable storage medium having program instructions...including at least a web server configured to provide communication with other computer devices | The Motive system allegedly includes computer-readable storage (e.g., RAM) and a web server for communication, as the cloud platform provides secure internet connectivity to the dashcams. | ¶159 | col. 1:52-56 |
| acquire an image via the image sensor | The AI Dashcam and AI Omnicam have processors that 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 AI Dashcam and AI Omnicam allegedly have software to process captured images to identify features related to unsafe driving, such as distracted driving, "hard brakes," or unsafe lane changes. A visual in the complaint shows the AI Omnicam identifying an "Unsafe lane change" Compl. p. 77 | ¶162 | col. 1:60-62 |
| determine an evaluation of the image based at least in part on the one or more features | The AI Dashcam and AI Omnicam are alleged to determine evaluations of images, such as classifying an event as an "unsafe driving event" or "distracted driver event." | ¶163 | col. 1:62-64 |
| locally store the image and the evaluation | The AI Dashcam and AI Omnicam are alleged to locally store images that may contain significant events. The complaint cites a Motive blog post explaining that dashcams locally "save video[s]" of severe events Compl. p. 77 | ¶164 | col. 1:65-66 |
| transmit the image and evaluation for remote storage | The AI Dashcam and AI Omnicam are alleged to transmit images and their evaluations (e.g., high-risk events and DPE logic) for storage on the Motive cloud. | ¶165 | col. 2:1-2 |
| execute the web server to provide secure remote access to the image and evaluation | The Motive Vehicle Gateway allegedly provides remote access for the Motive cloud to "fetch" videos stored on the dashcams, and the data is subsequently provided to fleet customers. | ¶166 | col. 2:3-5 |
- Identified Points of Contention:
- Scope Questions: The construction of "locally store" will likely be a key issue. The dispute may turn on whether the accused devices' method of saving videos of "potentially severe" events Compl. ¶164 meets the claim's requirement to store both "the image and the evaluation" locally.
- Technical Questions: A factual question may be how the accused system's "web server" functionality is implemented. The analysis will likely focus on whether the combination of the Vehicle Gateway providing connectivity and the cloud platform providing access constitutes executing a web server "to provide secure remote access to the image and evaluation" as required by the claim, particularly how the "evaluation" is accessed.
V. Key Claim Terms for Construction
'373 Patent
- The Term: "fuel/energy efficiency score"
- Context and Importance: This term is the ultimate output of the claimed system. Its definition is critical because the infringement case hinges on whether Motive's "Fuel Score" feature Compl. ¶136 falls within the scope of this term. Practitioners may focus on this term because its meaning will determine whether a score based on network-wide driver comparison and normalization constitutes the specific type of calculated score recited in the patent.
- Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The claim language defines the score broadly as being "based on the determined weightings and the first vehicle metric data" Compl. Ex. 1, claim 15, which may support an interpretation covering any score derived from weighted metrics.
- Evidence for a Narrower Interpretation: The specification describes the score as being generated from "a plurality of fuel/energy efficiency indicators" like "cruise control use, use of coasting, a particular type of use of the accelerator pedal, idling, braking anticipation... and/or particular RPM range(s)" Compl. Ex. 1, col. 4:1-7 This could support a narrower definition tied to these specific types of indicators, rather than a more abstract, comparative network score.
'130 Patent
- The Term: "locally store"
- Context and Importance: This term is central to the system's architecture, distinguishing between on-device and remote actions. The infringement allegation rests on the claim that Motive's dashcams locally store videos of "potentially severe" events Compl. ¶164 The case may turn on whether this temporary, event-based local caching satisfies the "locally store the image and the evaluation" limitation.
- Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The claim requires the system to "locally store the image and the evaluation" and separately to "transmit the image and evaluation for remote storage," suggesting local storage could be transient or a precursor to transmission, which might support a broader reading.
- Evidence for a Narrower Interpretation: The patent abstract mentions the "machine vision device may include on-device memory for storing images and analyses" Compl. Ex. 2, abstract This could be argued to imply a more permanent or comprehensive local storage function, rather than just temporary caching of select events, supporting a narrower interpretation.
VI. Other Allegations
- Indirect Infringement:
- Inducement: The complaint alleges Motive induces infringement by providing instructional materials to customers on how to use the accused features. For the '373 Patent, this includes instructing customers on how to use the Fuel Score feature Compl. ¶148 For the '130 Patent, this includes providing guides and videos on how to install and use its dashcams Compl. ¶167 For the '621 patent, this includes advertising and providing instructions on its safety event detection service Compl. ¶¶184-185
- Contributory Infringement: The complaint alleges that Motive's products (e.g., the Vehicle Gateway and Fuel Score feature for the '373 Patent) are "especially made and/or adapted for infringing" and are "not staple articles of commerce suitable for substantial non-infringing uses" Compl. ¶149 Similar allegations are made for the '130 and '621 patents Compl. ¶168 Compl. ¶186
- Willful Infringement: Willfulness is alleged for all three patents. The basis is alleged pre-suit knowledge, specifically that Samsara informed Motive of its patent portfolio on September 26, 2023, and then provided specific notice of the patents-in-suit with claim charts on January 23, 2024 Compl. ¶126 The complaint also alleges knowledge since the filing of the original complaint on January 24, 2024 Compl. ¶126
VII. Analyst's Conclusion: Key Questions for the Case
- A core issue will be one of technical implementation: does Motive's "Fuel Score," which is allegedly based on normalizing a driver's performance against a network of other drivers, perform the specific analytical steps required by claim 15 of the '373 patent-namely, determining fleet-wide "correlations" between metrics and fuel use, and then applying "weightings" derived from those specific correlations to calculate the score?
- A second central question will be one of architectural scope: for the '130 patent, does the accused system's alleged function of temporarily saving videos of "potentially severe" events on the dashcam Compl. ¶164 satisfy the "locally store the image and the evaluation" limitation, or does the claim require a more comprehensive or persistent local storage of both the image and its analytical evaluation?
- Beyond the patent claims, a significant aspect of the litigation involves extensive allegations of unfair competition, including that Motive built its business by systematically and fraudulently accessing Samsara's platform under false pretenses. A key question for the court will be whether the evidence supports this narrative of pervasive, leadership-driven copying, which underpins the willfulness and non-patent counts, or if the conduct constitutes more routine competitive intelligence gathering.
Analysis metadata
Loading Amended Complaint
Suggested improvements