EP1371047B1 - Mise a jour de donnees d'itineraires et de circulation, et appareil de navigation pour vehicule - Google Patents

Mise a jour de donnees d'itineraires et de circulation, et appareil de navigation pour vehicule Download PDF

Info

Publication number
EP1371047B1
EP1371047B1 EP02703494A EP02703494A EP1371047B1 EP 1371047 B1 EP1371047 B1 EP 1371047B1 EP 02703494 A EP02703494 A EP 02703494A EP 02703494 A EP02703494 A EP 02703494A EP 1371047 B1 EP1371047 B1 EP 1371047B1
Authority
EP
European Patent Office
Prior art keywords
data
traffic flow
route
vehicle navigation
flow data
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
EP02703494A
Other languages
German (de)
English (en)
Other versions
EP1371047A1 (fr
Inventor
Arne Friedrichs
Gerd Draeger
Michael Laedke
Volker Skwarek
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 EP1371047A1 publication Critical patent/EP1371047A1/fr
Application granted granted Critical
Publication of EP1371047B1 publication Critical patent/EP1371047B1/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/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/096811—Systems involving transmission of navigation instructions to the vehicle where the transmitted instructions are used to compute a route where the route is computed offboard
    • 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/096811—Systems involving transmission of navigation instructions to the vehicle where the transmitted instructions are used to compute a route where the route is computed offboard
    • G08G1/096816—Systems involving transmission of navigation instructions to the vehicle where the transmitted instructions are used to compute a route where the route is computed offboard where the complete route is transmitted to the vehicle at once
    • 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 present invention relates to a method for updating route data stored in a vehicle navigation device, in particular an off-board vehicle navigation device, wherein the route data is updated when at least one predetermined event occurs. Furthermore, the present invention relates to a vehicle navigation device, in particular an off-board vehicle navigation device, which is provided to receive and store route data from a control center. Furthermore, the present invention relates to a method for updating stored traffic flow data suitable for calculating route data.
  • Vehicle navigation devices are known.
  • One type of vehicle navigation device provides a complete database on which route data is calculated.
  • routes data is calculated.
  • the basic idea is to use messages from external databases, such as Traffic Message Channel (TMC) messages, and compare their positions with the planned route. If an event, for example a traffic jam, is reported for the planned route, then the vehicle navigation device determines an alternative route on the basis of the carried-on database.
  • TMC Traffic Message Channel
  • a manual input is provided via a so-called "traffic jam ahead button" provided on the vehicle navigation device.
  • the car navigation device calculates an alternative route based on the database it carries.
  • so-called off-board vehicle navigation devices are known, which do not carry a complete database on the basis of which route data could be calculated.
  • these off-board vehicle navigation devices it is provided that, for route planning, at least the start address and the destination address are transmitted to a central station, which then sends back corresponding route data to the offboard vehicle navigation device.
  • the problem may arise that the vehicle navigation device does not have complete traffic flow data available for calculating alternative routes.
  • the JP 06-119596 A describes a center which transmits traffic data and routes to an emergency vehicle to the nearest hospital.
  • the at least one predetermined traffic-flow-induced event comprises the occurrence of traffic flow disturbances on the originally planned route.
  • traffic flow disturbances can include, for example, congestion or weather-related traffic flow disturbances.
  • the manual feed of the traffic flow data can be done for example by the operation of an input already mentioned "traffic jam button ahead".
  • the driver in addition to the operation of the "traffic jam button” estimates the length of the jam and also supplies this information to the vehicle navigation device.
  • the input takes place via a voice input instead of a keyboard input.
  • the traffic flow data is communicated to the vehicle navigation device by vehicle sensors and / or by one or more external sources of traffic flow data.
  • vehicle sensors By suitable vehicle sensors, it is possible to analyze the current traffic condition in the vehicle, similar to what is provided for example in the so-called floating car data (FCD) algorithms.
  • FCD floating car data
  • external sources of traffic flow data for example, radio stations come into consideration, which emit the already mentioned TMC messages.
  • the inventive method for updating route data preferably further provides that the vehicle navigation device evaluates the traffic flow data supplied to it in order to determine whether there are traffic flow disturbances which require updating the route data. For example, the vehicle navigation device can first check whether there is a significant or rather minor traffic influence with regard to the planned route. If, based on the planned route, there is only a slight influence on traffic, which can be determined, for example, by means of the corresponding TMC message or the corresponding TMC event code, preferably no route request data are transmitted to the central station. In contrast, it is preferably provided that a significant traffic disruption always leads to a transmission of route request data to a central office.
  • the route request data comprises at least parts of the traffic flow data supplied to the vehicle navigation device and / or information obtained from the traffic flow data supplied to the vehicle navigation device.
  • the vehicle navigation device already transmits corresponding traffic flow data to a control center, for example traffic flow data with the content "lively to halting traffic on route section XY" already in the detection of low traffic incidents which do not necessarily require an updating of the route data.
  • the center after receiving route request data and before the calculation of the updated route data, subjects at least certain traffic flow data contained in the route request data to a check, in particular a plausibility check.
  • This check can be done, for example, by comparing the traffic flow data contained in the route request data with other traffic flow data available in the center. This may be advantageous, for example, in cases in which the center more current traffic flow data are available when they were supplied to the car navigation device.
  • the calculation of the updated route data is preferably carried out with the aid of traffic flow data available in the center.
  • available traffic flow data is understood to mean that the corresponding traffic flow data does not necessarily have to be located in the central physically available data carriers, but that the traffic flow data can also or exclusively be provided via WAN or LAN connections. In any case, it is possible to provide much more comprehensive traffic flow data in the control center than is possible for a vehicle navigation device arranged in the vehicle.
  • These traffic flow data may be composed of a plurality of route request data transmitted from a plurality of vehicle navigation devices, such traffic flow data preferably being subjected to a plausibility check prior to use. As a result, it can be avoided, for example, that an erroneously actuated "jam ahead button" results in incorrectly updated route data being transmitted to other vehicle navigation devices.
  • the calculation of the updated route data using is done by available at the headquarters digital road maps.
  • the method according to the invention for updating route data that traffic flow data available in the center is updated on the basis of traffic flow data contained in route request data.
  • the traffic flow data contained in the route request data is preferably subjected to a plausibility check before use.
  • the transmission of the route data and / or the transmission of the updated route data preferably takes place via a mobile radio network.
  • a mobile radio network can operate, for example, according to the GSM or the UMTS standard.
  • each central office which is suitable for participation in the method according to the invention for updating route data.
  • the at least one predetermined traffic-flow-induced event comprises the occurrence of traffic flow disturbances on the originally planned route, as has already been explained in connection with the method according to the invention for updating route data.
  • the vehicle navigation device preferably has input devices to which traffic flow data are fed manually and / or automatically.
  • the manual input of traffic flow data can be done, for example, via the operation of a "traffic jam button", where appropriate, additional information may be entered, for example, an estimated traffic jam length.
  • the traffic flow data are supplied to the input devices by vehicle sensors and / or by one or more external sources of traffic flow data.
  • FCD floating-car-data
  • the already mentioned floating-car-data (FCD) algorithms come into consideration again.
  • FCD floating-car-data
  • the current prevailing traffic conditions can be used, for example based on data on the vehicle acceleration or deceleration, the current vehicle speed and / or the average speed.
  • external sources of traffic flow data for example, radio stations are again considered, which emit TMC messages.
  • the vehicle navigation device preferably has evaluation devices which evaluate the supplied traffic flow data in order to determine whether there are traffic flow disturbances which require an updating of the route data. Similar to the method according to the invention for updating route data, it may also be provided in this context that no route request data is transmitted to a control center if there is only a slight traffic influence, while preferably always route request data be transmitted to a central office if there is a significant traffic incident.
  • the route request data transmitted by the vehicle navigation device according to the invention to at least one center preferably comprises at least parts of the traffic flow data supplied via the input devices and / or information obtained therefrom.
  • these traffic flow data transmitted to a center may continue to update traffic flow databases accessed by one or more centers using such traffic flow data included in the route request data.
  • the vehicle navigation device also has means which transmit traffic flow data to at least one center.
  • These means may be formed by the same means which, when at least one predetermined traffic flow-induced event occurs, transmit route request data to at least one central station.
  • traffic flow data may be advantageous to also transmit traffic flow data to the central office which does not require updating of the route data, for example traffic flow data with the content "Lively to halting traffic on route section XY".
  • the vehicle navigation device preferably has communication devices and / or it cooperates with separate communication devices to transmit the route request data and / or to receive the updated route data.
  • mobile radio devices which can work, for example, according to the GSM or the UMTS standard.
  • the traffic flow data transmitted by the vehicle navigation devices are components of route request data, as already explained in connection with the method according to the invention for updating route data and the vehicle navigation device according to the invention.
  • FIG. 1b shown portion of the flowchart closes over the connection point I to the in Figure. 1a represented portion of the flowchart, while the in Figure 1c represented section of the flowchart via the junction II to the in FIG. 1b followed section of the flowchart.
  • the in the FIGS. 1a to 1c Blocks 1 to 17 are assigned the functions that result from the following table: BLOCK FUNCTION 1 Start of the route guidance 2 Has a predetermined traffic flow-induced event occurred in the form of a traffic flow disruption? 3 Has the traffic flow disruption been detected by traffic flow data generated in the vehicle? 4 Is the traffic flow disruption significant for the originally planned route?
  • the route guidance begins.
  • block 2 it is checked whether a predetermined traffic-flow-induced event has occurred in the form of a traffic flow disturbance. If this is not the case, then the system returns to block 1. If a predetermined traffic flow-induced event has occurred in the form of a traffic flow disturbance, the system branches to block 3, in which it is checked whether the traffic flow disturbance was detected on the basis of traffic flow data generated in the vehicle. If this is the case, the route request data are supplemented by the traffic flow data generated in the vehicle. Otherwise, the system branches to block 4, in which it is checked whether the traffic flow disturbance is significant for the originally planned route.
  • the route branches to block 8, in which the route guidance is continued on the basis of the original route data.
  • the route request data are supplemented by blocked route sections.
  • the Rutenanfrage stylist be transmitted to at least one center, wherein the. Route request data also contain the original route data.
  • FIG. 1b located at Junction I to the FIG. 1a connects, the running in a central section of the inventive method is shown.
  • an update of traffic flow data stored in a traffic flow database 10 is carried out first.
  • block 11 it is checked whether the route data in the vehicle comprises generated traffic flow data. If this is the case, then branched to block 12, in which the im
  • Vehicle generated traffic flow data to be subjected to a plausibility check. Subsequently, or if it is determined in block 11 that the route request data does not contain any traffic flow data generated in the vehicle, the system branches to block 13, in which an alternative route is calculated. The calculation of the alternative route takes place on the basis of plausible traffic flow data generated in the vehicle, traffic flow data from the traffic flow database 10 and the digital road maps 14. Subsequently, a branch is made to block 15, in which the updated route data is transmitted to the vehicle navigation device.
  • Figure 1c illustrates the state in the vehicle after receiving the updated route data.
  • Block 16 provides the vehicle navigation device with the updated route data which specifies a route optimized with respect to the current traffic situation.
  • the route guidance starts based on the updated route data.
  • a vehicle is equipped with an off-board vehicle navigation device and calculates a route for the route between Hamburg and Kunststoff, where the current traffic jam messages are implemented by the head office. Near Kassel this vehicle arrives An accidental traffic jam that was not known at the time of the route calculation. Due to this, the driver operates the "traffic jam ahead button" on the car navigation device. Since the jam end is not within sight, the driver estimates the jam length at "greater than 2km". The vehicle navigation device then sends a message in the form of route request data to the center. In addition to the route request for the route between the current point of view and a destination point, this route request data also includes the traffic jam message, the current road and the estimated road section that has to be taken into account in the next route calculation due to the traffic jam message.
  • the central office is connected to a traffic data provider, to whom it sends a message that a vehicle has reported a traffic jam on the said section of the route.
  • the center now calculates an alternative route on which the vehicle can avoid the congestion, and transmits the alternative route in the form of updated route data to the vehicle.
  • the traffic jam near Kassel is reported on the radio and is available for navigation through a corresponding TMC message.
  • the car navigation device checks the traffic flow data received by the TMC message and concludes that it is a traffic incident significant to the originally planned route. Then a request, in the form of route request data, transmitted to the central office after an alternative route.
  • the route request data also includes the received TMC message.
  • the fact that the TMC message is an authenticated message compares the current database in the central office with the current message.
  • the center now calculates an alternative route for the vehicle and transmits it in the form of updated route data.
  • the vehicle has an FCD-capable system component in which intelligent algorithms analyze the driving profile. Based on the driving profile, the FCD algorithm determines that the vehicle is in halting traffic and requests a new route from the central station by transmitting route request data.
  • the route request data comprise in the form of corresponding traffic flow data additional information about the detected traffic state, so that a better alternative can be calculated in the center.
  • the traffic flow data transmitted by the vehicle or by the vehicle navigation device are checked for plausibility in the center and optionally stored in a traffic flow database in order to be able to take these messages into account when requesting routes from other road users.

Landscapes

  • Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Radar, Positioning & Navigation (AREA)
  • Remote Sensing (AREA)
  • General Physics & Mathematics (AREA)
  • Mathematical Physics (AREA)
  • Navigation (AREA)
  • Traffic Control Systems (AREA)
  • Instructional Devices (AREA)

Claims (20)

  1. Procédé d'actualisation de données d'itinéraire qui sont enregistrées dans un appareil de navigation pour véhicule, notamment un appareil de navigation pour véhicule non embarqué, les données d'itinéraire étant actualisées lorsqu'il se produit au moins un événement préalablement défini, caractérisé par l'étape suivante : communication des données d'interrogation d'itinéraire à au moins une centrale au moins lorsqu'il se produit au moins un événement préalablement défini qui influence la fluidité du trafic, les données d'interrogation d'itinéraire incluant au moins des parties des données de fluidité du trafic acheminées à l'appareil de navigation pour véhicule et/ou des informations obtenues à partir des données de fluidité du trafic acheminées à l'appareil de navigation pour véhicule.
  2. Procédé selon la revendication 1, caractérisé en ce qu'il comprend en plus les étapes suivantes :
    b) calcul des données d'itinéraire actualisées dans la centrale et
    c) communication des données d'itinéraire actualisées à l'appareil de navigation pour véhicule.
  3. Procédé selon l'une des revendications précédentes, caractérisé en ce que l'au moins un événement préalablement défini qui influence la fluidité du trafic comprend l'apparition de perturbations de la fluidité du trafic sur l'itinéraire initialement prévu.
  4. Procédé selon l'une des revendications précédentes, caractérisé en ce qu'il est prévu que les données de fluidité du trafic soient acheminées manuellement et/ou automatiquement à l'appareil de navigation pour véhicule.
  5. Procédé selon l'une des revendications précédentes, caractérisé en ce que les données de fluidité du trafic sont communiquées à l'appareil de navigation pour véhicule par des détecteurs de véhicule et/ou par une ou plusieurs sources externes de données de fluidité du trafic.
  6. Procédé selon l'une des revendications précédentes, caractérisé en ce que l'appareil de navigation pour véhicule interprète les données de fluidité du trafic qui lui sont acheminées afin de déterminer s'il existe des perturbations de la fluidité du trafic qui imposent une actualisation des données d'itinéraire.
  7. Procédé selon l'une des revendications précédentes, caractérisé en ce que la centrale, après la réception des données d'interrogation d'itinéraire et avant le calcul des données d'itinéraire actualisées, soumet au moins certaines des données de fluidité du trafic qui se trouvent dans les données d'interrogation d'itinéraire à un contrôle, notamment à un contrôle de plausibilité.
  8. Procédé selon l'une des revendications précédentes, caractérisé en ce que le calcul des données d'itinéraire actualisées s'effectue à l'aide des données de fluidité du trafic disponibles dans la centrale.
  9. Procédé selon l'une des revendications précédentes, caractérisé en ce que le calcul des données d'itinéraire actualisées s'effectue à l'aide des données de fluidité du trafic qui se trouvent dans les données d'interrogation d'itinéraire.
  10. Procédé selon l'une des revendications précédentes, caractérisé en ce que le calcul des données d'itinéraire actualisées s'effectue à l'aide de cartes routières numériques disponibles dans la centrale.
  11. Procédé selon l'une des revendications précédentes, caractérisé en ce que les données de fluidité du trafic disponibles dans la centrale sont actualisées au moyen des données de fluidité du trafic qui se trouvent dans les données d'interrogation d'itinéraire.
  12. Procédé selon l'une des revendications précédentes, caractérisé en ce que la communication des données d'interrogation d'itinéraire et/ou des données d'itinéraire actualisées s'effectue par le biais d'un réseau de radiocommunication mobile.
  13. Appareil de navigation pour véhicule, notamment un appareil de navigation pour véhicule non embarqué, qui est prévu pour recevoir de la part d'une centrale, mémoriser et actualiser des données d'itinéraire, caractérisé en ce qu'il comprend les dispositifs suivantes :
    - des moyens qui communiquent des données d'interrogation d'itinéraire à au moins une centrale au moins lorsqu'il se produit un événement préalablement défini qui influence la fluidité du trafic, les données d'interrogation d'itinéraire incluant au moins des parties des données de fluidité du trafic acheminées à l'appareil de navigation pour véhicule et/ou des informations obtenues à partir de celles-ci et
    - des moyens pour recevoir et mémoriser les données d'itinéraire actualisées par au moins une centrale en tant que réponse aux données d'interrogation d'itinéraire communiquées.
  14. Appareil de navigation pour véhicule selon la revendication 13, caractérisé en ce que l'au moins un événement préalablement défini qui influence la fluidité du trafic comprend l'apparition de perturbations de la fluidité du trafic sur l'itinéraire initialement prévu.
  15. Appareil de navigation pour véhicule selon l'une des revendications 13 à 14, caractérisé en ce qu'il présente des dispositifs d'entrée auxquels les données de fluidité du trafic sont acheminées manuellement et/ou automatiquement.
  16. Appareil de navigation pour véhicule selon l'une des revendications 13 à 15, caractérisé en ce que les données de fluidité du trafic sont acheminées aux dispositifs d'entrée par des détecteurs de véhicule et/ou par une ou plusieurs sources externes de données de fluidité du trafic.
  17. Appareil de navigation pour véhicule selon l'une des revendications 13 à 16, caractérisé en ce qu'il présente des dispositifs d'interprétation qui interprètent les données de fluidité du trafic acheminées afin de déterminer s'il existe des perturbations de la fluidité du trafic qui imposent une actualisation des données d'itinéraire.
  18. Appareil de navigation pour véhicule selon l'une des revendications 13 à 17, caractérisé en ce qu'il présente en outre : des moyens qui transmettent les données de fluidité du trafic à au moins une centrale.
  19. Appareil de navigation pour véhicule selon l'une des revendications 13 à 18, caractérisé en ce qu'il présente des dispositifs de communication et/ou interagit avec des dispositifs de communication séparés afin de communiquer les données d'interrogation d'itinéraire et/ou recevoir les données d'itinéraire actualisées.
  20. Appareil de navigation pour véhicule selon l'une des revendications 13 à 19, caractérisé en ce que les dispositifs de communication sont formés par des dispositifs de radiocommunication mobiles.
