WO2006123890A1 - Providing traffic information relating to a prediction of speed on a link and using the same - Google Patents

Providing traffic information relating to a prediction of speed on a link and using the same Download PDF

Info

Publication number
WO2006123890A1
WO2006123890A1 PCT/KR2006/001836 KR2006001836W WO2006123890A1 WO 2006123890 A1 WO2006123890 A1 WO 2006123890A1 KR 2006001836 W KR2006001836 W KR 2006001836W WO 2006123890 A1 WO2006123890 A1 WO 2006123890A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
travel speed
prediction
link
traffic data
Prior art date
Application number
PCT/KR2006/001836
Other languages
French (fr)
Inventor
Joon Hwi Lee
Chu Hyun Seo
Young In Kim
Mun Ho Jung
Original Assignee
Lg Electronics Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Lg Electronics Inc. filed Critical Lg Electronics Inc.
Priority to CN2006800168330A priority Critical patent/CN101228566B/en
Priority to DE602006010998T priority patent/DE602006010998D1/en
Priority to MX2007014604A priority patent/MX2007014604A/en
Priority to EP06747435A priority patent/EP1886294B1/en
Priority to BRPI0610741A priority patent/BRPI0610741B1/en
Priority to AT06747435T priority patent/ATE451679T1/en
Priority to CA2608700A priority patent/CA2608700C/en
Priority to KR1020077027148A priority patent/KR101236521B1/en
Publication of WO2006123890A1 publication Critical patent/WO2006123890A1/en

Links

Classifications

    • GPHYSICS
    • G08SIGNALLING
    • G08GTRAFFIC CONTROL SYSTEMS
    • G08G1/00Traffic control systems for road vehicles
    • G08G1/09Arrangements for giving variable traffic instructions
    • G08G1/091Traffic information broadcasting
    • G08G1/092Coding or decoding of the information
    • EFIXED CONSTRUCTIONS
    • E06DOORS, WINDOWS, SHUTTERS, OR ROLLER BLINDS IN GENERAL; LADDERS
    • E06BFIXED OR MOVABLE CLOSURES FOR OPENINGS IN BUILDINGS, VEHICLES, FENCES OR LIKE ENCLOSURES IN GENERAL, e.g. DOORS, WINDOWS, BLINDS, GATES
    • E06B3/00Window sashes, door leaves, or like elements for closing wall or like openings; Layout of fixed or moving closures, e.g. windows in wall or like openings; Features of rigidly-mounted outer frames relating to the mounting of wing frames
    • E06B3/32Arrangements of wings characterised by the manner of movement; Arrangements of movable wings in openings; Features of wings or frames relating solely to the manner of movement of the wing
    • E06B3/34Arrangements of wings characterised by the manner of movement; Arrangements of movable wings in openings; Features of wings or frames relating solely to the manner of movement of the wing with only one kind of movement
    • E06B3/42Sliding wings; Details of frames with respect to guiding
    • E06B3/46Horizontally-sliding wings
    • E06B3/4609Horizontally-sliding wings for windows
    • EFIXED CONSTRUCTIONS
    • E06DOORS, WINDOWS, SHUTTERS, OR ROLLER BLINDS IN GENERAL; LADDERS
    • E06BFIXED OR MOVABLE CLOSURES FOR OPENINGS IN BUILDINGS, VEHICLES, FENCES OR LIKE ENCLOSURES IN GENERAL, e.g. DOORS, WINDOWS, BLINDS, GATES
    • E06B3/00Window sashes, door leaves, or like elements for closing wall or like openings; Layout of fixed or moving closures, e.g. windows in wall or like openings; Features of rigidly-mounted outer frames relating to the mounting of wing frames
    • E06B3/30Coverings, e.g. protecting against weather, for decorative purposes
    • E06B3/301Coverings, e.g. protecting against weather, for decorative purposes consisting of prefabricated profiled members or glass
    • E06B3/306Covering plastic frames with metal or plastic profiled members
    • GPHYSICS
    • G08SIGNALLING
    • G08GTRAFFIC CONTROL SYSTEMS
    • G08G1/00Traffic control systems for road vehicles
    • G08G1/09Arrangements for giving variable traffic instructions
    • G08G1/0962Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
    • G08G1/0968Systems involving transmission of navigation instructions to the vehicle
    • G08G1/0969Systems involving transmission of navigation instructions to the vehicle having a display in the form of a map
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04HBROADCAST COMMUNICATION
    • H04H20/00Arrangements for broadcast or for distribution combined with broadcast
    • H04H20/53Arrangements specially adapted for specific applications, e.g. for traffic information or for mobile receivers
    • H04H20/55Arrangements specially adapted for specific applications, e.g. for traffic information or for mobile receivers for traffic information
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12Discovery or management of network topologies
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/14Network analysis or design
    • H04L41/147Network analysis or design for predicting network behaviour
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing data switching networks
    • H04L43/08Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0852Delays
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02Services making use of location information
    • H04W4/025Services making use of location information using location based information parameters
    • H04W4/027Services making use of location information using location based information parameters using movement velocity, acceleration information
    • EFIXED CONSTRUCTIONS
    • E05LOCKS; KEYS; WINDOW OR DOOR FITTINGS; SAFES
    • E05YINDEXING SCHEME RELATING TO HINGES OR OTHER SUSPENSION DEVICES FOR DOORS, WINDOWS OR WINGS AND DEVICES FOR MOVING WINGS INTO OPEN OR CLOSED POSITION, CHECKS FOR WINGS AND WING FITTINGS NOT OTHERWISE PROVIDED FOR, CONCERNED WITH THE FUNCTIONING OF THE WING
    • E05Y2600/00Mounting or coupling arrangements for elements provided for in this subclass
    • E05Y2600/60Mounting or coupling members; Accessories therefore
    • E05Y2600/62Bolts
    • EFIXED CONSTRUCTIONS
    • E05LOCKS; KEYS; WINDOW OR DOOR FITTINGS; SAFES
    • E05YINDEXING SCHEME RELATING TO HINGES OR OTHER SUSPENSION DEVICES FOR DOORS, WINDOWS OR WINGS AND DEVICES FOR MOVING WINGS INTO OPEN OR CLOSED POSITION, CHECKS FOR WINGS AND WING FITTINGS NOT OTHERWISE PROVIDED FOR, CONCERNED WITH THE FUNCTIONING OF THE WING
    • E05Y2800/00Details, accessories and auxiliary operations not otherwise provided for
    • E05Y2800/10Additional functions
    • E05Y2800/12Sealing
    • EFIXED CONSTRUCTIONS
    • E05LOCKS; KEYS; WINDOW OR DOOR FITTINGS; SAFES
    • E05YINDEXING SCHEME RELATING TO HINGES OR OTHER SUSPENSION DEVICES FOR DOORS, WINDOWS OR WINGS AND DEVICES FOR MOVING WINGS INTO OPEN OR CLOSED POSITION, CHECKS FOR WINGS AND WING FITTINGS NOT OTHERWISE PROVIDED FOR, CONCERNED WITH THE FUNCTIONING OF THE WING
    • E05Y2800/00Details, accessories and auxiliary operations not otherwise provided for
    • E05Y2800/40Protection
    • E05Y2800/422Protection against vibration or noise

