Systems and methods for remotely controlling data collection by a vehicle

• US 10,210,672 B2
• Filed: 04/07/2017
• Issued: 02/19/2019
• Est. Priority Date: 04/07/2017
• Status: Active Grant

• Current Assignee: Toyota Jidosha Kabushiki Kaisha (Toyota Motor Corporation)
• Original Assignee: Toyota Research Institute, Inc. (Toyota Motor Corporation)
• Inventors: James, Michael R., Olson, Edwin B.
• Primary Examiner(s): Lee, Tyler J
• Application Number:
  US15/481,818
• Publication Number:
  US 20180293809A1
• Time in Patent Office: 683 Days
• CPC Class Codes: B60R 16/0232 for measuring vehicle parameters and indicating critical, abnormal or dangerous conditions
• CPC Class Codes: G07C 5/008 communicating information to a remotely located station transmission systems for measured values G08C
• CPC Class Codes: G07C 5/085 using electronic data carriers
• CPC Class Codes: H04L 67/025 for remote control or remote monitoring of applications
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network
• CPC Class Codes: H04W 4/38 for collecting sensor information
• CPC Class Codes: H04W 4/44 for communication between vehicles and infrastructures, e.g. vehicle-to-cloud [V2C] or vehicle-to-home [V2H]
• CPC Class Codes: H04W 4/70 Services for machine-to-machine communication [M2M] or machine type communication [MTC]

Abstract

System, methods, and other embodiments described herein relate to controlling a vehicle to selectively collect event data. In one embodiment, a method includes, in response to receiving a collection request from a remote server, identifying defined parameters from the collection request about which data is to be harvested from the vehicle. The defined parameters include at least a content parameter that indicates criteria for determining which data associated with the vehicle is to be collected. The method includes collecting, from one or more vehicle systems of the vehicle, event data as a function of the content parameter and discarding extraneous data that does not match the content parameter. The method includes providing the event data to fulfill the collection request.

Claims

1. A collection system for collecting information from a vehicle, comprising:

one or more processors;

a memory communicably coupled to the one or more processors and storing;

a communication module including instructions that when executed by the one or more processors cause the one or more processors to, in response to receiving a collection request from a remote server, identify defined parameters from the collection request about which data is to be harvested from the vehicle, wherein the defined parameters include at least a content parameter that indicates criteria for determining which data associated with the vehicle is to be collected; and

a filter module including instructions that when executed by the one or more processors cause the one or more processors to collect, from one or more vehicle systems of the vehicle, event data as a function of the content parameter and discarding extraneous data that does not match the content parameter wherein the defined parameters further specify a trigger event that indicates when the event data that matches the content parameter is to be collected, wherein the filter module includes instructions to buffer, in an incident buffer, preliminary data from the vehicle prior to detection of the trigger event for a defined period of time before cycling additional data into the incident buffer, and,

wherein the communication module includes instructions to provide the event data to fulfill the collection request.

2. The collection system of claim 1,

wherein the filter module further includes instructions to collect the event data by querying one or more sensors of the vehicle to activate and provide data about the trigger event.

3. The collection system of claim 2, wherein the filter module includes instructions to detect the trigger event by monitoring the one or more vehicle systems according to filters that define the trigger event and by scanning a data stream for information matching an occurrence of the trigger event.

4. The collection system of claim 2, wherein the incident buffer is a first-in-first-out buffer, and wherein the filter module further includes instructions to buffer the preliminary data to avoid discarding information associated with the trigger event that occurs prior to the trigger event.

5. The collection system of claim 1, wherein the defined parameters indicate a termination parameter that specifies when to stop collecting the event data for a trigger event, and wherein the termination parameter indicates one or more of:

(i) a period of time for which to collect the event data, and

(ii) a quantity of the event data to collect prior to providing the event data.

6. The collection system of claim 1, wherein the communication module further includes instructions to identify the defined parameters by parsing the collection request to retrieve the defined parameters and to configure a filter of the vehicle with the defined parameters.

7. The collection system of claim 1, wherein the filter module further includes instructions to collect the event data by collecting nominal data about processes and communications between processes executing within the one or more vehicle systems, and

