EP0883872B1 - Information method and device for mobile subscribers - Google Patents

Abstract

Disclosed is an information method for mobile subscribers, whereby, on request and/or automatically, data are transmitted between a central control unit and a mobile subscriber unit. Also disclosed is an information device for mobile subscribers, encompassing at least one central control unit and a plurality of mobile subscriber units.

Description

The invention relates to a method and an arrangement for route information mobile Participant according to the preamble of claim 1.

Due to the steadily growing volume of traffic, the need for high quality Systems for traffic information and traffic management are becoming increasingly urgent. Surrender However, the problems arise as the user always has current information available can be provided, which also offer a high level of user comfort.

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. In the navigation unit can 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.

This object is achieved by the features of patent claim 1.

Further possible embodiments of the invention are in the dependent ones Claims specified.

In particular, 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.

Therefore, the driver must be made aware of upcoming maneuvers in good time. As a maneuver instruction, it is not sufficient to just perform the maneuver immediately specify (eg "turn right"), but the user must use an abstracted Representation (signposts) informing about the intersection topography at the maneuver point be (see Fig. 1). The appendix contains a proposal for such signage symbols.

The central unit (T-Traffic center) 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. In the Route evaluation becomes a route known in the terminal from the terminal to the head office transfer. In the control center, the route is based on the current traffic situation Estimated travel time and transferred to the terminal.

1.1 Brief description of orientation aid

1. Routenanfrage an die Zentrale

2. Routenberechnung und -aufbereitung, Übertragung der vollständigen Route ins Endgerät

3. Abarbeitung der Route im Endgerät

siehe Fig. 2The orientation guide has the following basic sequence:

1. Route request to the head office

2. Route calculation and preparation, transmission of the complete route to the end device

3. Processing the route in the terminal

see Fig. 2

• seiner Startposition (im Regelfall die aktuelle Position),
• der Zielposition und
• von Optimierungskriterien (z. B. kürzeste oder schnellste Route)

in der Zentrale ab.The customer asks for the route

• his starting position (usually the current position),
• the target position and
• optimization criteria (e.g. shortest or fastest route)

at the headquarters.

In addition, there are points that can be reached on the route (via points). or Points that should not be approached (avoid points) must also be specified.

Various forms are supported for entering the destination address (e.g. city and street, POI: e.g. B. airport, train station).

• Zieleingabe direkt am Endgerät: der Kunde gibt die notwendigen Informationen zur Routenberechnung am EG ein, bzw. ruft sie aus einem vorhandenen Zielespeicher im Endgerät ab.
• Telefonie: hierbei ermittelt die Zentrale (Operator) die oben genannten Informationen zur Routenberechnung im Dialog mit dem Kunden

The route request to the head office can be made via

• Entering a destination directly on the end device: the customer enters the necessary information for route calculation on the ground floor or retrieves it from an existing destination memory in the end device.
• Telephony: the control center (operator) determines the above-mentioned information for route calculation in dialog with the customer

At the head office, the route request is followed by a destination request directly on the end device First, 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.

• eine textuelle Routengrobbeschreibung zur Übersicht über die geplante Route durch den Benutzer,
• die berechnete Gesamtentfernung zum Zielort und die Reisezeit zum Zielort unter Berücksichtigung der aktuellen Verkehrslage sowie
• eine Liste von Wegepunkten mit zugeordneten Icons zur Navigation während der Fahrt.

The route information contains

• a rough textual description of the route to provide an overview of the planned route by the user,
• the calculated total distance to the destination and the travel time to the destination taking into account the current traffic situation and
• a list of waypoints with associated icons for navigation while driving.

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.

1. in einen Kompaß-Mode umschalten, in dem auf dem Bildschirm die Richtung und Entfernung zum nächsten Wegepunkt auf der Route angezeigt wird, oder

2. dem Kunden die Möglichkeit zu einer neuen Routenanfrage bieten.

The terminal can then

1. Switch to a compass mode in which the direction and distance to the next waypoint on the route is shown on the screen, or

2. offer the customer the opportunity to make a new route request.

1.2 Brief description of route evaluation

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).

1.3 Overview of the documents

In this document, 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.

• Interne Dienste - Endgeräteseitige Beschreibung des Dienstablaufs

Cross-service specifications required to understand this specification:

• Internal services - terminal-side description of the service flow

• Anforderungen an den logischen Aufbau einer Lokalisierungsperlenkette für eine Punktlokalisierung
• Beschreibung der diensteübergreifenden Fehlerbehandlung

The following documents are also required to understand this specification:

• Requirements for the logical structure of a localization pearl chain for point localization
• Description of cross-service error handling

• Application Data Protocol Navigation Services
• ADP Message Types of General Interest

The message types listed can be found in the documents:

• Application Data Protocol Navigation Services
• ADP Message Types of General Interest

• Address Coding
• Coding of Text and Transparent Data
• Coding of Extended Location Message
• Area and Location Coding
• Coding of Absolute Time

Guidelines for the coding of special data types can be found in the following documents:

• Address coding
• Coding of Text and Transparent Data
• Coding of Extended Location Message
• Area and location coding
• Coding of absolute time

• Transport Protocol

The transport frame for the message types is defined in:

• Transport Protocol

• CAS Protocol
• ADP Key Management
• Dienstebeschreibung Key Management and Security

Data protection and data security procedures are specified in the documents "Conditional Access and Security (CAS)":

• CAS Protocol
• ADP key management
• Key Management and Security

• Message Type Numbering

The numbering of telegram types corresponds to the document:

• Message Type Numbering

The current version numbers of the listed documents are for each Change passed on to our partners.

2 General processes 2.1 Definitions of terms

• aktive Quittung   aktive Bestätigung des Erhalts einer Message durch den Nutzer
• ADP   Application Data Protocol
• Geo-Code   Eindeutige Festlegung und Identifikation eines geographischen Objektes durch Koordinaten
• Kompaßmode/Homing   reine endgeräteseitige Funktion, bei der ein Pfeil auf dem Display in Richtung einer geographischen Koordinate zeigt (meist mit zusätzlicher Angabe der Entfernung in der Luftlinie)

The following terms are clearly defined for this document:

