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/091—Traffic information broadcasting
  • G08G1/092—Coding or decoding of the information

Definitions

• the invention relates to a device for transmitting route recommendations to at least one network of public transport to receivers and a receiver for route recommendations.
• the object of the present invention is to transmit such route recommendations if necessary in such a way that they can be received in a simple manner by many receiving devices.
• this object is achieved in that coding is carried out by means of at least one location database that maps at least parts of the traffic network.
• a first embodiment of the device according to the invention consists in that data protocols provided for the transmission of digitally coded traffic reports (TMC) are used. In particular, it is provided that data protocols provided for diversions are used.
• an RDS-ODA protocol is used for the transmission.
• the device according to the invention has the advantage that the route recommendations can be received and decoded by a large number of receiving devices.
• Car radios are currently designed to receive digitally coded traffic reports - both in connection with RDS (radio data system) and DAB (digital audio broadcasting). Since there is no return channel here, this group of receivers will essentially use the transmission of route recommendations that are of interest to many users of such receivers, for example for trade fair visitors arriving by motor vehicle, the recommendation to visit a parking space on the outskirts and one or use multiple lines of public transportation.
• the invention can also be used with other mobile radio media, such as GSM, SWIFT, UMTS.
• the device according to the invention also has the advantage that the known receivers, which are inexpensively manufactured in large numbers, can also be used for receiving route recommendations from public transport networks, and can also be linked to the road network.
• the device according to the invention for the transmission of travel route recommendations, Different locations of stored locations relate to locations, records of those locations that have at least one neighboring location in at least one of the other location databases contain at least one reference to at least one such adjacent location by means of a cross-reference.
• a route recommendation describes a route to be covered by the motor vehicle up to a so-called park and ride parking lot and a subsequent route by public transport.
• the route route recommendations can also be selected in accordance with the selection of the traffic reports in such a way that the receiver only receives those route route recommendations that are likely to be of importance to the user.
• the device according to the invention also has the advantage that for route recommendations, for which data from road networks are also required, for example the flow of traffic on the streets and highways is taken into account, the data automatically acquired for the TMC system or similar systems can be used.
• the route recommendations are longer than a traffic message transmitted by the TMC system, e.g. traffic jam, 5 km in length, A7 motorway, Hildesheim junction. Therefore, according to a further development, it is provided that the route recommendations are transmitted as multi-group messages.
• An advantageous receiver for route recommendations of at least one public means of transport consists in that at least one location database which depicts at least parts of the traffic network is provided for decoding in the receiver.
• a location database is preferably stored on an exchangeable data carrier, so that the user of a recipient has the most interesting traffic networks available to him, without having to purchase location databases for all traffic networks, for example a country.
• the receiver according to the invention can also be designed such that the location database can be updated via an air interface.
• devices for managing and decoding digitally coded traffic reports (TMC) are provided for managing and decoding the route recommendations.
• TMC digitally coded traffic reports
• the receiver according to the invention can provide that at least parts of a further location database that does not contain locations listed in the location database that maps the network, and that codes for the locations of the location database and the further location database are combined in a common location database .
• FIG. 1 shows a multi-group message for the implementation as an RDS-ODA application, which contains a route recommendation
• FIG. 3 shows a multi-group message for the implementation as a TMC application, which contains a route recommendation
• Fig. 4 shows a section of a location database for the device according to the invention.
• FIG. 2 shows an example of a route network that partially extends through the area of a large city 1 and partially through the surrounding area 2.
• a tram line 3 leads from a first end point 6 via stops 7, 8, 9, 10 to a second end point 11.
• Stop 8 is a transfer point to a bus line with end points 12, 15 and further stops 13, 14.
• Stop 10 serves as a transfer point to a P + R car park at the junction of a motorway 5, of which further junctions 16, 17, 18 are shown.
• the route network shown can be coded in the same way as the road networks in the TMC system, that is, location databases, as described in the ALERT C standard, list the individual locations in connection with a line, with each location, for example, to the stop 7, a predecessor 6 and a successor 8 are provided as a cross-reference. Since the transfer point 8 is also a location on the bus line 4, additional referencing takes place here, as is shown, for example, in patent application 196 06 010.
• lines 3, 4 of the public transport network are shown in a location database specially provided for this purpose or integrated into an existing location database, while highway 5 is stored in a conventional location database within the TMC system, corresponding cross-references can be made at location 10 in each case indicate the other route (highway or tram line).
• a message serving as a travel recommendation can have the following message elements:
• IP point of interest
• Line designation indicates the line in the route network
• Line end point specifies the end stops of lines in order to be able to indicate the direction of travel.
• Stop / Ummssimo indicates the point of entry or departure at which the means of transport can be boarded or left
• Cycle time gives the average time interval between the
• Period specifies the period in which the above Cycle time applies (e.g. from ⁇ hh: mm> to ⁇ hh: mm>)
• Coding 2x8 bit (example) according to ALERT C multi-group messages
• Coding tariff zone 3 bit (example)
• Zone 1 Zone 7
• TypeTime specifies the coding types .
• Number of transfer points can be reduced accordingly.
• the bit at position Y15 identifies the first group of a message.
• Each group has a length of 37 bits, which are designated in the example with X4 to X0, Y15 to 0 and Z15 to Z0.
• bits Y13 to Y11 are provided for the number of transfer points.
• bits Y10 to YO there is a so-called event marking that this message represents a travel recommendation FE.
• Y13 to Y12 indicate that it is the second group. This is followed by the destination information Z and the location code of the first transfer point U1, which extends into the third group.
• the location code of the changeover point U2 is then transmitted (bits Y7 to Z8) and the location code of the changeover point U3 (bits Z7 to ZO and bits Y11 to Y4 of the next group). Finally there is the location code of a changeover point U5, which is also partially transmitted with the fifth group. Subsequently, the travel time T, the tariff zone TZ, the time type TYPE and the departure time ST are transmitted, whereupon one bit remains free at ZO of the fifth group.
• FIG. 3 shows a route recommendation similar to that of FIG. 1, but the coding is in a form compatible with RDS-TMC, in which case only a maximum of four changeover points U1 to U4 can be coded.
• the transmission of additional information is also limited to one entry, in the present example to the train sequence ZF.
• the individual location codes are identified by labels. Label 11 means the destination, label 10 a waypoint and label 6 additional information.
• label 11 means the destination, label 10 a waypoint and label 6 additional information.
• the link to the "normal" TMC message is made via the location code S transmitted in the first group. This is the place where a transition to public transport is appropriate.
• Fig. 4 shows parts of a location database for public transport in the Hanover area.
• the location codes (LocCode) 45004 to 46009 refer to an S-Bru line, which has the "Road No.” 4 is assigned.
• Location code 22001 relates to a location (point) on road No. 2, which is the federal road B2. The name of this place is "airport”.
• " ⁇ V-Point” is entered as information on the type of location (LocType) for the locations on the S-Bru line, the location type "Line” for the S-Bru line overall in one direction.
• a blurred area - hence the type of place "Fuzzy" - with the location code 41922 characterizes the area that is to be counted as part of the operation of public transport.
• the name of the location type (RName), one or two names (Name, Name2) and references to other location codes (Offset +, Offset-, RefL and RefA) are given for the individual location codes where applicable.
• an "intersection code” is specified for some of the location codes, for location code 22001 a reference to location code 45775 and vice versa.
• a travel route recommendation transmitted according to the TMC standard is then, for example, as follows:

Landscapes

• Engineering & Computer Science (AREA)
• Multimedia (AREA)
• Physics & Mathematics (AREA)
• General Physics & Mathematics (AREA)
• Traffic Control Systems (AREA)
• Instructional Devices (AREA)

Priority Applications (3)

Applications Claiming Priority (2)

Publications (1)

Family

ID=7891623

Family Applications (1)

Country Status (4)

Cited By (1)

Families Citing this family (7)

Citations (4)

• 1998
  • 1998-12-18 DE DE19858568A patent/DE19858568A1/de not_active Withdrawn
• 1999
  • 1999-10-05 EP EP99973504A patent/EP1141911B1/de not_active Expired - Lifetime
  • 1999-10-05 DE DE59902889T patent/DE59902889D1/de not_active Expired - Lifetime
  • 1999-10-05 WO PCT/DE1999/003197 patent/WO2000038129A1/de active IP Right Grant
  • 1999-10-05 JP JP2000590118A patent/JP2002533820A/ja active Pending

Patent Citations (4)

Non-Patent Citations (2)

Also Published As

Similar Documents

Legal Events