Server determined bandwidth saving in transmission of events

• US 9,761,064 B2
• Filed: 06/22/2015
• Issued: 09/12/2017
• Est. Priority Date: 01/08/2013
• Status: Active Grant

• Current Assignee: Lytx, Inc.
• Original Assignee: Lytx, Inc.
• Inventors: Lambert, Daniel, Botnen, Joshua Donald
• Primary Examiner(s): Amin, Bhavesh V
• Application Number:
  US14/746,572
• Publication Number:
  US 20150287248A1
• Time in Patent Office: 813 Days
• CPC Class Codes: G07C 5/008 communicating information to a remotely located station transmission systems for measured values G08C
• CPC Class Codes: G07C 5/08 Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time

Abstract

A system for receiving a driving event comprises an interface and a processor. An interface is configured to receive a portion of data regarding a driving event. A processor is configured to determine whether more data regarding the driving event should be requested and, in the event that more data regarding the driving event should be requested, request more data regarding the driving event.

Claims

1. A system for receiving a driving event, comprising:

a communications interface configured to receive a portion of data regarding a driving event from a remote vehicle event recorder attached to a vehicle; and

a processor remote from the vehicle event recorder, the processor being configured to;

determine whether more data regarding the driving event should be requested from the vehicle event recorder;

in the event that more data regarding the driving event should be requested, request more data from the vehicle event recorder regarding the driving event;

determine whether the driving event satisfies a non-transmitting criteria; and

in the event that the driving event does not satisfy a non-transmitting criteria, send to the vehicle event recorder an indication to mark that the driving event has been checked against an exception database.

2. A system as in claim 1, wherein the processor is further configured to, in the event that the driving event does not satisfy a non-transmitting criteria, send to the vehicle event recorder an indication to mark the driving event with an indication of a version of the exception database.

3. A system as in claim 1, wherein the processor is further configured to compare the driving event to an exception indication and the determination of whether the driving event satisfies a non-transmitting criteria is based at least in part on the comparison of the driving event to the exception indication.

4. A system as in claim 3, further comprising a memory configured to store the exception indication, wherein the exception indication is based on a location-specific legal data.

5. A system as in claim 4, wherein the location-specific legal data comprises at least one of the following:

a speed limit error, a stop sign error, a parking zone error, and a railroad crossing error.

6. A system as in claim 1, wherein the processor is further configured to check customer-specific event exceptions and the determination of whether more data regarding the driving event should be requested is based at least in part on the checking the customer-specific event exceptions.

7. A system as in claim 1, wherein the processor is further configured to check customer-specific region exceptions and the determination of whether more data regarding the driving event should be requested is based at least in part on the checking the customer-specific region exceptions.

8. A system as in claim 1, wherein the processor is further configured to check location-specific legal information exceptions, and the determination of whether more data regarding the driving event should be requested is based at least in part on the checking location-specific legal information exceptions.

9. A system as in claim 1, wherein the processor is further configured to:

in the event that more data regarding the driving event should not be requested;

send to the vehicle event recorder an indication to indicate that the event is to be deleted.

10. A system as in claim 1, wherein the processor is further configured to:

in the event that more data regarding the driving event should not be requested;

send to the vehicle event recorder an indication to indicate that the event is to be soft deleted.

11. A system as in claim 1, wherein the processor is further configured to:

in the event that more data regarding the driving event should not be requested;

send to the vehicle event recorder an indication to indicate that the event is to be marked as not transmitted.

12. A system as in claim 1, wherein the processor is further configured to:

in the event that more data regarding the driving event should not be requested;

send to the vehicle event recorder an indication to indicate that the event is to be marked as deleted.

13. A system as in claim 1, wherein the more data from the vehicle event recorder regarding the driving event includes video information or still picture information.

14. A system as in claim 1, wherein the processor is further configured to determine a current segment.

15. A system as in claim 1, wherein the processor is further configured to determine subsegment information.

16. A method comprising:

receiving a portion of data regarding a driving event from a remote vehicle event recorder attached to a vehicle;

determining whether more data regarding the driving event should be requested from the vehicle event recorder;

in the event that more data regarding the driving event should be requested, requesting more data from the vehicle event recorder regarding the driving event;

determining whether the driving event satisfies a non-transmitting criteria; and

in the event that the driving event does not satisfy a non-transmitting criteria, sending to the vehicle event recorder an indication to mark that the driving event has been checked against an exception database.

17. A computer program product embodied in a non-transitory computer readable storage medium and comprising computer instructions for:

receiving a portion of data regarding a driving event from a remote vehicle event recorder attached to a vehicle;

determining whether more data regarding the driving event should be requested from the vehicle event recorder;

in the event that more data regarding the driving event should be requested, requesting more data from the vehicle event recorder regarding the driving event;

determining whether the driving event satisfies a non-transmitting criteria; and

in the event that the driving event does not satisfy a non-transmitting criteria, sending to the vehicle event recorder an indication to mark that the driving event has been checked against an exception database.