U.S. patent application number 14/802426 was filed with the patent office on 2016-07-14 for encoding and decoding traffic information using encoding fields.
The applicant listed for this patent is LG Electronics Inc.. Invention is credited to Jun KIM, Sang Hyup LEE, Kyoung Soo MOON.
Application Number | 20160205021 14/802426 |
Document ID | / |
Family ID | 37707968 |
Filed Date | 2016-07-14 |
United States Patent
Application |
20160205021 |
Kind Code |
A1 |
LEE; Sang Hyup ; et
al. |
July 14, 2016 |
ENCODING AND DECODING TRAFFIC INFORMATION USING ENCODING FIELDS
Abstract
A method for identifying traffic information includes receiving
traffic data including a first identifier, information that is
encoded, and information corresponding to a field indicative of an
encoding scheme. The first identifier enables a determination of a
type of information that is included within the received traffic
data. The method also includes determining a type of information
included within the received traffic data based on the first
identifier and determining encoding information based on the field
indicative of an encoding scheme included in the received traffic
data only if the first identifier enables a determination that the
received traffic data includes a field indicative of an encoding
scheme. The method further includes identifying the information
that is encoded based on the determined encoding information.
Inventors: |
LEE; Sang Hyup; (Seoul,
KR) ; MOON; Kyoung Soo; (Seoul, KR) ; KIM;
Jun; (Seoul, KR) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
LG Electronics Inc. |
Seoul |
|
KR |
|
|
Family ID: |
37707968 |
Appl. No.: |
14/802426 |
Filed: |
July 17, 2015 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
14477395 |
Sep 4, 2014 |
|
|
|
14802426 |
|
|
|
|
11420447 |
May 25, 2006 |
8259815 |
|
|
14477395 |
|
|
|
|
60684972 |
May 27, 2005 |
|
|
|
Current U.S.
Class: |
370/230 |
Current CPC
Class: |
H04H 60/73 20130101;
G08G 1/091 20130101; H04H 20/55 20130101; H04L 47/24 20130101; H04L
47/12 20130101 |
International
Class: |
H04L 12/801 20060101
H04L012/801; H04L 12/851 20060101 H04L012/851 |
Foreign Application Data
Date |
Code |
Application Number |
Oct 19, 2005 |
KR |
10-2005-0098759 |
Claims
1. (canceled)
2. A method for processing traffic data at a terminal that includes
a receiver and decoder, the method comprising: receiving, at a
receiver, traffic information; and decoding, at a decoder, the
received traffic information, wherein the traffic information
includes a traffic message comprising a message management
container, an event container and a location container, wherein the
management container includes message identifier (MID) identifying
the traffic massage and a version number of the traffic message,
wherein the location container includes location information
related to a link, wherein the event container has multi-layer
structure comprising a plurality of classes, wherein highest class
of the event container includes a congestion and travel time (CTT)
component and an additional information component, all of which are
respectively allocated different identifiers, wherein the CTT
component has lower class including an average speed component, a
travel time component and a traffic flow component, all of which
are respectively allocated different identifiers, wherein the
additional information component includes a language code and
additional information.
3. The method of claim 2, wherein the message management container
further includes a message generation time element indicating point
of the traffic message generation.
4. The method of claim 2, wherein the message management container
further includes a date and time element.
5. The method of claim 2, wherein the location component includes a
link identifier identifying the link and a descriptor element
related to the link.
6. An apparatus for processing traffic data, the apparatus
comprising: a receiver configured to receive traffic information;
and a decoder configured to decode the received traffic
information, wherein the traffic information includes a traffic
message comprising a message management container, an event
container and a location container, wherein the management
container includes message identifier (MID) identifying the traffic
massage and a version number of the traffic message, wherein the
location container includes location information related to a link,
wherein the event container has multi-layer structure comprising a
plurality of classes, wherein highest class of the event container
includes a congestion and travel time (CTT) component and an
additional information component, all of which are respectively
allocated different identifiers, wherein the CTT component has
lower class including an average speed component, a travel time
component and a traffic flow component, all of which are
respectively allocated different identifiers, wherein the
additional information component includes a language code and
additional information.
7. The method of claim 6, wherein the message management container
further includes a message generation time element indicating point
of the traffic message generation.
8. The method of claim 6, wherein the message management container
further includes a date and time element.
9. The method of claim 6, wherein the location component includes a
link identifier identifying the link and a descriptor element
related to the link.
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application is a continuation of U.S. application Ser.
No. 14/477,395, filed Sep. 4, 2014, now pending, which is a reissue
of U.S. application Ser. No. 11/420,447, filed May 25, 2006, now
U.S. Pat. No. 8,259,815, which claims priority from U.S.
Provisional Application No. 60/684,972 filed May 27, 2005, which
claims priority from Korean Application 10-2005-0098759 filed Oct.
19, 2005, the entire contents of which is incorporated by
reference.
BACKGROUND
[0002] 1. Field
[0003] This disclosure relates to encoding and decoding traffic
information using a field indicative of an encoding scheme.
[0004] 2. Description of the Related Art
[0005] With the advancement in digital signal processing and
communication technologies, radio and TV broadcasts are being
digitalized. Digital broadcasting enables provision of various
information (e.g., news, stock prices, weather, traffic
information, etc.) as well as audio and video content.
SUMMARY
[0006] In one general aspect, a method for identifying traffic
information is provided. The method includes receiving traffic data
including a first identifier, information that is encoded, and
information corresponding to a field indicative of an encoding
scheme. The first identifier enables a determination of a type of
information that is included within the received traffic data. The
method also includes determining a type of information included
within the received traffic data based on the first identifier and
determining encoding information based on the field indicative of
an encoding scheme included in the received traffic data only if
the first identifier enables a determination that the received
traffic data includes a field indicative of an encoding scheme. The
method further includes identifying the information that is encoded
based on the determined encoding information.
[0007] Implementations may include one or more additional features.
For instance, determining encoding information may involve
accessing information provided within the received traffic data and
recognizing that data as the field indicative of an encoding
scheme. Determining encoding information may include using the
received information corresponding to a field indicative of an
encoding scheme to access a reference table and extract a value
associated with a method of encoding. The extracted value may
include an indication of an amount of data per character associated
with the field indicative of encoding scheme. Different values
within the field indicative of an encoding scheme may yield
different extracted values. The indication of an amount of data per
character may be an indication of a number of bytes per character.
The extracted value may include, text and different values within
the field indicative of an encoding scheme may yield different
extracted text. The extracted value may include an indication of an
amount of data per character and associated text that is associated
with field indicative of an encoding scheme. Different values
within the field indicative of an encoding scheme may yield
different extracted values and associated text.
[0008] The method may also include receiving information
corresponding to a message management structure including
information corresponding to a generation time of information
reflected in the traffic data. The generation time included within
the received message management structure may relate to a plurality
of message component structures that correspond to more than one of
a predicted or current traffic tendency, a predicted or current
amount of traffic, a predicted or current speed, a predicted or
current time to traverse a particular link, or a link descriptor
including a field indicative of an encoding mechanism used to
encode the link descriptor. Each message component structure
corresponding to a link descriptor may further include an
identifier specific to the type of information and the first
identifier may be an identifier, in a message component structure,
corresponding to a link descriptor. A plurality of message
component structures corresponding to a link descriptor may be
included, and a single field indicative of an encoding mechanism
may be used to encode the link descriptors. A plurality of message
component structures corresponding to link descriptors may be
included. Each link descriptor may be associated with a field
indicative of an encoding mechanism used to encode the link
descriptor. The plurality of message component structures
corresponding to link descriptors may include the same descriptor
encoded in a plurality of languages or formats.
[0009] Further, in the method, receiving information corresponding
to a field indicative of an encoding scheme may include receiving a
value, associated within a reference table on a receiving device,
with the language or format of a descriptor. Receiving information
corresponding to a field indicative of an encoding scheme may
include receiving a text descriptor corresponding to a specific
link. The text descriptor may be encoded using the encoding method
indicated by the field. Receiving traffic data may include decoding
the traffic data such that the received traffic data is decoded
traffic data. The encoding information may reflect the field
indicative of an encoding scheme.
[0010] In another general aspect, an apparatus for identifying
traffic information is provided. The apparatus includes a decoder
configured to receive traffic data including a first identifier,
information that is encoded, and information corresponding to a
field indicative of an encoding scheme. The first identifier
enables a determination of a type of information that is included
within the received traffic data. The apparatus also includes a
processor configured to determine a type of information included
within the received traffic data based on the first identifier and
determine encoding information based on the field indicative of an
encoding scheme included in the received traffic data only if the
first identifier enables a determination that the received traffic
data includes a field indicative of an encoding scheme. The
processor is also configured to identify the information that is
encoded based on the determined encoding information.
[0011] Implementation may include one or more additional features.
For instance, in the apparatus the processor may be configured to
receive traffic data including information corresponding to a
version number of information reflected in the traffic data. The
version number may be associated with a specific syntax of the data
where any one of multiple syntaxes may be used. The processor may
be configured to receive information corresponding to a message
management structure including information corresponding to a
generation time of information reflected in the traffic data. The
processor may be configured to receive information corresponding to
a data length of the received data.
[0012] In a further general aspect, a traffic information
communication device is provided. The device includes a data
receiving interface configured to receive information that is
encoded. The received information includes a number of descriptor
components. At least one of the descriptor components includes an
encoding scheme component identifier that identifies the descriptor
component as a single one of the descriptor components included
within the descriptor information, and a field indicative of an
encoding scheme identifier configured to identify information
associated with the format or language of the descriptor. The
device also includes a processing device configured to process the
information that is encoded received from the data receiving
interface and to determine descriptor information based at least in
part on the information received.
[0013] The details of one or more implementations are set forth in
the accompanying drawings and the description below. Other features
will be apparent from the description and drawings, and from the
claims.
BRIEF DESCRIPTION OF THE DRAWINGS
[0014] FIG. 1 illustrates a network over which traffic information
is provided;
[0015] FIG. 2 illustrates a format of the traffic information
transmitted by radio;
[0016] FIG. 3 illustrates a transmission format of a congestion
traffic information component included in a CTT event
container;
[0017] FIG. 4 illustrates syntax of an additional information
component included in the CTT event container;
[0018] FIG. 5 illustrates a transmission format of a location
information component included in the CTT event container;
[0019] FIG. 6 illustrates a syntax of a link descriptor which is a
coordinates component including an ID of 02h;
[0020] FIG. 7 illustrates syntax of a character table ID, and a
reference character table index;
[0021] FIGS. 8 and 9 illustrate syntax of an additional information
component and a link descriptor component, each including a field
indicative of the encoding scheme of the character string; and
[0022] FIG. 10 illustrates a structure of a navigation terminal for
receiving traffic information from a server.
DETAILED DESCRIPTION
[0023] One use for digital broadcasts is to satisfy an existing
demand for traffic information. Proposals that involve the use of
digital broadcasts for this purpose contemplate the use of
standardized formatting of traffic information to be broadcast.
This approach may be used to enable the use of traffic information
receiving terminals made by different manufacturers, which each
could be configured to detect and interpret traffic information
broadcast in the same way.
[0024] FIG. 1 schematically depicts a network over which the
traffic information is provided. In the network 101 of FIG. 1, by
way of example, a traffic information providing server 210 of a
broadcasting station may reconfigure various congestion traffic
information aggregated from an operator's input and may broadcast
the reconfigured information by radio so that a traffic information
receiving terminal such as a navigation device installed to a car
200 may receive the information.
[0025] The congestion traffic information broadcast by the traffic
information providing server 100 via radio waves may comprise a
sequence of message segments (hereafter, referred to as Transport
Protocol Expert Group (TPEG) messages) as shown in FIG. 2. Among
the sequence, one message segment, that is, the TPEG message
comprises a message management container 21, a congestion and
travel-time information (CTT or CTI) event container 22, and a TPEG
location container 23. It is noted that a TPEG message 30 conveying
traffic information other than the CTT event, e.g., road traffic
message (RTM) event, public transport information (PTI), weather
information (WEA) may be included in the sequence.
[0026] Overall contents relating to the message may be included in
the message management container 21. Information relating to a
message identification (ID), a version number, date and time, and a
message generation time may be included in the message management
container 21. The CTT event container 22 may include current
traffic information of each link (road section) and additional
information. The TPEG location container 23 may include location
information relating to the link.
[0027] FIG. 3 illustrates an exemplary transmission format of a
congestion traffic information component included in the CTT event
container.
[0028] The CTT event container 22 may comprise a plurality of CTT
components. If the CTT component includes the congestion traffic
information, the CTT component may be assigned an ID of 80h and may
comprise status components indicative of the section mean speed,
the section travel-time, and the retardation. In the description,
specific IDs are described as assignments to structures associated
with specific information. The actual value of an assigned ID
(e.g., 80h) is exemplary, and different implementations may assign
different values for specific associations or circumstances. Thus,
the CTT component may be used to provide various different types of
data that may be signaled based on an identifier. For example, FIG.
2B and FIG. 2C illustrate a component with an identifier of 0x80
and 0x90 signaling, respectfully, status and location
information.
[0029] In various implementations, the ID of 80h is assigned to the
congestion traffic information component, more than one (m-ary)
status components may be included, and a field may be included to
represent the total data size of the included status components in
bytes.
[0030] Status component may include the information relating to the
section mean speed, the section travel-time, and/or the
retardation. An ID of 00 is assigned to the section mean speed, an
ID of 01 is assigned to the section travel-time, and an ID of 02 is
assigned to the retardation.
[0031] In various implementation, if an ID of 8Ah is assigned, the
CTT component may include additional information or auxiliary
information relating to the traffic information in a form, such as,
for example text. FIG. 4 depicts syntax of the additional
information component included in the CTT event container. The
additional information component is assigned the ID of 8Ah as
indicated by 4a, and may comprise a language code indicated by 4c,
additional information configured in text form, i.e., as character
sequence or character string indicated by 4d, and a field
representing the total data size of the components in bytes as
indicated by 4b.
[0032] Since the message carried in the CTT event container is
subordinate to the location information, the CTT message may
include the location information. A transmission target of the TPEG
congestion traffic information may include a TPEG decoder including
no digital map. Also, for the compatibility with an existing
location reference scheme, various location reference schemes may
be adapted. One is a location reference method using coordinates
transmission, and another is a location reference method using a
prescribed node-link ID.
[0033] FIG. 5 depicts a transmission format of the location
information component included in the CTT event container. If the
CTT component includes location information, the CTT component may
be assigned an ID of 90h and may comprise more than one TPEG
location sub-container TPEG_loc_container.
[0034] TPEG location sub-container may comprise one or more TPEG
location components TPEG_log_component, and TPEG location component
may comprise one or more coordinates components including an ID of
00h.
[0035] The coordinates component may carry information relating to
a road type such as highway, state road, and so on (a coordinates
component including an ID of 00h), coordinates component, which may
be represented in, for example, WGS 84 type (a coordinates
component including an ID of 01h), link ID information (a
coordinates component including an ID of 10h), link descriptor (a
coordinates component including an ID of 02h), and direction type
information (a coordinates component including an ID of 03h).
[0036] FIG. 6 depicts a syntax of the link descriptor which is the
coordinates component, according to various implementations,
including the ID of 02h. The coordinates component as to the link
descriptor may be assigned the ID of 02h. as indicated by 6a, and
may comprise a field indicative of an encoding scheme type as
indicated by 6c, a field indicative of an encoding scheme as
indicated by 6d, m-ary descriptor components as indicated by 6e,
and a field presenting the total data size of the component in
bytes as indicated by 6b. The descriptor may consist of a character
string indicative of a geographical name, a building name, a road
name, or a station name to represent the corresponding link.
[0037] According to an implementation, a field indicative of the
encoding scheme of the character string may be appended to the
component which includes the character string. This field may be
recorded as a value (identifier) indicative of a specific encoding
scheme in a table where several prescribed character string
encoding schemes are organized. The table and the identifier used
for the field may conform to a character table and a character
table identifier defined in Annex A of EBU B/TPEG
TPEG-SSF_3.0/002.
[0038] Moreover, through the use of the field, its value, and the
corresponding indicated scheme, a terminal which receives and
displays the traffic information included in the CTT container may
confirm how the character string received together with the traffic
information is encoded, for example, whether Hangul (Korean
language) is encoded to the complete type, the combination type, or
the unicode.
[0039] FIG. 7 depicts, according to various implementations, syntax
of the character table identifier and a reference character table
index that may be defined in Annex A of TPEG-SSF_3.0/002.
<chartab> identifies a number `t` arranged in the reference
character table index so as to confirm the encoding scheme of the
character string and bytes used for one character.
[0040] Accordingly, it is possible to use the encoding scheme
defined in the reference character table index or to define a new
encoding scheme to t=128 through t=255 that a service provider can
freely use, for example, complete Hangul, combination Hangul,
simplified Chinese, traditional Chinese, Japanese and the like.
[0041] FIGS. 8 and 9 depict syntax, according to various
implementations, of the additional information component and the
link descriptor component that include a field indicative of the
encoding scheme of the character string, respectively. In FIGS. 8
and 9, <chartab> is a field where an identifier indicative of
the encoding scheme of the following character string
<short_string> is recorded. Specifically, one number of the
plurality of encoding schemes prescribed in the reference character
table index is recorded.
[0042] The server 100 may configure the current congestion traffic
information and the location information as shown in FIGS. 3 and 5
according to the current traffic information aggregated through
several paths and its stored traffic information database, and may
transmit the configured information to the traffic information
receiving terminal. Additionally, when transmitting a component
including the additional information or the link descriptor in
relation to the traffic information in the form of the character
string, the server 100 may additionally insert an identifier
indicative of the encoding scheme of the character string into the
component as shown in FIGS. 8 and 9.
[0043] When transmitting the same character string in the
multi-language or the several encoding schemes, the server 100 may
transmit separate components which include the same character
string encoded in different encoding schemes. Identifiers
indicative of the encoding schemes of the character string included
in the components are appended to the corresponding components,
respectively.
[0044] FIG. 10 depicts an example structure of a navigation
terminal installed to a vehicle to receive the traffic information
from the server 100. FIG. 10 is an example implementations of a
system for receiving and utilizing traffic information. Other
systems may be organized differently or include different
components.
[0045] In FIG. 10, the navigation terminal comprises a tuner 210, a
demodulator 220, a TPEG decoder 230, a global positioning system
(GPS) module 280, a storage structure 240, an input device 290, a
navigation engine 250, a memory 250a, a display panel 270, and a
panel driver 260. The tuner 210 outputs the modulated traffic
information signal by tuning a signal band over which the traffic
information is transmitted. The demodulator 220 outputs the traffic
information signal by demodulating the modulated traffic
information signal. The TPEG decoder 230 acquires various traffic
information by decoding the demodulated traffic information signal.
The GPS module 280 receives satellite signals from a plurality of
low earth orbit satellites and acquires the current location
(longitude, latitude, and height). The storage structure 240 stores
a digital map including information about links and nodes, and
diverse graphical information. The input device 290 receives a
user's input. The navigation engine 250 controls an output to the
display based on the user's input, the current location, and the
acquired traffic information. The memory 250a temporarily stores
data. The display panel 270 displays video. The display panel 270
may be a liquid crystal display (LCD) or organic light emitting
diodes (OLED). The panel drive 260 applies a driving signal
corresponding to graphical presentation to be displayed to the
display panel 270. The input device 290 may be a touch screen
equipped to the display panel 270.
[0046] The tuner 210 tunes the signal transmitted from the server
100, and the demodulator 220 demodulates and outputs the tuned
signal according to a preset scheme. The TPEG decoder 230 decodes
the demodulated signal to the TPEG message sequence as configured
in FIG. 2, analyzes TPEG messages in the message sequence, and
provides the navigation engine 250 with the necessary information
and/or the control signal according to the message contents.
[0047] The TPEG decoder 230 extracts the data/time and the message
generation time from the message management container in each TPEG
message, and checks whether a subsequent container is the CTT event
container based on the `message element` (i.e. an identifier). If
the CTT event container is following, the TPEG decoder 230 provides
the navigation engine 250 with the information acquired from the
CTT components in the container so that the navigation engine 250
takes charge of the display of the traffic information. Providing
the navigation engine 250 with the information may include
determining, based on identifiers, that the traffic information
includes a message management container including status,
descriptor, or additional information within various message
components within the message management container. The components
may each include different status, descriptor, or additional
information associated with different links or locations and
identifiers associated with the different status, descriptor, or
additional information. The containers and components may also each
include information associated with a generation time, version
number, data length, and identifiers of included information.
[0048] When the additional information component or the link
descriptor component in the CTT container is received, the TPEG
decoder 230 may provide the navigation engine 250 with the encoding
scheme, together with the extracted character string, corresponding
to the field value indicative of the encoding scheme so that the
character string included in the component may be displayed in
conformity with the encoding scheme. To this end, the TPEG decoder
230 manages the reference character table index which defines the
encoding scheme of the character string.
[0049] The TPEG decoder 230 may acquire location information
corresponding to the current traffic information from the
subsequent TPEG location container. According to the type
information of the TPEG location container, the location
information may coordinate (longitude and latitude) of start and
end points or the link, i.e., the link ID assigned to the road
section.
[0050] When the storage structure 240 is equipped, the navigation
engine 250 may specify a section corresponding to the received
information in reference to the information relating to the links
and the nodes in the storage structure 240, and, may, utilize the
coordinates of the received link by converting the coordinates to
the link ID or converting the link ID to the coordinates.
[0051] The navigation engine 250 may read out from the storage
structure 240 the digital map of a certain area based on the
current coordinates which may be received from the GPS module 280,
and may display the digital map on the display panel 270 via the
panel drive 260. In doing so, the place corresponding to the
current location may be marked by a specific graphical symbol.
[0052] The navigation engine 250 may control display of the section
mean speed information received from the TPEG decoder 230 in the
section corresponding to the coordinates or the link ID of the
location container which follows the container carrying the section
mean speed information. The section mean speed may be displayed,
for example, by changing colors or indicating numbers to the
corresponding sections. By way of example of the ordinary road, the
red denotes 0.about.10 km/h, the orange denotes 10.about.20 km/h,
the green denotes 20.about.40 km/h, and the blue denotes more than
40 km/h.
[0053] A terminal without the storage structure 240 storing the
digital map may display the section mean speed by colors or by
numbers with respect to only links ahead of the current path. In
case that the path of the vehicle including the navigation terminal
is designated in advance, the section mean speed may be displayed
only with respect to the links along the path, rather than the
links ahead.
[0054] According to the user's request, the navigation engine 250
may control the display panel 270 to display the section
travel-time and the retardation of links received from the TPEG
decoder 230, instead of or together with the section mean
speed.
[0055] The navigation engine 250 may receive from the TPEG decoder
230 the information as to the encoding scheme of the character
string in the additional information component or the link
descriptor component, converts the character string extracted from
the additional information component or the link descriptor
component according to the encoding scheme, and may display the
converted character string on the display panel 270. If a user
designates a specific language or encoding scheme, the navigation
engine 250 may selectively convert and display the character string
of the designated encoding scheme amongst the character strings
extracted from the several additional information components or
link descriptor components.
[0056] In light of the foregoing as set forth above, according to
the present invention, the character information relating to the
traffic may be provided in the multi-language using different
character sets, and the information indicative of the display of
the transmitted character using which character set may be
provided.
[0057] Furthermore, since the traffic-related information is
provided in the multi-language without modifying the TPEG standard,
the TPEG standard may be expanded.
[0058] The foregoing description has been presented for purposes of
illustration. Thus, various implementations with improvements,
modifications, substitutions, or additions within the spirit and
scope as defined by the following appended claims.
* * * * *