Wireless broadcasting of drive-times data

• US 8,121,777 B2
• Filed: 03/07/2008
• Issued: 02/21/2012
• Est. Priority Date: 03/07/2008
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Guerrero, Miguel, Corbea, Cosmin
• Primary Examiner(s): BEAUCHAINE, MARK J
• Application Number:
  US12/043,955
• Publication Number:
  US 20090228193A1
• Time in Patent Office: 1,446 Days
• Field of Search: 701/118, 701/117, 701/119, 340/901, 340/905
• US Class Current: 701/118
• CPC Class Codes: G08G 1/091 Traffic information broadcasting broadcasting communication H04H
• CPC Class Codes: G08G 1/096716 where the received information does not generate an automatic action on the vehicle control
• CPC Class Codes: G08G 1/096758 where no selection takes place on the transmitted or the received information
• CPC Class Codes: G08G 1/096775 where the origin of the information is a central station
• CPC Class Codes: H04H 20/16 Arrangements for broadcast or for distribution of identical information repeatedly
• CPC Class Codes: H04H 20/55 for traffic information

Abstract

Either vehicle traffic or financial markets data is regularly broadcast in a fixed size packet over a wireless network in a push manner to one or more wireless receiver devices located within a particular service coverage region. A data center stores information specific to the particular region including drive-times strings metadata, drive-times data, drive-times route metadata, traffic incident data and financial markets indicators data. The data center decides upon a particular type of information to be placed into a payload of a next packet to be broadcast and pre-formats this information accordingly without receiving any information from the receiver devices. Data structures are provided which contain data representing the drive-times strings metadata, drive-times data, drive-times route metadata, traffic incident data and financial markets indicators data.

Claims

1. A computer-readable storage medium having stored thereon a vehicle traffic information data structure comprising a payload field containing data representing a particular type of vehicle traffic information, wherein,

the particular type of vehicle traffic information comprises one of (i) drive-times strings metadata, or (ii) drive-times data, or (iii) drive-times route metadata, and

the data structure and payload field have fixed sizes, and the data structure is generated on a regular basis by a data center and is subsequently broadcast on a regular basis over a wireless network in a push manner to one or more wireless receiver devices located within a particular service coverage region, and the data in the payload field is pre-formatted by the data center and is specific to the particular service coverage region, and wherein

whenever the particular type of vehicle traffic information comprises drive-times strings metadata, the payload field comprises,

a first sub-field comprising data representing route string-record metadata,

a second sub-field comprising data representing a region ID, wherein a change in the region ID informs each receiver device that the route string-record metadata in the first sub-field corresponds to a different service coverage region than the particular service coverage region,

a third sub-field comprising data representing a version value,

a fourth sub-field comprising data representing a packet number value specifying a sequence number for the vehicle traffic information data structure, and

a fifth sub-field comprising data representing a total packets value specifying a total number of vehicle traffic information data structures to be broadcast that will contain said route string-record metadata.

2. The computer-readable storage medium of claim 1, wherein,

a most significant two bits of the version value specify a major version value for the route string-record metadata in the first sub-field,

a least significant six bits of the version value specify a minor version value for said route string-record metadata, wherein,

whenever the minor version value is different from that which was previously broadcast but the major version value is the same as that which was previously broadcast, this informs each receiver device that the route string-record metadata represents additional routes to those which were previously broadcast, and

whenever the major version value is different from that which was previously broadcast, this informs each receiver device that any previously broadcast route string-record metadata should be deleted.

3. The computer-readable storage medium of claim 1, wherein the first sub-field of the payload field comprises a plurality of sub-fields organized as pairs of route sub-fields, wherein each pair of route sub-fields specifies a particular route string-record and comprises:

a first route sub-field comprising data representing an ID for the particular route string; and

a second route sub-field comprising data comprising a plurality of characters specifying a particular city, landmark or via, using a six bit encoding per character.

4. A computer-implemented process for regularly broadcasting packets of either vehicle traffic or financial markets data over a wireless FM radio sub-carrier network in a push manner to each of one or more wireless receiver devices located within a particular region, comprising, for each packet broadcast:

using a computer to perform the following process actions;

deciding upon a particular type of information to be placed into a payload of a next packet to be broadcast and pre-formatting said information accordingly, wherein,

the decision is made and pre-formatting is performed by a data center without receiving any information from the receiver devices, wherein the data center stores a plurality of types of information specific to a particular service coverage region, and