Definitions

  • TECHNICAL FIELD This disclosure relates to providing traffic information relating to a prediction of speed on a link and using the same
  • Digital broadcasting enables provision of various information (e.g., news, stock prices, weather, traffic information, etc) as well as audio and video content.
  • a method for identifying traffic information includes receiving traffic data including a first identifier, information corresponding to a prediction of travel speed for a particular link, and information corresponding to a location associated with the particular link.
  • the first identifier enables a determination of a type of the 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 travel speed prediction information based on the information included in the received traffic data only if the first identifier enables a determination that the received traffic data includes a prediction related to travel speed.
  • the method further includes determining location information based on the information that is included in the received traffic data corresponding to the location associated with the particular link and identifying traffic information based on the determined travel speed prediction information and the determined location information.
  • Implementations may include one or more additional features. For instance, determining travel speed prediction information may include accessing received data reflecting, among other items, results of measurements made with respect to traffic previously traversing the link, and computing a prediction for a future travel speed based on the received data. Determining travel speed prediction information may involve accessing information provided within the received traffic data and recognizing that data as the predicted travel speed.
  • 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, or a predicted or current time to traverse a particular link.
  • Each message component structure may further include an identifier specific to the type of information and the first identifier may be an identifier, in a message component structure, specific to the prediction of travel speed for the particular link.
  • Information corresponding to a chronological indication associated with the predicted travel speed revealed by the received information may be received. The chronological indication may reflect a particular time of day for which the predicted The chronological indication may be reflected using the universal time co-ordinated standard.
  • the method may also include determining the travel speed prediction information and the location information in a single step.
  • the location information may be determined before the travel speed prediction information is determined.
  • Receiving traffic data may include decoding the traffic data such that the received traffic data is decoded traffic data.
  • the prediction of travel speed may reflect an average of more than one indication of travel speed associated with the link.
  • the prediction of travel speed may reflect a weighted summation of more than one indication of travel speed associated with the link.
  • the predicted travel speed may be reflected in one of kilometers per hour and miles per hour.
  • Receiving information corresponding to a prediction of travel speed may include receiving a predicted travel speed for the link including a text descriptor.
  • the information corresponding to a prediction of travel speed for a particular link may reflect the predicted travel speed.
  • an apparatus for identifying traffic information includes an interface configured to receive traffic data including a first identifier, information corresponding to a prediction of travel speed for a particular link, and information corresponding to a location associated with the particular link.
  • the first identifier enables a determination of a type of the 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 dependent upon whether the first identifier enables a determination that the received traffic data includes a prediction related to a travel speed, determine travel speed prediction information based on the information included in the received traffic data.
  • the processor is further configured to determine location information based on the information that is included in the received traffic data corresponding to the location corresponding to the particular link and identify traffic information based on the determined travel speed prediction information and the determined location information.
  • Implementations may include one or more additional features.
  • 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.
  • the processor may be configured to receive the predicted travel speed reflected as one value in a set of possible values.
  • the processor may be further configured to determine the prediction of travel speed for a particular link only if the first identifier reveals that the traffic data relates to a prediction of travel speed for a particular link.
  • an apparatus for identifying traffic information includes means for an interface configured to receive traffic data including a first identifier, information corresponding to a prediction of travel speed for a particular link, and information corresponding to a location associated with the particular link. The first identifier enables a determination of a type of the information that is included within the received traffic data.
  • the apparatus also includes means for determining a type of information included within the received traffic data based on the first identifier and means for determining travel speed prediction information based on the information included in the received traffic data only if the first identifier enables a determination that the received traffic data includes a prediction related to a travel speed.
  • the apparatus further includes means for determining location information based on the information that is included in the received traffic data corresponding to the location corresponding to the particular link and means for identifying traffic information based on the determined travel speed prediction information and the determined location information.
  • FIG. 1 illustrates a schematic diagram of a network through which traffic information is provided
  • FIG. 2a illustrates a syntax of wirelessly transmitted traffic information
  • FIG. 2b illustrates a syntax of TPEG-CTT messages
  • FIG. 2c shows syntax of formats of components carrying congestion status information
  • FIGS. 2d and 2e show syntax of a CTT component carrying CTT events and location information, respectively;
  • FIG. 2f shows syntax of a CTT component carrying additional information of congestion status information;
  • FIG. 3a illustrates a syntax of the traffic/congestion information included in the CTT event container
  • FIGS. 3b through 3e illustrate syntaxes of the average link speed, the link travel time, the link delay, and the congestion type included in the status component shown in FIG. 3a, respectively
  • FIG. 4a illustrates a syntax of the traffic/congestion prediction information included in the CTT event container
  • FIGS. 4b through 4d illustrate syntaxes of the predicted average link speed, the predicted link travel time, and the tendency information included in the status component shown in FIG. 4a, respectively;
  • FIG. 5a illustrates an example of a database storing the history of traffic status at each link for providing the traffic/congestion prediction information
  • FIG. 5b illustrates an example of a graphical user interface configured to predict the average speed at a specific link using the database shown in FIG. 5a;
  • FIG. 6 illustrates a block diagram of a navigation terminal installed in a car for receiving traffic information transmitted from a server in accordance with one implementation
  • FIGS. 7a through 7c illustrate examples of graphical user interfaces configured to display the average speed at each link.
  • FIG. 8 illustrates an example of a graphical user interface configured to display the average speed predicted for a selected link.
  • One such 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.
  • FIG. 1 is a schematic diagram of a network through which traffic information is provided.
  • a traffic information providing server 100 in a broadcast station may transmit traffic information collected from various sources (e.g., operator input, or information received from another server or probe cars through a network 101) wirelessly so that a traffic information receiving terminal (e.g., navigation system installed in a car 200) may receive the traffic information.
  • sources e.g., operator input, or information received from another server or probe cars through a network 101
  • a traffic information receiving terminal e.g., navigation system installed in a car 200
  • the traffic information wirelessly transmitted from the traffic information providing server 100 may be a sequence of TPEG-CTT (transport protocol expert group-congestion and travel-time Information) messages.
  • a message segment of the sequence i.e., a TPEG-CTT message, whose syntax is shown in FIG. 2b, may include a message management container 21, a CTT event container (or Application Event Container) 22, and TPEG-CTT location container 23.
  • the TPEG-CTT message may also include different type of containers other than, less than, or in addition to the CTT event container as in the TPEG-CTT message 30.
  • the message management container 21 may be used for managing date and time information.
  • the time information may include message generation time (e.g., a chronological time indication) .
  • the message generation time may be included in every TPEG-CTT message when the corresponding message is transmitted.
  • the CTT event container 22 may include congestion and travel time status and predicted congestion and travel time status of links, i.e., road segments.
  • the congestion and travel time status may include average link speed, link travel time, link delay, or congestion type, etc.
  • the TPEG-CTT location container 23 may employ various location reference processes. For example, a rocation reference process using a coordinate system or a location reference process using pre-promised links may be used. When a coordinate system is used, the coordinates (latitudes and longitudes) of the start and end positions of a link for which the TPEG-CTT message is created, may be transmitted. When a reference process using pre-promised links is used, a unique identification for a specific link on a receiving device may be transmitted. For example, a receiving device may include a locally stored network of links, wherein each link may be identified by a unique identifier. A link may refer to a road segment which starts and ends at junctions and has no junction in between.
  • the coordinate system may be the WGS 84 model.
  • a text formatted name of the link may be transmitted.
  • a CTT event container and a TPEG-CTT location container are composed of one or more CTT components 201.
  • Each of CTT components may be constructed according to the syntax shown in FIG. 2d if it carries congestion status information while it may be constructed according to the syntax shown in FIG. 2e if the component carries location information.
  • a CTT event container 22 may be composed of one component or a plurality of CTT components.
  • CTT components including an ID of 8Oh (notation 'h' means hexadecimal) or 84h includes one or more status components including basic traffic information such as the average link speed, link travel time, link delay, or congestion type.
  • IDs are described as assignments to structures associated with specific information. The actual value of an assigned ID (e.g., 8Oh) is exemplary, and different implementations may assign different values for specific associations or circumstances.
  • CTT components including an ID of 8Ih include one or more status components including predicted CTT status.
  • the predicted CTT status may include predicted average link speed, predicted link travel time, or congestion acceleration tendency.
  • the congestion acceleration tendency may include information indicative of the tendency of congestion status.
  • the congestion acceleration tendency will be described as a type of prediction information as the congestion status in the near future may be predicted from it.
  • the TPEG-CTT message may include CTT components structured as FIG. 2f to deliver additional information of traffic information. As shown, an identifier 8Ah may be assigned to the CTT component carrying additional information, and a language code that is indicative of language used for the additional information may also be included in the CTT component.
  • FIG. 3a shows an example of a syntax of the CTT component included in the CTT event container, which delivers the current congestion and travel time status.
  • the CTT component may be assigned an ID 3a including a value of 8Oh or 84h and may include m status components 3c and a field 3b indicative of the length of the data included in the status components included therein, the length being expressed in the unit of byte. Other units, such as bit, may be used.
  • the status components 3c may include information on the average link speed, the link travel time, the link delay, and/or the congestion type.
  • status components delivering the average link speed, the link travel time, the link delay, and the congestion type are assigned IDs of 1 OO', 1 Ol', v 02', and '03', respectively.
  • the link delay may be, for example, the delay in the time required to pass through the link under current traffic condition with respect to the time required to pass through the link at a limit speed specified in the link.
  • the link delay may be expressed in the unit of minute, second, tens or tenths of seconds, or another unit.
  • the link delay may be calculated with respect to the average time required to pass the link on the same days or in the same time slot.
  • the link delay may enable traffic information receiving terminals that do not have information on each link (e.g., speed limit in the link, length of the link, etc) to expect the time required to pass a link.
  • FIG. 4a shows an example of a syntax of the CTT component included in the CTT event container, which delivers the predicted congestion and travel time status.
  • the CTT component may be assigned an ID 4a including a value of 81h and may include m status components 4c and a field 4b indicative of the length of the data included in the status components included therein, the length, may be, for example, expressed in the unit of byte.
  • the status components 4c may include information on the predicted average link speed, the predicted link travel time, and/or, the congestion acceleration tendency, the syntax, according to one implementation, of each of which, is shown in FIGS. 4b, 4c, and 4d, respectively.
  • the status components delivering the predicted average link speed, the predicted link travel time, and the congestion acceleration tendency may be assigned IDs of ⁇ 00', '01', and ⁇ 02', respectively.
  • the predicted congestion and travel time status may be delivered by the CTT component that delivers the current congestion and travel time status (e.g., average link speed, link travel time, link delay, congestion type) including an ID of 8Oh or 84h.
  • the status components delivering the predicted congestion and travel time status may be assigned IDs different from the IDs of the status components delivering the current congestion and travel time status.
  • the server 100 may create predicted status information shown, according to one implementation, in FIGS. 4b through 4d based on the traffic information which may be collected from various sources and/or its own traffic information database, which will be described in detail below.
  • the server 100 may store the average speed at each link according to day, time slot, week, month, or year. For example, in one implementation, the server 100 may store the average speed at each link at intervals, such as every 30 minutes, as shown in FIG. 5a.
  • the unit of the values shown in FIG. 5a is km/h, though other units, such as m/s, may be used.
  • the server 100 may store the average speed, or other information, such as travel time or congestion, of links for which the traffic information is currently provided at intervals for a predetermined period of time (e.g., 3 hours) and compare the pattern of change in the average speed for the period of time with the pattern of change in the same time slot of the same day stored in the database. For example, if FIG. 5b shows the pattern of change in the average speed for the past 3 hours from 4:30 pm on a Monday afternoon (A) , the server 100 compares the data with the average speeds of from 1:30 pm to 4:30 pm stored in the database (B) .
  • a predetermined period of time e.g. 3 hours
  • the server 100 reads the average speed Bl at 30 minutes after the current time (i.e., the average speed at 5:00 pm) from the database and transmits the value as the predicted average speed in the corresponding link according to the syntax shown in FIG. 4b.
  • the predicted average link speed may be expressed in the unit of km/h, for example.
  • the predicted time e.g., 5:00 pm in the previous example
  • UTC Universal Time Coordinated
  • the predicted time in UTC format may be indicative of a target time or date in the future, and the predicted speed indicates average speed (in km/h, for example) on a link at the target time or date, such as, a day of year, month of year, year, holiday, time of day, rush hour, event, morning/afternoon/evening.
  • the link may be an inter-road between cities, a bridge, or a road between intersections.
  • the data may be incorporated into the component in units of a byte unit, and/or it may be incorporated in units of a bit or a long byte, according to data size.
  • the speed may be expressed in various units, for example, m/sec, mile/hour, etc.
  • the server 100 may not provide the predicted average link speed, or alternatively, the server 100 may estimate the predicted average link speed Al from the average link speeds extracted for the past 3 hours and provide the estimated value as the predicted average link speed.
  • Various processes may be used to estimate the average speed from the measured average speed values.
  • One process for example, involves calculation of a weighted sum which gives the latest sample value the highest weight and gives the oldest sample value the lowest weight. For example, the predicted speed Al in FIG.
  • 5b can be extracted by calculating 0.5 x current speed + 0.2 x speed of 30 minutes ago + 0.1 x speed of 1 hour ago + 0.1 x speed of 1.5 hours ago + 0.05 x speed of 2 hours ago + 0.05 x 2.5 hours ago, etc.
  • the server 100 may calculate the predicted travel time of each link and transmit the predicted travel time of each link along with associated predicted time according to the syntax shown in FIG. 4c.
  • the predicted travel time may be calculated by multiplying the predicted average speed at each link by the length of the corresponding link stored in the database.
  • the predicted travel time may be expressed in the unit of minutes, tens of seconds, second, or a unit smaller than seconds, for example.
  • the server 100 may compare the current average speed with the average speed at the previous time slot and provide the tendency of change in the average link speeds 41 according to the syntax shown in FIG. 4d.
  • the information which is called the congestion acceleration tendency, may have one value among several values defined by a table shown in FIG. 4d. For example, the information may be assigned 1 if the current average speed is higher than the average speed of 30 minutes ago. The congestion acceleration tendency may be assigned 2 if the current average speed is lower than the average speed of 30 minutes ago. The congestion acceleration tendency may be assigned 3 if the average speed remains unchanged. If there is no available data to compare, the congestion acceleration tendency may be assigned 0.
  • the congestion acceleration tendency information may enable a driver to choose a route that shows improvement in the traffic congestion from among several possible routes showing similar average speeds.
  • the server 100 may provide the rate of change of the average speed, i.e., the slope in the graph shown in FIG. 5b as the congestion acceleration tendency, or other indicia or descriptors .
  • the server 100 may prevent the size of information which it should transmit from becoming excessively large by maintaining the ratio of the current congestion and travel time status to the predicted congestion and travel time status below an appropriate level (e.g., 3:1) .
  • an appropriate level e.g. 3:1
  • FIG. 6 is an example of a block diagram of a navigation terminal for receiving traffic information transmitted from the server 100.
  • Figs. 6-8 are example implementations of systems for receiving and utilizing traffic information, and interfaces used to output information generated by such systems. Other systems may be organized differently or include different components. As illustrated by Fig.
  • the navigation terminal includes a tuner 1 for receiving modulated traffic information signals by resonating at the required frequency band, a demodulator 2 for outputting traffic information signals by demodulating the modulated signals from the tuner 1, a TPEG- CTT decoder 3 for extracting traffic information by decoding the demodulated traffic information signals, a GPS module 8 for calculating the current position (i.e., latitude, longitude, and altitude) by receiving signals from a plurality of low-orbit satellites, storage structure 4 for storing various graphic data and an electronic map including information on links and nodes, an input device 9 for receiving user input, a navigation engine 5 for controlling screen display based on the user input, the current position, and extracted traffic information, a memory 5a for storing data temporarily, an LCD panel 7 for displaying data, and an LCD drive 6 for driving the LCD panel 7 according to data to be presented.
  • a tuner 1 for receiving modulated traffic information signals by resonating at the required frequency band
  • a demodulator 2 for outputting traffic information signals
  • the input unit 9 may be a touch screen incorporated into the LCD panel 7.
  • the tuner 1 tunes to the frequency of the signals transmitted by the server 100 and the demodulator 2 demodulates the tuned signals in a predetermined manner.
  • the TPEG-CTT decoder 3 decodes the demodulated signals into a TPEG-CTT message sequence as shown in FIG. 2, interprets each TPEG message included in the TPEG-CTT message sequence, and sends necessary information and/or control signals to the navigation engine 5.
  • the following description focuses on basic congestion and travel time status shown in FIGS. 3b through 3e and predicted congestion and travel time status shown in FIGS. 4b through 4d though other status information is involved, such as, for example, speed, is involved.
  • the TPEG-CTT decoder 3 extracts date/time and message generation time included in the message management container of each TPEG message and determines if the following container is a CTT event container based on 'message element' information (i.e. an identifier) . If it is determined that the following container is a CTT event container, the TPEG-CTT decoder 3 provides the navigation engine 5 with the information extracted from the CTT component included in the CTT event container so that the navigation engine 5 may display congestion and travel time status and predicted congestion and travel time status, which will be described below.
  • Providing the navigation engine 5 with the information may include determining, based on identifiers, that the traffic information includes a message management container including status information within various message components within the message management container.
  • the components may each include different status information associated with different links or locations and identifiers associated with the different status information.
  • the containers and components may each include information associated with a generation time, version number, data length, and identifiers of included information.
  • the TPEG-CTT decoder 3 then extracts information on the link location for which the previously extracted information is intended from the following TPEG-CTT location container.
  • the position information may be, for example, the coordinates (i.e., latitudes and longitudes) of the start and end positions or an ID that is uniquely assigned to each link, depending on the type of the TPEG-CTT location container.
  • the navigation engine 5 finds the location of the link for which the received traffic information is intended with reference to the information on each link and node stored in the storage structure 4.
  • the navigation engine 5 may convert the coordinates of a link into a link ID or vice versa.
  • the navigation engine 5 reads a part of the electronic map centered around the position coordinates received from the GPS module 8 from the storage structure 4 and displays the map on the LCD panel 7 via the LCD drive 6. A particular graphic symbol is displayed at the location corresponding to the current position on the LCD panel 7.
  • the navigation engine 5 displays the average link speed received from the TPEG-CTT decoder 3 at a location corresponding to the coordinates or link ID delivered via the TPEG-CTT location container following the container delivering the average link speed.
  • the navigation engine 5 may show links in different colors according to the average speed at the links as shown in FIGS. 7a and 7b, where the colors red, orange, green, and blue (colors themselves not shown) may be used to indicate average speeds of 0-10 km, 10-20 km, 20-40 km, over 40 km, respectively.
  • the navigation engine 5 may show the average link speed in numbers at each link as shown in FIG. Ic 1 or a combination of colors and numbers may be used.
  • the navigation engine 5 may use similar display tools to display the congestion acceleration tendency received from the TPEG-CTT decoder 3 at the corresponding link, or through the use of other display tools such as through the use of an icon or a string (e.g., 'improved' if the value of the congestion acceleration tendency is 1 and 'deteriorated' if the value is 2) .
  • the navigation engine 5 maintains the status unchanged if the value of the congestion acceleration tendency is 0 or 3. If the congestion acceleration tendency is received in the form of the rate of change of the average speed, the navigation engine 5 displays the value only when a request from the user is received to prevent visual confusion of the . user.
  • the rate of change may be displayed together for a user- chosen route or a front link.
  • the terminal may show the average link speed at links located in front of the current position in different colors, as shown in FIG. 7b, or in numbers, as shown in FIG. 7c. If the route of the vehicle with the navigation terminal installed is determined, the navigation terminal may show the average speed at the links included in the determined route instead of the links located in front of the current position.
  • the navigation engine 5 responsive to user input, may display the link travel time, the link delay, and the congestion type received from the TPEG-CTT decoder 3 on the LCD panel 7 instead of or simultaneously with the average link speed.
  • the navigation engine 5 displays the predicted average link speed at each link received from the TPEG-CTT decoder 3 in colors or in numbers instead of the current average link speed. In this case, the colors or numbers describing the predicted status may be displayed simultaneously with the current average link speed but the -location or used colors may be different. If the user switches the display mode to see the predicted link travel time instead of the predicted average link speed, the navigation engine 5 displays the predicted link travel time on the electronic map or graphics on the LCD panel 7.
  • the navigation engine 5 may search or research the desirable route based on the received predicted average link speed or predicted link travel time. For example, the navigation engine 5 finds the shortest time path to the destination by using the predicted link average time or predicted link travel time at each link to be reached 30 minutes later at the current speed.
  • the terminal in FIG. 6 may audibly output the received predicted status or congestion tendency information for a specified link or links.
  • the information and/or control signals received from the TPEG-CTT decoder 3 are temporarily stored in the rewritable memory 5a and used by the navigation engine 5.
  • the navigation engine 5 may store the average link speed or link travel time at intervals of, such as, for example, 20 minutes (e.g., 1:00, 1:20, 1:40) for the last 1 hour.
  • the interval of storage may differ depending on the storage capacity of the memory 5a.
  • the navigation engine 5 controls the LCD drive 6 so that the history of the average link speed or the history of the link travel time at the specified link is displayed as a graph shown in FIG. 8.
  • the unit of the displayed numbers is km/h and the name 81 of the link is displayed on the graph.
  • the link name is received along with the coordinates of the link or link ID through the TPEG location container 23 or included in the electronic map stored in the storage structure 4.
  • the current congestion status, predicted congestion status, or other status may be displayed in other ⁇ or different ways.
  • the navigation engine 5 may predict the average speed using the current average speed and the history of the average link speed stored in the memory 5a and display the predicted average link speed, as shown in PIG. 8a.
  • the method for predicting the average link speed may be the same as the aforementioned prediction method executed in the server 100.