• active acknowledgment active confirmation that the user has received a message
• ADP Application Data Protocol
• Geo-Code Clear definition and identification of a geographic object using coordinates
• Compass mode / homing pure device-side function, in which an arrow on the display points in the direction of a geographic coordinate (usually with additional indication of the distance in a straight line)

The message types with their contents are described as follows: Information element grade Length [bits] content Description of the field content
eg: Protocol discriminator or position Definition of the field type
MF:
Mandatory, fix length
MV:
Mandatory, variable length
OF:
Optional. Fix length
OV:
Optional, variable length Length of the field
in number of bits for MF or OF
var.
for MV or OV Definition of the content for the use of the services

2.2 Transport protocol - handling

The transport protocol is used as follows to use the orientation aid and route evaluation services: Information element grade Lenght (bits) content Transport Protocol Discriminator MF 8th 00000001 Application ID MF 8th s. Cape. 2.2.1 ADP version MF 7 0000001 (V 1.0) Initiative Flag MF 1 1: for Route Request Message and Travel Time Request Message, for Route Message only if this was initiated by the head office 0: for all subsequent messages Context Number MF 8th MSB = 1: assigned by the terminal MSB = 0: assigned by the control center for route messages initiated by the control center Total number of packets MF 5 Number = X - 1 ⇒ value range 1 ... 32 Index of Actual Packet MF 5 Index = 0 - (X-1) ⇒ value range 1 ... 32 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.

All functions defined within the CAS Protocol document, Procedures and processes are to be supported on the end device.

2.2.1 Service identifier

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.

Application ID 31 h

Orientierungshilfe: Digital Request

Application ID 32h

Orientierungshilfe: Operator Request

Application ID 33 h

Routenbewertung

The following application IDs are assigned:

Application ID 31 h

Orientation guide: digital request

Application ID 32h

Orientation guide: Operator request

Application ID 33 h

route review

2.2.2 Assignment of answers to an inquiry

• Initiative Flag
• Context Number

im Transport-Layer
im Auftrag an die Zentrale vergibt das Verkehrstelematik-Endgerät eine frei wählbare Context Number (Einschränkung: MSB = 1). Mit Initiative Flag = 1 (initiative) wird die erste Transaktion der Kette, der Auftrag, gekennzeichnet.Transactions are assigned using the two fields:

• Initiative Flag
• Context Number

in the transport layer
the traffic telematics terminal assigns a freely selectable context number (restriction: MSB = 1). Initiative Flag = 1 (initiative) marks the first transaction in the chain, the order.

If there is a response to the traffic telematics terminal, its context number is set again. The initiative flag is set to 0 for all associated answers, so that the client can clearly assign the answer to the order placed.

If route messages are not initiated by the terminal, the control center assigns a freely selectable context number (restriction: MSB = 0). The Initiative Flag = 1 (initiative).

2.3 Coding of text

All text elements within the navigation services use the following format: Information element grade Length (bits) content Text representation MF 2 permissible values: 1: Text: 6 bits per character 2: Text ISO 8859-1 (8 bits per character) Length OF 10 Length of the text in number of letters, including control characters Text / Data OV N × 8 text

2.4 Coding of the communication header of the ADPs used

The values for Protocol Discriminator and Message Type are in the document "Message Type Numbering ". The bulk flag is always set to 0

2.5 Time control of the communication processes

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

2.6 Management of service addresses 2.6.1 Orientation guide

The storage and updating of the service addresses in the terminal is in the Telematics service specification Internal services explained.

For the orientation aid service, the terminal must have the full address management Support functionality of internal services.

2.6.2 Route evaluation

The storage and updating of the service addresses in the terminal is in the Telematics service specification Internal services explained

For the route evaluation service, the terminal must have the full address management Support functionality of internal services.

2.7 Service parameters

All service parameters for navigation services are listed below. The of the Central services parameters currently supported are transferred to the end device by internal services loaded. Processes or functions that cannot be parameterized are a binding part of the standard and are supported by all centers.

2.7.1 Processes

32-bit switches are available for parameterizing the processes, which are assigned as follows (0: not supported by the control center, 1: supported by the control center): Procedure according to ADP Switch default Route_Description_Digital Request 1 1 Route_Description_Operator Aided Request_Timer_Based 2 1 Travel_Time_Estimation 3 0 reserved 4 - 32

2.7.2 Functions

64-bit switches are available to parameterize the functions and are assigned as follows. All of the functions listed are to be supported by the end device and are parameterized in a provider-specific manner via the internal services. Function acc. ADP Switch default Route_Request_Message_Starting / Arrival_Time_starting_time
Comment: The control center supports a different time than the actual time as the start time 1 0 Route_Request_Message_Starting / Arrival_Time_arrival_time
Comment: The control center supports the specification of a desired arrival time 2 0 Route_Request_Message_Rouling_Criteria_fastest 3 1 Route_Request_Message_Routing_Criteria_fastest_without_TINFO 4 0 Route_Request_Message_Routing_Criteria_shortest 5 1 Route_Request_Message_Routing_Criteria_user_defined 6 0 reserved 7-18 Route_Request_Message_Routing_Switches_main_roads_preferred 19 0 Route_Request_Message_Routing_Switches_minimize_villages 20 0 Route_Request_Message_Routing_Switches_no_toll_roads 21 0 Route_Request_Message_Avoid_Location
Comment: avoidance points are supported 22 0 reserved 23-26 Route_Request_Message_Number_of_Destinations_final_plus_1 27 1 Route_Request_Message_Number_of_Destinations_final_plus_2 28 0 Route_Request_Message_Number_of_Destinations_final_plus_3 29 0 Route_Request_Message_Number_of_Destinations_final_plus_4 30 0 Route_Request_Message_Number_of_Destinations_final_plus_5 31 0 Route_Request_Message_Number_of_Destinations_final_plus_6 32 0 Address_Kind_of_POI_Service_Provider_POI Comment: Service provider POIs are supported 33 1 Address_request_phone_numbers_accepted
Comment: Telephone numbers for address requests are supported 34 0 The use of the area code for a location selection is supported. 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 Address_request_Geo_Codes_accepted
Comment: Geo codes for address requests are supported 36 0 reserved 37-64

