US 12,450,959 B2
Systems and methods for managing vehicle data
Evangelos Simoudis, Menlo Park, CA (US)
Assigned to Synapse Partners, LLC, Menlo Park, CA (US)
Filed by Synapse Partners, LLC, Menlo Park, CA (US)
Filed on Apr. 25, 2024, as Appl. No. 18/646,539.
Application 18/646,539 is a continuation of application No. 16/983,478, filed on Aug. 3, 2020, granted, now 12,002,309.
Application 16/983,478 is a continuation of application No. PCT/US2019/060094, filed on Nov. 6, 2019.
Claims priority of provisional application 62/875,919, filed on Jul. 18, 2019.
Claims priority of provisional application 62/852,769, filed on May 24, 2019.
Claims priority of provisional application 62/799,697, filed on Jan. 31, 2019.
Claims priority of provisional application 62/757,517, filed on Nov. 8, 2018.
Prior Publication US 2024/0290148 A1, Aug. 29, 2024
Int. Cl. G07C 5/08 (2006.01); B60K 35/00 (2006.01); B60W 60/00 (2020.01); G06F 16/2457 (2019.01); G06N 5/02 (2023.01); G06N 5/04 (2023.01); G06N 20/00 (2019.01); G07C 5/00 (2006.01)
CPC G07C 5/085 (2013.01) [B60K 35/00 (2013.01); B60W 60/001 (2020.02); G06F 16/24573 (2019.01); G06N 5/02 (2013.01); G06N 5/04 (2013.01); G06N 20/00 (2019.01); G07C 5/008 (2013.01)] 17 Claims
OG exemplary drawing
 
1. A data orchestrator for managing vehicle data for a vehicle, comprising:
a data storage unit storing (i) application data related to one or more applications that generate one or more subsets of said vehicle data, and (ii) entity data related to one or more remote entities that request said one or more subsets of said vehicle data, wherein said data storage unit is local to said vehicle where said vehicle data is collected or generated;
a database, local to said vehicle and accessible to the data orchestrator, and configured as a knowledge base storing a machine learning-based predictive model, trained and tested using metadata and said vehicle data, and user-defined rules for determining a data transmission rule comprising at least one of: (i) a selected portion of said vehicle data to be transmitted; (ii) a timing for transmitting said selected portion of said vehicle data; and (iii) a remote entity of said one or more remote entities that is designated to receive said selected portion of said vehicle data, wherein (a) said vehicle data comprises sensor data processed by a pipeline engine, (b) said metadata is generated from said sensor data, and (c) wherein additional metadata is generated when said vehicle data is processed by said pipeline engine; and
a transmission module configured to transmit said selected portion of said vehicle data based at least in part on said application data, said entity data, and said data transmission rule.