# US 2014/0195105 A1 · Server determined bandwidth saving in transmission of events > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2014/0195105 A1 - Document ID: US20140195105A1 - Status: Published application - Kind: A1 - Application number: 13/736,842 - Filed: 2013-01-08 - Published: 2014-07-10 - Earliest claimed: 2013-01-08 - Assignees: Lytx, Inc. - Applicants: Lytx, Inc. - Inventors: Daniel Lambert; Joshua Donald Botnen - Web page: https://patentgrep.com/patent/US20140195105A1 ## CPC - G07C 5/008: {communicating information to a remotely located station (transmission systems for measured values G08C)} - 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 - G07C: TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE ## 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 ### Claim 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. ### Claim 2 (depends on 1) 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. ### Claim 3 (depends on 1) 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. ### Claim 4 (depends on 1) 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. ### Claim 5 (depends on 1) 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. ### Claim 6 (depends on 1) 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. ### Claim 7 (depends on 1) A system as in claim 1, wherein determining whether more data regarding the driving event should be requested comprises checking customer-specific event exceptions. ### Claim 8 (depends on 1) A system as in claim 1, wherein determining whether more data regarding the driving event should be requested comprises checking customer-specific region exceptions. ### Claim 9 (depends on 1) A system as in claim 1, wherein the data regarding the driving event includes video information or still picture information. ### Claim 10 (depends on 1) A system as in claim 1, wherein the processor is further configured to determine a current segment. ### Claim 11 (depends on 1) A system as in claim 1, wherein the processor is further configured to determine subsegment information. ### Claim 12 (depends on 1) 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. ### Claim 13 (depends on 12) A system as in claim 12, wherein the driving event is marked with an indication of a version or date of the exception database. ### Claim 14 (depends on 1) 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. ### Claim 15 (depends on 1) A system as in claim 1, wherein the non-transmitting criteria comprises an exception indication. ### Claim 16 (depends on 15) A system as in claim 15, wherein the exception indication is based on a location specific is legal data. ### Claim 17 (depends on 16) 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. ### Claim 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. ### Claim 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.