Drive event capturing based on geolocation
First Claim
Patent Images
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.
8 Assignments
0 Petitions
Accused Products
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.
152 Citations
23 Claims
-
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. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21)
-
-
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 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; determining 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, assigning the possible drive event as a non-event; capturing driving data from the one or more onboard sensors wherein capturing driving data includes causing storage of driving data associated with the drive event; scoring 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 moving 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 threshold, uploading less detail of the driving data associated with the drive event to the remote server.
-
-
23. A computer program product for drive event capturing based on geolocation, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions 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; 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 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 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 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; determining 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, assigning the possible drive event as a non-event; capturing driving data from the one or more onboard sensors wherein capturing driving data includes causing storage of driving data associated with the drive event; scoring 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 threshold, uploading less detail of the driving data associated with the drive event to the remote server.
-
Specification