Abstract

A method for identifying traffic information is provided. The method includes receiving traffic data including a first identifier, information corresponding to a prediction of travel speed for a particular link, and information corresponding to a location associated with the particular link. The first identifier enables a determination of a type of the 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 travel speed prediction information based on the information included in the received traffic data only if the first identifier enables a determination that the received traffic data includes a prediction related to travel speed. The method further includes determining location information based on the information that is included in the received traffic data corresponding to the location associated with the particular link and identifying traffic information based on the determined travel speed prediction information and the determined location information.

Description

D E S C R I P T I O N
PROVIDING TRAFFIC INFORMATION RELATING TO A PREDICTION OF SPEED ON A LINK AND USING THE SAME
1. TECHNICAL FIELD This disclosure relates to providing traffic information relating to a prediction of speed on a link and using the same,
2. BACKGROUND ART
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.
3. DISCLOSURE OF INVENTION
In one general aspect, a method for identifying traffic information is provided. The method includes receiving traffic data including a first identifier, information corresponding to a prediction of travel speed for a particular link, and information corresponding to a location associated with the particular link. The first identifier enables a determination of a type of the 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 travel speed prediction information based on the information included in the received traffic data only if the first identifier enables a determination that the received traffic data includes a prediction related to travel speed. The method further includes determining location information based on the information that is included in the received traffic data corresponding to the location associated with the particular link and identifying traffic information based on the determined travel speed prediction information and the determined location information. Implementations may include one or more additional features. For instance, determining travel speed prediction information may include accessing received data reflecting, among other items, results of measurements made with respect to traffic previously traversing the link, and computing a prediction for a future travel speed based on the received data. Determining travel speed prediction information may involve accessing information provided within the received traffic data and recognizing that data as the predicted travel speed. 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, or a predicted or current time to traverse a particular link. Each message component structure may further include an identifier specific to the type of information and the first identifier may be an identifier, in a message component structure, specific to the prediction of travel speed for the particular link. Information corresponding to a chronological indication associated with the predicted travel speed revealed by the received information may be received. The chronological indication may reflect a particular time of day for which the predicted The chronological indication may be reflected using the universal time co-ordinated standard. The method may also include determining the travel speed prediction information and the location information in a single step. The location information may be determined before the travel speed prediction information is determined. Receiving traffic data may include decoding the traffic data such that the received traffic data is decoded traffic data. Further, in the method, the prediction of travel speed may reflect an average of more than one indication of travel speed associated with the link. The prediction of travel speed may reflect a weighted summation of more than one indication of travel speed associated with the link. The predicted travel speed may be reflected in one of kilometers per hour and miles per hour. Receiving information corresponding to a prediction of travel speed may include receiving a predicted travel speed for the link including a text descriptor. The information corresponding to a prediction of travel speed for a particular link may reflect the predicted travel speed.
In another general aspect, an apparatus for identifying traffic information is provided. The apparatus includes an interface configured to receive traffic data including a first identifier, information corresponding to a prediction of travel speed for a particular link, and information corresponding to a location associated with the particular link. The first identifier enables a determination of a type of the 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 dependent upon whether the first identifier enables a determination that the received traffic data includes a prediction related to a travel speed, determine travel speed prediction information based on the information included in the received traffic data. The processor is further configured to determine location information based on the information that is included in the received traffic data corresponding to the location corresponding to the particular link and identify traffic information based on the determined travel speed prediction information and the determined location information.
Implementations may include one or more additional features. For instance, 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. The processor may be configured to receive the predicted travel speed reflected as one value in a set of possible values. Also, in the apparatus, the processor may be further configured to determine the prediction of travel speed for a particular link only if the first identifier reveals that the traffic data relates to a prediction of travel speed for a particular link. In another general aspect, an apparatus for identifying traffic information is provided. The apparatus includes means for an interface configured to receive traffic data including a first identifier, information corresponding to a prediction of travel speed for a particular link, and information corresponding to a location associated with the particular link. The first identifier enables a determination of a type of the information that is included within the received traffic data. The apparatus also includes means for determining a type of information included within the received traffic data based on the first identifier and means for determining travel speed prediction information based on the information included in the received traffic data only if the first identifier enables a determination that the received traffic data includes a prediction related to a travel speed. The apparatus further includes means for determining location information based on the information that is included in the received traffic data corresponding to the location corresponding to the particular link and means for identifying traffic information based on the determined travel speed prediction information and the determined location information.
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.
4. BRIEFDESCRIPTIONOFDRAWINGS
The accompanying drawings illustrate various implementations . In the drawings :
FIG. 1 illustrates a schematic diagram of a network through which traffic information is provided;
FIG. 2a illustrates a syntax of wirelessly transmitted traffic information; FIG. 2b illustrates a syntax of TPEG-CTT messages;
FIG. 2c shows syntax of formats of components carrying congestion status information;
FIGS. 2d and 2e show syntax of a CTT component carrying CTT events and location information, respectively; FIG. 2f shows syntax of a CTT component carrying additional information of congestion status information;
FIG. 3a illustrates a syntax of the traffic/congestion information included in the CTT event container; FIGS. 3b through 3e illustrate syntaxes of the average link speed, the link travel time, the link delay, and the congestion type included in the status component shown in FIG. 3a, respectively; FIG. 4a illustrates a syntax of the traffic/congestion prediction information included in the CTT event container;
FIGS. 4b through 4d illustrate syntaxes of the predicted average link speed, the predicted link travel time, and the tendency information included in the status component shown in FIG. 4a, respectively;
FIG. 5a illustrates an example of a database storing the history of traffic status at each link for providing the traffic/congestion prediction information;
FIG. 5b illustrates an example of a graphical user interface configured to predict the average speed at a specific link using the database shown in FIG. 5a;
FIG. 6 illustrates a block diagram of a navigation terminal installed in a car for receiving traffic information transmitted from a server in accordance with one implementation;
FIGS. 7a through 7c illustrate examples of graphical user interfaces configured to display the average speed at each link; and
FIG. 8 illustrates an example of a graphical user interface configured to display the average speed predicted for a selected link.
5. MODES FOR CARRYING OUT THE INVENTION
One such 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.
FIG. 1 is a schematic diagram of a network through which traffic information is provided. A traffic information providing server 100 in a broadcast station may transmit traffic information collected from various sources (e.g., operator input, or information received from another server or probe cars through a network 101) wirelessly so that a traffic information receiving terminal (e.g., navigation system installed in a car 200) may receive the traffic information.
As shown in FIG. 2a, the traffic information wirelessly transmitted from the traffic information providing server 100 may be a sequence of TPEG-CTT (transport protocol expert group-congestion and travel-time Information) messages. A message segment of the sequence, i.e., a TPEG-CTT message, whose syntax is shown in FIG. 2b, may include a message management container 21, a CTT event container (or Application Event Container) 22, and TPEG-CTT location container 23. The TPEG-CTT message may also include different type of containers other than, less than, or in addition to the CTT event container as in the TPEG-CTT message 30.
The message management container 21 may be used for managing date and time information. The time information may include message generation time (e.g., a chronological time indication) . The message generation time may be included in every TPEG-CTT message when the corresponding message is transmitted. The CTT event container 22 may include congestion and travel time status and predicted congestion and travel time status of links, i.e., road segments. The congestion and travel time status may include average link speed, link travel time, link delay, or congestion type, etc.
The TPEG-CTT location container 23 may employ various location reference processes. For example, a rocation reference process using a coordinate system or a location reference process using pre-promised links may be used. When a coordinate system is used, the coordinates (latitudes and longitudes) of the start and end positions of a link for which the TPEG-CTT message is created, may be transmitted. When a reference process using pre-promised links is used, a unique identification for a specific link on a receiving device may be transmitted. For example, a receiving device may include a locally stored network of links, wherein each link may be identified by a unique identifier. A link may refer to a road segment which starts and ends at junctions and has no junction in between. The coordinate system may be the WGS 84 model. A text formatted name of the link may be transmitted. In various implementations, a CTT event container and a TPEG-CTT location container, as illustrated in FIG. 2c, are composed of one or more CTT components 201. Each of CTT components may be constructed according to the syntax shown in FIG. 2d if it carries congestion status information while it may be constructed according to the syntax shown in FIG. 2e if the component carries location information.
A CTT event container 22 may be composed of one component or a plurality of CTT components. In various implementations, CTT components including an ID of 8Oh (notation 'h' means hexadecimal) or 84h includes one or more status components including basic traffic information such as the average link speed, link travel time, link delay, or congestion type. In the description, specific IDs are described as assignments to structures associated with specific information. The actual value of an assigned ID (e.g., 8Oh) is exemplary, and different implementations may assign different values for specific associations or circumstances.
In various implementations, CTT components including an ID of 8Ih include one or more status components including predicted CTT status. The predicted CTT status may include predicted average link speed, predicted link travel time, or congestion acceleration tendency. The congestion acceleration tendency may include information indicative of the tendency of congestion status. The congestion acceleration tendency will be described as a type of prediction information as the congestion status in the near future may be predicted from it. In various implementations, the TPEG-CTT message may include CTT components structured as FIG. 2f to deliver additional information of traffic information. As shown, an identifier 8Ah may be assigned to the CTT component carrying additional information, and a language code that is indicative of language used for the additional information may also be included in the CTT component.
FIG. 3a shows an example of a syntax of the CTT component included in the CTT event container, which delivers the current congestion and travel time status. The CTT component may be assigned an ID 3a including a value of 8Oh or 84h and may include m status components 3c and a field 3b indicative of the length of the data included in the status components included therein, the length being expressed in the unit of byte. Other units, such as bit, may be used.
The status components 3c may include information on the average link speed, the link travel time, the link delay, and/or the congestion type. The syntax, according to one implementation, of each of which, is shown in FIGS. 3b, 3c, 3d, and 3e, respectively. In one implementation, status components delivering the average link speed, the link travel time, the link delay, and the congestion type are assigned IDs of 1OO', 1Ol', v02', and '03', respectively. The link delay may be, for example, the delay in the time required to pass through the link under current traffic condition with respect to the time required to pass through the link at a limit speed specified in the link. The link delay may be expressed in the unit of minute, second, tens or tenths of seconds, or another unit. The link delay may be calculated with respect to the average time required to pass the link on the same days or in the same time slot. The link delay may enable traffic information receiving terminals that do not have information on each link (e.g., speed limit in the link, length of the link, etc) to expect the time required to pass a link. FIG. 4a shows an example of a syntax of the CTT component included in the CTT event container, which delivers the predicted congestion and travel time status. The CTT component may be assigned an ID 4a including a value of 81h and may include m status components 4c and a field 4b indicative of the length of the data included in the status components included therein, the length, may be, for example, expressed in the unit of byte.
The status components 4c may include information on the predicted average link speed, the predicted link travel time, and/or, the congestion acceleration tendency, the syntax, according to one implementation, of each of which, is shown in FIGS. 4b, 4c, and 4d, respectively. The status components delivering the predicted average link speed, the predicted link travel time, and the congestion acceleration tendency may be assigned IDs of λ00', '01', and λ02', respectively.
Alternatively, the predicted congestion and travel time status may be delivered by the CTT component that delivers the current congestion and travel time status (e.g., average link speed, link travel time, link delay, congestion type) including an ID of 8Oh or 84h. In this case, the status components delivering the predicted congestion and travel time status may be assigned IDs different from the IDs of the status components delivering the current congestion and travel time status.
The server 100 may create predicted status information shown, according to one implementation, in FIGS. 4b through 4d based on the traffic information which may be collected from various sources and/or its own traffic information database, which will be described in detail below.
To provide predicted traffic information, the server 100 may store the average speed at each link according to day, time slot, week, month, or year. For example, in one implementation, the server 100 may store the average speed at each link at intervals, such as every 30 minutes, as shown in FIG. 5a. The unit of the values shown in FIG. 5a is km/h, though other units, such as m/s, may be used.
Additionally, in one implementation, the server 100 may store the average speed, or other information, such as travel time or congestion, of links for which the traffic information is currently provided at intervals for a predetermined period of time (e.g., 3 hours) and compare the pattern of change in the average speed for the period of time with the pattern of change in the same time slot of the same day stored in the database. For example, if FIG. 5b shows the pattern of change in the average speed for the past 3 hours from 4:30 pm on a Monday afternoon (A) , the server 100 compares the data with the average speeds of from 1:30 pm to 4:30 pm stored in the database (B) . If the difference (e.g., the sum of the absolute values of the difference in average speeds at each corresponding time or a weighted sum thereof) is less than a predetermined threshold, the server 100 reads the average speed Bl at 30 minutes after the current time (i.e., the average speed at 5:00 pm) from the database and transmits the value as the predicted average speed in the corresponding link according to the syntax shown in FIG. 4b. The predicted average link speed may be expressed in the unit of km/h, for example. The predicted time (e.g., 5:00 pm in the previous example) may also be transmitted in the form of the syntax shown in FIG. 4b, for example in UTC (Universal Time Coordinated) format . Explaining FIG. 4b in more detail, the predicted time in UTC format may be indicative of a target time or date in the future, and the predicted speed indicates average speed (in km/h, for example) on a link at the target time or date, such as, a day of year, month of year, year, holiday, time of day, rush hour, event, morning/afternoon/evening. For example, the link may be an inter-road between cities, a bridge, or a road between intersections. The data may be incorporated into the component in units of a byte unit, and/or it may be incorporated in units of a bit or a long byte, according to data size. In addition, the speed may be expressed in various units, for example, m/sec, mile/hour, etc.
In one implementation, if the calculated difference exceeds the predetermined threshold, i.e., it is determined that the pattern of change in the average speed stored in the database does not match the pattern of change in the measured average speed, the server 100 may not provide the predicted average link speed, or alternatively, the server 100 may estimate the predicted average link speed Al from the average link speeds extracted for the past 3 hours and provide the estimated value as the predicted average link speed. Various processes may be used to estimate the average speed from the measured average speed values. One process, for example, involves calculation of a weighted sum which gives the latest sample value the highest weight and gives the oldest sample value the lowest weight. For example, the predicted speed Al in FIG. 5b can be extracted by calculating 0.5 x current speed + 0.2 x speed of 30 minutes ago + 0.1 x speed of 1 hour ago + 0.1 x speed of 1.5 hours ago + 0.05 x speed of 2 hours ago + 0.05 x 2.5 hours ago, etc.
After calculating the predicted average link speed in the aforementioned way, the server 100 may calculate the predicted travel time of each link and transmit the predicted travel time of each link along with associated predicted time according to the syntax shown in FIG. 4c. The predicted travel time may be calculated by multiplying the predicted average speed at each link by the length of the corresponding link stored in the database. The predicted travel time may be expressed in the unit of minutes, tens of seconds, second, or a unit smaller than seconds, for example.
When providing the average speed in a particular link, the server 100 may compare the current average speed with the average speed at the previous time slot and provide the tendency of change in the average link speeds 41 according to the syntax shown in FIG. 4d. In one implementation, the information, which is called the congestion acceleration tendency, may have one value among several values defined by a table shown in FIG. 4d. For example, the information may be assigned 1 if the current average speed is higher than the average speed of 30 minutes ago. The congestion acceleration tendency may be assigned 2 if the current average speed is lower than the average speed of 30 minutes ago. The congestion acceleration tendency may be assigned 3 if the average speed remains unchanged. If there is no available data to compare, the congestion acceleration tendency may be assigned 0. The congestion acceleration tendency information may enable a driver to choose a route that shows improvement in the traffic congestion from among several possible routes showing similar average speeds. Instead of providing the congestion acceleration tendency in the form of a number (e.g., 1, 2, 3, etc.), the server 100 may provide the rate of change of the average speed, i.e., the slope in the graph shown in FIG. 5b as the congestion acceleration tendency, or other indicia or descriptors .
In one implementation, the server 100 may prevent the size of information which it should transmit from becoming excessively large by maintaining the ratio of the current congestion and travel time status to the predicted congestion and travel time status below an appropriate level (e.g., 3:1) .
FIG. 6 is an example of a block diagram of a navigation terminal for receiving traffic information transmitted from the server 100. Figs. 6-8 are example implementations of systems for receiving and utilizing traffic information, and interfaces used to output information generated by such systems. Other systems may be organized differently or include different components. As illustrated by Fig. 6, the navigation terminal includes a tuner 1 for receiving modulated traffic information signals by resonating at the required frequency band, a demodulator 2 for outputting traffic information signals by demodulating the modulated signals from the tuner 1, a TPEG- CTT decoder 3 for extracting traffic information by decoding the demodulated traffic information signals, a GPS module 8 for calculating the current position (i.e., latitude, longitude, and altitude) by receiving signals from a plurality of low-orbit satellites, storage structure 4 for storing various graphic data and an electronic map including information on links and nodes, an input device 9 for receiving user input, a navigation engine 5 for controlling screen display based on the user input, the current position, and extracted traffic information, a memory 5a for storing data temporarily, an LCD panel 7 for displaying data, and an LCD drive 6 for driving the LCD panel 7 according to data to be presented. The input unit 9 may be a touch screen incorporated into the LCD panel 7. The tuner 1 tunes to the frequency of the signals transmitted by the server 100 and the demodulator 2 demodulates the tuned signals in a predetermined manner. The TPEG-CTT decoder 3 decodes the demodulated signals into a TPEG-CTT message sequence as shown in FIG. 2, interprets each TPEG message included in the TPEG-CTT message sequence, and sends necessary information and/or control signals to the navigation engine 5. For purposes of brevity, the following description focuses on basic congestion and travel time status shown in FIGS. 3b through 3e and predicted congestion and travel time status shown in FIGS. 4b through 4d though other status information is involved, such as, for example, speed, is involved.
The TPEG-CTT decoder 3 extracts date/time and message generation time included in the message management container of each TPEG message and determines if the following container is a CTT event container based on 'message element' information (i.e. an identifier) . If it is determined that the following container is a CTT event container, the TPEG-CTT decoder 3 provides the navigation engine 5 with the information extracted from the CTT component included in the CTT event container so that the navigation engine 5 may display congestion and travel time status and predicted congestion and travel time status, which will be described below. Providing the navigation engine 5 with the information may include determining, based on identifiers, that the traffic information includes a message management container including status information within various message components within the message management container. The components may each include different status information associated with different links or locations and identifiers associated with the different status information. The containers and components may each include information associated with a generation time, version number, data length, and identifiers of included information.
The TPEG-CTT decoder 3 then extracts information on the link location for which the previously extracted information is intended from the following TPEG-CTT location container. The position information may be, for example, the coordinates (i.e., latitudes and longitudes) of the start and end positions or an ID that is uniquely assigned to each link, depending on the type of the TPEG-CTT location container. If the navigation terminal is equipped with the storage structure 4, the navigation engine 5 finds the location of the link for which the received traffic information is intended with reference to the information on each link and node stored in the storage structure 4. The navigation engine 5 may convert the coordinates of a link into a link ID or vice versa.
The navigation engine 5 reads a part of the electronic map centered around the position coordinates received from the GPS module 8 from the storage structure 4 and displays the map on the LCD panel 7 via the LCD drive 6. A particular graphic symbol is displayed at the location corresponding to the current position on the LCD panel 7.
The navigation engine 5 displays the average link speed received from the TPEG-CTT decoder 3 at a location corresponding to the coordinates or link ID delivered via the TPEG-CTT location container following the container delivering the average link speed. There are various processes for the navigation engine 5 to display the traffic information. For example, the navigation engine 5 may show links in different colors according to the average speed at the links as shown in FIGS. 7a and 7b, where the colors red, orange, green, and blue (colors themselves not shown) may be used to indicate average speeds of 0-10 km, 10-20 km, 20-40 km, over 40 km, respectively. Alternatively, the navigation engine 5 may show the average link speed in numbers at each link as shown in FIG. Ic1 or a combination of colors and numbers may be used. In addition or as an alternative, the navigation engine 5 may use similar display tools to display the congestion acceleration tendency received from the TPEG-CTT decoder 3 at the corresponding link, or through the use of other display tools such as through the use of an icon or a string (e.g., 'improved' if the value of the congestion acceleration tendency is 1 and 'deteriorated' if the value is 2) . In this case, the navigation engine 5 maintains the status unchanged if the value of the congestion acceleration tendency is 0 or 3. If the congestion acceleration tendency is received in the form of the rate of change of the average speed, the navigation engine 5 displays the value only when a request from the user is received to prevent visual confusion of the . user. The rate of change may be displayed together for a user- chosen route or a front link.
If the navigation terminal is not equipped with the storage structure 4 for storing an electronic map, the terminal may show the average link speed at links located in front of the current position in different colors, as shown in FIG. 7b, or in numbers, as shown in FIG. 7c. If the route of the vehicle with the navigation terminal installed is determined, the navigation terminal may show the average speed at the links included in the determined route instead of the links located in front of the current position.
The navigation engine 5, responsive to user input, may display the link travel time, the link delay, and the congestion type received from the TPEG-CTT decoder 3 on the LCD panel 7 instead of or simultaneously with the average link speed.
If the user requests predicted congestion and travel time status through the input unit 9, the navigation engine 5 displays the predicted average link speed at each link received from the TPEG-CTT decoder 3 in colors or in numbers instead of the current average link speed. In this case, the colors or numbers describing the predicted status may be displayed simultaneously with the current average link speed but the -location or used colors may be different. If the user switches the display mode to see the predicted link travel time instead of the predicted average link speed, the navigation engine 5 displays the predicted link travel time on the electronic map or graphics on the LCD panel 7.
If the navigation engine 5 is capable of routing, the navigation engine 5 may search or research the desirable route based on the received predicted average link speed or predicted link travel time. For example, the navigation engine 5 finds the shortest time path to the destination by using the predicted link average time or predicted link travel time at each link to be reached 30 minutes later at the current speed.
If the terminal in FIG. 6 is equipped with a voice output capability, the terminal may audibly output the received predicted status or congestion tendency information for a specified link or links.
The information and/or control signals received from the TPEG-CTT decoder 3 are temporarily stored in the rewritable memory 5a and used by the navigation engine 5. After using the information stored in the memory 5a, the navigation engine 5 may store the average link speed or link travel time at intervals of, such as, for example, 20 minutes (e.g., 1:00, 1:20, 1:40) for the last 1 hour. The interval of storage may differ depending on the storage capacity of the memory 5a. By automatically expiring the information from within memory, the system may be assured that it is working with recent information when consulting the contents of the memory, and thus may be able to represent information as current with confidence without having to otherwise maintain or check information reflecting when the stored data was collected/aggregated/stored.
If a specific link is selected by the user while the average speed at each link is stored in the memory 5a, the navigation engine 5 controls the LCD drive 6 so that the history of the average link speed or the history of the link travel time at the specified link is displayed as a graph shown in FIG. 8. In the graph, the unit of the displayed numbers is km/h and the name 81 of the link is displayed on the graph. The link name is received along with the coordinates of the link or link ID through the TPEG location container 23 or included in the electronic map stored in the storage structure 4. The current congestion status, predicted congestion status, or other status may be displayed in other or different ways.
If the predicted congestion status is not included in the received traffic information, the navigation engine 5 may predict the average speed using the current average speed and the history of the average link speed stored in the memory 5a and display the predicted average link speed, as shown in PIG. 8a. The method for predicting the average link speed may be the same as the aforementioned prediction method executed in the server 100. While the disclosure has discussed a limited number of implementations, those skilled in the art having the benefit of this disclosure will appreciate numerous modifications and variations therefrom. It is intended that all such modifications and variations fall within the spirit and scope of this disclosure.

