DYNAMIC COMMUNICATION DATA USAGE

• US 20170070616A1
• Filed: 03/02/2015
• Published: 03/09/2017
• Est. Priority Date: 03/03/2014
• Status: Abandoned Application

• Current Assignee: Inrix Incorporated
• Original Assignee: Inrix Incorporated
• Inventors: DiMeo, David
• Application Number:
  US15/122,734
• Publication Number:
  US 20170070616A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: A61B 5/02055 Simultaneously evaluating both cardiovascular condition and temperature
• CPC Class Codes: A61B 5/024 Detecting, measuring or recording pulse rate or heart rate A61B5/0205, A61B5/021 take precedence
• CPC Class Codes: A61B 5/0531 Measuring skin impedance
• CPC Class Codes: A61B 5/4845 Toxicology, e.g. by detection of alcohol, drug or toxic products A61B5/4848 takes precedence
• CPC Class Codes: B60R 16/0236 for economical driving
• CPC Class Codes: B60W 2040/0809 Driver authorisation; Driver identity check
• CPC Class Codes: B60W 2040/0872 Driver physiology
• CPC Class Codes: B60W 2050/0075 Automatic parameter input, automatic initialising or calibrating means
• CPC Class Codes: B60W 2540/22 Psychological state; Stress level or workload
• CPC Class Codes: B60W 2552/00 Input parameters relating to infrastructure
• CPC Class Codes: B60W 2554/00 Input parameters relating to objects
• CPC Class Codes: B60W 2555/20 Ambient conditions, e.g. wind or rain
• CPC Class Codes: B60W 2556/10 Historical data
• CPC Class Codes: B60W 2710/1044 Output speed change rate
• CPC Class Codes: B60W 2710/18 Braking system
• CPC Class Codes: B60W 2720/10 Longitudinal speed
• CPC Class Codes: B60W 30/143 Speed control B60W30/16 takes precedence
• CPC Class Codes: B60W 40/04 Traffic conditions
• CPC Class Codes: B60W 40/08 related to drivers or passengers
• CPC Class Codes: B60W 40/09 Driving style or behaviour
• CPC Class Codes: B64C 39/024 : of the remote controlled vehicle type, i.e. RPV
• CPC Class Codes: B64U 2101/30 : for imaging, photography or videography
• CPC Class Codes: G01C 21/3415 : Dynamic re-routing, e.g. recalculating the route when the user deviates from calculated route or after detecting real-time traffic data or accidents
• CPC Class Codes: G01C 21/3469 : Fuel consumption; Energy use; Emission aspects
• CPC Class Codes: G01C 21/3608 : using speech input, e.g. using speech recognition
• CPC Class Codes: G01C 21/3617 : using user history, behaviour, conditions or preferences, e.g. predicted or inferred from previous use or current movement
• CPC Class Codes: G01C 21/3655 : Timing of guidance instructions
• CPC Class Codes: G01C 21/3667 : Display of a road map G01C21/3614 takes precedence; guidance using 3D or perspective road maps G01C21/3635
• CPC Class Codes: G01C 21/3682 : output of POI information on a road map G01C21/3614, G01C21/3685 take precedence
• CPC Class Codes: G05D 1/0011 : associated with a remote control arrangement
• CPC Class Codes: G06F 16/29 : Geographical information databases
• CPC Class Codes: G06N 20/00 : Machine learning
• CPC Class Codes: G06Q 20/102 : Bill distribution or payments
• CPC Class Codes: G06Q 2240/00 : Transportation facility access, e.g. fares, tolls or parking
• CPC Class Codes: G06Q 30/0283 : Price estimation or determination
• CPC Class Codes: G06Q 40/08 : Insurance
• CPC Class Codes: G06Q 50/40 : Business processes related to the transportation industry shipping G06Q10/083
• CPC Class Codes: G07B 15/00 : Arrangements or apparatus for collecting fares, tolls or entrance fees at one or more control points handling coins or valuable papers, e.g. banknotes, G07D; apparatus for vending or hiring articles or services activated by coins, credit cards, paper currency or the like G07F7/00, G07F17/00
• CPC Class Codes: G07B 15/063 : using wireless information transmission between the vehicle and a fixed station identification of vehicles G08G
• CPC Class Codes: G07C 5/008 : communicating information to a remotely located station transmission systems for measured values G08C
• CPC Class Codes: G08G 1/0112 : from the vehicle, e.g. floating car data [FCD]
• CPC Class Codes: G08G 1/012 : from other sources than vehicle or roadside beacons, e.g. mobile networks
• CPC Class Codes: G08G 1/0129 : for creating historical data or processing based on historical data
• CPC Class Codes: G08G 1/0133 : for classifying traffic situation
• CPC Class Codes: G08G 1/0141 : for traffic information dissemination
• CPC Class Codes: G08G 1/0145 : for active traffic flow control
• CPC Class Codes: G08G 1/065 : by counting the vehicles in a section of the road or in a parking area, i.e. comparing incoming count with outgoing count
• CPC Class Codes: G08G 1/07 : Controlling traffic signals
• CPC Class Codes: G08G 1/093 : Data selection, e.g. prioritizing information, managing message queues, selecting the information to be output
• CPC Class Codes: G08G 1/0962 : having an indicator mounted inside the vehicle, e.g. giving voice messages
• CPC Class Codes: G08G 1/0965 : responding to signals from another vehicle, e.g. emergency vehicle
• CPC Class Codes: G08G 1/0967 : Systems involving transmission of highway information, e.g. weather, speed limits transmission of navigation instructions to the vehicle G08G1/0968
• CPC Class Codes: G08G 1/096725 : where the received information generates an automatic action on the vehicle control
• CPC Class Codes: G08G 1/096741 : where the source of the transmitted information selects which information to transmit to each vehicle
• CPC Class Codes: G08G 1/096775 : where the origin of the information is a central station
• CPC Class Codes: G08G 1/096791 : where the origin of the information is another vehicle
• CPC Class Codes: G08G 1/096811 : where the route is computed offboard
• CPC Class Codes: G08G 1/096822 : where the segments of the route are transmitted to the vehicle at different locations and times
• CPC Class Codes: G08G 1/096838 : where the user preferences are taken into account or the user selects one route out of a plurality
• CPC Class Codes: G08G 1/097 : Supervising of traffic control systems, e.g. by giving an alarm if two crossing streets have green light simultaneously
• CPC Class Codes: H04B 1/3822 : specially adapted for use in vehicles H04B1/3827 takes precedence
• CPC Class Codes: H04B 7/18504 : Aircraft used as relay or high altitude atmospheric platform
• CPC Class Codes: H04L 67/02 : based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/306 : User profiles
• CPC Class Codes: H04L 9/3247 : involving digital signatures
• CPC Class Codes: H04M 15/60 : based on actual use of network resources
• CPC Class Codes: H04W 12/08 : Access security
• CPC Class Codes: H04W 4/024 : Guidance services
• CPC Class Codes: H04W 4/029 : Location-based management or tracking services
• CPC Class Codes: H04W 4/40 : for vehicles, e.g. vehicle-to-pedestrians [V2P]
• CPC Class Codes: H04W 4/42 : for mass transport vehicles, e.g. buses, trains or aircraft
• CPC Class Codes: H04W 4/48 : for in-vehicle communication
• CPC Class Codes: H04W 4/50 : Service provisioning or reconfiguring

