Data collection policy management for vehicle sensor data

1 . A computer program product, the computer program product being tangibly embodied on a non-transitory computer-readable storage medium and comprising instructions that, when executed by at least one computing device, are configured to cause the at least one computing device to:

receive a policy file, over an external network, at a vehicle outfitted with a plurality of sensors, the policy file governing a policy for capturing and uploading sensor data from at least one of the plurality of sensors characterizing a driving event of the vehicle, wherein the policy file is a configuration file that defines policy parameters for capturing and uploading sensor data;

execute an over the air (OTA) update of a policy manager installed at the vehicle to install the policy file, wherein the policy manager is an application-layer software module that parses the policy file and dynamically applies the policy parameters to control operations of an event manager, a recorder, and an uploader, the policy manager being configured to analyze the sensor data to detect and capture a subset of the sensor data related to the driving event, using the event manager and based on the policy file;

record the subset of the sensor data in an event file using the recorder and based on the policy file; and

upload the event file to the external network, using the uploader and based on the policy file.

2 . The computer program product of claim 1 , wherein the instructions, when executed, are configured to cause the at least one computing device to:

store the sensor data in at least one random access memory (RAM).

3 . The computer program product of claim 2 , wherein the instructions, when executed, are configured to cause the at least one computing device to:

store the sensor data in a circular buffer having a maximum size; and

delete oldest-stored sensor data from the circular buffer when the maximum size is reached and new sensor data is added.

4 . The computer program product of claim 2 , wherein the instructions, when executed, are configured to cause the at least one computing device to:

detect a recording trigger, based on the policy file, that initiates recording of the subset of sensor data from the RAM to a second memory.

5 . The computer program product of claim 4 , wherein the instructions, when executed, are configured to cause the at least one computing device to:

select, in response to the recording trigger and based on the policy file, at least one sensor from which to record the subset of sensor data; and

designate a start time and end time of recording of the subset of sensor data.

6 . The computer program product of claim 5 , wherein the instructions, when executed, are configured to cause the at least one computing device to:

designate the start time as occurring prior to the recording trigger;

capture, from the RAM, a first portion of the subset of sensor data recorded prior to the recording trigger; and

capture a second portion of the subset of sensor data recorded in the RAM after the recording trigger, until the end time is reached.

7 . The computer program product of claim 4 , wherein the instructions, when executed, are configured to cause the at least one computing device to:

identify the recording trigger as including a sensor value of a first sensor of the plurality of sensors;

identify, in response to the recording trigger and based on the policy file, at least a second sensor of the plurality of sensors; and

include sensor data from the first sensor and the at least the second sensor within the subset of sensor data.

8 . The computer program product of claim 2 , wherein the instructions, when executed, are configured to cause the at least one computing device to:

store first sensor data of a first sensor type from a first sensor at a first location within the RAM that is designated for the first sensor at a start of the vehicle; and

store second sensor data of a second sensor type from a second sensor at a second location within the RAM that is designated for the second sensor type at the start of the vehicle.

9 . The computer program product of claim 1 , wherein the instructions, when executed, are configured to cause the at least one computing device to:

classify the subset of sensor data as an event type, based on the policy file.

10 . The computer program product of claim 1 , wherein the instructions, when executed, are configured to cause the at least one computing device to:

compress the subset of sensor data, based on the policy file;

designate the compressed subset of sensor data within an upload queue, based on the policy file; and

upload the compressed subset of sensor data to the external network, based on the upload queue.

11 . A computer-implemented method, comprising:

receiving a policy file, over an external network, at a vehicle outfitted with a plurality of sensors, the policy file governing a policy for capturing and uploading sensor data from at least one of the plurality of sensors characterizing a driving event of the vehicle, wherein the policy file is a configuration file that defines policy parameters for capturing and uploading sensor data;

executing an over the air (OTA) update of a policy manager installed at the vehicle to install the policy file, wherein the policy manager is an application-layer software module that parses the policy file and dynamically applies the policy parameters to control operations of an event manager, a recorder, and an uploader, the policy manager being configured to analyze the sensor data to detect and capture a subset of the sensor data related to the driving event, using the event manager and based on the policy file;

recording the subset of the sensor data in an event file using the recorder and based on the policy file; and

uploading the event file to the external network, using the uploader and based on the policy file.

12 . The method of claim 11 , comprising:

storing the sensor data in at least one random access memory (RAM).

13 . The method of claim 12 , comprising:

storing the sensor data in a circular buffer having a maximum size; and

deleting oldest-stored sensor data from the circular buffer when the maximum size is reached and new sensor data is added.

14 . The method of claim 12 , comprising:

detecting a recording trigger, based on the policy file, that initiates recording of the subset of sensor data from the RAM to a second memory.

15 . The method of claim 14 , comprising:

selecting, in response to the recording trigger and based on the policy file, at least one sensor from which to record the subset of sensor data; and

designating a start time and end time of recording of the subset of sensor data.

16 . The method of claim 15 , comprising:

designating the start time as occurring prior to the recording trigger;

capturing, from the RAM, a first portion of the subset of sensor data recorded prior to the recording trigger; and

capturing a second portion of the subset of sensor data recorded in the RAM after the recording trigger, until the end time is reached.

17 . The method of claim 14 , comprising:

identifying the recording trigger as including a sensor value of a first sensor of the plurality of sensors;

identifying, in response to the recording trigger and based on the policy file, at least a second sensor of the plurality of sensors; and

including sensor data from the first sensor and the at least the second sensor within the subset of sensor data.

18 . A vehicle comprising:

a chassis;

a frame mounted on the chassis;

a motor mounted within the frame;

a plurality of sensors mounted on the vehicle;

at least one memory including instructions; and

at least one processor that is operably coupled to the at least one memory and that is arranged and configured to execute instructions that, when executed, cause the at least one processor to:

receive a policy file, over an external network, at a vehicle outfitted with a plurality of sensors, the policy file governing a policy for capturing and uploading sensor data from at least one of the plurality of sensors characterizing a driving event of the vehicle, wherein the policy file is a configuration file that defines policy parameters for capturing and uploading sensor data;

execute an over the air (OTA) update of a policy manager installed at the vehicle to install the policy file, wherein the policy manager is an application-layer software module that parses the policy file and dynamically applies the policy parameters to control operations of an event manager, a recorder, and an uploader, the policy manager being configured to analyze the sensor data to detect and capture a subset of the sensor data related to the driving event, using the event manager and based on the policy file;

record the subset of the sensor data in an event file using the recorder and based on the policy file; and

upload the event file to the external network, using the uploader and based on the policy file.

19 . The vehicle of claim 18 , wherein the instructions, when executed by the at least one processor, cause the at least one processor to:

detect a recording trigger, based on the policy file, that initiates recording of the subset of sensor data from a random access memory (RAM) to a second memory;

select, in response to the recording trigger and based on the policy file, at least one sensor from which to record the subset of sensor data; and

designate a start time and end time of recording of the subset of sensor data.

20 . The vehicle of claim 19 , wherein the instructions, when executed by the at least one processor, cause the at least one processor to:

designate the start time as occurring prior to the recording trigger;

capture, from the RAM, a first portion of the subset of sensor data recorded prior to the recording trigger; and

capture a second portion of the subset of sensor data recorded in the RAM after the recording trigger, until the end time is reached.