Claims

C LAI M S
1. A method for identifying traffic information, the method comprising: receiving traffic data including a first identifier, information corresponding to a prediction of travel speed for a particular link, and information corresponding to a location associated with the particular link; determining travel speed prediction information based on the information included in the received traffic data; determining location information based on the information that is included in the received traffic data corresponding to the location associated with the particular link; and identifying traffic information based on the determined travel speed prediction information and the determined location information.
2. The method of claim 1, wherein determining travel speed prediction information includes accessing received data reflecting, among other items, results of measurements made with respect to traffic previously traversing the link, and computing a prediction for a future travel speed based on the received data.
3. The method of claim 1, wherein determining travel speed prediction information involves accessing information provided within the received traffic data and recognizing that data as the predicted travel speed.
4. The method of claim 1, further comprising receiving information corresponding to a message management structure including information corresponding to a generation time of information reflected in the traffic data.
5. The method of claim 4, wherein the generation time included within the received message management structure relates 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, or a predicted or current time to traverse a particular link.
6. The method of claim 5, wherein each message component structure further includes an identifier specific to the type of information and the first identifier is an identifier, in a message component structure, specific to the prediction of travel speed for the particular link.
7. The method of claim 6, further comprising receiving information corresponding to a chronological indication associated with the predicted travel speed revealed by the received information.
8. The method of claim 7, wherein the chronological indication reflects a particular time of day for which the predicted travel speed corresponds.
9. The method of claim 7, wherein the chronological indication is reflected using the universal time co-ordinated standard.
10. The method of claim 1, wherein the travel speed prediction information and the location information are determined in a single step.
11. The method of claim 1, wherein the location information is determined before the travel speed prediction information is determined.
12. The method of claim 1, wherein receiving traffic data includes decoding the traffic data such that the received traffic data is decoded traffic data.
13. The method of claim 1, wherein the prediction of travel speed reflects an average of more than one indication of travel speed associated with the link.
14. The method of claim 1, wherein the prediction of travel speed reflects a weighted summation of more than one indication of travel speed associated with the link.
15. The method of claim 1, wherein the predicted travel speed is reflected in one of kilometers per hour and miles per hour.
16. The method of claim 1, wherein receiving information corresponding to a prediction of travel speed includes receiving a predicted travel speed for the link including a text descriptor.
17. The method of claim 1, wherein the information corresponding to a prediction of travel speed for a particular link reflects the predicted travel speed.
18. An apparatus for identifying traffic information, the apparatus comprising: an interface configured to receive traffic data including a first identifier, information corresponding to a prediction of travel speed for a particular link; and a processor configured to: dependent upon whether the first identifier enables a determination that the received traffic data includes a prediction related to a travel speed, determine travel speed prediction information based on the information included in the received traffic data; determine location information based on the information that is included in the received traffic data corresponding to the location corresponding to the particular link; and identify traffic information based on the determined travel speed prediction information and the determined location information.
19. The apparatus of claim 18, wherein the processor is configured to receive traffic data including information corresponding to a version number of information reflected in the traffic data, wherein the version number is associated with a specific syntax of the data where any one of multiple syntaxes may be used.
20. The apparatus of claim 18, wherein the processor is configured to receive information corresponding to a message management structure including information corresponding to a generation time of information reflected in the traffic data.
21. The apparatus of claim 18, wherein the processor is configured to receive information corresponding to a data length of the received data.
22. The apparatus of claim 18, wherein the processor is configured to receive the predicted travel speed reflected as one value in a set of possible values.
23. The apparatus of claim 18, wherein the processor is further configured to: determine the prediction of travel speed for a particular link only if the first identifier reveals that the traffic data relates to a prediction of travel speed for a particular link.
24. An apparatus for identifying traffic information, the apparatus comprising: means for an interface configured to receive traffic data including a first identifier, information corresponding to a prediction of travel speed for a particular link, and information corresponding to a location associated with the particular link; and means for determining travel speed prediction information based on the information included in the received traffic data; means for determining location information based on the information that is included in the received traffic data corresponding to the location corresponding to the particular link; and means for identifying traffic information based on the determined travel speed prediction information and the determined location information.
PCT/KR2006/001836 2005-05-18 2006-05-17 Providing traffic information relating to a prediction of speed on a link and using the same WO2006123890A1 (en)

