SYSTEM AND METHOD FOR IDENTIFYING NON-EVENT PROFILES

• US 20130197774A1
• Filed: 01/08/2013
• Published: 08/01/2013
• Est. Priority Date: 05/08/2006
• Status: Active Grant

• Current Assignee: Lytx, Inc.
• Original Assignee: Lytx, Inc.
• Inventors: Denson, Craig
• Granted Patent: US 8,803,695 B2
• Time in Patent Office: Days
• US Class Current: 701/99
• CPC Class Codes: G06F 16/22 Indexing; Data structures therefor; Storage structures
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06F 16/2379 Updates performed during online database operations; commit processing
• CPC Class Codes: G07C 5/008 communicating information to a remotely located station transmission systems for measured values G08C
• CPC Class Codes: G07C 5/0808 Diagnosing performance data testing of vehicles G01M17/00; testing of electrical installation on vehicles G01R31/005
• CPC Class Codes: G07C 5/085 using electronic data carriers
• CPC Class Codes: G07C 5/0858 wherein the data carrier is removable
• CPC Class Codes: G08B 23/00 Alarms responsive to unspecified undesired or abnormal conditions

Abstract

A system for identifying non-events comprising an event capture device and one or more processors in communication with the event capture device. The event capture device is associated with a vehicle that captures driving event data. The one or more processors is configured to receive the captured driving event data; classify the captured driving event data as a non-event or driving event by comparing the captured driving event data to a non-event profile; in the event that the captured driving event data is classified as a non-event, store an abbreviated record of the captured driving event data.

Claims

1. A system for identifying non-events, comprising:

an event capture device associated with a vehicle that captures driving event data; and

one or more processors in communication with the event capture device configured to;

receive the captured driving event data;

classify the captured driving event data as a non-event or driving event by comparing the captured driving event data to a non-event profile;

in the event that the captured driving event data is classified as a non-event, store an abbreviated record of the captured driving event data.

2. The system of claim 1, wherein the one or more processors are further configured to:

in the event that the captured driving event data is classified as a driving event, store a driving event record of the captured driving event data.

3. The system of claim 2, wherein the driving event record comprises:

time information, speed information, location information, audio data, video data, and trigger data.

4. The system of claim 2, wherein the driving event record comprises one or more of the following:

vehicle status data comprising of one or more of engine or electrical component information, number of occupants information, seatbelt information, or airbag information.

5. The system of claim 2, wherein the abbreviated record has a smaller storage size than the driving event record.

6. The system of claim 1, wherein one of the one or more processors is co-located with an evaluation server.

7. The system of claim 1, wherein one of the one or more processors is not co-located with an evaluation server.

8. The system of claim 1, wherein the captured driving event data comprises one or more of the following:

video data, audio data, location information, time information, speed information, force data, g-force data, vehicle direction information, elevation information, temperature information, moisture information, vehicle engine and electrical component information, sensor information about the number of occupants in the vehicle, sensor information detecting whether seat belts were fastened, or sensor information detecting whether airbags were deployed.

9. The system of claim 1, wherein the non-event profile comprises a unique identifier and location information.

10. The system of claim 9, wherein the non-event profile further comprises trigger information used to trigger the capture of driving event data.

11. The system of claim 10, wherein the trigger information is force data.

12. The system of claim 1, wherein the abbreviated record comprises a unique identifier of a non-event profile that the captured driving event data corresponds to.

13. The system of claim 1, wherein the one or more processors are further configured to re-classify some driving events as a non-event, after reviewing the captured driving event data classified as a driving event.

14. The system of claim 13, wherein the one or more processors are further configured to create a non-event profile from the captured driving event data that is re-classified to be a non-event.

15. The system of claim 14, wherein the one or more processors are further configured to store the created non-event profile.

16. The system of claim 15, wherein the created non-event profile is stored on a memory in communication with the one or more processors.

17. The system of claim 16, wherein the created non-event profile is transmitted to the one or more processors that classifies driving events or non-events.

18. The system of claim 13, wherein the re-classifying of some driving events as a non-event is based at least in part on a captured vertical force value, wherein the vertical force value is along the “

Z”

axis.

19. The system of claim 1, wherein the one or more processors are configured to keep count of the number of times an abbreviated record corresponds to a specific non-event profile.

20. The system of claim 19, wherein the one or more processors are further comprised to create an avoidance record when the number of times an abbreviated record corresponds to a specific non-event profile exceeds a certain threshold.

21. The system of claim 1, wherein the non-event profile can expire and in the event that the non-event profile has expired, the non-event profile is not used.

22. The system of claim 1, wherein the one or more processors are further configured to generate plots of frequency or location data of classified driving events and non-events.

23. A method for identifying non-events, comprising:

receiving captured driving event data;

classifying, with one or more processors, the captured driving event data as a non-event or driving event by comparing the captured driving event data to a non-event profile;

in the event that the captured driving event data is classified as a non-event, storing an abbreviated record of the captured driving event data.

24. A computer program product for identifying non-events, the computer program product being embodied in a non-transitory computer readable medium and comprising computer instructions for:

receiving captured driving event data;

classifying the captured driving event data as a non-event or driving event by comparing the captured driving event data to a non-event profile;

in the event that the captured driving event data is classified as a non-event, storing an abbreviated record of the captured driving event data.