EP1064638B1 - Systeme de navigation traitant des evenements de la circulation - Google Patents
Systeme de navigation traitant des evenements de la circulation Download PDFInfo
- Publication number
- EP1064638B1 EP1064638B1 EP99915596A EP99915596A EP1064638B1 EP 1064638 B1 EP1064638 B1 EP 1064638B1 EP 99915596 A EP99915596 A EP 99915596A EP 99915596 A EP99915596 A EP 99915596A EP 1064638 B1 EP1064638 B1 EP 1064638B1
- Authority
- EP
- European Patent Office
- Prior art keywords
- traffic
- road
- event
- affected
- road segments
- 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
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/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/091—Traffic information broadcasting
- G08G1/093—Data selection, e.g. prioritizing information, managing message queues, selecting the information to be output
-
- 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/096833—Systems involving transmission of navigation instructions to the vehicle where different aspects are considered when computing the route
- G08G1/096844—Systems involving transmission of navigation instructions to the vehicle where different aspects are considered when computing the route where the complete route is dynamically recomputed based on new data
Definitions
- the invention relates to a navigation system for providing navigational information to a driver, the system comprising:
- the invention further relates to a method for presenting navigational information to a driver the method comprising the steps of:
- a traffic message containing traffic congestion data relating to a certain location on the roads is assembled in a central subsystem on the basis of various inputs, e.g. traffic detectors and police reports.
- the traffic message is broadcast by the central subsystem and received by a receiver in a vehicle subsystem.
- the vehicle subsystem subsequently presents the traffic message to the driver.
- the traffic message may be presented as a textual message on a display, as an audible message through speech synthesis of the traffic message, or as a graphical symbol superimposed on a map overlay.
- the area is divided into a number of cells and it is established to what cell a particular message relates.
- the vehicle subsystem keeps track in which cell the vehicle is travelling and which other cells may be relevant in view of the route followed by the vehicle.
- the vehicle subsystem may be operated in such a way that only traffic messages relating to a relevant cell are actually presented to the driver. So the known navigational system filters.the traffic messages received in the vehicle. If a traffic message passes the filter, then the event included in the traffic message and the location to which the event relates are presented to the driver of the vehicle. The driver may subsequently decide to choose another route in order to avoid the traffic event on the indicated location.
- This object is achieved according to the invention in a navigation system that is characterised in that the system comprises defining means for defining at least one further one of the road segments as additionally affected by the traffic event and that the processing means are arranged for processing the traffic message in relation to the additionally affected road segments.
- the invention is based on the insight that the service of broadcasting traffic messages is limited to major roads and important, large traffic events only and will not include traffic messages related to small roads with minor, less important delays.
- a traffic event like a traffic queue on a motor way, the roads in the vicinity of that event are more occupied with traffic than usual, which may result in traffic queues on these roads as well.
- the inventors have realised that by given the reported traffic event a larger impact than the single reported road, the said limitation of the service of broadcasting traffic messages is mitigated and the actual result of the traffic event is better taken into account.
- An advantage of the navigation system according to the invention is the improved appreciation of the reported traffic event.
- a human receiving a traffic message concerning a certain traffic event could conclude that the traffic event also influences the area around the reported location and that a small detour around that location would be pointless, since such detour would include roads which would have problems too.
- the navigation system according to the invention by taking into account that a traffic message has a larger impact than the single reported location, will in a similar way as the human not suggest a detour in the direct vicinity of the location of the traffic event, which detour would be fraught with problems too.
- An embodiment of the navigation system according to the invention is defined in Claim 2. Defining an explicit region and declaring the road segments in it affected by the reported traffic event, is a simple and effective mechanism for representing the larger influence the traffic event has on its vicinity.
- An embodiment of the navigation system according to the invention is defined in Claim 4.
- the impact of the traffic event is better reflected.
- Examples of two event classes are a structural traffic event versus an occasional traffic event, whereby the size of the region for a structural event is made larger than the size of the region for an occasional event.
- the structural event class includes events like a traffic queue during rush hour and road works and the occasional event class includes an accident and bad weather conditions.
- a structural event is known to many drivers including those not receiving actual traffic information, causing the usage of escape routes nearby, and/or occurs at times that heavy traffic is expected anyhow. A structural traffic event will therefore influence a larger area than an occasional traffic event.
- An embodiment of the navigation system according to the invention is defined in Claim 5.
- it can be indicated to what extent individual road segments are expected to be influenced by the traffic event. This depends for example on the density of the road network and the topology of the road segment.
- An embodiment of the navigation system according to the invention is defined in Claim 6.
- the distance between the location where the traffic event occurs and the road segment provides an easy and effective estimation for the extent to which such road segments is influenced.
- a road segment nearby the location of the traffic event is very likely to be more affected than a road segment farther away.
- An embodiment of the navigation system according to the invention is defined in Claim 7. Suppressing the processing of road segments which are likely to be affected by the traffic event and which represent road that are less important than the road where the traffic event takes place, is an effective way of dealing with the consequences of the traffic event. It avoids the suggestion of a detour on a minor road in an easy way, by simply excluding the road segment representing such minor road. The remaining road segments are at least as important as the road segment for which the traffic message has been received and if on any one of these roads a traffic event would occur, the broadcasting service will include a traffic message for that event.
- An embodiment of the navigation system according to the invention is defined in Claim 8. It is very advantageous to apply the invention in a navigation system including a planning unit, because in that way the influence of the traffic event on the road segments is better taken into account.
- the planning unit plans a route between an origin and a destination, such route being composed of a number of the road segments in the database and being optimal with respect to a certain criterion, e.g. travel time. For each road segment in the database it is known how much it contributes to the criterion.
- the planning unit compares a number of alternative routes, i.e. consisting of alternative sets of road segments, between the origin and the destination and chooses that one which satisfies the criterion in the best way.
- the traffic event makes that the information for the road segments in the database does no longer conform to the actual situation and the planning unit of the navigation system uses the traffic message to correct this.
- the planning unit plans a route that better takes into account the influence of the traffic event avoiding problems in the direct vicinity of the traffic event.
- An embodiment of the navigation system according to the invention is defined in Claim 9.
- the driver may be warned for the existence of an area of influence around the traffic event. This warning is an advice to avoid this area and to not make a detour through this area.
- This object is achieved according to the invention in a method that is characterised in that the method further comprises a step defining at least one second road segment as additionally affected by the traffic event and that the traffic message is processed in relation to the second road segment.
- the influence of the traffic message is better taken into account.
- the improved representation of the influence of the traffic event allows for a better choice of a route.
- FIG. 1 schematically shows some of the components of a navigation system according to the invention.
- the navigation system 100 has a database with road segments representing the roads of an area of interest to the user of the system.
- the road segments together are sometimes called an electronic map since they represent the roads in a digitised form.
- a road segment represents a part of a road and is an elementary item in the database.
- a road segment has various attributes, holding information on the represented part of the road, e.g. name, location, direction, size, etc.
- the navigation system 100 also has a processing unit 104 that uses the information in the database with road segments to produce an output 106 that is of use to the user of the system. The nature of the processing and output is not essential to the understanding of the invention and is not further described here.
- the navigation system 100 further has a receiver 108 for the reception of traffic messages.
- a traffic message includes an event, indicating the happening to which the traffic message relates, and a location where the event occurs.
- An example of a traffic message is a message indicating a traffic queue of a particular length starting from a particular location on a particular road.
- the traffic message is broadcast via RDS as described in United States Patent 5,095,532 and its format and contents is conform the standardised Traffic Message Channel (TMC). There the event and location are transferred as codes in the traffic message and the meaning of the codes are agreed upon in the standard.
- TMC Traffic Message Channel
- the invention is not restricted to RDS TMC and other ways of transmitting the traffic message may be employed, e.g.
- a traffic message may include actual information concerning the roads in the area of interest.
- a traffic message may also include forecast information, e.g. a weather forecast or expected heavy traffic due to a large happening at a certain place.
- the processing unit 104 processed the dynamic information of the received traffic message to supplement the static information residing in the database. One or more values of the attributes in the database may no longer be valid in view of the actual information, and the processing unit will then use an updated value instead which is derived from the traffic message.
- the processing unit 104 determines to which of the road segment, or exceptionally road segments, the received traffic message relates.
- a traffic message according to RDS TMC includes a location code, which is an identification of a particular one of a large number of standardised problem locations.
- the processing unit consults a cross reference table residing in the database 102 indicating which road segment corresponds to a given location code. In this way it is determined to which road segment a received traffic message relates. This road segment is directly affected by the event of the traffic message. An alternative way of determining this road segment is by establishing which road segment is geographically seen the closest to the location reported in the traffic message.
- the processing unit 104 determines which road segment is directly affected by the traffic event as reported in the traffic message.
- the navigation system 100 further includes a defining unit 110 that defines one or more road segments of the database as being affected by the traffic message, in addition to the directly affected road segment. The processing unit subsequently treats these road segments as being affected so that the influence of the traffic event in the navigation system is larger than the directly affected road segment.
- Figure 2 shows a region in which the road segments are defined to be affected by the traffic event.
- a received traffic message contains a reported traffic event at location 202.
- the road segment 204 on which location 202 resides is directly affected by the traffic event.
- the defining unit 110 defines a circular region 206 with location 202 as its centre and defines the road segments inside this region as being additionally affected.
- road segments 208, 210 and 212 are defined to be affected by the traffic event. So in this embodiment, the influence of the reported traffic event is not only on the single road segment on which the reported location resides but also on the road segments in a circular region around this location.
- Figure 3 shows an alternative region in which the road segments are defined to be affected by the traffic event.
- the traffic event is a traffic queue 302 with a begin or head location 304 and an end or tail location 306.
- the defining unit defines a region 308 with a boundary that is at a constant, predetermined distance from the road segments on which the traffic resides.
- the road segments inside this region are defined to be affected by the traffic queue, e.g. road segments 310, 312 and 314.
- the location 304 reported in the traffic message corresponds to road segment 316 and the traffic queue resides on that road segments and on road segments 318 and 320.
- the defining unit determines the type of the traffic event and classifies it accordingly.
- the defining unit determines whether the traffic event is structural or occasional, based on the time the traffic event occurs and on historic data.
- an event occurring regularly at the same location, e.g. on the previous two consecutive working days, is considered a structural event.
- a traffic event occurring at another time and not occurring regularly is considered an occasion traffic event.
- the defining unit defines the region of affected road segments to extent for 5 kilometres from the traffic event itself. So then the radius of the circle of Figure 2 and the distance as described in Figure 3 is 5 kilometres. In case of an occasional traffic event, the extent of the region is defined to be 0.5 kilometres instead of 5 kilometres.
- a received traffic event is considered as structural if it occurs during rush hours and otherwise it is considered an occasional event. This avoids the need to maintain historic data of traffic events in the system.
- FIG. 4 schematically shows an embodiment of the navigation system including a planning unit.
- This embodiment is used in a vehicle for guiding the driver along a planned route.
- the navigation system 400 has a reader 402 for reading the data carrier 404 holding the database with the road segments.
- the data carrier 404 is a CD-ROM but another kind of storage would also be suitable, e.g. magnetic hard disk, floppy disk, SMART card and tape.
- the navigation system further has a receiver 108, for the reception of the traffic messages concerning road segments in the database, and a defining unit 110, for defining additional road segments being affected by the traffic event in the received traffic message.
- the navigation system has a planning unit 406 for planning a route between an origin and a destination.
- the origin may be the present position of the vehicle, e.g. obtained by a localising device, and the destination may be entered by the user of the navigation through a suitable input device.
- the localising device and the input device are not shown in the figure.
- the planning unit determines on the basis of the road segments in the database a route that is optimal for a given criterion. This criterion can be minimal travel distance or minimal travel time and can be chosen by the user for the route to be planned.
- a road segment has an attribute indicating the length of the represented part of the road and an attribute indicating the expected driving speed on that road.
- the planning unit will use the traffic message to update the attributes before using them. For instance in case of a traffic queue, the planning unit will determine the expected delay and the consequence thereof for the driving speed on that road. The planning unit will use the updated attributes to determine an optimal route. Also the relevant attributes of the additionally affected road segments, as defined by the defining unit 110, will be updated prior to being used by the planning unit 406.
- the planned route is stored in memory space 408 and a guidance unit 410 provides guidance information to the driver for following the planned route. The guidance information is presented on a display 412 and via a speaker 414.
- the level of affection by the traffic event is not the same for all road segments and may be adapted to the circumstances, e.g. in dependence on the density of the road network at the place of the road segment.
- the level of affection of a road segment is made dependent on the distance between the road segment and the location of the traffic event.
- First the influence of the traffic event is determined on the basis of the received traffic message. For instance a traffic queue of a given length is translated to an expected average speed on the corresponding road segment. This speed will be a certain factor slower than the undisturbed speed as stored in the database.
- V dis ((d + (D - d) . F) / D) .
- V norm in which:
- the invention can be applied with other functions for the calculation of the level of affection than the one given in equation (2), e.g. functions with a non-linear relation between the normal speed and the disturbed speed.
- the influence of the traffic event is taken into account by suppressing some of the road segments in the region of influence.
- Each road segment in this embodiment has a so-called road class attribute indicating the importance of the road represented by that road segment.
- the road class attribute has one of the following values:
- the road class of the road segment of the location of the traffic event is determined.
- the road class value of this road segment is used as a reference value in suppressing road segments later on.
- the defining unit 110 defines a region with additionally affected road segments.
- the route planner when planning a route, suppresses those additionally affected road segments that have a road class value higher than the reference value. So the roads that are less important than the road on which the traffic event takes place are not regarded as candidates for planning a route.
- the planning unit plans a route between the present position and the destination to verify whether the present route is still optimal.
- the planning unit considers in the defined region of influence only main roads and motor ways and will not plan a route there on lesser important roads. Outside the region, no roads are discarded on the basis of the reported traffic event. It is to be understood that a set of values different from the one above may be used for classification of the roads with respect to their importance.
- FIG. 5 schematically shows an embodiment of the navigation system including a display unit.
- the navigation system 500 has a reader 402 for reading the data carrier 404 holding the database with the road segments.
- the database may reside on a removable carrier, like the exemplary CD-ROM, or may reside on a fixed storage device in the navigation system.
- the navigation system further has a receiver 108, for the reception of the traffic messages concerning road segments in the database, and a defining unit 110, for defining additionally road segments being affected by the traffic event in the received traffic message.
- the navigation system has a display unit 502 for displaying the traffic message on a display 412.
- the display unit 502 displays the traffic event on the road segment corresponding to the reported location, in relation to the additionally affected road segments.
- a simple realisation of this is the presentation of a textual message including the event and the directly affected road segment together with an indication of the influenced area with the additionally affected road segments.
- An advanced realisation is the presentation of a map of the road segments on which the traffic event is superimposed on the road segment corresponding to the reported location and on which the additionally affected area are displayed in a style that is different from the other road segments. This style could be a different colour than the other road segments, a dimmed presentation compared to the other road segments, or a hatching of the region including the additionally affected road segment.
- This embodiment of the navigation system may be implemented as a system in the vehicle displaying the information to the driver or it may be implemented as a system external to a vehicle with a display positioned at the side of a road displaying the information to the drivers of all vehicles passing by.
- Figure 6 shows an example of a displayed map with a region of influence.
- the map shows a traffic event 202 and a directly affected road segment 204.
- the region of influence 206 is shown in a hatched way, indicating that the road segments inside the region are also affected by the traffic event.
- the display unit may display, if this information is available, the actual position of the vehicle and the route driven. In the same way, the system may display the planned route to the destination.
- the display unit may display the additionally affected road segments in correspondence with the level of affection as described above. This can be realised by displaying the affected road segments in a certain colour and with a respective brightness that is dependent on the level of affection.
- the navigation system with a display unit can optionally use the suppressing of additionally road segments as described above.
- the display unit then displays the region of influence with only those additionally affected road segments that have value for the road class attribute equal to or smaller than the reference value. So road segments in the region of influence with a value of the road class attribute indicating a less important road are not displayed.
- Step 702 is an initialisation step including for instance the display of a map with road segments, if the method is applied for display purposes, or the planning of a route, if the method is applied in a system with route planning.
- step 704 is verified whether a traffic message can be received, such traffic message including a traffic event and a location where the traffic event takes place. If there is presently no traffic message, a number of steps not further detailed in here may be executed after which step 704 is again executed. If a traffic message has been received then in step 706 the road segment corresponding to the location in the traffic message is determined. this road segment is directly affected by the traffic event in the traffic message.
- step 708 a number of road segments is defined as being affected by the traffic event in addition to the directly affected road segment.
- step 710 the traffic message is processed in relation to the direct related traffic event and the additionally affected road segments.
- step 704 for verifying whether a next traffic message is to be received and the steps are the repeated for this next traffic message.
- the method may be applied for displaying a map with road segments for which a traffic message may be received.
- step 710 displays the affected road segments, both the directly affected and the additionally affected, in a distinct way from the other road segments, so as to show the region of influence of the traffic event.
- the method may also be applied for planning a route between an origin and a destination over road segments for which a traffic message may be received.
- step 710 plans such a route while taking into account the traffic event for the affected road segments. This can be done by updating the planning related attributes of the relevant road segments.
Landscapes
- Physics & Mathematics (AREA)
- Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Radar, Positioning & Navigation (AREA)
- Remote Sensing (AREA)
- Multimedia (AREA)
- Mathematical Physics (AREA)
- Navigation (AREA)
- Traffic Control Systems (AREA)
Claims (10)
- Système de navigation destiné à fournir des informations de navigation à un conducteur, le système comprenant :une base de données avec des segments de route, un segment de route représentant une portion de route ;un récepteur destiné à la réception d'un message de circulation indiquant un événement de circulation et un emplacement auquel l'événement de circulation se rapporte, l'emplacement correspondant à au moins un segment particulier des segments de route qui est affecté par l'événement de circulation,un moyen de traitement relié à un récepteur afin de traiter le message de circulation en relation avec le au moins un segment de route affecté,le système comprend un moyen de définition destiné à définir au moins un autre des segments de route comme affecté en sus par l'événement de circulation, etle moyen de traitement est agencé de façon à traiter le message de circulation en relation avec les segments de route affectés en sus.
- Système de navigation selon la revendication 1, dans lequel le moyen de définition est agencé de façon à définir une région autour de l'emplacement auquel l'événement de circulation se rapporte et à définir les segments de route à l'intérieur de la région comme affectés en sus par l'événement de circulation.
- Système de navigation selon la revendication 2, dans lequel la région a une limite qui est à une distance fixe du segment de route précis correspondant à l'emplacement auquel le message de circulation se rapporte.
- Système de navigation selon la revendication 2, dans lequel le moyen de définition est agencé afin de déterminer un type d'événement de l'événement de circulation du message de circulation reçu et de donner à la région une taille qui est basée sur le type d'événement.
- Système de navigation selon la revendication 1 dans lequel le moyen de définition est agencé afin d'assigner un niveau respectif d'affectation à des segments de route affectés en sus et dans lequel le moyen de traitement est agencé de façon à employer le niveau d'affectation des segments de route affectés en sus.
- Système de navigation selon la revendication 5, dans lequel le niveau d'affectation d'au moins d'un des segments de route affectés en sus est assigné sur la base de la distance entre le segment de route et l'emplacement auquel le message de circulation se rapporte.
- Système de navigation selon la revendication 2, dans lequel les segments de route de la base de données ont des attributs de type de route respectifs indiquant l'importance des parties respectives de la route représentée par les segments de route respectifs et dans lequel le moyen de traitement est agencé pour supprimer, sur la base de leurs attributs de type de route, le traitement des segments de route affectés en sus dans la région qui est moins importante que les segments de route particuliers correspondant à l'emplacement du message de circulation.
- Système de navigation selon la revendication 1, dans lequel le moyen de traitement comprend une unité de planification destinée à planifier un itinéraire entre une origine et une destination sur la base des segments de route dans la base de données en prenant en compte un segment de route particulier affecté par l'événement de circulation et les segments de route affectés en sus.
- Système de navigation selon la revendication 1, dans lequel le moyen de traitement comprend une unité d'affichage destinée à afficher l'événement de circulation en relation avec un segment de route particulier et les segments de route affectés en sus.
- Procédé destiné à présenter des informations de navigation à un conducteur, le procédé comprenant les étapes consistant à :recevoir un message de circulation indiquant un événement de circulation et un emplacement auquel l'événement de circulation se rapporte, l'emplacement correspondant à un premier segment de circulation qui est affecté par l'événement de circulation,traiter le message de circulation relatif au segment de route affecté,le procédé comprend en outre une étape de définition d'au moins un second segment de route comme étant affecté en sus par l'événement de circulation, etle message de circulation est traité en relation avec le second segment de route.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP99915596A EP1064638B1 (fr) | 1998-03-19 | 1999-03-13 | Systeme de navigation traitant des evenements de la circulation |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP98200881 | 1998-03-19 | ||
EP98200881 | 1998-03-19 | ||
PCT/EP1999/001654 WO1999048073A1 (fr) | 1998-03-19 | 1999-03-13 | Systeme de navigation traitant des evenements de la circulation |
EP99915596A EP1064638B1 (fr) | 1998-03-19 | 1999-03-13 | Systeme de navigation traitant des evenements de la circulation |
Publications (2)
Publication Number | Publication Date |
---|---|
EP1064638A1 EP1064638A1 (fr) | 2001-01-03 |
EP1064638B1 true EP1064638B1 (fr) | 2002-06-12 |
Family
ID=8233487
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP99915596A Expired - Lifetime EP1064638B1 (fr) | 1998-03-19 | 1999-03-13 | Systeme de navigation traitant des evenements de la circulation |
Country Status (6)
Country | Link |
---|---|
EP (1) | EP1064638B1 (fr) |
JP (1) | JP2002507808A (fr) |
AT (1) | ATE219270T1 (fr) |
BR (1) | BR9908922A (fr) |
DE (1) | DE69901809T2 (fr) |
WO (1) | WO1999048073A1 (fr) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP2986944A1 (fr) * | 2013-04-17 | 2016-02-24 | TomTom Navigation B.V. | Moteur d'acheminement |
Families Citing this family (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE10002918C2 (de) * | 2000-01-19 | 2003-06-18 | Ddg Ges Fuer Verkehrsdaten Mbh | Stabile Zuordnung von Verkehrsmeldungen und deren Ursache repräsentierenden Zusatzinformationen |
DE10015935A1 (de) * | 2000-03-30 | 2001-10-04 | Bosch Gmbh Robert | Verfahren zur Übertragung einer Position einer Verkehrsinformation, insbesondere einer Verkehrsstörung |
KR20040064634A (ko) | 2003-01-10 | 2004-07-19 | 가부시끼가이샤 히다치 세이사꾸쇼 | 네비게이션 서버, 네비게이션의 표시방법 |
EP1550097B1 (fr) * | 2003-07-17 | 2007-09-12 | Harman Becker Automotive Systems GmbH | Calcul d'itineraire contournant des obstacles du trafic au moyen de deviations signalees |
DE102005050575A1 (de) * | 2005-10-21 | 2007-04-26 | Robert Bosch Gmbh | Verfahren zur Codierung von Verkehrsstörungen und Berechnung einer Route |
JP4778411B2 (ja) * | 2006-12-18 | 2011-09-21 | クラリオン株式会社 | 交通情報配信方法および交通情報配信装置 |
DE102008010721A1 (de) * | 2008-02-22 | 2009-08-27 | Volkswagen Ag | Verfahren zum Steuern einer Anzeigevorrichtung in einem Fahrzeug zum Visualisieren von Verkehrsinformationen |
JP5535711B2 (ja) * | 2010-03-24 | 2014-07-02 | アルパイン株式会社 | 車載用ナビゲーション装置及び交通情報表示方法 |
US9437107B2 (en) | 2013-03-15 | 2016-09-06 | Inrix, Inc. | Event-based traffic routing |
DE102015216817A1 (de) * | 2015-09-02 | 2017-03-02 | Volkswagen Aktiengesellschaft | Verfahren und System zur Unterstützung eines Nutzers bei der Planung und Durchführung eines Befahrens einer Fahrstrecke mit einem Fahrzeug |
US11474518B2 (en) * | 2019-05-13 | 2022-10-18 | International Business Machines Corporation | Event validation using multiple sources |
US11669071B2 (en) | 2020-01-08 | 2023-06-06 | International Business Machines Corporation | Organizing a temporary device group for collaborative computing |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
ATE158886T1 (de) * | 1987-05-09 | 1997-10-15 | Koninkl Philips Electronics Nv | Einrichtung für empfang und verarbeitung von strassennachrichtenmeldungen |
US5095532A (en) * | 1989-12-29 | 1992-03-10 | Robert Bosch Gmbh | Method and apparatus for route-selective reproduction of broadcast traffic announcements |
US5164904A (en) * | 1990-07-26 | 1992-11-17 | Farradyne Systems, Inc. | In-vehicle traffic congestion information system |
DE4208277A1 (de) * | 1992-03-13 | 1993-09-16 | Bosch Gmbh Robert | Verkehrsrundfunkempfaenger |
-
1999
- 1999-03-13 WO PCT/EP1999/001654 patent/WO1999048073A1/fr active IP Right Grant
- 1999-03-13 AT AT99915596T patent/ATE219270T1/de not_active IP Right Cessation
- 1999-03-13 DE DE69901809T patent/DE69901809T2/de not_active Expired - Lifetime
- 1999-03-13 EP EP99915596A patent/EP1064638B1/fr not_active Expired - Lifetime
- 1999-03-13 JP JP2000537192A patent/JP2002507808A/ja active Pending
- 1999-03-13 BR BR9908922-0A patent/BR9908922A/pt not_active IP Right Cessation
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP2986944A1 (fr) * | 2013-04-17 | 2016-02-24 | TomTom Navigation B.V. | Moteur d'acheminement |
Also Published As
Publication number | Publication date |
---|---|
DE69901809D1 (de) | 2002-07-18 |
BR9908922A (pt) | 2000-11-21 |
JP2002507808A (ja) | 2002-03-12 |
DE69901809T2 (de) | 2002-11-28 |
EP1064638A1 (fr) | 2001-01-03 |
WO1999048073A1 (fr) | 1999-09-23 |
ATE219270T1 (de) | 2002-06-15 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP1064638B1 (fr) | Systeme de navigation traitant des evenements de la circulation | |
EP2102596B1 (fr) | Procédé permettant d'indiquer les retards de trafic, programme informatique et système de navigation afférent | |
US6868331B2 (en) | Method for outputting traffic information in a motor vehicle | |
US6591188B1 (en) | Method, system and article of manufacture for identifying regularly traveled routes | |
EP1657692B1 (fr) | Dispositifs, méthodes et programmes pour collecter des informations de circulation routière | |
US7739041B2 (en) | Safety navigation system applying wireless communication technology and method therefor | |
EP1111340B1 (fr) | Méthode et dispositif pour sélection de route | |
US6453230B1 (en) | Apparatus for handling a traffic message | |
US20020019835A1 (en) | Metod of planning appointments and electronic organiser therefor | |
US6587780B2 (en) | System and method for disseminating traffic information | |
US20080167804A1 (en) | Traffic delay indication | |
JP2000500878A (ja) | 車両内交通関連情報供給装置及び方法 | |
US20040236504A1 (en) | Vehicle navigation point of interest | |
EP1936519A1 (fr) | Système de création de données de recherche de zones environnantes, système de recherche de zones environnantes, procédé de création de données de recherche de zones environnantes, procédé de recherche de zones environnantes et dispositif de navigation | |
WO2009070572A1 (fr) | Système et procédé de fourniture de données de trafic à un dispositif mobile | |
JP2001506390A (ja) | 車両用ナビゲーションシステム | |
JP2000505908A (ja) | 運転者を案内する方法及びこのような方法用のナビゲーション装置 | |
WO1998043192A1 (fr) | Occultation des ecrans de bord d'un vehicule a l'aide de donnees de vitesse fournies par le systeme gps | |
EP0935795B1 (fr) | Systeme de navigation pour vehicule | |
Ness et al. | A prototype low cost in-vehicle navigation system | |
US20060267793A1 (en) | Method and device for danger warning displays with voice output according to different degrees of urgency, especially in a motor vehicle | |
US20240339032A1 (en) | Method and device for controlling in-vehicle signage | |
US20040236505A1 (en) | Method and device for ouput of data on an attribute on a digital street map | |
US20240068834A1 (en) | Determination of Trip Information | |
US20240177598A1 (en) | Method for Updating Traffic Information Relating to a Vehicle, Computer-Readable Medium, System, and Vehicle |
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 |
|
17P | Request for examination filed |
Effective date: 20000803 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AT BE CH DE ES FR GB IT LI LU SE |
|
GRAG | Despatch of communication of intention to grant |
Free format text: ORIGINAL CODE: EPIDOS AGRA |
|
17Q | First examination report despatched |
Effective date: 20011004 |
|
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 |
|
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: SIEMENS AKTIENGESELLSCHAFT |
|
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): AT BE CH DE ES FR GB IT LI LU SE |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LI 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: 20020612 Ref country code: CH 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: 20020612 Ref country code: BE 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: 20020612 Ref country code: AT 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: 20020612 |
|
REF | Corresponds to: |
Ref document number: 219270 Country of ref document: AT Date of ref document: 20020615 Kind code of ref document: T |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: EP |
|
REF | Corresponds to: |
Ref document number: 69901809 Country of ref document: DE Date of ref document: 20020718 |
|
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: 20020912 |
|
ET | Fr: translation filed | ||
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 FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20021220 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
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: 20030313 |
|
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: 20030313 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20090325 Year of fee payment: 11 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: IT Payment date: 20090324 Year of fee payment: 11 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: FR Payment date: 20090312 Year of fee payment: 11 |
|
GBPC | Gb: european patent ceased through non-payment of renewal fee |
Effective date: 20100313 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: ST Effective date: 20101130 |
|
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: 20100331 |
|
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: 20100313 Ref country code: IT Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20100313 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20140331 Year of fee payment: 16 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R119 Ref document number: 69901809 Country of ref document: DE |
|
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: 20151001 |