EP0883872B1 - Procede et dispositif d'information d'abonnes mobiles - Google Patents

Procede et dispositif d'information d'abonnes mobiles Download PDF

Info

Publication number
EP0883872B1
EP0883872B1 EP97952715A EP97952715A EP0883872B1 EP 0883872 B1 EP0883872 B1 EP 0883872B1 EP 97952715 A EP97952715 A EP 97952715A EP 97952715 A EP97952715 A EP 97952715A EP 0883872 B1 EP0883872 B1 EP 0883872B1
Authority
EP
European Patent Office
Prior art keywords
route
request
message
der
information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Lifetime
Application number
EP97952715A
Other languages
German (de)
English (en)
Other versions
EP0883872A1 (fr
Inventor
Bernd Günther
Henning Weise
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.)
Telekom Deutschland GmbH
Original Assignee
Deutsche Telekom AG
DeTeMobil Deutsche Telekom Mobilnet 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 Deutsche Telekom AG, DeTeMobil Deutsche Telekom Mobilnet GmbH filed Critical Deutsche Telekom AG
Publication of EP0883872A1 publication Critical patent/EP0883872A1/fr
Application granted granted Critical
Publication of EP0883872B1 publication Critical patent/EP0883872B1/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/096833—Systems involving transmission of navigation instructions to the vehicle where different aspects are considered when computing the route
    • G08G1/096838—Systems involving transmission of navigation instructions to the vehicle where different aspects are considered when computing the route where the user preferences are taken into account or the user selects one route out of a plurality
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/09—Arrangements for giving variable traffic instructions
    • G08G1/0962—Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
    • G08G1/0968—Systems involving transmission of navigation instructions to the vehicle
    • G08G1/096855—Systems involving transmission of navigation instructions to the vehicle where the output is provided in a suitable form to the driver
    • G08G1/096861—Systems involving transmission of navigation instructions to the vehicle where the output is provided in a suitable form to the driver where the immediate route instructions are output to the driver, e.g. arrow signs for next turn
    • 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/096877—Systems involving transmission of navigation instructions to the vehicle where the input to the navigation device is provided by a suitable I/O arrangement
    • G08G1/096883—Systems involving transmission of navigation instructions to the vehicle where the input to the navigation device is provided by a suitable I/O arrangement where input information is obtained using a mobile device, e.g. a mobile phone, a PDA

