[go: up one dir, main page]

EP0790591B1 - Banque de données de lieux pour la détermination d'itinéraires dans un réseau de circulation routière - Google Patents

Banque de données de lieux pour la détermination d'itinéraires dans un réseau de circulation routière Download PDF

Info

Publication number
EP0790591B1
EP0790591B1 EP96116545A EP96116545A EP0790591B1 EP 0790591 B1 EP0790591 B1 EP 0790591B1 EP 96116545 A EP96116545 A EP 96116545A EP 96116545 A EP96116545 A EP 96116545A EP 0790591 B1 EP0790591 B1 EP 0790591B1
Authority
EP
European Patent Office
Prior art keywords
location
locations
location database
public road
references
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
Application number
EP96116545A
Other languages
German (de)
English (en)
Other versions
EP0790591A1 (fr
Inventor
Wolfgang Klingenberg
Ulrich Kersken
Christian Radin
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Robert Bosch GmbH
Original Assignee
Robert Bosch GmbH
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 Robert Bosch GmbH filed Critical Robert Bosch GmbH
Publication of EP0790591A1 publication Critical patent/EP0790591A1/fr
Application granted granted Critical
Publication of EP0790591B1 publication Critical patent/EP0790591B1/fr
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

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/091—Traffic information broadcasting
    • G08G1/092—Coding or decoding of the information

Definitions

  • the invention relates to a location database for the determination of routes within a traffic network and one Radio receiver with a device for receiving and Decoding of digitally coded traffic reports.
  • Radio data system an additional and inaudible transmission of digital data parallel to Broadcast programs in a data channel.
  • Specifications of the radio data system for FM radio are among others in the publication Tech. 3244-E, March 1984 of the European Runfunk Union (EBU).
  • Radio receivers with suitable RDS decoders can transmitted data in addition to radio reception with the Record and decode the same receiver.
  • For the Data transmission is 32 groups of 104 bits each provided, each of the transmitted groups one each certain service is assigned.
  • Group 8a is for Time for the transmission of digitally coded Traffic announcements provided.
  • This location database structure so no relationships between the same places on different traffic routes are recognizable, is sufficient for the decoding of the Traffic-news.
  • For the output of the decoded Traffic announcements are then the same for each Place also provided the same name, which is in coded form each time the same location appears in the location database is specified. However, this information is only used to output the actual name as an alphanumeric display or Voice output.
  • the computer carrying out this selection the expected route is known. This can be done by the expected route is entered manually. Another option is the destination enter and have the route determined by the computer. Suitable calculation methods are known and for example available within PC programs. It will however, a road map is required which is the one in question upcoming roads and intersections as well as the distances between the intersections and other places.
  • EP-A-0 760 565 A1 describes one method and one Device for selecting traffic information known become, in which a route guidance by means of Traffic information is possible.
  • the Additional table necessary for RDS-TMC operation Information that enables route calculation.
  • the table is enriched with a board of complementary attributes, which specifies the distance between each location on the table are adjacent to the location in question. Furthermore, too Indications given as two places on a bypass can be achieved that are not in the RDS-TMC table is included. This will make it possible to find the way between two places or a detour to be taken to calculate.
  • the object of the present invention is a Location database for the determination of routes within a Traffic network indicate the one hand on this Location database based and on the other hand also a decoding of digitally coded traffic reports according to specified Procedure allows.
  • the location database according to the invention also has the Advantage that only a small storage capacity per location is required.
  • the inventive Location database on already created for the TMC system Location databases are largely used by only information is added.
  • a reduction in storage capacity is according to one Continuing education possible because of each location and traffic route just a cross reference to the same place on another Traffic route is provided, with locations on more than two traffic routes cyclically executed the cross references are. This gives each of these locations only one Cross-reference. It is then not necessary per location Storage space for the largest number of possible Provide traffic routes on which a place lies.
  • Location databases used for decoding digitally encoded Traffic reports serve, do not have to be a complete one Road network included. In such location databases are missing for example, crucial in some places Road connections: partly because parts of the Motorways are still under construction or because of connectors are not listed in the location database. At a appropriate coding of traffic reports on this The limits of the local database can be taken into account Traffic reports can still be decoded.
  • the driver When planning the route, the driver is still the one take into account the route concerned and for example in Take a few kilometers of main road instead of one Detour to drive on highways. So that the determination of the Route these anyway in the local database as dead ends can take into account the streets shown is according to a another development of the invention in location databases, which contain the coordinates of the locations, provided that furthermore, locations not encoded by a The traffic route provided for traffic reports is connected, are cross-referenced.
  • the consideration of is not for the decoding of the traffic routes provided is possible that further selected places that are except on one for the Decoding provided on another traffic route for the decoding is not intended traffic route Reference is made to the further traffic route and that the further traffic route with the places where clues are available on the further traffic route in the Location database is listed.
  • the length of the other traffic routes are taken into account in that Distances between locations on the others Traffic routes are stored.
  • a radio receiver with a device for receiving and for decoding digitally coded traffic reports with A location database is identified by a Establishment of routes using the Location database according to one of the preceding claims.
  • Radio receiver According to the invention can be provided that at the determination of routes an evaluation of the lengths of the Traffic routes take place according to the respective road type.
  • a further development of the radio receiver according to the invention consists of the determined routes for the selection of received digitally coded traffic reports that only those traffic reports are used are output which relate to the determined routes. According to a further development, it can be provided that the routes determined can be represented graphically.
  • the section shown in Fig. 1 from a Location database contains six records, four of which are to locations on the A1 motorway, one to a location on the A61 motorway and another to a location on the A53 motorway Respectively.
  • each record contains according to ALERT C, a location code, a location type (Type), the indication of the street number (Road Number), the type the junction (Exit Type), the name of the respective Place and references to the previous and the following Location (offset +, offset-).
  • the place names are written out for the sake of clarity shown, located in the realized location database there is, however, a place name code below which in a Place name database the place name is stored. This one has the advantage that the location database does not differ long place names must be taken into account that the encoded place names take up less space and that if necessary, foreign language in the place name database Place names for foreign drivers should be listed can.
  • Fig. 1 are seen geographically same places - in this case the place Bliesheim - in the Location database listed completely independently of each other and also provided with different location codes. To one To enable route determination are shown in the Location database cross-references (cross-ref.) For those locations registered that lie on several traffic routes. Since the Place Bliesheim - what is meant here is not the community, but the motorway junction - they are on three traffic routes Cross-references cyclically interchanged, so that with each data record only a cross reference is necessary.
  • location code 4144 (Bliesheim an der A1) to the previous location 4143, the subsequent location 4145 and the geographically identical location 6380 on the A61 motorway entered.
  • the latter contains a reference to the location 7235 on the A553 and this one Cross-reference to location 4144 on the A1 motorway.
  • places 4144, 6380 and 7235 are one represent only place within the transport network.
  • there is a record for place 7235 Feature Since the A553 motorway ends at this location as a subsequent place a special mark entered, namely 0xffff.
  • the "offset" interpreted the following data as a cross-reference or reference.
  • Fig. 4 shows a section of a location database, the Locations in the area shown as a road map in Fig. 5 contains.
  • the Autobahn A31 a gap between the junctionshafen-Gostenhof and Laufen-Ost on what at the Entries 0xffff is recognizable. Since using intermediate city expressways it makes sense to do this when determining a route be taken into account.
  • the location database according to FIG. 4 are therefore cross references to the places 6644 and 6645 Places 15006 and 15007 on one with respect to the Location database fictional street F between these two locations specified.
  • a place type was used for these two places Designation FCT_LOC selected, which means that these places lying on a fictional street.
  • the endpoints of this fictional road are the Provide locations with references Offset +, Offset- and 0xffff. These locations also have cross-references to the locations 6644 and 6645, each with a geographical Form place.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Traffic Control Systems (AREA)

Claims (12)

  1. Banque de données de lieux pour déterminer des itinéraires dans un réseau de circulation, comprenant une banque de données de lieux pour décoder des messages de circulation à codage numérique, cette banque contenant pour le décodage de messages de circulation en code numérique, les lieux nécessaires comme codes de lieux, dans laquelle chaque fois à un code de lieu est associé un itinéraire, et des indications concernant les lieux voisins sur le même itinéraire dans un jeu de données, les codes de lieux ayant des liens transversaux (9, 12, 14, 16) qui indiquent le même lieu (3, 7, 12) sur d'autres chemins de circulation à l'intérieur de la banque de données et les liens transversaux sont formés à partir du code du lieu situé sur l'autre chemin de circulation.
  2. Banque de données de lieux selon la revendication 1,
    caractérisée en ce que
    chaque lieu et chaque itinéraire ne comporte qu'un lien transversal vers le même lieu sur un autre chemin de circulation,
    et les lieux sur plus de deux itinéraires sont fournis de manière cyclique avec les liens transversaux (12, 14, 16).
  3. Banque de données de lieux selon l'une quelconque des revendications précédentes,
    caractérisée en ce que
    dans les jeux de données des lieux sur un itinéraire, et qui se situent sur un autre itinéraire, on a enregistré des indications concernant le lieu chaque fois suivant sur l'itinéraire et qui se situe également sur au moins un autre itinéraire.
  4. Banque de données de lieux selon l'une quelconque des revendications précédentes, selon laquelle on indique les coordonnées des lieux,
    caractérisée en ce qu'
    en outre des lieux qui ne sont pas liés à un itinéraire prévu pour le codage de messages de circulation, sont munis d'un lien transversal réciproque.
  5. Banque de données de lieux selon l'une quelconque des revendications 1 à 3, indiquant les éloignements entre les lieux,
    caractérisée en ce que
    pour les lieux sélectionnés en outre qui se trouvent en dehors d'un itinéraire prévu pour le décodage, sur un autre itinéraire non prévu pour le décodage, il est prévu une indication relative à cet autre itinéraire et cet autre itinéraire avec les lieux pour lesquels il y a des indications concernant l'autre itinéraire, est enregistré dans la banque de données de lieux.
  6. Banque de données de lieux selon 1a revendication 5,
    caractérisée en ce que
    les éloignements entre les lieux sont enregistrés sur les autres itinéraires.
  7. Banque de données de lieux selon l'une quelconque des revendications 5 ou 6,
    caractérisée en ce que
    le type de chaussée (type d'endroit) est enregistré pour les autres itinéraires.
  8. Banque de données de lieux selon l'une quelconque des revendications précédentes,
    caractérisée en ce que
    dans les jeux de données on a chaque fois une information supplémentaire formée d'au moins un bit concernant la présence de liens transversaux et/ou d'indications et le cas échéant du nombre et/ou de la nature des liens transversaux et/ou des indications.
  9. Récepteur radio avec une installation pour recevoir et décoder des messages de circulation en codage numérique à l'aide d'une banque de données de lieux,
    caractérisé par
    une installation pour déterminer des itinéraires en utilisant la banque de données de lieux selon l'une quelconque des revendications précédentes.
  10. Récepteur radiophonique selon la revendication 9,
    caractérisé en ce qu'
    en déterminant les trajets on exploite les longueurs des itinéraires selon le type de chaussée respectif.
  11. Récepteur radiophonique selon l'une quelconque des revendications 9 ou 10,
    caractérisé en ce qu'
    on utilise les itinéraires obtenus pour sélectionner les messages de circulation à codage numérique reçus, pour émettre seulement les messages de circulation qui concernent l'itinéraire choisi.
  12. Récepteur radiophonique selon l'une quelconque des revendications 9 à 11,
    caractérisé en ce que
    les itinéraires obtenus sont présentés graphiquement.
EP96116545A 1996-02-17 1996-10-16 Banque de données de lieux pour la détermination d'itinéraires dans un réseau de circulation routière Expired - Lifetime EP0790591B1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE19606010 1996-02-17
DE19606010A DE19606010A1 (de) 1996-02-17 1996-02-17 Ortsdatenbank für die Ermittlung von Routen innerhalb eines Verkehrswegenetzes

Publications (2)

Publication Number Publication Date
EP0790591A1 EP0790591A1 (fr) 1997-08-20
EP0790591B1 true EP0790591B1 (fr) 2002-03-27

Family

ID=7785744

Family Applications (1)

Application Number Title Priority Date Filing Date
EP96116545A Expired - Lifetime EP0790591B1 (fr) 1996-02-17 1996-10-16 Banque de données de lieux pour la détermination d'itinéraires dans un réseau de circulation routière

Country Status (2)

Country Link
EP (1) EP0790591B1 (fr)
DE (2) DE19606010A1 (fr)

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE19747230A1 (de) * 1997-10-25 1999-05-12 Bosch Gmbh Robert Verfahren zur Berücksichtigung ergänzender Verkehrsinformationen in einer fahrzeugfesten Zielführungseinrichtung
US6636800B1 (en) 1997-10-27 2003-10-21 Siemens Aktiengesellschaft Method and device for computer assisted graph processing
DE19750791C2 (de) * 1997-11-07 2000-01-05 Peter E Dunse Adressierungs- und Identifizierungssystem für adressierte Informationen an und von mobile(n) Verkehrsteilnehmer(n)
DE19810173A1 (de) * 1998-03-10 1999-10-07 Bosch Gmbh Robert Navigationssystem für Kraftfahrzeuge
DE19861486B4 (de) * 1998-03-18 2013-07-25 Robert Bosch Gmbh Datenvorrichtung für ein Kraftfahrzeug
DE19811707A1 (de) * 1998-03-18 1999-09-30 Bosch Gmbh Robert Datenvorrichtung für ein Kraftfahrzeug
DE19839413A1 (de) 1998-08-29 2000-03-02 Bosch Gmbh Robert Verfahren zur Verknüpfung von digitalen Verkehrswegenetzbeschreibungen und Ortsdatenbank
EP1011219A3 (fr) * 1998-12-14 2005-01-26 ATX Europe GmbH Méthode et dispositif pour la génération d'informations routières concernant des situations routières couvrant une pluralité de segments d'un réseau routier
DE19858568A1 (de) * 1998-12-18 2000-06-21 Bosch Gmbh Robert Einrichtung zur Übertragung von Fahrtroutenempfehlungen und Empfänger
US6292743B1 (en) * 1999-01-06 2001-09-18 Infogation Corporation Mobile navigation system
DE19956108A1 (de) * 1999-11-22 2001-05-23 Mannesmann Vdo Ag Verfahren zur dynamischen Zielführung eines Kraftfahrzeugs
KR20080049387A (ko) * 2006-11-30 2008-06-04 엘지전자 주식회사 교통정보 수신기용 저장매체 및 이를 구비한 교통정보수신장치 그리고 교통정보 메세지의 처리방법

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0290679B2 (fr) * 1987-05-09 2003-08-06 Koninklijke Philips Electronics N.V. Dispositif de réception et de traitement de messages d'information routière
FR2689667B1 (fr) * 1992-04-01 1995-10-20 Sagem Recepteur de bord d'aide a la navigation d'un vehicule automobile.
FR2716994B1 (fr) * 1994-03-04 1996-03-29 Renault Procédé et dispositif de sélection d'informations routières.

Also Published As

Publication number Publication date
DE59608960D1 (de) 2002-05-02
DE19606010A1 (de) 1997-08-21
EP0790591A1 (fr) 1997-08-20

Similar Documents

Publication Publication Date Title
EP0769180B1 (fr) Dispositif pour preparer et fournir des informations destinees au conducteur d'un vehicule
EP0769181B1 (fr) Dispositif permettant de fournir des informations au conducteur d'un vehicule
EP0902406B1 (fr) Procédé de transmission de données routières et d'analyse du réseau de circulation routière, unité centrale de mesure du trafic routier et terminal associé
EP1141909B1 (fr) Procede de transmission d'informations routieres
EP0730726B1 (fr) Procede de realisation d'une carte routiere numerisee
EP0584310A1 (fr) Recepteur de radiodiffusion pour la circulation routiere
DE3810177A1 (de) Rundfunkempfaenger, insbesondere fahrzeugempfaenger
EP0790591B1 (fr) Banque de données de lieux pour la détermination d'itinéraires dans un réseau de circulation routière
EP1145210B1 (fr) Procede pour identifier des evenements couvrant plusieurs segments, par l'intermediaire desdits segments
EP1966780B1 (fr) Procede de codage de messages, procede de decodage de messages et recepteur pour recevoir et interpreter des messages
EP1062481B1 (fr) Procede d'affichage d'informations de trafic
EP1114406B1 (fr) Procede pour coder des encombrements affectant plusieurs voies de circulation
EP1460599B1 (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
EP0962004B1 (fr) Dispositif et procede servant a donner des informations sur les encombrements de la circulation
EP1141911B1 (fr) Dispositif pour la transmission de recommandations d'itineraires routiers, et recepteur associe
DE10052934A1 (de) Verfahren zur Bestimmung eines Weges zwischen einem Ausgangspunkt und einem Endpunkt eines Netzes, wie beispielsweise Straßennetzes
EP0984416B1 (fr) Procédé de rattachement de descriptions numériques de réseaux de circulation routière et une base de données de lieux
EP1092950A1 (fr) Procédé pour déterminer le trajet d'un véhicule
DE10311516A1 (de) Verfahren zur Fahrtroutenberechnung in einem Navigationssystem
DE19941648C2 (de) Verfahren zur Übertragung von Verkehrsinformationen betreffend ein Straßenverkehrsnetz von einer Verkehrsinformationszentrale an mindestens ein Endgerät sowie Verkehrsinformationszentrale und Endgerät zur Durchführung des Verfahrens
EP1011219A2 (fr) Méthode et dispositif pour la génération d'informations routières concernant des situations routières couvrant une pluralité de segments d'un réseau routier
DE19948109A1 (de) Verkehrsinformations-Generation bei sich über mehrere verkettete Segmente eines Straßenverkehrsnetzes erstreckenden Zuständen
DE19917842A1 (de) Verfahren zur Identifizierung segmentübergreifender Ereignisse durch Segmente

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: A1

Designated state(s): DE FR GB NL

17P Request for examination filed

Effective date: 19980220

17Q First examination report despatched

Effective date: 20000706

GRAG Despatch of communication of intention to grant

Free format text: ORIGINAL CODE: EPIDOS AGRA

GRAG Despatch of communication of intention to grant

Free format text: ORIGINAL CODE: EPIDOS AGRA

GRAH Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOS IGRA

REG Reference to a national code

Ref country code: GB

Ref legal event code: IF02

GRAH Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOS IGRA

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): DE FR GB NL

REF Corresponds to:

Ref document number: 59608960

Country of ref document: DE

Date of ref document: 20020502

ET Fr: translation filed
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: 20021230

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: NL

Payment date: 20061018

Year of fee payment: 11

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20061024

Year of fee payment: 11

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20061221

Year of fee payment: 11

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20071016

NLV4 Nl: lapsed or anulled due to non-payment of the annual fee

Effective date: 20080501

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: 20080501

REG Reference to a national code

Ref country code: FR

Ref legal event code: ST

Effective date: 20080630

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 NON-PAYMENT OF DUE FEES

Effective date: 20080501

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20061020

Year of fee payment: 11

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20071016

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: 20071031