3 Description of the services 3.1 Orientation guide

1. Routenanfrage (im Fehlerfall folgt eine Error Message)

2. Routenberechnung und Aufbereitung in der Zentrale/Übertragung ins Endgerät (Route Message)

3. Abarbeitung der Route im Endgerät

The orientation guide has the following basic sequence:

1. Route request (an error message follows in the event of an error)

2. Route calculation and preparation in the control center / transmission to the end device (route message)

3. Processing the route in the terminal

In addition, it will be possible in the future that the customer via the operator or z. B. 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.

3.1.1 Route request

• Zieleingabe direkt am Endgerät: der Kunde gibt die notwendigen Informationen zur Routenberechnung am EG ein (insbesondere Adressinformationen)
• Operator (Sprachverbindung): hierbei ermittelt der Operator die oben genannten Informationen zur Routenberechnung im Dialog mit dem Kunden

The route request to the head office can be made via

• Destination input directly on the end device: the customer enters the necessary information for route calculation on the ground floor (especially address information)
• Operator (voice connection): the operator determines the above information for route calculation in dialog with the customer

• Startpunkt/Adresse (Generierung im Regelfall automatisch durch das Endgerät: aktuelle Position): Lokalisierungs-Perlenkette oder postalische Adressebeschreibung (mandatory)
• Zieladresse: Geographische Koordinate und/oder postalische Adressbeschreibung (darf nur bei einer Operatoranfrage fehlen)
• gewünschte Abfahrtzeit oder gewünschte Ankunftszeit, diese Informationen werden bei der Routenberechnung auf Basis der aktuellen Verkehrslage mit berücksichtigt (die Unterstützung dieser Funktionalität ist parametrierbar, s. Kapitel 2.7).

As part of the route request, the following information must be provided or automatically generated by the end device:

• Starting point / address (usually generated automatically by the end device: current position) : localization pearl string or postal address description (mandatory)
• Destination address: Geographical coordinate and / or postal address description (may only be missing if there is an operator request)
• Desired departure time or desired arrival time, this information is taken into account in the route calculation based on the current traffic situation (the support of this functionality can be parameterized, see chapter 2.7).

• die Kriterien zur Routenberechnung (die Unterstützung der einzelnen Kriterien ist parametrierbar, s. Kapitel s. Kapitel 2.7:
  • schnellste Route mit Berücksichtigung der aktuellen Verkehrslage (wird als Default-Vorgabe für das Endgerät empfohlen),
  • schnellste Route ohne Berücksichtigung der aktuellen Verkehrslage,
  • kürzeste Route (ohne Berücksichtigung der aktuellen Verkehrslage),
  • benutzerdefiniert (anhand von in der Zentrale hinterlegten Kriterien; die Kriterien-Hinterlegung erfolgt über Customer Care, nicht über das Endgerät),
    sowie den zusätzlichen Wahlmöglichkeiten
  • Bevorzugung von Fernstraßen,
  • Minimierung von Ortsdurchfahrten,
  • keine Straßen mit Maut-Pflicht
• sowie bis zu 6 zusätzlichen Adressen, die je nach Wahl des Kunden entweder angefahren werden müssen (Via-Punkte) oder nicht angefahren werden dürfen (Meide-Punkte): Geographische Koordinate und/oder postalische Adressbeschreibung (die Anzahl der möglichen Adressen ist parametrierbar, siehe s. Kapitel 2.7)). Bei Via-Punkten werden die Adressen in der vorgegebenen Reihenfolge abgefahren, d.h. es wird kein Traveling Salesman-Problem gelöst.

The "desired departure time" transmitted from the terminal to the control center is initially ignored by T-Traffic.

• the criteria for route calculation (the support of the individual criteria can be parameterized, see chapter see chapter 2.7:
  • fastest route taking into account the current traffic situation (recommended as default for the end device),
  • fastest route without taking into account the current traffic situation,
  • shortest route (without taking into account the current traffic situation),
  • user-defined (based on criteria stored in the head office; the criteria are stored via Customer Care, not via the end device),
    as well as the additional options
  • Preference for highways,
  • Minimization of local passages,
  • no toll roads
• as well as up to 6 additional addresses which, depending on the customer's choice, must either be approached (via points) or not permitted (avoid points): geographic coordinate and / or postal address description (the number of possible addresses can be parameterized, see see chapter 2.7)). With Via points, the addresses are traversed in the specified order, ie no traveling salesman problem is solved.

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).

• Telefonnummer des Benutzers (optional):Dieses Feld ist dann mit der Telefonnummer des Empfängers der Route auszufüllen, wenn die Routenanfrage fremdinitiiert wird.
• Informationen über das Endgerät (muß übertragen werden, ausgewertet wird die Information über die Ortung)
• sowie in zukünftigen Diensteausprägungen Informationen über das Fahrzeug.

In the Route_Request_Message the following additional user-specific information is transmitted to the control center:

• Telephone number of the user (optional): This field is to be filled in with the telephone number of the recipient of the route if the route request is initiated externally.
• Information about the end device (must be transmitted, the information about the location is evaluated)
• as well as information about the vehicle in future service versions.

3.1.1.1 Entering a destination on the end device

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.

• Abspeicherung einer innerhalb einer Route-Message erhaltenen Adresse (inklusive geographischer Koordinaten)
• Abspeicherung einer durch einen Auskunftsdienst erhaltenen Adresse (Service-Provider-POI)
• Positionsspeicherung: Der Kunde kann am Endgerät seine aktuelle Position (geographische Koordinate), ergänzt um zusätzliche Adressinformationen, im Adreßbuch speichern (z. B. Heimatadresse).

The address memory (address book) should be filled in the following ways:

• Storage of an address received within a route message (including geographic coordinates)
• Storage of an address received by an information service (service provider POI)
• Position storage: The customer can save his current position (geographical coordinate), supplemented by additional address information, in the address book (e.g. home address) on the end device.

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.

If the address or individual details are not clear, the error message is transmitted to the vehicle. This can contain selection lists. The support of the error message depends on the service provider.

