EP1145210B1 - Method for identifying events which cover more than one segment using segments - Google Patents
Method for identifying events which cover more than one segment using segments Download PDFInfo
- Publication number
- EP1145210B1 EP1145210B1 EP99964419A EP99964419A EP1145210B1 EP 1145210 B1 EP1145210 B1 EP 1145210B1 EP 99964419 A EP99964419 A EP 99964419A EP 99964419 A EP99964419 A EP 99964419A EP 1145210 B1 EP1145210 B1 EP 1145210B1
- Authority
- EP
- European Patent Office
- Prior art keywords
- traffic information
- segments
- segment
- transmitted
- terminal device
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Lifetime
Links
Images
Classifications
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G1/00—Traffic control systems for road vehicles
- G08G1/09—Arrangements for giving variable traffic instructions
- G08G1/091—Traffic information broadcasting
- G08G1/092—Coding or decoding of the information
Definitions
- the invention relates to a method for decoding from a traffic center a terminal with traffic information transmitted by radio Road network.
- Traffic information from a traffic information center by radio End devices that can be found in vehicles, for example status data, such as travel times, average speed etc., in Segments (roads, road sections, roadways, road sections of Roads) of a road network.
- the document EP 0 347 354 A1 discloses a method for the transmission and decoding of traffic information transmitted from a traffic information center to a terminal.
- the state of the at least one segment of the road network The relevant traffic information is located in the direction of travel Segment-related manner stored in the terminal.
- the object of the present invention is the most efficient, reliable, simple Realizable optimization of traffic information, which reduces the amount of data transferred allowed.
- the task is performed by the independent Claims resolved.
- the invention allows a reduction in the amount of data from the Traffic control center for traffic information to be transmitted to a terminal.
- a match of two segments in comparison may also be a match of three, four, five or more than five segments in the Comparison in the terminal as a prerequisite for the definition of the status data of the older traffic information than the segments in the current traffic information be fixed regarding.
- Agreement between the control center and the end device should be the type of prescribed Concern match; in particular, it should include whether at least two (or at least more than two, see above) segments must match or whether one (or two or three or more than three) segments must match and one additionally transmitted (or in the direction-specific segment number implied) directional information regarding the direction of travel must match, contain.
- the method for decoding is in the terminal, for example, as an electronic one Circuit or programmable can be implemented; however, it is by design as a program neither defined nor restricted.
- Figure 1 shows a section of a road network.
- Roads or sections of roads or lanes or sections of lanes one Road network can be represented by segments.
- the in Figure 1 of road leading left to right is, for example, by segments 4712, 4713, 4714, 4715, 4716, 4717 specified at least in the local area shown.
- In this Traps are in a segment 4712 all lanes with the different Directions included. It is also possible in a section of a street Segments for one or all lanes in 9998 in one direction and one segment 9999 for one or (as here) all lanes in the opposite direction set.
- the Segments 2243 to 2246 specified.
- the segment digits can be transmitted in Traffic data is transmitted decoded in the usual ways; you can for example, with a bit length that is up to 10,000 segments can define (14 bit).
- FIG. 2 shows an example from a central station 1 to a terminal 2 via a radio channel 3 transmitted traffic information 4 to 7.
- the control center 1 receives from different information sources Traffic information which is stored in a memory 9.
- the Sources of information 8 can be floating in particular in traffic Traffic detectors in the form of traffic reporting devices in vehicles (FCD), stationary detectors arranged along the streets of the traffic network, historical data etc. Processes for revising the are not shown here traffic information received from the information sources 8 to end devices traffic information to be sent through interpolation, interpretation, etc.
- the Information from the memory 9 is (if necessary after appropriate preprocessing) from a traffic information packet generation device 10 with access to FIG a memory 11 stored segment tables (to segments of the Road traffic network according to Figure 1) encoded in a form to be transmitted. Of The transmission device 12 transmits the traffic information to terminals 2 transmitted.
- the transmission can be in particular via radio, for example RDS-TMC respectively.
- the determination can in particular also be carried out by mobile radio.
- mobile radio Via mobile radio
- a cell broadcast transmission in GSM can be, for example, an SMS-CB.
- the traffic information 4 sent from the central office to a plurality of terminals 2 to 7 can in cellular cell broadcast messages (SMS-CB) for cells or Cell groups can be sent out individually (i.e. with different contents).
- SMS-CB cellular cell broadcast messages
- radio cells of a mobile radio network it is thus possible in radio cells of a mobile radio network to only those there to transfer relevant information, for example in the city area Düsseldorf only information related to the Düsseldorf city area and no information Information regarding Kunststoff, accordingly only on a motorway Information on the motorway in the direction of travel and not far away or in Information relating to motorways segments lying in a different direction of travel.
- the traffic information 4, 5, 6, 7 is in this order from a center all terminals 2 in a specific cell or cell group per Cellular cell broadcast broadcast.
- the traffic information 4, 5, 6 contains, for example, status data 19, which the State of segments represented in the traffic information 4 to 6.
- Status data can include travel times or speeds in Specify the specified accuracy.
- the segments on which status data is based in traffic information 4 are referred to here by a in the control center (11) and in the terminal (14) saved segment table defined identically. So only the numbers of the segments, here 4711, 4712, 4713, 4714 for the four of the traffic information 4 transferred affected segments. The same applies to traffic information 5, 6. In traffic information 7, however, certain or all status data are do not transfer. No traffic data is shown in traffic information 7 here, So only the segment data "4716,4715, 1714, 4713" from the headquarters 1 to the Transfer terminal 2. Nevertheless, the terminal can determine according to the invention Assign certain status data such as traffic jams etc. to segments of the transport network.
- the terminal checks in a decoding and comparison device 15 for over one Receiving device 16 (for mobile radio or RDS-TMC) received in one Memory 14 (for older and current traffic information, segment tables and Status tables) stored traffic information 7 whether a match identities of at least one of the segments in older traffic information (4, 5 or 6) and one of the segments of the current traffic information (7) and Agreement of segments representing the direction of travel further information (especially in the current (7) and older (4, 5 or 6) Traffic information).
- This review is done by comparing the Segments and in the direction of information representing the current Traffic information 7 one after the other individually with the older ones Traffic information 4, 5, 6 carried out. In this case, a Correspondence of the segment 4714 in the traffic information 7 and in the older traffic information 5 and 4 found.
- the information representing affected lanes in the segments is here Sequence of the transmission and storage of another device on the device checked the first segment of the adjacent segment, in this case segment 4713.
- traffic information 4 4713 is transmitted before 4714, while it is in the older one Traffic information 5 as well as in the new traffic information 7 after 4714 is transmitted. This is 5 in the older traffic information and in the newer Traffic information 7 designated driving direction identical.
- the Traffic information 5 and 7 at least partially matching sections a street. It is therefore assumed that the state data in the older traffic information 5 also represented the traffic jam in the current one Traffic information 7 affected segments, namely all specified there Affect segments (4716, 4715, 4714, 4713). It is considered for example assumed that a traffic jam has partially shifted.
- segments according to Figure 1 segment 9998 and 9999, each individually for all lanes of a direction of travel of a road section are sufficient the match of a segment (for example 9998) in the older ones Traffic information and current traffic information to a Assume agreement and the state data of the older Traffic information as segments relating to the current traffic information define, since here the direction of travel is already defined in a single segment is. If one for all lanes (even in different directions) Street section together only one segment is defined, the direction of travel affected lanes by the order of transmitting segments or by a direction flag transmitted to a segment can be determined.
- the output 18 in FIG. 2 can, for example, be optically or acoustically in the form of Congestion notices etc. are given.
- Output traffic information 18 can for example, directly from the transmitted traffic information according to their Decoding can be obtained.
- the traffic information to be output 18 can also be navigation instructions, which are based on the transmitted Traffic information is created for the end user.
- FIG. 3 shows the traffic information 4 to 7 transmitted in the list Order of their transmission.
Abstract
Description
Die Erfindung betrifft ein Verfahren zur Dekodierung von von einer Verkehrszentrale an ein Endgerät per Funk übertragenen Verkehrsinformationen betreffend ein Straßenverkehrsnetz.The invention relates to a method for decoding from a traffic center a terminal with traffic information transmitted by radio Road network.
Verkehrsinformationen, welche von einer Verkehrsinformationszentrale per Funk an Endgeräte, die sich beispielsweise in Fahrzeugen befinden können, übertragen werden, können Zustandsdaten, wie Reisezeiten, Durchschnittsgeschwindigkeit etc., in Segmenten (Straßen, Straßenabschnitte, Fahrbahnen, Fahrbahnabschnitte von Straßen) eines Straßenverkehrsnetzes betreffen.Traffic information from a traffic information center by radio End devices that can be found in vehicles, for example status data, such as travel times, average speed etc., in Segments (roads, road sections, roadways, road sections of Roads) of a road network.
Die Identifikation der in von einer Zentrale an ein Endgerät übertragenen Verkehrsinformationen betroffenen Segmente eines Straßenverkehrsabschnittes erfolgt üblicherweise dadurch, daß in einem Satz von Verkehrsinformationen einen bestimmten Zustand (= Ereignis) repräsentierende Zustandsdaten und von diesem Zustand betroffene Segmente durch die Segmentidentitäten angebende Segmentdaten in der Übertragung angegeben werden.The identification of those transmitted from a central to a terminal Traffic information affected segments of a road traffic section usually takes place in that a set of traffic information state data representing certain state (= event) and from this Condition of affected segments by the segment identifiers Segment data can be specified in the transfer.
Die Schrift EP 0 347 354 A1 offenbart ein Verfahren zur Übertragung und Dekodierung von von einer Verkehrsinformationszentrale an ein Endgerät übertragenen Verkehrsinformationen. Die den Zustand des mindestens ein Segment des Straßenverkehrsnetztes betreffenden Verkehrsinformationen werden in einer die in Fahrtrichtung liegenden Segmente betreffenden Weise im Endgerät gespeichert.The document EP 0 347 354 A1 discloses a method for the transmission and decoding of traffic information transmitted from a traffic information center to a terminal. The state of the at least one segment of the road network The relevant traffic information is located in the direction of travel Segment-related manner stored in the terminal.
Aufgabe der vorliegenden Erfindung ist eine möglichst effiziente, zuverlässige, einfach realisierbare Optimierung der Verkehrsinformation, welche eine Verringerung der übertragenen Datenmenge erlaubt. Die Aufgabe wird jeweils durch die unabhängigen Ansprüche gelöst.The object of the present invention is the most efficient, reliable, simple Realizable optimization of traffic information, which reduces the amount of data transferred allowed. The task is performed by the independent Claims resolved.
Die Erfindung ermöglicht eine Reduktion der Datenmenge der von der Verkehrszentrale an ein Endgerät zu übertragenden Verkehrsinformationen. Dadurch, daß in aktuell vom Endgerät empfangenen Verkehrsinformationen und in vom Endgerät davor empfangenen älteren Verkehrsinformationen repräsentierte, durch die in den Verkehrsinformationen repräsentierten Zustandsdaten betroffenen Segmente identifizierende Segmentinformationen sowie die Fahrtrichtung der betroffenen Segmente angebende weitere Informationen (entweder zusätzliche Fahrtrichtungsinformationen oder implizite Fahrtrichtungsinformationen enthalten in der Reihenfolge übertragener Segmente oder gespeicherter Segmente) verglichen werden, wobei nur bei Übereinstimmung im Vergleich die Zustandsinformationen der älteren Verkehrsinformationen den Segmenten der aktuellen Verkehrsinformation zugeordnet werden, kann die übertragene Datenmente erheblich reduziert werden. So kann beispielsweise wenn in älteren Verkehrsinformationen als Zustandsinformationen die Angabe "Stau" und als Segmentinformationen beispielsweise zwei Segmente in einer bestimmten Reihenfolge übertragen und gespeichert wurden, in einer neuen aktuellen Verkehrsinformation lediglich eine Segmentkette von der Zentrale an das Endgerät übertragen werden, welche diese mindestens zwei Segmente in der gleichen Reihenfolge enthält. Somit kann auch wenn sich ein Stau ausgeweitet oder verkürzt oder an einem Ende ausgeweitet und am anderen verkürzt hat, allein durch Angabe der Segmente (bzw. eines Segmentes und dessen Fahrtrichtung) ohne wiederholte Angabe dieser speziellen Zustandsinformationen eine vollständig dekodierbare Verkehrsinformation von der Zentrale an das Endgerät mit geringer Datenmenge übertragen werden. Anstatt einer Übereinstimmung von zwei Segmenten im Vergleich kann auch eine Übereinstimmung von drei, vier, fünf oder mehr als fünf Segmenten im Vergleich im Endgerät als Voraussetzung für die Definition der Zustandsdaten der älteren Verkehrsinformation als die Segmente in der aktuellen Verkehrsinformation betreffend festgelegt sein. Durch übereinstimmende Ausbildung der Vorschriften zur Definition in der Verkehrszentrale und im Endgerät wird die Schaffung eines datenmengenreduzierten Übertragungsprotokolls ermöglicht. Die Übereinstimmung zwischen der Zentrale und dem Endgerät sollte die Art der vorgeschriebenen Übereinstimmung betreffen; sie sollte insbesondere umfassen, ob mindestens zwei (oder mindestens mehr als zwei, s. oben) Segmente übereinstimmen müssen oder ob ein (oder zwei oder drei oder mehr als drei) Segment übereinstimmen muß und eine zusätzlich übertragene (oder in der fahrtrichtungsspezifischen Segmentnummer implizierte) Richtungsinformation betreffend die Fahrtrichtung übereinstimmen muß, enthalten.The invention allows a reduction in the amount of data from the Traffic control center for traffic information to be transmitted to a terminal. Thereby, that in traffic information currently received by the terminal and in from Represented earlier traffic information received by the terminal by which Segments affected in the traffic information represented status data identifying segment information and the direction of travel of the affected Additional information indicating segments (either additional Direction information or implicit direction information contained in the Order of transmitted segments or stored segments) compared only if the status information of the older traffic information the segments of the current traffic information assigned, the transmitted data mentions can be significantly reduced. So can for example if in older traffic information as status information the indication "traffic jam" and as segment information, for example two segments in transferred and saved in a specific order, in a new one current traffic information only a segment chain from the headquarters to the Terminal are transmitted, which these at least two segments in the same Order contains. This means that even if a traffic jam expands or shortens or expanded at one end and shortened at the other, simply by specifying of the segments (or a segment and its direction of travel) without repeated Specifying this special status information is a fully decodable Traffic information from the control center to the terminal with a small amount of data be transmitted. Instead of a match of two segments in comparison may also be a match of three, four, five or more than five segments in the Comparison in the terminal as a prerequisite for the definition of the status data of the older traffic information than the segments in the current traffic information be fixed regarding. By corresponding training of the regulations for Definition in the traffic center and in the end device will create a data transfer protocol with reduced data volume. Agreement between the control center and the end device should be the type of prescribed Concern match; in particular, it should include whether at least two (or at least more than two, see above) segments must match or whether one (or two or three or more than three) segments must match and one additionally transmitted (or in the direction-specific segment number implied) directional information regarding the direction of travel must match, contain.
Das Verfahren zur Dekodierung ist im Endgerät beispielsweise als elektronische Schaltung oder programmgestützt realisierbar; es ist jedoch durch eine Ausgestaltung als Programm weder definiert noch beschränkt.The method for decoding is in the terminal, for example, as an electronic one Circuit or programmable can be implemented; however, it is by design as a program neither defined nor restricted.
Weitere Merkmale und Vorteile der Erfindung ergeben sich aus den Unteransprüchen und der nachfolgenden Beschreibung eines Ausführungsbeispiels anhand der Zeichnung. Dabei zeigt.
- Fig. 1
- beispielhaft ein auf eine digitale Karte mit Straßenabschnitten oder Fahrbahnabschnitten repräsentierenden Segmenten abgebildetes Straßenverkehrsnetz,
- Fig. 2
- als Blockschaltbild eine Zentrale, ein Endgerät und von der Zentrale an das Endgerät übertragene und dort bearbeitete Verkehrsinformationen, und
- Fig. 3
- eine beispielhafte Liste von übertragenen Verkehrsinformationen.
- Fig. 1
- an example of a road traffic network depicted on a digital map with road segments or road segments,
- Fig. 2
- as a block diagram, a control center, a terminal and traffic information transmitted from the control center to the terminal and processed there, and
- Fig. 3
- an exemplary list of transmitted traffic information.
Figur 1 zeigt einen Ausschnitt eines Straßenverkehrsnetzes. Straßen oder Abschnitte
von Straßen oder Fahrbahnen oder Abschnitte von Fahrbahnen eines
Straßenverkehrsnetzes können durch Segmente repräsentiert sein. Die in Figur 1 von
links nach rechts führende Straße ist beispielsweise durch die Segmente 4712, 4713,
4714, 4715, 4716, 4717 zumindest im dargestellten Ortsbereich angegeben. In diesem
Falle sind in einem Segment 4712 alle Fahrbahnen mit den verschiedenen
Fahrtrichtungen enthalten. Ebenso ist es möglich, in einem Abschnitt einer Straße
Segmente für eine oder alle Fahrbahnen in 9998 in eine Richtung und ein Segment
9999 für eine oder (wie hier) alle Fahrbahnen in die entgegengesetzte Richtung
festzulegen.Figure 1 shows a section of a road network. Roads or sections
of roads or lanes or sections of lanes one
Road network can be represented by segments. The in Figure 1 of
road leading left to right is, for example, by
In einer in Figur 1 von unten nach oben führenden Straße sind ferner beispielhaft die
Segmente 2243 bis 2246 angegeben. Die Segment-Ziffern können in übertragenen
Verkehrsdaten in üblichen Weisen dekodiert übertragen werden; sie können
beispielsweise mit einer Bitlänge übertragen werden, die bis zu 10.000 Segmente
definieren kann (14 Bit).In a road leading from bottom to top in FIG. 1, the
Figur 2 zeigt beispielhaft von einer Zentrale 1 an ein Endgerät 2 über einen Funkkanal
3 übertragene Verkehrsinformationen 4 bis 7.FIG. 2 shows an example from a
Die Zentrale 1 erhält aus unterschiedlichen Informationsquellen
Verkehrsinformationen, welche in einem Speicher 9 abgespeichert werden. Die
Informationsquellen 8 können insbesondere im Verkehr mitschwimmende
Verkehrsdetektoren in Form von Verkehrsmeldegeräten in Fahrzeugen (FCD),
stationäre, entlang der Straßen des Verkehrsnetzes angeordnete Detektoren,
historische Daten etc. sein. Nicht dargestellt sind hier Verfahren zur Überarbeitung der
aus den Informationsquellen 8 empfangenen Verkehrsinformationen zu an Endgeräte
zu sendenden Verkehrsinformationen durch Interpolation, Interpretation usw. Die
Informationen aus dem Speicher 9 werden (ggf. nach entsprechender Vorbearbeitung)
von einer Verkehrsinformationspaket-Generierungseinrichtung 10 unter Zugriff auf in
einem Speicher 11 gespeicherte Segmenttabellen (zu Segmenten des
Straßenverkehrsnetzes entsprechend Figur 1) in eine zu sendende Form kodiert. Von
der Sendeeinrichtung 12 werden die Verkehrsinformationen an Endgeräte 2
übermittelt. Die Übermittlung kann insbesondere per Radio, beispielsweise RDS-TMC
erfolgen. Die Ermittlung kann insbesondere auch per Mobilfunk erfolgen. Per Mobilfunk
ist neben einer Point-to-Point-Übertragung eine Zell-Rundspruch-Übertragung möglich.
Eine Zell-Rundspruch-Übertragung kann in GSM beispielsweise eine SMS-CB sein.
Die von der Zentrale an mehrere Endgeräte 2 ausgesendeten Verkehrsinformationen 4
bis 7 können bei Mobilfunk-Zell-Rundspruch-Nachrichten (SMS-CB) für Zellen oder
Zellengruppen individualisiert (also unterschiedlichen Inhalts) ausgesendet werden.
Damit ist es möglich, in Funkzellen eines Mobilfunknetzes nur die dort möglicherweise
relevanten Informationen zu übertragen, also beispielsweise im Stadtbereich
Düsseldorf nur den Stadtbereich Düsseldorf betreffende Informationen und keine
Informationen betreffend München, entsprechend auf einer Autobahn nur diese
Autobahn in Fahrtrichtung betreffende Informationen und nicht weitab liegende oder in
anderer Fahrtrichtung liegende Autobahnen-Segmente betreffende Informationen. The
Die Verkehrsinformation 4, 5, 6, 7 werden in dieser Reihenfolge von einer Zentrale an
alle Endgeräte 2 in einer bestimmen Mobilfunkzelle oder Mobilfunkzellengruppe per
Mobilfunk-Zell-Rundspruch ausgesendet.The
Die Verkehrsinformationen 4, 5, 6 enthalten beispielsweise Zustandsdaten 19, welche den
Zustand von in den Verkehrsinformationen 4 bis 6 repräsentierte Segmenten betreffen.
Zustandsdaten können beispielsweise Reisezeiten oder Geschwindigkeiten in
vorgegebener Genauigkeit angeben. Die Quantisierung (= Genauigkeit) kann
insbesondere vier oder fünf Stufen beinhalten, beispielsweise Stau, stockender
Verkehr, zähfließender Verkehr, geringer Verkehr, frei. Bei einer Quantisierung in vier
Stufen ist eine Übertragung mit 2 Bit bei einer Quantisierung in weniger als acht Stufen
in 3 Bit möglich.The
Die Segmente, auf welche sich Zustandsdaten in einer Verkehrsinformation 4
beziehen, werden hier durch eine in der Zentrale (11) und im Endgerät (14)
gespeicherten Segmenttabelle identisch definiert. Somit werden lediglich die Nummern
der Segmente, hier 4711, 4712, 4713, 4714 für die vier von der Verkehrsinformation 4
betroffenen Segmente übertragen. Entsprechendes gilt für die Verkehrsinformationen
5, 6. In der Verkehrsinformation 7 werden jedoch bestimmte oder alle Zustandsdaten
nicht mitübertragen. Hier werden in der Verkehrsinformation 7 keine Zustandsdaten,
also nur die Segmentdaten "4716,4715, 1714, 4713" von der Zentrale 1 an das
Endgerät 2 übertragen. Dennoch kann das Endgerät erfindungsgemäß bestimmten
Segmenten des Verkehrsnetzes bestimmte Zustandsdaten, wie Stau etc., zuordnen.The segments on which status data is based in
Das Endgerät überprüft in einer Dekodier- und Vergleichseinrichtung 15 für über eine
Empfangseinrichtung 16 (für Mobilfunk oder RDS-TMC) empfangene, in einem
Speicher 14 (für ältere und aktuelle Verkehrsinformationen, Segmenttabellen und
Zustandstabellen) gespeicherte Verkehrsinformationen 7, ob eine Übereinstimmung
von Identitäten mindestens eines der Segmente in älteren Verkehrsinformationen (4, 5
oder 6) und eines der Segmente der aktuellen Verkehrsinformation (7) sowie
Übereinstimmung von die Fahrtrichtung betroffener Segmente repräsentierender
weiterer Informationen (insbesondere in den aktuellen (7) und älteren (4, 5 oder 6)
Verkehrsinformationen) besteht. Diese Überprüfung wird durch Vergleich der
Segmente und in die Richtung repräsentierender Informationen der aktuellen
Verkehrsinformationen 7 jeweils nacheinander einzeln mit den älteren
Verkehrsinformationen 4, 5, 6 durchgeführt. In diesem Falle wird eine
Übereinstimmung des Segmentes 4714 in der Verkehrsinformation 7 sowie in den
älteren Verkehrsinformationen 5 und 4 festgestellt. Als weitere die Richtung
betroffener Fahrbahnen in den Segmenten repräsentierende Information wird hier die
Reihenfolge der Übermittlung und endgerätseitigen Speicherung eines weiteren dem
ersteren Segment benachbarten Segmentes überprüft, also hier des Segmentes 4713.
In der Verkehrsinformation 4 ist 4713 vor 4714 übermittelt, während es in der älteren
Verkehrsinformation 5 ebenso wie in der neuen Verkehrsinformation 7 nach 4714
übermittelt ist. Somit ist die in der älteren Verkehrsinformation 5 und in der neueren
Verkehrsinformation 7 bezeichnete Fahrtrichtung identisch. Somit betreffen die
Verkehrsinformationen 5 und 7 zumindest teilweise übereinstimmende Abschnitte
einer Straße. Deshalb wird angenommen, daß der durch die Zustandsdaten in der
älteren Verkehrsinformation 5 repräsentierte Stau auch die in den aktuellen
Verkehrsinformationen 7 betroffenen Segmente, und zwar alle dort angegebenen
Segmente (4716, 4715, 4714, 4713) betreffen. Es wird als beispielsweise
angenommen, daß sich ein Stau teilweise verschoben hat.The terminal checks in a decoding and
Wenn Segmente, entsprechend Figur 1 Segment 9998 und 9999, jeweils einzeln für
alle Fahrbahnen einer Fahrtrichtung eines Straßenabschnittes definiert werden, reicht
die Übereinstimmung eines Segmentes (beispielsweise 9998) in den älteren
Verkehrsinformationen und den aktuellen Verkehrsinformationen, um eine
Übereinstimmung anzunehmen und die Zustandsdaten der älteren
Verkehrsinformation als Segmente der aktuellen Verkehrsinformation betreffend zu
definieren, da hier in einem einzigen Segment bereits dessen Fahrtrichtung definiert
ist. Wenn für alle Fahrbahnen (auch unterschiedlicher Richtungen) eines
Straßenabschnittes zusammen nur ein Segment definiert wird, kann die Fahrtrichtung
betroffener Fahrbahnen durch die Reihenfolge übertragender Segmente oder durch
ein zu einem Segment übertragenes Richtungsflag bestimmt werden.If segments, according to Figure 1
Bei zumindest teilweiser Übereinstimmung von einem Segment und die Fahrtrichtung implizierenden Daten in einer aktuellen und einer älteren Verkehrsinformation kann somit eine aktuelle Verkehrsinformation sowohl ohne als auch mit Zustandsdaten übertragen und sodann gespeichert (17) werden. With at least partial agreement of a segment and the direction of travel can be implicit data in current and older traffic information thus current traffic information both without and with status data transferred and then saved (17).
Die Ausgabe 18 in Figur 2 kann beispielsweise optisch oder akustisch in Form von
Stauhinweisen etc. erfolgen. Ausgegebene Verkehrsinformationen 18 können
beispielsweise unmittelbar aus den übertragenen Verkehrsinformationen nach ihrer
Dekodierung gewonnen werden. Die auszugebenden Verkehrsinformationen 18
können auch Navigationshinweise sein, welche aufgrund der übertragenen
Verkehrsinformationen für den Endgerätnutzer erstellt werden.The
Figur 3 zeigt als Liste die übertragenen Verkehrsinformationen 4 bis 7 in der
Reihenfolge ihrer Übertragung.FIG. 3 shows the
Claims (21)
- Method of decoding (15) traffic information (4, 5, 6; 7) transmitted from a central traffic information unit (1) to a terminal device (2) and relating to a road network (4712, 4713 ...),
where transmitted traffic information (4 to 7) represents at least the status of at least one segment (4714, 4713) of the road network and the identity ("4714", "4713") of the segment
where the terminal device (2) stores the segment data ("4712"...) representing the segments affected by the traffic information (4, 5, 6, 7) received as a result of transmission, in a manner which represents the direction of travel of the affected carriageways in the affected segments, and stores the status data representing the status of the segment,
characterised in that
the terminal device (2) compares segments (4716, 4715, 4714, 4713) represented in current traffic information (7) transmitted to it with segments represented in older traffic information (4; 5; 6) transmitted before this current traffic information (7)
and in that
where there is a match between the identity of at least one of the segments (4713) of the older traffic information (5) and one of the segments of the current traffic information (7), and where there is a further match of the direction of travel in these segments (4713, 4713), the terminal device (2) defines the status data (4) stored in respect of this older traffic information (5) as relating to the segments (4716, 4715, 4714, 4713) given in the current traffic information (7), and uses it (17) for output (18) to the user of the device. - Method as in Claim 1,
characterised in that in the central traffic information unit (1) and the terminal device (2), a segment represents an entire road or all or some of the carriageways in a single direction on a road. - Method as in one of the preceding Claims,
characterised in that in the central traffic information unit (1) and the terminal device (2), a segment represents a section of a road (4712) or a section of all or some of the carriageways in a single direction (9998) on a road. - Method as in one of the preceding Claims,
characterised in that
status data, quantised into two, three, four, five or more than five stages, represent the speeds or journey times in at least one segment. - Method as in one of the preceding Claims,
characterised in that
status data represent weather data in at least one segment. - Method as in one of the preceding Claims,
characterised in that
status data represent accidents of diversions in at least one segment. - Method as in one of the preceding Claims,
characterised in that
traffic information is transmitted by radio, particularly by RDS-TMC. - Method as in one of the preceding Claims,
characterised in that
traffic information is transmitted by mobile telephony. - Method as in Claim 8,
characterised in that
traffic information is transmitted by cellular broadcast bulletin (GSM CB3). - Method as in Claim 9,
characterised in that
the transmitted traffic information (4 to 7) is different in different mobile telephony cells or cell groups, especially in that it is broadcast selectively for its relevance to the locality. - Method as in one of the preceding Claims,
characterised in that
several older items of traffic information (4; 5; 6) are present in the terminal device, and are each compared with at least one current traffic information item. - Method as in one of the preceding Claims,
characterised in that
several current traffic information items are stored in the terminal device. - Method as in one of the preceding Claims,
characterised in that
status data (19) of an older traffic information item (5) are defined, in relation to the direction of travel, as current traffic information (7) on the basis of additional information in the current and older traffic information, if at least two stored segment identities (4714, 4713) and their sequence match in the memory. - Method as in one of the preceding Claims,
characterised in that
status data of an older traffic information item (5) are defined as segments of a current traffic information item (7) if there is agreement between at least one segment identity and information transmitted or present in the terminal device and representing the direction of travel of the carriageway affected in the segment. - Method as in one of the preceding Claims,
characterised in that
in the transmitted traffic information (4 to 7) on the transmission path (3) from the central traffic information unit (1) to the terminal device (2), are represented
a string (4716, 4715, 4714, 4713) of several segments which follow one another in one direction of travel by means of its first (4716) or last (4713) segment and the number - e.g. 4 - of the segments in the string,
and a direction indication representing the direction in which the string extends from the first segment (4716) to the last segment (4713). - Method as in one of the preceding Claims,
characterised in that
the current traffic information (7) are transmitted without any status data (19) from the central unit (1) to the terminal device (2) if, in the segments contained in the current traffic information, at least one matches a segment in an older traffic information (5). - Method as in Claim 16,
characterised in that
transmission without status data takes place only if there is agreement between at least two segments in the current status data and any older status data transmitted earlier. - Terminal device, in particular to implement the method as in one of the preceding Claims, havingcharacterised bya receiver (16) for receiving traffic information (4 to 7) transmitted from a central traffic information unit (1) by radio,a memory device (14) for storing transmitted traffic information
a comparison device (15) for comparing segments represented in older traffic information with segments represented in current traffic information (7), which is made in such a way that the terminal device compares (15) segments represented in current traffic information transmitted to it with segments represented in older traffic information (5) transmitted prior to this current traffic information,
where the terminal device (2) is made in such a way that, where there is agreement between the identities of at least one of the segments (4713) of the current traffic information and of the older traffic information, and of the direction of travel affected in the segments compared, it defines (15) the stored status data (19) on this older traffic information as relating to the segments (4716, 4715, 4714, 4713) given in the current traffic information, and prepares it for output (18) to the user of the device. - Terminal device as in Claim 18,
characterised in that
the receiver is a radio receiver, in particular an RDS-TMC receiver. - Terminal device as in Claim 18,
characterised in that
the receiver is a mobile telephony receiver for decoding information transmitted by mobile telephony. - Central traffic information unit, in particular for implementing the method as in one of Claims 1 to 17, havingcharacterised bya transmitter (12) for transmitting traffic information,a memory device (9) for traffic information which is to be transmitted,
a traffic information package generation device (10), which is made in such a way that traffic information (7) for current transmission is made up, for transmission by a transmitter (12), of segment information designating segments of a road network without status information relating to the traffic in these segments if the status information relating to at least one of these segments was already contained in an older traffic information item, the segment data of which represent at least one segment (4713) the same as the current traffic information,
while the traffic information package generation device (10) otherwise gives the status data of the affected segments in traffic information for current transmission.
Applications Claiming Priority (5)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| DE19859598 | 1998-12-14 | ||
| DE19859598 | 1998-12-14 | ||
| DE19917842 | 1999-04-13 | ||
| DE19917842A DE19917842A1 (en) | 1998-12-14 | 1999-04-13 | Traffic data distribution system provides data to user terminals which compare past and current data to provide traffic advice |
| PCT/DE1999/003950 WO2000039774A2 (en) | 1998-12-14 | 1999-12-06 | Method for identifying events which cover more than one segment using segments |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| EP1145210A2 EP1145210A2 (en) | 2001-10-17 |
| EP1145210B1 true EP1145210B1 (en) | 2002-09-11 |
Family
ID=26050985
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| EP99964419A Expired - Lifetime EP1145210B1 (en) | 1998-12-14 | 1999-12-06 | Method for identifying events which cover more than one segment using segments |
Country Status (6)
| Country | Link |
|---|---|
| US (1) | US6618667B1 (en) |
| EP (1) | EP1145210B1 (en) |
| JP (1) | JP2002533854A (en) |
| AT (1) | ATE224086T1 (en) |
| ES (1) | ES2181497T3 (en) |
| WO (1) | WO2000039774A2 (en) |
Families Citing this family (21)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7096115B1 (en) | 2003-09-23 | 2006-08-22 | Navteq North America, Llc | Method and system for developing traffic messages |
| JP2005181219A (en) * | 2003-12-22 | 2005-07-07 | Aisin Aw Co Ltd | Information delivery system and program for information delivery method |
| KR20060119739A (en) * | 2005-05-18 | 2006-11-24 | 엘지전자 주식회사 | Method and apparatus for providing prediction information on travel time for a link and using the information |
| KR20060119746A (en) * | 2005-05-18 | 2006-11-24 | 엘지전자 주식회사 | Method and apparatus for providing transportation status information and using it |
| KR20060119742A (en) * | 2005-05-18 | 2006-11-24 | 엘지전자 주식회사 | Method and apparatus for providing link information and using the information |
| WO2006123903A1 (en) * | 2005-05-18 | 2006-11-23 | Lg Electronics Inc. | Fourniture d'information de trafic comprenant des sous liaisons de liaisons |
| 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 |
| KR100711866B1 (en) * | 2005-05-18 | 2007-04-25 | 엘지전자 주식회사 | Method and apparatus for providing prediction information on traffic and using the information |
| KR20060119743A (en) | 2005-05-18 | 2006-11-24 | 엘지전자 주식회사 | Method and apparatus for providing prediction information on average speed on a link and using the information |
| KR20060119741A (en) * | 2005-05-18 | 2006-11-24 | 엘지전자 주식회사 | Method and apparatus for providing information on congestion tendency on a link and using the information |
| KR20060122668A (en) * | 2005-05-27 | 2006-11-30 | 엘지전자 주식회사 | Method for providing traffic information and apparatus for receiving traffic information |
| US8711850B2 (en) * | 2005-07-08 | 2014-04-29 | Lg Electronics Inc. | Format for providing traffic information and a method and apparatus for using the format |
| EP2128839B1 (en) | 2005-07-08 | 2010-08-25 | LG Electronics Inc. | Providing traffic information including average travel speed for a link and generation time |
| KR101254219B1 (en) * | 2006-01-19 | 2013-04-23 | 엘지전자 주식회사 | method and apparatus for identifying a link |
| DE602007008693D1 (en) * | 2006-01-19 | 2010-10-07 | Lg Electronics Inc | METHOD FOR SENDING AND RECEIVING TRAFFIC INFORMATION AND DEVICE THEREFOR |
| JP4736979B2 (en) * | 2006-06-30 | 2011-07-27 | 日産自動車株式会社 | In-vehicle device, traffic information acquisition method, traffic information providing system, and traffic information providing method |
| US9251703B1 (en) | 2006-09-18 | 2016-02-02 | Here Global B.V. | Methods of providing traffic information and supporting apparatus, readable medium, and memory |
| KR100795586B1 (en) | 2006-09-25 | 2008-01-21 | 주식회사 케이티프리텔 | System and method for providing traffic information in mobile communication network |
| US8180518B2 (en) * | 2008-04-15 | 2012-05-15 | Robert Bosch Gmbh | System and method for determining microenvironment conditions external to a vehicle |
| JP5535711B2 (en) * | 2010-03-24 | 2014-07-02 | アルパイン株式会社 | Car navigation system and traffic information display method |
| US8554468B1 (en) * | 2011-08-12 | 2013-10-08 | Brian Lee Bullock | Systems and methods for driver performance assessment and improvement |
Family Cites Families (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| DE2930509C2 (en) * | 1979-07-27 | 1985-02-14 | ANT Nachrichtentechnik GmbH, 7150 Backnang | Method of transferring information |
| ATE158886T1 (en) * | 1987-05-09 | 1997-10-15 | Koninkl Philips Electronics Nv | FACILITY FOR RECEIVING AND PROCESSING STREET NEWS REPORTS |
| FR2633080B1 (en) * | 1988-06-17 | 1990-11-09 | France Etat | BROADCAST OF INFORMATION MESSAGES, IN PARTICULAR OF ROAD INFORMATION, FOR FIXED OR MOBILE RECEIVERS WITH INTERMITTENT LISTENING |
| DE4008460A1 (en) * | 1990-03-16 | 1991-09-19 | Bosch Gmbh Robert | NAVIGATION SYSTEM |
| JP3632706B2 (en) * | 1994-09-22 | 2005-03-23 | アイシン・エィ・ダブリュ株式会社 | Vehicle navigation device |
| JP3203979B2 (en) * | 1994-10-06 | 2001-09-04 | トヨタ自動車株式会社 | Vehicle data processing system, vehicle data processing device, and vehicle data processing method |
| ES2140713T3 (en) * | 1994-10-07 | 2000-03-01 | Mannesmann Ag | INTRODUCTION OF THE DESTINATION FOR A NAVIGATION SYSTEM. |
| ES2142053T5 (en) * | 1995-03-23 | 2007-03-16 | T-Mobile Deutschland Gmbh | PROCEDURE AND DEVICE FOR THE DETERMINATION OF DYNAMIC TRAFFIC INFORMATION. |
| KR100508807B1 (en) * | 1998-10-10 | 2005-12-21 | 삼성전자주식회사 | Traffic Information Service Method |
-
1999
- 1999-12-06 WO PCT/DE1999/003950 patent/WO2000039774A2/en active IP Right Grant
- 1999-12-06 JP JP2000591598A patent/JP2002533854A/en active Pending
- 1999-12-06 ES ES99964419T patent/ES2181497T3/en not_active Expired - Lifetime
- 1999-12-06 AT AT99964419T patent/ATE224086T1/en not_active IP Right Cessation
- 1999-12-06 EP EP99964419A patent/EP1145210B1/en not_active Expired - Lifetime
- 1999-12-06 US US09/868,085 patent/US6618667B1/en not_active Expired - Lifetime
Also Published As
| Publication number | Publication date |
|---|---|
| US6618667B1 (en) | 2003-09-09 |
| WO2000039774A3 (en) | 2000-09-21 |
| JP2002533854A (en) | 2002-10-08 |
| ES2181497T3 (en) | 2003-02-16 |
| WO2000039774A2 (en) | 2000-07-06 |
| EP1145210A2 (en) | 2001-10-17 |
| ATE224086T1 (en) | 2002-09-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP1145210B1 (en) | Method for identifying events which cover more than one segment using segments | |
| EP1141909B1 (en) | Method for transmitting traffic information | |
| EP1151428B1 (en) | Method and device for obtaining relevant traffic information and dynamic route optimizing | |
| EP0902406B1 (en) | Method for transmitting traffic data and for analysing the road traffic network, traffic-evaluating central unit and terminal therefor | |
| EP0769181B1 (en) | Device for providing a vehicle driver with information | |
| EP1224645B2 (en) | Method for coding and decoding objects in a road traffic network | |
| EP0584310B1 (en) | Road traffic radio receiver | |
| DE19606258C1 (en) | Vehicle autonomous traffic jam detection method | |
| EP1966780B1 (en) | Method for coding messages, method for decoding messages and receiver for receiving and evaluating messages | |
| EP1214697B1 (en) | Method for encoding and decoding objects with reference to a road network | |
| EP1079353A2 (en) | Method for requesting and processing traffic messages | |
| DE19857782A1 (en) | Method for transmitting table information from a control center to a terminal via a transmission channel and control center for carrying out the method | |
| EP0790591B1 (en) | Locationdatabase for determining routes within a road traffic network | |
| EP1460599B1 (en) | Database for coding and decoding of traffic messages and method for transmitting coded traffic messages | |
| DE19729914A1 (en) | Process for the analysis of a traffic network, traffic analysis, traffic forecast as well as creation of a historical traffic database and traffic analysis and forecasting center | |
| DE102007032956B4 (en) | Vehicle navigation system in a network with navigation systems of other vehicles with filtering of the data input and for the detection of traffic disruptions | |
| EP1141911B1 (en) | Device for transmitting route recommendations and receiver | |
| DE19917842A1 (en) | Traffic data distribution system provides data to user terminals which compare past and current data to provide traffic advice | |
| DE10052934A1 (en) | Method for determining a path between a starting point and an end point of a network, such as a road network | |
| EP0984416B1 (en) | Process to link digital road traffic network descriptions and a location database | |
| DE19941648C2 (en) | Method for transmitting traffic information relating to a road traffic network from a traffic information center to at least one terminal, and traffic information center and terminal for carrying out the method | |
| DE102022128927A1 (en) | Procedures for influencing traffic | |
| DE19948109A1 (en) | Generation of traffic information in the case of states extending over several linked segments of a road traffic network | |
| EP1011219A2 (en) | Method and means for producing traffic information concerning traffic situations covering a plurality of mutually interconnected segments of a road traffic system | |
| EP1619642A2 (en) | Method for transmitting digitally coded messages in data groups and receiver |
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: 20010606 |
|
| AK | Designated contracting states |
Kind code of ref document: A2 Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE |
|
| XX | Miscellaneous (additional remarks) |
Free format text: DERZEIT SIND DIE WIPO-PUBLIKATIONSDATEN A3 NICHT VERFUEGBAR. |
|
| RIN1 | Information on inventor provided before grant (corrected) |
Inventor name: VIEWEG, STEFAN Inventor name: KRIESINGER, RALF Inventor name: VAN HAUTEN, SWEN Inventor name: BERWANGER, CHRISTIAN |
|
| GRAG | Despatch of communication of intention to grant |
Free format text: ORIGINAL CODE: EPIDOS AGRA |
|
| 17Q | First examination report despatched |
Effective date: 20020125 |
|
| 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 |
|
| RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: VODAFONE AG |
|
| 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 CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IE 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: 20020911 Ref country code: GR 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: 20020911 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: 20020911 |
|
| REF | Corresponds to: |
Ref document number: 224086 Country of ref document: AT Date of ref document: 20020915 Kind code of ref document: T |
|
| REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D Free format text: NOT ENGLISH |
|
| XX | Miscellaneous (additional remarks) |
Free format text: DERZEIT SIND DIE WIPO-PUBLIKATIONSDATEN A3 NICHT VERFUEGBAR. |
|
| REG | Reference to a national code |
Ref country code: CH Ref legal event code: EP |
|
| REG | Reference to a national code |
Ref country code: CH Ref legal event code: NV Representative=s name: E. BLUM & CO. PATENTANWAELTE |
|
| REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D Free format text: GERMAN |
|
| REF | Corresponds to: |
Ref document number: 59902705 Country of ref document: DE Date of ref document: 20021017 |
|
| ET | Fr: translation filed | ||
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LU Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20021206 |
|
| 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: 20021211 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: 20021211 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: CY 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: 20021231 Ref country code: BE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20021231 |
|
| GBT | Gb: translation of ep patent filed (gb section 77(6)(a)/1977) |
Effective date: 20021217 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: PT 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: 20030124 |
|
| REG | Reference to a national code |
Ref country code: ES Ref legal event code: FG2A Ref document number: 2181497 Country of ref document: ES Kind code of ref document: T3 |
|
| REG | Reference to a national code |
Ref country code: IE Ref legal event code: FD4D Ref document number: 1145210E Country of ref document: IE |
|
| RAP2 | Party data changed (patent owner data changed or rights of a patent transferred) |
Owner name: VODAFONE HOLDING GMBH |
|
| BERE | Be: lapsed |
Owner name: *VODAFONE A.G. Effective date: 20021231 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MC Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20030701 |
|
| 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 |
|
| NLT2 | Nl: modifications (of names), taken from the european patent patent bulletin |
Owner name: VODAFONE HOLDING GMBH |
|
| 26N | No opposition filed |
Effective date: 20030612 |
|
| PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: NL Payment date: 20031128 Year of fee payment: 5 |
|
| PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: CH Payment date: 20031201 Year of fee payment: 5 Ref country code: AT Payment date: 20031201 Year of fee payment: 5 |
|
| REG | Reference to a national code |
Ref country code: FR Ref legal event code: CJ Ref country code: FR Ref legal event code: CD |
|
| REG | Reference to a national code |
Ref country code: GB Ref legal event code: 732E |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: AT Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20041206 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20041231 Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20041231 |
|
| REG | Reference to a national code |
Ref country code: FR Ref legal event code: TP |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: NL Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20050701 |
|
| REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
| NLV4 | Nl: lapsed or anulled due to non-payment of the annual fee |
Effective date: 20050701 |
|
| PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: IT Payment date: 20061231 Year of fee payment: 8 |
|
| PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20070628 Year of fee payment: 8 |
|
| PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: ES Payment date: 20070629 Year of fee payment: 8 |
|
| PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20070628 Year of fee payment: 8 |
|
| PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: FR Payment date: 20070629 Year of fee payment: 8 |
|
| GBPC | Gb: european patent ceased through non-payment of renewal fee |
Effective date: 20071206 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20080701 |
|
| REG | Reference to a national code |
Ref country code: FR Ref legal event code: ST Effective date: 20081020 |
|
| 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 NON-PAYMENT OF DUE FEES Effective date: 20071206 |
|
| REG | Reference to a national code |
Ref country code: ES Ref legal event code: FD2A Effective date: 20071207 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: FR Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20071231 Ref country code: ES Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20071207 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IT Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20071206 |