Definitions

  • the invention relates to a method and an arrangement for route information mobile Participant according to the preamble of claim 1.
  • WO-A-90/02391 describes a route guidance system for determining a route between two given geographic locations.
  • the location information is provided by a User fed a central data processing system, which from this data generates a route description and makes it available to the user.
  • This system is not for mobile use, i.e. a mobile user.
  • WO-A-96/11381 relates to a device for guiding people.
  • the facility comprises a navigation unit which has a receiving device for wirelessly transmitted Has information for recognizing the current geographic position, a Communication unit, which is an input unit in particular for entering a target position and an output unit, in particular for output of route guidance information.
  • a central computer for route planning is also provided, which has a memory has at least one digitized road map and that with the navigation unit is technically connectable via the communication unit. The computer transmits the calculated route information to the navigation unit.
  • the current position can be shown on a map and it can Route directions are issued.
  • WO-A-96/00373 relates to an electronic navigation system in which starting from a subscriber unit makes a route request to a central unit in which Central unit a route calculation and preparation of the data and the complete route information is transmitted to the subscriber unit in which one The route is processed.
  • the object of the invention is to provide a method and an arrangement for To propose route information of mobile participants that is always current to the participant Provides information and at the same time offers a high level of user comfort.
  • data can be related to a wide variety of output parameters e.g. Location, start or destination information or route information of the trip, Central or terminal-side queries that are device-based or person-based can be carried out.
  • the data transfers can too Information acquisition purposes and / or for information transmission purposes as well be carried out to update information.
  • the navigation services support the customer on their way to their destination Route.
  • the route is calculated taking into account the current traffic situation in the service center.
  • the orientation guide described in this document is a simple navigation service, the customer with limited wrong way detection and return to his destination leads.
  • the route is preferably presented in the terminal by means of a Rough route description and can be represented in particular by icons (signposts) are used to guide the customer to their destination.
  • the orientation aid has preferably a restricted mistrack detection. A targeted return to the Route can be supported
  • the Orientation Aid service is intended in particular for devices that do not stored location or street data like a digital map in the vehicle, but only with Positioning devices such as are equipped with GPS (in the following is mostly a system with GPS is described as an example). It is therefore usually not possible to be exact at a certain location (maneuver point) turn instructions such as B. "turn right now” to give, because due to the limited positioning accuracy often the necessary exact determination of the vehicle position (especially with GPS approx. 10m) not is possible.
  • the central unit takes into account the route generated by the Terminal transmitted information about the location function of the terminal (e.g. pure GPS or additional dead reckoning). This ensures that even with end devices a functional orientation aid without dead reckoning - albeit of lower quality - becomes possible.
  • the route evaluation service is also described in this document.
  • the Route evaluation becomes a route known in the terminal from the terminal to the head office transfer.
  • the route is based on the current traffic situation Estimated travel time and transferred to the terminal.
  • Various forms are supported for entering the destination address (e.g. city and street, POI: e.g. B. airport, train station).
  • POI e.g. B. airport, train station
  • the route request is followed by a destination request directly on the end device
  • the customer information is checked for correctness, completeness and uniqueness. Possibly. an error message is sent to the vehicle.
  • the user request is incomplete If the address information is not clearly interpreted, the error message will result in a Selection list delivered to the vehicle with which the request can be specified.
  • the route is prepared at the headquarters. With the Route_Message the Route information sent to the vehicle. With the transfer of the route into the vehicle is for the head office ended the request.
  • the list of waypoints is processed locally in the end device.
  • the order of Waypoints on the route are given by the order of their appearance in the list.
  • the route is processed sequentially according to the waypoint list, whereby for each Intersection at which a turning maneuver must be carried out, this by an appropriate Icon is displayed.
  • Wrong journeys are recognized when the customer enters a given corridor whose width the route description is loaded into the terminal.
  • This service enables the evaluation of a route existing in the terminal with regard to the travel time to be expected on the basis of the current traffic situation (see FIG. 3). For this, the Transfer the route description (of the route to be calculated) to the head office (Travel_Time_-Request_Message). The route becomes the same as for orientation aid or route guidance described in the form of guidance points.
  • the head office estimates the travel time for this route based on the current traffic situation and transfers this to the end device (Travel_Time_Message).
  • the individual services are described functionally and the specific ones Processes shown based on the ADP's.
  • the coding of the ADPs is explained.
  • the services can be parameterized with regard to certain processes and functions.
  • the defined Service parameters are listed in this document. Determining the individual Service parameterization is the task of the respective service provider. This basic specification sets the total scope of those to be supported by first generation devices Functions and processes. In addition, these processes and functions can be performed by respective service providers are specified in more detail in separate documents.
  • Mailbox flag MF 1 0 no messages in the mailbox 1: There are messages in the mailbox Debit Info MF 4 0: not supported in this version Length user data MF 9 Number (in bytes) of the user data transmitted within the message (CAS header + ADPU)
  • the framework supports the sending of several short messages.
  • Application IDs are unique service identifiers assigned by the head office. This are transferred in the Application ID field in the transport layer.
  • the service providers can operate independent services within the defined processes define. These can, for example, be characterized in that the transmitted Information content can be restricted. To identify the services offered Assign service identifiers.
  • the Initiative Flag 1 (initiative).
  • Protocol Discriminator and Message Type are in the document "Message Type Numbering ".
  • the bulk flag is always set to 0
  • the timers relevant for the navigation services are listed below. description function unit value range resolution default TNAVa Waiting state for reply of a route message or an error message sec 0-300 30 90 TNAVb Waiting for the first call to the call center sec 0 - 60 5 10 TNAVc Max. Duration of access to the operator at the call center min 0 - 15 1 5 TNAVd Waiting for an answer sec 0-300 30 90 Travel time message
  • the terminal For the orientation aid service, the terminal must have the full address management Support functionality of internal services.
  • the terminal For the route evaluation service, the terminal must have the full address management Support functionality of internal services.
  • the switch determines whether the entry of complete telephone numbers is also permitted.
  • Address_request_ambigious_addresses_selection_list Commentary Selection lists are returned for address inquiries 35 1
  • one Online service initiates a route calculation (also with a time delay) so that the terminal then receives a route description without initiating a route request. In this case it starts the process immediately with the processing of the route in the terminal.
  • the end devices must process this processing from "foreign", i.e. route initiated by third parties Support messages.
  • Via points can be used to exclude or close unwanted routes correct. Avoidance points are initially not supported.
  • the head office checks the information received for correctness, completeness and uniqueness and assigns the address or addresses a geographic coordinate or their geographic Coordinate to (see below).
  • the customer When entering the destination on the end device, the customer provides the addresses for the destination and all desired Viapoints on the end device or select them from an existing one Address memory of the terminal.
  • the addresses are transmitted to the head office via the Route_Request_Message and there checked for correctness, completeness and uniqueness. In the event of incomplete address details there is an error message, which if possible an address selection list for the questionable Contains addresses.
  • the customer can then select the desired address and with it initiate a new route request. It can be set by a parameter whether the control center fundamentally supports the return of selection lists (see Chapter 2.7). All in the ADP provided fields for the specification and transmission of address information are support on the terminal side. Which combinations and subsets on the central side support is to be specified specifically for the service provider.
  • the error message is transmitted to the vehicle. This can contain selection lists. The support of the error message depends on the service provider.
  • Postal code and telephone number may not be passed at the same time, otherwise there is an error message. The same applies if the place name and postal code or telephone number are contradictory.
  • control center can use the bit "start / desination / additional address ambiguous ".
  • a selection list field follows within the Address description, in which an error declaration in free text in the "Additional Information" field is specified. If a complete telephone number cannot be clearly interpreted, then returned the phone number with the digits that could be interpreted (Example: 0228-5201900 is transferred, the control center can dial the number up to 02285201 interpret and return this number).
  • the coding of the individual IE's is detailed in the ADP for the navigation services described.
  • the request telegram is not subject to any special restrictions. It is recommended that Starting address and the criteria selected by the customer for route calculation in the end device to save and transfer to the control center.
  • the desired operator request is also identified in the message by that no destination address is also transmitted.
  • the message must contain the start address (pearl necklace or postal address description). If desired, the criteria for route calculation can already be transferred with the request.
  • the message can also contain all other IE's except for the destination address. It's closed recommend that the criteria selected by the customer for route calculation in the end device save and transfer to the central office.
  • the operator determines the in dialogue with the customer missing information until there are unique addresses for the destination as well possible via and avoid points.
  • the center then sends the route after the route has been calculated (Route_Message) into the vehicle.
  • the route is based on the transmitted information based on the current Traffic situation created and coded in the Route_Message. Then the Transfer Route_Message to the vehicle.
  • the central one When calculating the route and preparing the route, the central one is used for the Route request with transmitted information about the location considered. In doing so first a terminal with pure GPS and terminals with additional coupling navigation distinguished.
  • the travel time to the destination is transmitted in a rounded manner, ie the head office rounds the calculated travel time (e.g. 37 minutes or 3 hours, 31 minutes) to a reasonable value, which depends on the accuracy of the calculation (e.g. 40 minutes; 3 hours, 30 minutes). If an arrival time is calculated in the end device from the travel time to the destination by addition to the actual time and displayed to the customer, then an additional rounding should also take place here. A suggestion is made in the table below: Travel time to the destination Proposed resolution up to 30 minutes 5 minutes up to 90 minutes 10 mins greater than 90 minutes 15 minutes
  • the list of waypoints denotes maneuver points. They are placed in places where the driver is likely to need information in order to be able to follow the route (turn, classify, name changes of streets, etc.).
  • the order in which the waypoints are to be driven is by the order of the Waypoints specified in the list.
  • the waypoints can be positioned to be handled differently depending on the service provider. This is especially for the first or last waypoint in a waypoint list. In their interpretation is also the code contained in the IE "Type of Starting Point” or "Type of Destination” to consider. The exact definitions are specific to the service provider Additional specifications made.
  • the terminal should then be in compass mode switch, with the compass arrow pointing to the first waypoint.
  • the type "capture area" is not supported for guidance.
  • the rough textual description of the route contains essential milestones of the route Provide users with an overview of the route to be traveled (e.g. drive from Bonn to Düsseldorf: A555 to Kreuzchen Süd, A4 todorfchen Ost, A1 to Stammchen Nord, A57 to Buch Kaarst).
  • the milestones are transmitted either as text or as geo-code. A mix of text and geo-codes is possible.
  • the geographic coordinates are dependent on the type of intersection and set link flag set.
  • the meaning of the coordinates is specified in the service specification of the Provider specified in detail.
  • the geographic coordinates are preferably assigned according to the following rules: mating type link flag unset link fiag set 1st waypoint 2nd waypoint star Center of the junction Center of the junction 1st intersection Center of the junction 2nd intersection roundabout traffic Entry point of the roundabout Entry point into the roundabout Exit point from the roundabout Motorway exit / fork Start of the turning lane for simple exits, for complex exits the actual exit lane % %
  • both waypoints contain an icon coding of the star type.
  • the screen display should be in an icon.
  • the Exit street of the 1st waypoint is closed with the entrance street of the 2nd waypoint combine.
  • Wrong journeys are recognized because the reference area spanned by the corridor width the user must be informed.
  • the terminal should now give the user the Give the possibility to start a new route request related to the same destination. additionally should be switched to compass mode, with the arrow pointing to the closest one Waypoint shows.
  • a change in the waypoint pointed by the arrow should be explicitly acknowledged by the user.
  • the user can switch between waypoints in compass mode.
  • the user should only be informed of an incorrect drive when the position is above moved a greater distance outside the corridor. This can cause inaccuracies in the GPS are taken into account or suppressed.
  • the further one Clarification / individualization takes place via the evaluation of the geo codes relative to the current position or to the waypoints and the associated corridor information.
  • T-Traffic traffic reports preferably contain these Street name (e.g. A555, B236). This makes it possible to record traffic reports refer to roads that are on the route from the total of the terminal filter out existing traffic reports (e.g. in the case of or targeted VI service, cell broadcast).
  • the terminal device should not include one in the rough route description receive interpretable geo-code, then this can be done using the TINFO message TINFO_Code_Request_Message can be translated into plain text (see ADP TINFO).
  • Traffic announcements contain a bypass flag. Will a traffic announcement Received on the route with the redirection flag set, should the customer with the display the traffic announcement the possibility of a new route request (combined with a travel Time request) (see also chapter 3.4).
  • Each service provider can freely assign numbers for service provider POIs Assign individual POI types (e.g. petrol stations, ATMs).
  • individual POI types e.g. petrol stations, ATMs.
  • service provider POIs are not initially numbered established. If service provider POIs are to be used for the navigation service, then the complete address of the desired one must be used by using an information service POIs can be loaded from the head office. This address can then be used for a destination request be used. It should always be the complete address information received from the central office to the service provider POI to avoid ambiguity (see also Chapter 3.1.1.1).
  • the request to the control center is only the route request message (no operator, see Fig. 5).
  • the information is off at the central site the route message (at least the starting position) and from the dialog with the operator merge. It must be through a timer-based synchronization mechanism be sure that the Route_Message is available to the operator at the start of the call.
  • the terminal After a timer has expired, the terminal sets up the voice connection to the operator (FIG. 6).
  • Route_Messages that it did not initiate (FIG. 7).
  • Route_Messages can e.g. B. Online services have been initiated via other media).
  • the route message should never be presented without an active acknowledgment by the user.
  • a route description (a calculated route) is included in the route evaluation Transfer headquarters (Travel_Time_Request_Message).
  • the Rolute is like the Orientation aid or route guidance described in the form of guidance points.
  • the head office estimates the travel time for this route based on the current traffic situation and transfers this to the end device (Travel_Time_Message).
  • the coding of the individual IE'S is detailed in the ADP for the navigation services described.
  • the service-specific error messages are defined in the ADP.
  • Services Cross Errors e.g. communication errors
  • Description of the cross-service error handling is described in the document "Description of the cross-service error handling ".
  • Cross-Service Error Handling Description Document additional destination 1 not identified s. Chapter 3.1.1.1 additional destination 2 not identified s. Chapter 3.1.1.1 additional destination 3 not identified s. Chapter 3.1.1.1 additional destination 4 not identified s. Chapter 3.1.1.1 additional destination 5 not identified s. Chapter 3.1.1.1 additional destination 6 not identified s. Chapter 3.1.1.1 additional destination 1 ambiguous s. Chapter 3.1.1.1 additional destination 2 ambiguous s. Chapter 3.1.1.1 additional destination 3 ambiguous s. Chapter 3.1.1.1 additional destination 4 ambiguous s. Chapter 3.1.1.1 additional destination 5 ambiguous s. Chapter 3.1.1.1 additional destination 6 ambiguous s. Chapter 3.1.1.1 phone call not completed s.
  • the data communication between the terminal and the control center is carried out by the GSM available short message service. Unlike other VT services Cell broadcast is not required for navigation services, so only Short message services SMS-MT (TS 21) and SMS-MO (TS 22) for handling the Services are needed. In order to continue to allow operator requests, the voice service (TS 11) are supported.
  • GSM Global System for Mobile communications
  • the end device should have dead reckoning.
  • the location accuracy with coupler navigation must be ⁇ 50 m on average.
  • the accuracy of the Dead reckoning should be 5% of the distance traveled when driving slowly around town (30 - 50 km / h) Distance and when driving at medium speed (70 - 90 km / h) 3% of the distance traveled Do not exceed the distance, with a maximum GPS shadowing distance of 1000 meters is taken as a basis.
  • the GPS signal acquisition times should be in the range of 1 to 2 seconds.
  • the end device must have a graphic display with the possibility of graphic and text display, as well as a convenient input option. In addition, a voice output of the maneuvers is desirable.
  • Recommendation dot matrix min 128x112 minute 4 lines, min. 20 characters / line
  • the device should be able to store at least 40 waypoints for orientation. Ideally, 100 waypoints that can be saved should be provided for a route. Around A notebook with at least 50 entries should make it easier to enter destinations exist from which i.a. the target description can also be adopted.
  • the waypoint memory should be designed dynamically so that for example at waypoints, which are transmitted without street names, no memory for the street name is kept free.
  • a destination entry should also be possible with the help of geo-coding.
  • the display of instructions should be announced by an acoustic signal.
  • the user should be able to scroll between the signpost symbols can (especially switch to the next waypoint).
  • the orientation aid service is intended for end devices, which are preferably equipped with GPS without a digital map in the vehicle. That is why not possible, as with navigation systems at the maneuvering point, turn instructions such as B. turn right now "because of the limited Positioning accuracy the necessary exact determination of the vehicle position (about 10m exactly) is not feasible.
  • the signpost symbol should be approx. 50m (without dead reckoning 100m) after reaching the geographical coordinates of the signpost icon are removed from the screen (at link flag after reaching the second geographic coordinate).
  • the display is based on a display with at least 128 x 112 pixels.