Abstract

One or more techniques and/or systems are provided for selectively collecting vehicle telemetry data from one or more vehicles. For example, a communication data budget for a vehicle may be identified (e.g., a 5 GB per month data connection plan). A determination may be made as to whether the vehicle can provide vehicle telemetry data used to model a travel condition (e.g., road imagery, temperature, a windshield wiper state, and/or other vehicle telemetry data used to model a road safety condition). If the vehicle has remaining communication data budget available for transmission of the vehicle telemetry data without the vehicle exceeding the communication data budget for a billing cycle, then a data request for the vehicle telemetry data may be sent to the vehicle. Responsive to receiving the vehicle telemetry data from the vehicle, the travel condition may be modeled (e.g., the road condition may be determined as icy).

Claims

1. A system for selectively collecting vehicle telemetry data from one or more vehicles, comprising:

a data collection component configured to;

identify a first communication data budget for a first vehicle;

determine that the first vehicle can provide vehicle telemetry data used to model a travel condition;

evaluate first data usage information of the first vehicle to determine a first remaining amount of communication data of the first communication data budget;

construct a first data request based upon the vehicle telemetry data and the first remaining amount of communication data;

send the first data request to the first vehicle;

receive a first vehicle telemetry data response from the first vehicle; and

model the travel condition based upon the first vehicle telemetry data response.

2. The system of claim 1, the first vehicle telemetry data response comprising a first portion of the vehicle telemetry data, and the data collection component configured to:

identify a second communication data budget for a second vehicle;

determine that the second vehicle can provide the vehicle telemetry data used to model the travel condition;

evaluate second data usage information of the second vehicle to determine a second remaining amount of communication data of the second communication data budget;

construct a second data request based upon the vehicle telemetry data and the second remaining amount of communication data;

send the second data request to the second vehicle;

receive a second vehicle telemetry data response from the second vehicle, the second vehicle telemetry data response comprising a second portion of the vehicle telemetry data; and

model the travel condition based upon the first portion of the vehicle telemetry data and the second portion of the vehicle telemetry data.

3. The system of claim 2, the data collection component configured to:

responsive to determining that the first remaining amount of communication data is greater than the second remaining amount of communication data;

specify a first amount of vehicle telemetry data to request from the first vehicle;

specify a second amount of vehicle telemetry data to request from the second vehicle, the first amount of vehicle telemetry data greater than the second amount of vehicle telemetry data;