the plurality of types of information comprise drive-times strings metadata, drive-times data, drive-times route metadata, traffic incident data and financial markets indicators data;

whenever it is decided that the particular type of information to be placed into said payload comprises drive-times strings metadata, generating a corresponding route string-record metadata element and placing it into said payload, wherein the route string-record metadata element comprises data specifying a region ID, a metadata version value, a packet number value, a total packets value and a plurality of different route string-records;

whenever it is decided that the particular type of information to be placed into said payload comprises drive-times data, generating a corresponding drive-time records data element and placing it into said payload, wherein the drive-time records data element comprises data specifying a region ID, a packet number value and a plurality of different drive-time records each of which is mapped to a particular route;

whenever it is decided that the particular type of information to be placed into said payload comprises drive-times route metadata, generating a corresponding route description metadata element and placing it into said payload, wherein the route description metadata element comprises data specifying a region ID, a metadata version value, a packet number value, a total packets value and a plurality of different routes;

whenever it is decided that the particular type of information to be placed into said payload comprises traffic incident data, generating a corresponding traffic incident data element and placing it into said payload, wherein the traffic incident data element comprises data specifying a description of a particular traffic incident, a particular type of traffic incident according to a prescribed set of possible types of traffic incidents, a unique ID for the particular traffic incident, and a start time and estimated end time for the particular traffic incident; and

whenever it is decided that the particular type of information to be placed into said payload comprises financial markets indicators data, generating a corresponding financial markets indicators records data element and placing it into said payload, wherein the financial markets indicators records data element comprises data specifying a current status for the financial markets and a plurality of different financial market indicator records.

5. The process of claim 4, wherein said financial markets indicators records data element is represented by a field in the payload and comprises:

a first sub-field comprising data representing financial markets indicators records; and

a second sub-field comprising data representing a current status for the financial markets, wherein each bit in the second sub-field represents a different financial market, a zero in a particular bit in the second sub-field specifies that the financial market is currently closed, and a one in the particular bit specifies that the financial market is currently open.

6. The process of claim 5, wherein the first sub-field comprises a plurality of sub-fields organized as sets of records sub-fields, wherein each set of records sub-fields comprises data representing a particular financial market indicator record and five sub-fields comprising:

a first records sub-field comprising data representing a name of a particular market index, wherein said name comprises a plurality of characters using a six bit encoding per character;

a second records sub-field comprising data representing a current price for the particular market index;

a third records sub-field comprising data representing a percentage of change from the preceding day'"'"'s closing price for the particular market index;

a fourth records sub-field comprising data representing a high price for the current day for the particular market index; and

a fifth records sub-field comprising data representing a low price for the current day for the particular market index.

7. The process of claim 6, wherein,

the data in the third records sub-field comprises a value of one in a most significant bit whenever the current price is lower than the preceding day'"'"'s closing price, and a value of zero in said bit whenever the current price is higher than the preceding day'"'"'s closing price,

the data in the fourth records sub-field represents a difference between the high price for the current day and the current price, wherein the high price for the current day is determined by adding said difference to the current price, and

the data in the fifth records sub-field represents a difference between the low price for the current day and the current price, wherein the low price for the current day is determined by subtracting said difference from the current price.

8. The process of claim 4, wherein said traffic incident data element is represented by a field in the payload and comprises:

a first sub-field comprising data representing a description of a particular traffic incident;

a second sub-field comprising data specifying a particular type of traffic incident according to a prescribed set of possible types of traffic incidents;

a third sub-field comprising data representing a unique ID for the particular traffic incident;

a fourth sub-field comprising data representing a start time for the particular traffic incident; and

a fifth sub-field comprising data representing an estimated end time for the particular traffic incident.

9. The process of claim 8, wherein,

the data in the fourth sub-field comprises the number of minutes since midnight using the universal time code,

the data in the fifth sub-field comprises the number of minutes after the start time, and

the data in the first sub-field comprises a plurality of characters which describe the particular traffic incident, using a six bit encoding per character.

10. A computer-readable storage medium having stored thereon a vehicle traffic information data structure comprising a payload field containing data representing a particular type of vehicle traffic information, wherein,

the particular type of vehicle traffic information comprises one of (i) drive-times strings metadata, or (ii) drive-times data, or (iii) drive-times route metadata, and

