EP3113119B1 - Procede de suivi de vehicules soumis a peage dans un systeme de peage - Google Patents

Procede de suivi de vehicules soumis a peage dans un systeme de peage Download PDF

Info

Publication number
EP3113119B1
EP3113119B1 EP15175360.5A EP15175360A EP3113119B1 EP 3113119 B1 EP3113119 B1 EP 3113119B1 EP 15175360 A EP15175360 A EP 15175360A EP 3113119 B1 EP3113119 B1 EP 3113119B1
Authority
EP
European Patent Office
Prior art keywords
toll
vehicle
mobile display
display device
control
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
EP15175360.5A
Other languages
German (de)
English (en)
Other versions
EP3113119A1 (fr
Inventor
Matthias Heyd
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.)
Toll Collect GmbH
Original Assignee
Toll Collect GmbH
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Toll Collect GmbH filed Critical Toll Collect GmbH
Priority to EP15175360.5A priority Critical patent/EP3113119B1/fr
Publication of EP3113119A1 publication Critical patent/EP3113119A1/fr
Application granted granted Critical
Publication of EP3113119B1 publication Critical patent/EP3113119B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07BTICKET-ISSUING APPARATUS; FARE-REGISTERING APPARATUS; FRANKING APPARATUS
    • G07B15/00Arrangements or apparatus for collecting fares, tolls or entrance fees at one or more control points
    • G07B15/06Arrangements for road pricing or congestion charging of vehicles or vehicle users, e.g. automatic toll systems