1. geographische Koordinaten (alle anderen angegebenen Felder werden zentraleseitig ignoriert)

2. Geo-Codes (alle anderen Felder werden zentraleseitig ignoriert)

3. Service-Provider-POI: die vollständige bei einer Adreßabfrage über Auskunftsdienste erhaltene Adreßinformation muß übertragen werden (Ausnahme: "additional information" und "country"). Service-Provider-POI können über Auskunftsdienste (s. Kapitel 3.2.2) ins Endgerät geladen und ggf. im Adreßbuch gespeichert werden.

4. MAP-POI mit Ortswahl (Straßenbeschreibung und POI-Name wird ignoriert): Bei mehreren in Frage kommenden POI's wird der nächstliegende POI ausgewählt (ggf. wird auch eine Auswahlliste übertragen).

5. MAP-POI ohne Ortswahl: Die Zentrale wählt als Default den nächstliegenden POI dieses Typs aus (bezogen auf die mitübertragene Startadresse). Straßenbeschreibung und POI-Name werden ignoriert.

6. Ortswahl und Straßenname: Der Straßenname muß entweder als "Street Identification" oder als "Street Name incl. House Number" übertragen werden. Werden beide übertragen, wird die Street Identification ignoriert. Es wird empfohlen, die Street Identification nicht für eine Adreßanfrage zu verwenden.

7. nur Ortswahl (Default s.u.)

8. vollständige Telefonnummer: Ortsvorwahl und Teilnehrnernummer müssen übergeben werden. Die Landeskennziffer ist optional.

The following address requests are accepted:

1. Geographic coordinates (all other specified fields are ignored at the central site)

2. Geo-Codes (all other fields are ignored at the central site)

3. Service provider POI: the complete address information received when an address is requested via information services (exception: "additional information" and "country"). Service provider POIs can be loaded into the end device via information services (see Chapter 3.2.2) and saved in the address book if necessary.

4. MAP POI with location selection (street description and POI name is ignored): If there are several POIs in question, the closest POI is selected (a selection list may also be transferred).

5. MAP-POI without location selection: The control center selects the nearest POI of this type as a default (based on the start address also transmitted). Street description and POI name are ignored.

6. Place selection and street name: The street name must either be transferred as "Street Identification" or as "Street Name incl. House Number". If both are transmitted, the street identification is ignored. It is recommended not to use street identification for an address request.

7. only location selection (default see below)

8. Complete telephone number: Area code and subscriber number must be transferred. The country code is optional.

• nur Ortsname (Default: Ortsmittelpunkt)
• nur Postleitzahl (Default: Zentrum des PLZ-Bezirks)
• nur Telefon-Ortsvorwahl (Default: Zentrum des Ortsvorwahlbereiches)
• Ortsname und Telefon-Ortsvorwahl oder Postleitzahl

The following options are permitted for the location selection:

• only place name (default: center of place)
• Postcode only (default: center of the postcode district)
• Telephone area code only (default: center of the area code area)
• Place name and telephone area code or zip code

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.

The "Additional Information" as well as the "Country" field is always included in the address request ignored. If the "State" field is empty, Germany (D) is taken as the country.

• geographische Koordinaten nach der Digitalen Karte in der Zentrale. Bei bloßer Angabe von Koordinaten können Start und Ziel im Rahmen der Ungenauigkeiten vom Kundenwunsch abweichen.
• Ortsnamen nach dem offiziellen Ortsnamen. Gibt es mehrere Orte gleichen offiziellen Namens, wird zur Identifizierung die Postleitzahl oder die Ortsvorwahl herangezogen. Ortsnamen sowie Namen von Autobahnanschlußstellen können mit Bindestrich übergeben werden (z. B. Köln-Lindenthal, Bonn-Bad Godesberg). Werden im überregionalen Sprachgebrauch auch nur die Namen der Vororte verwendet (z. B. Wattenscheid, Bad Godesberg), werden auch diese von der Zentrale akzeptiert.
• Straßenbezeichnungen: Straßentypen BAB, Bundesstraße, Landstraße, Staatsstraße, Kreisstraße, Europastraße mit Nummer und eventueller zusätzlicher Bezeichnung (a,b,n,r), z. B. B55n (s. ADP).
• Straßennamen nach dem offiziellen ortsabhängigen Straßenverzeichnis.
• Postleitzahlen nach dem Postleitzahlenverzeichnis der Deutschen Bundespost.
• POI-Typ: MAP-POI's Zentrum, Bahnhof, Flughafen so wie sie in der Digitalen Karte der Zentrale verzeichnet sind. Service-Provider-POI's werden im Rahmen der Auskunftsdienste beschrieben.
• Staat nach Liste der internationalen Kfz-Zeichen.
• Telefonummer: nur Vorwahl (Länderkennziffer ist Kannfeld, default: Deutschland).

The following requirements apply to the individual IEs:

• Geographic coordinates according to the digital map in the headquarters. If coordinates are only given, the start and finish may differ from the customer's request due to the inaccuracies.
• Place names after the official place name. If there are several places with the same official name, the postcode or area code is used for identification. Place names and names of motorway junctions can be passed with a hyphen (e.g. Cologne-Lindenthal, Bonn-Bad Godesberg). If only the names of the suburbs are used in national language (e.g. Wattenscheid, Bad Godesberg), these are also accepted by the head office.
• Street designations : BAB, Bundesstraße, Landstraße, Staatsstraße, Kreisstraße, Europastraße with number and any additional designation (a, b, n, r), e.g. B. B55n (see ADP).
• Street names according to the official location-dependent street directory.
• Postcodes according to the postcode directory of the Deutsche Bundespost.
• POI type: MAP-POI's center, train station, airport as they are shown in the digital map of the headquarters. Service provider POIs are described as part of the information services.
• State according to list of international license plates.
• Telephone number: Area code only (country code is Kannfeld, default: Germany).

• gleichzeitig Angabe geographischer Koordinaten und Geo-Code
• gleichzeitig Angabe geographischer Koordinaten und Service-Provider-POI
• nicht interpretierbare geographische Koordinaten, Geo-Codes oder Service-Provider-POI
• nicht interpretierbare Telefonortsvorwahl oder Postleitzahl
• nicht interpretierbare vollständige Telefonnummer

