# US 2017/0287328 A1 · Traffic Data Encoding Using Fixed References

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2017/0287328 A1
- Document ID: US20170287328A1
- Status: Published application
- Kind: A1
- Application number: 15/473,113
- Filed: 2017-03-29
- Published: 2017-10-05
- Earliest claimed: 2016-03-29
- Applicants: Sirius XM Radio Inc.
- Inventors: Leslie John French
- Web page: https://patentgrep.com/patent/US20170287328A1

## CPC

- G08G 1/092: {Coding or decoding of the information}
- G08G 1/0112: {from the vehicle, e.g. floating car data [FCD]}
- G08G 1/0129: {for creating historical data or processing based on historical data}
- G08G 1/0133: {for classifying traffic situation}
- G08G 1/0141: {for traffic information dissemination}
- G08G 1/091: {Traffic information broadcasting (broadcasting communication H04H)}
- G08G 1/096716: {where the received information does not generate an automatic action on the vehicle control}
- G08G 1/09675: {where a selection from the received information takes place in the vehicle}
- G08G 1/096775: {where the origin of the information is a central station}
- G08G 1/096791: {where the origin of the information is another vehicle}
- G08G: TRAFFIC CONTROL SYSTEMS (guiding railway traffic, ensuring the safety of railway traffic B61L; arrangement of road signs or traffic signals E01F9/00; radar or analogous systems, sonar systems, lidar systems specially adapted for traffic control G01S13/91, G01S15/88, G01S17/88; {radar or analogous systems, sonar systems, lidar systems specially adapted for anti-collision purposes G01S13/93, G01S15/93, G01S17/93})

## Abstract

A method is provided for encoding traffic incident and flow data using target map locations, such as OpenStreetMap (OSM) locations directly, rather than going through a conversion stage. In exemplary embodiments, the method can include selecting a set of fixed, identifiable locations along a roadbed, matching these to a target map, generating flow vectors in the target map's referencing model, and deliver only target map location data to the external application. Non-point location data such as incidents can also be represented using the same scheme, using an offset along a previously defined path for the start and end points.

## Claims

### Claim 1

A computer-implemented method of encoding traffic data, the method comprising:
at a computing device having a data processor and computer memory:
matching a set of fixed locations along a roadbed to a target map;
generating flow vectors representing traffic data using the fixed locations of the target map; and;
delivering the generated flow vectors to a receiver to enable the receiver to render the represented traffic data based on the generated flow vectors.

### Claim 2 (depends on 1)

A computer-implemented method according to claim 1, further comprising receiving vehicle telematics data from a plurality of probes, and aggregating the received vehicle telematics data to generate current traffic data.

### Claim 3 (depends on 2)

A computer-implemented method according to claim 2, wherein the traffic data is generated based at least in part on a traffic model and the current traffic data.

### Claim 4 (depends on 1)

A computer-implemented method according to claim 1, wherein the traffic data is generated based at least in part on a traffic model.

### Claim 5 (depends on 1)

A computer-implemented method according to claim 1, wherein the generating of flow vectors include translating coordinates of intermediate points between the fixed locations as vectors with respect to the fixed locations.

### Claim 6 (depends on 1)

A computer-implemented method according to claim 1, wherein the target map is OpenStreetMap (OSM).

### Claim 7 (depends on 6)

A computer-implemented method according to claim 6, wherein the fixed locations are represented using Nodes and Ways.

### Claim 8 (depends on 1)

A computer-implemented method according to claim 1, wherein the set of locations are intersections.

### Claim 9

A traffic encoding system comprising:
a processor; a memory coupled to the processor; and a program stored in the memory, the program including instructions for:
matching a set of fixed locations along a roadbed to a target map;
generating flow vectors representing traffic data using the fixed locations of the target map; and;
delivering the generated flow vectors to a receiver to enable the receiver to render the represented traffic data based on the generated flow vectors.

### Claim 10 (depends on 9)

A traffic encoding system according to claim 9, wherein the instructions further comprises receiving vehicle telematics data from a plurality of probes, and aggregating the received vehicle telematics data to generate current traffic data.

### Claim 11 (depends on 10)

A traffic encoding system according to claim 10, wherein the traffic data is generated based at least in part on a traffic model and the current traffic data.

### Claim 12 (depends on 11)

A traffic encoding system according to claim 11, wherein the traffic data is generated based at least in part on a traffic model.

### Claim 13 (depends on 9)

A traffic encoding system according to claim 9, wherein the generating of flow vectors include translating coordinates of intermediate points between the fixed locations as vectors with respect to the fixed locations.

### Claim 14 (depends on 9)

A traffic encoding system according to claim 9, wherein the target map is OpenStreetMap (OSM).

### Claim 15 (depends on 14)

A traffic encoding system according to claim 14, wherein the fixed locations are represented using Nodes and Ways.

### Claim 16 (depends on 9)

A traffic encoding system according to claim 9, wherein the fixed locations are intersections.

### Claim 17

A non-transitory computer-readable storage medium storing one or more programs, the one or more programs comprising instructions that, when executed by a data processor, causes the data processor to:
match a set of fixed locations along a roadbed to a target map;
generate flow vectors representing traffic data using the fixed locations of the target map; and;
deliver the generated flow vectors to a receiver to enable the receiver to render the represented traffic data based on the generated flow vectors.

### Claim 18 (depends on 17)

A non-transitory computer-readable storage medium according to claim 17, wherein the instructions further causes the data processor to receive vehicle telematics data from a plurality of probes, and aggregating the received vehicle telematics data to generate current traffic data.

### Claim 19 (depends on 17)

A non-transitory computer-readable storage medium according to claim 17, wherein the traffic data is generated based at least in part on a traffic model and the current traffic data.

### Claim 20 (depends on 17)

A non-transitory computer-readable storage medium according to claim 17, wherein the traffic data is generated based at least in part on a traffic model.

### Claim 21 (depends on 17)

A non-transitory computer-readable storage medium according to claim 17, wherein the generating of flow vectors include translating coordinates of intermediate points between the fixed locations as vectors with respect to the fixed locations.

### Claim 22 (depends on 17)

A non-transitory computer-readable storage medium according to claim 17, wherein the target map is OpenStreetMap (OSM).

### Claim 23 (depends on 22)

A non-transitory computer-readable storage medium according to claim 22, wherein the fixed locations are represented using Nodes and Ways.

### Claim 24 (depends on 17)

A non-transitory computer-readable storage medium according to claim 17, wherein the fixed locations are intersections.
