SERVER DETERMINED BANDWIDTH SAVING IN TRANSMISSION OF EVENTS

• US 20140195105A1
• Filed: 01/08/2013
• Published: 07/10/2014
• Est. Priority Date: 01/08/2013
• Status: Active Grant

• Current Assignee: Lytx, Inc.
• Original Assignee: Lytx, Inc.
• Inventors: Lambert, Daniel, Botnen, Joshua Donald
• Granted Patent: US 9,761,063 B2
• Time in Patent Office: Days
• US Class Current: 701/33.4
• 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:

an interface configured to receive a portion of data regarding a driving event; and

a processor 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.

2. 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;

indicate that the event is to be deleted.

3. 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;

indicate that the event is to be soft deleted.

4. 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;

indicate that the event is to be marked as not transmitted.

5. 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;

indicate that the event is to be marked as deleted.

6. A system as in claim 1, wherein determining whether more data regarding the driving event should be requested comprises checking location-specific legal information exceptions.

7. A system as in claim 1, wherein determining whether more data regarding the driving event should be requested comprises checking customer-specific event exceptions.

8. A system as in claim 1, wherein determining whether more data regarding the driving event should be requested comprises checking customer-specific region exceptions.

9. A system as in claim 1, wherein the data regarding the driving event includes video information or still picture information.

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

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

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

in the event that the driving event does not satisfy non-transmitting criteria, mark that the driving event has been checked against the exception database.

13. A system as in claim 12, wherein the driving event is marked with an indication of a version or date of the exception database.

14. A system as in claim 1, wherein the driving event includes an indication of a version or date of a location-specific legal information database.

15. A system as in claim 1, wherein the non-transmitting criteria comprises an exception indication.

16. A system as in claim 15, wherein the exception indication is based on a location specific is legal data.

17. A system as in claim 16, wherein the location specific legal data comprises one of the following:

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

18. A method for receiving a driving event, comprising:

receiving a portion of data regarding a driving event;

determining, using a processor, whether more data regarding the driving event should be requested; and

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

requesting more data regarding the driving event.

19. A computer program product for receiving a driving event, the computer program product being embodied in a tangible computer readable storage medium and comprising computer instructions for:

receiving a portion of data regarding a driving event;

determining whether more data regarding the driving event should be requested; and

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

requesting more data regarding the driving event.