the data structure and payload field have fixed sizes, and the data structure is generated on a regular basis by a data center and is subsequently broadcast on a regular basis over a wireless network in a push manner to one or more wireless receiver devices located within a particular service coverage region, and the data in the payload field is pre-formatted by the data center and is specific to the particular service coverage region, and wherein

whenever the particular type of vehicle traffic information comprises drive-times data, the payload field comprises,

a first sub-field comprising data representing drive-time records,

a second sub-field comprising data representing a region ID, wherein a change in the region ID informs each receiver device that the drive-time records in the first sub-field correspond to a different service coverage region than the particular service coverage region, and

a third sub-field comprising data representing a packet number value, wherein,

whenever a most significant bit of the packet number value is set to one, this indicates to each receiver device that the vehicle traffic information data structure is the first in a sequence of said data structures to be subsequently broadcast, and a least significant seven bits of the packet number value specify the total number of said data structures in the sequence that will be broadcast, and

whenever the most significant bit of the packet number value is set to zero, the least significant seven bits of the packet number value specify a sequence number for the vehicle traffic information data structure.

11. The computer-readable storage medium of claim 10, wherein the first sub-field of the payload field comprises a plurality of sub-fields organized as sets of records sub-fields, wherein each set of records sub-fields comprises data representing a particular drive-time record which is mapped to a particular route and three sub-fields comprising:

a first records sub-field comprising data representing a current drive-time for the particular route;

a second records sub-field comprising data representing a current traffic volume for the particular route; and

a third records sub-field comprising data representing drive-time and traffic volume trend information for the particular route.

12. The computer-readable storage medium of claim 11, wherein,

a particular data value in the first records sub-field specifies that no additional drive-time records are available for the particular route,

the data in the second records sub-field is encoded such that a value of one decimal in said sub-field specifies that the current traffic volume is moderate, a value of two decimal specifies that the current traffic volume is heavy, a value of zero specifies that the particular route is currently clear, and a value of three decimal specifies that current traffic volume traffic volume data is unavailable for the particular route, and

the data in the third records sub-field is encoded such that a value of zero in said sub-field specifies that the drive-time and traffic volume are unchanged, a value of one decimal specifies that the drive-time and traffic volume are trending upward, a value of two decimal specifies that the drive-time and traffic volume are trending downward, and a value of three decimal specifies that drive-time and traffic volume trend information is unavailable for the particular route.

13. A computer-readable storage medium having stored thereon a vehicle traffic information data structure comprising a payload field containing data representing a particular type of vehicle traffic information, wherein,

the particular type of vehicle traffic information comprises one of (i) drive-times strings metadata, or (ii) drive-times data, or (iii) drive-times route metadata, and

the data structure and payload field have fixed sizes, and the data structure is generated on a regular basis by a data center and is subsequently broadcast on a regular basis over a wireless network in a push manner to one or more wireless receiver devices located within a particular service coverage region, and the data in the payload field is pre-formatted by the data center and is specific to the particular service coverage region, and wherein

whenever the particular type of vehicle traffic information comprises drive-times route metadata, the payload field comprises,

a first sub-field comprising data representing route description metadata,

a second sub-field comprising data representing a region ID, wherein a change in the region ID informs each receiver device that the route description metadata in the first sub-field corresponds to a different service coverage region than the particular service coverage region,

a third sub-field comprising data representing a version value, wherein a most significant two bits of the version value specify a major version value for the route description metadata in the first sub-field, and a least significant six bits of the version value specify a minor version value for said route description metadata,

a fourth sub-field comprising data representing a packet number value specifying a sequence number for the vehicle traffic information data structure, and

a fifth sub-field comprising data representing a total packets value specifying a total number of vehicle traffic information data structures to be broadcast that will contain said route description metadata.

14. The computer-readable storage medium of claim 13, wherein the first sub-field of the payload field comprises a plurality of sub-fields organized as sets of route sub-fields, wherein each set of route sub-fields comprises data representing a particular route and four sub-fields comprising:

a first route sub-field comprising data representing an ID for a particular drive-time record that is mapped to the particular route, wherein said ID specifies a sequence position for the particular drive-time record;

a second route sub-field comprising data representing an origin for the particular route;

a third route sub-field comprising data representing a destination for the particular route; and

a fourth route sub-field comprising data representing a pathway for the particular route.