IP Library Granted Patent US 9,792,319
Granted Patent B2
US 9,792,319 · App. 14/998,044 · Granted Oct 17, 2017

System and method for identifying non-event profiles

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 9,792,319
App. No.
14/998,044
Granted
Oct 17, 2017
Kind
B2
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 (28)

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.

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 →