[go: up one dir, main page]

EP3136351B1 - Systeme de peage routier, unite embarquee et procede permettant de faire fonctionner une unite embarquee - Google Patents

Systeme de peage routier, unite embarquee et procede permettant de faire fonctionner une unite embarquee Download PDF

Info

Publication number
EP3136351B1
EP3136351B1 EP15465532.8A EP15465532A EP3136351B1 EP 3136351 B1 EP3136351 B1 EP 3136351B1 EP 15465532 A EP15465532 A EP 15465532A EP 3136351 B1 EP3136351 B1 EP 3136351B1
Authority
EP
European Patent Office
Prior art keywords
board unit
message
data
communication module
latitude
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
EP15465532.8A
Other languages
German (de)
English (en)
Other versions
EP3136351A1 (fr
Inventor
Doru Aldea-Ungurean
Iosif Mudra
Daniel-Adrian Pascu
Sorin Soare
Silviu Stan
Ciprian Vasile Botiz
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 Technologies GmbH
Original Assignee
Continental Automotive Technologies 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
Family has litigation
First worldwide family litigation filed litigation Critical https://patents.darts-ip.com/?family=54291234&utm_source=google_patent&utm_medium=platform_link&utm_campaign=public_patent_search&patent=EP3136351(B1) "Global patent litigation dataset” by Darts-ip is licensed under a Creative Commons Attribution 4.0 International License.
Application filed by Continental Automotive Technologies GmbH filed Critical Continental Automotive Technologies GmbH
Priority to EP15465532.8A priority Critical patent/EP3136351B1/fr
Publication of EP3136351A1 publication Critical patent/EP3136351A1/fr
Application granted granted Critical
Publication of EP3136351B1 publication Critical patent/EP3136351B1/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 current invention refers to a road toll system, an on-board unit and a method for operating an on-board unit, particularly an on-board unit in a road toll system.
  • toll roads also known as turnpikes or tollways
  • a fee or toll
  • Different systems for collecting the toll are known.
  • toll booths or toll plazas where the user may pay the toll may be positioned at entry or exit points of the toll road.
  • electronic road toll systems are known.
  • GNSS Global Navigation Satellite System
  • a GNSS unit is a satellite navigation system, which allows to determine the position of the vehicle. Satellite navigation systems use a version of triangulation to locate a user through calculations involving information from a number of satellites.
  • GNSS systems are GPS (Global Positioning System) or Galileo, for example.
  • Document US2015088618 A1 discloses a precision usage-based transportation infrastructure charging service that includes a dynamic road and infrastructure usage engine that can fairly assess road usage based on any combination of mileage, time of day, vehicle mass, location, road class, defined zones and other relevant parameters.
  • GB2448743 A discloses an asset tracking system comprising a plurality of mobile devices to be tracked and a central server that is able to communicate with each of the mobile devices over a communications network.
  • Each mobile device sends position data to the central server over the communications network.
  • the central server further sends position data regarding the said mobile devices to each of the mobile devices over the communications network.
  • the position data may be a difference between a previous position and a current position of each mobile device to reduce the amount of data being transferred.
  • WO9704421 A1 shows a system and method for determining the distance travelled by a vehicle to enable a charge to be rendered for roadway usage.
  • US2004162673 A1 discloses a communications device for conveying geographic location information over capacity constrained wireless systems.
  • the on-board unit acquires data concerning the vehicle position.
  • Several approaches are known for processing the acquired vehicle position data and calculating the payable toll.
  • One approach is the so-called "Thick-Client-Approach", also known as “Fat-Client-” or “Smart-Client-Approach”.
  • Thick-Client-Approach the toll is calculated directly in the on-board unit. This information is then transmitted to a central office.
  • An advantage of the Thick-Client-Approach is that the data transmission volume is relatively low and tolling information is immediately available at the central office.
  • the on-board unit determines the vehicle position, concentrates the data and transmits this position information to the central office.
  • the payable toll is calculated in the central office.
  • the system is more flexible, as changes of road toll rates and toll roads can easily be implemented in the central office.
  • the data transmission volume is rather high.
  • the problem to be solved by the current invention is, therefore, to reduce the data transmission volume, especially in systems that use the Thin-Client-Approach.
  • a vehicle on-board unit for a toll road system comprises a processor, configured to determine the position of the on-board unit in regular intervals and to provide data representing the determined positions, the data including at least one of a latitude, a longitude and a timestamp representing the time at which the correspondent position has been determined.
  • the on-board unit further comprises a communication module, configured to receive the data representing the determined positions, and to generate at least one message, each message including the data of at least two successive positions, whereby the message includes a data header and payload, the payload including the position data, wherein the communication module is also configured to generate the at least one message to include a first timestamp for a first position in each message and to omit timestamps for at least one successive position of the same message.
  • the total amount of data may be reduced. For example, one header will then be sent for several positions, not for each single position.
  • the communication module is configured to generate the at least one message to include a first timestamp for a first position in each message and to omit timestamps for at least one successive position of the same message. By omitting timestamps, the size of each message may be reduced. If the message size is kept constant, the data of more positions may be included within one message.
  • the communication module may be configured to generate each message to include a first latitude and a first longitude specifying a first position and at least one delta-latitude and delta-longitude specifying at least one successive position, the delta-latitude representing a deviation from the first latitude and the delta-longitude representing a deviation from the first longitude.
  • the size of a delta-longitude is generally smaller than the size of a complete longitude and the size of a delta-latitude is generally smaller than the size of a complete latitude. Therefore, message size may further be reduced by transmitting delta-positions.
  • the communication module may be configured to generate each message to include data of at least 16 positions, at least 356 positions or at least 710 positions. The more positions are sent within one message, the less headers need to be sent for a certain amount of positions. Data traffic may therefore be reduced.
  • the communication module may be configured to open a network socket to establish a connection with a central office.
  • the communication module may further configured to transmit the at least one message to the central office while the network socket is open and to close the network socket after transmission of a predetermined number of messages. In this way, less network sockets needs to be opened at the same time.
  • the communication module may be configured to transmit the at least one message using the Transmission Control Protocol or the User Datagram Protocol.
  • the communication module may be configured to include the latitude and longitude that define a position each with a precision of 6 decimals.
  • the communication module may also be configured to include the latitude and longitude that define a position each with a precision of 5 decimals. By reducing the number of decimals, the message size may be reduced, while the precision may still be acceptable for billing purposes.
  • the satellite system may comprise at least four satellites, wherein each satellite is configured to transmit signals, the signals comprising information about the time of transmission and/or the position of the respective satellite at the time of transmission.
  • the on-board unit may be configured to receive signals of at least four satellites of the satellite system at the same time when the on-board unit is in an operating mode and to determine its own position based on these signals. If signals of at least four satellites are received, the position of the on-board unit may be determined.
  • the road toll system may further comprise a central office, which is configured to receive the message from the communication module.
  • the central office may then do the necessary calculations for billing.
  • Figure 1 illustrates a road toll system including a satellite system 1, an on-board unit 2 and a central office 3.
  • the on-board unit 2 may be installed in a vehicle, for example.
  • the satellite system 1 may be a global navigation network system, for example, and may include at least four satellites (not shown).
  • the satellites are configured to continually transmit signals, the signals including the time of transmission and the position of the respective satellite at the time of transmission.
  • the on-board unit 2 may determine its own position. This is, however, only an example.
  • the position of the on-board unit 2 may be determined in any other suitable way.
  • Data X representing the position of the on-board unit 2 may then be transmitted to the central office 3 for billing. Billing may be based on a distance travelled, the time spent in a tolling zone, the location of the on-board unit 2 within the tolling zone and vehicle characteristics, for example.
  • the position of the on-board unit 2 may be determined in regular intervals, e.g. every second. This, however, is only an example. The position may be determined more or less often than every second.
  • a data transmission according to TCP/IP is schematically illustrated in Fig. 2 .
  • the TCP/IP provides, prepares and forwards data packets 4 over a network.
  • a data packet 4 that is sent from the on-board unit 2 to a central office 3 generally includes a header 41 and a message 42, which includes the position data that is needed for billing.
  • a data packet 4 may have a total size of 1492 bytes, for example.
  • the header 41 may include, among other data, the IP (Internet Protocol) address of the central office 3 and may have a size of 40 bytes.
  • the data packet 4, the header 41 and the message 42 may have a larger or a smaller size than specified above.
  • an acknowledgement 43 may be sent to the on-board unit 2 to confirm reception of the data.
  • Such acknowledgement 43 may have a size of 40 bytes, for example.
  • the acknowledgement 43 may include only a header, without any further message.
  • TCP/IP Transmission Control Protocol/Internet Protocol
  • UDP User Datagram Protocol
  • UDP uses a simple connectionless transmission model with a minimum of protocol mechanisms.
  • the central office 3 receives the data packet 5 (including a header 51 and a message 52) from the on-board unit 2, but does not send an acknowledgement in return.
  • the on-board unit 2 therefore, does not know if the central office 3 received a message.
  • the communication protocols described above, however, are only examples. Other communication protocols may be used as well to transmit data from the on-board unit 2 to the central office 3.
  • the message 42 of a data packet 4 is illustrated in more detail.
  • the message 42 may contain information about the serial number OBU SN of the on-board unit 2, which is transmitting the data. Further, the message 42 includes a data header and the payload, the payload including the position data.
  • a cyclic redundancy check CRC may be performed to detect accidental changes of the transmitted data. Therefore, a check value CRC of a fixed size may be included in the data packet, forming a codeword.
  • the check value CRC may have a size of 2 bytes, for example.
  • the receiving device either compares its check value with a freshly calculated check value or performs a CRC on the codeword and compares the resulting check value with an expected residue constant.
  • the data header, payload and check value CRC together have a certain size. This size may be determined and the data packet may further include information LEN about this size.
  • the serial number OBU SN of the on-board unit may have a size of 4 bytes.
  • the information LEN about the size of the data header, payload and check value CRC may have a size of 2 bytes.
  • Such data may be sent as plain text (non-encrypted text).
  • the data header may include a preamble (1 byte), information about the size of the message (2 bytes), information about the software version that is used by the on-board unit (1 byte), a timestamp (4 bytes), information about the version of the communication protocol (1 byte) and a command ID (1 byte).
  • the data header may, therefore, have a total size of 10 bytes.
  • information about more than one position is transmitted in one data packet. For example, information about 16 positions may be transmitted in one data packet. In this way, only one header is sent for several positions. If each determined position was sent within a separate packet, a header would be needed for every transmitted position. For each position, a timestamp (e.g. 4 bytes) as well as information about latitude (e.g. 4 bytes) and longitude (e.g. 4 bytes) may be transmitted (resulting in a total size of 12 bytes for each position). A position is generally sufficiently defined if both latitude and longitude are known.
  • the latitude specifies the north-south position of a point on the Earth's surface
  • the longitude specifies the east-west position of a point on the Earth's surface.
  • the vehicle position may be determined less often, e.g. every 2, 3, 4,... seconds. This, however, results in a less precise billing.
  • Another possibility to for reducing the total amount of sent data is to reduce the size of each data packet.
  • the size of a data packet may be reduced, if a timestamp is not sent for every position.
  • a timestamp may be transmitted only for the first position.
  • the timestamp is omitted.
  • the latitude and longitude may only be included for the first position in each data packet.
  • a "delta-latitude” and “delta-longitude” may be transmitted, meaning that not a complete position will be sent to the central office, but information about a deviation from the first position in the same data packet.
  • a data packet including delta-positions for following positions is schematically illustrated in Fig. 7 . Assuming that a complete position has a size of 8 bytes (4 bytes for latitude and 4 bytes for longitude), a delta-position may have a size of only 4 bytes (2 bytes latitude and 2 bytes longitude) .
  • the size for following positions is reduced by omitting the timestamp (or transmitting a delta-timestamp, respectively) and/or delta-positions are transmitted for following positions, more positions may be transmitted in one data packet (e.g. 30 or 303 positions instead of 16 positions), without exceeding the maximum size of the data packet. This further reduces the data transmission volume, as less headers need to be sent for the same number of positions.
  • a connection needs to be established between the on-board unit 2 and the central office 3.
  • This connection may be used for bidirectional data transmission.
  • TCP Transmission Control Protocol
  • both the on-board unit 2 and the central office 3 need to open a so-called network socket.
  • a network socket is an endpoint of an inter-process communication across a network. Opening a socket generally takes about 280 - 300 bytes. Data packets may be transmitted while the sockets are open. Further, acknowledgements may be sent from the central office 3 to the on-board unit 2 while the sockets are open. This is schematically illustrated in Fig. 8 .
  • header size 40 bytes
  • the size for each delta-latitude and delta-longitude may be further reduced, e.g. to 1 byte. If, for example, the delta-latitude and the delta-longitude each are transmitted with 6 decimals, the size of one delta-position may be 4 Bytes. The precision in such a case is very high (e.g. precision of 0,11132m). If the delta-latitude and delta-longitude are transmitted with only 5 decimals, for example, the size of one delta-position may be reduced to 2 Bytes. The precision (e.g. 1,113 m) may still be sufficient for billing.
  • the on-board unit 2 may include a processor 21.
  • the processor 21 may receive signals transmitted from the satellites of the satellite system 1.
  • the processor 21 may further process these signals, determine the position of the on-board unit 2 and may provide data relating to the position of the on-board unit 2.
  • the position data may either be stored in the on-board unit 2 for later transmission or may be transmitted without prior storing.
  • the on-board unit 2 may include a communication module 22.
  • the communication module 22 may transmit data to the central office 3.
  • the data may be transmitted to the central office 3 via a wireless data channel, for example. In this case, it is not required that the vehicle in which the on-board unit 2 is installed return to a billing station to read out the data.
  • the communication module 22 may transmit data to the central office 3 whenever a data connection is available.
  • the data may be transmitted in regular intervals. For example, the data may be transmitted at the end of each day. This is, however, only an example. Data may also be transmitted more or less regularly.
  • a method for operating an on-board unit 2 is illustrated in Fig. 11 .
  • the position of the on-board unit is determined (step 601). More precisely, the position may be determined in regular intervals.
  • Data representing the determined positions may then be provided (step 602) .
  • Such data may include at least one of a latitude, a longitude and a timestamp, the timestamp representing the time at which the correspondent position was determined.
  • a message is then generated, including the data of at least two successive positions (step 603) .

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)
  • Traffic Control Systems (AREA)