EP02703494A 2001-02-07 2002-01-17 Mise a jour de donnees d'itineraires et de circulation, et appareil de navigation pour vehicule Expired - Lifetime EP1371047B1 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
DE10105449A DE10105449A1 (de) 2001-02-07 2001-02-07 Aktualisierung von Routen- und Verkehrsflussdaten sowie Fahrzeugnavigationsgerät
DE10105449 2001-02-07
PCT/DE2002/000114 WO2002063587A1 (fr) 2001-02-07 2002-01-17 Mise a jour de donnees d'itineraires et de circulation, et appareil de navigation pour vehicule

Publications (2)

Publication Number Publication Date
EP1371047A1 EP1371047A1 (fr) 2003-12-17
EP1371047B1 true EP1371047B1 (fr) 2010-09-01

Family

ID=7673103

Family Applications (1)

Application Number Title Priority Date Filing Date
EP02703494A Expired - Lifetime EP1371047B1 (fr) 2001-02-07 2002-01-17 Mise a jour de donnees d'itineraires et de circulation, et appareil de navigation pour vehicule

Country Status (5)

Country Link
US (1) US20040117113A1 (fr)
EP (1) EP1371047B1 (fr)
JP (1) JP2004518145A (fr)
DE (2) DE10105449A1 (fr)
WO (1) WO2002063587A1 (fr)