wherein the filter module further includes instructions to collect the event data by storing the event data in a local memory of the vehicle, and wherein the defined parameters are filter controls that comprise a software package.

8. The collection system of claim 1, wherein the communication module further includes instructions to provide the event data by wirelessly communicating the event data to the remote server upon fulfillment of the collection request, and

wherein the filter module includes instructions to, in response to the collection request, configure and monitor filters at different hook points within the vehicle to collect the event data associated with the content parameters while avoiding collection of unrelated data.

9. A non-transitory computer-readable medium storing instructions that when executed by one or more processors cause the one or more processors to:

in response to receiving a collection request from a remote server, identify defined parameters from the collection request about which data is to be harvested from a vehicle, wherein the defined parameters include at least a content parameter that indicates criteria for determining which data associated with the vehicle is to be collected;

collect, from one or more vehicle systems of the vehicle, event data as a function of the content parameter and discarding extraneous data that does not match the content parameter, wherein the defined parameters further specify a trigger event that indicates when the event data that matches the content parameter is to be collected;

buffer, in an incident buffer, preliminary data from the vehicle prior to detection of the trigger event for a defined period of time before cycling additional data into the incident buffer, and;

provide the event data to fulfill the collection request.

10. The non-transitory computer-readable medium of claim 9,

wherein the instructions to collect the event data include instructions to query one or more sensors of the vehicle to activate and provide data about the trigger event.

11. The non-transitory computer-readable medium of claim 10, wherein the instructions to detect the trigger event include instructions to monitor the one or more vehicle systems according to filters that define the trigger event and by scanning a data stream for information matching an occurrence of the trigger event.

12. The non-transitory computer-readable medium of claim 10, wherein the incident buffer is a first-in-first-out buffer,

and wherein the instructions to buffer the preliminary data avoid discarding information associated with the trigger event that occurs prior to the trigger event.

13. The non-transitory computer-readable medium of claim 9, wherein the instructions to collect the event data include instructions to collect nominal data about processes and communications between processes executing within the one or more vehicle systems, and

wherein the instructions to collect the event data include instructions to store the event data in a local memory of the vehicle, and wherein the defined parameters are filter controls that comprise a software package.

14. A method of collecting information from a vehicle, comprising:

in response to receiving a collection request from a remote server, identifying defined parameters from the collection request about which data is to be harvested from the vehicle, wherein the defined parameters include at least a content parameter that indicates criteria for determining which data associated with the vehicle is to be collected;

collecting, from one or more vehicle systems of the vehicle, event data as a function of the content parameter and discarding extraneous data that does not match the content parameter wherein the defined parameters further specify a trigger event that indicates when the event data that matches the content parameter is to be collected;

buffering, in an incident buffer, preliminary data from the vehicle prior to detection of the trigger event and for a defined period of time before cycling additional data into the incident buffer; and

providing the event data to fulfill the collection request.

15. The method of claim 14,

wherein collecting the event data includes querying one or more sensors of the vehicle to activate and provide data about the trigger event.

16. The method of claim 15, wherein detecting the trigger event includes monitoring the one or more vehicle systems according to filters that define the trigger event by scanning a data stream for information matching an occurrence of the trigger event.

17. The method of claim 15,

wherein the incident buffer is a first-in-first-out buffer that stores the preliminary data and, wherein buffering the preliminary data avoids discarding information associated with the trigger event that occurs prior to the trigger event.

18. The method of claim 14, wherein the defined parameters indicate a termination parameter that specifies when to stop collecting the event and data for a trigger event, wherein the termination parameter indicates one or more of:

(i) a period of time for which to collect the event data, and

(ii) a quantity of the event data to collect prior to providing the event data.

19. The method of claim 14, wherein identifying the defined parameters includes parsing the collection request to retrieve the defined parameters and configuring a filter of the vehicle with the defined parameters.

20. The method of claim 14, wherein collecting the event data includes collecting nominal data about processes and communications between processes executing within the one or more vehicle systems,

wherein providing the event data includes communicating the event data to the remote server upon fulfillment of the collection request,

wherein collecting the event data includes storing the event data in a local memory of the vehicle, and wherein the defined parameters are filter controls that comprise a software package.