WO1996037057A1 - Procede de transmission sans fil de messages codes numeriquement pour voies maritimes et/ou navigables et dispositif permettant de recevoir des messages pour voies maritimes et/ou navigables - Google Patents

Procede de transmission sans fil de messages codes numeriquement pour voies maritimes et/ou navigables et dispositif permettant de recevoir des messages pour voies maritimes et/ou navigables Download PDF

Info

Publication number
WO1996037057A1
WO1996037057A1 PCT/DE1996/000726 DE9600726W WO9637057A1 WO 1996037057 A1 WO1996037057 A1 WO 1996037057A1 DE 9600726 W DE9600726 W DE 9600726W WO 9637057 A1 WO9637057 A1 WO 9637057A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
location
code
field
level
Prior art date
Application number
PCT/DE1996/000726
Other languages
German (de)
English (en)
Inventor
Peter Braegas
Ulrich Kersken
Karin Hempel
Original Assignee
Robert Bosch Gmbh
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Robert Bosch Gmbh filed Critical Robert Bosch Gmbh
Priority to EP96911923A priority Critical patent/EP0772926A1/fr
Publication of WO1996037057A1 publication Critical patent/WO1996037057A1/fr

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04HBROADCAST COMMUNICATION
    • H04H20/00Arrangements for broadcast or for distribution combined with broadcast
    • H04H20/28Arrangements for simultaneous broadcast of plural pieces of information
    • H04H20/33Arrangements for simultaneous broadcast of plural pieces of information by plural channels
    • H04H20/34Arrangements for simultaneous broadcast of plural pieces of information by plural channels using an out-of-band subcarrier signal
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04HBROADCAST COMMUNICATION
    • H04H20/00Arrangements for broadcast or for distribution combined with broadcast
    • H04H20/53Arrangements specially adapted for specific applications, e.g. for traffic information or for mobile receivers
    • H04H20/55Arrangements specially adapted for specific applications, e.g. for traffic information or for mobile receivers for traffic information
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04HBROADCAST COMMUNICATION
    • H04H20/00Arrangements for broadcast or for distribution combined with broadcast
    • H04H20/86Arrangements characterised by the broadcast information itself
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04HBROADCAST COMMUNICATION
    • H04H2201/00Aspects of broadcast communication
    • H04H2201/10Aspects of broadcast communication characterised by the type of broadcast system
    • H04H2201/13Aspects of broadcast communication characterised by the type of broadcast system radio data system/radio broadcast data system [RDS/RBDS]