Priority Applications (8)

Application Number Priority Date Filing Date Title
CN2006800168330A CN101228566B (en) 2005-05-18 2006-05-17 Method and device for providing traffic information relating to a prediction of speed on road
DE602006010998T DE602006010998D1 (en) 2005-05-18 2006-05-17 PROVISION OF TRAFFIC INFORMATION IN RELATION TO THE PREDICTION OF SPEED ON CONNECTION AND USE OF THE SPEED
MX2007014604A MX2007014604A (en) 2005-05-18 2006-05-17 Providing traffic information relating to a prediction of speed on a link and using the same.
EP06747435A EP1886294B1 (en) 2005-05-18 2006-05-17 Providing traffic information relating to a prediction of speed on a link and using the same
BRPI0610741A BRPI0610741B1 (en) 2005-05-18 2006-05-17 method and apparatus for processing traffic data
AT06747435T ATE451679T1 (en) 2005-05-18 2006-05-17 PROVIDING TRAFFIC INFORMATION REGARDING THE PREDICTION OF SPEED ON A CONNECTION AND THE USE OF IT
CA2608700A CA2608700C (en) 2005-05-18 2006-05-17 Providing traffic information relating to a prediction of speed on a link and using the same
KR1020077027148A KR101236521B1 (en) 2005-05-18 2006-05-17 Providing traffic information relating to a prediction of speed on a link and using the same

