System and method for identifying non-event profiles

• US 9,792,319 B2
• Filed: 12/23/2015
• Issued: 10/17/2017
• Est. Priority Date: 05/08/2006
• Status: Active Grant

• Current Assignee: Lytx, Inc.
• Original Assignee: Lytx, Inc.
• Inventors: Denson, Craig
• Primary Examiner(s): MULLEN, THOMAS J
• Application Number:
  US14/998,044
• Publication Number:
  US 20160140163A1
• Time in Patent Office: 664 Days
• Field of Search: 340439, 340576, 701 324, 701 334, 701 36, 348148, 434 62
• 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 avoidance records comprises an interface and a processor. An interface is configured to receive an abbreviated record associated with a non-event profile identifier. A processor is configured to determine a counter value associated with the non-event profile identifier and, in the event that the counter value is greater than a predetermined threshold, create and store an avoidance record.

Claims

1. A system for identifying non-event profiles, comprising:

an interface to receive a driving event record;

a processor to;

determine whether a driving event associated with the driving event record is valid; and

in the event that the driving event is not valid, creating a non-event profile based at least in part on the driving event record.

2. A system as in claim 1, wherein the processor is further to, in the event that the driving event is not valid, send the non-event profile to event detectors.

3. A system as in claim 1, wherein the driving event record is received from an event detector.

4. A system as in claim 1, wherein the determination of whether a driving event associated with the driving event record is valid is based at least in part on GPS information.

5. A system as in claim 1, wherein the determination of whether a driving event associated with the driving event record is valid is based at least in part on a trigger force.

6. A system as in claim 1, wherein the processor is further to, in the event that the driving event is not valid, count a number of times the driving event record matches the non-event profile.

7. A method for identifying non-event profiles, comprising:

receiving a driving event record;

determining, using a processor, whether a driving event associated with the driving event record is valid; and

in the event that the driving event is not valid, creating a non-event profile based at least in part on the driving event record.

8. A method as in claim 7, further comprising in the event that the driving event is not valid, sending the non-event profile to event detectors.

9. A method as in claim 7, wherein the driving event record is received from an event detector.

10. A method as in claim 7, wherein the determination of whether a driving event associated with the driving event record is valid is based at least in part on GPS information.

11. A method as in claim 7, wherein the determination of whether a driving event associated with the driving event record is valid is based at least in part on a trigger force.

12. A method as in claim 7, further comprising in the event that the driving event is not valid, counting a number of times a driving event profile matches the non-event profile.

13. A computer program product for identifying non-event profiles, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for:

receiving a driving event record;

determining, using a processor, whether a driving event associated with the driving event record is valid; and

in the event that the driving event is not valid, creating a non-event profile based at least in part on the driving event record.

14. A computer program product recited in claim 13, further comprising computer instructions for in the event that the driving event is not valid, sending the non-event profile to event detectors.

15. A computer program product recited in claim 13, wherein the driving event record is received from an event detector.

16. A computer program product recited in claim 13, wherein the determination of whether a driving event associated with the driving event record is valid is based at least in part on GPS information.

17. A computer program product recited in claim 13, wherein the determination of whether a driving event associated with the driving event record is valid is based at least in part on a trigger force.

18. A computer program product recited in claim 13, further comprising computer instructions for in the event that the driving event is not valid, counting a number of times a driving event profile matches the non-event profile.