EP1708144B1 - Dispositif et procédé destinés à l'échange de données de péage dans des systèmes d'identification par radiofréquence - Google Patents

Dispositif et procédé destinés à l'échange de données de péage dans des systèmes d'identification par radiofréquence Download PDF

Info

Publication number
EP1708144B1
EP1708144B1 EP06004736A EP06004736A EP1708144B1 EP 1708144 B1 EP1708144 B1 EP 1708144B1 EP 06004736 A EP06004736 A EP 06004736A EP 06004736 A EP06004736 A EP 06004736A EP 1708144 B1 EP1708144 B1 EP 1708144B1
Authority
EP
European Patent Office
Prior art keywords
toll
obu
board
interface
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.)
Not-in-force
Application number
EP06004736A
Other languages
German (de)
English (en)
Other versions
EP1708144A2 (fr
EP1708144A3 (fr
Inventor
Peter Selmayr
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.)
M2C Solutions GmbH
Original Assignee
MPS Solutions 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=36659950&utm_source=google_patent&utm_medium=platform_link&utm_campaign=public_patent_search&patent=EP1708144(B1) "Global patent litigation dataset” by Darts-ip is licensed under a Creative Commons Attribution 4.0 International License.
Priority claimed from DE200510010888 external-priority patent/DE102005010888A1/de
Priority claimed from DE202005009152U external-priority patent/DE202005009152U1/de
Priority claimed from DE102005030030A external-priority patent/DE102005030030A1/de
Application filed by MPS Solutions GmbH filed Critical MPS Solutions GmbH
Publication of EP1708144A2 publication Critical patent/EP1708144A2/fr
Publication of EP1708144A3 publication Critical patent/EP1708144A3/fr
Application granted granted Critical
Publication of EP1708144B1 publication Critical patent/EP1708144B1/fr
Not-in-force 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
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00—Registering or indicating the working of vehicles
    • G07C5/008—Registering or indicating the working of vehicles communicating information to a remotely located station
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/20—Monitoring the location of vehicles belonging to a group, e.g. fleet of vehicles, countable or determined number of vehicles

Definitions

  • the present invention relates to an apparatus and a method for toll collection and / or for the collection and calculation of toll-related data of a vehicle.
  • the invention relates to such toll collection systems that are based on a so-called DSRC communication (DSRC D edicated- S hort- R reasonable ommunication C).
  • Previously known DSRC systems of the prior art include a DSRC tag containing a unique code.
  • the tag may be formed as a small box that can be attached to the car or to the windshield.
  • a one-to-one relation between a vehicle and a DSRC tag is provided so that the DSRC tag can uniquely identify the particular vehicle.
  • the system includes beacons arranged on the street and comprising electronic modules adapted for data exchange with the DSRC tag and optionally with further units. A vehicle passing the respective beacon is uniquely registered and detected by the beacon via its DSRC tag.
  • the data captured by the beacon must now be transmitted to a local back office of the respective toll operator, which further processes this data for the purpose of toll collection.
  • the local toll system for vehicles shows mobile devices which are arranged in means of transport and which are set up for communication with a central station on the one hand and with a plurality of stationary base stations on the other hand.
  • a corresponding communication is initiated by the electronic module in the beacon whenever a vehicle with a DSRC tag the DSRC-Bake happens.
  • the DSRC tag sends its identification to the beacon and the DSRC tag can receive all relevant data of the beacon.
  • the electronic module of the beacon is designed as a transmitting and receiving module and is with respect to the DSRC data exchange, the active component. Accordingly, the beacon sends the relevant data, in particular the identification of the vehicle and a time stamp of the data collection on to the back office of the respective toll operator, in order to be able to carry out the tariff calculation and invoicing there.
  • DSRC communication a major disadvantage of DSRC communication is the fact that it is designed for short distances, especially for those under 8 meters, and is only very limited operational capability. Furthermore, such prior art systems are susceptible to errors because there are no alternative ways to collect toll-related data. That is, if the data acquisition of a passing vehicle in the beacon has not been performed or is not completed or erroneous, the toll calculation can not be performed. Alternative ways to provide the necessary data in other ways are not possible due to the short distance limitation.
  • the object of the present invention is therefore to propose a way of ensuring the interoperability of different toll-related systems so that it becomes possible to exchange data relating to toll-related data, in particular the associated data Synchronization effort, to improve and to ensure greater flexibility.
  • the desired flexibility is particularly relevant if additional toll operators are to be added and / or if toll-related data of an existing toll operator changes. This is relatively often the case, since on the one hand, the legal provisions and on the other hand, the technical requirements of the local toll operators can change relatively quickly.
  • This object is achieved by a method for processing toll-related data of a vehicle, the vehicle comprising an on-board unit which is in communication with a plurality of beacons arranged on a toll road, the on-board Unit the data of the data exchange between the on-board unit and the beacons traveled by the vehicle via a back-office interface to a central back-office for processing the toll-related data, in particular for calculating a toll for the traveled distance of the vehicle, forwards.
  • the present invention is based on the basic concept that a plurality of on-board mobile units (each attached to a vehicle and in one-to-one relation with the respective vehicle) and a central back-office, a so-called Europe OBU system, to which the respective toll operators are connected via a single interface.
  • a so-called Europe OBU system to which the respective toll operators are connected via a single interface.
  • the central idea is that the processing of toll-related data is no longer decentralized to the respective toll operator, but centrally in the OBU system, ie in the central back-office.
  • the present invention solves the above problem by designing an on-board unit to forward toll-related data or all data relevant to toll collection to the central back-office.
  • the toll system is a DSRC system.
  • the toll-related data is thus sent from the beacon to the on-board unit, which forwards it individually or in a batch to the central back-office.
  • the respective beacon sends a DSRC request to the passing vehicle sending its DSRC tag identification to the beacon.
  • the beacon sends the data received from the DSRC tag and a timestamp of data collection to the back office for tariff calculation and billing.
  • the DSRC tag or the known on-board unit of the vehicle also receives a record that includes all relevant data of the current beacon. However, this data will not be used further.
  • the known from the prior art on-board unit stores this data only for control purposes. So far, so the beacon is the active element that sends the toll-related data to the assigned toll operator while the DSRC tag or the known on-board unit remains passive.
  • the beacon is inventively designed as a passive element and serves to transfer all relevant data of the beacon only to the on-board unit and not - as before - to other instances.
  • the on-board unit is designed as an active element which sends the data received from the beacon to the central OBU back-office, possibly after buffering in a buffer memory.
  • a significant advantage of the solution according to the invention is the fact that the existing DSRC systems need not be changed and can be used without restriction in the context of the present inventive solution.
  • the data set sent by the beacon to the on-board unit anyway is merely processed further so that the unique beacon information and a time stamp are transmitted to the central back-office.
  • the data of the on-board unit received by the beacon is in principle not further processed by the on-board unit.
  • this data transmission is optional and not necessary for the operation of the system.
  • the DSRC technique used by the different toll operators may differ. Especially with regard to the DSRC protocol used, with regard to the frequencies used, the signal coding, etc. It is In order to exchange toll-related data from different toll operators, possibly with different DSRC techniques, interoperability between the respective DSRC techniques must be ensured. This is possible according to the invention. Due to the inventively extended functionality of the on-board unit, it is possible that this automatically detects their position. In the preferred embodiment of the invention, it is provided that the on-board unit recognizes its position automatically via the detection of satellite-supported position data. This data can be compared with a geo-file, so that it is possible to automatically detect in which toll carrier area the vehicle is currently located.
  • the information about the toll operator can be obtained via the country code.
  • the OBU can then automatically determine which communication technology the respective toll operator uses, eg which protocol and / or the required syntax and / or semantics for the data exchange.
  • the on-board unit can automatically configure the interface between the beacon and the on-board unit, depending on the toll operator's determined communication technology.
  • the flexibility of the toll collection system can be significantly increased by the current requirements for data exchange automatically recorded and implemented or generated.
  • the risk of errors can be significantly reduced by a false or erroneous data exchange and / or by an incorrect adaptation to the respective requirements with regard to the data exchange.
  • the road network may be an open system, such as in Austria.
  • the term "open” is intended here to indicate that the entry into and out of the toll road network does not necessarily have to be coupled with the passage through a beacon.
  • a predeterminable toll route length is defined when passing through a beacon. This toll route in relation to the beacon in this case also belongs to the toll-related data and is stored in the back-office.
  • the traveled route can be calculated according to the invention in the back office.
  • the method according to the invention, and in particular the calculation of the route traveled, are carried out independently of whether the toll route network is an open system or a closed system.
  • the on-board unit is formed with a position detection module, so that it is possible to automatically determine the exact position of the vehicle. As a rule, this is satellite-based, via a corresponding GPS receiver and / or via a Galileo receiver or similar receivers for satellite-supported position data. Due to the detected position data, it is possible for the on-board unit according to the invention to initiate activation and / or deactivation of the interface between the on-board unit and the beacon. According to the invention, it is provided that the on-board unit automatically detects whether the vehicle is currently in an area of a toll operator with DSRC communication and, if so, activates the beacon interface and / or otherwise deactivates the beacon interface. This has the advantage that unwanted data exchange via the interface can be avoided.
  • the beacon interface is designed such that each beacon transmits at least one unambiguous beacon identification and / or a time stamp of the data collection to the respective on-board unit of the passing vehicle.
  • further data sets e.g. Data relating to predecessor and / or successor beacons, etc. are transmitted.
  • the communication between the beacon and the on-board unit is based on the DSRC communication technique.
  • the DSRC standard such as the CEN standard ( C omite E uropeen de N ormalisation / European Commitee for Standardization) or the UNI standard (UNInfo Italian Standard UNI10607).
  • the back-office interface that is, the interface between the on-board unit and the back-office, is usually designed so that the on-board unit all toll-related data of the vehicle, especially the data exchange with the drivers Beacons, to the central back office transfers.
  • the central back-office sends back a corresponding receipt acknowledgment to the on-board unit after the transfer of the toll-related data from the on-board unit to the back-office, the error-free communication To signal exchange.
  • a successful data exchange via the beacon interface So between the on-board unit and the beacon, signaled by a corresponding signal to the on-board unit and / or to the beacon.
  • the toll-related data In principle, different modalities are provided for the transfer of the toll-related data from the on-board unit to the central back-office.
  • a plurality of toll-related data records it is possible for a plurality of toll-related data records to be buffered in a buffer memory and for configurable time intervals and / or depending on the occurrence of a configurable event (eg the departure of a particular link or a request from the back-office or another instance) to the backend Office are transmitted.
  • the data can be transferred directly to the back-office.
  • the modalities of data transmission are configurable. So it is particularly adjustable, after which time interval or after which event the data should be transmitted. This can be done via a corresponding user input via a user interface in the back office.
  • the interfaces are air interfaces.
  • the data exchange can be handled via the mobile network.
  • a significant advantage of the solution according to the invention is the fact that the interfaces; In particular, the interfaces between the on-board units and the back-office are uniformly formed. This has the advantage that extensions of the system can be easily implemented.
  • the interface in particular the back-office interface - ie the interface between the on-board unit and the central back-office - independent of the toll operator. This makes it possible to use one and the same on-board unit for a variety of different toll operators, without further reconfigurations are necessary.
  • all toll-related data streams are merged in the central back-office.
  • the central back office is accordingly designed with interfaces to the respectively connected toll operator and / or optionally to other
  • the present invention is particularly directed to the interoperability between different toll related systems and different toll operators.
  • an international user ie a user of a vehicle in international operation
  • Registration and / or billing or toll collection takes place only once, preferably at a local toll operator and / or at a billing partner.
  • the user indicates all countries where he wants a toll collection.
  • the vehicle data and all other registration data are stored in the central back-office of the European OBU system and the user receives a European OBU with a unique identification number, a so-called OBU-ID.
  • the central Europe OBU system operates with the number range or with the identification numbers of the local toll operators.
  • all activated toll operators are informed about the assignment of an identification number for a registered vehicle. This ensures that the system is interoperable and can also be used internationally. Furthermore, it can be ensured that the correct local or local OBU identification number (according to the mapping table) is always used.
  • the above-mentioned transmission of information need not necessarily take place. The toll operator releases a number range, which can then be activated. In this case the toll operator does not know when an ID is mapped with the Europa OBU.
  • All identification numbers transmitted by the local toll operator to the central European OBU system are identified as valid identification numbers by the respective local toll operator. This also applies to packet-wise transmitted identification numbers and number ranges already transmitted in the past.
  • a vehicle or its users can register in the OBU system in different ways: First, he can register with the local toll operator who then the registration data via an interface to the central OBU system. On the other hand, he can also register centrally directly with the European OBU system.
  • a security mechanism is provided in the preferred embodiment that monitors the interface between the on-board unit and the central back-office.
  • a transfer of manipulated data records can be limited or completely excluded.
  • the on-board unit Only after successful generation of a session key, the on-board unit is ready to collect and can receive data from the beacon. Before the generation of a session key or an unsuccessful generation of the same, the interface between the on-board unit and the beacon is deactivated. If the attempt to generate the session key fails, at least one new retry attempt can be started. How many retries are possible is also presettable. If the generation fails - possibly after multiple retry attempts - the on-board unit will acknowledge all communication requests or all transactions with the DSRC system negatively or alternatively will not respond to the DSRC requests. The local DSRC beacon recognizes this negative or failed communication and may initiate appropriate further action based on the detected miscommunication. Usually, a so-called Enförcement process is initiated here for the toll car. If the lifetime of a session key has expired, it is provided that the on-board unit generates a new session key in good time and in advance.
  • Another security measure is to ensure that all toll-related data sent by the beacon, which is stored in the on-board unit, is also forwarded to the back-office. If there is an error in the interface between the on-board unit and the central back-office so that it is no longer possible to transfer this toll-related data, it must be ensured that the data previously collected in the on-board unit do not get lost. For this purpose, it is provided that it is checked whether after a configurable number of received DSRC data records, these have also been transmitted successfully to the back-office. For the maximum number, a threshold value can be defined. If this threshold of maximum entries has been exceeded without a successful transfer to the back office, the interface between the on-board unit and the beacon is deactivated. That is, the on-board unit stops any DSRC communication. This means that no new data is collected and the data collected so far are stored in the buffer memory.
  • the user of the vehicle is notified by a signal to the fault.
  • the signal can be acoustic and / or visual.
  • the signal serves as an indication that it is not possible to continue because the on-board unit is not ready for collection. He is therefore requested to leave the toll road.
  • the error signal is sent to the beacon and / or to the central back-office. This makes it possible to initiate further recovery measures.
  • a further problem solution according to the invention lies in the provision of the on-board unit for processing toll-related data of a vehicle, the vehicle being equipped with the on-board unit according to the invention, which in turn has a beacon interface for data transmission with a large number of on roads arranged beacons and a back-office interface for transmission to a central back-office, wherein the back-office is intended for processing the toll-related data and wherein the data exchange between the beacon and the on-board unit, in particular on a DSRC Communication technology.
  • the on-board unit comprises a position detection unit which is adapted to automatically detect the current toll operator via the satellite-based position detection of the vehicle, and wherein the on-board unit continues a configuration module comprises for the automatic determination of a communication technique used by the detected toll operator, in particular a transmission protocol, and for the automatic configuration of the beacon interface (BSS) in dependence on the determined communication technology of the toll operator.
  • BSS beacon interface
  • the on-board unit according to the invention can therefore also be referred to as a "virtual DSRC tag". It is preferably in the form of an integrated circuit and thus a smarter and more complex solution than the previous DSRC tag.
  • the inventive virtual DSRC tag is characterized by increased functionality.
  • the on-board unit according to the invention is designed to temporarily store toll-related data that it receives from the beacon and forward it to the central back-office via the back-office interface after a configurable time interval.
  • a particular advantage of the solution according to the invention is that the method steps, preferably all method steps, are carried out automatically. It is no longer necessary for the user to intervene manually in the processing process. Thus, the error rate of the overall system can be significantly reduced.
  • An alternative task solution provides a storage medium which is intended to store the above-described computer-implemented method and is readable by a computer.
  • the invention may also be used to otherwise process the toll related data.
  • toll collection here are e.g. to use in other accounting systems, clearing systems, fleet management systems or the like.
  • Every vehicle that wants to use the Europe OBU system is equipped with an on-board unit OBU.
  • the toll collection is based on the DSRC technique.
  • On a toll road beacons 16 are arranged, which include electronic modules that are intended for data exchange with a corresponding module in the vehicle.
  • the electronic modules arranged in the vehicle were DSRC tags.
  • the functionality of the previously known DSRC tags is of functionality comprises the on-board units OBU used according to the invention.
  • the on-board units OBU according to the invention have a more complex functionality and preferably comprise a buffer memory 10 which can buffer the data received by the beacon 16.
  • the on-board unit OBU consists of a receiving unit for receiving toll-related data from the beacon 16 and a transmitting unit, which is intended to forward the data thus received to a central back-office BO.
  • the interface between the back-office BO and the on-board unit OBU is identified as the back-office interface BoSS.
  • the interface between the on-board unit OBU and the beacon 16 is identified as a beacon interface BSS.
  • the processing of the toll-related data takes place centrally in the back-office BO.
  • the toll-related data is no longer transferred from the beacon 16 to the back-office BO as before, but by the mobile on-board unit OBU via the back-office interface BoSS.
  • the beacon 16 it is possible, but not essential, for the beacon 16 to send toll-related data relating to a passing vehicle to a local toll operator. According to the invention, this is only provided if an additional control method is desired.
  • the local toll operator then receives toll related data from both the central back office BO and the beacon 16 itself. Preferably, however, the beacon 16 does not send data to the local toll operator.
  • the decentralized local toll operators are connected via an appropriate transaction interface to the central back office BO.
  • a vehicle registers with the local toll operator or back-office BO, and receives an identification number that uniquely identifies its vehicle. If the user has registered with the local toll operator, the registration data is transmitted via the transaction interface to the central back office BO. In the registration process, the user can specify in which countries or in which areas he activates the according to the invention or toll collection wishes. However, it is also possible later, so to speak while driving, further areas or other countries nachzulit.
  • the on-board unit OBU comprises a position detection unit which is intended to detect the current position of the vehicle.
  • the on-board unit OBU can autonomously and automatically determine whether the vehicle is currently located in one of the registered toll operator areas. Typically, the areas are DSRC areas. If the vehicle is not located in such an area, the interfaces remain disabled. Otherwise, the on-board unit OBU can automatically determine on which communication technology the data exchange of the respective toll operator is based. The on-board unit OBU thus automatically recognizes which interface-specific parameters are necessary for the data exchange between the on-board unit OBU and the current beacon 16, in particular which transmission protocol, which coding etc. is necessary. In accordance with the determined communication-technical data, the on-board unit OBU automatically and independently configures the beacon interface BSS between the on-board unit OBU and the beacon 16.
  • a uniform on-board unit OBU can be used for different toll operators without the user having to intervene, e.g. by exchanging DSRC tags - as before - or by switching certain functions.
  • the on-board unit OBU sends its OBU identification number to the beacon 16 and receives all toll-relevant data from the beacon 16.
  • the toll-relevant data in this case is a beacon identification number and a timestamp for a survey of the data record.
  • the advantage of this embodiment is the fact that the transmission method between the on-board unit OBU and the beacon 16 from the previously known systems can be fully maintained and does not need to be changed.
  • beacon 16 it is provided to change the previously known data exchange between on-board unit OBU and beacon 16 to the effect that the beacon 16 is formed only as a transmitting unit.
  • the beacon 16 then receives no data, in particular no identification number of the on-board unit OBU and therefore can no longer forward it to local toll operators for control purposes. It is only designed to transfer beacon-specific data and possibly other toll-related data to the on-board unit.
  • the toll-related data received by the on-board unit OBU can either be forwarded directly to the central back-office BO or buffered in a buffer memory 10.
  • the data records held in the buffer memory 10 may be determined via a threshold. Once the threshold is reached, the data records are forwarded from the buffer memory 10 of the on-board unit OBU via the back-office interface BoSS to the back-office BO.
  • the back-office BO is formed with a transaction unit 14, which is intended to process the accumulated toll-related data records into an overall result for the toll collection.
  • the collected toll is then fed via the interface to the respective toll operator, in which the user has registered.
  • the back-office interface BoSS is preferably based on a proprietary protocol. In an alternative development of the invention, however, it is also possible to use another known protocol here.
  • the beacon interface BSS is based on the DSRC communication technology. However, fundamentally different physical characteristics of the DSRC technique are possible. The The respective physical characteristics of the DSRC technology used by the respective toll operator can be automatically recognized by the on-board unit OBU. This information is used according to the invention for the configuration of the beacon interface BSS.
  • the back office BO comprises a mapping unit 12.
  • the management of the mapping table takes place in the back office BO.
  • a current extract of the table must be kept in the on-board unit OBU in order to be able to use the correct OBU ID, if necessary.
  • the mapping unit 12 is designed to provide a one-to-one mapping rule between the toll operator's local identification numbers and the central OBU system's identification numbers. This makes it possible for the Europe OBU system to work either with a central identification number assignment or with the identification numbers of the local toll operator.
  • the allocation of identification numbers from the OBU-ID number range, which a toll operator can provide is organized such that the respective identification numbers are available in a list and are used sequentially with each new registration of a vehicle.
  • Fig.2 it is possible according to the invention to provide an interoperable exchange between any number of toll operators.
  • the respective toll operators are via the DSRC interface with the respective beacons 16 in the data exchange and are in addition to the data exchange with the central back-office BO in addition to each other in data exchange.
  • This usually takes place via a uniform transaction interface and / or via a uniform interface for exchanging user, vehicle and / or identification number data.
  • additional additional toll-related data can be exchanged via this interface.
  • the central processing according to the invention in the back office the synchronization effort can be significantly reduced.
  • system extensions are easy to implement. In contrast to known methods, it is no longer necessary for a user to be in such a toll operator area registered in which he will not drive. This can reduce transaction and administration costs.
  • the back-office BO is designed as a Europe OBU system. All vehicle data is stored centrally in the Europe OBU system. This makes it much easier to use the system internationally, allowing a user to use foreign DSRC systems without the need for a new DSRC tag, or without the need for further manual intervention.
  • the on-board unit OBU recognizes from the current position (the automatic position determination is preferably satellite-based) whether it is located in an area of a DSRC toll operator. If a DSRC area is detected, the OBU application automatically configures the integrated DSRC modem. However, it is also possible that the on-board unit OBU is equipped with several DSRC modems. The configuration takes place in such a way that communication can take place on the basis of the technology employed by the toll operator. This means that the OBU application controls the protocol and the semantic content depending on the respective toll operator. Only different physical characteristics of the DSRC technique (CEN, UNI) require different DSRC modules / modems in the on-board unit OBU.
  • CEN UNI
  • the "European OBU system” is the central back-office BO.
  • the toll - related data converges and is distributed to the respective toll operators or to their transaction partners.
  • the toll operators communicate with the back office BO via an interface via which, in particular, the provided identification number circles are assigned.
  • the transfer of the identification numbers can be done automatically but also manually. This means that the identification number circles can be automatically read in via an interface from a provided file. It is also possible that the number circles are read on other communication channels, such as by a manual input via a user interface, an input via e-mail, etc.
  • the interface between the respective toll operators and operated by them beacons 16 may advantageously remain unchanged. An adjustment is not required here.
  • the central Europe OBU system BO communicates with the transaction and / or transaction partners via a unified transaction interface, providing fast and easy interoperability.
  • the interface between the back office or the European OBU system BO and the local toll operators can also be any interface and need not be a wireless connection.

Landscapes

  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Business, Economics & Management (AREA)
  • Finance (AREA)
  • Devices For Checking Fares Or Tickets At Control Points (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Position Fixing By Use Of Radio Waves (AREA)

Claims (13)

  1. Procédé pour le traitement des données de péage d'un véhicule, le véhicule comprenant un dispositif embarqué [On-Board-Unit - OBU -] qui est en échange de données avec une pluralité de balises (16) - disposées sur une route praticable - à travers une interface de balise (BSS), le dispositif embarqué [On-Board-Unit - OBU] transmettant les données de péage de l'échange de données entre le dispositif embarqué [On-Board-Unit - OBU] et les balises (16) fréquentées par le véhicule à travers une interface Back Office (BoSS) (interface de bureau administratif) avec un Back Office central (BO) pour le traitement des données de péage relatif à l'itinéraire fréquenté par le véhicule,
    caractérisé en ce que
    le dispositif embarqué [On-Board-Unit - OBU] réalise les étapes suivantes :
    - détermination automatique de l'exploitant de péage actuel dans chaque cas au moyen d'une recherche de position par satellite du véhicule,
    - identification automatique de la technique de communication utilisée par l'exploitant de péage saisi, notamment d'un protocole de transmission,
    - configuration automatique de l'interface de balise (BSS) en fonction de la technique de communication identifiée de l'exploitant de péage.
  2. Procédé selon la revendication précédente,
    caractérisé en ce que
    le dispositif embarqué [On-Board-Unit - OBU] saisi automatiquement si le véhicule se trouve dans une zone d'un l'exploitant de péage avec communications spécialisées à courte portée (DSRC) en recherchant la position du véhicule par satellite, et dans l'affirmative, en activant et/ou désactivant l'interface de balise (BSS).
  3. Procédé selon au moins l'une des revendications précédentes,
    caractérisé en ce que
    l'interface de balise (BSS) est configurée en sorte que chaque balise (16) transmet à chaque dispositif embarqué [On-Board-Unit - OBU] passant au moins un code d'identification univoque de balise et/ou une estampille pour une collecte de données.
  4. Procédé selon au moins l'une des revendications précédentes,
    caractérisé en ce que
    l'interface Back Office (BoSS) (interface de bureau administratif) est configurée en sorte que le dispositif embarqué [On-Board-Unit - OBU] transmet toutes les données de péage du véhicule - notamment l'échange de données avec les balises (16) fréquentées - au Back Office central (BO).
  5. Procédé selon au moins l'une des revendications précédentes,
    caractérisé en ce que
    le dispositif embarqué [On-Board-Unit - OBU] mémorise temporairement les données de péage et les transmet au Back Office (BO) dans des intervalles configurables et/ou en fonction de l'occurrence d'au moins un événement configurable.
  6. Procédé selon au moins l'une des revendications précédentes,
    caractérisé en ce que
    que l'interface (BSS, BoSS) est une interface aérienne.
  7. Procédé selon au moins l'une des revendications précédentes,
    caractérisé en ce que
    l'interface de balise (BSS) est configurable automatiquement et/ou que les interfaces Back Office (BoSS) (interfaces de bureau administratif) sont unitaires et/ou indépendantes de l'exploitant de péage respectif.
  8. Procédé selon au moins l'une des revendications précédentes,
    caractérisé en ce que
    des exploitants de péage ultérieurs et/ou des instances ultérieures peuvent être raccordés au Back Office (BO) pour le traitement des données de péage.
  9. Procédé selon au moins l'une des revendications précédentes,
    caractérisé en ce
    qu'un numéro d'identification est attribué à chaque véhicule en ayant accès à un règlement d'attribution biunivoque qui peut être attribué de manière décentralisée par un exploitant de péage local ou de manière centralisée par le Back Office (BO).
  10. Procédé selon au moins l'une des revendications précédentes,
    caractérisé en ce que
    l'itinéraire fréquenté par le véhicule, notamment une longueur de l'itinéraire fréquenté, est calculée dans le Back Office (BO).
  11. Procédé selon au moins l'une des revendications précédentes,
    caractérisé en ce que
    la route est attribuée à au moins un réseau routier à péage qui est un système ouvert ou un système fermé.
  12. Dispositif embarqué [On-Board-Unit - OBU] pour un véhicule, le dispositif embarqué comprenant une interface de balise (BSS) pour la transmission de données avec une pluralité de balises disposées sur des routes, et une interface Back Office (BoSS) (interface de bureau administratif) pour la transmission de données à un Back Office central (BO), le Back Office (BO) étant destiné au traitement des données de péage,
    caractérisé en ce que
    le dispositif embarqué [On-Board-Unit - OBU] comprend en outre :
    - une unité de recherche de position prévue pour la recherche automatique d'un l'exploitant de péage actuel à travers une recherche de position par satellite du véhicule,
    - un module de configuration pour identification automatique d'une technique de communication utilisée par l'exploitant de péage saisi, notamment d'un protocole de transmission, et pour configuration automatique de l'interface de balise (BSS) en fonction de la technique de communication identifiée de l'exploitant de péage.
  13. Système de péage comprenant au moins un exploitant de péage, pour le traitement des données de péage, le système de péage comprenant :
    - une pluralité de balises (16) disposées sur des routes ;
    - au moins un dispositif embarqué [On-Board-Unit - OBU] présentant une interface de balise (BSS) pour la transmission de données avec la pluralité de balises (16), et une interface Back Office (BoSS) (interface de bureau administratif) avec un Back Office (BO),
    - le Back Office (BO) - qui présente une interface avec au moins un dispositif embarqué [On-Board-Unit - OBU] - étant prévu avec des moyens pour le calcul de la position du dispositif embarqué [On-Board-Unit - OBU] à l'aide de données pseudo-distances,
    le système de péage étant caractérisé en ce que
    le dispositif embarqué [On-Board-Unit - OBU] comprend en outre :
    - une unité de recherche de position prévue pour la recherche automatique d'un l'exploitant de péage actuel à travers une recherche de position par satellite du dispositif embarqué [On-Board-Unit - OBU];
    - un module de configuration pour identification automatique d'une technique de communication utilisée par au moins un exploitant de péage saisi, notamment d'un protocole de transmission, et pour configuration automatique de l'interface de balise (BSS) en fonction de la technique de communication identifiée d'au moins un exploitant de péage.
EP06004736A 2005-03-09 2006-03-08 Dispositif et procédé destinés à l'échange de données de péage dans des systèmes d'identification par radiofréquence Not-in-force EP1708144B1 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
DE200510010888 DE102005010888A1 (de) 2005-03-09 2005-03-09 Verfahren und Anordnung zur Positionsbestimmung
DE202005009152U DE202005009152U1 (de) 2005-03-09 2005-03-09 Anordnung zur Positionsbestimmung
DE102005030030A DE102005030030A1 (de) 2005-03-09 2005-06-27 System zur Verarbeitung von positions- und/oder mautbezogenen Daten für Fahrzeuge

Publications (3)

Publication Number Publication Date
EP1708144A2 EP1708144A2 (fr) 2006-10-04
EP1708144A3 EP1708144A3 (fr) 2007-04-25
EP1708144B1 true EP1708144B1 (fr) 2010-12-15

Family

ID=36659950

Family Applications (2)

Application Number Title Priority Date Filing Date
EP06004735A Withdrawn EP1708143A3 (fr) 2005-03-09 2006-03-08 Système destiné au traitement de données de position et/ou de péage pour des véhicules
EP06004736A Not-in-force EP1708144B1 (fr) 2005-03-09 2006-03-08 Dispositif et procédé destinés à l'échange de données de péage dans des systèmes d'identification par radiofréquence

Family Applications Before (1)

Application Number Title Priority Date Filing Date
EP06004735A Withdrawn EP1708143A3 (fr) 2005-03-09 2006-03-08 Système destiné au traitement de données de position et/ou de péage pour des véhicules

Country Status (1)

Country Link
EP (2) EP1708143A3 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130144687A1 (en) * 2011-12-05 2013-06-06 Kapsch Trafficcom Ag Method and on-board unit for signaling toll transactions in a road toll system
WO2019179678A1 (fr) * 2018-03-23 2019-09-26 Bayerische Motoren Werke Aktiengesellschaft Procédé d'exploitation d'un système de péage

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1944736A1 (fr) * 2007-01-12 2008-07-16 Brisa-Auto-Estradas de Portugal S.A. Système multiservice de paiement sans fil pour des véhicules
DE102007045479A1 (de) * 2007-09-21 2009-04-02 Deutsche Telekom Ag Verfahren zur Ermittlung streckenbezogener Straßenbenutzungsentgelte mittels einer Anordnung aus Fahrzeugendgerät und Dienstezentrale
SI2242024T1 (sl) 2009-04-14 2015-06-30 Kapsch Trafficcom Ag Postopek, komponente in sistem za tvorjenje cestninskih transakcij
EP2256694A1 (fr) 2009-05-25 2010-12-01 Kapsch TrafficCom AG Procédé et composants destinés à la production de transactions de péage
PT2624218E (pt) * 2012-02-02 2014-08-25 Kapsch Trafficcom Ag Dispositivos de controlo e métodos para um sistema de portagem rodoviária
EP2709051B1 (fr) * 2012-09-17 2017-03-22 Kapsch TrafficCom AG Procédé de traitement électronique d'une infraction routière et unité embarquée à cet effet
SI2860703T1 (sl) 2013-10-08 2016-10-28 Kapsch Trafficcom Ag Postopek preverjanja cestninskih transakcij in sestavni deli le-tega
EP2866206B2 (fr) * 2013-10-23 2021-10-27 Kapsch TrafficCom AG Unité embarquée et serveur de transaction pour un système de péage routier
NO336505B1 (no) 2013-12-20 2015-09-14 Q Free Asa Sonedeteksjon i et GNSS-system
DE102014202587A1 (de) * 2014-02-13 2015-08-13 Continental Automotive Gmbh Mauterfassungseinrichtung zum Erfassen einer Maut eines Kraftfahrzeuges
EP3132648B2 (fr) 2014-04-14 2022-06-29 Continental Teves AG & Co. OHG Procédé de traitement d'un message de véhicule à x, module de communication de véhicule à x et support de stockage
EP3174015A1 (fr) * 2015-11-27 2017-05-31 Toll Collect GmbH Reconnaissance d'erreurs dans une unité embarquée à bord d'une véhicule d'un système de péage
DE102020110659A1 (de) 2020-04-20 2021-10-21 Bayerische Motoren Werke Aktiengesellschaft Betreiben eines Fahrzeugs sowie Fahrzeug und System
EP3920149A1 (fr) * 2020-06-04 2021-12-08 Toll Collect GmbH Procédé de détermination d'un péage, appareil de véhicule et système de péage
CN113379936B (zh) * 2021-03-29 2022-07-08 李任永 一种省市级公路费用计算方法和装置

Family Cites Families (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5289183A (en) * 1992-06-19 1994-02-22 At/Comm Incorporated Traffic monitoring and management method and apparatus
DE19733579A1 (de) * 1997-08-02 1999-02-04 Kdm Sicherheitstechnik Gmbh Verfahren und Einrichtung zum Überwachen von Personen und/oder beweglichen Objekten
DE19755142B4 (de) * 1997-11-28 2004-03-18 Krönke, Matthias Verfahren und System zur Transport- und Positionsüberwachung beweglicher Objekte
DE19906529A1 (de) * 1999-01-18 2000-07-20 Volkswagen Ag System und Verfahren zur Erfassung und Übertragung von Fahrzeugpositionsdaten
IT1306768B1 (it) * 1999-01-27 2001-10-02 Marcello Federici Sistema di addebito automatico per mezzi di trasporto.
EP1200937B1 (fr) * 1999-08-04 2005-06-01 Vodafone Holding GmbH Systeme de peage pour le prelevement central de taxes dues par des vehicules utilisant un reseau routier a peage
NO310538B1 (no) * 2000-04-28 2001-07-16 Powercom Ventures As System for automatisert betaling av bompenger og parkeringsavgifter
US6484096B2 (en) * 2000-06-06 2002-11-19 Satellite Devices Limited Wireless vehicle monitoring system
AT411941B (de) * 2000-11-28 2004-07-26 Frv Electronics Vertriebs Und Verfahren zum erfassen von mindestens einem fahrzeug bzw. verkehrsteilnehmer auf öffentlichen verkehrsflächen
DE10104499A1 (de) * 2001-01-31 2002-08-14 Daimler Chrysler Ag Strassengebührenerfassungssystem
DE10155501A1 (de) * 2001-11-13 2003-05-28 Vodafone Ag Erfassungssystem für flächige Bereiche zum Erfassen von Fahrzeugen mit GPS
US6657557B1 (en) * 2002-05-08 2003-12-02 Te Hsin Hsu Information communicating apparatus for vehicles
DE10228401A1 (de) * 2002-06-25 2004-01-22 Daimlerchrysler Ag Vorrichtung zur Bestimmung von Benutzungsgebühren und Gebührenerfassungssystem
EP1400937A1 (fr) * 2002-09-12 2004-03-24 TeamSharp Space Tech Inc. Système de communication et de prévention de vol pour des motocyclettes
GB2399441A (en) * 2003-03-11 2004-09-15 Sema Uk Ltd Road use charging system using a mobile telecommunications network
US20040200899A1 (en) * 2003-04-08 2004-10-14 Bor-Shenn Jeng Automatic toll collection architecture and method combining short-range and long-range communication schemes
EP1475752A3 (fr) * 2003-05-05 2005-12-14 Vodafone Holding GmbH Système et méthode de perception électronique de droits de péage
DE20319131U1 (de) * 2003-12-10 2004-03-18 KNÜPFER, Jürgen Vorrichtung für die Überwachung von Ladegut (Ladegutüberwachung)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130144687A1 (en) * 2011-12-05 2013-06-06 Kapsch Trafficcom Ag Method and on-board unit for signaling toll transactions in a road toll system
WO2019179678A1 (fr) * 2018-03-23 2019-09-26 Bayerische Motoren Werke Aktiengesellschaft Procédé d'exploitation d'un système de péage

Also Published As

Publication number Publication date
EP1708144A2 (fr) 2006-10-04
EP1708144A3 (fr) 2007-04-25
EP1708143A3 (fr) 2007-04-25
EP1708143A2 (fr) 2006-10-04

Similar Documents

Publication Publication Date Title
EP1708144B1 (fr) Dispositif et procédé destinés à l'échange de données de péage dans des systèmes d'identification par radiofréquence
EP2920777B1 (fr) Procédé pour fournir des informations de trajet au moyen d'au moins un véhicule automobile
EP3363005B1 (fr) Procédé de détermination et de mise à disposition d'une banque de données liée à un environnement prédéfini, contenant des données d'environnement
EP2195796B1 (fr) Procédé de mise à disposition de données de marche de véhicule
EP2567371B1 (fr) Procédé pour la détermination d'une aire de stationnement dans la proximité d'un véhiclue et système d'aide à la conduite approprié
EP3482574B1 (fr) Fournir information depuis un groupe de véhicules automobiles
DE102015201420A1 (de) Parkraum-Zufahrtskontrollsystem sowie Verfahren zur Kontrolle der Zufahrt in einen Parkraum
EP1741077A1 (fr) Procede et systeme pour transmettre des informations concernant des espaces de stationnement
DE112019001611T5 (de) Fahrassistenzsystem, fahrzeuginterne Vorrichtung, Verfahren und Computerprogramm
WO2018015133A1 (fr) Procédé et dispositif de relevé de données d'une pluralité de véhicules
DE10329871A1 (de) Verfahren und System zur telemetrischen Diagnose elektronischer Einrichtungen eines Fahrzeugs
EP2690601B1 (fr) Procédé de contrôle de péage et installations de contrôle de péage ainsi que le système de péage doté des installations de contrôle de péage de ce type
DE112016000584B4 (de) Fahrzeugkommunikationseinrichtung
DE102018008730A1 (de) Verfahren und Vorrichtung zum Erheben von fahrzeugbasierten Datensätzen für vorgegebene Streckenabschnitte
DE102005031419A1 (de) Vorrichtung und Verfahren zum Datenaustausch von mautbezogenen Daten bei DSRC-Systemen
DE202006021041U1 (de) Vorrichtung und System zum Datenaustausch von mautbezogenen Daten bei DSRC-Systemen
DE102017206884B4 (de) Verfahren und System zum Erfassen eines Problems bei einem internetbasierten Infotainmentsystem für ein Kraftfahrzeug
EP3920149A1 (fr) Procédé de détermination d'un péage, appareil de véhicule et système de péage
EP3242205A1 (fr) Procede de mise a jour de la configuration d'un dispositif de vehicule, dispositif de vehicule, dispositif de traitement de donnees central et systeme de peage
EP1702199B1 (fr) Mise en service d'une application chez un client mobile
DE112012004816T5 (de) Speichernetzwerksystem
EP3038062B1 (fr) Procédé et dispositifs de véhicule pour communication DSRC
DE102019001735B3 (de) Erheben von fahrzeugbasierten, ortsbezogenen Datensätzen
DE102018008731A1 (de) Verfahren und Vorrichtung zum Erheben von fahrzeugbasierten Datensätzen für vorgegebene Streckenabschnitte
LU500620B1 (de) Eine Inhaltsverteilungsvorrichtung basierend auf einem Informationsverteilungssystem

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

AK Designated contracting states

Kind code of ref document: A2

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

AX Request for extension of the european patent

Extension state: AL BA HR MK YU

PUAL Search report despatched

Free format text: ORIGINAL CODE: 0009013

AK Designated contracting states

Kind code of ref document: A3

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

AX Request for extension of the european patent

Extension state: AL BA HR MK YU

17P Request for examination filed

Effective date: 20070626

17Q First examination report despatched

Effective date: 20070727

AKX Designation fees paid

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

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

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

Owner name: MPS SOLUTIONS GMBH

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): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

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

REF Corresponds to:

Ref document number: 502006008489

Country of ref document: DE

Date of ref document: 20110127

Kind code of ref document: P

REG Reference to a national code

Ref country code: NL

Ref legal event code: T3

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

LTIE Lt: invalidation of european patent or patent extension

Effective date: 20101215

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

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

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

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

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

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

REG Reference to a national code

Ref country code: IE

Ref legal event code: FD4D

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

Ref country code: PT

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

Effective date: 20110415

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

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

Ref country code: IE

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

Effective date: 20101215

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

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

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

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

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

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

PLAZ Examination of admissibility of opposition: despatch of communication + time limit

Free format text: ORIGINAL CODE: EPIDOSNOPE2

PLBI Opposition filed

Free format text: ORIGINAL CODE: 0009260

BERE Be: lapsed

Owner name: MPS SOLUTIONS G.M.B.H.

Effective date: 20110331

26 Opposition filed

Opponent name: TOLL COLLECT GMBH

Effective date: 20110915

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

Ref country code: MC

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

Effective date: 20110331

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: DE

Ref legal event code: R026

Ref document number: 502006008489

Country of ref document: DE

Effective date: 20110915

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

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

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

Ref country code: LI

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

Effective date: 20110331

Ref country code: CH

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

Effective date: 20110331

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

Owner name: M2C SOLUTIONS GMBH

REG Reference to a national code

Ref country code: NL

Ref legal event code: SD

Effective date: 20120213

PLBG Opposition deemed not to have been filed

Free format text: ORIGINAL CODE: 0009274

REG Reference to a national code

Ref country code: DE

Ref legal event code: R082

Ref document number: 502006008489

Country of ref document: DE

Representative=s name: STOLMAR SCHEELE & PARTNER, DE

26D Opposition deemed not to have been filed

Opponent name: TOLL COLLECT GMBH

Effective date: 20111225

REG Reference to a national code

Ref country code: DE

Ref legal event code: R081

Ref document number: 502006008489

Country of ref document: DE

Owner name: M2C SOLUTIONS GMBH, DE

Free format text: FORMER OWNER: MPS SOLUTIONS GMBH, 94560 OFFENBERG, DE

Effective date: 20120316

Ref country code: DE

Ref legal event code: R082

Ref document number: 502006008489

Country of ref document: DE

Representative=s name: SCHWARZ & BALDUS PATENTANWAELTE, DE

Effective date: 20120316

Ref country code: DE

Ref legal event code: R082

Ref document number: 502006008489

Country of ref document: DE

Representative=s name: PATENTANWAELTE SCHWARZ & BALDUS PARTNERSCHAFT , DE

Effective date: 20120316

REG Reference to a national code

Ref country code: GB

Ref legal event code: 732E

Free format text: REGISTERED BETWEEN 20120614 AND 20120620

REG Reference to a national code

Ref country code: AT

Ref legal event code: PC

Ref document number: 492008

Country of ref document: AT

Kind code of ref document: T

Owner name: M2C SOLUTIONS GMBH, DE

Effective date: 20120518

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

Ref country code: GB

Payment date: 20130321

Year of fee payment: 8

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

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

Ref country code: TR

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

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

Effective date: 20101215

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

Ref country code: NL

Payment date: 20140328

Year of fee payment: 9

REG Reference to a national code

Ref country code: DE

Ref legal event code: R082

Ref document number: 502006008489

Country of ref document: DE

Representative=s name: SCHWARZ & BALDUS PATENTANWAELTE, DE

Ref country code: DE

Ref legal event code: R082

Ref document number: 502006008489

Country of ref document: DE

Representative=s name: PATENTANWAELTE SCHWARZ & BALDUS PARTNERSCHAFT , DE

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

Effective date: 20140308

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

PLAB Opposition data, opponent's data or that of the opponent's representative modified

Free format text: ORIGINAL CODE: 0009299OPPO

R26D Opposition deemed not to have been filed (corrected)

Opponent name: TOLL COLLECT GMBH

Effective date: 20111225

REG Reference to a national code

Ref country code: NL

Ref legal event code: MM

Effective date: 20150401

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 11

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 12

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

Ref country code: NL

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

Effective date: 20150401

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 13

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

Ref country code: DE

Payment date: 20180328

Year of fee payment: 13

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

Ref country code: AT

Payment date: 20180327

Year of fee payment: 13

Ref country code: FR

Payment date: 20180321

Year of fee payment: 13

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 502006008489

Country of ref document: DE

REG Reference to a national code

Ref country code: AT

Ref legal event code: MM01

Ref document number: 492008

Country of ref document: AT

Kind code of ref document: T

Effective date: 20190308

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

Ref country code: AT

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

Effective date: 20190308

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