Computer platform for development and deployment of sensor data based applications and services
US-10216485-B2 · Feb 26, 2019 · US
US12116013B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12116013-B2 |
| Application number | US-202017131175-A |
| Country | US |
| Kind code | B2 |
| Filing date | Dec 22, 2020 |
| Priority date | Dec 22, 2020 |
| Publication date | Oct 15, 2024 |
| Grant date | Oct 15, 2024 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A system for a distributed in-vehicle real-time sensor data processing can be adapted to receive a request for sensor data from vehicles. The system may be further adapted to generate an application for collection of the sensor data. The application may have sensor requirements for performing the collection of sensor data. The system may be further adapted to identify a set of vehicles for distribution of the application based on available sensors in each vehicle corresponding to the sensor requirements. The system may be further adapted to transmit the application to the set of vehicles and receive sensor data results from respective instances of the application executing on the set of vehicles. The system may be further adapted to transmit a command to remove the respective instances of the application from the set of vehicles.
Opening claim text (preview).
What is claimed is: 1. A system for distributed in-vehicle sensor data processing comprising: at least one processor; and memory configured to store instructions thereon that, when executed by the at least one processor, cause the at least one processor to: receive a request from a third party for sensor data from a set of vehicles, wherein the request specifies one or more sensor requirements including types of data to be collected and types of sensors required to collect the types of data; generate an application for collection of the sensor data, wherein the application is configured and customized based on the specified one or more sensor requirements to utilize one or more specific sensors available in the set of vehicles, wherein the set of vehicles is identified for distribution of the application based on a compatibility of the one or more specific sensors available in each vehicle with the the one or more sensor requirements; transmit the application to the set of vehicles; receive sensor data from the one or more specific sensors from respective instances of the application executing on the set of vehicles; and transmit a command to remove the respective instances of the application from the set of vehicles. 2. The system of claim 1 , wherein the request includes a location or a time of day for sensor data collection. 3. The system of claim 2 , wherein identifying the set of vehicles is based on a location of each vehicle corresponding to the location of the request. 4. The system of claim 2 , further comprising instructions to: determine a schedule for execution of the application based on the time of day for collection of the sensor data from the request; and transmit the schedule for execution of the application to the set of vehicles. 5. The system of claim 1 , further comprising instructions to: determine a priority for the application; and transmit the priority for the application to the set of vehicles, wherein the priority is defined based on present vehicle priorities. 6. The system of claim 1 , further comprising instructions to: transform the received sensor data to a common format; validate that the received sensor data corresponds to the request for sensor data; and transmit sensor data results to a data consumer. 7. The system of claim 6 , wherein validating the sensor data results includes using data heuristics for validation. 8. The system of claim 6 , wherein validating the sensor data results includes verifying the sensor data results comply with a privacy policy. 9. The system of claim 1 , wherein the request includes a duration for the collection of the sensor data. 10. The system of claim 1 , further comprising instructions to present, on a display, the sensor data results in a user interface. 11. At least one non-transitory machine-readable medium configured to store instructions for distributed in-vehicle sensor data processing stored thereon, the instructions when executed by a machine, cause the machine to perform operations comprising: receiving a request from a third party for sensor data from a set of vehicles, wherein the request specifies one or more sensor requirements including types of data to be collected and types of sensors required to collect the types of data; generating an application for collection of the sensor data, wherein the application is configured and customized based on the specified one or more sensor requirements to utilize one or more specific sensors available in the set of vehicles, wherein the set of vehicles is identified for distribution of the application based on a compatibility of the one or more specific sensors available in each vehicle with the one or more sensor requirements; transmitting the application to the set of vehicles; receiving sensor data results from respective instances of the application executing on the set of vehicles; and transmitting a command to remove the respective instances of the application from the set of vehicles. 12. The at least one non-transitory machine-readable medium of claim 11 , wherein the request includes a location or a time of day for sensor data collection. 13. The at least one non-transitory machine-readable medium of claim 12 , wherein identifying the set of vehicles is based on a location of each vehicle corresponding to the location of the request. 14. The at least one non-transitory machine-readable medium of claim 12 , the operations further comprising: determining a schedule for execution of the application based on the time of day for collection of the sensor data from the request; and transmitting the schedule for execution of the application to the set of vehicles. 15. The at least one non-transitory machine-readable medium of claim 11 , the operations further comprising: determining a priority for the application; and transmitting the priority for the application to the set of vehicles, wherein the priority is defined based on present vehicle priorities. 16. The at least one non-transitory machine-readable medium of claim 11 , the operations further comprising: transforming the received sensor data to a common format; validating that the received sensor data correspond to the request for sensor data; and transmitting sensor data results to a data consumer. 17. The at least one non-transitory machine-readable medium of claim 16 , wherein validating the sensor data results includes using data heuristics for validation. 18. The at least one non-transitory machine-readable medium of claim 16 , wherein validating the sensor data results includes verifying the sensor data results comply with a privacy policy. 19. The at least one non-transitory machine-readable medium of claim 11 , wherein the request includes a duration for the collection of the sensor data. 20. The at least one non-transitory machine-readable medium of claim 11 , the operations further comprising presenting, on a display, the sensor data results in a user interface. 21. A system for distributed in-vehicle sensor data processing, the system comprising: means for receiving a request for sensor data from a set of vehicles, wherein the request specifies one or more sensor requirements including types of data to be collected and types of sensors required to collect the types of data; means for generating an application for collection of the sensor data, wherein the application is configured and customized based on the specified one or more sensor requirements to utilize one or more specific sensors available in the set of vehicles, wherein the set of vehicles is identified for distribution of the application based on a compatibility of the one or more specific sensors available in each vehicle with the one or more the sensor requirements; means for transmitting the application to the set of vehicles; means for receiving sensor data from the one or more specific sensors from respective instances of the application executing on the set of vehicles; and means for transmitting a command to remove the respective instances of the application from the set of vehicles.
Radar; Laser, e.g. lidar · CPC title
Image sensing, e.g. optical camera · CPC title
indicating the position of vehicles, e.g. scheduled vehicles; {Managing passenger vehicles circulating according to a fixed timetable, e.g. buses, trains, trams}(transmission of navigation instructions to vehicles G08G1/0968) · CPC title
Display means · CPC title
Audio sensitive means, e.g. ultrasound · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.