IP Library Granted Patent US 12,073,665
Granted Patent B2
US 12,073,665 · App. 18/123,188 · Granted Aug 27, 2024

System, method, and apparatus for managing vehicle data collection

Inventors: Yu Fang (Palo Alto, CA); Yixiang Chen (Palo Alto, CA); Robin Reed (Redwood City, CA); Thurston Zhu (San Francisco, CA)
Assignee: Sonatus, Inc.
G07C5/008G07C5/0808G07C5/0816H04L67/125
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,073,665
App. No.
18/123,188
Granted
Aug 27, 2024
Kind
B2
Abstract

A vehicle that includes a policy manager circuit, an endpoint, and a vehicle data interface. The policy manager circuit interprets a data collection policy including a trigger condition and a trigger evaluation data identifier. The endpoint captures a trigger evaluation data stream in response to the trigger evaluation data identifier and the trigger condition. The vehicle data interface receives the trigger evaluation data stream.

Claims (20)

1. A vehicle comprising:

a policy manager circuit configured to interpret a data collection policy including: a vehicle data identifier, a trigger configured to define a trigger condition, and a plurality of trigger conditions having a plurality of trigger types, the plurality of trigger types including at least two of a signal trigger, a vehicle status trigger, a timing trigger, a schedule trigger, a geofence trigger, an error trigger, an environment trigger, or a user input trigger; and

a trigger evaluation circuit configured to:

determine a trigger event occurrence in response to a trigger condition and trigger evaluation data and based on a first portion of the plurality of trigger conditions, the first portion including a first trigger having a first trigger type and a second trigger having a second trigger type,

determine a trigger event termination based on a second portion of the plurality of trigger conditions, wherein the second portion includes a first trigger having a first trigger type and a second trigger having a second trigger type,

determine a data capture window in response to the trigger event occurrence, trigger event termination, and the data collection policy, and

capture identified vehicle data in response to the data capture window and the vehicle data identifier.

2. The vehicle of claim 1 , wherein the trigger evaluation circuit determines the trigger event occurrence by evaluating the trigger evaluation data using the trigger condition, wherein the trigger condition defines a relationship with a present value that may be satisfied or unsatisfied by the trigger evaluation data.

3. The vehicle of claim 1 , wherein the trigger evaluation data includes at least one of a vehicle state, a vehicle status, a vehicle operating mode, or a vehicle discrete event.

4. The vehicle of claim 1 , wherein the identified vehicle data is generated by the vehicle before the trigger event occurrence and stored using a rotating buffer circuit.

5. The vehicle of claim 1 , wherein the plurality of trigger conditions corresponds to one of a plurality of trigger evaluation data values.

6. The vehicle of claim 5 , wherein the trigger evaluation circuit determines the trigger event occurrence in response to at least two of the plurality of trigger conditions.

7. The vehicle of claim 5 , wherein:

the plurality of trigger conditions includes a trigger condition that corresponds to one of the plurality of trigger evaluation data values; and

the trigger evaluation circuit determines the trigger event occurrence in response to the trigger condition.

8. The vehicle of claim 5 , wherein the plurality of trigger evaluation data values correspond to a plurality of data types, including at least two of a controller area network (CAN) message, a CAN signal, an ethernet packet, a vehicle location, a vehicle status, and a diagnostic trouble code.

9. The vehicle of claim 5 , wherein the plurality of trigger evaluation data values correspond to a plurality of data types, including at least one of a controller area network (CAN) message, a CAN signal, an ethernet packet, a vehicle location, a vehicle status, and a diagnostic trouble code.

10. The vehicle of claim 1 , wherein the trigger evaluation data includes a virtual sensor value derived from a plurality of vehicle data values.

11. The vehicle of claim 1 , wherein the data capture window terminates after a delay following the trigger event termination in response to the data collection policy.

12. The vehicle of claim 1 , wherein the data capture window terminates based at least in part on one or more trigger conditions.

Assignments (2)
SECURITY INTEREST Recorded Dec 23, 2025
From: SONATUS, INC.; SONATUS INTERNATIONAL HOLDING INC.; SONATUS IRELAND, LIMITED
To: TRIPLEPOINT CAPITAL LLC
Reel/Frame 074052/0671 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 5, 2024
From: CHEN, YIXIANG; FANG, YU; REED, ROBIN; ZHU, THURSTON
To: SONATUS, INC.
Reel/Frame 067022/0242 →
Continuity (11)
Continuation 17469148 · Sep 8, 2021
Continuation 17195589 · Mar 8, 2021
Continuation In Part 17027167 · Sep 21, 2020
Continuation In Part 17027187 · Sep 21, 2020
Provisional Application 63123531 · Dec 10, 2020
Provisional Application 63024383 · May 13, 2020
Provisional Application 62986444 · Mar 6, 2020
Provisional Application 62911249 · Oct 5, 2019
Provisional Application 62911248 · Oct 5, 2019
Provisional Application 62903462 · Sep 20, 2019
Related Publication 20230298403A1 · Sep 21, 2023
Cited By (8)
US 12,244,464 US 12,261,747 US 12,403,921 US 12,413,552 US 12,415,479 US 12,528,442 US 12,573,245 US 12,710,956