In the following cases, an error message "start / destination / additional address not identified" follows (the corresponding bit in the error message is set):

• simultaneous indication of geographic coordinates and geo-code
• at the same time specification of geographic coordinates and service provider POI
• Geographical coordinates, geo codes or service provider POIs that cannot be interpreted
• Telephone area code or postcode that cannot be interpreted
• Full telephone number that cannot be interpreted

In addition, the control center can use the bit "start / desination / additional address ambiguous ". In this case, 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).

• Ortsname: Auswahlliste mit max. 5 Alternativen
• Straßenname: Auswahlliste mit max. 5 Alternativen
• MAP-POI: Auswahlliste mit max. 5 Alternativen

If the address information regarding the choice of location, a MAP-POI, or a street name is not clear, selection lists are transferred to the vehicle with the error message according to the following criteria, whereby the selection list only contains the IE's to be specified (ie no complete address fields, exceptions are mentioned ):

• Place name: selection list with max. 5 alternatives
• Street name: selection list with max. 5 alternatives
• MAP POI: selection list with max. 5 alternatives

The coding of the individual IE's is detailed in the ADP for the navigation services described.

3.1.1.2 Request via operator (Speech Connection)

1. Es wird mit der Operatoranfrage eine Route_Request_Message versandt, die zumindest die Startposition enthält.

2. Der Kunde wählt direkt den Operator an (auch über andere Telefone möglich). In diesem Fall muß er dem Operator auch seine Startposition mitteilen. Das Endgerät erhält eine nicht von ihm initiierte_Route_Message und interpretiert diese.

There are two basic cases when requesting an operator:

1. A route_Request_Message is sent with the operator request, which contains at least the start position.

2. The customer dials the operator directly (also possible via other telephones). In this case, he must also inform the operator of his starting position. The terminal device receives a route_message that it has not initiated and interprets it.

Below is the first case of an operator request with a transfer Route_Message described. This should be viewed as a separate service, which is a separate one Service ID received.

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 possible processes for establishing the voice connection are shown in Section 3.3.2. Receiving an error message interrupts the establishment of the voice connection, if this has not yet been set up (with the timer-based process).

There are preferably the following additional requirements for the request:

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.

During the voice connection, 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.

3.1.2 Route calculation and preparation

In the control center, 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.

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.

Certain road classes are used for route calculation for devices with pure GPS or even excluded individual streets. This can lead to detours. in principle a positioning accuracy of approx. 100 m is assumed for these end devices.

In addition, a more detailed rough route description is provided for devices with pure GPS generated.

After consultation with the manufacturers, devices with a digital map (navigation systems) a detailed rough route description can be generated. The list of Guide symbols in the navigation systems should be reduced to a level that is necessary for a vehicle-autonomous route fine calculation based on this.

3.1.3 Processing the route in the end device

• eine textuelle Routengrobbeschreibung zur Übersicht über die geplante Route durch den Benutzer (Route Briefing)
• die berechnete Reisezeit zum Zielort und die Gesamtentfemung zum Zielort (Routenlänge) unter Berücksichtigung der aktuellen Verkehrslage.
• eine Liste von Wegepunkten mit zugeordneten Icons zur Navigation während der Fahrt

The Route_Message can contain the following information:

• a textual rough route description to provide an overview of the planned route by the user (route briefing)
• the calculated travel time to the destination and the total distance to the destination (route length) taking into account the current traffic situation .
• a list of waypoints with associated icons for navigation while driving

There will be special cases where the route description remains empty or no waypoints are included.

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

There should be breaks when updating the calculated arrival time while driving are taken into account (detection by switching off the device).

In addition, it is recommended that if the actual travel time from the transmitted date is exceeded completed travel time of more than 30% and at least 10 minutes the user about it to inform and offer him the possibility of a new route request.

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.).

1. Die textuelle Routengrobbeschreibung wird angezeigt und vom Kunden quittiert.

2. Ein Pfeil zeigt in Richtung auf den ersten Wegepunkt (Kompaßmode). Zusätzlich wird die Entfernung (Luftlinie) zu diesem Wegepunkt mit angezeigt.

3. Wird der Wegepunkt erreicht, wird dieser als passiert markiert und der nächste Wegepunkt wird mit der aktuellen Entfernung zu diesem Wegepunkt (Fahrstrecke) angezeigt.

4. Nach dem Passieren des letzten Wegepunktes wird dies dem Kunden angezeigt. Gleichzeitig zeigt ein Pfeil in Richtung des Zielortes (mit Entfernungsangabe in Luftlinie; Kompaßmode).

The outline of the guidance is as follows:

1. The rough textual route description is displayed and acknowledged by the customer.

2. An arrow points towards the first waypoint (compass mode). The distance (beeline) to this waypoint is also shown.

3. When the waypoint is reached, it is marked as passed and the next waypoint is displayed with the current distance to this waypoint (route).

4. After passing the last waypoint this will be shown to the customer. At the same time, an arrow points in the direction of the destination (with distance as the crow flies; compass mode).

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.

• Geographische Koordinate
• wenn POI: POI-Typ und POI-Name
• Straßenbeschreibung (nicht bei Map-POI's)
• Ortsbezeichnung

The start and destination addresses are always only transmitted with the following information, whereby individual optional fields are not transmitted if they were already included in the request with the same content:

• Geographic coordinate
• if POI: POI type and POI name
• Street description (not with map POIs)
• place name

If the first waypoint is not identical to the start address, this is indicated with the type of the start waypoint also communicated. 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.

1. Die Ortsmitte wird als Bezugspunkt gewählt bzw. bei POI's die nächst mögliche Koordinate

2. Ist der Punkt nicht erreichbar (z. B. in einer Fußgängerzone), dann wird zentraleseitig ebenfalls eine in der Nähe liegende Koordinate zugeordnet.

If an exact geographical coordinate cannot be assigned to the destination address on the digital map in the head office, the assignment to a coordinate is carried out on the central side according to the following principle (specified in the type of the destination address):

1. The center of the town is chosen as the reference point or, for POIs, the next possible coordinate

2. If the point cannot be reached (eg in a pedestrian zone), a coordinate located nearby is also assigned on the central side.

Upon receipt of the telegram with the 1st waypoint, the processing of the Route started, i.e. there is no need to wait until the complete route in Device arrives.

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 Kreuz Köln Süd, A4 to Kreuz Köln Ost, A1 to Kreuz Köln Nord, A57 to Kreuz Kaarst). The milestones are transmitted either as text or as geo-code. A mix of text and geo-codes is possible.

