EP1079353B1 - Méthode pour demander et traiter des messages routiers - Google Patents
Méthode pour demander et traiter des messages routiers Download PDFInfo
- Publication number
- EP1079353B1 EP1079353B1 EP00115719A EP00115719A EP1079353B1 EP 1079353 B1 EP1079353 B1 EP 1079353B1 EP 00115719 A EP00115719 A EP 00115719A EP 00115719 A EP00115719 A EP 00115719A EP 1079353 B1 EP1079353 B1 EP 1079353B1
- Authority
- EP
- European Patent Office
- Prior art keywords
- traffic
- data
- radio
- transmitted
- information
- Prior art date
- Legal status (The legal status 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 status listed.)
- Expired - Lifetime
Links
Classifications
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G1/00—Traffic control systems for road vehicles
- G08G1/09—Arrangements for giving variable traffic instructions
- G08G1/0962—Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
- G08G1/0967—Systems involving transmission of highway information, e.g. weather, speed limits
- G08G1/096708—Systems involving transmission of highway information, e.g. weather, speed limits where the received information might be used to generate an automatic action on the vehicle control
- G08G1/096716—Systems involving transmission of highway information, e.g. weather, speed limits where the received information might be used to generate an automatic action on the vehicle control where the received information does not generate an automatic action on the vehicle control
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G1/00—Traffic control systems for road vehicles
- G08G1/09—Arrangements for giving variable traffic instructions
- G08G1/0962—Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
- G08G1/0967—Systems involving transmission of highway information, e.g. weather, speed limits
- G08G1/096733—Systems involving transmission of highway information, e.g. weather, speed limits where a selection of the information might take place
- G08G1/096741—Systems involving transmission of highway information, e.g. weather, speed limits where a selection of the information might take place where the source of the transmitted information selects which information to transmit to each vehicle
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G1/00—Traffic control systems for road vehicles
- G08G1/09—Arrangements for giving variable traffic instructions
- G08G1/0962—Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
- G08G1/0967—Systems involving transmission of highway information, e.g. weather, speed limits
- G08G1/096766—Systems involving transmission of highway information, e.g. weather, speed limits where the system is characterised by the origin of the information transmission
- G08G1/096775—Systems involving transmission of highway information, e.g. weather, speed limits where the system is characterised by the origin of the information transmission where the origin of the information is a central station
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G1/00—Traffic control systems for road vehicles
- G08G1/09—Arrangements for giving variable traffic instructions
- G08G1/0962—Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
- G08G1/0968—Systems involving transmission of navigation instructions to the vehicle
- G08G1/096805—Systems involving transmission of navigation instructions to the vehicle where the transmitted instructions are used to compute a route
- G08G1/096827—Systems involving transmission of navigation instructions to the vehicle where the transmitted instructions are used to compute a route where the route is computed onboard
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G1/00—Traffic control systems for road vehicles
- G08G1/09—Arrangements for giving variable traffic instructions
- G08G1/0962—Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
- G08G1/0968—Systems involving transmission of navigation instructions to the vehicle
- G08G1/096855—Systems involving transmission of navigation instructions to the vehicle where the output is provided in a suitable form to the driver
- G08G1/096872—Systems involving transmission of navigation instructions to the vehicle where the output is provided in a suitable form to the driver where instructions are given per voice
Definitions
- the invention is based on a method for requesting and processing traffic reports according to the type of the main claim.
- WO 98/26396 a method and an arrangement for informing mobile subscribers have already become known.
- data are transmitted between a central unit or a mobile subscriber unit on request and / or automatically. These data are intended in particular to transmit traffic information to the mobile subscriber.
- the central station gives the mobile subscriber all the information about traffic management, so that the road user is completely dependent on the information from the central office.
- the other possibility is to be seen in the fact that the road user carries a navigation device on board his vehicle, by means of which it is possible to obtain traffic management from the given current position to a target position.
- control center is only used to transmit traffic information of this type from the control center that could lead to a hindrance to the journey, in particular traffic jams, road closures, diversions or weather-related disruptions.
- This information can either be transmitted in plain text or in a reduced form, only codes being transmitted, and these codes then being combined in the receiver to form complete messages.
- a radio To send and receive the information, a radio must be available for each participant, which enables both the transmission of messages and the reception of messages.
- Such a radio device can be, for example, a customary mobile radio device, as described in DE 196 51 143 A1, but it can also be transmitters that send information to a central station on a specific frequency and, for example, radio receivers operating in the Are able to receive customized messages.
- the control center can then broadcast the information via a radio transmitter and, on the basis of the individual identifier, ensure that the message can only be evaluated by the recipient who is appropriately individualized.
- the measure according to the invention has the advantage that the information transmitted to the control center ensures that the coded traffic messages must also be evaluated in the vehicle, since the version number transmitted ensures that the information transmitted back from the control center is also in the vehicle Vehicle can be evaluated with the data available there. Misinformation or incorrect information that relates to incorrect or missing versions of the saved data will be avoided.
- data group information the version and / or the manufacturer and / or the date of issue of the traffic request is transmitted separately for each data group, hereinafter referred to as data group information.
- the traffic report request is sent on request. This ensures that the user has in his hand how often and how often he wants to query traffic news. In particular, if he ascertains after a query that traffic obstructions are not to be expected, it is often sufficient that renewed queries are only necessary after a longer driving time. The user of the device is therefore able to send the queries according to his wishes.
- the traffic jams and disabilities that were transmitted due to the traffic request are taken into account when determining the route.
- the location code is transmitted together with the version from the base station when several data groups in the radio or navigation device are evaluated. This ensures that even with extensive geographical areas, eg. B. Germany and France, a clear assignment of the location is achieved so that French locations are assigned to the French data group and German locations to the German data group.
- FIG. 1 shows a mobile vehicle radio device and a central radio transceiver
- FIGS. 2 to 4 the structure of the data word that is sent from the mobile subscriber to the control center
- FIGS. 5 to 7 the structure of the data word that is sent from the control center to the mobile subscriber
- FIG. 8 shows a possible division of data groups.
- FIG. 1 shows a mobile radio device 4 installed in a vehicle, not shown, which is capable of transmitting and receiving radio transmissions via an antenna 5.
- a mobile device z. B. to understand radios that work according to the GSM or AMPS standard, but also individualized radio receivers, eg. B. DAB receivers that have a return channel, or where the transmission of the transmission signal takes place on another mobile radio channel.
- the mobile radio device 4 is connected to a navigation device 6, the navigation device 6 being able to determine a route based on the current location of a vehicle and an entered destination, which the vehicle has to drive.
- the navigation device 6 is connected to a mass storage device 7.
- the mass storage device 7 contains, in digital form, information about roads of a specific geographical area.
- the memory also contains in data groups information for evaluating traffic messages transmitted in coded form, these traffic messages being received in coded form in the radio receiver 4. Details of this are described in DE-OS 35 36 820. Furthermore, information about the location codes of the coded transmitted traffic messages and their linkage with the location codes of the digital map are stored in the memory 7 in the data groups.
- FIG. 1 also shows a base station 2, which is capable of receiving radio signals from the mobile radio device 4 and sending messages back to the mobile radio device 4 via an antenna 3.
- the base station can also be a Broadcasting stations, e.g. B.
- a DAB transmitter that can send out individualized messages, with a return channel receiver or a mobile radio receiver.
- the base station 2 is connected to a memory 1, information about traffic disturbances and traffic obstructions being read into the memory 1, coded and transmitted for transmission Will be provided.
- a connection to the base station 2 is established either manually, if the driver has set this, for example at the push of a button, or automatically by the user of the mobile device 4.
- a radio telegram according to FIG. 2 is now sent to the base station 2.
- the radio telegram according to FIG. 2 has a header 10, by means of which the base station can recognize which type of messages are requested by whom.
- the message according to FIG. 2 has a field for data type 11.
- the data type 11 indicates how the data part 12 and 13 of the radio telegram is structured from the mobile station to the base station.
- the base station is now able, on the one hand, to identify the station to be transmitted and, on the other hand, to recognize the request profile.
- the transmitted radio telegram is evaluated in accordance with data type 11 by the corresponding service provider in the base station.
- the data part 12 is shown in more detail in FIG. 3.
- the data part 12 comprises a field 15 which indicates how many data groups are stored in the memory 7.
- Field 16 indicates whether one or more data groups are allowed when the traffic reports are sent back for evaluation. Act it Only simple recipients who are unable to ensure the evaluation of traffic reports on the basis of several data groups are transmitted in data field 16 that only one data group may be used to generate the traffic messages. The fact that only one data group can be used also arises if only a single data group, for example the location codes, and the road connections from Germany are stored in the memory 7.
- Data field 17 and 18 contains data group information. If only one data group is stored in the memory 7 and only one data group is permitted due to the data field 15, only one data group information is transmitted in the data field 17.
- the data fields 17 and 18 can be supplemented by further data fields.
- the data field 15 must be consistent with the number of data group information in the data fields 17, 18 and following. If the traffic report can only be evaluated with one data group when transmitting mobile radio devices, this is indicated in field 16.
- the data word is supplemented by a further data field 13, through which further information is to be transmitted.
- the other information that can also be transmitted is e.g. B. to information about the intended use of toll roads, and / or the type of vehicle and information about the current location of the vehicle and the desired destination.
- the content of data fields 17 or 18 is shown in detail in FIG. At version 19, the version number of the data group, which is stored in memory 7, is transmitted. On Position 20 stores the issue date on which this data group was issued. The manufacturer of the data group is entered at position 21 in order to be able to distinguish different manufacturers with specific differences in one and the same data group. The manufacturer's version number is given at position 22. This information ensures that the devices in the vehicle are able to reliably decode the traffic reports on the part of the mobile radio device. While it can usually be assumed that a service provider knows the data groups in different versions and from different manufacturers, the vehicle devices will usually have different data groups depending on the age of the vehicle, the manufacturer of the navigation device or the vehicle manufacturer, with regard to their content and their age.
- FIG. 5 shows the data word which is broadcast by the service provider via the base station 2 after it has received and evaluated the data word according to FIG. 2.
- the data field 25 contains the header which, for example, contains the destination address as information, ie for which mobile radio station the message is intended.
- the number of transmitted messages is indicated in field 26, so that the mobile radio device can recognize when the message is complete.
- Field 27 indicates which data group in memory 7 the radio receiver 4 must access in order to be able to evaluate the following information. This information corresponds to the information sent by the mobile radio device 4 in field 19 to the base station. This field is particularly important if the radio receiver is only able to evaluate only one data group when transmitting a message or if only one data group is stored in the memory 7. Traffic messages are now transmitted in field 28, which further fields 29 can follow if more than one traffic message is to be transmitted.
- FIG. 6 shows in detail how the field 28 or further fields 29 are structured in detail.
- the location code of a traffic message is transmitted at location 30, for example at which location of a motorway a traffic jam is to be expected.
- the extent of the traffic disruption is indicated at point 31.
- Position 32 indicates the direction in which the traffic obstruction is located, whether it is, for example, a traffic obstruction in the south or west direction or a traffic obstruction in the north or east direction.
- the location code 30 is in turn divided into two pieces of information, first the data field 35 in which the version number of the field 19 is written, and the actual location code 36.
- This measure ensures that when the Receiver is able to evaluate location codes from different data groups in a data telegram, receives an indication of which data group a particular location code belongs to. For example, if you imagine that the data group for Germany for Saarmaschinen has the same location code as Nice for the data group France, it is very It is important that the data group is also specified for the location code. However, this has the consequence that the location code does not have to be transmitted with a very small bit width, for example with 8 or 16 bits, but with a larger bit width, for example with 32 bits.
- the field 27 is then an empty field in which, for. B. a zero is written.
- the location code of the data field 30 can be shortened to 8 or 16 bits, but it is not possible to pass on data group information. For this reason, for simple receivers, the output of traffic information is limited to a data group that is defined in field 27, in the example mentioned either to Germany or to France.
- FIG. 8 now shows the structure of data groups that is stored in the memory 7 assigned to the mobile radio device 4.
- Data group 38 is a table in which location codes, road connections and standard texts from Germany are stored, as is described in more detail, for example, in DE 35 36 820 or in standard ENV-278/7/3/006.
- the data group 39 relates to location information and road connections that can be found in France and the data group 40 relates to tables in which location codes and road connections of the city of Frankfurt a. M. are listed in more detail.
- the list of data groups can be designed as desired. Data groups with tourist sights, such as the Black Forest or the Allgäu, are also possible.
- the navigation system 6 On the basis of the transmitted traffic information, it is possible for the navigation system 6 to calculate a route from the instantaneous point to the destination point, taking into account the requested traffic reports, whereby traffic obstructions can be avoided as far as this is necessary. It is also useful if the current point and the destination are known to only transmit traffic reports that are in a corridor between the current point and the destination. This ensures that not all traffic reports from Germany or France have to be transmitted, but that traffic reports can be limited to a certain area in the direction of the route.
Landscapes
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Atmospheric Sciences (AREA)
- Radar, Positioning & Navigation (AREA)
- Life Sciences & Earth Sciences (AREA)
- Engineering & Computer Science (AREA)
- Remote Sensing (AREA)
- Navigation (AREA)
- Traffic Control Systems (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephonic Communication Services (AREA)
- Communication Control (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Claims (12)
- Procédé pour demander et pour traiter des messages de trafic routier, selon lequel une requête de message de trafic est envoyée par un appareil radio (4) et au moins un message de trafic qui est transmis à l'appareil radio (4) est préparé par un prestataire de services par l'intermédiaire d'un poste de base (2), les messages routiers étant transmis par radio en tant que flash d'information, de préférence en tant qu'information TMC,
caractérisé en ce que
la requête de message de trafic comprend des informations sur la version du groupe de données ou des groupes de données mémorisées dans la mémoire (7) associée à l'appareil radio (4) et/ou sur le producteur des données mémorisées et/ou sur la date d'édition des données mémorisées, et seuls les messages de trafic qui sont exploitables grâce aux données ou aux groupes de données mémorisés dans la mémoire (7) associée à l'appareil radio (4) sont transmis en tant que messages en retour par le prestataire de services à l'appareil radio (4). - Procédé selon la revendication 1,
caractérisé en ce que
dans la mémoire (7) sont mémorisés plusieurs groupes de données pour différentes données géographiques. - Procédé selon la revendication 1 ou 2,
caractérisé en ce que
pour une région géographique plusieurs groupes de données (38, 39, 40) comportant des détails différents sont stockés dans la mémoire (7). - Procédé selon l'une des revendications précédentes,
caractérisé en ce que
la version et/ou le producteur et/ou la date d'édition sont transmis dans la requête de message de trafic séparément pour chaque groupe de données. - Procédé selon l'une des revendications précédentes,
caractérisé en ce que
la requête de message de trafic contient une information (16) indiquant si l'appareil radio (4) à l'aide d'un appareil de navigation (6) n'exploite que des messages sur la base d'un groupe de données (38, 39, 40), et en fonction de cette information (16) seuls sont transmis les messages qui peuvent être exploités à l'aide d'un groupe de données (38, 39, 40). - Procédé selon l'une des revendications précédentes,
caractérisé en ce que
la requête de message de trafic est envoyée sur demande. - Procédé selon l'une des revendications 1 à 5,
caractérisé en ce que
la requête de message de trafic est envoyée automatiquement, de préférence à des intervalles de temps prédéterminés. - Procédé selon l'une des revendications précédentes,
caractérisé en ce qu'
un itinéraire est calculé de l'endroit actuel de l'appareil radio (4) jusqu'à un endroit cible en tenant compte des messages de trafic demandés. - Procédé selon l'une des revendications précédentes,
caractérisé en ce que
l'endroit actuel de l'appareil radio (4) et l'endroit cible sont transmis par l'appareil radio (4) avec la requête de message de trafic et seuls des messages dans un couloir entre l'endroit actuel et l'endroit cible sont transmis à l'appareil radio (4). - Procédé selon l'une des revendications précédentes,
caractérisé en ce qu'
un code local (36) est transmis conjointement avec l'information sur la version (35) lorsqu'il est possible d'exploiter plusieurs groupes de données (38, 39, 40) dans l'appareil radio (4). - Procédé selon l'une des revendications précédentes,
caractérisé en ce que
la version du groupe de données (27) est transmise une seule fois par le poste de base (2) lorsque l'appareil radio (4) a signalé que l'exploitation des messages de trafic se fonde sur un groupe de données (38, 39, 40). - Procédé selon les revendications 1 à 10,
caractérisé en ce que
la version du groupe de données (35) est transmise avec le code local (36) du message de trafic concerné lorsque l'appareil radio (4) a signalé que l'exploitation des messages de trafic peut se fonder sur plusieurs groupes de données (38, 39, 40).
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
DE19937372 | 1999-08-12 | ||
DE19937372A DE19937372A1 (de) | 1999-08-12 | 1999-08-12 | Verfahren zur Anforderung und zur Verarbeitung von Verkehrsmeldungen |
Publications (3)
Publication Number | Publication Date |
---|---|
EP1079353A2 EP1079353A2 (fr) | 2001-02-28 |
EP1079353A3 EP1079353A3 (fr) | 2001-08-22 |
EP1079353B1 true EP1079353B1 (fr) | 2004-04-28 |
Family
ID=7917595
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP00115719A Expired - Lifetime EP1079353B1 (fr) | 1999-08-12 | 2000-07-21 | Méthode pour demander et traiter des messages routiers |
Country Status (8)
Country | Link |
---|---|
US (1) | US6434477B1 (fr) |
EP (1) | EP1079353B1 (fr) |
JP (1) | JP2001082967A (fr) |
AT (1) | ATE265727T1 (fr) |
AU (1) | AU775994B2 (fr) |
DE (2) | DE19937372A1 (fr) |
DK (1) | DK1079353T3 (fr) |
ES (1) | ES2219229T3 (fr) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7804860B2 (en) | 2005-10-05 | 2010-09-28 | Lg Electronics Inc. | Method of processing traffic information and digital broadcast system |
US7840868B2 (en) | 2005-10-05 | 2010-11-23 | Lg Electronics Inc. | Method of processing traffic information and digital broadcast system |
US8332131B2 (en) | 2005-05-18 | 2012-12-11 | Lg Electronics Inc. | Method and apparatus for providing transportation status information and using it |
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 |
Families Citing this family (31)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7620556B1 (en) * | 2000-12-11 | 2009-11-17 | Alcatel-Lucent Usa Inc. | Telecommunications system for broadcasting and receiving information whose pertinence is at least partially based on geography |
DE10111131A1 (de) * | 2001-03-08 | 2002-10-02 | Harman Becker Automotive Sys | System und Verfahren zur Verarbeitung von Verkehrsinformationen |
DE10215848A1 (de) * | 2002-04-10 | 2003-10-23 | Bosch Gmbh Robert | Verfahren zum Austausch nutzer und/oder gerätespezifischer Daten zwischen nutzerseitigen Einrichtungen und einem Diensteanbieter |
US6741932B1 (en) | 2002-04-16 | 2004-05-25 | Navigation Technologies Corp. | Method and system for using real-time traffic broadcasts with navigation systems |
US7251558B1 (en) * | 2003-09-23 | 2007-07-31 | Navteq North America, Llc | Method and system for developing traffic messages |
US7050903B1 (en) * | 2003-09-23 | 2006-05-23 | Navteq North America, Llc | Method and system for developing traffic messages |
US7505732B2 (en) * | 2004-12-22 | 2009-03-17 | Fmr Llc | Broadcasting user-specific information |
US7457835B2 (en) | 2005-03-08 | 2008-11-25 | Cisco Technology, Inc. | Movement of data in a distributed database system to a storage location closest to a center of activity for the data |
TW200636631A (en) * | 2005-04-15 | 2006-10-16 | Mitac Int Corp | Satellite navigation device for real-time route planning |
TWI282525B (en) * | 2005-04-15 | 2007-06-11 | Mitac Int Corp | Information integration method for satellite navigation device |
KR20060119741A (ko) * | 2005-05-18 | 2006-11-24 | 엘지전자 주식회사 | 소통상태의 추이정보를 제공하고 이를 이용하는 방법 및장치 |
BRPI0610713B1 (pt) * | 2005-05-18 | 2019-05-14 | Lg Electronics Inc | Provimento de informação de tráfego relacionada com uma predição do estado de congestionamento e uso da mesma |
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 |
KR101061460B1 (ko) * | 2005-05-18 | 2011-09-02 | 엘지전자 주식회사 | 소통상태에 대한 예측정보를 제공하고 이를 이용하는 방법및 장치 |
KR20060119743A (ko) * | 2005-05-18 | 2006-11-24 | 엘지전자 주식회사 | 구간 속도에 대한 예측정보를 제공하고 이를 이용하는 방법및 장치 |
KR20060119739A (ko) * | 2005-05-18 | 2006-11-24 | 엘지전자 주식회사 | 구간 통과시간에 대한 예측정보를 제공하고 이를 이용하는방법 및 장치 |
KR20060119742A (ko) * | 2005-05-18 | 2006-11-24 | 엘지전자 주식회사 | 도로 정보를 제공하고 이를 이용하는 방법 및 장치 |
KR20060122668A (ko) * | 2005-05-27 | 2006-11-30 | 엘지전자 주식회사 | 교통 정보 제공 방법 및 수신 장치 |
KR20060125449A (ko) * | 2005-06-01 | 2006-12-06 | 엘지전자 주식회사 | 교통 정보를 제공하고 이를 이용하는 방법 및 장치 |
CA2562220C (fr) * | 2005-10-05 | 2013-06-25 | Lg Electronics Inc. | Methode de traiter de l'information de trafic et systeme de radiodiffusion numerique |
CA2562206C (fr) * | 2005-10-05 | 2012-07-10 | Lg Electronics Inc. | Procede et emetteur de diffusion numerique servant a emettre un signal de radiodiffusion numerique |
CA2562202C (fr) | 2005-10-05 | 2013-06-18 | Lg Electronics Inc. | Methode de traiter de l'information de trafic et systeme de radiodiffusion numerique |
KR101254219B1 (ko) * | 2006-01-19 | 2013-04-23 | 엘지전자 주식회사 | 링크 식별 방법 및 링크 식별 장치 |
CA2562209C (fr) | 2005-10-05 | 2011-11-22 | Lg Electronics Inc. | Methode de traiter de l'information de trafic et systeme de radiodiffusion numerique |
US7668209B2 (en) * | 2005-10-05 | 2010-02-23 | Lg Electronics Inc. | Method of processing traffic information and digital broadcast system |
US7720062B2 (en) * | 2005-10-05 | 2010-05-18 | Lg Electronics Inc. | Method of processing traffic information and digital broadcasting system |
DE102007019244A1 (de) * | 2007-04-24 | 2008-10-30 | Robert Bosch Gmbh | Navigationseinrichtung und Verfahren zur grafischen Darstellung von Teilgebieten mit Verkehrsbeschränkungen |
DE112009004558B4 (de) * | 2009-03-12 | 2017-07-13 | Toyota Jidosha Kabushiki Kaisha | Informationsbereitstellungsverfahren, informationsbereitstellungssystem und informationsbereitstellungszentrum sowie fahrzeuginterne vorrichtung, die das informationsbereitstellungssystem bildet |
US8527198B2 (en) | 2010-12-23 | 2013-09-03 | Honda Motor Co., Ltd. | Predictive traffic warning and suggestive rerouting system and method |
FR2982988B1 (fr) * | 2011-11-23 | 2014-08-22 | Wikango | Systeme electronique d'aide a la conduite a mise a jour geolocalisee et procede associe |
DE102012223780A1 (de) * | 2012-12-19 | 2014-06-26 | Bayerische Motoren Werke Aktiengesellschaft | Verfahren und System zum Erzeugen von Verkehrsinformationen für mindestens ein Fahrzeug |
Family Cites Families (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE3536820A1 (de) | 1985-10-16 | 1987-04-16 | Bosch Gmbh Robert | Verkehrfunk-decoder |
DE3914104A1 (de) * | 1989-04-28 | 1990-11-15 | Bosch Gmbh Robert | Rundfunkempfaenger, insbesondere fahrzeugempfaenger |
US5131020A (en) | 1989-12-29 | 1992-07-14 | Smartroutes Systems Limited Partnership | Method of and system for providing continually updated traffic or other information to telephonically and other communications-linked customers |
DE4008460A1 (de) * | 1990-03-16 | 1991-09-19 | Bosch Gmbh Robert | Navigationssystem |
SE516278C2 (sv) * | 1994-03-04 | 2001-12-10 | Volvo Ab | Trafikinformationssystem och förfarande för tillhandahållande av trafikinformation |
US5543789A (en) | 1994-06-24 | 1996-08-06 | Shields Enterprises, Inc. | Computerized navigation system |
FR2734938A1 (fr) * | 1995-05-31 | 1996-12-06 | Philips Electronics Nv | Appareil d'information routiere muni d'un generateur de messages polyglotte |
DE19538453A1 (de) * | 1995-10-16 | 1997-04-17 | Bayerische Motoren Werke Ag | Funksignalempfänger für Kraftfahrzeuge mit einem RDS-Dekoder für digitale Signale |
DE19539641C2 (de) * | 1995-10-25 | 2000-02-17 | Daimler Chrysler Ag | Verfahren und Einrichtung zur verkehrssituationsabhängigen Fahrzeugzielführung |
TW303436B (en) * | 1996-03-12 | 1997-04-21 | Philips Electronics Nv | Storage medium carrying geographical location data |
DE19637258A1 (de) * | 1996-09-13 | 1998-03-19 | Philips Patentverwaltung | RDS-TMC-Rundfunkempfänger zur Verarbeitung von regionalspezifischen und überregionalen Straßen- oder Bereichsbezeichnungen |
US6111521A (en) * | 1996-09-18 | 2000-08-29 | Mannesmann Vdo Ag | Apparatus for supplying traffic-related information |
DE19651146A1 (de) | 1996-12-10 | 1998-06-25 | Deutsche Telekom Mobil | Verfahren und Anordnung zur Information mobiler Teilnehmer |
DE19651143B4 (de) | 1996-12-10 | 2013-07-25 | T-Mobile Deutschland Gmbh | Verfahren und Anordnung zur Verkehrsinformation |
DE19708748B4 (de) | 1997-02-25 | 2004-03-25 | Atx Europe Gmbh | Verfahren und System zur Bereitstellung und Übermittlung individualisierter Verkehrsinformationen |
DE19739257A1 (de) | 1997-09-08 | 1999-03-11 | Bosch Gmbh Robert | Verfahren und Empfänger zum Empfang von digital codierten Meldungen |
US6374175B1 (en) | 1997-12-23 | 2002-04-16 | Mannesmann Vdo Ag | Method of using memories in aid of vehicle navigation |
DE19823123C2 (de) * | 1998-05-23 | 2000-05-25 | Opel Adam Ag | Verfahren zum Betrieb eines Navigationssystems für Kraftfahrzeuge |
US6384739B1 (en) * | 1999-05-10 | 2002-05-07 | Bellsouth Intellectual Property Corporation | Traffic monitoring system and method |
-
1999
- 1999-08-12 DE DE19937372A patent/DE19937372A1/de not_active Withdrawn
-
2000
- 2000-05-11 US US09/568,839 patent/US6434477B1/en not_active Expired - Fee Related
- 2000-07-21 EP EP00115719A patent/EP1079353B1/fr not_active Expired - Lifetime
- 2000-07-21 DE DE50006225T patent/DE50006225D1/de not_active Expired - Lifetime
- 2000-07-21 AT AT00115719T patent/ATE265727T1/de not_active IP Right Cessation
- 2000-07-21 DK DK00115719T patent/DK1079353T3/da active
- 2000-07-21 ES ES00115719T patent/ES2219229T3/es not_active Expired - Lifetime
- 2000-08-11 AU AU51965/00A patent/AU775994B2/en not_active Ceased
- 2000-08-14 JP JP2000246075A patent/JP2001082967A/ja active Pending
Cited By (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8332131B2 (en) | 2005-05-18 | 2012-12-11 | Lg Electronics Inc. | Method and apparatus for providing transportation status information and using it |
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 |
US7804860B2 (en) | 2005-10-05 | 2010-09-28 | Lg Electronics Inc. | Method of processing traffic information and digital broadcast system |
US7840868B2 (en) | 2005-10-05 | 2010-11-23 | Lg Electronics Inc. | Method of processing traffic information and digital broadcast system |
US8018976B2 (en) | 2005-10-05 | 2011-09-13 | Lg Electronics Inc. | Method of processing traffic information and digital broadcast system |
US8018977B2 (en) | 2005-10-05 | 2011-09-13 | Lg Electronics Inc. | Method of processing traffic information and digital broadcast system |
US8018978B2 (en) | 2005-10-05 | 2011-09-13 | Lg Electronics Inc. | Method of processing traffic information and digital broadcast system |
US8098694B2 (en) | 2005-10-05 | 2012-01-17 | Lg Electronics Inc. | Method of processing traffic information and digital broadcast system |
US8473807B2 (en) | 2005-10-05 | 2013-06-25 | Lg Electronics Inc. | Method of processing traffic information and digital broadcast system |
US8542709B2 (en) | 2005-10-05 | 2013-09-24 | Lg Electronics Inc. | Method of processing traffic information and digital broadcast system |
Also Published As
Publication number | Publication date |
---|---|
US6434477B1 (en) | 2002-08-13 |
ES2219229T3 (es) | 2004-12-01 |
DK1079353T3 (da) | 2004-07-26 |
AU775994B2 (en) | 2004-08-19 |
ATE265727T1 (de) | 2004-05-15 |
DE19937372A1 (de) | 2001-02-15 |
DE50006225D1 (de) | 2004-06-03 |
EP1079353A2 (fr) | 2001-02-28 |
EP1079353A3 (fr) | 2001-08-22 |
JP2001082967A (ja) | 2001-03-30 |
AU5196500A (en) | 2001-02-15 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP1079353B1 (fr) | Méthode pour demander et traiter des messages routiers | |
EP0769180B1 (fr) | Dispositif pour preparer et fournir des informations destinees au conducteur d'un vehicule | |
EP0499608B1 (fr) | Recepteur radio, en particulier autoradio | |
DE3536820C2 (fr) | ||
EP1030475A2 (fr) | Méthode pour la transmission d'informations routières codées numériques et récepteur pour mettre en oeuvre cette méthode | |
EP0892379B1 (fr) | Procédé et appareil de télématique pour élaborer et diffuser des informations de circulation significatives | |
DE19857782C2 (de) | Verfahren zum Übertragen von Tabelleninformationen von einer Zentrale an ein Endgerät über einen Übertragungskanal und Zentrale zum Durchführen des Verfahrens | |
EP1105856B1 (fr) | Dispositif pour le codage et le decodage d'emplacements | |
WO2000036771A1 (fr) | Systeme de transmission binaire | |
EP0817151A1 (fr) | Méthode, dispositif embarqué et fixe d'avertissement individuel de difficultés de circulation à venir | |
DE10101349B4 (de) | Verfahren zur Meldung von Verkehrsstörungen | |
EP1338867A1 (fr) | Système d'information pour des données de trafic | |
EP1460599A2 (fr) | Base de données pour codage et décodage des messages de trafic et procédé pour transmettre des messages de trafic codés | |
EP0900432B1 (fr) | Procede et recepteur pour la selection geographique de messages codes numeriquement | |
EP1141911B1 (fr) | Dispositif pour la transmission de recommandations d'itineraires routiers, et recepteur associe | |
CH690347A5 (de) | Einrichtung zur Informationsubertragung in einem beweglichen Nahbereichskommunikationssystem. | |
DE10011702A1 (de) | Verfahren zur standortbezogenen Information von Verkehrsteilnehmern | |
EP0794521A1 (fr) | Système pour guider et informer le trafic | |
EP1076325B1 (fr) | Méthode pour demander et traiter des messages routiers | |
DE19905431A1 (de) | Verfahren zur Übertragung von auf Orte bezogenen Informationen | |
WO1996030883A1 (fr) | Systeme de guidage de la circulation pour reseau routier | |
DE19855638B4 (de) | Verfahren, Empfänger und Sender zur Übertragung von digital codierten Verkehrsinformationen | |
DE10110550B4 (de) | Informationssystem für mobile Teilnehmer | |
DE29724629U1 (de) | Fahrzeugseitige Einrichtung zur individuellen Warnung vor Verkehrsstörungen | |
DE19916656A1 (de) | Vorrichtung zur Information von Verkehrsteilnehmern |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
AK | Designated contracting states |
Kind code of ref document: A2 Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE |
|
AX | Request for extension of the european patent |
Free format text: AL;LT;LV;MK;RO;SI |
|
PUAL | Search report despatched |
Free format text: ORIGINAL CODE: 0009013 |
|
AK | Designated contracting states |
Kind code of ref document: A3 Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE |
|
AX | Request for extension of the european patent |
Free format text: AL;LT;LV;MK;RO;SI |
|
RIC1 | Information provided on ipc code assigned before grant |
Free format text: 7G 08G 1/09 A, 7G 08G 1/0967 B, 7H 04H 1/00 B |
|
17P | Request for examination filed |
Effective date: 20020222 |
|
AKX | Designation fees paid |
Free format text: AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE |
|
17Q | First examination report despatched |
Effective date: 20030320 |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: NL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20040428 Ref country code: FI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20040428 Ref country code: CY Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20040428 Ref country code: IE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20040428 |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D Free format text: NOT ENGLISH |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: EP |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: NV Representative=s name: SCINTILLA AG, DIREKTION |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D Free format text: GERMAN |
|
REF | Corresponds to: |
Ref document number: 50006225 Country of ref document: DE Date of ref document: 20040603 Kind code of ref document: P |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LU Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20040721 |
|
REG | Reference to a national code |
Ref country code: DK Ref legal event code: T3 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20040728 Ref country code: GR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20040728 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: BE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20040731 Ref country code: MC Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20040731 |
|
GBT | Gb: translation of ep patent filed (gb section 77(6)(a)/1977) |
Effective date: 20040804 |
|
NLV1 | Nl: lapsed or annulled due to failure to fulfill the requirements of art. 29p and 29m of the patents act | ||
REG | Reference to a national code |
Ref country code: ES Ref legal event code: FG2A Ref document number: 2219229 Country of ref document: ES Kind code of ref document: T3 Ref country code: IE Ref legal event code: FD4D |
|
ET | Fr: translation filed | ||
BERE | Be: lapsed |
Owner name: ROBERT BOSCH G.M.B.H. Effective date: 20040731 |
|
PLBE | No opposition filed within time limit |
Free format text: ORIGINAL CODE: 0009261 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT |
|
26N | No opposition filed |
Effective date: 20050131 |
|
BERE | Be: lapsed |
Owner name: ROBERT *BOSCH G.M.B.H. Effective date: 20040731 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: PT Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20040928 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: ES Payment date: 20100726 Year of fee payment: 11 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: AT Payment date: 20100721 Year of fee payment: 11 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DK Payment date: 20100726 Year of fee payment: 11 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: CH Payment date: 20110725 Year of fee payment: 12 |
|
REG | Reference to a national code |
Ref country code: DK Ref legal event code: EBP |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: MM01 Ref document number: 265727 Country of ref document: AT Kind code of ref document: T Effective date: 20110721 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DK Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20110731 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20120723 Year of fee payment: 13 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: FR Payment date: 20120803 Year of fee payment: 13 Ref country code: IT Payment date: 20120725 Year of fee payment: 13 Ref country code: DE Payment date: 20120927 Year of fee payment: 13 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: AT Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20110721 |
|
REG | Reference to a national code |
Ref country code: ES Ref legal event code: FD2A Effective date: 20130531 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: ES Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20110722 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
GBPC | Gb: european patent ceased through non-payment of renewal fee |
Effective date: 20130721 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: ST Effective date: 20140331 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20140201 Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20130731 Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20130731 Ref country code: GB Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20130721 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R119 Ref document number: 50006225 Country of ref document: DE Effective date: 20140201 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: FR Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20130731 Ref country code: IT Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20130721 |