Drive event capturing based on geolocation

Patent metadata

Field	Value
Publication number	US-9298575-B2
Application number	US-201113271417-A
Country	US
Kind code	B2
Filing date	Oct 12, 2011
Priority date	Oct 12, 2011
Publication date	Mar 29, 2016
Grant date	Mar 29, 2016

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.

First claim

What is claimed is:

1. A system for drive event capturing based on geolocation, comprising:
an interface for receiving driving data from one or more onboard sensors of a vehicle, wherein one of the onboard sensors of the vehicle includes an accelerometer, wherein the one or more onboard sensors of the vehicle further comprises a video data capture device;
a processor configured to:
receive geolocation data of the vehicle;
determine geolocation based criteria for detecting drive events based on the received geolocation data of the vehicle, wherein the geolocation based criteria comprises a set of sensor criteria specifically tuned for a particular geolocation to determine whether the driving data represents one of many possible drive events, wherein each possible drive event is represented by a drive event profile, wherein the geolocation based criteria further comprises: different sensitivities of sensors for triggering detection of drive events based on the geolocation data of the vehicle, and different deceleration thresholds for triggering detection of drive events based on sensor data from the accelerometer and geolocation data;
detect a drive event based on the geolocation based criteria, wherein detecting the drive event further comprises filtering out non-events using a geolocation based non-event profile, wherein the filtering out of the non-events comprises:
determine a geolocation of a possible drive event;
determine whether the geolocation of the possible drive event corresponds with a geolocation of a known object stored in a database, the database including known objects and corresponding geolocations; and
in the event that the geolocation of the possible drive event corresponds with the geolocation of the known object:
determine whether a profile of the possible drive event matches a non-event profile associated with the known object based on the sensor data; and
in the event that the profile of the possible drive event matches the non-event profile associated with the known object, assign the possible drive event as a non-event;

capture driving data from the one or more onboard sensors, wherein capturing driving data includes causing storage of driving data associated with the drive event;
score the drive event based on the determined geolocation based criteria, wherein the score indicates a severity of the drive event and is adjusted based on the geolocation of the vehicle;
determine whether the driving data is to be uploaded to a remote server based on the score;
in the event that the score of the drive event is below a pre-defined threshold, upload less detail of the driving data associated with the drive event to the remote server; and
a memory coupled to the processor and configured to provide the processor with instructions.

2. The system of claim 1 , wherein the drive event includes a vehicle collision drive event.

3. The system of claim 1 , wherein the geolocation of the vehicle is represented using a set of geographic coordinates of the vehicle.

4. The system of claim 1 , wherein a start of the drive event is detected based at least in part on the geolocation based criteria.

5. The system of claim 1 , wherein an end of the drive event is detected based at least in part on the geolocation based criteria.

6. The system of claim 1 , wherein the geolocation based criteria reflects the effect of geolocation on whether the driving data represents a true drive event of interest.

7. The system of claim 1 , wherein the non-event profile associated with the known object is a pot-hole profile experienced by a moving vehicle.

8. The system of claim 1 , wherein the non-event profile associated with the known object is a speed bump profile experienced by a moving vehicle.

9. The system of claim 1 , wherein the non-event profile associated with the known object is a bumpy road profile experienced by a moving vehicle.

10. The system of claim 1 , further comprising in the event that the score of the drive event is above the pre-defined threshold, upload complete detail of the driving data associated with the drive event from a volatile memory buffer to a persistent storage on the remote server.

11. The system of claim 1 , wherein the one or more onboard sensors comprises one or more of the following: an image capturing device, a global positioning system (GPS) receiver, a vehicle operation state sensor, a speedometer, and a gyroscope.

12. The system of claim 1 , wherein capturing the drive event includes capturing a portion of pre-event driving data, a portion of during-event driving data, and a portion of post-event driving data.

13. The system as in claim 1 , wherein different sensitivities for sensors comprises adjusting one or more of the following: a gain of the sensors, attenuation of the sensors, or bandwidth of the sensors.

14. The system as in claim 1 , wherein the geolocation based criteria determines a drive event using the driving data and a frequency of stops.

15. The system as in claim 1 , wherein the geolocation based criteria determines a drive event using the driving data and a frequency of turns.

16. The system as in claim 1 , wherein the geolocation based criteria determines a drive event using the driving data and a sharpness of turns.

17. The system as in claim 1 , wherein a deceleration threshold is higher for a geolocation where a road is bumpy.

18. The system as in claim 1 , wherein the geolocation based criterion is determined using the database that associates geolocation based criteria with a geo-fenced zone, wherein the geo-fenced zone is a geographical area on a digital map defined by a geo-boundary.

19. The system as in claim 1 , wherein the geolocation based criteria comprises higher sensor sensitivity for a known risky intersection.

20. The system as in claim 1 , wherein the geolocation based criteria comprises lower sensor sensitivity for the vehicle being in a company yard.

21. The system of claim 1 , wherein the database includes a digital map.

22. A method for drive event capturing based on geolocation, comprising:
receiving driving data from one or more onboard sensors of a vehicle, wherein one of the onboard sensors of the vehicle includes an accelerometer, wherein the one or more onboard sensors of the vehicle further comprises a video data capture device;
receiving geolocation data of the vehicle;
determining geolocation based criteria for detecting drive events based on the received geolocation data of the vehicle, wherein the geolocation based criteria comprises a set of sensor criteria specifically tuned for a particular geolocation to determine whether the driving data represents one of many possible drive events, wherein each possible drive event is represented by a drive event profile, wherein the geolocation based criteria further comprises: different sensitivities of sensors for triggering detection of drive events based on the geolocation data of the vehicle, and different deceleration thresholds for triggering detection of drive events based on sensor data from the accelerometer and geolocation data;
detecting a drive event based on the determined geolocation based criteria, wherein detecting the drive event further comprises filtering out non-events using a geolocation based non-event profile, wherein the filtering out of the non-events comprises:
determining a geolocation of a possible drive event;
determining whether the geolocation of the possible drive event corresponds with a geolocation of a known

Assignees

• Tamari Roni
• Botnen Joshua Donald
• Lytx Inc

Inventors

• Tamari Roni
• Botnen Joshua Donald

Classifications

• G08G1/0112

  from the vehicle, e.g. floating car data [FCD] · CPC title

• G08G1/0129

  for creating historical data or processing based on historical data · CPC title

• G06F11/3013 Primary

  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 title

• G08G1/20

  Monitoring the location of vehicles belonging to a group, e.g. fleet of vehicles, countable or determined number of vehicles · CPC title

• G08G1/0133

  for classifying traffic situation · CPC title