Drive event capturing based on geolocation

• US 10,445,954 B2
• Filed: 02/18/2016
• Issued: 10/15/2019
• Est. Priority Date: 10/12/2011
• Status: Active Grant

• Current Assignee: Lytx, Inc.
• Original Assignee: Lytx, Inc.
• Inventors: Tamari, Roni, Botnen, Joshua Donald
• Primary Examiner(s): Mott, Genna M
• Application Number:
  US15/047,498
• Publication Number:
  US 20160335814A1
• Time in Patent Office: 1,335 Days
• Field of Search: None
• CPC Class Codes: G06F 11/3013 where the computing system is an embedded system, i.e. a combination of hardware and software dedicated to perform a certain function in mobile devices, printers, automotive or aircraft systems testing or monitoring of control systems or parts thereof G05B23/02
• CPC Class Codes: G06F 11/3058 Monitoring arrangements for monitoring environmental properties or parameters of the computing system or of the computing system component, e.g. monitoring of power, currents, temperature, humidity, position, vibrations thermal management in cooling arrangements of a computing system G06F1/206
• CPC Class Codes: G06F 11/3072 where the reporting involves data filtering, e.g. pattern matching, time or event triggered, adaptive or policy-based reporting
• CPC Class Codes: G07C 5/085 using electronic data carriers
• CPC Class Codes: G08G 1/0112 from the vehicle, e.g. floating car data [FCD]
• CPC Class Codes: G08G 1/0129 for creating historical data or processing based on historical data
• CPC Class Codes: G08G 1/0133 for classifying traffic situation
• CPC Class Codes: G08G 1/0141 for traffic information dissemination
• CPC Class Codes: G08G 1/123 indicating the position of vehicles, e.g. scheduled vehicles; Managing passenger vehicles circulating according to a fixed timetable, e.g. buses, trains, tramstransmission of navigation instructions to vehicles G08G1/0968
• CPC Class Codes: G08G 1/20 Monitoring the location of vehicles belonging to a group, e.g. fleet of vehicles, countable or determined number of vehicles

Abstract

A system for drive event capturing based on geolocation comprises an interface and a processor. The interface receives driving data from one or more onboard sensors of a vehicle, and the processor is configured to capturing a drive event based on a geolocation of the vehicle. The capturing of the drive event includes causing storage of driving data associated with the drive event.

Claims

1. A system for classifying driving data based on geolocation, comprising:

an interface to receive a driving data from a sensor data device of a vehicle and a geolocation data of the vehicle;

a processor configured to;

determine whether the geolocation data corresponds to a geo-fenced zone that includes a geolocation of a stored non-event profile;

in response to determining that the geolocation data corresponds to the geo-fenced zone that includes the geolocation of the stored non-event profile;

determine an adjusted sensor sensitivity for capturing driving data that matches the stored non-event profile;

cause adjusting of a sensor sensitivity of the sensor data device to the adjusted sensor sensitivity;

receive during-event driving data associated with the geolocation using the adjusted sensor sensitivity;

receive the stored non-event profile from a data storage;

determine whether the during-event driving data matches the stored non-event profile;

in response to the during-event driving data matching the stored non-event profile, assign the during-event driving data as a non-event; and

in response to the during-event driving data not matching the stored non-event profile, indicate that the during-event driving data comprises an event of interest; and

a memory coupled to the processor and configured to provide the processor with instructions.

2. The system of claim 1, wherein the driving data comprises data collected from one or more of the following:

an image capturing device, a global positioning system (GPS) receiver, a vehicle operation state sensor, a speedometer, or a gyroscope.

3. The system of claim 1, wherein the processor is further configured to receive pre-event driving data associated with the geolocation using the adjusted sensor sensitivity, and post-event driving data associated with the geolocation using the adjusted sensor sensitivity.

4. The system of claim 1, wherein the processor is further configured to determine whether the driving data comprises a drive event based at least in part on a drive event criterion.

5. The system of claim 4, wherein the drive event comprises a vehicle collision drive event.

6. The system of claim 4, wherein the drive event criterion is based at least in part on the geolocation data.

7. The system of claim 4, wherein a deceleration threshold of the drive event criterion is adjusted based at least in part on the geolocation data.

8. The system as in claim 4, wherein the drive event criterion comprises a frequency of stops, a frequency of turns, or a sharpness of turns.

9. The system of claim 1, wherein adjusting the sensor sensitivity of the sensor data device comprises adjusting one or more of the following:

a gain of the sensor data device, an attenuation of the sensor data device, a bandwidth of the sensor data device, a detection threshold of the sensor data device, and a sensor cut-off filter frequency of the sensor data device.

10. The system of claim 1, wherein the stored non-event profile comprises a pot-hole profile, a speed bump profile, or a bumpy road profile.

11. The system as in claim 1, wherein the geo-fenced zone is a geographical area on a digital map defined by a geo-boundary.

12. The system of claim 1, wherein the processor is further configured to determine a drive score for the driving data based at least in part on the geolocation data, wherein the drive score comprises an indication of risk.

13. The system of claim 12, wherein the processor is further configured to determine whether the drive score is above a threshold.

14. The system of claim 12, wherein the processor is further configured to upload the driving data from a volatile memory buffer to a persistent storage on a remote server in a level of detail that is based at least in part on the drive score.

15. The system of claim 1, wherein the processor is further configured to upload the driving data from a volatile memory buffer to a persistent storage on a remote server.

16. A method for classifying driving data based on geolocation, comprising:

receiving a driving data from a sensor data device of a vehicle and a geolocation data of the vehicle;

determining, using a processor, whether the geolocation data corresponds to a geo-fenced zone that includes a geolocation of a stored non-event profile; and

in response to determining that the geolocation data corresponds to the geo-fenced zone that includes the geolocation of the stored non-event profile;

determining an adjusted sensor sensitivity for capturing driving data that matches the stored non-event profile;

causing adjusting of a sensor sensitivity of the sensor data device to the adjusted sensor sensitivity;

receiving during-event driving data associated with the geolocation using the adjusted sensor sensitivity;

receiving the stored non-event profile from a data storage;

determining whether the during-event driving data matches the stored the non-event profile;

in response to the during-event driving data matching the stored non-event profile, assigning the during-event driving data as a non-event; and

in response to the during-event driving data not matching the stored non-event profile, indicating that the during-event driving data comprises an event of interest.

17. A computer program product for classifying driving data based on geolocation, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for:

receiving a driving data from a sensor data device of a vehicle and a geolocation data of the vehicle;

determining whether the geolocation data corresponds to a geo-fenced zone that includes a geolocation of a stored non-event profile; and

in response to determining that the geolocation data corresponds to the geo-fenced zone that includes the geolocation of the stored non-event profile;

determining an adjusted sensor sensitivity for capturing driving data that matches the stored non-event profile;

causing adjusting of a sensor sensitivity of the sensor data device to the adjusted sensor sensitivity;

receiving during-event driving data associated with the geolocation using the adjusted sensor sensitivity;

receiving the stored non-event profile from a data storage;

determining whether the during-event driving data matches the stored non-event profile;

in response to the during-event driving data matching the stored non-event profile, assigning the during-event driving data as a non-event; and

in response to the during-event driving data not matching the stored non-event profile, indicating that the during-event driving data comprises an event of interest.