Definitions

  • the present invention relates to a method for tracking vehicles subject to toll in a toll system, for example in a road toll system, and to a system for carrying out the method.
  • the toll is paid, for example, by purchasing a vignette or other usage authorization and is then valid for a specified period of time and a specified area.
  • toll traffic area In addition to these methods that provide a flat-rate authorization to use a toll traffic area, methods are also known in which the toll is collected depending on use.
  • the distance actually traveled by the toll vehicle on the toll traffic area is used as a basis for calculating the toll due - usually according to vehicle types and/or vehicle specifics such as the mass of the vehicle, the number of axles of the vehicle, the length of the vehicle, and the emission class of the vehicle and/or the presence of a trailer.
  • usage-dependent toll systems are also known in such a way that the vehicles subject to toll are recorded automatically.
  • the toll vehicle is automatically recorded when entering the toll traffic area, when leaving the toll traffic area and/or when entering the toll traffic area and its movement and/or route is evaluated in order to determine the toll due for the route actually driven to be able to raise.
  • decentralized collecting systems are known here in which a position determination device is provided in the vehicle, for example in a vehicle device or a vehicle device, which is also referred to as an “on board unit” (OBU).
  • a GNSS (Global Navigation Satellite System, GNSS for short) receiver in the vehicle records the position of the vehicle via a GNSS system and a DSRC (Dedicated Short Range Communication, DSRC for short) receiver in the vehicle can receive positions from roadside devices.
  • this position data is processed in the vehicle device to identify any toll traffic areas that may be used.
  • the toll can be collected decentrally in the vehicle device, for example by debiting a pre-paid credit.
  • the toll can be collected by the toll center, which carries out the debit or invoice.
  • the toll is collected after driving on the toll section.
  • a position determination device is provided in the vehicle or a vehicle device, which transmits the position data to a toll center and the toll recognition, the toll determination and the toll collection are carried out in the toll center.
  • a GNSS receiver in the vehicle records the position of the vehicle via a GNSS system and a DSRC receiver in the vehicle can receive positions from roadside devices.
  • Toll recognition can be carried out in the vehicle device or in the toll center. If the toll recognition is carried out outside the vehicle device, only position data is transmitted to the toll center, which carries out the toll recognition. The toll is collected after driving on the toll section.
  • Toll collection systems are also known that do not use GNSS receivers and only determine positioning and toll recognition on the road side Carry out vehicle detection devices.
  • the toll vehicle sends a corresponding identification signal to the roadside vehicle detection device.
  • the identification signals received from the roadside vehicle detection devices are transmitted to a toll center, which determines the toll on this basis and collects the toll. With this toll collection system, the toll is also collected after driving on the toll section.
  • the Toll Collect GmbH system is used to collect tolls when using motorways, with roadside control devices in the form of permanently installed control bridges spanning the road, which record the license plates of every vehicle passing by.
  • the determined license plates of the vehicles can be compared with vehicle-specific data available in a central database under vehicle license plates in order to check that the applicable toll has been collected correctly and possibly to be able to determine whether the driver of the vehicle is currently committing a toll violation, in particular if there is no vehicle-specific data, in particular toll data, under the determined license plate number of a vehicle for the relevant section of route on which the vehicle was recorded.
  • information about a route preselected for the respective license plate or information about payment methods can be stored in the central database.
  • mobile control devices can also be provided, which support further detection of the vehicles. This system can be expanded to other roads.
  • vehicle-side vehicle devices which are also referred to as OBUs (On-Board Units), have proven successful, which have a position-determining device for detecting the position of the vehicle or are coupled to a position-determining device provided in the vehicle.
  • OBUs On-Board Units
  • the vehicle devices can accordingly determine and/or record the position of the respective toll vehicle and, based on map material stored in the vehicle device, determine whether the vehicle is on a toll traffic area. If this is the case, the vehicle device determines a toll fee for the use of the determined toll traffic area and the corresponding toll data, which includes the determined fee, is transmitted to a toll center.
  • the toll due is then collected at the toll center, either by calculating the toll from the transmitted route data or by using the transmitted fee data.
  • the toll due is then billed to the respective user or deducted from an existing credit balance.
  • the user In order to enable correct toll collection, the user must initialize the vehicle device before starting the journey and, among other things, enter vehicle data, such as the total weight of the vehicle, its emission class and the current number of axles.
  • vehicle data such as the total weight of the vehicle, its emission class and the current number of axles.
  • the vehicle device determines the toll applicable for the respective journey, taking into account the position of the toll vehicle determined via the position determination device and the comparison of the position of the toll vehicle with a database in which the toll roads are stored, and transmits this toll data at the latest Fulfillment of a certain criterion, for example when leaving the toll route, to the toll center.
  • the position data determined over the course of the journey by the position determination device and recorded by the vehicle device are transmitted to the toll center continuously or when a specific criterion is met, for example when a predetermined amount of position data is reached.
  • the toll to be paid for this journey for the toll vehicle is then determined and collected centrally in the toll center based on the vehicle data and the toll traffic areas identified as being in use from the position data.
  • This method of collecting toll data in which the user of the toll vehicle only has to initialize the vehicle device and then the recording of the route, the transmission of the toll data to the toll center, and the collection of the toll after initialization are carried out without any further user input, will also be carried out called automatic procedure (AV).
  • AV automatic procedure
  • the toll is only determined after the respective toll section has been traveled and is collected by being invoiced accordingly or deducted from a deposited or pre-paid credit.
  • the vehicle device carried by the toll vehicle recognizes the corresponding position data based on the comparison Position determination device was determined, with map data stored in a database, whether, and if so, which toll section of the route is being traveled.
  • Such a toll route section is then stored in a storage device of the vehicle device.
  • toll route sections are stored section by section in the storage device in the vehicle device and then transmitted to the toll center as toll data when a predetermined criterion occurs, for example after a predetermined number of stored route sections has been exceeded.
  • the toll determination takes place either in the toll center or in the vehicle device. In the latter case, the toll to be collected is then transmitted to the toll center as toll data.
  • the authorization to use the toll route section being traveled is acquired step by step after each individual toll route section has been traveled, with the toll being collected via the toll center after leaving the toll route section and transmitting the relevant data to the toll center becomes.
  • the respective user can use one of the approximately 3,600 toll booth terminals, which are typically set up at truck stops, rest areas or gas stations.
  • a web service on the Internet can also be used in the manual process (MV).
  • the user acquires a usage authorization for the respective toll route section before driving on the toll route section or a toll route, which consists of one or more toll route sections.
  • the user indicates the planned entrance to and the planned exit from the toll traffic area at the toll station terminal or in the web service before driving on the route, which then defines the one or more toll sections of the route.
  • the user can also enter via positions in his route, which are taken into account when determining the route to be traveled and which are used as a basis for calculating the toll fee due.
  • the user of the manual procedure (MV) applies the toll before actually driving on the toll route sections route and pay the corresponding toll fee.
  • the toll fee can either be paid directly at the toll station terminal or online, or it can be provided to registered users via the toll center in a monthly collective bill or deducted from an existing credit balance.
  • Booking a route using the manual method results in a fixed route that the user cannot leave without potentially being considered a toll evader.
  • a change to the route may become necessary, for example, if a section of the booked route is closed or if a traffic jam occurs that needs to be avoided. It can also happen that a user wants to go to additional stations along the way. If the user wants to change his route after starting the journey booked using the manual process, he must do so at a stationary toll terminal so that the route he actually traveled remains traceable. The user then has to partially cancel the booked route and then book the new desired route.
  • the position determination device In the vehicle devices or vehicle devices, highly accurate position determination is possible by means of the position determination device, which has a GNSS receiver which receives specific signals from satellites of a global navigation satellite system which are stationed in Earth orbit and which emit corresponding position signals.
  • the position determination device uses these signals in a known manner to calculate its own position.
  • GNSS systems include the US GPS system, the Russian GLONASS, the European Galileo and the Chinese Compass system, although the latter are still under construction.
  • Either a positioning device that is already provided in the toll vehicle and which transfers its data to an OBU can be used as the positioning device, or the OBU itself can have a positioning device.
  • position indicators speedometer, odometer
  • direction indicators such as a gyroscope or an electronic compass of the toll vehicle
  • position indicators can be connected to the position determination device in order to enable even more precise position determination through dead reckoning. This can be particularly important if no GNSS data is available due to coverage, for example in a tunnel, and an accurate position determination is still desired.
  • the information is transmitted to the toll center via a communication module present in the vehicle device, which uses a known mobile radio standard and communicates the data to the toll center, for example via the GSM standard.
  • a communication module present in the vehicle device which uses a known mobile radio standard and communicates the data to the toll center, for example via the GSM standard.
  • Two-way communication is generally not provided, but only the toll-relevant data determined by the vehicle device is transmitted to the toll center when the vehicle device has completed collecting the data.
  • usage-based toll systems rely on recording the route of the respective toll vehicles, at least in the area that is relevant for the use of the toll road.
  • the vehicle positions in the toll collection system operated by the German toll operator Toll Collect GmbH are regularly recorded in the area of the entrance to the respective toll traffic area and in the area of the exit from this traffic area.
  • Toll data is understood here to mean data of toll traffic areas and/or toll fees assigned to a user, which are determined through a toll identification and/or toll determination.
  • Toll-relevant data is all data that is included in determining the toll fee, such as the identifier and/or the length of the toll traffic area as well as vehicle data such as weight, number of axles and emission class.
  • a basic fee or fee rate is usually linked to at least one toll-relevant data set, which, in conjunction with the other toll-relevant data, allows the total fee for toll collection to be determined.
  • Toll recognition is here technically understood to mean the process of linking a used, toll traffic area, identified based on the recorded vehicle position(s), with the user. In other words, this means linking the user for the first time to a used toll traffic area.
  • Toll determination is technically understood here as the process of determining a toll fee from the toll traffic area used or to be used in the future, if necessary taking into account toll-relevant vehicle data and time information.
  • Toll collection is here technically understood to mean the process of collecting the specific toll fee from the user whose vehicle has demonstrably used the toll traffic area or will use it in the future, for example by taking cash such as at a toll station terminal, by central debiting from an account or through decentralized deduction from a pre-paid credit on a chip card arranged in a vehicle device.
  • a toll traffic area is understood to mean traffic areas for which a toll fee is due for use.
  • the amount of the toll fee can be determined, for example, according to the route traveled on the toll traffic area, for example measured in meters, according to the number of toll route sections used or as a flat rate or according to the time for using a specific toll route network, for example in the case of a city toll.
  • a toll violation is understood here to mean that a vehicle subject to toll is using or has used a toll traffic area and the toll fee actually due for use cannot be collected. This may be due to the fact that the vehicle subject to toll is not accessible to automatic recording because the technical requirements for carrying out an automatic procedure are missing - for example, an on-board unit suitable for the respective toll system is not available, is not switched on or is defective. However, it may also be the case that the section of route currently being traveled has not been booked for the respective vehicle in the manual process.
  • a toll violation can also occur if the toll collection fails because the toll fee to be paid cannot be collected - for example because an account, credit card or credit account is not funded.
  • it can also happen that a toll fee is not paid out by the foreign operator of the on board unit to the domestic operator of the toll system and a toll violation only becomes apparent at a point in time after the actual passage of the toll section.
  • inspectors are provided to inspect toll vehicles and to punish toll violations If a potential toll violation has been identified, they should be removed from traffic and punished accordingly if the suspicion of a toll violation is confirmed.
  • the toll violation notices are determined either by a central data processing device or in the roadside control device, for example in the data processing device provided in the roadside control device, by appropriate analysis of the vehicle data determined by the roadside control device.
  • the procedures used to determine whether a vehicle subject to toll is one in which a toll violation is suspected are known in principle.
  • control devices for example control bridges arranged on the road side, by means of which vehicle license plates, vehicle properties and the status of vehicle devices accommodated in the respective toll vehicle are recorded, the corresponding ones Control data is transmitted to inspectors.
  • the inspectors are usually trained by the crews of inspection vehicles that can be used on a mobile basis and are stationed near the respective roadside inspection facility.
  • the inspection vehicles are intended to pursue toll vehicles that are believed to have committed a toll violation.
  • the check of the actual existence of a toll violation is then carried out by the crew of the inspection vehicle. If, when checking the suspicion of a toll violation, the inspector comes to the conclusion that a toll violation has actually occurred, the driver or owner of the vehicle subject to the toll will be punished.
  • the respective controller or the crew of a control vehicle can evaluate the data received from the respective roadside control device and then check toll vehicles where a toll violation is suspected and, for example, remove them in order to contact the driver or owner of the toll vehicle after a toll violation has been detected to be punished.
  • the inspectors or the crews of the inspection vehicles often travel with the inspection vehicles in the section of the toll traffic area that they control. It can therefore happen that the data from the road-side control device assigned to the respective inspector is sent to the inspector or made available to him, even though the inspector is at a significant distance from the road-side control device assigned to him and is possibly even closer to another road-side control device. This means that decisions as to whether a specific toll vehicle for which a toll violation is suspected should be removed cannot be made in a timely manner or, in this way, efficient and safe control and/or removal of the toll vehicle is made more difficult.
  • the EP 2 624 231 B1 Devices and methods for control in a road toll system are known, in which recording vehicles and control vehicles are provided.
  • the control vehicles have reading devices for reading license plates and are connected to a crime server.
  • the recording vehicles are equipped with a DSRC transceiver for reading out the toll parameters.
  • This provides a first fleet of recording vehicles (“hunters”) and a second fleet of control vehicles (“collectors”), which communicate with each other via a common crime server.
  • From the US 2006/0056658 A1 discloses a method for reading a vehicle license plate located on a vehicle, which includes determining whether a license plate image is required, wherein the license plate image is automatically processed in response to the determination that a license plate image is required, at least one verified image is provided, and determining whether manual reading of the license plate image is necessary by matching the license plate image with the at least one verified image .
  • a method for tracking toll vehicles in a road toll system comprising the steps of providing at least two fixed, roadside control devices for detecting at least one license plate of a toll vehicle, detecting a license plate of a toll vehicle by a first of the control devices, and transmitting the license plate to a central data processing device, determining the current vehicle position of the toll vehicle based on the position of the first control device, providing at least two mobile display devices for displaying license plates and current vehicle positions of identified toll vehicles, and transmitting the current position of each mobile display device to the central one Data processing device.
  • the proposed method further includes determining exactly one closest mobile display device, which is at a closer distance from the current vehicle position than all other mobile display devices, based on the current vehicle position of the toll vehicle and the current position of all display devices in the central data processing device, transmitting the license plate and the current vehicle position to the one nearest mobile display device through the central data processing device, and displaying the license plate and the current vehicle position of the toll vehicle on the at least one nearest mobile display device.
  • determining a nearest mobile display device in the central data processing device which is at a shorter distance from the current vehicle position than at least one further mobile display device, it can be achieved that the data recorded by the roadside control devices is sent to that mobile display device or the inspection vehicle that is closer to the toll vehicle to be inspected will be sent other mobile display devices. This can ensure that the corresponding control data is sent to the inspector or the crew of a control vehicle who are actually positioned in the immediate vicinity or closest to the toll vehicle that is then to be checked.
  • a crew of a control vehicle that moves on the toll traffic area together with the toll vehicles can always be provided with the control data that relates to the toll vehicles located in the vicinity of the control vehicle.
  • the controller of the control vehicle " sees " the toll vehicles in his area, and in particular the toll vehicles in his area, for which diversion decisions must be made or for which there is a suspicion of a toll violation.
  • a clear assignment to a single roadside control device, as was conventionally practiced, is therefore no longer necessary and no longer desired.
  • control data is dynamically transmitted to the inspector's mobile display device in such a way that the data of the toll vehicles that are in the vicinity of the control vehicle and for which there is a suspicion of a toll violation, are transmitted to the nearest inspection vehicle, regardless of where the inspection vehicle is currently located.
  • control vehicles that are equipped with the mobile display devices to be able to constantly move in flowing traffic, to be able to move away from the roadside control devices at will, to be able to move towards roadside control devices and/or to change their location between different roadside control devices can change.
  • the respective mobile display device can be sent data from different roadside control devices, regardless of where the mobile display device is located with respect to the position of the respective roadside control devices.
  • a toll violation is linked to the license plate to form a control data record and the control data record is transmitted together with the current vehicle position to at least one nearest mobile display device.
  • the data that proves the suspicion of violation even more precisely and, in particular, to make it possible, in particular during a later check, to also name the respective individual control device or the respective sensor that detects the toll vehicle.
  • the position of the respective recorded toll vehicle can be equated with the position of the first control device that detects the toll vehicle.
  • the current vehicle position of the toll vehicle is particularly preferred, starting from the position of the roadside control device that detected the vehicle, taking into account the time of detection and a calculated, assumed or measured speed, in order in this way to be able to close the current position of the recorded toll vehicle or a current section of the route in which the toll vehicle is suspected.
  • the current probable position of the detected vehicle is preferably determined from the known position and direction data and a speed estimate. This current position is then set in relation to the current position of the mobile display devices and the data record of the toll vehicle is accordingly transmitted to the mobile display device which is closest or closer to the determined vehicle than the other mobile display devices.
  • a toll violation is linked to the license plate to form a control data record, and the control data record together with the current vehicle position is transmitted to at least one nearest mobile display device.
  • the mobile display device In order to further increase efficiency, the mobile display device must be determined which of all mobile display devices is closest to the position, in particular the current position, of the toll vehicle. In this way, the travel times can be reduced even further and a higher utilization of the crews of the control vehicles can be achieved.
  • This process of transmitting the data of a toll vehicle to the nearest mobile display device can either be carried out once, or in a particularly preferred embodiment, the distance between the current position of the Toll vehicle and the mobile display devices are checked constantly, cyclically or triggered by an external event and the license plate of the toll vehicle is assigned to the mobile display device which is closest to the current position of the toll vehicle.
  • Whether a mobile display device is closer than other mobile display devices to the toll vehicle to be checked can be determined, for example, via the absolute distance, the distance along a path provided on the traffic area from the respective mobile display device to the toll vehicle to be checked, or based on the estimated Time until reaching the toll vehicle to be checked can be determined based on the position (and direction of movement) of the mobile display device.
  • the possible route between the respective mobile display devices and the toll vehicle to be checked is preferably determined, for example using a navigation system or a digital road map, and is used as the basis for the calculation.
  • the data processing device precisely determines a nearest mobile display device whose position is at a closer distance to the current vehicle position than all other mobile display devices. This means that a toll vehicle to be checked is only communicated to a single mobile display device, so that the inspectors only receive an efficient number of data sets and can make diversion decisions quickly.
  • a fixed number of nearest mobile display devices can also be determined, to which the data is then transmitted to the toll vehicle to be checked, in order on the one hand to reduce data traffic, but on the other hand to achieve the highest possible probability of control.
  • the central data processing device checks continuously, cyclically or when a predetermined condition is present, whether the current position of one of the mobile display devices is still at a smaller distance from the current vehicle position than the other mobile display devices.
  • the mobile one can still be used Display device of the number of mobile display devices is excluded from the group and exchanged for another mobile display device which is further away from the current vehicle position at a later point in time than the other mobile display device which was initially not in the group of the number of at an earlier point in time mobile display devices was included. This means that even when using a group with a fixed number of mobile display devices, it can be achieved that only those mobile display devices that are actually in the vicinity of the current vehicle position are supplied with data from the toll vehicle to be checked.
  • At least one mobile display device is included in a control vehicle for tracking detected toll vehicles, is carried in it or is provided by it.
  • the mobile display device can also be implemented by a mobile device such as a mobile computer, tablet computer or smartphone.
  • a tracking case request is generated and displayed on at least one nearest mobile display device, with interaction means being provided in the mobile display device, by means of which a tracking case request can be accepted or rejected by a user input, the acceptance or rejection is transmitted from the respective display device to the central data processing device after the user input.
  • the interaction means can be provided, for example, in the form of a button or switch on the mobile display device, which is intended to accept or reject a tracking case request.
  • the interaction means can also be provided in the form of soft buttons or other interaction fields on a display of the mobile display device.
  • a tracking case request means that the inspector is asked whether he wants to take over the tracking (and then accordingly checking, expelling and, if necessary, punishing) a toll vehicle that is to be checked and for which a toll violation is suspected. In this way, the prosecution of toll violations can be carried out efficiently and it is possible to avoid multiple inspectors pursuing a single toll vehicle.
  • the tracking case request is transmitted to at least two nearest display devices and, upon acceptance of the tracking case request by a first closest mobile display device, a cancellation message is sent from the central data processing device to all other closest mobile display devices in order to cancel the tracking case request in these display devices.
  • a cancellation message is sent from the central data processing device to all other closest mobile display devices in order to cancel the tracking case request in these display devices.
  • the tracking case request is only transmitted to a single first nearest display device and if there is no acceptance or rejection by the interaction means of the display device within a predetermined period of time after transmission of the tracking case request to the nearest mobile display device, the tracking case request is sent to a further or all other closest display devices is transmitted and a cancellation message is sent to the first nearest display device to cancel the tracking case request in the first nearest display device.
  • this can initially reduce data traffic and at the same time ensure efficient utilization of the inspectors, since a tracking request is initially only displayed on a mobile display device and the other inspectors are not initially bothered.
  • a rejection of the tracking case request is also automatically generated by a nearest mobile display device if a tracking case request that was accepted before this tracking case request is still marked as active. This avoids a tracking case request being sent to a mobile display device whose controllers are already dealing with another tracking case.
  • control device In addition to at least one license plate of the toll vehicle, the control device preferably also records the direction of travel and/or the speed and/or the number of axles and/or the emission class and/or the vehicle weight of the toll vehicle and/or the status of a vehicle device and/or a Image of the toll vehicle and/or an assessment of the violation security of the control device and the determined data are included in the control data set.
  • the central data processing device transmits the control data set and the current vehicle position to at least two nearest display devices and at the same time transmits communication data from the other of the at least two nearest display devices to the display device in order to ensure communication between these display devices in relation to the respective toll vehicle detected to support.
  • the current vehicle position and the current position of the nearest mobile display device are preferably displayed on a map or a map section in the nearest mobile display device, the map or the map section being generated in the central data processing device or in the nearest mobile display device.
  • This allows the inspector or the crew of a control vehicle to view their own position, which is predetermined by the position of their mobile display device, as well as the current position of the toll vehicle to be checked in a familiar map display and in this way plan the necessary tracking operation.
  • the current vehicle positions of additional or all vehicles subject to toll can also be displayed on a map or a map section in the nearest mobile display device for which a toll violation is suspected. This gives the inspector or the crew of the nearest inspection vehicle an overview of which other vehicles suspected of toll violations are also located in their area and can potentially be tracked additionally.
  • the current vehicle position is preferably displayed together with the control data set in the nearest mobile display device, in particular the control data set is displayed at the location of the current vehicle position on a map or a map section in the nearest mobile display device.
  • control data set without the current vehicle position on a map or a map section in the nearest mobile display device, with the control data set preferably being displayed at the location of the current vehicle position on a map or a map section in the nearest mobile display device.
  • the position of at least one further nearest mobile display device is transmitted by the central data processing device to the at least one nearest mobile display device and displayed on the map or the map section of this nearest mobile display device.
  • the individual controller can take on tracking orders based on the knowledge of the other controllers in the area and can therefore plan the tracking cases accordingly.
  • control data and the current vehicle position are provided with a time stamp and discarded after a predetermined period of time based on the time stamp. This can ensure that tracking requests or data from potential toll violations are removed from the mobile display device when it becomes unlikely that they can still be processed by the inspector carrying the mobile display device. In this way, efficiency can also be significantly increased.
  • FIG. 1 A system for carrying out a method for tracking toll vehicles is shown schematically.
  • a toll traffic area 100 is provided, on which toll vehicles 102 move.
  • the license plates 104 of the toll vehicles 102 are checked using roadside control devices.
  • a first roadside control device 202 is provided, which monitors a first section of the toll traffic area 100.
  • the road-side control device 202 is arranged in a stationary manner and is shown here in the form of a control bridge, which extends over the toll traffic area 100 and which enables the toll vehicles 102 moving on the toll traffic area 100 to be recorded.
  • cameras or other optical reading devices are installed in the control device 202, by means of which the license plates 104 of the registration plates of the respective toll motor vehicles can be read.
  • cameras and/or laser distance sensors can also be used to determine further detailed information about the toll vehicles 102, for example whether a truck is carrying a trailer or not, the size or volume of the toll vehicle 102 and, for example, the number of axles of the toll vehicle 102.
  • Other detection devices can also be provided in the roadside control device 202.
  • receiving and transmitting devices can also be provided in the road-side control device 202, by means of which specific vehicle data, which are emitted by the toll vehicle 102, can be received or data to be transmitted can be output to a vehicle unit located, for example, in the toll vehicle 102.
  • a second roadside control device 204 is provided, which is also designed to be stationary and which can be constructed identically to the first roadside control device 202 or just similarly.
  • the second roadside control device 204 is also shown in the exemplary embodiment shown as a toll bridge spanning the toll road 100, by means of which details of the toll vehicles and in particular license plates 104 and other detailed information of the toll vehicle 102 can be recorded.
  • the data recorded by the roadside control devices 202, 204 and in particular the license plate data are transmitted to a central data processing device 300.
  • the central data processing device 300 which is, for example, at the operator's location of the toll system, or can also be designed at another location, data center or as a distributed central data processing device with several interconnected processors or servers or as a cloud service, the data determined by the individual roadside control devices 202, 204 Vehicle-relevant data and in particular the license plates 104 of these toll vehicles 102 are received and processed.
  • the central data processing device 300 or in the control device 202 which has recorded the license plate 104 of the toll vehicle 102, it is determined whether a toll violation has occurred. Methods known per se can be used to determine whether a toll vehicle 102 is using a toll traffic area 100, but the authorization required for use is missing.
  • the authorization may be missing if, for example, the toll fee actually due cannot be collected. This could be due to the fact that the toll vehicle 102 is not accessible to automatic detection because the technical requirements for carrying out an automatic procedure are missing - for example, an on-board unit suitable for the respective toll system is not available, is not switched on or is defective. However, it may also be the case that the section of route currently being traveled has not been booked for the respective vehicle 102 in the manual process. A toll violation can also occur if the correct parameters have not been registered for the toll vehicle 102 - for example, the toll vehicle 102 is traveling with a trailer but is registered without a trailer.
  • a toll violation notice is generated and linked to the license plate 104 to form a control data record.
  • the current vehicle position of the toll vehicle 102 can be determined based on the position of the first control device 202, by means of which the toll vehicle 102 was detected, or can be received by the first control device 202.
  • a hypothetical current position of the toll vehicle 102 can also be continuously updated in the central data processing device 300 based on an assumed speed of the toll vehicle on the basis of a digital road map that shows the time and location of the detection of the toll vehicle License plate 104 of the toll vehicle 102 are known by the first roadside control device 202, and the direction of travel of the toll vehicle 102 can also be determined from the data transmitted by the control device 202.
  • the direction of travel can be determined, for example, by knowing the sensor detecting the toll vehicle 102, the sensor then being assigned to a specific roadway. In this way, a clear assignment to the direction of travel can be achieved, particularly when collecting data on motorways.
  • a current position of the toll vehicle 102 is then calculated at a later time based on the time of detection and the direction of travel, taking the speed of the toll vehicle 102 as a basis.
  • the speed of the toll vehicle can either also be measured by the roadside control device 102, or can be determined from the average speeds known in the route section downstream of the roadside control device 202 or based on a general estimate of the speed of the toll vehicle 102.
  • mobile display devices 402, 404 are also provided, which are each provided in control vehicles that are intended for checking or monitoring the toll vehicles 102. For example, if there is a suspicion of a toll violation, the control vehicles or their crews should check the toll vehicle 102, possibly divert it, confront the driver with the suspicion of a toll violation, check his registration documents and/or the on-board unit carried in the vehicle 102 and if the suspicion has been confirmed, the driver or the owner of the toll vehicle 102 is suspected.
  • the mobile display devices 402, 404 are intended to accept and display the data determined by the central data processing device 300, in particular license plates of toll vehicles 102 for which a toll violation is suspected.
  • the central data processing device 300 is preferably connected to the mobile display devices 402, 404 via mobile radio, as indicated here schematically by the antenna 302.
  • the mobile display devices 402, 404 receive the accordingly Data from the central data processing device 300 and display this data on its display.
  • the inspectors for example the crew of the control vehicles that carry the mobile display devices 402, 404, can in this way recognize whether a toll violation is suspected for a vehicle subject to toll and can accordingly start tracking this vehicle and check accordingly.
  • the mobile display devices 402, 404 in turn transmit their current position to the central data processing device 300.
  • the mobile display devices 402, 404 can, for example, carry out a location by evaluating the respective radio cells, via a satellite-based position analysis, for example via a GPS position determination or others familiar way.
  • the position data is then transmitted from each mobile display device 402, 404 to the central data processing device 300.
  • the central data processing device 300 therefore contains the current or cyclically updated position data of the mobile display devices 402, 404, preferably from all mobile display devices 402, 404 located in the toll system or the mobile display devices 402, 402 located in a specific route section or route area .
  • the mobile display device 402 that is closest to the toll vehicle 102 or to the determined current position of the toll vehicle 102 is then determined in the central data processing device 300.
  • a distance vector or a train of several distance vectors along a path between the detected toll vehicle 102 and the current positions of the mobile display devices 402, 404 is determined in the central data processing device 300 and based on the amount of the distance vector or the sum of the amounts of the distance vectors of the train several distance vectors determine the mobile display device 402 closest to the detected toll vehicle 102.
  • the nearest mobile display device 402 When determining the nearest mobile display device 402, it is preferably further taken into account whether the mobile display device 402 and thus also the control vehicle and whose crew is in the direction of travel of the toll vehicle 102. If this is not the case, the route or time to reach the toll vehicle 102 must be extended by the route to a possible turning point for the control vehicle.
  • the estimated travel time between the mobile display device 402, 404 and the toll vehicle 102 can also be estimated and then the closest mobile display device 402, which corresponds to the toll vehicle 102 the fastest can reach, selected in order to then transmit the corresponding data to this mobile display device 402.
  • the nearest mobile display device 402 which is carried by the respective control vehicle or the crew of the control vehicle, is used to control the respective determined toll vehicle 102, which is closest to it.
  • an assignment of the mobile display device 402, 404 to a single stationary roadside control device 202, 204 that precedes the occurrence of a control case can be avoided.
  • the toll vehicle 102 or the toll vehicles 102 can be displayed on the mobile display device 402, 404 in order to provide a short Travel time or a short time to reach the toll vehicle, for which there is, for example, a toll violation notice.
  • the control vehicles, which carry the mobile display devices 402, 404 can also "swim along" in traffic and fixed stationing in the vicinity of fixed roadside control devices 202, 204 is not necessary.
  • a control vehicle or the crew of the control vehicle can start tracking another toll vehicle that is in its vicinity immediately after completing an inspection, without the specific starting position of the control vehicle being important for this.
  • the control vehicle which carries the mobile display devices 402, 404, can always be ready for use and in this way also increase efficiency, since the crew of the control vehicle can be used again more quickly in this way, since the times to reach the respective toll station are reduced vehicle 102 can be reduced because z.
  • the central data processing device 300 dynamically designs the assignment of toll vehicles 102 to be tracked based on the knowledge of the current position of the mobile display devices 402, 404. In other words, if a control vehicle or a mobile display device 402 moves away from the toll vehicle 102 to be checked and correspondingly another mobile display device 404 is closer to the also moving toll vehicle 102 after a certain time, the data can then be sent to this closer mobile display device 404 sends, and preferably away from the previously addressed mobile display device 402.
  • a vehicle to be tracked can preferably be selected on the mobile display device 402, 404 and it can be confirmed that this vehicle will be tracked and checked. If the mobile display device 402, 404 is then switched to a tracking mode, further tracking requests sent by the central data processing device 300 can be forwarded to a further mobile display device 404, which does not yet have an active tracking display and which is then also in the is close to the vehicle to be tracked.
  • the mobile display device 402, 404 can initially be excluded from determining the nearest mobile display device until the corresponding tracking order has been processed.
  • An exemplary central data processing device 300 of the toll system 200 for carrying out the method is shown as a block diagram in Figure 2 shown.
  • instructions for example in the form of software code sections, are executed so that the Data processing device 300 is set up to carry out one or more of the method steps and functions described herein.
  • the central data processing device 300 can only include a single computer. However, it can also be a distributed system. According to one embodiment, the central data processing device 300 is a single, preferably physically separate, computer. According to another embodiment, this is a distributed system, that is, several independent computers that are connected and interact with one another in such a way that they appear to a user as a single, coherent system. In the latter case, each of the computers would have at least one processor with internal memory. The several computers in the computing device then work autonomously but functionally coordinated with one another.
  • the exemplary central data processing device 300 includes a central processor 220 (e.g., a CPU, a GPU, or both) with an internal memory, a central main memory 222 and a central static memory 224, which are communicatively coupled to one another via a bus 226.
  • the central data processing device 300 can also be communicatively coupled to a user interface.
  • This user interface may include a display unit 228 (e.g., a flat screen or similar) and a first input unit 230 (e.g., a touch screen, input keys, a scroll wheel, a joystick, a touch pad, a mouse, or a voice recognition system) and a second input unit 232 (for example, a touch screen, input keys, a scroll wheel, a joystick, a touch pad, a mouse, or a voice recognition system).
  • the user interface may include the display unit 228 and the input unit(s) in an integrated device, such as a touch screen.
  • the central data processing device 300 also includes a central storage device 234, a signal generating device 236 and a central communication device 238, which are communicatively connected to one another via the bus 226.
  • the central storage device 234 includes a machine-readable medium 240 on which are stored software code sections and data (e.g. instructions 242) required for the methods and functions of the computing device described herein.
  • the instructions 242 can also, at least partially, be stored in the main memory 222 and/or in the internal memory of the Processor 220 may be loaded, with main memory 222 and the internal memory of processor 220 also being machine-readable media.
  • instructions 242 can also be transmitted or received via a network 244 by means of the central communication device 238, using one of the numerous known transmission protocols (for example TCP/IP, HTTP).
  • machine-readable medium 240 (which is preferably non-transitory) is a single medium in an exemplary embodiment, the term "mach-readable medium " includes both a single medium and multiple media (e.g., a central or distributed database and any caches associated therewith (" Cache ”) and servers) which store the instructions 242 in the form of software code sections.
  • the term “mach-readable medium ” also includes any medium capable of storing, encoding or carrying instructions 242. This can be solid-state memory, optical memory or magnetic memory.
  • Exemplary embodiments of the central data processing device 300 may be implemented in digital circuits or in computer hardware, firmware, software, or combinations thereof.
  • the positions of the mobile display devices 402, 404 can be processed and related to the control data sets and vehicle positions in order to then be able to determine the nearest mobile display device 402, 404 and then transmit the license plate 104 or the control data set to it.
  • central data processing device 300 which can be arranged, for example, at the location of the operator of the toll system, or at another location, data center or as a distributed central data processing device with several interconnected processors or servers or as a cloud service , will continue to be those of the individual street-side Vehicle-relevant data determined by control devices 202, 204 and in particular the license plates 104 of these toll vehicles 102 are received and processed.
  • the central data processing device 300 or in the control device 202 which has recorded the license plate 104 of the toll vehicle 102, it is determined whether a toll violation has occurred.
  • Known methods can be used to determine whether a toll vehicle 102 is using a toll traffic area 100 and the authorization required for use is missing. The authorization may be missing if, for example, the toll fee actually due cannot be collected.
  • toll vehicle 102 is not accessible to automatic detection because the technical requirements for carrying out an automatic procedure are missing - for example, an on-board unit suitable for the respective toll system is not available, is not switched on or is defective. However, it may also be the case that the section of route currently being traveled has not been booked for the respective vehicle 102 in the manual process.
  • a toll violation can also occur if the correct parameters have not been registered for the toll vehicle 102 - for example, the toll vehicle 102 is traveling with a trailer but is registered without a trailer.
  • a toll violation notice is generated and linked to the license plate 104 to form a control data record.

Landscapes

  • 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 (8)

  1. Procédé de suivi de véhicules soumis à péage (102) dans un système de péage routier, comprenant les étapes consistant à :
    - fournir au moins deux appareils de contrôle (202, 204) fixes, côté route pour la détection au moins d'une plaque d'immatriculation (104) d'un véhicule (102) soumis à péage,
    - détecter une plaque d'immatriculation (104) d'un véhicule soumis à péage (102) par un premier des appareils de contrôle (202),
    - transmettre la plaque d'immatriculation (104) à un appareil de traitement de données (300) central,
    - déterminer la position de véhicule actuelle du véhicule soumis à péage (102) sur la base de la position du premier appareil de contrôle (202),
    - fournir au moins deux dispositifs d'affichage (402, 404) mobiles pour l'affichage de plaques d'immatriculation (104) et de positions de véhicule actuelles de véhicules (102) soumis à péage déterminés,
    - transmettre la position actuelle de chacun des dispositifs d'affichage (402, 404) mobiles à l'appareil de traitement de données (300) central,
    - déterminer dans l'appareil de traitement de données (300) central précisément d'un dispositif d'affichage (402) mobile le plus proche qui se trouve à une distance plus faible de la position de véhicule actuelle que tous les autres dispositifs d'affichage (404) mobiles, sur la base de la position de véhicule actuelle du véhicule (102) soumis à péage et des positions actuelles de tous les dispositifs d'affichage (402, 404) mobiles,
    - transmettre la plaque d'immatriculation (104) et de la position de véhicule actuelle au précisément un dispositif d'affichage (402) mobile le plus proche par l'appareil de traitement de données (300) central,
    - représenter la plaque d'immatriculation (104) et la position de véhicule actuelle du véhicule (102) soumis à péage sur le précisément un dispositif d'affichage (402) mobile le plus proche.
  2. Procédé selon la revendication 1, caractérisé en ce que chaque appareil de contrôle (202, 204) présente un identifiant individuel qui est indicatif de la position de l'appareil de contrôle (202, 204) ou comporte un tel, et en complément de, de préférence conjointement avec, la plaque d'immatriculation (104), l'identifiant du premier appareil de contrôle (202) est transmis à l'appareil de traitement de données (300) central.
  3. Procédé selon la revendication 1 ou 2, caractérisé en ce que la position de véhicule actuelle du véhicule (102) soumis à péage correspond à la position du premier appareil de contrôle (402).
  4. Procédé selon la revendication 1 ou 2, caractérisé en ce que la position de véhicule actuelle du véhicule (102) soumis à péage est déterminée à partir de la position du premier appareil de contrôle (202), d'un moment de détection de la détection de la plaque d'immatriculation (104) qui est transmise de préférence aussi à l'appareil de traitement de données (300) central, ainsi que d'une vitesse calculée, acceptée ou mesurée du véhicule (104) soumis à péage, de préférence dans l'appareil de traitement de données (300) central, dans le dispositif d'affichage (402) mobile et/ou dans l'appareil de contrôle (202).
  5. Procédé selon l'une des revendications précédentes, caractérisé en ce que dans l'appareil de traitement de données (300) central ou dans l'appareil de contrôle (202) qui a détecté la plaque d'immatriculation (104) de ce véhicule (102) soumis à péage, une infraction au péage est reliée à la plaque d'immatriculation (104) pour former un jeu de données de contrôle et le jeu de données de contrôle est transmis conjointement avec la position de véhicule actuelle au précisément un dispositif d'affichage (402) mobile le plus proche.
  6. Procédé selon l'une des revendications précédentes, caractérisé en ce qu'au moins un dispositif d'affichage (402, 404) mobile est compris par un véhicule de contrôle pour le suivi de véhicules (202, 204) soumis à péage détectés, est entraîné dans celui-ci ou est fourni par celui-ci et/ou le dispositif d'affichage (402, 404) mobile est compris par un appareil mobile, de préférence ordinateur portable, tablette-ordinateur ou smartphone.
  7. Procédé selon la revendication 5, caractérisé en ce qu'avec la transmission du jeu de données de contrôle, une demande de cas de suivi est générée et est affichée sur le précisément un dispositif d'affichage (402, 404) mobile le plus proche, dans lequel des moyens d'interaction sont prévus dans le dispositif d'affichage (402, 404) mobile, au moyen duquel par une entrée utilisateur une demande de cas de suivi peut être acceptée ou refusée, dans lequel l'acceptation ou le refus est transmis après l'entrée utilisateur par le précisément un dispositif d'affichage (402, 404) mobile au dispositif de traitement de données (300) central.
  8. Procédé selon la revendication 7, caractérisé en ce qu'un refus de la demande de cas de suivi est généré automatiquement par le précisément un dispositif d'affichage (402) mobile le plus proche lorsqu'une demande de cas de suivi acceptée avant cette demande de cas de suivi est encore marquée comme active.
EP15175360.5A 2015-07-03 2015-07-03 Procede de suivi de vehicules soumis a peage dans un systeme de peage Active EP3113119B1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP15175360.5A EP3113119B1 (fr) 2015-07-03 2015-07-03 Procede de suivi de vehicules soumis a peage dans un systeme de peage

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
EP15175360.5A EP3113119B1 (fr) 2015-07-03 2015-07-03 Procede de suivi de vehicules soumis a peage dans un systeme de peage

Publications (2)

Publication Number Publication Date
EP3113119A1 EP3113119A1 (fr) 2017-01-04
EP3113119B1 true EP3113119B1 (fr) 2023-11-15

Family

ID=53514063

Family Applications (1)

Application Number Title Priority Date Filing Date
EP15175360.5A Active EP3113119B1 (fr) 2015-07-03 2015-07-03 Procede de suivi de vehicules soumis a peage dans un systeme de peage

Country Status (1)

Country Link
EP (1) EP3113119B1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111882686B (zh) * 2020-07-28 2022-08-16 广州珠江黄埔大桥建设有限公司 一种基于etc门架系统的漏缴费车的稽查方法、系统及设备

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5945919A (en) * 1996-05-30 1999-08-31 Trimble Navigation Limited Dispatcher free vehicle allocation system
US6642844B2 (en) * 2000-08-22 2003-11-04 Sivan Llc Direct dispatcherless automatic vehicle-to-vehicle and non-vehicle to vehicle police/emergency medical service notification system for life threatening accidents, hijackings, thefts and medical emergencies
IL156675A0 (en) * 2001-01-26 2004-01-04 Raytheon Co Vehicle trip determination system and method
US7970644B2 (en) * 2003-02-21 2011-06-28 Accenture Global Services Limited Electronic toll management and vehicle identification
US7701363B1 (en) * 2007-01-17 2010-04-20 Milan Zlojutro Vehicle tracking and monitoring system
US9406086B2 (en) * 2010-11-03 2016-08-02 Endeavoring, Llc System and method for violation enforcement utilizing vehicle immobilization
DE102011085814B3 (de) 2011-11-07 2013-03-28 Robert Bosch Gmbh System mit untereinander über einen gemeinsamen zentralen Server drahtlos vernetzten Mobiltelefonen
NZ605569A (en) 2012-02-02 2013-04-26 Kapsch Trafficcom Ag Factor VIII Formulations
EP2752821A2 (fr) * 2013-01-02 2014-07-09 Albert Kuiper Amélioration de la mise en oeuvre de la tarification routière

Also Published As

Publication number Publication date
EP3113119A1 (fr) 2017-01-04

Similar Documents

Publication Publication Date Title
EP1088286B2 (fr) Dispositif de controle cote route pour un appareil de peage installe dans un vehicule
EP2909815B1 (fr) Procédé et installations de soulèvement de péage conditionné par le trafic
EP1537541B1 (fr) Procede permettant d'identifier un tron on de route soumis a peage
EP1395957B1 (fr) Systeme de peage duel
EP1101201B1 (fr) Procede et systeme pour controler si un appareil servant a debiter une somme d'argent fonctionne correctement
EP3002733B1 (fr) Centrale d'encaissement de péage, appareil mobile et procédé d'encaissement d'un péage
EP3002734B1 (fr) Dispositifs de véhicule et système de péage
DE102022125933A1 (de) System und Verfahren zur Mauterhebung für ein Kraftfahrzeug
EP2811467B1 (fr) Procédé et dispositifs de détection des erreurs dans un système de péage
DE102006032468B3 (de) Adaptive Datenvolumen bei der Übertragung von Daten für eine zentrale Geoobjekterkennung
EP3113119B1 (fr) Procede de suivi de vehicules soumis a peage dans un systeme de peage
EP3113118B1 (fr) Procede de suivi de vehicules soumis a peage dans un systeme de peage et systeme de peage
EP3210194A1 (fr) Procédé et unité embarquée (obu) pour la détermination de taxes de péage
WO2007045623A1 (fr) Appareil de detection de peage et procede de detection de peage
EP3211605B1 (fr) Dispositif de véhicule, système, dispositif coté route et procédé d'exécution d'au moins une transaction
EP2665044B1 (fr) Procédé de mesure de la capacité de puissance d'un système de péage routier
EP3920149A1 (fr) Procédé de détermination d'un péage, appareil de véhicule et système de péage
EP2854111A1 (fr) Procédé, dispositifs, système et produit de programme informatique destinés à percevoir un péage dans un système de péage double
EP2922031B1 (fr) Procédé et dispositifs de détection des erreurs dans un système de péage
DE102018130399A1 (de) Bestimmung einer Fahrtroute
WO2002101661A2 (fr) Systeme de peage double
DE102006024729A1 (de) Verfahren zur Überprüfung der Funktion einer mobilen Detektionseinheit
EP1868163A1 (fr) Procédé et système destinés à la détection automatique d'une voie de trafic soumise à péage et au paiement automatique
EP1361554B1 (fr) Appareil d'identification de véhicules
EP4163886A1 (fr) Système et procédé de perception de péage pour un véhicule automobile

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

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

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

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

Free format text: STATUS: EXAMINATION IS IN PROGRESS

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

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

INTC Intention to grant announced (deleted)
APBK Appeal reference recorded

Free format text: ORIGINAL CODE: EPIDOSNREFNE

APBN Date of receipt of notice of appeal recorded

Free format text: ORIGINAL CODE: EPIDOSNNOA2E

APBR Date of receipt of statement of grounds of appeal recorded

Free format text: ORIGINAL CODE: EPIDOSNNOA3E

APAV Appeal reference deleted

Free format text: ORIGINAL CODE: EPIDOSDREFNE

APBT Appeal procedure closed

Free format text: ORIGINAL CODE: EPIDOSNNOA9E

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

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

Ref legal event code: R096

Ref document number: 502015016673

Country of ref document: DE

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

Free format text: LANGUAGE OF EP DOCUMENT: GERMAN

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20231115

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

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

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

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

Ref country code: NL

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

Effective date: 20231115

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

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

Ref country code: NL

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

Effective date: 20231115

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

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

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

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

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

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

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

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

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

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

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

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