Families Citing this family (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100241342A1 (en) * 2009-03-18 2010-09-23 Ford Global Technologies, Llc Dynamic traffic assessment and reporting
US7319931B2 (en) * 2004-04-06 2008-01-15 Honda Motor Co., Ltd. Methods for filtering and providing traffic information
US8606516B2 (en) * 2004-11-30 2013-12-10 Dash Navigation, Inc. User interface system and method for a vehicle navigation device
US20060161335A1 (en) * 2005-01-14 2006-07-20 Ross Beinhaker Routing system and method
JP2007114044A (ja) * 2005-10-20 2007-05-10 Toyota Motor Corp 渋滞情報提供・受信システム及び方法、並びに、渋滞情報提供装置、及び車両用渋滞情報受信装置
US7668653B2 (en) 2007-05-31 2010-02-23 Honda Motor Co., Ltd. System and method for selectively filtering and providing event program information
EP2186074A1 (fr) 2007-08-29 2010-05-19 Continental Teves AG & CO. OHG Actualisation personnalisée de cartes de navigation numériques
US20090207043A1 (en) * 2008-02-20 2009-08-20 Ford Global Technologies, Inc Wireless, infrastructureless communication system for vehicles and method for the same
US20100292916A1 (en) * 2009-05-13 2010-11-18 Honda Motor Co., Ltd. Navigation System For a Motor Vehicle
US20110004523A1 (en) * 2009-07-06 2011-01-06 Ford Global Technologies, Llc Method and Apparatus for Preferential Determination and Display of Points of Interest
US20110098915A1 (en) * 2009-10-28 2011-04-28 Israel Disatnik Device, system, and method of dynamic route guidance
US9737268B1 (en) * 2010-02-24 2017-08-22 Sprint Communications Company L.P. Facilitating navigation data updates
US8423273B2 (en) 2010-03-30 2013-04-16 Honda Motor Co., Ltd. Minimum energy route for a motor vehicle
US8527132B2 (en) 2010-03-30 2013-09-03 Honda Motor Co., Ltd. Energy maps and method of making
US9846046B2 (en) 2010-07-30 2017-12-19 Ford Global Technologies, Llc Vehicle navigation method and system
US8335643B2 (en) 2010-08-10 2012-12-18 Ford Global Technologies, Llc Point of interest search, identification, and navigation
US8521424B2 (en) 2010-09-29 2013-08-27 Ford Global Technologies, Llc Advanced map information delivery, processing and updating
US8849552B2 (en) 2010-09-29 2014-09-30 Ford Global Technologies, Llc Advanced map information delivery, processing and updating
DE102011101359A1 (de) * 2011-05-12 2012-11-15 GM Global Technology Operations LLC (n. d. Gesetzen des Staates Delaware) Verfahren und Vorrichtung zur Klassifikation von Daten
US8688321B2 (en) 2011-07-11 2014-04-01 Ford Global Technologies, Llc Traffic density estimation
US8838385B2 (en) 2011-12-20 2014-09-16 Ford Global Technologies, Llc Method and apparatus for vehicle routing
US9713963B2 (en) 2013-02-18 2017-07-25 Ford Global Technologies, Llc Method and apparatus for route completion likelihood display
US9863777B2 (en) * 2013-02-25 2018-01-09 Ford Global Technologies, Llc Method and apparatus for automatic estimated time of arrival calculation and provision
US8977479B2 (en) 2013-03-12 2015-03-10 Ford Global Technologies, Llc Method and apparatus for determining traffic conditions
US9047774B2 (en) 2013-03-12 2015-06-02 Ford Global Technologies, Llc Method and apparatus for crowd-sourced traffic reporting
US9874452B2 (en) 2013-03-14 2018-01-23 Ford Global Technologies, Llc Method and apparatus for enhanced driving experience including dynamic POI identification
DE102014201041A1 (de) * 2014-01-21 2015-07-23 Bayerische Motoren Werke Aktiengesellschaft Bereitstellung einer Fahrtroute in einem Navigationssystem eines Kraftfahrzeugs

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH06119596A (ja) * 1992-10-08 1994-04-28 Fujitsu General Ltd 救急車ナビゲーションシステム
JP3469930B2 (ja) * 1994-02-14 2003-11-25 株式会社シーエスケイ 移動体マルチメディア通信システム及び移動体
JPH08136277A (ja) * 1994-11-11 1996-05-31 Sumitomo Electric Ind Ltd 迂回経路計算機能を備えるナビゲーション装置
JP3472896B2 (ja) * 1994-12-28 2003-12-02 オムロン株式会社 交通情報システム
JPH11183180A (ja) * 1997-12-16 1999-07-09 Mitsubishi Electric Corp 移動体通信ナビゲーションシステム並びに該システムの固定局装置及び該システムの移動体装置
US6150961A (en) * 1998-11-24 2000-11-21 International Business Machines Corporation Automated traffic mapping
JP3896728B2 (ja) * 1999-06-23 2007-03-22 トヨタ自動車株式会社 携帯型端末装置及び車載情報処理装置
US6480783B1 (en) * 2000-03-17 2002-11-12 Makor Issues And Rights Ltd. Real time vehicle guidance and forecasting system under traffic jam conditions

Also Published As

Publication number Publication date
DE50214625D1 (de) 2010-10-14
JP2004518145A (ja) 2004-06-17
DE10105449A1 (de) 2002-08-08
US20040117113A1 (en) 2004-06-17
EP1371047A1 (fr) 2003-12-17
WO2002063587A1 (fr) 2002-08-15

Similar Documents

Publication Publication Date Title
EP1371047B1 (fr) Mise a jour de donnees d'itineraires et de circulation, et appareil de navigation pour vehicule
EP0819295B1 (fr) Procede pour systeme de guidage et d'information de vehicule
DE10217880B4 (de) Verfahren zum Kompilieren von Navigationsrouteninhalt
EP2186077B1 (fr) Procédé et dispositif de commande du trafic routier
EP1186865B1 (fr) Procédé de détermination de la trajectoire d'un véhicule
EP1224645B2 (fr) Procede de codage et de decodage d'objets dans un reseau de voies de circulation
EP2953111B1 (fr) Procédé et dispositif destinés à déterminer des aires de stationnement libres sur des parkings de camions et communication au conducteur de camion
DE102015219467A1 (de) Verfahren zum Betreiben eines zentralen Servers und Verfahren zum Handhaben einer Regelkarte
EP1360458B1 (fr) Procede d'echange d'informations de navigation
DE112009004441B4 (de) Fahrzeugantriebs-Unterstützungsvorrichtung
EP2872351B1 (fr) Procédé pour faire fonctionner un système d'assistance à la conduite pour un véhicule et système d'assistance à la conduite pour un véhicule
DE112006002676T5 (de) Berechnung einer optimalen Route auf der Grundlage einer Kohortenanalyse
DE102009008745A1 (de) Verfahren und System zur automatischen Verkehrsführung
EP2662848A2 (fr) Procédé de fabrication dýun profil de conduite
DE102016003432A1 (de) System und Verfahren zur Koordinierung einer Fahrzeugverbandsformation
DE102017213073A1 (de) Verfahren zum Ermitteln eines Anhalteorts eines Kraftfahrzeugs
DE19547574A1 (de) Verfahren für ein Fahrzeugleit- und Informationssystem
DE102022001844A1 (de) Verfahren zum Ermitteln einer Navigationsroute
DE102007000971B4 (de) Verfahren zur kollaborativen Pflege von Kartenmaterial für mobile Navigationsgeräte
EP1342221B1 (fr) Procede permettant d'effacer automatiquement une signalisation de trafic
EP1466140A1 (fr) Procede de determination d'un temps de trajet
DE102012212815B4 (de) Verfahren zur Auswahl und Aufbereitung von Verkehrsinformationen
DE102006013297B4 (de) Verfahren zum Betrieb eines Navigationssystems
EP3140616B1 (fr) Procédé d'utilisation d'un système de navigation d'un véhicule automobile et véhicule automobile
DE102021003610A1 (de) Verfahren zur Absicherung der Kommunikation

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

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR

RIN1 Information on inventor provided before grant (corrected)

Inventor name: SKWAREK, VOLKER

Inventor name: DRAEGER, GERD

Inventor name: FRIEDRICHS, ARNE

Inventor name: LAEDKE, MICHAEL

RIN1 Information on inventor provided before grant (corrected)

Inventor name: SKWAREK, VOLKER

Inventor name: DRAEGER, GERD

Inventor name: FRIEDRICHS, ARNE

Inventor name: LAEDKE, MICHAEL

17Q First examination report despatched

Effective date: 20090512

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): DE ES FR GB IT SE

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

Free format text: NOT ENGLISH

REF Corresponds to:

Ref document number: 50214625

Country of ref document: DE

Date of ref document: 20101014

Kind code of ref document: P

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

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

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

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

Effective date: 20110117

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 50214625

Country of ref document: DE

Effective date: 20110606

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

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 15

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 16

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 17

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

Ref country code: FR

Payment date: 20190122

Year of fee payment: 18

Ref country code: IT

Payment date: 20190121

Year of fee payment: 18

Ref country code: DE

Payment date: 20190326

Year of fee payment: 18

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 50214625

Country of ref document: DE

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

Ref country code: DE

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

Effective date: 20200801

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

Ref country code: IT

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

Effective date: 20200117