DEVICE DETERMINED BANDWIDTH SAVING IN TRANSMISSION OF EVENTS
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.
This application is a continuation of co-pending U.S. patent application Ser. No. 13/736,839, entitled DEVICE DETERMINED BANDWIDTH SAVING IN TRANSMISSION OF EVENTS filed Jan. 8, 2013 which is incorporated herein by reference for all purposes.
BACKGROUND OF THE INVENTIONModern vehicles (e.g., airplanes, boats, trains, cars, trucks, etc.) can include a vehicle event recorder in order to better understand the timeline of an anomalous event (e.g., an accident). A vehicle event recorder typically includes a set of sensors, e.g., video recorders, audio recorders, accelerometers, gyroscopes, vehicle state sensors, GPS (global positioning system), etc., that report data, which is used to determine the occurrence of an anomalous event. If an anomalous event is detected, the sensor data related to the event is stored for later review. A vehicle event recorder for cars and trucks (e.g., vehicles that operate on public roads) can include road map data comprising location-specific legal information (e.g., speed limit information, stop sign information, traffic light information, yield sign information, etc.). Location-specific legal information can be used to identify an anomalous event in the case of the vehicle acting against the law (e.g., traveling in excess of the speed limit, rolling through a stop sign, etc.). If there is an error in the legal information, anomalous events can be incorrectly identified, possibly leading to unnecessary expense as the event is processed, stored, and/or transmitted.
Various embodiments of the invention are disclosed in the following detailed description and the accompanying drawings.
The invention can be implemented in numerous ways, including as a process; an apparatus; a system; a composition of matter; a computer program product embodied on a computer readable storage medium; and/or a processor, such as a processor configured to execute instructions stored on and/or provided by a memory coupled to the processor. In this specification, these implementations, or any other form that the invention may take, may be referred to as techniques. In general, the order of the steps of disclosed processes may be altered within the scope of the invention. Unless stated otherwise, a component such as a processor or a memory described as being configured to perform a task may be implemented as a general component that is temporarily configured to perform the task at a given time or a specific component that is manufactured to perform the task. As used herein, the term ‘processor’ refers to one or more devices, circuits, and/or processing cores configured to process data, such as computer program instructions.
A detailed description of one or more embodiments of the invention is provided below along with accompanying figures that illustrate the principles of the invention. The invention is described in connection with such embodiments, but the invention is not limited to any embodiment. The scope of the invention is limited only by the claims and the invention encompasses numerous alternatives, modifications and equivalents. Numerous specific details are set forth in the following description in order to provide a thorough understanding of the invention. These details are provided for the purpose of example and the invention may be practiced according to the claims without some or all of these specific details. For the purpose of clarity, technical material that is known in the technical fields related to the invention has not been described in detail so that the invention is not unnecessarily obscured.
Device determined bandwidth saving in transmission of events is disclosed. A system for transmitting a driving event comprises an interface configured to receive a portion of data. A system for transmitting a driving event comprises a processor configured to detect a driving event; determine whether the event satisfies a non-transmitting criteria; in the event that the event satisfies the non-transmitting criteria, indicate that the event is not to be transmitted; and a memory coupled to the processor and configured to provide the processor with instructions.
A vehicle event recorder system comprises a set of sensors comprising a Global Positioning System (GPS) and a set of map data. The GPS in conjunction with the map data serves to identify the position and speed of the vehicle on a road described in the map data. The map data comprises location-specific legal information for determining whether the vehicle is operating within the law. In some embodiments, the map data comprising location-specific legal information is provided to the manufacturer of the vehicle event recorder by a third party (e.g., by a map data vendor). In some embodiments, the location-specific legal information includes errors—for example, locations where indicated speed limit information differs from the actual speed limit (e.g., the legal default speed limit or the posted speed limit) or locations where a stop sign is indicated but none exists or parking in violation for a mislabeled no parking zone. Errors in stored location-specific legal information can lead to a vehicle operating according to the law being flagged for a violation in error. This raises costs when a violation is detected, the capture and transmission of a video recording is triggered, needlessly incurring costs to the owner of the vehicle event recorder system (e.g., cost of transmission, cost of storage on the recorder, cost of reviewing the event, etc.).
Event detector 220 communicates with sensors 202 and map data 216. In some embodiments, event detector 220 receives sensor data from sensors 202. In some embodiments, event detector 220 detects events using sensor data from sensors 202. In some embodiments, an interface receives data (e.g., from sensors) and a processor processes the data to determine whether an event has been detected. Event detector 220 receives map and speed limit information from map data 216. In some embodiments, event detector 220 uses map and speed limit information from map data 216 in conjunction with GPS data from sensors 202 (e.g., from GPS 204) in order to identify violation events (e.g., events violating legal information indicated in location-specific legal information database 218). In some embodiments, identifying a violating event comprises determining a current map segment. In some embodiments, identifying a violating event comprises determining subsegment information. In some embodiments, when event detector 220 detects a violation event, it records the event. In some embodiments, the event includes an indication of a version or a date of location-specific legal information database 218. In some embodiments, recording the event comprises recording video information. In some embodiments, recording the event comprises recording still picture information. In some embodiments, when event detector 220 detects a violation event, it stores the event in event storage 224. In some embodiments, event detector stores an image from camera 210 in event storage 224 associated with the violation event. In some embodiments, event detector 220 stores video from camera 210 in event storage 224 associated with the violation event. In some embodiments, when event detector 220 uses map and speed limit information from map data 216 in conjunction with GPS data from sensors 202 in order to identify violation events, events are identified incorrectly (e.g., a violation event is identified even though the vehicle is traveling in accordance with the law), due to an error in location-specific legal information database 218.
Event detector 220 additionally communicates with exception database 222. Exception database 222 comprises a database of exceptions—for example, criteria under which detected events should be ignored. In various embodiments, exception database 222 comprises locations for which the actual speed limit (e.g., the legal default speed limit or the posted speed limit) is known to be different from the speed limit recorded in location-specific legal information database 218, instances where a stop sign indicated in location-specific legal information 218 is known not to exist, regions for which a given customer has declared it is not interested in receiving exceptions, modifications of legal requirements a customer is interested in following (e.g., only record an event when a driver is more than 5 MPH over the speed limit), or any other appropriate exceptions. In some embodiments, in the event that event detector 220 detects a violation event, it checks the event against exception database 222. In various embodiments, in the event that the event detector determines a violation event has been identified incorrectly using exception database 222, the event and any associated images and/or video are deleted from event storage 224, the event and any associated images and/or video are soft deleted from event storage 224, or the event and any associated images and/or video are modified in any other appropriate way. In some embodiments, soft deleting the event and any associated images and/or video comprises marking the event and any associated images and/or video for deletion but not removing them from storage until the storage space is required for other data.
In some embodiments, vehicle event recorder 200 transmits event information to a vehicle data server (e.g., vehicle data server 104 of
In 502, location-specific legal information exceptions (e.g., location-specific legal information exceptions 402 of
In 504, customer-specific event exceptions (e.g., customer-specific event exceptions 404 of
In 506, customer-specific region exceptions (e.g., customer-specific region exceptions 406 of
In 508, it is determined if the event satisfies the non-transmitting criteria. In some embodiments, the event satisfies the non-transmitting criteria if it corresponds to any of the exceptions checked (e.g., the exceptions checked in 502, 504, and 506). In the event the event satisfies the non-transmitting criteria, control passes to 512. In 512, it is indicated that the event is not to be transmitted. In some embodiments, in the event that the event is indicated not to be transmitted, the event is deleted. In some embodiments, in the event that the event is indicated not to be transmitted, the event is soft deleted. In various embodiments, soft deleting an event comprises marking it for later deletion, deleting a reference to the event, moving it to a soft delete partition, or soft deleting it in any other appropriate way. In some embodiments, in the event that the event is indicated not to be transmitted, the event is marked as not transmitted. In some embodiments, in the event that the event is indicated not to be transmitted, the event is marked as deleted. If it is determined in 508 that the event does not satisfy the non-transmitting criteria, control passes to 510. In 510, the event is transmitted. In some embodiments, the event is marked that it has been checked against the exception database. In some embodiments, the event is marked with an indication of the version or date of the exception database.
In some embodiments, a non-transmitting criteria comprises an exception indication. In some embodiments, the exception indication is based on a location specific legal data. In various embodiments, the location specific legal data comprises one of the following: a speed limit error, a stop sign error, a parking zone error, railroad crossing error, or any other appropriate data.
Although the foregoing embodiments have been described in some detail for purposes of clarity of understanding, the invention is not limited to the details provided. There are many alternative ways of implementing the invention. The disclosed embodiments are illustrative and not restrictive.
Claims
1. A system for transmitting a driving event, comprising:
- an interface configured to receive a portion of data; and
- a processor 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 by marking that the driving event is not to be transmitted.
2. A system as in claim 1, wherein detecting the driving event uses a threshold increased or reduced based at least in part on event exceptions.
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: mark the driving event as allowed to be removed.
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 1, wherein determining whether the driving event satisfies a non-transmitting criteria comprises checking location-specific legal information exceptions.
8. A system as in claim 1, wherein determining whether the driving event satisfies a non-transmitting criteria comprises checking customer-specific event exceptions.
9. A system as in claim 1, wherein determining whether the driving event satisfies a non-transmitting criteria comprises checking customer-specific region exceptions.
10. A system as in claim 1, wherein the processor is further configured to record a driving event.
11. A system as in claim 10, wherein recording a driving event comprises recording video information or still picture information.
12. A system as in claim 1, wherein the processor is further configured to determine a current segment.
13. A system as in claim 1, wherein the processor is further configured to determine subsegment information.
14. 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.
15. A system as in claim 14, wherein the driving event is marked with an indication of a version or date of the exception database.
16. 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.
17. A system as in claim 1, wherein the non-transmitting criteria comprises an exception indication.
18. A system as in claim 17, wherein the exception indication is based on a location specific legal data.
19. A system as in claim 18, 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.
20. A method for transmitting a driving event, comprising:
- receiving a portion of data;
- detecting a driving event based at least in part on the portion of data;
- determining, using a processor, whether the driving event satisfies a non-transmitting criteria; and
- in the event that the driving event satisfies the non-transmitting criteria: indicating by marking that the driving event is not to be transmitted.
21. A computer program product for transmitting 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;
- detecting a driving event based at least in part on the portion of data;
- determining whether the driving event satisfies a non-transmitting criteria; and
- in the event that the driving event satisfies the non-transmitting criteria: indicating by marking that the driving event is not to be transmitted.
Type: Application
Filed: Jun 10, 2016
Publication Date: Jan 5, 2017
Inventors: Daniel Lambert (Carlsbad, CA), Joshua Donald Botnen (San Diego, CA)
Application Number: 15/178,988