Device determined bandwidth saving in transmission of events

• US 9,389,147 B1
• Filed: 01/08/2013
• Issued: 07/12/2016
• 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): Black, Thomas G
• Assistant Examiner(s): Li, Ce
• Application Number:
  US13/736,839
• Time in Patent Office: 1,281 Days
• Field of Search: 701/1, 701 322- 325, 701 327- 328, 701 333- 334, 701/33.9, 701/34.4
• US Class Current: 1/1
• CPC Class Codes: G01C 21/20 Instruments for performing navigational calculations G01C21/24, G01C21/26 take precedence
• CPC Class Codes: G01M 17/007 Wheeled or endless-tracked vehicles G01M17/08 takes precedence
• CPC Class Codes: G07C 5/008 communicating information to a remotely located station transmission systems for measured values G08C

Abstract

A system for transmitting a driving event comprises an interface and a processor. The interface is configured to receive a portion of data. The processor is configured to detect a driving event based at least in part on the portion of data; determine whether the driving event satisfies a non-transmitting criteria; and in the event that the driving event satisfies the non-transmitting criteria, indicate that the driving event is not to be transmitted.

Claims

1. A system coupled to a vehicle for recording and transmitting a driving event, comprising:

a plurality of sensors coupled to a vehicle to capture a portion of sensor data;

a set of map data comprising location-specific legal information;

a processor configured to;

detect a driving event based at least in part on the portion of sensor data and the location-specific legal information, wherein the detected driving event comprises a stop sign violation, a parking zone violation, or a railroad crossing violation;

check the driving event against an exception database comprising locations of errors in the location-specific legal information, wherein the locations of errors comprise a stop sign error location, a parking zone error location, a railroad crossing error location, or any combination thereof;

determine whether the driving event satisfies a non-transmitting criteria, wherein the non-transmitting criteria comprises an exception indication as found in the exception database; and

in the event that the driving event satisfies the non-transmitting criteria, indicate that the driving event is not to be transmitted to a vehicle data server; and

an interface to;

in the event that the event does not satisfy the non-transmitting criteria, send the driving event data to the vehicle data server over a network; and

a memory coupled to the processor and configured to provide the processor with instructions.

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

in the event that the driving event is indicated not to be transmitted;

delete the driving event.

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

in the event that the driving event is indicated not to be transmitted;

soft delete the driving event.

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

in the event that the driving event is indicated not to be transmitted;

mark the driving event as not transmitted.

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

in the event that the driving event is indicated not to be transmitted;

mark the driving event as deleted.

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

in the event that the driving event is not indicated not to be transmitted;

transmit the driving event.

7. A system as in claim 6, wherein recording a driving event comprises recording video information or still picture information.

8. A system as in claim 1, wherein the exception database further comprises customer-specific region exceptions.

9. A system as in claim 8, wherein the customer-specific region exceptions comprise a set of exceptions that apply to a given region for a specific customer.

10. A system as in claim 1, wherein the processor is further configured to record a driving event.

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

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

13. 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.

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

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

16. A system as in claim 1, wherein in the event that the driving event satisfies the non-transmitting, the driving event that is indicated to not be transmitted comprises indicating not to transmit captured video data.

17. A system as in claim 1, wherein the exception database further comprises customer specific driving event types that are not to be transmitted.

18. A system as in claim 17, wherein the customer specific driving event types comprise a rolling stop.

19. A system as in claim 1, wherein:

one of the plurality of sensors comprises an accelerometer to capture shock values;

the detected driving event further comprises a shock event; and

the exception database further comprises a shock value of a driving event that is different than a preset threshold.

20. A method for recording and transmitting a driving event, comprising:

receiving a portion of sensor data from a plurality of sensors coupled to a vehicle;

receiving a set of map data comprising location-specific legal information;

detecting a driving event based at least in part on the portion of sensor data and the location-specific legal information, wherein the detected driving event comprises a stop sign violation, a parking zone violation, or a railroad crossing violation;

checking the driving event against an exception database comprising locations of errors in the location-specific legal information, wherein the locations of errors comprise a stop sign error location, a parking zone error location, a railroad crossing error location, or any combination thereof;

determining, using a processor, whether the driving event satisfies a non-transmitting criteria, wherein the non-transmitting criteria comprises an exception indication as found in the exception database; and

in the event that the driving event satisfies the non-transmitting criteria, indicating that the driving event is not to be transmitted to a vehicle data server; and

in the event that the event does not satisfy the non-transmitting criteria, sending the driving event data through an interface to the vehicle data server over a network.

21. A computer program product for recording and transmitting a driving event, the computer program product being embodied in a tangible non-transitory computer readable storage medium and comprising computer instructions for:

receiving a portion of sensor data from a plurality of sensors coupled to a vehicle;

receiving a set of map data comprising location-specific legal information;

detecting a driving event based at least in part on the portion of sensor data and the location-specific legal information, wherein the detected driving event comprises a stop sign violation, a parking zone violation, or a railroad crossing violation;

checking the driving event against an exception database comprising locations of errors in the location-specific legal information, wherein the locations of errors comprise a stop sign error location, a parking zone error location, a railroad crossing error location, or any combination thereof;

determining whether the driving event satisfies a non-transmitting criteria, wherein the non-transmitting criteria comprises an exception indication as found in the exception database; and

in the event that the driving event satisfies the non-transmitting criteria, indicating that the driving event is not to be transmitted to a vehicle data server; and

in the event that the event does not satisfy the non-transmitting criteria, sending the driving event data through an interface to the vehicle data server over a network.