EP0883872A1 - Verfahren und anordnung zur information mobiler teilnehmer - Google Patents
Verfahren und anordnung zur information mobiler teilnehmerInfo
- Publication number
- EP0883872A1 EP0883872A1 EP97952715A EP97952715A EP0883872A1 EP 0883872 A1 EP0883872 A1 EP 0883872A1 EP 97952715 A EP97952715 A EP 97952715A EP 97952715 A EP97952715 A EP 97952715A EP 0883872 A1 EP0883872 A1 EP 0883872A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- route
- message
- information
- request
- service
- 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.)
- Granted
Links
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
- data can be related to various output parameters, e.g. Location, start or destination information or route information of the trip, central or terminal-side queries that can be carried out with the aid of devices or people.
- output parameters e.g. Location, start or destination information or route information of the trip, central or terminal-side queries that can be carried out with the aid of devices or people.
- the data transfers can too
- the navigation services support the customer when driving to his destination on a route.
- the route is calculated taking the current traffic situation into account in the service center.
- the orientation guide described in this document is a simple navigation service that guides customers to their destination with limited wrong way detection and feedback.
- the route is preferably presented in the terminal using a rough route description and can in particular be represented by icons (route symbols), by means of which the customer is guided to the destination.
- the orientation aid preferably has a restricted mistrack detection. A targeted return to the route can be supported.
- the Orientation Aid service is intended in particular for end devices that have no stored location or street data such as a digital map in the vehicle, but only with location determination devices such as are equipped with GPS (in the following is mostly
- the central unit takes into account the information transmitted by the terminal about the location function of the terminal (e.g. pure GPS or additional dead reckoning). This ensures that a functional orientation aid - albeit of a lower quality - is possible even with terminal devices without dead reckoning.
- the route evaluation service is also described in this document.
- a route known in the terminal is transmitted from the terminal to the control center.
- the travel time for this route is estimated on the basis of the current traffic situation and transmitted to the terminal.
- the orientation guide has the following basic sequence:
- the customer asks for the route
- optimization criteria e.g. shortest or fastest route
- points that should be approached on the route (via points) or points that should not be approached (avoid points) can also be specified.
- Various forms are supported for entering the destination address (e.g. city and street, POI: e.g. airport, train station).
- POI e.g. airport, train station
- the route request to the head office can be made via
- control center determines the above information for route calculation in dialog with the customer
- CORRECTED SHEET (RULE 91) ISA / EP
- the customer information is first checked for correctness, completeness and uniqueness when the route is requested with a destination request directly on the end device. Possibly. an error message is sent to the vehicle. If the user request cannot be clearly interpreted in the case of incomplete address information, a selection list is sent to the vehicle with the error message, with which the request can be specified.
- the route is prepared at the headquarters.
- the route information is sent to the vehicle using the Route_Message.
- the request for the head office ends.
- the route information contains
- the list of waypoints is processed locally in the end device.
- the order of the waypoints on the route is 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 has to be carried out, this is indicated by a corresponding icon.
- Wrong journeys are recognized when the customer leaves a predetermined corridor, the width of which is loaded into the terminal along with the route description.
- the terminal can then be
- This service enables the evaluation of a route present in the terminal with regard to the travel time to be expected on the basis of the current traffic situation (see FIG. 3).
- the route description (of the route to be calculated) is transferred to the head office (Travel_Time_-Request_Message).
- the route is described in the form of guidance points as with the orientation aid or the route guidance.
- the head office estimates the travel time for this route based on the current traffic situation and transfers it to the end device (Travel_Time_Message).
- the individual services are described functionally and the concrete processes based on the ADPs are shown.
- 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.
- the definition of the individual service parameters is the task of the respective service provider. This basic specification specifies the total scope of the functions and processes to be supported by the first-generation end devices. In addition, these processes and functions can be specified in more detail by the respective service providers in separate documents.
- the transport frame for the message types is defined in:
- Compass mode / pure terminal-side function in which an arrow on the homing display points in the direction of a geographic coordinate (usually with additional indication of the distance in a straight line)
- variable length
- the transport protocol is used as follows to use the orientation aid and route evaluation services:
- the framework supports the sending of several short messages.
- Application IDs are unique service identifiers assigned by the head office. These are transferred in the Fe / o ⁇ pplication ID in the transport layer.
- the service providers can define independent services within the defined processes. These can be characterized, for example, in that the information content transmitted is restricted. Service identifiers are assigned to identify the services offered.
- Initiative Fla ⁇ 1 (initiative) marks the first transaction in the chain, the order.
- the initiative Flao 1 (initiative).
- Protocol Discriminator and Message Type can be found in the document "Message Type Numbering".
- the bulk flag is always set to 0.
- the terminal For the orientation aid service, the terminal must support the full functionality of the internal services with regard to address management.
- the terminal For the route evaluation service, the terminal must support the full functionality of the internal services with regard to address management.
- All service parameters for navigation services are listed below.
- the service parameters currently supported by the control center are loaded into the terminal device by internal services. Processes or functions that cannot be parameterized are a binding part of the standard and are supported by all control centers.
- 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.
- the orientation guide has the following basic sequence:
- the customer may use the operator or e.g. B. initiates an online service to calculate a route (also with a time delay), so that the terminal then receives a route description without initiating a route request. In this case, the process begins immediately with the processing of the route in the terminal.
- the end devices must support this processing of "foreign", i.e. route messages initiated by third parties.
- the route request to the headquarters can be done via
- the following information must be provided or automatically generated by the end device:
- 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 when calculating the route based on the current traffic situation (the support of this functionality can be parameterized, see chapter 2.7).
- the "desired departure time" transmitted from the terminal to the control center is initially ignored by T-Traffic.
- Via points can be used to exclude or correct unwanted routes. 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 its geographic coordinate (see below).
- This field must then be filled in with the phone number of the recipient of the route if the route request is initiated externally.
- the customer When entering the destination on the terminal, the customer enters the addresses for the destination and all desired Viapoints on the terminal or selects them from an address memory of the terminal, if available.
- the address memory (address book) should be filled in the following ways:
- Position storage The customer can save his current position (geographic coordinate), supplemented by additional address information, in the address book (eg home address) on the end device.
- address book eg home address
- the addresses are transmitted to the head office using the Route_Request_Message and checked there for correctness, completeness and uniqueness. If the address information is incomplete, an error message is displayed, which if possible contains an address selection list for the addresses in question.
- the customer can then select the desired address and use it to initiate a new route request. It can be set by means of a parameter whether the control center fundamentally supports the return of selection lists (see chapter 2.7). All fields provided in the ADP for the specification and transmission of address information are to be supported on the terminal side. The service provider must specify which combinations and subsets are supported centrally.
- the error message is transmitted to the vehicle. This can contain selection lists. The support of the error message depends on the service provider.
- Service provider POl the complete address information received when an address is queried via information services must be transmitted (exception: "additional information” and "country”). Service provider POl can be loaded into the end device via information services (see chapter 3.2.2) and saved in the address book if necessary.
- MAP POI with location selection (street description and POI name are ignored): If there are several POIs in question, the closest POI is selected (a selection list may also be transferred).
- 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.
- Place selection and street name The street name must either be transmitted 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.
- the postcode and telephone number must not be passed at the same time, otherwise an error message will appear. The same applies if the place name and postal code or telephone number are contradictory.
- 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.
- hyphen e.g. Cologne-Lindenthal, Bonn-Bad Godesberg.
- 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.
- Telephone number Area code only (country code is Kannfeld, default: Germany).
- control center can set the "start / desination / additional address ambiguous" bit for the address concerned.
- a selection list field follows in the address description, in which an explanation of the error is given in free text in the "Additional Information" field. If a complete telephone number cannot be clearly interpreted, the telephone number is returned with the digits that could be interpreted (example: 0228-5201900 is transferred, the control center can interpret the number up to 02285201 and returns this number).
- selection lists are transferred to the vehicle with the error message according to the following criteria, whereby the selection list only contains the IUs to be specified (ie no complete address fields, exceptions are mentioned ):
- a Route_Req ⁇ est_Message is sent that contains at least the start position.
- 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 end device receives a Route_Message that it has not initiated and interprets it.
- the request telegram is not subject to any special restrictions. It is recommended to save the start address and the criteria selected by the customer for route calculation in the end device and to transfer them to the control center.
- Receiving an error message interrupts the establishment of the voice connection if it has not yet been established (with the timer-based procedure).
- the desired operator request is also identified in the message by the fact that no destination address is 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 IU's except for the destination address. It is recommended to save the criteria selected by the customer for route calculation in the end device and to transfer them to the control center.
- the control center After the route has been calculated, the control center then sends the route (Route_Message) to the vehicle.
- the route is created on the basis of the transmitted information based on the current traffic situation and coded in the Route_Message.
- the Route_Message is then transferred to the vehicle.
- a detailed rough route description can be generated for devices with a digital map (navigation systems).
- the list of route symbols in the navigation systems should be reduced to a level that is necessary for a vehicle-autonomous route fine calculation based on them.
- the Route_Message can contain the following information:
- the travel time to the destination is rounded, i.e. the control center 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:
- Breaks should be taken into account when updating the calculated arrival time while driving (detection by switching off the device).
- the list of waypoints denotes maneuvering 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 traveled is determined by the order of the waypoints in the list.
- the positioning of the waypoints can be handled differently depending on the service provider. This is particularly the case for the first or last waypoint in a waypoint list.
- the code contained in the IE "Type of Starting Point” or “Type of Destination” must also be observed when interpreting them. The exact definitions are made in the service provider specific additional specifications.
- 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:
- the terminal should then switch to compass mode, with the compass arrow pointing to the first waypoint.
- the "capture area" type is not supported for guidance.
- the center of the town is chosen as the reference point or, for POIs, the next possible coordinate
- a coordinate located nearby is also assigned on the central side.
- processing of the route should begin, i.e. there is no need to wait until the complete route arrives at the terminal.
- the rough textual description of the route contains essential milestones of the route, which give the user an overview of the route to be traveled (e.g. travel from Bonn to Düsseldorf: A555 to Kreuzchen Süd, A4 todorfchen Ost, A 1 to funnelchen 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 individual waypoints have the following content:
- the place name The place name is usually transmitted.
- 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.
- 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).
- 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 set depending on the type of intersection and the link flag set.
- the meaning of the coordinates is defined in detail in the service specification of the provider.
- the geographic coordinates are preferably assigned according to the following rules:
- both waypoints contain an icon code of the star type.
- the screen display should be in an icon.
- the exit street of the 1st waypoint is to be combined with the entry street of the 2nd waypoint.
- the appendix contains a suggestion for possible icon displays and suitable display behavior.
- a change in the waypoint pointed to by the arrow should be explicitly acknowledged by the user.
- the user can switch between the waypoints in compass mode.
- the user should only be informed of an incorrect travel if the position has moved a long distance outside the corridor. This allows inaccuracies in the GPS to be taken into account or suppressed.
- T-Traffic traffic reports preferably contain this street name (e.g. A555, B236). This makes it possible to filter out traffic reports that relate to roads that are on the route from the totality of the traffic reports available to the terminal (e.g. in the case of a circle-related or targeted Vl service, cell broadcast).
- the terminal device receives a geo code that cannot be interpreted in the rough route description, this can be translated into plain text using the TINFO message TINFO_Code_Request_Message (see ADP TINFO).
- Traffic announcements contain a redirection flag ("bypass flag"). If a traffic announcement is received on the route with the redirection flag set, the customer should be given the opportunity to make a new route request (combined with a travel time request) by displaying the traffic announcement (see also chapter 3.4).
- the proposed use of the route information provided within the navigation service and the reference area in connection with the traffic information service is a pure terminal feature, which is made possible by the compatibility of the services shown.
- Each service provider can freely assign numbers for individual POI types within the framework of the service provider POIs (e.g. petrol stations, ATMs).
- POIs e.g. petrol stations, ATMs.
- no numbering of service provider POIs is initially defined. If service provider POIs are to be used for the navigation service, then the full address of the desired POIs must be loaded from the central office by using an information service. This address can then be used for a destination request. The complete address information received from the control center should always be transferred to the service provider POl in order to avoid ambiguities (see also chapter 3.1.1.1).
- the service specification and the associated ADP for the information services describe how a service provider POI can be loaded.
- the request to the central office only receives the Route Request Message (no operator, see Fig. 5).
- the information from the route message (at least the starting position) and from the dialog with the operator are to be merged centrally.
- a timer-based synchronization mechanism must ensure 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 from the user.
- a route description (a calculated route) is transferred to the head office (Travel_Time_Request_Message).
- the route is described in the form of guidance points as with the orientation aid or the route guidance.
- the head office estimates the travel time for this route based on the current traffic situation and transfers it to the end device (Travel_Time_Message).
- the Travel_Time_Request_Message has the following content:
- intersections are coded in the same way as when entering the address on the end device when the route request is described.
- a transmitted telephone number is integrated 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.
- the service-specific error messages are defined in the ADP.
- Cross-service errors e.g. communication errors
- Description of cross-service error handling are shown in the document "Description of cross-service error handling".
- the data communication between the terminal and the control center is handled by the short message service available in GSM.
- the cell broadcast is not required for the navigation services, so that only short message services SMS-MT (TS 21) and SMS-MO (TS 22) are required for handling the services.
- SMS-MT short message services
- SMS-MO SMS-MO
- TS 11 The voice service (TS 11) must be supported in order to continue to enable operator requests.
- the end device should have dead reckoning.
- the end device may only send a localization pearl chain to the headquarters as the start address if a sufficiently precise localization is guaranteed.
- the location accuracy with coupler navigation must be ⁇ 50 m on average.
- the accuracy of dead reckoning navigation should not exceed 5% of the distance covered when driving slowly in the city (30 - 50 km / h) and 3% of the distance covered when driving at medium speed (70 - 90 km / h), 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.
- 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. To make it easier to enter destinations, a notebook with at least 50 entries should exist in the end device, from which, among other things, the target description can also be adopted.
- the waypoint memory should be designed dynamically so that no memory for the street name is kept free for waypoints that are transmitted without a street name.
- 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 (in particular, switch to the next signpost point).
- the orientation aid service is intended for devices that are preferably equipped with GPS without a digital map in the vehicle. It is therefore not possible, as is the case with navigation systems, at the maneuvering point of turning instructions such as. B. "turn right now” because the limited positioning accuracy does not allow the exact determination of the vehicle position (approx. 10m).
- the driver must be made aware of upcoming maneuvers in good time. As a maneuver tip, it is not sufficient to simply state the maneuver to be carried out immediately (e.g. turn right), but the user must be informed in advance of the intersection topography at the maneuver point by means of an abstract representation.
- the route guide symbol should be removed from the screen approx. 50m (without dead reckoning navigation 100m) after reaching the geographic coordinates of the route guide symbol (if the link flag is set, 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)
Description
Claims
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 (de) | 1996-12-10 | 1997-12-10 | Verfahren und anordnung zur information mobiler teilnehmer |
Publications (2)
Publication Number | Publication Date |
---|---|
EP0883872A1 true EP0883872A1 (de) | 1998-12-16 |
EP0883872B1 EP0883872B1 (de) | 2002-05-08 |
Family
ID=7814139
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP97952715A Expired - Lifetime EP0883872B1 (de) | 1996-12-10 | 1997-12-10 | Verfahren und anordnung zur information mobiler teilnehmer |
Country Status (5)
Country | Link |
---|---|
EP (1) | EP0883872B1 (de) |
AT (1) | ATE217434T1 (de) |
AU (1) | AU5650798A (de) |
DE (2) | DE19651146A1 (de) |
WO (1) | WO1998026396A1 (de) |
Families Citing this family (29)
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 |
ATE454687T1 (de) * | 1998-11-23 | 2010-01-15 | Integrated Transp Information | System zur momentan-verkehrsüberwachung |
DE19906863A1 (de) * | 1999-02-18 | 2000-10-19 | Nokia Mobile Phones Ltd | Verfahren zur Navigation eines Objekts |
EP1106965B1 (de) * | 1999-06-22 | 2007-08-22 | Mitsubishi Denki Kabushiki Kaisha | Mobilendgerät und server in einem navigationssystem |
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 |
WO2001029514A1 (en) | 1999-10-19 | 2001-04-26 | 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 |
AU2321102A (en) | 2001-03-12 | 2002-09-19 | Magellan Dis, Inc. | Off-board navigation system with personalized navigation database |
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 |
AU2003223090A1 (en) | 2002-04-30 | 2003-11-17 | Telmap Ltd. | Template-based map distribution system |
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 |
KR20060119739A (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 |
KR20060119746A (ko) | 2005-05-18 | 2006-11-24 | 엘지전자 주식회사 | 교통상태에 대한 정보를 제공하고 이를 이용하는 방법 및장치 |
EP2216762B1 (de) * | 2005-05-18 | 2011-05-11 | Lg Electronics Inc. | Bereitstellung von Verkehrsinformation in Bezug auf die Vorhersage eines Staustatus und Verwendung davon |
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 |
WO2014045146A1 (en) | 2012-09-23 | 2014-03-27 | Telmap Ltd | Inferring user risk profile from travel patterns |
Family Cites Families (3)
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 |
-
1996
- 1996-12-10 DE DE19651146A patent/DE19651146A1/de not_active Withdrawn
-
1997
- 1997-12-10 DE DE59707219T patent/DE59707219D1/de not_active Expired - Lifetime
- 1997-12-10 EP EP97952715A patent/EP0883872B1/de not_active Expired - Lifetime
- 1997-12-10 WO PCT/DE1997/002884 patent/WO1998026396A1/de active IP Right Grant
- 1997-12-10 AT AT97952715T patent/ATE217434T1/de active
- 1997-12-10 AU AU56507/98A patent/AU5650798A/en not_active Abandoned
Non-Patent Citations (1)
Title |
---|
See references of WO9826396A1 * |
Also Published As
Publication number | Publication date |
---|---|
DE59707219D1 (de) | 2002-06-13 |
AU5650798A (en) | 1998-07-03 |
WO1998026396A1 (de) | 1998-06-18 |
EP0883872B1 (de) | 2002-05-08 |
DE19651146A1 (de) | 1998-06-25 |
ATE217434T1 (de) | 2002-05-15 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP0883872B1 (de) | Verfahren und anordnung zur information mobiler teilnehmer | |
EP0883871B1 (de) | Verfahren und anordnung zur verkehrsinformation | |
EP1186865B1 (de) | Verfahren zur Bestimmung einer Fahrtroute eines Fahrzeugs | |
EP1206766B1 (de) | Ortsbezogene wap-staukarte durch verknüpfung von kartenausschnitten in einer verkehrsinformationszentrale | |
EP1198696B1 (de) | Verfahren und vorrichtung zur übermittlung von navigations-informationen von einer datenzentrale an ein fahrzeug-basiertes navigationssystem | |
DE69925779T2 (de) | Routensuchvorrichtung | |
EP1255964B1 (de) | Navigationsverfahren mit dynamischer zielauswahl und navigationsgerät | |
EP1062481B1 (de) | Verfahren zur ausgabe von verkehrsinformationen | |
DE102010006702A1 (de) | Verfahren und Vorrichtung zur Berechnung alternativer Routen in einem Navigationssystem | |
EP1360458B1 (de) | Verfahren zum austauschen von navigationsinformationen | |
EP0979987A2 (de) | Verfahren zum Bestimmen einer Route von einem Ausgangspunkt zu einem Zielpunkt | |
WO2007062899A1 (de) | Vorrichtung und verfahren zur ausgabe von zielführungsinformationen eines navigationssystems | |
DE10354218A1 (de) | Verfahren zur Auswahl und Aufbereitung von Verkehrsinformationen | |
EP1342221A1 (de) | Verfahren zum automatischen löschen einer verkehrsmeldung | |
DE10009727A1 (de) | Navigationseinheit für ein Kraftfahrzeug | |
DE102015200081A1 (de) | Bereitstellen von Navigationshinweisen in einem Fahrzeug | |
EP2205942B1 (de) | Navigationssystem und verfahren zur routenermittlung | |
EP1255092B1 (de) | Vorrichtung und Verfahren zur Informationsanzeige in einem Fahrzeug | |
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 | |
EP1714261B1 (de) | Verfahren zur decodierung, codierung und übertragung von fahrtroutendaten und navigationsvorrichtung | |
DE19861486B4 (de) | Datenvorrichtung für ein Kraftfahrzeug | |
WO2004094953A1 (de) | Verfahren zur fahrroutenplanung |
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 |