IP Library Granted Patent US 10,445,954
Granted Patent B2
US 10,445,954 · App. 15/047,498 · Granted Oct 15, 2019

Drive event capturing based on geolocation

Inventors: Roni Tamari (San Diego, CA); Joshua Donald Botnen (San Diego, CA)
Assignee: Lytx, Inc.
G07C5/085G06F11/3013G06F11/3058G06F11/3072G08G1/0112G08G1/0129G08G1/0133G08G1/0141G08G1/123G08G1/20
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,445,954
App. No.
15/047,498
Granted
Oct 15, 2019
Kind
B2
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 (48)

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.

Assignments (2)
NOTICE OF SUCCESSOR AGENT AND ASSIGNMENT OF SECURITY INTEREST (PATENTS) REEL/FRAME 043745/0567 Recorded Feb 28, 2020
From: HPS INVESTMENT PARTNERS, LLC
To: GUGGENHEIM CREDIT SERVICES, LLC
Reel/Frame 052050/0115 →
SECURITY INTEREST Recorded Aug 31, 2017
From: LYTX, INC.
To: HPS INVESTMENT PARTNERS, LLC, AS COLLATERAL AGENT
Reel/Frame 043745/0567 →
Continuity (2)
Continuation 13271417 · Oct 12, 2011
Related Publication 20160335814A1 · Nov 17, 2016