Claims (14)

  1. Unité embarquée sur véhicule (2) pour un système de péage routier, l'unité embarquée sur véhicule (2) comprenant
    un processeur (21 configuré pour déterminer la position de l'unité embarquée (2) à intervalles réguliers et fournir des données représentant les positions déterminées, les données comportant au moins une latitude, une longitude et un horodatage représentant l'heure à laquelle la position correspondante a été déterminée ; et
    un module de communication (22), configuré pour recevoir les données représentant les positions déterminées et générer au moins un message (42), chaque message (42) comportant les données d'au moins deux positions successives, moyennant quoi le message (42) comporte un en-tête et une charge utile de données, la charge utile comportant les données de position, dans laquelle le module de communication (22) est configuré en outre pour générer l'au moins un message (42) afin d'inclure un premier horodatage d'une première position dans chaque message (42) et d'omettre des horodatages d'au moins une position successive du même message (42).
  2. Unité embarquée (2) selon la revendication 1, dans laquelle le module de communication (22) est configuré pour générer chaque message (42) afin d'inclure une première latitude et une première longitude spécifiant une première position et au moins un delta de latitude et un delta de longitude spécifiant au moins une position successive, le delta de latitude représentant un écart par rapport à la première latitude et le delta de longitude représentant un écart par rapport à la première longitude.
  3. Unité embarquée (2) selon l'une des revendications 1 à 2, dans laquelle le module de communication (22) est configuré pour générer chaque message (42) afin d'inclure des données d'au moins 16 positions, d'au moins 356 positions ou d'au moins 710 positions.
  4. Unité embarquée (2) selon l'une des revendications précédentes, dans laquelle le module de communication (22) est configuré pour ouvrir une interface de connexion réseau pour établir une connexion avec un central (3).
  5. Unité embarquée (2) selon la revendication 4, dans laquelle le module de communication (22) est configuré en outre pour transmettre l'au moins un message au central (3) pendant que l'interface de connexion réseau est ouverte.
  6. Unité embarquée (2) selon la revendication 5, dans laquelle le module de communication (22) est configuré pour fermer l'interface de connexion réseau après la transmission d'un nombre prédéterminé de messages (42).
  7. Unité embarquée (2) selon l'une des revendications 4 à 6, dans laquelle le module de communication (22) est configuré pour transmettre l'au moins un message en utilisant le protocole TCP transmission ou le protocole UDP.
  8. Unité embarquée (2) selon l'une des revendications précédentes, dans laquelle le module de communication (22) est configuré pour inclure la latitude et la longitude qui définissent chacune une position avec une précision de 6 décimales.
  9. Unité embarquée (2) selon l'une des revendications 1 à 7, dans laquelle le module de communication (22) est configuré pour inclure la latitude et la longitude qui définissent chacune une position avec une précision de 5 décimales.
  10. Procédé de fonctionnement d'une unité embarquée sur véhicule (2) pour un système de péage routier, le procédé comprenant :
    la détermination de la position de l'unité embarquée (2) à intervalles réguliers ;
    la fourniture de données représentant les positions déterminées, les données comportant au moins une latitude, une longitude et un horodatage représentant l'heure à laquelle la position correspondante a été déterminée ;
    la génération d'un message (42), le message (42) comportant les données d'au moins deux positions successives, moyennant quoi le message (42) comporte un en-tête et une charge utile de données, la charge utile comportant les données de position ;
    le procédé comprenant en outre la génération de l'au moins un message (42) afin d'inclure un premier horodatage d'une première position dans chaque message (42) et d'omettre des horodatages d'au moins une position successive du même message (42).
  11. Système de péage routier comprenant :
    un système satellitaire (1) ; et
    une unité embarquée sur véhicule (2), selon l'une des revendications 1 à 9.
  12. Système de péage routier selon la revendication 11, dans lequel le système satellitaire (1) comprend au moins quatre satellites, dans lequel chaque satellite est configuré pour transmettre des signaux, les signaux comprenant des informations sur l'heure de transmission et/ou la position du satellite respectif au moment de la transmission.
  13. Système de péage routier selon la revendication 12, dans lequel l'unité embarquée (2) est configurée pour recevoir les signaux d'au moins quatre satellites du système satellitaire (1) simultanément lorsque l'unité embarquée (2) est en service et déterminer sa propre position en fonction de ces signaux.
  14. Système de péage routier selon l'une des revendications 11 à 13, comprenant en outre un central (3), lequel est configuré pour recevoir le message provenant du module de communication (22).
EP15465532.8A 2015-08-26 2015-08-26 Systeme de peage routier, unite embarquee et procede permettant de faire fonctionner une unite embarquee Active EP3136351B1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP15465532.8A EP3136351B1 (fr) 2015-08-26 2015-08-26 Systeme de peage routier, unite embarquee et procede permettant de faire fonctionner une unite embarquee

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
EP15465532.8A EP3136351B1 (fr) 2015-08-26 2015-08-26 Systeme de peage routier, unite embarquee et procede permettant de faire fonctionner une unite embarquee

Publications (2)

Publication Number Publication Date
EP3136351A1 EP3136351A1 (fr) 2017-03-01
EP3136351B1 true EP3136351B1 (fr) 2023-10-11

Family

ID=54291234

Family Applications (1)

Application Number Title Priority Date Filing Date
EP15465532.8A Active EP3136351B1 (fr) 2015-08-26 2015-08-26 Systeme de peage routier, unite embarquee et procede permettant de faire fonctionner une unite embarquee

Country Status (1)

Country Link
EP (1) EP3136351B1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3944203A1 (fr) 2020-07-23 2022-01-26 Toll Collect GmbH Procédé et système d'enregistrer des données de position dans un système de péage

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002031793A2 (fr) 2000-10-13 2002-04-18 Paxgrid Telemetric Systems Inc. Protocole de telemesure pour vehicules
US20040162673A1 (en) * 2002-03-28 2004-08-19 Numerex Investment Corp. Communications device for conveying geographic location information over capacity constrained wireless systems
WO2006072225A1 (fr) 2005-01-07 2006-07-13 Deutsche Telekom Ag Systeme de surveillance de transport
GB2424149A (en) 2005-03-07 2006-09-13 John Kielty Bell Wireless security system for tracking an individual
DE102005010888A1 (de) 2005-03-09 2006-09-21 Mps Solutions Gmbh Verfahren und Anordnung zur Positionsbestimmung
EP1909231A1 (fr) 2006-10-06 2008-04-09 Deutsche Telekom AG Enregistrement de péage routier
GB2448743A (en) 2007-04-26 2008-10-29 Eads Defence And Security Systems Ltd Bi-directional communication in an asset tracking system
DE102009042470A1 (de) 2009-09-24 2011-03-31 Bähring, Horst, Dr. Anordnung und Verfahren zur Erfassung von Gebühren auf mautpflichtigen Straßen
US20110112717A1 (en) 2009-11-11 2011-05-12 Benjamin Resner Methods and Apparatus for Automatic Internet Logging and Social Comparison of Vehicular Driving Behavior

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE4402614A1 (de) * 1994-01-28 1995-08-03 Deutsche Telekom Mobil Verfahren zur Ermittlung von Gebühren für die Nutzung von Verkehrswegen durch Fahrzeuge
AUPN437395A0 (en) * 1995-07-24 1995-08-17 D & E Consulting Pty Ltd System and method for determining the distance travelled by a vehicle
GB2510174B (en) * 2013-01-28 2016-02-24 Canon Kk Method and device for encoding headers of a message using an in-memory indexing table
US20150088618A1 (en) * 2013-08-26 2015-03-26 Ims Solutions, Inc. Road tolling

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002031793A2 (fr) 2000-10-13 2002-04-18 Paxgrid Telemetric Systems Inc. Protocole de telemesure pour vehicules
US20040162673A1 (en) * 2002-03-28 2004-08-19 Numerex Investment Corp. Communications device for conveying geographic location information over capacity constrained wireless systems
WO2006072225A1 (fr) 2005-01-07 2006-07-13 Deutsche Telekom Ag Systeme de surveillance de transport
GB2424149A (en) 2005-03-07 2006-09-13 John Kielty Bell Wireless security system for tracking an individual
DE102005010888A1 (de) 2005-03-09 2006-09-21 Mps Solutions Gmbh Verfahren und Anordnung zur Positionsbestimmung
EP1909231A1 (fr) 2006-10-06 2008-04-09 Deutsche Telekom AG Enregistrement de péage routier
GB2448743A (en) 2007-04-26 2008-10-29 Eads Defence And Security Systems Ltd Bi-directional communication in an asset tracking system
DE102009042470A1 (de) 2009-09-24 2011-03-31 Bähring, Horst, Dr. Anordnung und Verfahren zur Erfassung von Gebühren auf mautpflichtigen Straßen
US20110112717A1 (en) 2009-11-11 2011-05-12 Benjamin Resner Methods and Apparatus for Automatic Internet Logging and Social Comparison of Vehicular Driving Behavior

Also Published As

Publication number Publication date
EP3136351A1 (fr) 2017-03-01

Similar Documents

Publication Publication Date Title
EP2017790A2 (fr) Chargement selon la position
US8489327B2 (en) Navigation device and method for providing alternative network connections
US8896468B2 (en) Control method for a road toll system
US11223934B2 (en) Road-vehicle communication system, roadside communication apparatus, in-vehicle communication apparatus, and road-vehicle communication method
US20060166656A1 (en) Cell or mobile phone, and wireless PDA traffic advisory method
US20070016539A1 (en) Smart meter parking system
CN105974453A (zh) 基于智能车路协同系统的差分定位方法及智能车路协同系统
Al-Taee et al. Remote monitoring of vehicle diagnostics and location using a smart box with global positioning system and general packet radio service
CN101379536A (zh) 智能实时分布式交通采样和导航系统
WO2006088316A1 (fr) Service d'informations de circulation reposant sur les informations de circulation envoyees a un systeme de navigation
US7526380B2 (en) Method and system to provide a global multiuser service of localization information with integrity as required under liability or commercial issues
US9269197B2 (en) Method and device for generating toll information in a road-toll system
US9092913B2 (en) Method for providing location-specific data services
HUP0402035A2 (hu) Eljárás és rendszer elektronikus úthasználati díjelszámolásra
CN111835811A (zh) 用于校正车辆位置的方法、电子设备和计算机可读介质
EP3136351B1 (fr) Systeme de peage routier, unite embarquee et procede permettant de faire fonctionner une unite embarquee
GB2425858A (en) Map correction
US8768619B2 (en) Road side data exchange net and method thereof
US7599788B1 (en) System and method for monitoring the movement of one or more vehicles
WO2012002838A2 (fr) Procédé de transmission de données concernant la localisation et l'état de véhicules dans des systèmes de surveillance des transports
WO2004097747A2 (fr) Dispositif de paiement d'une taxe d'encombrement
RU113396U1 (ru) СПУТНИКОВЫЙ ТЕЛЕМАТИЧЕСКИЙ КОМПЛЕКС ГЛОНАСС/GPS С ИСПОЛЬЗОВАНИЕМ КАНАЛОВ СВЯЗИ Inmarsat D+/GPRS
Toledo et al. An integrity navigation system based on GNSS/INS for remote services implementation in terrestrial vehicles
Hong et al. Event Information Delivery Method Using Location Information for Route Replanning in V2I Local Environment
KR101612323B1 (ko) 능동형 단거리 전용 통신을 활용한 가상 영업소의 위치 정보 및 보정용 위성 위치 확인 시스템 정보 전송 시스템

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

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

Free format text: STATUS: THE APPLICATION HAS BEEN PUBLISHED

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

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

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20170901

RBV Designated contracting states (corrected)

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

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

Owner name: CONTINENTAL AUTOMOTIVE GMBH

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

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

Owner name: CONTINENTAL AUTOMOTIVE TECHNOLOGIES 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

GRAJ Information related to disapproval of communication of intention to grant by the applicant or resumption of examination proceedings by the epo deleted

Free format text: ORIGINAL CODE: EPIDOSDIGR1

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

Free format text: STATUS: EXAMINATION IS IN PROGRESS

INTG Intention to grant announced

Effective date: 20230116

INTC Intention to grant announced (deleted)
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: 20230411

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

Effective date: 20230522

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

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602015086036

Country of ref document: DE

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: NL

Ref legal event code: FP

REG Reference to a national code

Ref country code: SK

Ref legal event code: T3

Ref document number: E 42711

Country of ref document: SK

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R081

Ref document number: 602015086036

Country of ref document: DE

Owner name: CONTINENTAL AUTOMOTIVE TECHNOLOGIES GMBH, DE

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

P02 Opt-out of the competence of the unified patent court (upc) changed

Effective date: 20240207

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1621001

Country of ref document: AT

Kind code of ref document: T

Effective date: 20231011

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

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

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

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

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

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

Effective date: 20231011

RAP4 Party data changed (patent owner data changed or rights of a patent transferred)

Owner name: CONTINENTAL AUTOMOTIVE TECHNOLOGIES GMBH

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

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

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

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

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

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

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

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

Ref country code: AT

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

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

REG Reference to a national code

Ref country code: CH

Ref legal event code: PK

Free format text: DIE PUBLIKATION VOM 27.03.2024 WURDE AM 24.04.2024 IRRTUEMLICHERWEISE ERNEUT PUBLIZIERT. LA PUBLICATION DU 27.03.2024 A ETE REPUBLIEE PAR ERREUR LE 24.04.2024. LA PUBBLICAZIONE DEL 27.03.2024 E STATA ERRONEAMENTE RIPUBBLICATA IL 24.04.2024.

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

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

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

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

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

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

REG Reference to a national code

Ref country code: DE

Ref legal event code: R026

Ref document number: 602015086036

Country of ref document: DE

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

PLBI Opposition filed

Free format text: ORIGINAL CODE: 0009260

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

PLAX Notice of opposition and request to file observation + time limit sent

Free format text: ORIGINAL CODE: EPIDOSNOBS2

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

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

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

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

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

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

26 Opposition filed

Opponent name: TOLL COLLECT GMBH

Effective date: 20240708

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

Ref country code: DE

Payment date: 20240831

Year of fee payment: 10

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

Ref country code: BE

Payment date: 20240821

Year of fee payment: 10

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

Ref country code: FR

Payment date: 20240829

Year of fee payment: 10

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

Ref country code: CH

Payment date: 20240901

Year of fee payment: 10

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

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

Ref country code: SK

Payment date: 20240820

Year of fee payment: 10

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

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

Ref country code: IT

Payment date: 20240827

Year of fee payment: 10

PLBB Reply of patent proprietor to notice(s) of opposition received

Free format text: ORIGINAL CODE: EPIDOSNOBS3

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

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

Effective date: 20240826

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

Effective date: 20231011

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

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 NON-PAYMENT OF DUE FEES

Effective date: 20240826

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

Ref country code: NL

Payment date: 20250821

Year of fee payment: 11

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

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