Definitions

  • the invention relates to a method for the transmission of shipping / waterway reports according to the preamble of the main claim.
  • Shipping / waterway reports have so far only been transmitted via radio signals in the form of spoken water level messages.
  • Most users of these messages rely on round-the-clock messages, as a television or telephone is not available everywhere.
  • the spoken messages have the disadvantage for the user that they are only sent at certain times, are often out of date and can often only be received in poor quality. Since the messages cannot be selected by these users, all messages must always be listened to, even if a large part of the announcement messages are not important to the user.
  • the inventive method with the characterizing features of the main claim has the advantage that the known RDS transmission principle can also be used for the distribution of shipping / waterway reports. Because the shipping and
  • Waterway messages can be divided into a number of different message types, with a message of a certain message type being transmitted in a typical RDS data group, it is not necessary to develop a completely new transmission protocol. Because a message type code is transmitted in the message type code field provided for this purpose in the data group, a correspondingly designed receiving device can evaluate the different message types differently, so that it is not necessary to define a single, fixed coating structure that is uniform for each message type. Of course, other digital transmission methods, such as DAB, suitable. All advantages of the RDS transmission process are retained. The transfer of the
  • Shipping / waterway reports are made in parallel with the current program.
  • the messages are also repeated cyclically and are therefore available shortly after switching on and are always up to date.
  • no plain text messages are transmitted, only changeable information. It is also possible to select the messages relevant to the user according to selectable selection criteria, for example individual message types.
  • time code field in the data group that contains a message of the message type water level message, in which a time code is entered which indicates the time of the current day for which the level information in the water level message is valid.
  • transmission capacity can be saved by coding the time. This is then available for other purposes.
  • an event code field is provided in the data group which contains a message of the message type Fault message - first sequence, in which an event code is stored which indicates which
  • a message of the type of fault report - first sequence contains a data field for a first kilometer specification, in which it is entered at which distance kilometer of the corresponding body of water the fault begins.
  • a data field for a kilometer difference can then be provided, in which the extent to which the fault extends over the water is entered.
  • a sign code field can also be provided, in which it is coded whether the mileage difference is to be subtracted from or added to the kilometer specification in the message of the message type fault report - first sequence.
  • the location data field contained in the second sequence, together with the message type code serves to uniquely identify the relationship between the first sequence and the second sequence. This is particularly important if the second sequence does not immediately follow the first.
  • the coded transmission of the date on which the maximum level of a flood is expected to arrive in the case of a message of the message type peak level message, also enables the transmission capacity to be saved.
  • the evaluation unit contains an evaluation unit that filters out the data groups in which shipping / waterway reports are contained from the continuous data stream of an RDS decoder and that the evaluation unit continues Means that the message type code of a Shipping / waterway report evaluates, it evaluates the information in the data group according to the message type code and that the evaluation unit contains a frame set table and reads the correct frame set from the frame set list according to the message type code and, if necessary, the location code and after completion of the frame set with the information of the evaluated Forward message to an output unit.
  • the evaluation unit can consist of an appropriately programmed microcomputer.
  • the evaluation unit additionally contains a location database and a first normal value is stored in the location database in addition to the location information stored under corresponding location codes for certain location information.
  • B. indicates the characteristic normal level for the location. This is required to calculate the current level. It is then also possible for the normal water level to be included in the specification of the current water level based on the message of the message type water level message, without this having to be transmitted. It is also advantageous if, in addition to the location information, a second normal value is stored in the location database, which indicates the distance kilometer of the water where the respective location is located. This value is used to calculate the current mileage. This information also then no longer needs to be transmitted. This is particularly advantageous in the case when a body of water such. B.
  • a certain river is so long that the distance kilometers from distant places can no longer be transmitted in the defined data field of the message for the location, because the data field can no longer accommodate such long distance kilometers.
  • the location database, the event table and the frame set list are stored on a chip card and the receiving device has a chip card reading device. This makes it possible for the user of the message service to receive the messages in his own mother tongue, even if he is traveling in a foreign-language area. It must then be possible to purchase chip cards for the possible different languages.
  • FIG. 1 shows the structure of a message of the water level message type
  • Figure 2 shows the structure of a message of the message type fault message - first sequence and a message of the message type fault message - second sequence
  • 3 shows the structure of a message of the message type flood report - first sequence and a message of the message type flood report - second sequence
  • Figure 4 shows the structure of a message of the message type peak level message
  • FIG. 5 shows a rough block diagram of a device for receiving shipping / waterway reports
  • Figure 6 shows an example of a location database
  • Figure 7 shows an example of an event table
  • 8 shows an example of a frame set table
  • FIG. 9 shows a rough program structure for the evaluation unit of the device according to FIG. 5.
  • the invention is based on the known radio data system RDS.
  • RDS radio data system
  • more and more FM stations broadcast a continuous data stream. It is the data stream is divided into data groups of 104 bits each.
  • the technical implementation, in which frequency band the data stream is transmitted, which type of modulation is used, etc., is well known from the prior art. In this regard, reference is again made to the article by Manfred Königsberger "Broadcast Traffic Information Systems" mentioned in the prior art chapter.
  • the continuous RDS data stream is designated by the reference number 10 in FIG. As already mentioned, it is divided into data groups. Each data group consists of 104 bits. Each data group is also divided into four blocks. A block then consists of 26 bits each. A data group is designated by the reference number 11 in FIG. Its structure is shown in more detail in Figure 1.
  • the hatched parts of blocks 1 - 4 of data group 11 contain test codes which serve to secure the data transmission. The check codes each require 10 bits in a block of a data group. This means that 64 bit spaces are available for user information in a data group. 16 different data group types are available for the radio data system. So far, not all data group types have been defined. According to the invention, one of the data group types is used for the transmission of the shipping / waterway reports.
  • Blocks 1 and 2 already contain 27 user data bits for the tuning and switching information and for the identification of the group type. In block 2, five bit spaces are therefore still available for the user data. Blocks 3 and 4 are entirely free.
  • a message of the water level message type is entered in data group 11.
  • the free bit spaces in data group are 11 as follows.
  • a message type code field 12 five bit spaces are available for the message type code. This enables 32 different message types.
  • bit field 13 nine bit spaces are available for a location code.
  • a bit space for a time code is available in bit field 14.
  • a bit space for a sign code is available in a sign code field 16.
  • ten bit spaces are available for a level.
  • a bit space is available for a sign code.
  • ten bit locations for a level difference value are available in data field 17.
  • the decimal value zero is entered in the message type code field 12. From this a receiver device recognizes that the message type is water level message. On the basis of this message type code, it is then also determined how the evaluation unit in the receiver device has to evaluate the remaining bit spaces in the data group. The
  • the receiver device recognizes that the next nine user data bits have been used for a location code, followed by a bit field for a time code, and then finally a sign code field with a bit width for indicating whether the following information in a data field with a ten bit width is associated with that Normal level must be added or subtracted. It also recognizes from the message type code that there is a sign code field consisting of a bit for specifying the sign of the level difference and then finally a ten-bit data field with the specification of the actual level difference. After evaluating the message type and other information, such as, in particular, the location code, the evaluation unit in the receiver device then selects a frame set from a corresponding frame set table. Finally completes the evaluation unit in the
  • Receiver device this frame set with the information in the individual bit fields of the message and supplements the frame set to a complete message.
  • the complete message is shown in FIG. 1.
  • Reference number 12 in turn denotes a message type code field. This again consists of five bit spaces.
  • the message type code field is in turn included
  • Location code field 13 In this case, the location code field has a size of ten bit spaces. A total of 1024 different locations can thus be selected via location code field 13.
  • a data field 18 for indicating the kilometer follows the location code field 13. This data field 18 has a width of 14 bits. The kilometers are specified in this bit field with one digit after the comma. The value 1638.3 km can thus be entered in the data field for the kilometer specification as the maximum distance kilometer specification.
  • An event code field 19 connects to the data field 18 for the mileage. This has a width of eight bit spaces. This allows 256 different events to be coded which indicate the faults and / or causes of the fault.
  • the message of the message type fault message - second sequence also begins with a message type code field 12 of five bits wide.
  • the location code field 13 with a width of ten bits then follows again. This is followed by a sign code field 20 which only provides one bit location.
  • the sign code in this bit field determines whether the Add the mileage difference in the following bit field to the distance kilometer specification in the data field 18 or subtract from this. In the following data field 21 for the kilometer difference, 13 bit spaces are kept ready. Here, too, the mileage in this bit field follows exactly with one decimal place.
  • a value of +/- 819.1 km can be entered in this bit field as the maximum kilometer difference.
  • This bit field is eight bits wide. The number entered in this bit field indicates, for example, the number of days during which the fault is likely to continue. However, it can also specify hours or weeks instead. For example, a maximum of 255 days is possible.
  • the corresponding arrows show how the fault message in the lower part of FIG. 2 is composed of the individual entries in the bit fields of the two messages.
  • the frame set is selected on the basis of the message type code "1" in the message type code field 12 of the message of the type fault message - first sequence.
  • Figure 3 shows the composition of the message type flood report - first sequence and flood report - second sequence.
  • these two messages can be transmitted by preferably successive data groups 11, but this is not absolutely necessary, and the entire flood report can also be carried out in two different cycles are transmitted, since a clear relationship is guaranteed by the message type code and location code.
  • the first sequence follows the data group of message type code field 12 at the end of the user data field in block 2.
  • the field here also consists of five bit locations.
  • the location code field 13 then follows. In this case, it has a bit width of nine bits. This makes it possible to differentiate between 512 different locations.
  • the subsequent field is followed by a data field 15 for the last high water level measured an hour ago. This bit field is eleven bits wide.
  • This sign code field 16 indicates whether the value in the subsequent data field 17 for the level difference within the past past hour must be added or subtracted to the previous measured value in the data field 15. This is followed by data field 17 for the
  • Level difference This has a width of six bits. Level differences that can occur within an hour of up to ⁇ 63 cm can be specified with an accuracy of 1 cm.
  • a data field is provided for the current time. This has a width of five bits.
  • Reference number 12 designates the message type code field of this message. It is also five bit wide.
  • the location code is also entered in a subsequent location code field 13. This also has a width of nine bit spaces. This is followed by a sign code field 16 with a width of one bit space.
  • a data field 17 for a level difference then follows. This has a width of six bit spaces. A level difference value is entered in this bit field, which indicates which changes in the water level can be expected in six hours after the flood report has been sent.
  • the sign code in the sign code field 16 indicates whether the value in the data field 17 is to be added or subtracted to the specified level in the data field 17 of the previous message of the message type flood report - first sequence.
  • the following sign code field 16 again has a width of one bit.
  • a data field 24 for the fluctuation range of the prediction This has a width of three bit spaces.
  • the number given in this data field 24 means that the predicted water level may differ in a certain direction by the number given in this bit field multiplied by 5 cm. The direction is indicated by the sign code in the sign code field 16. If the decimal number 2 is therefore entered in this data field 24, this means that the water level of the prediction can fluctuate up or down by 10 cm, depending on the information in the preceding sign code field 16.
  • the following bit fields apply to a second prediction. This second forecast provides information about the expected flood level in 24 hours after the flood report was broadcast.
  • the sign code field is again only one bit wide and the data field for the level difference is seven bit wide. The value entered in this bit field must be multiplied again by 5 cm. This means that a maximum value of ⁇ 640 cm change can be entered in this data field within 24 hours.
  • the sign code field 16 and the data field for the fluctuation width 24 then follow again.
  • the sign code field 16 again has a width of 1 bit and the data field for the
  • Fluctuation width is again three bits wide. The conditions are exactly the same as for the forecast report for six hours after the flood report was broadcast. Arrows again indicate which information in the complete flood report from the bit fields of the
  • FIG. 4 shows the composition of a message of the message type peak level message.
  • Reference number 12 in turn designates the message type code field.
  • the field is five bits wide.
  • the reference number 13 denotes a location code field.
  • Reference number 15 denotes a data field for the level. This field also has a width of eleven bit spaces, so that the maximum level can be specified up to 2047 cm above the normal value.
  • Reference number 23 denotes a data field for the time at which the maximum level is to be expected. The field is five bits wide. This allows 32 different entries. So it covers the 24 full hours safely. In addition, 8 times can be coded with data field 23.
  • the data field 25 has a width of three bits. This means that the maximum level can be predicted up to eight days after the message has been transmitted.
  • Bit field 26 relates to an empty field, the bits there are not used. This field is three bit wide.
  • the date for the peak is calculated from the number of days transferred in data field 25 and the current date.
  • the current date can be taken from RDS data group 4. Arrows in turn show how the individual information is put together in the bit fields of the message for the complete flood message.
  • reference numeral 30 denotes a broadcasting station. The information from the flood reporting centers flows there together and it will be the
  • the receiving device then has the following structure, as also shown in FIG. 5.
  • Reference number 31 denotes a tuning and receiving unit. For example, this is an FM tuner.
  • Reference number 32 denotes an LF amplifier. This amplifies the demodulated radio signal and feeds the loudspeaker 33. The sound signal of the
  • the tuning and reception unit 31 outputs a demodulated MPX signal to the decoder circuit 34.
  • the decoder circuit can be designed in particular as an RDS decoder. It is used to extract the continuous data stream from the MPX signal. If necessary, processing stages can also be included here which already evaluate certain data groups of the data stream and forward corresponding information to the output unit 36.
  • the reference number 35 denotes an evaluation unit.
  • the evaluation unit 35 analyzes the data stream which is output by the decoder circuit 34.
  • the evaluation circuit then converts those data groups which contain shipping / waterway messages so that a readable message can be passed on to the output unit 36.
  • a microcomputer arrangement with corresponding storage units is most suitable for the evaluation circuit 35.
  • a suitable evaluation program is then processed in the microcomputer.
  • the evaluation unit 35 contains a frame set table, a location database and an event table in its memory.
  • the location database is shown in more detail in FIG. 6. It contains a column 40 for the location code.
  • the location code is also transmitted with the messages. Based on the location code, the microcomputer can immediately select the correct information from the table.
  • the table also contains a column 41 for a type specification.
  • the type specification specifies the possible hierarchy levels, the relationship between them is indicated by references.
  • the type specification determines whether, in extreme cases, the location information affects an entire continent, the national territory of a specific country, a federal state, a specific body of water or a specific location on a body of water. In this way frame sets can be specifically selected that relate specifically to a specific body of water, country, etc.
  • the location database also includes a column 42 for subtype specification. So z. B. be differentiated between barrages or water levels for certain locations.
  • a column 43 for specifying the proper name is also contained in the location database. The proper name of a state, a continent, a federal state, a body of water and a place is given.
  • a column 44 for a first normal value and a column 45 for a second normal value are provided in the location database.
  • the information in column 45 may e.g. B. refer to a mileage, this z. B. indicates the kilometer section of the location with respect to the source of the river.
  • a reference can also be added in column 46. In this column, you can enter the waters where this location is for different locations. This can be done in a simple manner in that the location code for the corresponding column
  • Water name is entered in the local database.
  • Column 47 can be provided for a second reference in the location database. The second reference then refers to the political area to which the respective location belongs (e.g. federal state).
  • the location database can additionally contain a column 48 for specifying the successor location. It stores the location code of the next location downstream. Accordingly, a further column 49 can be provided in which the location code of the previous location is entered. So here the location code of the next location is entered in the direction upstream. This information is useful if the locations of a river are not entered in the correct order in the location database.
  • subsequent extensions to the location database e.g. possible with little effort by adding a new level point.
  • three entries under different location codes are provided in the location database for the location Frankfurt.
  • the entries with the code numbers 00143 and 00144 are separately typed in column 42 by the entries level 1 and level 2.
  • the evaluation unit recognizes from these entries that those transmitted with the message
  • Figures refer to predictions. If the location code 00143 is transmitted in a message of the water level message type, the evaluation unit evaluates the information for the water level in the data field for the water level 15 as in the following bit fields 16 and 17 for the Sign code and the level difference.
  • the information in data field 15 represents a forecast for the 2nd day after the previously transmitted water level message with location code 00142. Accordingly, the information in fields 16 and 17 are the prediction values for the 3rd day after the water level message.
  • a water level message with the location code 00144 then contains the forecast values for the 4th and 5th day after the current message. The relationship between the messages is given by the offset reference.
  • Figure 7 shows an example of an event table. This consists of a column 55 for the event code and a column 56 for the fault event.
  • Figure 8 shows a frame set table. It contains one
  • FIG. 9 shows a rough program structure for a program for the evaluation unit 35.
  • the reference number 65 denotes a program step in which the evaluation unit evaluates the data group code of the data groups in the continuous data stream 10.
  • the shipping / waterway reports are always transmitted with the same data group code.
  • the microcomputer only needs to compare this specific data group code with the data group code of the respectively received data group in order to select the data groups relevant to it.
  • program step 66 the information of a shipping / waterway report is then evaluated.
  • the message type code is analyzed for this. Depending on the message type code, the individual bit fields of the message must then be evaluated differently. However, this has already been explained with reference to FIGS. 1-4, so that it will not be discussed in more detail below.
  • the microcomputer selects the appropriate frame set based on the message type code and location code. He completes the framework with the information contained in the message, using the location database and the event table. The complete sentence is finally transmitted to the output unit 36 in program step 68. Subsequently, a new data group code is evaluated as in program step 65. The next message can then be evaluated.
  • the shipping / waterway reports were broadcast via the RDS transmission method already used in VHF radio.
  • the invention is not limited to this embodiment.
  • a transmission method for digital data also exists in the medium wave broadcasting sector under the name AMDS.
  • the shipping / waterway reports can also be made in this or in another frequency range, e.g. DAB, GSM are transmitted.
  • the receiving device does not have to be designed as a radio.
  • the data can then be output on the monitor using the personal computer. Voice output is also possible.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Arrangements For Transmission Of Measured Signals (AREA)