3.1.3.1 Contents of the waypoints

• geographische Koordinate des Wegepunktes (WGS84)
• optional die offizielle Straßenbezeichnung: für die Straße, in die abgebogen werden soll (wird im Regelfall angegeben)
• der Ortsname: Der Ortsname wird im Regelfall übertragen.
• eine Flag, welches gesetzt ist, wenn die Route bis zum nächsten Manöverpunkt auf Autobahnen bzw. autobahnähnlichen Straßen verläuft. Das gesetzte Flag gibt den Hinweis darauf, daß eine frühzeitige Signalisierung des nächsten Manövers vorgenommen werden sollte.

The individual waypoints have the following content:

• geographical coordinate of the waypoint (WGS84)
• optional the official street name : for the street into which you should turn (usually given)
• the place name: The place name is usually transmitted.
• a flag , which is set when the route runs to the next maneuver point on highways or highway-like roads . The flag set indicates that the next maneuver should be signaled early.

• eine abstrahierte Darstellung (lcons) der Kreuzung. Dabei werden 4 verschiedene Kreuzungstypen unterschieden
  • keine Kreuzung (der Wechsel eines Straßen- oder Ortsnamens wird übertragen)
  • sternförmige Kreuzung mit bis zu 8 möglichen Ein-/Ausfahrten
  • Kreisverkehr mit bis zu 8 Ein-/Ausfahrten
  • Autobahnausfahrten mit bis zu vier Abfahrtsmöglichkeiten pro Abfahrtsrichtung. Alle Darstellungen beziehen sich auf die Fahrtrichtung entsprechend der Routenbeschreibung. Die jeweilige Ausfahrtstraße ist gekennzeichnet. Ein Wendemanöver wird in der sternförmigen Kreuzung als Stern mit der Codierung Einfahrtsstraße = Ausfahrtstraße gekennzeichnet. Die Kreuzungstypen Stern und Kreis können als "Moving Map" dargestellt werden. Dazu können Angaben zum Winkel zwischen Fahrtrichtung (= Einfahrtsstraße), Ausfahrtsstraße und gegen Norden enthalten sein.
• ein Hinweis (wenn link flag= 1) darauf, daß 2 Manöver so dicht aufeinander folgen, daß sie zusammengefaßt und als eine Anweisung ausgegeben werdeg sollten. Das link flag wird im ersten der beiden zusammenzufassenden Wegepunkte gesetzt. Zwei aufeinanderfolgende Wegepunkte mit gesetztem link flag sind nicht zulässig.
• die geschätzte Fahrzeit zum nachfolgenden Wegepunkt (wird nur dann nicht übertragen, wenn im selben Wegepunkt das Link-Flag gesetzt ist).
• die Weglänge zum nachfolgenden Wegepunkt (wird nur dann nicht übertragen, wenn im selben Wegepunkt das Link-Flag gesetzt ist).
• ein optionaler Aktionshinweis, der unterstützende Informationen zum Manöver in Textform enthält (z.B. Richtung Köln, Achtung: Enge Kurve).
• optional die Angabe einer Korrridorbreite. Die Korridorbreite definiert zusammen mit der Länge der Luftlinie zum nächsten Wegpunkt (zu errechnen aus den WGS-84-Koordinaten) ein rechteckiges Bezugsgebiet. Dieses Bezugsgebiet wird zur Fehlfahrtenerkennung verwendet. Verläßt der Kunde das Bezugsgebiet, wird die Fehlfahrt erkannt Zusätzlich kann das Bezugsgebiet zur Selektion von routenrelevanten Verkehrsinformationen eingesetzt werden (s. Kapitel 3.2.1).
• optional die Anzahl der Kreuzungen bis zum nachfolgenden Manöverpunkt sowie die Entfernung zur nächsten Kreuzung: Wenn es aufgrund des Straßenverlaufs sinnvoll erscheint, wird die Anzahl der Kreuzungen bis zum nächsten Manöverpunkt übertragen. Dies ermöglich es in Verbindung mit dem nächsten Manöverpunkt, dem Kunden eine zusätzliche Information zu geben (z. B. "6. Kreuzung links").

If the flag is set, the motorway exits are coded with geo-codes. The terminal can take the information about the next exit and the distance to it from the geo-code table and display it.

• an abstracted representation (icons) of the crossing. There are 4 different types of crossings
  • no intersection (the change of a street or place name is transmitted)
  • star-shaped intersection with up to 8 possible entrances / exits
  • Roundabout with up to 8 entrances / exits
  • Motorway exits with up to four departure options per direction of departure. All representations refer to the direction of travel according to the route description. The respective exit road is marked. A turning maneuver is marked in the star-shaped intersection as a star with the code entry road = exit road. The intersection types star and circle can be displayed as a "moving map". This can include information about the angle between the direction of travel (= entrance road), exit road and towards the north.
• a hint (if link flag = 1) that 2 maneuvers follow each other so closely that they should be summarized and issued as one instruction. The link flag is set in the first of the two waypoints to be combined. Two consecutive waypoints with the link flag set are not permitted.
• the estimated travel time to the next waypoint (will not be transmitted if the link flag is set in the same waypoint).
• the path length to the next waypoint (is only transmitted if the link flag is set in the same waypoint).
• an optional action note that contains supporting information on the maneuver in text form (e.g. towards Cologne, attention: tight curve).
• optionally the specification of a corridor width . The corridor width together with the length of the air line to the next waypoint (calculated from the WGS-84 coordinates) defines a rectangular reference area. This reference area is used to identify incorrect journeys. If the customer leaves the reference area, the wrong journey is recognized. In addition, the reference area can be used to select route-relevant traffic information (see Chapter 3.2.1).
• Optionally, the number of intersections to the next maneuver point and the distance to the next intersection : If it makes sense due to the course of the road, the number of intersections to the next maneuver point is transmitted. In connection with the next maneuvering point, this enables the customer to be given additional information (eg "6th intersection on the left").

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 % %

