EP2994890B1 - Procédé et dispositif de fourniture de données pour la perception de péage et système de péage - Google Patents

Procédé et dispositif de fourniture de données pour la perception de péage et système de péage Download PDF

Info

Publication number
EP2994890B1
EP2994890B1 EP14724012.1A EP14724012A EP2994890B1 EP 2994890 B1 EP2994890 B1 EP 2994890B1 EP 14724012 A EP14724012 A EP 14724012A EP 2994890 B1 EP2994890 B1 EP 2994890B1
Authority
EP
European Patent Office
Prior art keywords
toll
checksum
vehicle
stipulated
beacon
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.)
Active
Application number
EP14724012.1A
Other languages
German (de)
English (en)
Other versions
EP2994890A1 (fr
Inventor
Jochen HECHLER
Hans Gregor MOLTER
Gernot KNAUSENBERGER
Roland Lange
Günter Seidel
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Continental Automotive GmbH
Original Assignee
Continental Automotive 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 Continental Automotive GmbH filed Critical Continental Automotive GmbH
Publication of EP2994890A1 publication Critical patent/EP2994890A1/fr
Application granted granted Critical
Publication of EP2994890B1 publication Critical patent/EP2994890B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07B—TICKET-ISSUING APPARATUS; FARE-REGISTERING APPARATUS; FRANKING APPARATUS
    • G07B15/00—Arrangements or apparatus for collecting fares, tolls or entrance fees at one or more control points
    • G07B15/06—Arrangements for road pricing or congestion charging of vehicles or vehicle users, e.g. automatic toll systems
    • G07B15/063—Arrangements for road pricing or congestion charging of vehicles or vehicle users, e.g. automatic toll systems using wireless information transmission between the vehicle and a fixed station

Definitions

  • the invention relates to a method and a device for providing data for toll collection and a toll system.
  • the toll is collected automatically via a toll collection device, also known as an on-board unit (OBU), installed in the vehicle.
  • the toll collection device uses satellite tracking to determine the truck's movement and independently calculates the toll due.
  • the toll fee due is transmitted from the toll collection device to a toll collection center for the collection and billing of the fees.
  • a toll collection device provided free of charge by an operating company is installed in the truck.
  • the toll collection devices have a position receiver for a global navigation satellite system (GNSS) with which the position of the vehicle is determined.
  • GNSS global navigation satellite system
  • the toll collection devices are equipped with a computing unit and a memory that contains vehicle-specific information and the position data of the toll highways. With the help of this data, the toll collection device calculates the toll to be paid using the satellite navigation system already mentioned. The effort for the toll collection devices is very high, in particular due to data security and data protection requirements.
  • EP 2 325 807 A1 discloses a method and apparatus for generating toll information in a road toll system. Provision is made to provide a set of location data from a local environment of a beacon in the beacon and, if a vehicle device is in a transceiver area of the beacon, to receive a location data set from the beacon in the vehicle device.
  • DE 10 2006 032 468 B3 discloses a toll system for levying a toll on vehicles in a road network with toll road sections.
  • a toll calculation unit uses a transmitted vehicle position and a comparison with toll road sections of an electronic road network to calculate a prediction value for a query parameter that identifies an entry or exit into or from a toll road section.
  • US 2012/0265583 A1 discloses a method for billing location uses of vehicles in a road toll system by means of a payment transaction system.
  • the payment transaction system comprises a transaction server and, connected to it, decentralized transaction terminals for billing payment transactions by means of payment cards.
  • the object on which the invention is based is to create a method and a device for providing data for toll collection, in particular for passenger vehicles, as well as a toll system which enable the data for toll collection to be provided reliably and cost-effectively.
  • the invention is characterized by a method and a corresponding device for providing data for toll collection.
  • a collision-free checksum is determined in each case as a function of a predetermined amount of recorded position data values for a vehicle.
  • the amount of the recorded position data values is stored in a predefined manner together with the associated checksum.
  • a first data record which includes at least one of the stored checksums, is sent to the respective toll beacon.
  • at least some of the stored position data values with the associated checksums are provided in a predefined manner on a predefined communication interface.
  • position data values for example GPS data (Global Positioning System), which are usually used for recording routes taken by the vehicle, cannot simply be falsified.
  • An additional device for secure storage and processing of the position data values which is also referred to as hardware security, is not required. This enables a very cost-effective provision of the data for toll collection. It is advantageously possible in this way to ensure the route of the vehicle by means of the position data values and random controls of the respective toll beacons to such an extent that subsequent manipulation of the routes can be recognized.
  • collision occurs with checksums if the same checksum is assigned to two different input data.
  • the collision-free property thus means that it it is practically impossible to generate two different input data with the same checksum.
  • the respective set of the recorded position data values comprises a predetermined number of the last recorded position data values.
  • the last determined checksum is transmitted to the respective toll beacon. This enables easy verification of the data.
  • a checksum determination time is recorded together with the checksum and stored in a predetermined manner together with the associated checksum.
  • the first data record includes the checksum determination time for the respective checksum and / or identification information of the vehicle and / or identification information of a device that can be arranged in the vehicle. This enables easy verification of the data.
  • the recorded position data values are each provided together with an associated acquisition time and the set of position data values with their acquisition times and the associated checksum and their Checksum determination time is stored predetermined.
  • the respective associated acquisition times and / or the checksum determination times of the associated checksums are specified at the specified communication interface provided.
  • the acquisition times enable the route to be easily verified and the checksums with the checksum determination times can be compared easily and reliably with the data records of the toll beacons.
  • the position data values for the vehicle are recorded at predetermined time intervals. This enables a simple and reliable evaluation of the data.
  • the checksum is determined as a function of a previously determined checksum. This can advantageously make a contribution to increasing the manipulation security of the position data values.
  • the collision-free checksum is a hash value.
  • a hash function also called a spread function, is used, preferably a cryptological hash function, in particular an SHA-2 (secure hash algorithm).
  • SHA-2 secure hash algorithm
  • the invention is characterized by a toll system.
  • the toll system comprises a toll determination device, at least one device according to the second aspect, which is arranged in a vehicle, and at least one toll beacon.
  • the at least one toll beacon is designed to forward the first data set sent by the vehicle to the toll beacon, which in each case includes at least one checksum, directly or indirectly to the toll determination device, the toll determination device being configured to be directly or indirectly controlled by the device to verify provided position data and checksums depending on the data record received from the at least one toll beacon.
  • the toll beacon does not forward all of the first data records received to the toll determination device.
  • the first data records are preferably forwarded to the toll calculation device according to a random principle. This has the advantage that it is much more difficult to manipulate the routes, since it is not known which toll beacon actually forwarded the respective first data record to the toll determination device.
  • the toll beacon is designed to capture at least one image of a license plate of the respective vehicle that has the toll beacon happens, and / or to determine a vehicle registration number of the respective vehicle passing the toll beacon and to forward the image or the determined vehicle registration number together with position information from the toll beacon and time information to the toll determination device.
  • This advantageously enables so-called "silent enforcements" to be carried out.
  • checks are carried out without a device on the vehicle recognizing whether such a check is being carried out.
  • the data are transmitted to the toll determination device according to a random principle, the data including the image or the vehicle registration number, the position information of the toll beacon and the time information.
  • This has the advantage that, for example, a potential hacker of the toll system has no knowledge of the frequency and time of such controls, which makes subsequent manipulation of the position data values much more difficult.
  • Figure 1 10 shows a block diagram of a toll system 10.
  • the toll system 10 comprises a toll determination device 20, at least one device 30 for providing data for toll collection and at least one toll beacon 40.
  • the toll determination device 20 comprises, for example, a computing unit, for example a server.
  • the toll determination device 20 is arranged, for example, in a stationary manner in a back end of a toll operator.
  • the device 30 is preferably arranged in a motor vehicle, in particular in a passenger vehicle. Preferably a large number of motor vehicles are equipped with such a device 30.
  • the toll system 10 preferably comprises a plurality of toll beacons 40.
  • the respective toll beacon 40 can be designed both as a stationary system and as a mobile system.
  • the respective toll beacon 40 is designed, for example, as a control bridge over a toll road.
  • the device 30 is designed to determine a collision-free checksum for the vehicle in each case as a function of a predetermined set of detected position data values.
  • the position data values are provided, for example, by a position-determining device arranged in the vehicle.
  • the device 30 can comprise the position determination device.
  • the device 30 is also designed to store the quantity of the detected position data values together with the associated checksum in a predetermined manner.
  • the recorded position data values are, for example, each provided together with an associated recording time.
  • the respective amount of the recorded position data values includes, for example, a predefined number of the last recorded position data values.
  • GPS data global positioning system data
  • a hash value is determined as a function of the n GPS data records and a hash value that was last determined.
  • This new hash value is written to the stack as an (n + 1) th GPS data record with the next number and the time of the checksum determination.
  • the following list shows an example of the content of the stack memory: 756 Hash value Time_1 757 GPS Time_2 758 GPS Time_2 ... ... ... 766 GPS Time_2 767 (Hash (756 to 766) Time_1 768 GPS Time_2
  • Time_1 represents the checksum determination time and Time_2 represents the respective acquisition time.
  • the checksum determination time and the acquisition time preferably have the same time format.
  • the checksum determination time and the acquisition time can also include date information.
  • the device 30 is also designed, when the vehicle passes one of the toll beacons 40, to send a first data record, which includes at least one of the stored checksums, to the respective toll beacon 40.
  • the first data record preferably also includes the checksum determination time for the respective checksum and / or identification information of the vehicle and / or identification information of the device 30.
  • the first data record also includes, for example, the consecutive number. According to the above list, the device 30 sends the first data record with the number 767 in the format: [767, hash value (756 to 766), time_1], for example to the toll beacon 40 that the vehicle is passing.
  • the device 30 is preferably initialized prior to delivery from the factory and / or when it is handed over to a user. For this purpose, for example, a random number is written into a first memory location of the stack memory. This random number is used as the first checksum on the stack. This random number is also stored assigned to the device 30 by the toll determination device 20. This has the advantage that the devices 30 for providing the data for toll collection are not mixed up will. Otherwise, in particular in an initial phase of using such a device 30, if the vehicles cover the same routes, mix-ups may occur.
  • the device 30 is also designed to provide at least some of the stored position data values with the associated checksums at a predetermined communication interface in response to a predetermined readout signal and / or at predetermined time intervals.
  • the device 30 can be assigned a mobile radio interface or the device 30 can have the mobile radio interface, so that the device 30 sends all new contents of the stack memory to the toll determination device 20 in response to a data release by a vehicle user.
  • new content is to be understood as meaning the content that has not yet been sent to the toll determination device 20 at an earlier point in time and / or has not been read from the stack memory for an indirect transfer.
  • the data can be read out by means of a memory reader and forwarded to the toll determination device 20, for example via an Internet application.
  • the respective toll beacon 40 is designed to forward the first data record sent by the vehicle to the toll beacon 40 directly or indirectly to the toll determination device 20. Preferably, not all of the first data records received are forwarded from the toll beacon 40 to the toll determination device 20. The first data records are preferably forwarded to the toll determination device 20 according to a random principle.
  • the toll determination device 20 is designed to use the position data and checksums provided directly or indirectly by the device 30 as a function of the at least a toll beacon 40 to verify the respective first data record received.
  • the toll determination device 20 determines each checksum on the basis of the transmitted position data values and compares the respective calculated value with the associated checksums transmitted by the device 30. If there is an associated first data record forwarded by one of the toll beacons 40, the checksum of this first data record is compared with the checksum sent by the device 30 and determined by the toll determining device 20. If the checksums do not match, manipulation of the device 30 can be assumed.
  • the toll determination device 20 calculates, for example, the hash value 767 and compares the hash value transmitted by the device 30 to the toll determination device 20 and the hash value transmitted by the toll beacon 40.
  • the hash value with the number 767 would change, for example. However, this leads to an error in a comparison with the associated hash value which was transmitted by the toll beacon 40.
  • a protocol with predefined fields is preferably used to transmit the respective data.
  • the protocol can include, for example, the fields number, position data value / hash value and time.
  • the numbers are preferably consecutive and without jumps.
  • the position data values in particular the GPS values, preferably have no additional characters and / or values that do not match the position data values.
  • the time information preferably only includes numbers.
  • a maximum length of the respective fields is specified, for example.
  • the toll determination device 20 carries out a plausibility check of the position data values if there are doubts as to the correctness of the received position data values. In this case, it is checked, for example, whether the route is on a road and / or a speed of the motor vehicle is plausible and so on.
  • "silent enforcements” can be carried out, for example. This means that checks are carried out without a device on the vehicle recognizing whether such a check is being carried out.
  • the toll beacon 40 has, for example, an image capture device and is designed to capture at least one image of a license plate of a vehicle that passes the toll beacon 40. Furthermore, the toll beacon 40 is designed to record time information associated with the passing of the toll beacon 40, for example to record the time at which the vehicle passes the toll beacon 40. Furthermore, the toll beacon 40 is designed to link the image of the license plate and / or data determined therefrom, for example the vehicle license plate, with the time information and the GPS data of the toll beacon 40 to form a data record and to display this data record forward the backend.
  • the toll determination device 20 is also designed, for example, to calculate a toll fee as a function of the data provided by the device 30, in particular the position data values of the motor vehicle, and as a function of the position data of toll motorways and / or other toll roads.
  • the toll determination device 20 for example, a memory in which the position data of the toll highways and the other toll roads are stored.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Business, Economics & Management (AREA)
  • Finance (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Devices For Checking Fares Or Tickets At Control Points (AREA)

Claims (13)

  1. Procédé de fourniture de données destinées à la perception de péage, procédé dans lequel
    - au moyen d'un dispositif (30) disposé dans un véhicule automobile, une somme de contrôle sans collision est déterminée pour le véhicule à chaque fois en fonction d'un ensemble prédéterminé de valeurs de données de position acquises,
    - au moyen du dispositif (30), l'ensemble de valeurs de données de position acquises est mémorisé d'une manière prédéterminée conjointement avec la somme de contrôle associée,
    - lorsque le véhicule passe devant une balise de péage prédéterminée (40), un premier ensemble de données, qui comprend au moins une des sommes de contrôle mémorisées, est envoyé à la balise de péage respective (40), la balise de péage (40) étant conçue pour transmettre à une unité de détermination de péage (20) le premier ensemble de données envoyé à la balise de péage (40), l'unité de détermination de péage (20) étant conçue pour vérifier les données de position et les sommes de contrôle fournies par le dispositif (30) en fonction du premier ensemble de données reçu de la balise de péage (40),
    - au moyen du dispositif (30) en réponse à un signal de lecture prédéfini et/ou à des intervalles de temps prédéfinis, au moins une partie des valeurs de données de position mémorisées est fournie conjointement avec les sommes de contrôle associées à une interface de communication prédéfinie.
  2. Procédé selon la revendication 1, dans lequel l'ensemble respectif de valeurs de données de position acquises comprend un nombre prédéterminé de dernières valeurs de données de position acquises.
  3. Procédé selon la revendication 1 ou 2, dans lequel, lorsque le véhicule passe devant la balise de péage prédéterminée (40), la dernière somme de contrôle déterminée est transmise à la balise de péage respective (40).
  4. Procédé selon l'une des revendications précédentes, dans lequel un instant de détermination de somme de contrôle est acquis conjointement avec la somme de contrôle et est mémorisé conjointement avec la somme de contrôle associée.
  5. Procédé selon l'une des revendications précédentes, dans lequel le premier ensemble de données comprend l'instant de détermination de somme de contrôle pour la somme de contrôle respective et/ou une information d'identification du véhicule et/ou une information d'identification d'une unité qui peut être disposée dans le véhicule.
  6. Procédé selon la revendication 4 ou 5, dans lequel les valeurs de données de position acquises sont fournies conjointement avec un instant d'acquisition associé et l'ensemble de valeurs de données de position est mémorisé de manière prédéterminée avec leurs instants d'acquisition et la somme de contrôle associée et son instant de détermination de somme de contrôle sont mémorisés de manière prédéterminée.
  7. Procédé selon l'une des revendications 4 à 6, dans lequel, en réponse au signal de lecture prédéterminé et/ou aux intervalles de temps prédéterminés pour l'au moins une partie des valeurs de données de position mémorisées, les instants d'acquisition respectivement associés et/ou les instants de détermination de somme de contrôle des sommes de contrôle associées sont en plus fournis à l'interface de communication prédéterminée.
  8. Procédé selon l'une des revendications précédentes, dans lequel les valeurs de données de position du véhicule sont acquises à des intervalles de temps prédéterminés.
  9. Procédé selon l'une des revendications précédentes, dans lequel la somme de contrôle est déterminée en fonction d'une somme de contrôle préalablement déterminée.
  10. Procédé selon l'une des revendications précédentes, dans lequel la somme de contrôle sans collision est une valeur de hachage.
  11. Dispositif (30) de fourniture de données destinées à la perception de péage, lequel dispositif est conçu pour mettre en œuvre un procédé selon l'une des revendications 1 à 10.
  12. Système de péage (10) comportant
    - une unité de détermination de péage (20)
    - au moins un dispositif (30) selon la revendication 11, qui est disposé dans un véhicule,
    - au moins une balise de péage (40) qui est conçue pour transmettre le premier ensemble de données, qui est envoyé par le véhicule à la balise de péage (40) et qui comprend à chaque fois au moins une somme de contrôle, directement ou indirectement à l'unité de détermination de péage (20), l'unité de détermination de péage (20) étant conçue pour vérifier les données de position et les sommes de contrôle, fournies directement ou indirectement par le dispositif (30), en fonction de l'ensemble de données reçu de l'au moins une balise de péage (40).
  13. Système de péage (10) selon la revendication 12, dans lequel la balise de péage (40) est conçue pour acquérir au moins une image d'une plaque d'immatriculation du véhicule respectif qui passe devant la balise de péage (40) et/ou pour déterminer un numéro d'immatriculation du véhicule respectif qui passe devant la balise de péage (40) et pour transmettre l'image ou le numéro d'immatriculation du véhicule déterminé conjointement avec une information de position de la balise de péage (40) et une information de temps à l'unité de détermination de péage (20).
EP14724012.1A 2013-05-08 2014-04-25 Procédé et dispositif de fourniture de données pour la perception de péage et système de péage Active EP2994890B1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE102013208470.6A DE102013208470A1 (de) 2013-05-08 2013-05-08 Verfahren und Vorrichtung zur Bereitstellung von Daten zur Mauterhebung und Mautsystem
PCT/EP2014/058512 WO2014180685A1 (fr) 2013-05-08 2014-04-25 Procédé et dispositif de fourniture de données pour la perception de péage et système de péage

Publications (2)

Publication Number Publication Date
EP2994890A1 EP2994890A1 (fr) 2016-03-16
EP2994890B1 true EP2994890B1 (fr) 2021-01-27

Family

ID=50729453

Family Applications (1)

Application Number Title Priority Date Filing Date
EP14724012.1A Active EP2994890B1 (fr) 2013-05-08 2014-04-25 Procédé et dispositif de fourniture de données pour la perception de péage et système de péage

Country Status (3)

Country Link
EP (1) EP2994890B1 (fr)
DE (1) DE102013208470A1 (fr)
WO (1) WO2014180685A1 (fr)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3346451B1 (fr) * 2017-01-04 2023-12-13 Toll Collect GmbH Procédé destinés au suivi de véhicules assujettis au péage dans un système de péage et un système de péage correspondant
US11557154B2 (en) * 2017-06-23 2023-01-17 Kapsch Trafficcom Ag System and method for verification and/or reconciliation of tolling or other electronic transactions, such as purchase transactions
CN111009044A (zh) * 2019-12-17 2020-04-14 交通运输部公路科学研究所 一种基于北斗高精度定位的里程收费系统
DE102020134212B3 (de) 2020-12-18 2022-03-10 Jenoptik Robot Gmbh Verfahren und Vorrichtung zur Zuordnung einer Identifizierungsinformation und Identifizierungsdaten zu einem Fahrzeug
CN112967409B (zh) * 2021-02-03 2023-02-17 北京千方科技股份有限公司 一种用于etc信息发送的防碰撞方法及系统

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120265583A1 (en) * 2011-04-15 2012-10-18 Kapsch Trafficcom Ag Method for fee charging position usages of vehicles

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1783692A3 (fr) * 2005-10-06 2007-12-05 Siemens Aktiengesellschaft Mise en application avec des temps de cycle réduits
DE102006032468B3 (de) * 2006-07-13 2007-07-26 Siemens Ag Adaptive Datenvolumen bei der Übertragung von Daten für eine zentrale Geoobjekterkennung
WO2009090515A2 (fr) * 2008-01-15 2009-07-23 Nxp B.V. Systeme de peage routier
DK2325806T3 (da) * 2009-10-30 2013-03-18 Kapsch Trafficcom Ag Fremgangsmåde til frembringelsen af afgiftstransaktioner
ES2382951T5 (es) * 2009-11-23 2022-08-26 Kapsch Trafficcom Ag Procedimiento y dispositivos para generar informaciones de peaje en un sistema de peaje viario
ES2427163T3 (es) * 2011-03-22 2013-10-29 Kapsch Trafficcom Ag Procedimiento para validar una transacción de peaje

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120265583A1 (en) * 2011-04-15 2012-10-18 Kapsch Trafficcom Ag Method for fee charging position usages of vehicles

Also Published As

Publication number Publication date
EP2994890A1 (fr) 2016-03-16
WO2014180685A1 (fr) 2014-11-13
DE102013208470A1 (de) 2014-11-13

Similar Documents

Publication Publication Date Title
EP0741891B1 (fr) Procede et dispositif permettant de determiner les droits de peage a encaisser pour des voies et/ou des zones de circulation empruntees par des vehicules
EP2860703B1 (fr) Procédé de vérification de transactions de péage et composants associés
EP1088286B1 (fr) Dispositif de controle cote route pour un appareil de peage installe dans un vehicule
EP2994890B1 (fr) Procédé et dispositif de fourniture de données pour la perception de péage et système de péage
AT507031B1 (de) Verfahren und vorrichtung zum einheben von maut
EP2423885B1 (fr) Dispositif et procédé de surveillance de fonction d'un système de péage routier
WO2008000227A1 (fr) Procédé et dispositif pour garantir la protection des données lors de la détection de télépéage
EP1192600B1 (fr) Dispositif de collecte de taxes flexible
EP2949096B1 (fr) Production de donnés de position au moyen d'un protocole délimiteur de distance
DE102013008373A1 (de) Verfahren und System zum Bereitstellen von Informationen über Parkgebühren auf einem gebührenpflichtigen Parkplatz
DE102014116756A1 (de) Vorrichtung zum Erheben einer Fahrzeugmaut
EP2503518B1 (fr) Procédé de validation d'une transaction de péage
EP2325806B1 (fr) Procédé de production de transactions de péage
EP2757513B1 (fr) Procédé de calcul d'utilisations d'espaces
EP3211605B1 (fr) Dispositif de véhicule, système, dispositif coté route et procédé d'exécution d'au moins une transaction
EP3038062B1 (fr) Procédé et dispositifs de véhicule pour communication DSRC
EP3113118B1 (fr) Procede de suivi de vehicules soumis a peage dans un systeme de peage et systeme de peage
EP1335324A2 (fr) Dispositif pour déterminer des droits de péage
DE102013201730A1 (de) Bereitstellung von Positionsdaten mittels eines Distance-Bounding Protokolls
WO2002101661A2 (fr) Systeme de peage double
EP2772886B2 (fr) Système de tableau de bord électronique de véhicule et procédé de contrôle correspondant
EP1729254B1 (fr) Procédé et système de transmission de données
EP3389291B1 (fr) Communication entre un véhicule et une pluralité de dispositifs de route
EP3188133B1 (fr) Dispositif de traitement de donnees de position et systeme de peage et procede de fonctionnement d'un dispositif de traitement de donnees de position et d'un systeme de peage
DE102010029171A1 (de) Verfahren zur Routenberechnung

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: 20151208

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

RIN1 Information on inventor provided before grant (corrected)

Inventor name: HECHLER, JOCHEN

Inventor name: SEIDEL, GUENTER

Inventor name: KNAUSENBERGER, GERNOT

Inventor name: LANGE, ROLAND

Inventor name: MOLTER, HANS, GREGOR

DAX Request for extension of the european patent (deleted)
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20191118

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: CONTINENTAL AUTOMOTIVE GMBH

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20201001

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

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: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1359040

Country of ref document: AT

Kind code of ref document: T

Effective date: 20210215

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

Free format text: LANGUAGE OF EP DOCUMENT: GERMAN

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 502014015238

Country of ref document: DE

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20210127

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NO

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: 20210427

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: 20210127

Ref country code: BG

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: 20210427

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: 20210527

Ref country code: LT

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: 20210127

Ref country code: HR

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: 20210127

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: 20210428

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: 20210127

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LV

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: 20210127

Ref country code: PL

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: 20210127

Ref country code: RS

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: 20210127

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: 20210127

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IS

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: 20210527

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 502014015238

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CZ

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: 20210127

Ref country code: EE

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: 20210127

Ref country code: SM

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: 20210127

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SK

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: 20210127

Ref country code: RO

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: 20210127

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: 20210127

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210127

Ref country code: MC

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: 20210127

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

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20210427

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: 20210425

26N No opposition filed

Effective date: 20211028

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20210430

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210430

Ref country code: AL

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: 20210127

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210430

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210430

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210427

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

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: 20210127

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 FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210127

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210425

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IS

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: 20210527

REG Reference to a national code

Ref country code: AT

Ref legal event code: MM01

Ref document number: 1359040

Country of ref document: AT

Kind code of ref document: T

Effective date: 20210425

REG Reference to a national code

Ref country code: DE

Ref legal event code: R081

Ref document number: 502014015238

Country of ref document: DE

Owner name: CONTINENTAL AUTOMOTIVE TECHNOLOGIES GMBH, DE

Free format text: FORMER OWNER: CONTINENTAL AUTOMOTIVE GMBH, 30165 HANNOVER, DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210430

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: 20210425

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20140425

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230522

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: 20210127

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20230430

Year of fee payment: 10

REG Reference to a national code

Ref country code: DE

Ref legal event code: R081

Ref document number: 502014015238

Country of ref document: DE

Owner name: CONTINENTAL AUTOMOTIVE TECHNOLOGIES GMBH, DE

Free format text: FORMER OWNER: CONTINENTAL AUTOMOTIVE TECHNOLOGIES GMBH, 30165 HANNOVER, DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

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: 20210127