Abstract

L'invention concerne un procédé de transmission de messages pour voies maritimes et/ou navigables, à l'aide de signaux radio. L'émetteur de radiodiffusion diffuse à cet effet un flux sériel continu de données comportant des messages pour voies maritimes et/ou navigables. Les messages sont transmis en groupes de données. Les messages pour voies maritimes et/ou navigables sont répartis en un nombre de différents types, concernant notamment le niveau de l'eau, les perturbations, la marée haute et le niveau le plus haut. Dans le groupe de données, pour différencier les divers types de messages, il est prévu une zone de code de type de message, dans laquelle est déposé un code de type de message. Il est en outre prévu un dispositif permettant de recevoir des messages pour voies maritimes et/ou navigables. A cet effet, le dispositif de réception contient une unité d'évaluation (35) qui détecte les messages pour voies maritimes et/ou navigables significatifs dans le flux continu de données et évalue le message en fonction du code de type de message contenu dans le message.
PCT/DE1996/000726 1995-05-19 1996-04-26 Procede de transmission sans fil de messages codes numeriquement pour voies maritimes et/ou navigables et dispositif permettant de recevoir des messages pour voies maritimes et/ou navigables WO1996037057A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP96911923A EP0772926A1 (fr) 1995-05-19 1996-04-26 Procede de transmission sans fil de messages codes numeriquement pour voies maritimes et/ou navigables et dispositif permettant de recevoir des messages pour voies maritimes et/ou navigables

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE19518173.5 1995-05-19
DE1995118173 DE19518173A1 (de) 1995-05-19 1995-05-19 Verfahren zur drahtlosen Übertragung von digital codierten Schiffahrts/Wasserstraßenmeldungen und Vorrichtung zum Empfang von Schiffahrts-/Wasserstraßenmeldungen