If the link flag is set, the type of intersection of the first waypoint is decisive for the interpretation rule.

If the link flag is set and the intersection type star, 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.

If the type of intersection with a link flag of the type roundabout or motorway exit, then no icon coding is transmitted in the second waypoint, but it becomes one specified second geographic coordinate to support the icon display in the terminal (see above).

In the appendix is a suggestion for possible icon representations as well as for a suitable one Display behavior included.

lack trips

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 (because another waypoint to next waypoint) should be explicitly acknowledged by the user. Ideally 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.

3.2 Connection to other services 3.2.1 Traffic information service

The IE "Street Identification", which is used in the services traffic information and Navigation / orientation aid is used, allows new, Traffic disturbances occurring during the journey in relation to the current route. 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.

Those used for the navigation services and in the traffic information services Street names are identical. 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).

In addition, it is taking advantage of the by the wrong-way corridor and the waypoints spanned reference area possible to eliminate the traffic reports which are not lying on the route. This happens because only traffic reports are selected where, in addition to the street name, the geo-codes in the reference area lie (see Fig. 4). The rectangle side spanned by the distance of the waypoints should be extended by 1km on both sides to ensure that the overlap of the Corridors leads to a selection of all traffic information relating to the route.

In exceptional cases, 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).

The proposed use of those provided within the navigation service Route information and the reference area in connection with the traffic information service is a pure terminal feature, which is represented by the Compatibility of services is enabled.

3.2.2 Information service

Each service provider can freely assign numbers for service provider POIs Assign individual POI types (e.g. petrol stations, ATMs).

In the context of navigation services, 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).

In the service specification and the associated ADP for the information services describes how a service provider POI can be loaded.

3.3 Communication processes

All bidirectional communication processes are shown in the ADP of the navigation services.

An inquiry from the head office is considered complete when the desired answer (Route_Message, Travel_Time_Estimation) or the Error_Message was sent. contains the Error_Message a selection list, with the help of which the customer specifies his request a subsequent request with a unique address is still considered complete new process evaluated.

3.3.1 Digital request

The request to the control center is only the route request message (no operator, see Fig. 5).

• TNAVa (wird mit Empfang der Delivery Notification gestartet)

The following timers are used:

• TNAVa (starts upon receipt of the delivery notification)

When the route message or error message is sent, the process is centralized completed.

3.3.2 Operator-assisted requests

An operator request within the meaning of this specification is always accompanied by a route request Message started. Operator requests without route request message (see chapter 3.1.1.2) are to be treated like inquiries initiated by third parties.

In the case of an operator request with a route message, 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.

3.3.2.1 Timer-based (MO)

After a timer has expired, the terminal sets up the voice connection to the operator (FIG. 6).

• TNAVa (wird mit Absenden der Route_Request_Message gestartet)
• TNAVb (wird mit Empfang der Delivery Notification für die Route_Request_Message gestartet)
• TNA Vc (wird mit Empfang der Delively Notification für die Route_Request_Message gestartet)

The following timers are used:

• TNAVa (starts with sending the Route_Request_Message)
• TNAVb (starts with receipt of the delivery notification for the Route_Request_Message)
• TNA Vc (starts with receipt of the Delively Notification for the Route_Request_Message)

When the route message or error message is sent, the process is centralized completed.

3.3.3 Route messages initiated by others

In addition to the communication processes shown, the terminal must be able to process Route_Messages that it did not initiate (FIG. 7). Such 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.

3.4 Route evaluation

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 process is as follows (see Fig. 8, see also ADP navigation services):

• Anzahl der Wegeleitpunkte zur Routenbeschreibung,
• Geogaphische Koordinate und/oder offizielle Straßenbezeichung/Straßenname, Kreuzungen werden dabei genauso wie bei der Adresseingabe am Endgerät bei der Routenanfrage beschrieben codiert.
• Grobe Himmelsrichtung, die nach dem Erreichen des Wegepunktes gefahren wird (nicht beim Zielwegepunkt).
• optional benutzerspezifische Informationen (Telefonnummer; Angaben zum Endgerät werden ignoriert). Von der Zentrale wird eine übertragene Telefonnummer als die Zieladresse der Travel_Time_Estimation interpretiert. Dieses Feld ist insbesondere dann mit der Empfängertelefonnummer der Route auszufüllen, wenn die Route an ein anderes Endgerät als das absendende Endgerät gesendet werden soll.

The Travel_Time_Request_Message has the following content:

• Number of route guidance points for route description,
• Geographic coordinates and / or official street name / street name, intersections are coded in the same way as when entering the address on the end device when the route request is described.
• Rough cardinal direction, which is driven after reaching the waypoint (not at the destination waypoint).
• optional user-specific information (telephone number; information about the end device is ignored). A transmitted telephone number is interpreted by the head office as the destination address of the Travel_Time_Estimation. This field is to be filled in with the recipient's telephone number of the route in particular if the route is to be sent to a different terminal than the sending terminal.

• TNAVd (wird mit Absenden der Travel Time Request Message gestartet)

The following timers are used:

• TNAVd (started with sending the Travel Time Request Message)

When the Travel Time Message or the Error Message is sent, the Process ended.

The coding of the individual IE'S is detailed in the ADP for the navigation services described.

3.5 Error handling

The service-specific error messages are defined in the ADP. Services Cross Errors (e.g. communication errors) are described in the document "Description of the cross-service error handling ".

If no additional explanations are given in this document, service-specific error messages are to be interpreted as follows: Error Type Explanation / Meaning input error s. Cross-Service Error Handling Description Document server timed out s. Cross-Service Error Handling Description Document server error s. Cross-Service Error Handling Description Document server overloaded s. Cross-Service Error Handling Description Document on treatment If a quick response to the request is not possible due to the current overload of the server, this error message will be sent. The calculated route will be forwarded at a later time. start not identified s. Chapter 3.1.1.1 destination not identified s. Chapter 3.1.1.1 start ambiguous s. Chapter 3.1.1.1 destination ambiguous s. Chapter 3.1.1.1 route not identified It was not possible to calculate a route based on the criteria passed. further requests not possible s. 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. Cross-Service Error Handling Description Document order ignored: previous order is still being processed s. Cross-Service Error Handling Description Document