Landscapes

  • Engineering & Computer Science (AREA)
  • Radar, Positioning & Navigation (AREA)
  • Remote Sensing (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Mathematical Physics (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Navigation (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Claims (11)

  1. Procédé pour informer des abonnés mobiles sur une trajectoire, selon lequel des données sont transmises, sur demande ou automatiquement, entre une unité centrale et une unité d'abonné mobile ; côté unité d'abonné, une demande d'itinéraire est faite à l'unité centrale, un calcul d'itinéraire et un traitement des données ont lieu dans cette unité centrale et l'information complète sur l'itinéraire est transmise à l'unité centrale, dans laquelle ladite information est traitée ; l'information sur l'itinéraire est sortie dans l'unité d'abonné à l'aide d'une unité d'entrée/sortie sous la forme d'une description textuelle grossière d'itinéraire et d'une distance totale et d'un temps de parcours calculés jusqu'au lieu de destination compte tenu de la situation actuelle du trafic, et contient une liste de points de route qui désignent des points de manoeuvre à l'aide desquels des manoeuvres imminentes sont signalées rapidement à l'abonné mobile ; et l'abonné est informé, à l'aide d'une représentation abstraite de symboles d'orientation, de la topographie des intersections et des manoeuvres à effectuer au niveau du point de manoeuvre
       caractérisé en ce qu'on définit entre les points de route individuels une zone de référence d'une certaine largeur de corridor, qui sert à détecter les trajets incorrects et à sélectionner des informations routières importantes pour l'itinéraire.
  2. Procédé selon la revendication 1, caractérisé en ce que l'interrogation d'itinéraire se fait grâce à une entrée au niveau de l'unité d'abonné, ou à l'aide d'une liaison phonie avec un opérateur.
  3. Procédé selon la revendication 1 ou 2, caractérisé en ce que le calcul d'itinéraire se fait dans l'unité centrale, à partir d'une demande d'itinéraire, à l'aide des données suivantes : point de départ, adresse de destination et heure de départ ou d'arrivée souhaitée.
  4. Procédé selon la revendication 1, caractérisé en ce qu'on transmet la liste des points de route avec les contenus suivants :
    les coordonnées géographiques du point de route ;
    le nom de la localité ;
    une représentation abstraite de l'intersection sous la forme de symboles d'orientation ; et
    un ou plusieurs indicateurs.
  5. Procédé selon la revendication 3 ou 4, caractérisé en ce que grâce aux symboles d'orientation, quatre types d'intersections possibles peuvent être représentés par l'unité d'entrée/sortie :
    intersection en étoile ;
    rond-point ;
    sortie d'autoroute/bifurcation; et
    double intersection/déportement.
  6. Procédé selon l'une des revendications 1, 3 à 5, caractérisé en ce qu'on transmet la liste des points de route avec les contenus supplémentaires suivants :
    désignation officielle de la route au niveau de laquelle il faut tourner ;
    la durée de trajet évaluée jusqu'au point de route suivant ;
    la distance jusqu'au point de route suivant ;
    une indication d'action ;
    la largeur de corridor pour définir une zone de référence ; et
    le nombre d'intersections jusqu'au point de manoeuvre suivant, et la distance jusqu'à l'intersection suivante.
  7. Procédé selon l'une des revendications 1 à 6, caractérisé en ce que sous la forme d'un service supplémentaire, une évaluation d'un itinéraire quelconque prévu dans l'unité d'abonné et transmis à l'unité centrale a lieu et porte sur la durée de voyage à prévoir, sur la base de l'état actuel de la circulation, la durée du voyage calculée étant transmise à l'unité d'abonné.
  8. Procédé selon l'une des revendications 1 à 7, caractérisé en ce que la communication entre l'unité d'abonné et l'unité centrale est réalisée par l'intermédiaire du service de messages courts d'un réseau de communication GSM.
  9. Procédé selon l'une des revendications 1 à 7, caractérisé en ce que pour localiser l'unité d'abonné, on utilise un dispositif de réception GPS.
  10. Procédé selon l'une des revendications 1 à 8, caractérisé en ce qu'on utilise une unité d'entrée/sortie sous la forme d'un affichage graphique.
  11. Procédé selon l'une des revendications 1 à 10, caractérisé en ce qu'on utilise une unité d'entrée/sortie pourvue d'un dispositif de sortie vocale.
EP97952715A 1996-12-10 1997-12-10 Procede et dispositif d'information d'abonnes mobiles Expired - Lifetime EP0883872B1 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
DE19651146A DE19651146A1 (de) 1996-12-10 1996-12-10 Verfahren und Anordnung zur Information mobiler Teilnehmer
DE19651146 1996-12-10
PCT/DE1997/002884 WO1998026396A1 (fr) 1996-12-10 1997-12-10 Procede et dispositif d'information d'abonnes mobiles

Publications (2)

Publication Number Publication Date
EP0883872A1 EP0883872A1 (fr) 1998-12-16
EP0883872B1 true EP0883872B1 (fr) 2002-05-08

Family

ID=7814139

Family Applications (1)

Application Number Title Priority Date Filing Date
EP97952715A Expired - Lifetime EP0883872B1 (fr) 1996-12-10 1997-12-10 Procede et dispositif d'information d'abonnes mobiles

Country Status (5)

Country Link
EP (1) EP0883872B1 (fr)
AT (1) ATE217434T1 (fr)
AU (1) AU5650798A (fr)
DE (2) DE19651146A1 (fr)
WO (1) WO1998026396A1 (fr)

Families Citing this family (29)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE19816585B4 (de) * 1998-04-08 2004-08-12 Atx Europe Gmbh Verfahren zur Routeninformation eines Endgerät-Benutzers durch Übermittlung von Routeninformationen von einer Zentrale an das Endgerät
EP2009608A3 (fr) * 1998-11-23 2009-09-23 Integrated Transport Information Services Limited Système instantané de surveillance de trafic
DE19906863A1 (de) * 1999-02-18 2000-10-19 Nokia Mobile Phones Ltd Verfahren zur Navigation eines Objekts
EP1750091B1 (fr) * 1999-06-22 2008-05-21 Mitsubishi Denki Kabushiki Kaisha Serveur d'un système de navigation
DE19937372A1 (de) 1999-08-12 2001-02-15 Bosch Gmbh Robert Verfahren zur Anforderung und zur Verarbeitung von Verkehrsmeldungen
DE19937370A1 (de) * 1999-08-12 2001-02-15 Bosch Gmbh Robert Verfahren zur Anforderung und zur Überarbeitung von Verkehrsmeldungen
AU2115601A (en) 1999-10-19 2001-04-30 Magellan Dis, Inc. Portable vehicle navigation system
DE10014806C2 (de) * 2000-03-27 2003-11-27 Tegaron Telematics Gmbh Verfahren zur Off-Board-Navigation eines Fahrzeug
DE10030805A1 (de) * 2000-06-29 2002-01-10 Nokia Mobile Phones Ltd Verfahren und Mobilstation zur Wegführung
US6587781B2 (en) 2000-08-28 2003-07-01 Estimotion, Inc. Method and system for modeling and processing vehicular traffic data and information and applying thereof
DE10105897A1 (de) * 2001-02-09 2002-08-14 Bosch Gmbh Robert Verfahren zum Austauschen von Navigationsinformationen
DE10105898A1 (de) 2001-02-09 2002-08-14 Bosch Gmbh Robert Verfahren zum Übergeben von Zielführungselementen, Fahrzeugnavigationsgerät und Zentrale
ATE288607T1 (de) 2001-03-12 2005-02-15 Magellan Dis Inc Off-board-navigationssystem mit personalisierter navigations-datenbank
US7853404B2 (en) 2001-04-03 2010-12-14 Mitac International Corporation Vehicle docking station for portable handheld computing device
DE10128409B4 (de) * 2001-06-12 2007-05-31 Harman Becker Automotive Systems Gmbh Navigationssystem
EP1502078A1 (fr) 2002-04-30 2005-02-02 Telmap Ltd. Systeme de distribution de cartes a base de modeles
TW588292B (en) * 2003-02-21 2004-05-21 Sin Etke Technology Co Ltd Simplified navigation guidance method and system thereof
TWI220508B (en) * 2003-05-02 2004-08-21 Sin Etke Technology Co Ltd Easy vehicle navigation method and system
DE10322558A1 (de) * 2003-05-20 2004-12-09 Robert Bosch Gmbh Verfahren und System zum Zuordnen von Diensteanbietern zu Telematikendgeräten
US7620402B2 (en) 2004-07-09 2009-11-17 Itis Uk Limited System and method for geographically locating a mobile device
US7251561B2 (en) 2004-07-28 2007-07-31 Telmap Ltd. Selective download of corridor map data
DE602006016025D1 (de) * 2005-05-18 2010-09-16 Lg Electronics Inc Bereitstellung von Verkehrsinformationen in Bezug auf einen Stautrend
KR20060119739A (ko) 2005-05-18 2006-11-24 엘지전자 주식회사 구간 통과시간에 대한 예측정보를 제공하고 이를 이용하는방법 및 장치
KR20060119746A (ko) 2005-05-18 2006-11-24 엘지전자 주식회사 교통상태에 대한 정보를 제공하고 이를 이용하는 방법 및장치
US7729335B2 (en) 2005-05-18 2010-06-01 Lg Electronics Inc. Providing traffic information relating to a prediction of congestion status and using the same
DE102008033907A1 (de) * 2008-07-18 2010-01-21 Deutsche Post Ag Verfahren und Vorrichtung zum Bereitstellen von Navigationsdaten, Navigationsgerät
GB0901588D0 (en) 2009-02-02 2009-03-11 Itis Holdings Plc Apparatus and methods for providing journey information
GB2492369B (en) 2011-06-29 2014-04-02 Itis Holdings Plc Method and system for collecting traffic data
US9141975B2 (en) 2012-09-23 2015-09-22 Intel Corporation Inferring user risk profile from travel patterns

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4954958A (en) * 1988-08-19 1990-09-04 Hacowie Corporation Directional information system
US5543789A (en) * 1994-06-24 1996-08-06 Shields Enterprises, Inc. Computerized navigation system
DE19521929A1 (de) * 1994-10-07 1996-04-11 Mannesmann Ag Einrichtung zur Zielführung von Personen

Also Published As

Publication number Publication date
EP0883872A1 (fr) 1998-12-16
ATE217434T1 (de) 2002-05-15
AU5650798A (en) 1998-07-03
WO1998026396A1 (fr) 1998-06-18
DE59707219D1 (de) 2002-06-13
DE19651146A1 (de) 1998-06-25

Similar Documents

Publication Publication Date Title
EP0883872B1 (fr) Procede et dispositif d'information d'abonnes mobiles
EP0883871B1 (fr) Technique et systeme d'information en matiere de trafic
EP1030166B1 (fr) Méthode pour la navigation d' un objet
EP1186865B1 (fr) Procédé de détermination de la trajectoire d'un véhicule
EP1198696B1 (fr) Procede et dispositif pour la transmission d'informations de navigation d'une centrale de donnees a un systeme de navigation monte dans un vehicule
EP0890080B1 (fr) Procede pour planifier l'itineraire de vehicules et guider ces derniers
DE2925656C2 (fr)
DE3887285T2 (de) Zielführungs- und Streckenauswahlsysteme für Kraftfahrzeuge.
EP1062481B1 (fr) Procede d'affichage d'informations de trafic
WO2001015117A1 (fr) Carte d'embouteillage topologique wap par combinaison de sections de cartes dans un central d'informations routieres
EP0988508A1 (fr) Procede et dispositif pour produire, reunir et actualiser des fichiers de parcours
DE10105897A1 (de) Verfahren zum Austauschen von Navigationsinformationen
DE69326114T2 (de) Verfahren und Vorrichtung zur Fahrzeugführung auf Verkehrsstrassen
EP1342221A1 (fr) Procede permettant d'effacer automatiquement une signalisation de trafic
EP1120632A1 (fr) Procédé de guidage de personnes vers une destination
DE102015200081A1 (de) Bereitstellen von Navigationshinweisen in einem Fahrzeug
EP2205942B1 (fr) Système de navigation et procédé de détermination d'itinéraire
DE10323936A1 (de) Navigationssystem und-Verfahren
DE10052934A1 (de) Verfahren zur Bestimmung eines Weges zwischen einem Ausgangspunkt und einem Endpunkt eines Netzes, wie beispielsweise Straßennetzes
EP1255092B1 (fr) Dispositif et procédé pour afficher de l'information dans un véhicule
DE19750777B4 (de) Verfahren zur Übertragung von einer Route eines Fahrzeuges in einem Verkehrsnetz betreffenden Routeninformationen zwischen einer Verkehrszentrale und einem Endgerät in einem Fahrzeug, eine Verkehrszentrale und ein Endgerät
EP1028405A2 (fr) Procédé de transmission d'information relative à un lieu
DE10024183A1 (de) Verfahren zur Zielführung einer Person in Stadtgebieten mittels eines WAP-fähigen Mobilfunknetzes
EP1714261B1 (fr) Procede de decodage, codage et transmission de donnees de route et dispositif de navigation

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

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE CH DE DK ES FI FR GB IT LI LU NL SE

17Q First examination report despatched

Effective date: 20000816

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): AT BE CH DE DK ES FI FR GB IT LI LU NL SE

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

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20020508

REF Corresponds to:

Ref document number: 217434

Country of ref document: AT

Date of ref document: 20020515

Kind code of ref document: T

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REF Corresponds to:

Ref document number: 59707219

Country of ref document: DE

Date of ref document: 20020613

RAP2 Party data changed (patent owner data changed or rights of a patent transferred)

Owner name: T-MOBILE DEUTSCHLAND GMBH

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

Ref country code: DK

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

REG Reference to a national code

Ref country code: CH

Ref legal event code: NV

Representative=s name: PATENTANWALTSBUERO JEAN HUNZIKER

NLT2 Nl: modifications (of names), taken from the european patent patent bulletin

Owner name: T-MOBILE DEUTSCHLAND GMBH

GBT Gb: translation of ep patent filed (gb section 77(6)(a)/1977)

Effective date: 20020812

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

BECN Be: change of holder's name

Effective date: 20020508

NLT1 Nl: modifications of names registered in virtue of documents presented to the patent office pursuant to art. 16 a, paragraph 1

Owner name: T-MOBILE DEUTSCHLAND GMBH

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

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 19

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 20

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

Ref country code: LU

Payment date: 20161221

Year of fee payment: 20

Ref country code: NL

Payment date: 20161221

Year of fee payment: 20

Ref country code: GB

Payment date: 20161222

Year of fee payment: 20

Ref country code: CH

Payment date: 20161222

Year of fee payment: 20

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

Ref country code: AT

Payment date: 20161219

Year of fee payment: 20

Ref country code: BE

Payment date: 20161221

Year of fee payment: 20

Ref country code: FR

Payment date: 20161221

Year of fee payment: 20

Ref country code: IT

Payment date: 20161220

Year of fee payment: 20

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

Ref country code: DE

Payment date: 20161220

Year of fee payment: 20

REG Reference to a national code

Ref country code: DE

Ref legal event code: R071

Ref document number: 59707219

Country of ref document: DE

REG Reference to a national code

Ref country code: NL

Ref legal event code: MK

Effective date: 20171209

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: GB

Ref legal event code: PE20

Expiry date: 20171209

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK07

Ref document number: 217434

Country of ref document: AT

Kind code of ref document: T

Effective date: 20171210

REG Reference to a national code

Ref country code: BE

Ref legal event code: MK

Effective date: 20171210

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 EXPIRATION OF PROTECTION

Effective date: 20171209