Publications (1)

Publication Number Publication Date
WO1996037057A1 true WO1996037057A1 (fr) 1996-11-21

Family

ID=7762193

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/DE1996/000726 WO1996037057A1 (fr) 1995-05-19 1996-04-26 Procede de transmission sans fil de messages codes numeriquement pour voies maritimes et/ou navigables et dispositif permettant de recevoir des messages pour voies maritimes et/ou navigables

Country Status (3)

Country Link
EP (1) EP0772926A1 (fr)
DE (1) DE19518173A1 (fr)
WO (1) WO1996037057A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6404408B1 (en) * 1999-01-07 2002-06-11 Surfer Network.Com, Inc. Enhanced radio graphic data system
AU5736400A (en) * 2000-01-05 2001-07-16 Harry E. Emerson Iii Enhanced radio data system

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2078468A (en) * 1980-06-09 1982-01-06 British Broadcasting Corp Broadcast information transmission
EP0290679A1 (fr) * 1987-05-09 1988-11-17 Koninklijke Philips Electronics N.V. Dispositif de réception et de traitement de messages d'information routière
DE3820641A1 (de) * 1988-06-18 1989-12-21 Bosch Gmbh Robert Verfahren zur auswertung von in einem datentelegramm digital codiert empfangener verkehrsnachrichten sowie rundfunkempfaenger

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2078468A (en) * 1980-06-09 1982-01-06 British Broadcasting Corp Broadcast information transmission
EP0290679A1 (fr) * 1987-05-09 1988-11-17 Koninklijke Philips Electronics N.V. Dispositif de réception et de traitement de messages d'information routière
DE3820641A1 (de) * 1988-06-18 1989-12-21 Bosch Gmbh Robert Verfahren zur auswertung von in einem datentelegramm digital codiert empfangener verkehrsnachrichten sowie rundfunkempfaenger