4 Requirements for the end devices 4.1 Communication

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.

4.2 Location

The end device should have dead reckoning.

Only then can the end device send a localization chain to the head office as the start address send if a sufficiently precise localization is guaranteed. To switch on the To enable a quick initialization or target request to the end device should always be last track before switching off be stored in the device.

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.

4.3 MMI

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

4.4 Storage

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.

If the end device cannot save all waypoints due to a lack of storage space, then except for the destination address, all waypoints that are no longer saved should be discarded could become. The customer must be informed that waypoints have been discarded are. After reaching the last saved waypoint of the route is in the Switch compass mode to the target. It is recommended to the customer in good time to give the opportunity to reach the last saved waypoint before reaching to make a new route request to the destination.

4.5 Other requirements

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).

4.6 Suggestions for signage symbols

As already explained in the introduction, 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.

Therefore, the driver must be made aware of upcoming maneuvers in good time. As a maneuver instruction, it is not sufficient to just perform the maneuver immediately to specify (e.g. turn right), but the user must use a abstracted representation of the intersection topography at the maneuver point become.

In the case of maneuvers or complex intersections that follow one after the other, they must do so Users are represented at the same time (i.e. in a symbol) because this is their perception of the maneuver in reality and its ability to react. The abstract from two icons to one symbol is indicated by the link flag.

The following suggestions are made for the latest time that the signpost symbol is displayed (the display should be accompanied by an acoustic warning): with dead reckoning without dead reckoning Highway: 1,500 m 1,500 m country road 500 m 500 m City (without city motorways) 50 m 100 m

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).

1. Sternförmige Kreuzung (junction)

2. Kreisverker (roundabout)

3. Autobahnausfahrt/Füßler (fork) Durch Einsatz des link flags beim Typ "junction" wird der zusätzliche Typ

4. Doppelkreuzung/Versatz

dargestellt.The proposed routing symbolism is based on four types of intersection, three of which are coded as basic types and transmitted to the vehicle:

1. Star-shaped junction

2nd circular anchor (roundabout)

3. Autobahn exit / Füßler (fork) By using the link flag in the "junction" type, the additional type

4. Double crossing / offset

shown.

The following are suggestions for the screen display of the individual intersection types made. The display is based on a display with at least 128 x 112 pixels.

1. Sternförmige Kreuzung (junction) s. Fig. 9a

2. Kreisverkehr (roundabout) s. Fig. 9b

3. Autobahnausfahrt/Füßler (fork) s. Fig. 9c

4. Doppelkreuzung/Versatz (aus junction mit link flag)

Geradeaus aufeinanderfolgende Kreuzungen s. Fig. 9d
schräger Versatz s. Fig. 9e
rechtwinkliger Versatz s. Fig. 9fIn addition, the distance to the first maneuvering point and the name of the street into which you should turn should be displayed.

1. Star-shaped junction. Fig. 9a

2. Roundabout s. Fig. 9b

3. Autobahn exit / Füßler (fork) s. Fig. 9c

4. Double crossing / offset (from junction with link flag)

Straight ahead intersections s. Fig. 9d
oblique offset s. Fig. 9e
right-angled offset s. Fig. 9f

Claims (11)

1. Method for providing route information to mobile subscribers, whereby, on request or automatically, data are transmitted between a central unit and a mobile subscriber unit, as follows: a route request is passed from the subscriber unit to the central unit, a route calculation and data editing are carried out in the central unit, and the complete route information is transmitted into the subscriber unit, in which processing of the route information is carried out; the route information is read out in the subscriber unit by means of an input-output unit, in the form of a textual route briefing and a calculated total distance and journey time to destination taking the present traffic situation into account, and comprises a list of way points identifying manoeuvre points for giving the mobile subscriber timely prompts of forthcoming manoeuvres; and he is informed by an icon of the topography of the road junction and the manoeuvres to be made at the manoeuvre point; characterized in that a reference zone with a specific corridor width is defined between the individual way points and is used for detection of straying from the route and for selection of traffic information relevant to the route.
2. Method according to Claim 1, characterized in that the route request is passed by input at the subscriber unit or by voice connection with an operator.
3. Method according to either of Claims 1 and 2, characterized in that the route calculation based on a route request is carried out in the central unit with the help of the following data: starting-point, destination address, and desired departure time or arrival time.
4. Method according to Claim 1, characterized in that the list of way points is transmitted with the following contents:

   the geographical coordinates of the way point;

   the place name;

   an icon of the junction in the form of a direction sign; and

   one or more flags.
5. Method according to either of Claims 3 and 4, characterized in that four possible junction types can be displayed by the input/output unit in the form of direction signs:

   radial junction;

   roundabout;

   motorway exit or fork; and

   double or staggered junction.
6. Method according to any one of Claims 1 and 3 to 5, characterized in that the list of way points is transmitted with the following additional contents:

   the official identification of the road to be taken;

   the estimated journey time to the next way point;

   the distance to be covered to the next way point;

   an action flag;

   the width of the corridor defining a reference zone; and

   the number of junctions to the next manoeuvre point, together with the distance to the next junction.
7. Method according to any one of Claims 1 to 6, characterized in that as an additional service an evaluation is made of any desired route logged in the subscriber unit and transmitted to the central unit as to the probable journey time based on the present traffic situation, the computed journey time then being transmitted to the subscriber unit.
8. Method according to any one of Claims 1 to 7, characterized in that communication between the subscriber unit and the central unit is conducted via the short message service of a GSM communication network.
9. Method according to any one of Claims 1 to 7, characterized in that a GPS receiver is used to determine the position of the subscriber unit.
10. Method according to any one of Claims 1 to 8, characterized in that an input/output unit in the form of a graphic display is used.
11. Method according to any one of Claims 1 to 10, characterized in that an input/output unit with a voice output device is used.

Images