EP1141911B1 - Einrichtung zur übertragung von fahrtroutenempfehlungen und empfänger - Google Patents
Einrichtung zur übertragung von fahrtroutenempfehlungen und empfänger Download PDFInfo
- Publication number
- EP1141911B1 EP1141911B1 EP99973504A EP99973504A EP1141911B1 EP 1141911 B1 EP1141911 B1 EP 1141911B1 EP 99973504 A EP99973504 A EP 99973504A EP 99973504 A EP99973504 A EP 99973504A EP 1141911 B1 EP1141911 B1 EP 1141911B1
- Authority
- EP
- European Patent Office
- Prior art keywords
- locality
- database
- locality database
- route recommendations
- travel route
- 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 device for the transmission of Route recommendations for at least one network of public Transportation to recipients and a recipient for Route recommendations.
- WO 96/00960 is an electronic Timetable information system, in which Information beacons continuously, i.e. without being asked Passengers send data received from handheld terminals become.
- the data concern public transport networks and Timetables can be saved and saved in the hand terminal Timetable information is processed, which is then sent to the user are displayed.
- Such a system requires special for developed and developed this public transport manufactured hand-held terminals.
- the object of the present invention is to provide such To transfer route recommendations if necessary, that the known inexpensive in large quantities manufactured receivers also for the reception of Route recommendations from public transport networks can be used, including a link to the Road network can take place.
- a coding by means of at least one imaging at least parts of the transport network Location database is that for Transfer of route recommendations that are also in at least one location database depicting a road network (Road network location database) relate to stored locations, Records of those places that have at least one neighboring location in the at least one road network location databases have at least one reference to at least one such neighboring location by means of a Cross-reference included.
- a first embodiment of the device according to the invention is that for the transmission of digitally encoded Traffic reports (TMC) provided data protocols be used.
- TMC Traffic reports
- An RDS-ODA protocol will be set up for transmission used.
- the device according to the invention has the advantage that the Route recommendations of a large number available Receiving devices can be received and decoded.
- Receiving devices there are currently essentially car radios for receiving digitally coded traffic reports - both in Relation to RDS (radio data system) and as well DAB (Digital Audio Broadcasting).
- RDS radio data system
- DAB Digital Audio Broadcasting
- the invention can also be used with other mobile radio media such as GSM, SWIFT, UMTS.
- the receiver is installed in a vehicle that has a location system (e.g. GPS) or a Navigation system can also select the Route recommendations according to the selection of the Traffic announcements are made that the recipient receives only those route recommendations that are likely to be of importance to the user.
- a location system e.g. GPS
- a Navigation system can also select the Route recommendations according to the selection of the Traffic announcements are made that the recipient receives only those route recommendations that are likely to be of importance to the user.
- the device according to the invention also has the advantage that for route recommendations, for which also data from Road networks are needed, for example the Traffic flow on roads and highways are taken into account is that for the TMC system or similar systems automatically recorded data can be used.
- the route recommendations are longer than a traffic report transmitted by the TMC system, e.g. traffic jam, 5 km in length, A7 motorway, junction Hildesheim. That is why according to a training course provided that the route recommendations as Multi-group messages are transmitted.
- An advantageous recipient for route recommendations at least one public transport consists of that for decoding in the receiver at least one at least Location database depicting parts of the transport network (Traffic network location database) is provided and that for Decoding of route recommendations, which are also in at least one location database depicting a road network (Road network location database) relate to stored locations, Records of those places that have at least one neighboring location in the at least one road network location databases have at least one reference to at least one such neighboring location by means of a Cross-reference included.
- Such location databases are preferably on one removable disk, so that the user of a recipient is the one that most interests him Traffic networks available, without location databases for everyone To acquire traffic networks, for example of a country have to.
- the receiver according to the invention can also be used in this way be trained that the location database on a Air interface is upgradeable.
- this receiver are for Management and decoding of route recommendations Digital management and decoding facilities coded traffic reports (TMC) provided.
- TMC coded traffic reports
- Fig. 2 shows an example of a route network, the partly the area of a big city 1 and partly that Surrounding area 2 runs through.
- a tram line 3 leads from one first end point 6 via stops 7, 8, 9, 10 to one second end point 11.
- Stop 8 is a transfer point to a bus line with endpoints 12, 15 and others Stops 13, 14.
- the stop 10 serves as Transfer point to a P + R car park at the junction a highway 5, from which further junctions 16, 17, 18th are shown.
- the route network shown can in the same way as that Road networks are encoded in the TMC system, that is Location databases as described in the ALERT C standard are, the individual places lead in connection with on a line, to any location, for example to the Stop 7, a predecessor 6 and a successor 8 as Cross-reference are provided. Since the transfer point 8 is also a Location on bus line 4, there is an additional one Referencing, such as that used in patent applications 196 06 010 is shown.
- lines 3, 4 of the public Transport network in a specially designed for this Place database shown or in an existing Location database integrated while the Autobahn 5 in one conventional location database within the TMC system corresponding cross-references can be found at the place 10 on the other route (highway or Tram line).
- This can be a message that for example, "use the freeway to Junction 10, then change to tram line 3 towards the final stop 6 to the change point 8 and then use bus line 4 in the direction of end point 12 to Stop 13 "with the usual protocols in the TMC system or protocols defined within the scope of ODA applications encoded and transmitted to the recipient, who then uses its location database (s) a coding and implementation can make in text or speech.
- the one to be transferred Amount of information also deviate from this table. Also, because of the very compact coding, you do not need all message elements to be transferred. So can for example message elements, such as means of transport, Line name, line end point for decoding from the Location database can be taken.
- the bit at position Y15 identifies the first group of a message.
- Each group has a length of 37 bits, which in the Example with X4 to X0, Y15 to 0 and Z15 to Z0 are.
- bits Y13 to Y11 are for Number of transfer points provided.
- bits Y10 to Y0 then moves as a so-called event that this message represents a travel recommendation FE.
- the location of the start S follows, for example the Location code for location 10 in a recommendation, in 10 (Fig. 2) leave the highway and take the tram continue.
- Y13 to Y12 indicate that it is the second group.
- the Destination Z and the location code of the first transfer point U1 which extends into the third group.
- the Transfer location code of transfer point U2 bits Y7 to Z8
- the location code of the changeover point U3 bits Z7 to Z0 and Bits Y11 to Y4 of the next group.
- the location code of a transfer point U5 which also partially transmitted with the fifth group. in the Following this, the travel time T, the tariff zone TZ, the Time type TYPE as well as the departure time ST are transferred to what one bit remains free at Z0 of the fifth group.
- FIG. 3 shows a similar route recommendation as FIG. 1, however, the coding is done in a RDS-TMC compatible Form, with a maximum of only four transfer points U1 to U4 can be encoded. Even the transfer of Additional information is limited to one statement in the present example on the train sequence ZF.
- ALERT are the individual location codes are identified by labels. There Label 11 means the destination, Label 10 a waypoint and Label 6 additional information.
- the in Fig. 3 shown example of the so-called "silent event (1907) "made use of.
- the link to the" normal " TMC reporting is done via the in the first group transmitted location code S. This is the place where a transition to public transport is advisable is.
- Fig. 4 shows parts of a location database for the public Passenger traffic in the Hanover area.
- Location code 22001 relates to a location (point) on the Road number 2, which is the federal road B2.
- the name this place is "airport”.
- As information about the type of place (LocType) are for the locations on the S-Bru line “ ⁇ V-Point” registered, for the S-Bru line in total in each case Direction of the place type "Line”.
- An out of focus area - therefore place type "Fuzzy" - with the place code 41922 characterizes the area which is used to operate the public transport is to be counted.
- the route recommendation is then, for example, as follows:
Abstract
Description
- Meldungselement
- Bedeutung
- Fahrtziel
- Location Code in TMC-Ortsdatenbank, in der Regel ein sogenannter Point of Interest (POI); Codierung: Location Code (z.B. "MESSE")
- Verkehrsmittel
- Verkehrsmittel des Streckennetzes (z.B. U-Bahn, S-Bahn, Bus, ...) Codierung: Teil des Location Code
- Linienbezeichnung
- gibt die Linie im Streckennetz an (z.B. "S6") Codierung: Teil des Location Code
- Linienendpunkt
- gibt die Endhaltestellen von Linien an, um die Fahrtrichtung angeben zu können. Dient dem Nutzer zur Orientierung beim Wechsel des Verkehrsmittels. Codierung: Location Code
- Haltepunkt/Umsteigepunkt
- gibt den Zugangs- oder Abgangsort an, an dem das Verkehrsmittel bestiegen oder verlassen werden kann (z.B. Haltestellen oder Bahnhöfe) Codierung: Location Code
- Taktzeit
- gibt den durchschnittlichen zeitlichen Abstand zwischen den Abfahrtszeiten des Verkehrsmittels an
Codierung: 3 bit (Beispiel) 000 : keine 100 : 15 min 001 : 1 h 101 : 10 min 010 : 0,5 h 110 : 5 min 011 : 20 min 111 : 2 min - Zeitraum
- gibt an, in welchem Zeitraum die o.g. Taktzeit gilt (z.B. von <hh:mm> bis <hh:mm>) Codierung: 2x8 bit (Beispiel) gemäß ALERT C Mehrgruppenmeldungen, Label 7/8
- Gesamtfahrtzeit
- gibt die planmäßige Fahrtzeit für die gesamte Fahrtempfehlung in Minuten an
Codierung: 4 bit (Beispiel) 0000:keine 0110:30 1100:60 0001:5 0111:35 1101:70 0010:10 1000:40 1110:80 0011:15 1001:45 1111:90 0100:20 1010:50 0101 :25 1011:55 - Gesamtkosten/Tarifzone
- gibt den Gesamtpreis für die Fahrtempfehlung an (z.B. in [DM] oder als Tarifzone in einem Verkehrsverbund).
Codierung Tarifzone: 3 bit(Beispiel) 000:keine Angabe ... :... 001:Zone 1 111 :Zone 7 010:Zone 2 - TypZeit
- gibt die Codierungsarten der Abfahrtszeit an: Codierung: 2 bit (Beispiel)
- 00:
- keine Angabe
- 01:
- Bezug auf CT-Signal (ALERT C), d.h. Differenzzeit in <min> (siehe DE 42 08 277 A1: CT+2n; n in 6 bit)
- 10:
- Angabe der Abfahrtszeit im CT-Format (ALERT C) mit 11 bit
- 11:
- Angabe des Zeitraums (siehe oben) und der Taktzeit (siehe oben) mit insgesamt 19 bit
Bei der Codierung nach 10/11 muß die Anzahl Umsteigepunkte entsprechend reduziert werden.
- Abfahrtszeit
- gibt die Abfahrtszeit des Verkehrsmittels an Codierung: siehe <TypZeit>
Claims (11)
- Einrichtung zur Übertragung von Fahrtroutenempfehlungen für mindestens ein Netz öffentlicher Verkehrsmittel zu Empfängern, dadurch gekennzeichnet, daß eine Codierung mittels mindestens einer mindestens Teile des Verkehrsnetzes abbildenden Ortsdatenbank (Verkehrsnetz-Ortsdatenbank) erfolgt, daß zur Übertragung von Fahrtroutenempfehlungen, die auch in mindestens einer ein Straßennetz abbildenden Ortsdatenbank (Straßennetz-Ortsdatenbank) abgelegte Orte betreffen, Datensätze derjenigen Orte, die mindestens einen benachbarten Ort in der mindestens einen Straßennetz-Ortsdatenbanken aufweisen, mindestens einen Verweis auf mindestens einen solchen benachbarten Ort mittels eines Querverweises enthalten.
- Einrichtung nach Anspruch 1, dadurch gekennzeichnet, daß für die Übertragung von digital codierten Verkehrsmeldungen (TMC) vorgesehene Datenprotokolle verwendet werden.
- Einrichtung nach Anspruch 1, dadurch gekennzeichnet, daß für die Übertragung ein RDS-ODA-Protokoll verwendet wird.
- Einrichtung nach Anspruch 2, dadurch gekennzeichnet, daß für Umleitungen vorgesehene Datenprotokolle verwendet werden.
- Einrichtung nach einem der vorhergehenden Ansprüche, dadurch gekennzeichnet, daß die Fahrtroutenempfehlungen als Mehrgruppenmeldungen übertragen werden.
- Empfänger für Fahrtroutenempfehlungen für mindestens ein Netz offentlicher Verkehrsmittel, dadurch gekennzeichnet, daß zur Decodierung im Empfänger mindestens eine mindestens Teile des Verkehrsnetzes abbildende Ortsdatenbank (Verkehrsnetz-Ortsdatenbank) vorgesehen ist und daß zur Decodierung von Fahrtroutenempfehlungen, die auch in mindestens einer ein Straßennetz abbildenden Ortsdatenbank (Straßennetz-Ortsdatenbank) abgelegte Orte betreffen, Datensätze derjenigen Orte, die mindestens einen benachbarten Ort in der mindestens einen Straßennetz-Ortsdatenbanken aufweisen, mindestens einen Verweis auf mindestens einen solchen benachbarten Ort mittels eines Querverweises enthalten.
- Empfänger nach Anspruch 6, dadurch gekennzeichnet, daß zur Verwaltung und Decodierung der Fahrtroutenempfehlungen Einrichtungen zur Verwaltung und Decodierung von digital codierten Verkehrsmeldungen (TMC) vorgesehen sind.
- Empfänger nach einem der Ansprüche 6 oder 7, dadurch gekennzeichnet, daß Codes für die Orte der Verkehrsnetz-Ortsdatenbank und der Straßennetz-Ortsdatenbank in einer gemeinsamen Ortsdatenbank zusammengeführt werden.
- Empfänger nach einem der Ansprüche 6 bis 8, dadurch gekennzeichnet, daß eine Einrichtung zur Ausgabe der Fahrtroutenempfehlungen als Text, Sprache und/oder Graphik unter Verwendung von Umsteigepunkten vorgesehen ist.
- Empfänger nach einem der Ansprüche 6 bis 9, dadurch gekennzeichnet, daß die Ortsdatenbank auf einem austauschbaren Datenträger abgelegt ist.
- Empfänger nach einem der Ansprüche 6 bis 9, dadurch gekennzeichnet, daß die Ortsdatenbank über eine Luftschnittstelle aktualisierbar ist.
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
DE19858568A DE19858568A1 (de) | 1998-12-18 | 1998-12-18 | Einrichtung zur Übertragung von Fahrtroutenempfehlungen und Empfänger |
DE19858568 | 1998-12-18 | ||
PCT/DE1999/003197 WO2000038129A1 (de) | 1998-12-18 | 1999-10-05 | Einrichtung zur übertragung von fahrtroutenempfehlungen und empfänger |
Publications (2)
Publication Number | Publication Date |
---|---|
EP1141911A1 EP1141911A1 (de) | 2001-10-10 |
EP1141911B1 true EP1141911B1 (de) | 2002-09-25 |
Family
ID=7891623
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP99973504A Expired - Lifetime EP1141911B1 (de) | 1998-12-18 | 1999-10-05 | Einrichtung zur übertragung von fahrtroutenempfehlungen und empfänger |
Country Status (4)
Country | Link |
---|---|
EP (1) | EP1141911B1 (de) |
JP (1) | JP2002533820A (de) |
DE (2) | DE19858568A1 (de) |
WO (1) | WO2000038129A1 (de) |
Families Citing this family (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE10034463A1 (de) | 2000-07-15 | 2002-04-04 | Bosch Gmbh Robert | Navigationsverfahren und Navigationsgerät |
DE10131432A1 (de) * | 2001-06-29 | 2003-01-09 | Bosch Gmbh Robert | Verfahren zur Navigation eines Fahrzeugs |
TW581309U (en) * | 2001-11-26 | 2004-03-21 | Sin Etke Technology Co Ltd | Real-time traffic condition providing device |
DE10231833A1 (de) * | 2002-07-12 | 2004-01-22 | Robert Bosch Gmbh | Verfahren zur Aktualisierung von Routendaten |
DE10252735B4 (de) * | 2002-11-13 | 2017-11-16 | Robert Bosch Gmbh | Datenformat, digitales Rundfunksignal, zugeordnetes Informationssystem und Verfahren zum Betreiben desselben |
AU2003256156A1 (en) * | 2003-08-04 | 2005-02-15 | Wouter Gort | Method and device for initiating via rds/rbds a desired action related to an external event |
KR101276265B1 (ko) * | 2006-03-09 | 2013-06-21 | 삼성전자주식회사 | 경로 정보 애플리케이션을 제공하는 장치 및 방법 |
EP2500887B1 (de) * | 2011-03-17 | 2020-09-09 | Harman Becker Automotive Systems GmbH | Beschreibung eines Straßensegments mithilfe von ISO 17572-3 |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB2195868A (en) * | 1986-08-21 | 1988-04-13 | Gainsborough Holdings Ltd | Broadcasting of map information |
WO1996000960A1 (de) * | 1994-06-29 | 1996-01-11 | Siemens Aktiengesellschaft | Elektronisches fahrplan-auskunftssystem für öffentliche verkehrsmittel |
DE19606010A1 (de) * | 1996-02-17 | 1997-08-21 | Bosch Gmbh Robert | Ortsdatenbank für die Ermittlung von Routen innerhalb eines Verkehrswegenetzes |
DE19630195A1 (de) * | 1996-05-08 | 1997-11-13 | Bosch Gmbh Robert | Verfahren zur Übertragung von Durchsagen mit Empfänger zur Durchführung des Verfahrens |
-
1998
- 1998-12-18 DE DE19858568A patent/DE19858568A1/de not_active Withdrawn
-
1999
- 1999-10-05 EP EP99973504A patent/EP1141911B1/de not_active Expired - Lifetime
- 1999-10-05 DE DE59902889T patent/DE59902889D1/de not_active Expired - Lifetime
- 1999-10-05 WO PCT/DE1999/003197 patent/WO2000038129A1/de active IP Right Grant
- 1999-10-05 JP JP2000590118A patent/JP2002533820A/ja active Pending
Also Published As
Publication number | Publication date |
---|---|
DE19858568A1 (de) | 2000-06-21 |
WO2000038129A1 (de) | 2000-06-29 |
EP1141911A1 (de) | 2001-10-10 |
DE59902889D1 (de) | 2002-10-31 |
JP2002533820A (ja) | 2002-10-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP0769180B1 (de) | Einrichtung zur aufbereitung und ausgabe von informationen für einen fahrzeugführer | |
EP1079353B1 (de) | Verfahren zur Anforderung und zur Verarbeitung von Verkehrsmeldungen | |
DE3810177C2 (de) | Rundfunkempfänger, insbesondere Fahrzeugempfänger | |
EP1966780B1 (de) | Verfahren zur codierung von meldungen, verfahren zur decodierung von meldungen und empfänger zum empfang und zur auswertung von meldungen | |
EP0769181A1 (de) | Einrichtung zur information eines fahrzeugführers | |
EP1030475A2 (de) | Verfahren zur Übertragung von digital codierten Verkehrsnachrichten und Funkempfänger dazu | |
DE19857782C2 (de) | Verfahren zum Übertragen von Tabelleninformationen von einer Zentrale an ein Endgerät über einen Übertragungskanal und Zentrale zum Durchführen des Verfahrens | |
EP1114406B1 (de) | Verfahren zur codierung strassenübergreifender verkehrsbehinderungen | |
EP1105856B1 (de) | Einrichtung zur codierung und zur decodierung von orten | |
EP1141911B1 (de) | Einrichtung zur übertragung von fahrtroutenempfehlungen und empfänger | |
EP0790591B1 (de) | Ortsdatenbank für die Ermittlung von Routen innerhalb eines Verkehrswegennetzes | |
EP0896314B1 (de) | Navigationssystem für ein Kraftfahrzeug | |
EP0962004B1 (de) | Einrichtung und verfahren zur information über verkehrsstörungen | |
EP0984416B1 (de) | Verfahren zur Verknüpfung von digitalen Verkehrswegenetzbeschreibungen und Ortsdatenbank | |
DE19905431A1 (de) | Verfahren zur Übertragung von auf Orte bezogenen Informationen | |
DE10105468A1 (de) | Verfahren zur Übertragung von codierten TMC-Meldungen in einem Nachrichtenübertragungssystem und Vorrichtung zum Empfang solcher Meldungen | |
EP1076325A2 (de) | Verfahren zur Anforderung und zur Verarbeitung von Verkehrsmeldungen | |
EP1011219A2 (de) | Verfahren und Vorrichtung für die Erzeugung von Verkehrsinformationen für sich über mehrere verkettete Segmente eines Strassenverkehrsnetzes erstreckenden Zuständen | |
DE19917842A1 (de) | Verfahren zur Identifizierung segmentübergreifender Ereignisse durch Segmente | |
DE19948109A1 (de) | Verkehrsinformations-Generation bei sich über mehrere verkettete Segmente eines Straßenverkehrsnetzes erstreckenden Zuständen | |
EP1619642A2 (de) | Verfahren zur Übertragung von digital codierten Meldungen in Datengruppen und Empfänger |
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: 20010718 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE |
|
AX | Request for extension of the european patent |
Free format text: AL;LT;LV;MK;RO;SI |
|
GRAG | Despatch of communication of intention to grant |
Free format text: ORIGINAL CODE: EPIDOS AGRA |
|
17Q | First examination report despatched |
Effective date: 20011212 |
|
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 |
|
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): DE DK FR GB IT NL |
|
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 FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20020925 Ref country code: IT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT;WARNING: LAPSES OF ITALIAN PATENTS WITH EFFECTIVE DATE BEFORE 2007 MAY HAVE OCCURRED AT ANY TIME BEFORE 2007. THE CORRECT EFFECTIVE DATE MAY BE DIFFERENT FROM THE ONE RECORDED. Effective date: 20020925 |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D Free format text: NOT ENGLISH |
|
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: 59902889 Country of ref document: DE Date of ref document: 20021031 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20021225 |
|
GBT | Gb: translation of ep patent filed (gb section 77(6)(a)/1977) |
Effective date: 20030128 |
|
NLV1 | Nl: lapsed or annulled due to failure to fulfill the requirements of art. 29p and 29m of the patents act | ||
ET | Fr: translation filed | ||
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FD4D Ref document number: 1141911E Country of ref document: IE |
|
PLBE | No opposition filed within time limit |
Free format text: ORIGINAL CODE: 0009261 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT |
|
26N | No opposition filed |
Effective date: 20030626 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: FR Payment date: 20081021 Year of fee payment: 10 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: ST Effective date: 20100630 |
|
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: 20091102 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20121023 Year of fee payment: 14 |
|
GBPC | Gb: european patent ceased through non-payment of renewal fee |
Effective date: 20131005 |
|
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: 20131005 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20141208 Year of fee payment: 16 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R119 Ref document number: 59902889 Country of ref document: DE |
|
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: 20160503 |