Also Published As

Publication number Publication date
EP0772926A1 (fr) 1997-05-14
DE19518173A1 (de) 1996-11-21

Similar Documents

Publication Publication Date Title
EP0769180B1 (fr) Dispositif pour preparer et fournir des informations destinees au conducteur d'un vehicule
EP1966780B1 (fr) Procede de codage de messages, procede de decodage de messages et recepteur pour recevoir et interpreter des messages
DE3820640C2 (de) Auswerteverfahren digitaler Verkehrsnachrichten
DE2544511A1 (de) Empfaenger mit einer abstimmschaltung mit einer sendersuchanordnung
WO1993009446A1 (fr) Systeme de determination de la position d'objets mobiles
EP0263332A2 (fr) Récepteur pour transmissions radio pour le trafic
WO2000036771A1 (fr) Systeme de transmission binaire
EP0412286B1 (fr) Méthode de reproduction sélective suivant l'itinéraire de messages numériques routiers transmis d'un émetteur vers un récepteur pour véhicule ainsi que récepteur pour véhicule
EP1721299B1 (fr) Procede de sortie d'informations textuelles au moyen d'un affichage
EP0756257A1 (fr) Récepteur radio RDS-TMC
EP0900432B1 (fr) Procede et recepteur pour la selection geographique de messages codes numeriquement
DE19606010A1 (de) Ortsdatenbank für die Ermittlung von Routen innerhalb eines Verkehrswegenetzes
EP0962004B1 (fr) Dispositif et procede servant a donner des informations sur les encombrements de la circulation
EP0725502B1 (fr) Méthode pour le décodage et l'affichage des informations routières numériques radiodiffusées
WO1996037057A1 (fr) Procede de transmission sans fil de messages codes numeriquement pour voies maritimes et/ou navigables et dispositif permettant de recevoir des messages pour voies maritimes et/ou navigables
DE19538876A1 (de) System zur Lagebestimmung von beweglichen Objekten
DE19503417A1 (de) Einrichtung zur Sprachausgabe von digital codierten Verkehrsmeldungen
DE4229654A1 (de) Verfahren zur uebertragung eines audio- und/oder videosignals
DE19637843C2 (de) Verfahren zur Identifizierung eines Verkehrsteilnehmers und Anordnung zur Durchführung des Verfahrens
DE2923121A1 (de) Verfahren und schaltungsanordnung zur vornahme einer plausibilitaetspruefung bezueglich aufeinanderfolgend auftretender zeitinformationen in verkehrssignalanlagen
EP1537382A1 (fr) Procede et dispositifs pour utiliser des donnees figurant sous des formats ne pouvant etre traites directement
EP0836292B1 (fr) Méthode et dispositif pour la présentation sélective, selon la région ou se trouve le récepteur, de messages codés numériques radiodiffusés
DE19839413A1 (de) Verfahren zur Verknüpfung von digitalen Verkehrswegenetzbeschreibungen und Ortsdatenbank
DE19822918A1 (de) Einrichtung zur grafischen Markierung eines Straßenverlaufs unter Zuhilfenahme einer Ortsdatenbank
EP1840857A1 (fr) Procédé pour la radiodiffusion de signalements de trafic et récepteur de radiodiffusion

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 1996911923

Country of ref document: EP

AK Designated states

Kind code of ref document: A1

Designated state(s): CZ HU PL

AL Designated countries for regional patents

Kind code of ref document: A1

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

121 Ep: the epo has been informed by wipo that ep was designated in this application
WWP Wipo information: published in national office

Ref document number: 1996911923

Country of ref document: EP

WWW Wipo information: withdrawn in national office

Ref document number: 1996911923

Country of ref document: EP