Applications Claiming Priority (8)

Application Number Priority Date Filing Date Title
US68197105P 2005-05-18 2005-05-18
US60/681,971 2005-05-18
KR20050089477 2005-09-26
KR10-2005-0089477 2005-09-26
US75996306P 2006-01-19 2006-01-19
US60/759,963 2006-01-19
KR1020060023214A KR20060119743A (en) 2005-05-18 2006-03-13 Method and apparatus for providing prediction information on average speed on a link and using the information
KR10-2006-0023214 2006-03-13

Publications (1)

Publication Number Publication Date
WO2006123890A1 true WO2006123890A1 (en) 2006-11-23

Family

ID=37431439

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2006/001836 WO2006123890A1 (en) 2005-05-18 2006-05-17 Providing traffic information relating to a prediction of speed on a link and using the same

Country Status (10)

Country Link
US (1) US7940741B2 (en)
EP (2) EP1886294B1 (en)
KR (2) KR20060119743A (en)
CN (1) CN101228566B (en)
AT (2) ATE451679T1 (en)
BR (1) BRPI0610741B1 (en)
CA (1) CA2608700C (en)
DE (2) DE602006016352D1 (en)
MX (1) MX2007014604A (en)
WO (1) WO2006123890A1 (en)

Families Citing this family (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20060119743A (en) 2005-05-18 2006-11-24 엘지전자 주식회사 Method and apparatus for providing prediction information on average speed on a link and using the information
KR20060119739A (en) * 2005-05-18 2006-11-24 엘지전자 주식회사 Method and apparatus for providing prediction information on travel time for a link and using the information
KR101061460B1 (en) * 2005-05-18 2011-09-02 엘지전자 주식회사 Method and apparatus for providing prediction information about communication status and using it
KR20060119742A (en) * 2005-05-18 2006-11-24 엘지전자 주식회사 Method and apparatus for providing link information and using the information
KR20060119741A (en) * 2005-05-18 2006-11-24 엘지전자 주식회사 Method and apparatus for providing information on congestion tendency on a link and using the information
KR20060119746A (en) 2005-05-18 2006-11-24 엘지전자 주식회사 Method and apparatus for providing transportation status information and using it
KR20060122668A (en) * 2005-05-27 2006-11-30 엘지전자 주식회사 Method for providing traffic information and apparatus for receiving traffic information
US8711850B2 (en) * 2005-07-08 2014-04-29 Lg Electronics Inc. Format for providing traffic information and a method and apparatus for using the format
KR101254219B1 (en) * 2006-01-19 2013-04-23 엘지전자 주식회사 method and apparatus for identifying a link
KR100725519B1 (en) * 2006-01-02 2007-06-07 삼성전자주식회사 Method and apparatus for displaying traffic information based on user selection level
JP4736979B2 (en) * 2006-06-30 2011-07-27 日産自動車株式会社 In-vehicle device, traffic information acquisition method, traffic information providing system, and traffic information providing method
CN101554000A (en) * 2006-12-08 2009-10-07 Lg电子株式会社 Method and apparatus for managing versions of various application information messages and using the application information messages
JP4788598B2 (en) * 2006-12-28 2011-10-05 株式会社デンソー Congestion degree judgment device, traffic information notification device, and program
US7755509B2 (en) * 2007-09-20 2010-07-13 Traffic.Com, Inc. Use of pattern matching to predict actual traffic conditions of a roadway segment
US8892345B2 (en) * 2011-04-08 2014-11-18 Here Global B.V. Trend based predictive traffic
CN103069464B (en) * 2011-05-23 2015-01-14 丰田自动车株式会社 Information processing system for vehicle
JP5893953B2 (en) * 2012-02-22 2016-03-23 日立建機株式会社 Vehicle operation management system
US9685166B2 (en) 2014-07-26 2017-06-20 Huawei Technologies Co., Ltd. Classification between time-domain coding and frequency domain coding
CN106156966A (en) 2015-04-03 2016-11-23 阿里巴巴集团控股有限公司 Logistics monitoring method and equipment
US11170030B2 (en) * 2015-07-02 2021-11-09 Fannie Mae Selecting properties using location constraints based on travel time contours
EP3700108B1 (en) * 2019-02-20 2023-08-09 Volkswagen Aktiengesellschaft Method for supporting a first mobile station to predict the channel quality for a planned decentralized wireless communication to a communication partner station und mobile station
JP7337750B2 (en) * 2020-06-01 2023-09-04 株式会社東芝 Communication control device, communication control method, information processing device, information processing method, and program

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH11160081A (en) * 1997-11-27 1999-06-18 Alpine Electron Inc Navigation method
WO2000039774A2 (en) 1998-12-14 2000-07-06 Mannesmann Ag Method for identifying events which cover more than one segment using segments
KR20020017535A (en) * 2000-08-30 2002-03-07 박종헌 A method estimating the section-velocity for the advance direction
US6615133B2 (en) * 2001-02-27 2003-09-02 International Business Machines Corporation Apparatus, system, method and computer program product for determining an optimum route based on historical information
KR20040033141A (en) * 2002-10-11 2004-04-21 에스케이 주식회사 Traffic information providing system and method thereof

Family Cites Families (105)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE3752122T3 (en) 1987-05-09 2004-07-29 Koninklijke Philips Electronics N.V. Facility for receiving and processing road news reports
US5662109A (en) 1990-12-14 1997-09-02 Hutson; William H. Method and system for multi-dimensional imaging and analysis for early detection of diseased tissue
EP1202028A1 (en) 1994-09-08 2002-05-02 Matsushita Electric Industrial Co., Ltd. Method and system of route selection
US5649297A (en) 1994-10-21 1997-07-15 Seiko Communications Holding N.V. Transmitting digital data using multiple subcarriers
DE19503415A1 (en) 1995-02-03 1996-08-08 Bosch Gmbh Robert Device for managing digitally coded traffic reports in receiving devices
JP3194460B2 (en) 1995-08-24 2001-07-30 矢崎総業株式会社 Operation information collection device and vehicle operation management system using the same
DE69631458T2 (en) 1995-10-04 2004-07-22 Aisin AW Co., Ltd., Anjo Car navigation system
US5933100A (en) 1995-12-27 1999-08-03 Mitsubishi Electric Information Technology Center America, Inc. Automobile navigation system with dynamic traffic data
KR100267543B1 (en) 1996-04-28 2000-10-16 모리 하루오 Device for processing road data or intersection data
CA2259179C (en) * 1996-07-03 2008-09-23 University Of Pittsburgh Emulsion formulations for hydrophilic active agents
JP3569393B2 (en) 1996-07-31 2004-09-22 パイオニア株式会社 Data broadcast receiver
KR100278972B1 (en) 1996-08-21 2001-01-15 모리 하루오 Navigation device
JPH10141496A (en) 1996-10-25 1998-05-29 Aqueous Res:Kk Vehicle controller
WO1998024079A1 (en) 1996-11-28 1998-06-04 Mannesmann Ag Method and terminal unit for the spatial allocation of information referring to one location
DE19651143B4 (en) * 1996-12-10 2013-07-25 T-Mobile Deutschland Gmbh Method and arrangement for traffic information
JPH10281790A (en) 1997-04-08 1998-10-23 Aisin Aw Co Ltd Route search device, navigation apparatus and medium on which computer program for navigation processing is stored
JPH1165436A (en) 1997-08-21 1999-03-05 Toyota Motor Corp Data selection support device, and map data processing system and processor including same support device
EP0899703B1 (en) 1997-08-25 2002-10-30 Texas Instruments France A navigational system
DE69817306T2 (en) 1997-12-02 2004-06-24 Siemens Ag Device for processing a traffic announcement
JPH11281377A (en) 1998-03-31 1999-10-15 Sony Corp Map information obtaining method, navigation method, region information providing method, navigation apparatus, region information providing apparatus, and automobile
JPH11311533A (en) * 1998-04-28 1999-11-09 Xanavi Informatics Corp Routing device
KR20000021530A (en) 1998-09-30 2000-04-25 전주범 Traffic information terminal using digital audio broadcasting
US6438561B1 (en) * 1998-11-19 2002-08-20 Navigation Technologies Corp. Method and system for using real-time traffic broadcasts with navigation systems
DE19857782C2 (en) * 1998-12-04 2001-01-11 Mannesmann Ag Method for transmitting table information from a control center to a terminal via a transmission channel and control center for performing the method
WO2000036771A1 (en) * 1998-12-14 2000-06-22 Mannesmann Ag Binary transmission system
US6633808B1 (en) 1998-12-14 2003-10-14 Mannesmann Ag Method for transmitting traffic information
DE19905893A1 (en) 1999-02-11 2000-08-17 Bosch Gmbh Robert Process for the transmission of digitally coded traffic messages and radio receivers therefor
CA2266208C (en) 1999-03-19 2008-07-08 Wenking Corp. Remote road traffic data exchange and intelligent vehicle highway system
DE19914041A1 (en) 1999-03-27 2000-09-28 Bosch Gmbh Robert Procedure for informing motorists
JP4102952B2 (en) 1999-04-26 2008-06-18 ソニー株式会社 Receiving machine
DE19933970A1 (en) 1999-07-20 2001-01-25 Bosch Gmbh Robert Procedure for coding cross-road traffic obstructions
DE19937372A1 (en) * 1999-08-12 2001-02-15 Bosch Gmbh Robert Procedure for requesting and processing traffic reports
DE19942522A1 (en) 1999-09-07 2001-03-08 Bosch Gmbh Robert Method for coding and decoding objects related to a traffic network
EP1224645B2 (en) 1999-09-07 2010-02-17 Robert Bosch Gmbh Method for coding and decoding objects in a road traffic network
EP1228453A4 (en) 1999-10-22 2007-12-19 Activesky Inc An object oriented video system
JP2001272246A (en) 2000-03-23 2001-10-05 Honda Motor Co Ltd Road traffic information notification apparatus
DE10015935A1 (en) 2000-03-30 2001-10-04 Bosch Gmbh Robert Method for transmitting a position of traffic information, in particular a traffic disruption
KR100424481B1 (en) 2000-06-24 2004-03-22 엘지전자 주식회사 Apparatus and method for recording and reproducing a digital broadcasting service information on optical medium
DE10038765A1 (en) 2000-08-09 2002-02-21 Bosch Gmbh Robert Process for the transmission of digitally coded traffic messages
DE10060599A1 (en) 2000-12-05 2002-06-06 Peter Badenhop Traffic information transmission system for use in vehicle has data received from information providers entered in databank and supplied to transmitter after conversion into broadcast signal
WO2002046698A1 (en) * 2000-12-08 2002-06-13 Matsushita Electric Industrial Co., Ltd. Position information identifier providing system, and position information identifier transmitting method and device
DE10101349B4 (en) 2001-01-13 2007-08-16 Robert Bosch Gmbh Method for reporting traffic congestion
US6970132B2 (en) 2001-02-02 2005-11-29 Rosum Corporation Targeted data transmission and location services using digital television signaling
US6594576B2 (en) * 2001-07-03 2003-07-15 At Road, Inc. Using location data to determine traffic information
US6904362B2 (en) 2001-08-09 2005-06-07 Aisin Aw Co., Ltd. Route guidance system, information delivery center, and vehicular route guidance apparatus
JP3659203B2 (en) * 2001-08-13 2005-06-15 日産自動車株式会社 Vehicle communication control device
KR100454922B1 (en) 2001-10-31 2004-11-15 삼성전자주식회사 Navigation system for providing a real-time traffic information and method thereof
US7221287B2 (en) * 2002-03-05 2007-05-22 Triangle Software Llc Three-dimensional traffic report
US6995769B2 (en) 2002-03-21 2006-02-07 Hewlett-Packard Development Company, L.P. Systems and methods for compressing rasterization setup data within a sort middle graphics architecture
JP2003284110A (en) 2002-03-22 2003-10-03 Toshiba Corp Local information broadcast system, broadcast facility thereof, and reception terminal
JP4212536B2 (en) 2002-03-27 2009-01-21 パナソニック株式会社 Road information providing system and apparatus and road information generation method
CA2480493A1 (en) 2002-03-29 2003-10-23 Matsushita Electric Industrial Co., Ltd. Map matching method, map matching device, database for shape matching, and shape matching device
US6741932B1 (en) 2002-04-16 2004-05-25 Navigation Technologies Corp. Method and system for using real-time traffic broadcasts with navigation systems
JP2004005493A (en) 2002-04-24 2004-01-08 Vehicle Information & Communication System Center Driver assist information transmitter, driver assist information receiver and driver assist information providing system
AU2003258956A1 (en) 2002-06-27 2004-01-19 Robert E. Berger Traffic data acquisition system and method
DE10229195A1 (en) 2002-06-28 2004-01-15 Robert Bosch Gmbh Information transmission procedures and information recipients
US20040198339A1 (en) 2002-09-27 2004-10-07 Martin Ronald Bruce Selective multi-media broadcast of traffic information
GB2394347A (en) 2002-10-15 2004-04-21 Canon Kk Lattice encoding
JP4416996B2 (en) 2002-11-01 2010-02-17 三菱電機株式会社 Map information processing apparatus and map information providing apparatus
JP3742379B2 (en) 2002-11-14 2006-02-01 日本電信電話株式会社 Traffic jam information conversion method, traffic jam information conversion device, traffic jam information conversion program, and recording medium recording the program
JP2004186741A (en) 2002-11-29 2004-07-02 Kenwood Corp Transmitter, receiver, transmission method, reception method and program
KR100965662B1 (en) 2003-01-11 2010-06-24 삼성전자주식회사 Navigation system using paging channel and method for providing traffic information
DE10304546A1 (en) * 2003-02-04 2004-08-05 Robert Bosch Gmbh Method of transmission of traffic data uses base data transmission with additional data transmitted at same time and carrying traffic positional data
US6810321B1 (en) 2003-03-17 2004-10-26 Sprint Communications Company L.P. Vehicle traffic monitoring using cellular telephone location and velocity data
DE10312024A1 (en) 2003-03-18 2004-09-30 Robert Bosch Gmbh Database for coding or decoding traffic reports and method for transmitting coded traffic reports
EP1463255A1 (en) 2003-03-25 2004-09-29 Sony United Kingdom Limited Interleaver for mapping symbols on the carriers of an OFDM system
JP4270922B2 (en) 2003-03-28 2009-06-03 三菱電機株式会社 Mobile communication device, traffic jam information generation device, mobile communication method of mobile communication device, traffic jam information generation transmission method of traffic jam information generation device, and
KR100469714B1 (en) * 2003-06-04 2005-02-02 삼성전자주식회사 Method and apparatus for collecting traffic information in realtime
US7013983B2 (en) 2003-06-18 2006-03-21 Komatsu Ltd. Blade mounting structure of bulldozer
DE602004002048T2 (en) 2003-07-30 2007-02-22 Pioneer Corp. Device, system and method for signaling the traffic situation
JP2005056061A (en) 2003-08-01 2005-03-03 Matsushita Electric Ind Co Ltd Method for encoding traffic information, traffic information providing system and device thereof
EP1505369B1 (en) * 2003-08-08 2009-02-25 Harman/Becker Automotive Systems GmbH Method and system for outputting traffic data to a driver of a vehicle
KR20050015912A (en) * 2003-08-14 2005-02-21 삼성전자주식회사 Navigation system using paging network and tethod for providing traffic information thereof
US7251558B1 (en) 2003-09-23 2007-07-31 Navteq North America, Llc Method and system for developing traffic messages
US6990407B1 (en) 2003-09-23 2006-01-24 Navteq North America, Llc Method and system for developing traffic messages
KR100557046B1 (en) 2003-09-29 2006-03-03 엘지전자 주식회사 Method and apparatus for effective selecting service component of digital broadcasting
US7355528B2 (en) 2003-10-16 2008-04-08 Hitachi, Ltd. Traffic information providing system and car navigation system
US7106219B2 (en) 2003-11-07 2006-09-12 Pearce James W Decentralized vehicular traffic status system
US7188025B2 (en) * 2003-12-18 2007-03-06 International Business Machines Corporation Method and apparatus for exchanging traffic condition information using peer to peer networking
US7890246B2 (en) 2003-12-26 2011-02-15 Aisin Aw Co., Ltd. Method of interpolating traffic information data, apparatus for interpolating, and traffic information data structure
JP4007353B2 (en) 2003-12-26 2007-11-14 アイシン・エィ・ダブリュ株式会社 Traffic information processing device in navigation system
JP4063281B2 (en) 2004-02-20 2008-03-19 セイコーエプソン株式会社 Presentation support device and program thereof
JP4346472B2 (en) * 2004-02-27 2009-10-21 株式会社ザナヴィ・インフォマティクス Traffic information prediction device
JP4561139B2 (en) * 2004-03-22 2010-10-13 アイシン・エィ・ダブリュ株式会社 Navigation system
US7319931B2 (en) 2004-04-06 2008-01-15 Honda Motor Co., Ltd. Methods for filtering and providing traffic information
US7289039B2 (en) 2004-09-10 2007-10-30 Xanavi Informatics Corporation Apparatus and method for processing and displaying traffic information in an automotive navigation system
KR100565089B1 (en) 2004-10-06 2006-03-30 삼성전자주식회사 Video service providing and receiving method in dab system, and apparatus thereof
US7831384B2 (en) 2004-10-29 2010-11-09 Aol Inc. Determining a route to destination based on partially completed route
KR100754168B1 (en) 2004-11-12 2007-09-03 삼성전자주식회사 Method and apparatus for updating map data, and recording medium storing a program to implement thereof
JP4476789B2 (en) 2004-11-18 2010-06-09 クラリオン株式会社 Map update system, navigation device, distribution device
JP2006195415A (en) 2004-12-13 2006-07-27 Fujitsu Ten Ltd Display apparatus and display method
KR101066292B1 (en) 2005-02-07 2011-09-20 삼성전자주식회사 Apparatus and method for receiving selectively the data broadcasting of digital multimedia broadcasting
JP4727245B2 (en) 2005-02-08 2011-07-20 三菱電機株式会社 Map information processing device
KR20060119741A (en) 2005-05-18 2006-11-24 엘지전자 주식회사 Method and apparatus for providing information on congestion tendency on a link and using the information
KR20060119742A (en) 2005-05-18 2006-11-24 엘지전자 주식회사 Method and apparatus for providing link information and using the information
KR20060119746A (en) 2005-05-18 2006-11-24 엘지전자 주식회사 Method and apparatus for providing transportation status information and using it
US7729335B2 (en) * 2005-05-18 2010-06-01 Lg Electronics Inc. Providing traffic information relating to a prediction of congestion status and using the same
KR20060119743A (en) 2005-05-18 2006-11-24 엘지전자 주식회사 Method and apparatus for providing prediction information on average speed on a link and using the information
KR20060119739A (en) 2005-05-18 2006-11-24 엘지전자 주식회사 Method and apparatus for providing prediction information on travel time for a link and using the information
KR101061460B1 (en) 2005-05-18 2011-09-02 엘지전자 주식회사 Method and apparatus for providing prediction information about communication status and using it
KR20060122668A (en) 2005-05-27 2006-11-30 엘지전자 주식회사 Method for providing traffic information and apparatus for receiving traffic information
KR100713427B1 (en) 2005-06-14 2007-05-04 삼성전자주식회사 Digital multimedia broadcastingdmb data reception apparatus and method for improving dmb data reception speed
US8711850B2 (en) 2005-07-08 2014-04-29 Lg Electronics Inc. Format for providing traffic information and a method and apparatus for using the format
KR101254219B1 (en) 2006-01-19 2013-04-23 엘지전자 주식회사 method and apparatus for identifying a link
CA2562206C (en) 2005-10-05 2012-07-10 Lg Electronics Inc. A method and digital broadcast transmitter for transmitting a digital broadcast signal

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH11160081A (en) * 1997-11-27 1999-06-18 Alpine Electron Inc Navigation method
WO2000039774A2 (en) 1998-12-14 2000-07-06 Mannesmann Ag Method for identifying events which cover more than one segment using segments
KR20020017535A (en) * 2000-08-30 2002-03-07 박종헌 A method estimating the section-velocity for the advance direction
US6615133B2 (en) * 2001-02-27 2003-09-02 International Business Machines Corporation Apparatus, system, method and computer program product for determining an optimum route based on historical information
KR20040033141A (en) * 2002-10-11 2004-04-21 에스케이 주식회사 Traffic information providing system and method thereof

Also Published As

Publication number Publication date
CA2608700C (en) 2011-11-15
KR101236521B1 (en) 2013-02-21
KR20060119743A (en) 2006-11-24
US20060268736A1 (en) 2006-11-30
MX2007014604A (en) 2008-02-11
BRPI0610741B1 (en) 2018-07-17
ATE451679T1 (en) 2009-12-15
US7940741B2 (en) 2011-05-10
DE602006016352D1 (en) 2010-09-30
ATE478409T1 (en) 2010-09-15
EP2124211B1 (en) 2010-08-18
KR20080016575A (en) 2008-02-21
DE602006010998D1 (en) 2010-01-21
EP2124211A1 (en) 2009-11-25
CN101228566A (en) 2008-07-23
CA2608700A1 (en) 2006-11-23
EP1886294B1 (en) 2009-12-09
EP1886294A1 (en) 2008-02-13
BRPI0610741A2 (en) 2010-07-20
CN101228566B (en) 2010-05-19
EP1886294A4 (en) 2008-10-29

Similar Documents

Publication Publication Date Title
CA2608698C (en) Providing traffic information including a prediction of travel time to traverse a link and using the same
CA2608700C (en) Providing traffic information relating to a prediction of speed on a link and using the same
CA2609189C (en) Providing information relating to traffic congestion tendency and using the same
US7729335B2 (en) Providing traffic information relating to a prediction of congestion status and using the same
CA2608701C (en) Providing traffic information relating to a prediction of congestion status and using the same

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 200680016833.0

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application
ENP Entry into the national phase

Ref document number: 2608700

Country of ref document: CA

WWE Wipo information: entry into national phase

Ref document number: 4416/KOLNP/2007

Country of ref document: IN

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: MX/a/2007/014604

Country of ref document: MX

WWE Wipo information: entry into national phase

Ref document number: 1020077027148

Country of ref document: KR

WWE Wipo information: entry into national phase

Ref document number: 2006747435

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: RU

WWP Wipo information: published in national office

Ref document number: 2006747435

Country of ref document: EP

ENP Entry into the national phase

Ref document number: PI0610741

Country of ref document: BR

Kind code of ref document: A2