construct the first data request based upon the first amount of vehicle telemetry data; and

construct the second data request based upon the second amount of vehicle telemetry data.

4. The system of claim 1, the travel condition corresponding to a road segment, and the data collection component configured to:

identify a driving pattern of the first vehicle;

responsive to the driving pattern indicating that the first vehicle will travel the road segment above a threshold probability, determine that the first vehicle can provide the vehicle telemetry data; and

construct the first data request to instruct the first vehicle to collect new vehicle telemetry data while traveling the road segment.

5. The system of claim 1, the travel condition corresponding to at least one of a road condition, a vehicle condition, or a traffic condition.

6. The system of claim 1, the vehicle telemetry data corresponding to at least one of a vehicle sensor reading, a temperature, an image, a video, a state of a vehicle component, a weather condition, or a driving behavior of the user derived from at least one of a braking pattern, an acceleration pattern, a deceleration pattern, a turn signal usage, or a driving pattern of the first vehicle.

7. The system of claim 1, the data collection component configured to:

define a data request threshold based upon a projected amount of periodic communication usage by the first vehicle; and

responsive to the vehicle telemetry data not exceeding the data request threshold, construct the first data request to send to the first vehicle.

8. The system of claim 7, the data collection component configured to:

determine the projected amount of periodic communication usage based upon a periodic billing cycle and a current amount of data usage for the periodic billing cycle.

9. The system of claim 7, the data collection component configured to:

responsive to the vehicle telemetry data exceeding the data request threshold, refrain from constructing the first data request to send to the first vehicle.

10. The system of claim 9, the data collection component configured to:

responsive to determining that a new allocation of the first communication data budget has occurred for the first vehicle, construct the first data request to send to the first vehicle.

11. The system of claim 7, the data collection component configured to:

responsive to the vehicle telemetry data exceeding the data request threshold, include an instruction, within the first data request, for the first vehicle to collect measured vehicle telemetry data to send to the data collection component upon the first vehicle receiving a new allocation of the first communication data budget.

12. The system of claim 1, the data collection component configured to:

determine that the travel condition corresponds to a geographical region;

establish communication connections with one or more vehicles within a threshold proximity to the geographical region; and

send data requests, for the vehicle telemetry data, to the one or more vehicles based upon the vehicle telemetry data not exceeding data request thresholds of the one or more vehicles.

13. The system of claim 12, the geographical region comprising at least one of an address range, a road, or locational coordinates.

14. A system for selectively providing vehicle telemetry data to a data collection component, comprising:

a vehicle data provider component configured to;

receive a data request for vehicle telemetry data of a vehicle;

query one or more vehicle sensors of the vehicle to obtain measured vehicle telemetry data;

determine a data request threshold based upon a remaining amount of communication data of a communication data budget for the vehicle; and

responsive to the measured vehicle telemetry data not exceeding the data request threshold, send a vehicle telemetry data response, comprising the measured vehicle telemetry data, to a data collection component over a communication connection.

15. The system of claim 14, the vehicle data provider component configured to:

responsive to the measured vehicle telemetry data exceeding the data request threshold;

store the measured vehicle telemetry data as stored vehicle telemetry data within a data storage device; and

mark the stored vehicle telemetry data for subsequent transmission to the data collection component.

16. The system of claim 15, the vehicle data provider component configured to:

responsive to determining that a new allocation of the communication data budget has occurred for the vehicle, send the vehicle telemetry data response, comprising the stored vehicle telemetry data, to the data collection component over the communication connection.

17. The system of claim 14, the vehicle data provider component configured to:

determine that the vehicle telemetry data corresponds to a geographical location; and

trigger querying the one or more vehicle sensors to obtain the measured vehicle telemetry data based upon a determine that the vehicle is within a threshold proximity of the geographical location.

18. The system of claim 14, the vehicle data provider component configured to:

obtain current vehicle telemetry data during operation of the vehicle;

store the current vehicle telemetry data as stored vehicle telemetry data within a data storage device; and

responsive to receiving a second data request corresponding to the stored vehicle telemetry data;

determine a current data request threshold based upon a current remaining amount of communication data of the communication data budget for the vehicle; and

responsive to the stored vehicle telemetry data not exceeding the current data request threshold, send a current vehicle telemetry data response, comprising the stored vehicle telemetry data, to the data collection component over the communication connection.

19. The system of claim 14, the vehicle data provider component configured to:

periodically transmit location data of the vehicle to the data collection component.

20. A method for selectively collecting vehicle telemetry data from one or more vehicles, comprising:

identifying a communication data budget for a vehicle;

determining that the vehicle can provide vehicle telemetry data used to model a travel condition;

evaluating data usage information of the vehicle to determine a remaining amount of communication data of the communication data budget;

constructing a data request based upon the vehicle telemetry data and the remaining amount of communication data;

sending the data request to the vehicle;

receiving a vehicle telemetry data response from the vehicle; and

modeling the travel condition based upon the vehicle telemetry data response.