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

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

Info

Publication number
EP3113118B1
EP3113118B1 EP15175359.7A EP15175359A EP3113118B1 EP 3113118 B1 EP3113118 B1 EP 3113118B1 EP 15175359 A EP15175359 A EP 15175359A EP 3113118 B1 EP3113118 B1 EP 3113118B1
Authority
EP
European Patent Office
Prior art keywords
toll
violation
vehicle
database
toll violation
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
EP15175359.7A
Other languages
German (de)
English (en)
Other versions
EP3113118A1 (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 EP15175359.7A priority Critical patent/EP3113118B1/fr
Publication of EP3113118A1 publication Critical patent/EP3113118A1/fr
Application granted granted Critical
Publication of EP3113118B1 publication Critical patent/EP3113118B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07B—TICKET-ISSUING APPARATUS; FARE-REGISTERING APPARATUS; FRANKING APPARATUS
    • G07B15/00—Arrangements or apparatus for collecting fares, tolls or entrance fees at one or more control points
    • G07B15/06—Arrangements for road pricing or congestion charging of vehicles or vehicle users, e.g. automatic toll systems
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/01—Detecting movement of traffic to be counted or controlled
    • G08G1/017—Detecting movement of traffic to be counted or controlled identifying vehicles
    • G08G1/0175—Detecting movement of traffic to be counted or controlled identifying vehicles by photographing vehicles, e.g. when violating traffic rules
    • 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
    • G08G1/205—Indicating the location of the monitored vehicles as destination, e.g. accidents, stolen, rental

Definitions

  • the present invention relates to a method for tracking vehicles subject to tolls in a toll system and to a toll system for carrying out such a method.
  • toll roads Different methods for collecting user fees or tolls for toll traffic areas, for example toll roads, are known.
  • 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.
  • toll systems There are also usage-dependent toll systems known in which an automated registration of the vehicles subject to toll is carried out. This will be the case vehicle subject to toll is automatically recorded when entering the toll traffic area, when leaving the toll traffic area and/or when driving on the toll traffic area and its movement and/or route is evaluated in order to be able to determine and collect the toll due for the route actually driven .
  • decentralized collecting systems are known 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 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 facilities.
  • 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 that carries out the toll recognition. The toll is collected after driving on the toll section.
  • toll collection systems are known that do not use GNSS receivers and carry out position determination and toll recognition exclusively via roadside 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 and collects the toll on this basis. 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. Based on the information transmitted by the vehicle device, the toll due can then be 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 whether, and if so, which toll route section is being traveled, based on the comparison of position data, which was determined using the position determination device, with map data stored in a database.
  • the toll 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) determines the route to be traveled before actually driving on the toll route sections and pays the corresponding toll fee.
  • the toll fee can either be paid directly at the toll station terminal or online, or for registered users are provided via the toll center in a monthly collective bill or are deducted from an existing credit.
  • 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 (Global Navigation Satellite System, GNSS for short) which are stationed in earth orbit and which receive corresponding position signals send out.
  • 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 a specific toll fee from the user whose vehicle has demonstrably used the toll traffic area or will be used in the future, for example by taking cash such as at a toll booth terminal, by central debiting from an account or by 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 toll vehicle 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 .
  • a toll violation notice is a data set that an inspector can use to check a vehicle suspected of a toll violation.
  • a toll violation notice specifies a toll violation that is related to a toll vehicle.
  • the toll violation notice therefore includes the information that an inspector needs in order to have a valid reason for diverting or stopping a vehicle.
  • a toll violation notice is linked to or associated with a vehicle license plate and contains information about the toll violation for which the vehicle is suspected. This information can be, for example, the type and time of the potential toll violation as well as further details about the control device that detects the potential toll violation.
  • inspectors are provided to inspect toll vehicles and to punish toll violations. They inspect toll vehicles that have been identified as having a potential toll violation, remove them from traffic and, if the suspicion of a toll violation is confirmed, punish them accordingly .
  • a control vehicle and its crew are usually stationed near a roadside control device, which can be in the form of a control bridge, for example, and are equipped with a mobile display device in such a way that when a potential toll violation of a vehicle subject to toll is determined, a corresponding toll violation notice is displayed on the mobile display device can be displayed.
  • a roadside control device which can be in the form of a control bridge, for example, and are equipped with a mobile display device in such a way that when a potential toll violation of a vehicle subject to toll is determined, a corresponding toll violation notice is displayed on the mobile display device can be displayed.
  • 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.
  • toll violations In the area of toll systems, it may happen that certain toll violations that occurred in the past were not punished. This may be the case, for example, because a large number of potential toll violations have been detected at a given time and the respective inspectors do not have all of the vehicles for which a toll violation was detected Toll violation notice was generated, could be identified, checked and possibly punished.
  • a lack of control and punishment of a potential toll violation can also occur because the vehicle for which the information about a potential toll violation is available left the monitored traffic area and was then no longer accessible to monitoring. This is particularly the case for vehicles subject to tolls that have left the catchment area of the toll system, for example by crossing the border into a neighboring country or into a neighboring toll system.
  • EETS European Electronic Toll Service
  • EETS European Electronic Toll Service
  • the so-called EETS provider provides on-board units that calculate the toll on the territory of another toll operator, who in turn also which operates or has its control facilities operated.
  • the respective on-board units are not necessarily provided by the actual operator of the toll system, but can be provided by another operator, for example located abroad.
  • a toll vehicle registered abroad enters the area of the domestic toll system and this vehicle is equipped with an on-board unit that is functional for the domestic toll system.
  • the toll fees are paid out on a regular basis by the operator of the on-board units based abroad to the operator of the domestic toll system.
  • 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.
  • a system for detecting and tracking legal violations by vehicles which contains a first server and a second server.
  • the first server contains a vehicle information database that communicates with the second server.
  • the second server is a mobile data terminal that enables the identification of vehicles and retrieves the vehicle information relating to the identified vehicles from the first server via a communication connection. Once the vehicle information is received, appropriate enforcement tactics are created based on the received vehicle information.
  • a method for tracking vehicles subject to toll is specified in a toll system, which has at least one data processing device in communication with an offense database and at least one stationary, road-side control device, with first toll violation notices associated with license plates of vehicles subject to toll being stored in the offense database.
  • the method includes the steps of detecting at least one license plate of a toll vehicle by means of the stationary, roadside control device, forming a control data record which includes the license plate of the detected toll vehicle and its time of capture, and determining
  • Data processing device determines whether there is already a first toll violation notice recorded before the time of capture in the offense database for the recorded license plate, and if there is a first toll violation notice for the recorded license plate in the offense database, associating the first toll violation notice with the control data record.
  • control data record By associating the control data record with the first toll violation notice, it is possible for an inspector who has this data available to punish a toll violation that was committed in the past.
  • the data available to the inspector is enriched accordingly by associating the control data with the first toll violation notice, so that the tracking of toll violations is simplified.
  • control data record associated with the first toll violation notice is stored in a data memory, preferably in the offense database, in a data memory assigned to the central data processing device, a data memory assigned to the roadside control device, a data memory assigned to a transmission device or another data memory.
  • a data memory assigned to the central data processing device
  • a data memory assigned to the roadside control device a data memory assigned to a transmission device or another data memory.
  • the control data record associated with the first toll violation notice can then be retrieved from the data memory for further evaluation, for example.
  • the one associated with the first toll violation notice Control data sets can also be retrieved from a display device in order to then be available for searches and punishment.
  • the toll violation notices stored in the offense database are determined by previously detecting at least one license plate of a toll vehicle by means of a roadside control device and by previously determining whether the toll vehicle has committed a toll violation.
  • the determination of whether there is potentially a toll violation and whether the toll vehicle should be checked by an inspector, diverted and, if the suspicion is confirmed, punished can be carried out in the toll system using actually known procedures.
  • the determination itself can be carried out in a data processing device of the roadside control device, in a central data processing device or in the interaction of different data processing devices and databases.
  • the analysis can be carried out using known criteria based on the identified or collected and known data. For example, it can be determined whether a specific route section was booked in advance using the manual process for the license plate of a vehicle subject to toll.
  • the automatic process can be used to determine whether the setting made in an on-board unit, for example the number of axles or the emission class of the toll vehicle, matches the data determined by the roadside control device and/or whether the OBU is functional.
  • a pre-paid survey can be used to determine whether the pre-paid credit is still sufficient to pay the current toll. The determination can also be carried out using other known criteria and procedures.
  • the determination of whether a toll violation has occurred can also be carried out after the toll vehicle has actually driven on the toll traffic area.
  • toll violations which, for example due to the time delay between the return of the corresponding toll fees by an operator of on-board units based abroad, for example in the EETS system, to the domestic toll operator, can also be detected well after the toll traffic area has been driven on be punished.
  • the existence of such a toll violation is usually determined in a central data processing device of the toll operator, which is connected to a payment database.
  • an overall improved control and punishment of the payment of toll fees in a toll system can be achieved if toll violations registered before the current recording time are associated with the respective license plate at the time of recording and are displayed accordingly to the inspectors via the mobile display devices.
  • a toll violation that exists at the current time of recording can preferably also be determined and, if such a toll violation exists at the time of recording, a second toll violation notice can be generated and this can also be associated with the control data record.
  • the control data record is then stored at least temporarily together with the first toll violation notice associated with it in a data memory of the toll system by a data processing device of the toll system. This can ensure that all toll violations committed by a vehicle subject to toll can be effectively and safely recorded and assigned to it.
  • control data record and at least the first toll violation notice associated therewith are transmitted to a mobile display device and the control data record and the first toll violation notice associated therewith are displayed on the mobile display device.
  • the inspector can at least keep an eye on the first toll violation known for the respective vehicle license plate that has not yet been checked or not yet punished. It is particularly preferred if several or all toll violation notices that are associated with the license plate are transmitted to the mobile display device.
  • the decision about the removal of a toll vehicle can be prioritized, in particular when a large number of toll violation notices are transmitted to the controller or his mobile display device, so that, for example, a vehicle is prioritized for which more than one toll violation or there is a past toll violation.
  • the determination of whether there is already a first toll violation detected before the time of detection for the license plate recorded at the time of detection is preferably carried out in a central data processing device of the toll system and/or in a data processing device of the roadside control device itself.
  • the offense database can either be present in a central data processing device or can be addressed by it, or the offense database can be located in the roadside control device before or can be addressed by it. It can be advantageous to fill the offense database with toll violations or toll violation notices that have not been punished after a predetermined time interval, and then to update the data in the offense database accordingly or to update the data in a central offense database with a decentralized offense database or in the respective ones to synchronize the offense databases available at roadside control devices. This makes it possible to provide data from unpunished toll violations after a short time interval in such a way that the vehicle license plates determined by the roadside control device can be checked promptly for the existence of a criminal offense.
  • the situation is also conceivable in which the control, removal and inspection of a vehicle subject to toll could not be carried out by the inspectors assigned to a first roadside inspection device, since these inspectors may have already been involved in the inspection and punishment of a toll violation by another motor vehicle, and After completion of this inspection and punishment, the other vehicle subject to toll, which had caused a toll violation at the time of recording, is already outside the control radius of the respective inspector.
  • a further, downstream inspector can then check this vehicle, divert it and punish it if this vehicle passes another roadside control device, here a control data record with the license plate recorded at this roadside control device at the time of recording is checked in the offense database and then determined that there is a toll violation recorded in the past, namely the toll violation that could not previously be punished.
  • a toll violation data record in the offense database which includes the first toll violation notice, the associated license plate, the time of detection of the toll violation and a position identifier of the control device detecting the toll violation, the toll violation data record being associated with the control data record and being transmitted to the mobile display device and the data is displayed on the mobile display device.
  • a toll violation data record with a lot of details can make it easier to clarify the facts during control and verification.
  • control data set transmitted to the mobile display device is also provided with a position identifier of the control device that detects the toll violation, such that the inspector, to whom this information is also displayed, can provide the driver of the correspondingly diverted motor vehicle with detailed information about the previous toll violation to facilitate the acceptance of the punishment as well as the punishment itself.
  • the first toll violation notice can preferably be recorded at a time before the time of recording by means of a control device and transmitted to the central data processing device. There, the first toll violation notice can be entered into an offense database in the data processing device.
  • the first toll violation notice can be stored together with the associated license plate, the time of detection of the toll violation and the position identifier of the control device detecting the toll violation in a toll violation data record in the offense database of the central data processing device, in particular if the toll violation cannot be resolved within a predetermined period Duration from the time of detection to the central data processing device is signaled. This can ensure that unpunished toll violations are punished during a later inspection by an inspector.
  • toll violation data records stored in the offense database can be transmitted to several stationary, road-side control devices or all control devices, or for the offense database to provide the stored toll violation data records to several stationary, road-side control devices or to all control devices, so that a safe and quick determination of whether a license plate of the control data record matches an identifier of a toll violation data record, can be carried out in a control device.
  • This preferably happens in the control device that recorded the license plate at the time of capture.
  • a controller located near the control device can be informed particularly quickly about the toll violation notice or it can be transmitted to the inspector's mobile display device, since the license plate can be compared directly in the control device.
  • the central data processing device determines whether there is more than one toll violation notice for the determined license plate at the time of detection. Accordingly, if there is more than one toll violation notice, a prioritization notice can be generated and associated with the control data record, which can be transmitted via the mobile display device and displayed on it together with the control data record and the toll violation notices. If several toll violations occur in his control area, the inspector can be given an indication as to which of the vehicles he should prefer to remove in order to check and possibly punish the toll violation.
  • the toll violation notice preferably includes an identification of the type of toll violation. Based on the type of toll violation, a corresponding prioritization note can then be generated using a weighting table available in a central or decentralized prioritization database, associated with the control data record and transmitted to the mobile display device. The inspector can read the prioritization notice together with the control data record and the toll violation notice on the mobile display device and accordingly select which toll vehicle should be given priority.
  • a control vehicle for tracking detected toll vehicles includes the mobile display device or is carried by it or provided by it, so that an inspector located in the control vehicle can, for example, read out toll violation notices while driving.
  • the controller can access the mobile display device via a mobile device, preferably a mobile computer, a tablet computer or a smartphone, and provide the driver of the appropriately routed motor vehicle with clear information directly at the location where the motor vehicle is parked to the previous toll violation in order to make it easier to accept the punishment as well as the punishment itself and to shorten its duration.
  • a mobile device preferably a mobile computer, a tablet computer or a smartphone
  • the mobile display device can comprise a flat screen or similar and the input unit can be in the form of a touch screen, scroll wheel, joystick, touch pad, a mouse, one or more input keys or voice control.
  • control data record and the associated toll violation notices can preferably be transmitted to a mobile display device by means of a tracking case request.
  • an input unit is also provided with which the inspector can answer the doctrine case request.
  • a pursuit case request means that license plates and associated toll violation notices are sent to an inspector or multiple inspectors and the inspector or inspectors are requested to take over this pursuit case.
  • the doctrine case can then be accepted through user input. If the tracking case request is sent to several controllers, the tracking case request will be removed from the other controllers when the tracking order is accepted by one controller or will be displayed as inactive or already accepted.
  • the toll violation records present in the offense database can be inactivated or deleted if there is an event that justifies the inactivation or deletion.
  • the toll violation data records can be deleted after a period of time has been exceeded from the time the first toll violation notice was recorded, since these may become statute-barred after the period of time has expired.
  • this can be done to the central data processing device in order not to unnecessarily increase the required data capacity of the data processing device and to free up the storage space occupied by the completed toll violations.
  • the at least one license plate of a vehicle subject to toll is recorded using a stationary roadside control device.
  • a stationary roadside control device can, for example be formed by a control bridge.
  • the above-mentioned task to be solved is further solved by a toll system for tracking toll vehicles with the features of claim 12.
  • Advantageous further training results from implementing the features from the above-mentioned process steps and training.
  • a toll system for tracking vehicles subject to toll, comprising a data processing device, an offense database communicating with the data processing device, and at least one stationary, roadside control device.
  • the data processing device is set up to determine, in response to a control data set created by one of the stationary, road-side control devices, which includes a license plate of a toll vehicle recorded by the control device and the associated recording time, whether in the offense database for the registered license plate before At the time of recording, there is a first toll violation notice and, if there is a toll violation notice, to associate the first toll violation notice with the control data record.
  • Computer program product which comprises software code sections which can be loaded into an internal memory of a data processing device which is communicatively coupled to at least one offense database and which, when executed by the data processing device, cause the data processing device to carry out the method described above.
  • a toll system 200 for tracking toll vehicles 102 is shown schematically, with a toll traffic area 100 being provided, for example in the form of a highway, along which a toll vehicle 102 travels.
  • the toll vehicle 102 has, among other things, a license plate 104, wherein the license plate 104 can be, for example, the conventionally known motor vehicle license plate or registration plate.
  • Other forms of identification can also be included here, for example another optical or electronic identification, by means of which a toll vehicle 102 is clearly identified and which can be recognized automatically.
  • the toll system 200 includes, among other things, a roadside control device 202, which in the exemplary embodiment shown is provided in the form of a control bridge which spans the toll traffic area 100.
  • a roadside control device 202 which in the exemplary embodiment shown is provided in the form of a control bridge which spans the toll traffic area 100.
  • Such control bridges are known in principle and enable registration of license plates 104 and other parameters and properties of toll vehicles 104 on all lanes of the toll traffic area 100. Registration can essentially take place directly from the front.
  • the roadside control device 202 can also be designed in the form of a control device arranged on the edge of the toll traffic area 100, which enables the license plates 104 and other parameters of the toll vehicles 104 to be recorded from the side position.
  • Each lane of the toll traffic area 100 is then preferably assigned its own roadside control device 202.
  • the roadside control device 202 has detection devices 204, 204 ', which in the exemplary embodiment shown are designed in the form of optical detection devices, by means of which the license plates 104 of toll motor vehicles 102 are read can.
  • detection devices 204, 204 ' which in the exemplary embodiment shown are designed in the form of optical detection devices, by means of which the license plates 104 of toll motor vehicles 102 are read can.
  • cameras are installed in the control devices 202, which enable the license plates 104 of the toll vehicles 102 passing the control device 202 to be read out. Additional sensors and receivers can also be provided, by means of which additional parameters and identifiers of the toll vehicles 102 passing the roadside control device 202 can be determined.
  • the license plates 104 read by the control device 202 or the optical detection device 204 are fed to a central data processing device 206, which can, for example, be arranged centrally at the location of the operator of the toll system.
  • the central data processing device 206 can also be designed in a distributed manner and accordingly be made up of several interconnected computers or processors which are not located locally at a single physical location.
  • the system can also be structured as a distributed system or as a cloud system.
  • the data recorded by at least two, preferably by a plurality or plurality of roadside control devices 202 are fed to the central data processing device 206.
  • the central data processing device 206 is connected to a crime database 208 of the toll system 200.
  • Data sets are stored in the offense database 208 which link the license plate 104 of a toll vehicle 102 with a first toll violation notice associated with this license plate.
  • These data sets, which are stored in the offense database 208, were recorded by the roadside control device 202 before the actual recording time of the current registration of the toll vehicle 102.
  • the data records available in the offense database 208 are historical toll violation notices from toll vehicles 102 which have not yet been checked or punished.
  • the central data processing device 206 checks upon receipt of a control data record from the roadside control device 202, which includes a license plate 104 of the toll vehicle 102 detected by the roadside control device 202 Offense database 208 whether a data record with a toll violation notice is already stored in the offense database 208 for this license plate 104.
  • the data processing can also be carried out in a data processing device 205 of the control device 202.
  • the data processing device 205 can have a data memory 203, which is intended for temporary storage or permanent storage of data.
  • the data processing device 205 of the control device 202 can also carry out the determination.
  • the data processing device 205 of the control device 202 in the exemplary embodiment shown is in communication with the offense database 208, which can be a copy or a locally stored version of the offense database 208 in order to improve performance.
  • the toll violation notice is associated with the license plate and, together with the control data record, via a corresponding transmission device 210, for example mobile radio, to a mobile display device 212, which is, for example located in a controller vehicle 214.
  • a transmission from the control device 202 or from the data processing device 205 of the control device 202 can be transmitted via mobile radio directly to the mobile display device (214). Alternatively, this can also take place via mobile radio to the mobile display device 214 via a schematically illustrated transmission device 210, which is in communication with the central data processing device 206.
  • control data record which includes the license plate 104 of the recorded toll vehicle 102 as well as the time of its capture, and the associated toll violation notice, which was taken from the offense database 208, is displayed.
  • the inspector can accordingly recognize on the display of the mobile display device 212 that the toll vehicle 102, which has passed the roadside control device 202, has already committed a toll violation before the current detection time or is suspected of doing so.
  • the inspector can decide to remove this vehicle, inspect it and possibly prosecute it.
  • the central data processing device 206 it is also possible to determine from the control data set transmitted by the roadside control device 202 whether a toll violation has also occurred at the time of detection, i.e. the time the toll vehicle 102 is detected by the roadside control device 202. If this is the case, this second toll violation is also transmitted to the mobile display device 212. The determination of whether there is a potential toll violation is carried out in the data processing device 206 on the basis of the data determined for the respective toll vehicle 102 by the roadside control device 202 and from the data made available in a database using known analysis methods.
  • a determination of whether there is a first toll violation notice recorded before the time of detection in the offense database 208 for the license plate can also be carried out in a data processing device arranged in the road-side control device 202 or in a data processing device directly assigned to it, the road-side control device 202 directly assigned data processing device then either has access to a central offense database 208, or has a locally stored copy of the offense database 208.
  • FIG. 2 A flowchart of the procedural steps for tracking toll vehicles in a toll system is shown schematically.
  • step S10 a license plate number of a vehicle subject to toll is first detected by a roadside control device. This detection and the sensors and process steps used for it are known in principle.
  • step S12 a control data record is formed which includes the license plate number and the time the license plate was captured.
  • step S14 it is checked whether a toll violation notice is already present in an offense database of the toll system for the license plate included in the control data record. If this is not the case, the query from the offense database ends.
  • control data record and the toll violation notice associated with it are transmitted to the mobile display device in step S16.
  • control data record is then displayed on the mobile display device in step S18 together with the associated toll violation notice.
  • the toll violation notice is preferably transmitted to a mobile display device of the controller, which is connected to the respective roadside detection device or which is associated with it.
  • a controller is usually either stationed directly at a roadside detection device, or he is stationed in the direction of travel after such a roadside detection device. This stationing is preferably arranged between the road-side detection device and a subsequent departure from the toll traffic area in order to be able to potentially control and divert all vehicles that were detected by the road-side detection device.
  • control data record and the toll violation notice associated with it can also be transmitted to a mobile display device of another controller, which is in a different relationship to the roadside detection device.
  • FIG. 3 An exemplary central data processing device 206 of the toll system 200 for carrying out the method is shown as a block diagram in Figure 3 shown.
  • instructions for example in the form of software code sections, are executed, so that the data processing device 206 is set up to carry out one or more of the method steps and functions described herein.
  • the central data processing device 206 can only include a single computer. However, it can also be a distributed system. According to one embodiment, the central data processing device 206 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 206 includes a central processor 220 (e.g. a CPU (Central Processing Unit), a GPU (Graphics Processing Unit) or both) with an internal memory, a central main memory 222 and a central static memory 224, which communicate with each other via a Bus 226 are communicatively coupled.
  • the central data processing device 206 can also be communicatively coupled to a user interface.
  • This user interface may include a display unit 228 (e.g., a flat panel display or the like) 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 a single integrated device, such as a touch screen.
  • the central data processing device 206 also includes a central data memory 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 data storage 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 be loaded, at least in part, into the main memory 222 and/or into the internal memory of the processor 220, whereby the main memory 222 and the internal memory of the processor 220 are also 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 206 may be implemented in digital circuits or in computer hardware, firmware, software, or combinations thereof.
  • the offense database 208 is also connected to the bus 226 of the central data processing device 206.
  • this is also a data memory that can be designed in the manner described above.
  • the data storage of the offense database 208 can also be designed in a known manner by a database server that is technically connected to a mass storage device, for example a RAID array of hard drives. The data from the offense database 208 is then stored in the mass storage and access is organized by the database server in a known manner.

Landscapes

  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Business, Economics & Management (AREA)
  • Finance (AREA)
  • Devices For Checking Fares Or Tickets At Control Points (AREA)
  • Traffic Control Systems (AREA)

Claims (12)

  1. Procédé de suivi de véhicules (102) soumis à péage dans un système de péage (200) qui présente au moins un appareil de traitement de données (205, 206) se trouvant en communication avec une base de données de délit (208) et au moins un appareil de contrôle (202) fixe, côté route, selon lequel de premières mentions d'infraction au péage associées respectivement à des plaques d'immatriculation de véhicules soumis à péage sont enregistrées dans la base de données de délit (208), comprenant les étapes suivantes :
    - la détection au moins d'une plaque d'immatriculation (104) d'un véhicule soumis à péage (102) au moyen de l'appareil de contrôle (202) fixe, côté route,
    - la formation d'un jeu de données de contrôle qui comprend la plaque d'immatriculation (104) du véhicule (102) soumis à péage détecté et son moment de détection, par l'appareil de contrôle fixe, côté route
    - la détermination par l'appareil de traitement de données (205, 206) établissant si une première mention d'infraction au péage détectée avant le moment de détection existe déjà dans la base de données de délit (208) pour la plaque d'immatriculation (104) détectée, selon lequel les mentions d'infraction au péage enregistrées dans la base de données de délit (208) sont déterminées par la détection précédente au moins d'une plaque d'immatriculation (104) d'un véhicule (102) soumis à péage au moyen d'un appareil de contrôle (202) côté route et la détermination précédente établissant s'il existe une infraction au péage du véhicule (102) soumis à péage,
    - en présence d'une première mention d'infraction au péage pour la plaque d'immatriculation (104) détectée dans la base de données de délit (208), l'association de la première mention d'infraction au péage au jeu de données de contrôle par l'appareil de traitement de données, selon lequel
    - le jeu de données de contrôle et au moins la première mention d'infraction au péage associée à celui-ci sont transmis à un dispositif d'affichage (212) mobile et le jeu de données de contrôle et au moins la première mention d'infraction au péage associée à celui-ci sont affichés sur le dispositif d'affichage (212) mobile,
    - selon lequel le dispositif d'affichage (212) mobile est compris par un véhicule de contrôle pour le suivi de véhicules soumis à péage détectés, est embarqué dans celui-ci ou est fourni par celui-ci et/ou le dispositif d'affichage mobile est compris par un appareil mobile, de préférence ordinateur portable, tablette ou smartphone.
  2. Procédé selon la revendication 1, caractérisé en ce que le jeu de données de contrôle associé à la première mention d'infraction au péage est enregistré dans une mémoire de données (203, 208, 211, 222), de préférence dans la base de données de délit (208), dans une mémoire de données (222) associée à l'appareil de traitement de données (206) central, une mémoire de données (203) associée à l'appareil de contrôle (202) fixe, côté route, une mémoire de données (211) associée à un appareil de transmission (210) ou une autre mémoire de données.
  3. Procédé selon la revendication 1 ou 2, caractérisé en ce qu'il est déterminé si au moment de la détection, une autre infraction au péage existe et, en présence d'une autre infraction au péage, une seconde mention d'infraction au péage est générée et cette seconde mention d'infraction au péage est aussi associée au jeu de données de contrôle, selon lequel de préférence la détermination établissant si une infraction au péage existe aussi au moment de la détection, est réalisée dans l'appareil de traitement de données (206) central et/ou l'appareil de contrôle (202).
  4. Procédé selon l'une quelconque des revendications précédentes, caractérisé en ce qu'un jeu de données d'infraction au péage est enregistré dans la base de données de délit (208), lequel jeu comprend la première mention d'infraction au péage, la plaque d'immatriculation (104) liée à celle-ci, le moment de la détection de l'infraction au péage ainsi qu'une caractéristique de position de l'appareil de contrôle (202) détectant l'infraction au péage, selon lequel le jeu de données d'infraction au péage est associé au jeu de données de contrôle.
  5. Procédé selon l'une quelconque des revendications précédentes, caractérisé en ce que l'appareil de contrôle (202) fixe, côté route présente une caractéristique de position et la caractéristique de position de l'appareil de contrôle (202) qui a détecté la plaque d'immatriculation du véhicule (102) soumis à péage, est comprise par le jeu de données de contrôle.
  6. Procédé selon l'une quelconque des revendications précédentes, caractérisé en ce que la première mention d'infraction au péage est détectée à un moment précédant le moment de la détection au moyen d'un appareil de contrôle (202) et est transmise à l'appareil de traitement de données (206) central.
  7. Procédé selon la revendication 6, caractérisé en ce que la première mention d'infraction au péage est enregistrée conjointement avec la plaque d'immatriculation (104) associée à celle-ci, le moment de la détection de l'infraction au péage ainsi que la caractéristique de position de l'appareil de contrôle (202) fixe, côté route détectant l'infraction au péage dans un jeu de données d'infraction au péage dans la base de données de délit (208) de l'appareil de traitement de données (206) central, de préférence lorsqu'une exécution de l'infraction au péage n'est pas signalée à l'appareil de traitement de données (206) central au cours d'une période prédéfinie à partir du moment de la détection .
  8. Procédé selon l'une quelconque des revendications précédentes, caractérisé en ce que des jeux de données d'infraction au péage enregistrés dans la base de données de délit (208) sont transmis à tous les appareils de contrôle (202) fixes, côté route ou la base de données de délit (208) fournit les jeux de données d'infraction au péage enregistrés à tous les appareils de contrôle (202) fixes, côté route et la détermination établissant si une plaque d'immatriculation du jeu de données de contrôle coïncide avec une plaque d'immatriculation (104) d'un jeu de données d'infraction au péage est réalisée dans un appareil de contrôle (202) fixe, côté route, de préférence dans l'appareil de contrôle (202) fixe, côté route qui a détecté la plaque d'immatriculation (104) au moment de la détection.
  9. Procédé selon l'une quelconque des revendications précédentes, caractérisé en ce qu'il est déterminé dans l'appareil de traitement de données (206) central s'il existe, au moment de la détection, plus d'une mention d'infraction au péage pour la plaque d'immatriculation (104) déterminée et, en présence de plus d'une mention d'infraction au péage, une mention de priorisation est générée et est associée au jeu de données de contrôle, est transmise au dispositif d'affichage (212) mobile et est affichée sur celui-ci conjointement avec le jeu de données de contrôle et les mentions d'infraction au péage.
  10. Procédé selon l'une quelconque des revendications précédentes, caractérisé en ce que la mention d'infraction au péage comprend une caractérisation du type d'infraction au péage et, sur la base du type d'infraction au péage à l'aide d'un tableau de pondération se trouvant dans une base de données de priorisation centrale ou décentralisée, une mention de priorisation correspondante est générée et est reliée au jeu de données de contrôle, est transmise à l'appareil d'affichage (212) mobile et est affichée conjointement avec le jeu de données de contrôle et la mention d'infraction au péage sur le dispositif d'affichage (212) mobile.
  11. Procédé selon l'une quelconque des revendications précédentes, caractérisé en ce que les jeux de données d'infraction au péage présents dans la base de données de délit (208) sont inactivés ou supprimés en présence d'un événement, selon lequel l'événement est de préférence le dépassement d'une durée à partir du moment de la détection de la première mention d'infraction au péage et/ou le signalement du traitement de l'infraction au péage à l'appareil de traitement de données (206) central.
  12. Système de péage (200) pour le suivi de véhicules (102) soumis à péage comprenant
    - un appareil de traitement de données (205, 206),
    - une base de données de délit (208) communiquant avec l'appareil de traitement de données (205, 206),
    - au moins un appareil de contrôle (202) fixe, côté route, et
    - un dispositif d'affichage (212) mobile qui est compris par un véhicule de contrôle pour le suivi de véhicules soumis à péage détectés, est embarqué dans celui-ci ou est fourni par celui-ci et/ou un dispositif d'affichage mobile qui est compris par un appareil mobile, de préférence ordinateur portable, tablette ou smartphone,
    caractérisé en ce que
    - l'appareil de traitement de données (205, 206) est conçu afin de
    - en réponse à un jeu de données de contrôle établi par un des appareils de contrôle (202) fixes, côté route qui comprend une plaque d'immatriculation (104) détectée par l'appareil de contrôle fixe, côté route d'un véhicule (102) soumis à péage et le moment de la détection afférent,
    - déterminer s'il existe une première mention d'infraction au péage détectée avant le moment de la détection dans la base de données de délit (208) pour la plaque d'immatriculation (104) et, en présence d'une mention d'infraction au péage, associer la première mention d'infraction au péage au jeu de données de contrôle par l'appareil de traitement de données, selon lequel les mentions d'infraction au péage enregistrées dans la base de données de délit (208) sont déterminées par la détection précédente au moins d'une plaque d'immatriculation (104) d'un véhicule (102) soumis à péage au moyen d'un appareil de contrôle (202) fixe, côté route et la détermination précédente établissant s'il existe une infraction au péage du véhicule (102) soumis à péage,
    - selon lequel le système de péage (200) est configuré afin de transmettre le jeu de données de contrôle et au moins la première mention d'infraction au péage associée à celui-ci au dispositif d'affichage (212) mobile, qui est configuré pour afficher le jeu de données de contrôle et au moins la première mention d'infraction au péage associée à celui-ci sur le dispositif d'affichage (212) mobile.
EP15175359.7A 2015-07-03 2015-07-03 Procede de suivi de vehicules soumis a peage dans un systeme de peage et systeme de peage Active EP3113118B1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP15175359.7A EP3113118B1 (fr) 2015-07-03 2015-07-03 Procede de suivi de vehicules soumis a peage dans un systeme de peage et systeme de peage

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
EP15175359.7A EP3113118B1 (fr) 2015-07-03 2015-07-03 Procede de suivi de vehicules soumis a peage dans un systeme de peage et systeme de peage

Publications (2)

Publication Number Publication Date
EP3113118A1 EP3113118A1 (fr) 2017-01-04
EP3113118B1 true EP3113118B1 (fr) 2023-12-13

Family

ID=53514062

Family Applications (1)

Application Number Title Priority Date Filing Date
EP15175359.7A Active EP3113118B1 (fr) 2015-07-03 2015-07-03 Procede de suivi de vehicules soumis a peage dans un systeme de peage et systeme de peage

Country Status (1)

Country Link
EP (1) EP3113118B1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AT521875B1 (de) * 2018-10-25 2021-07-15 Gharb Samy Überwachungssystem zur Verfolgung von Fahrzeugen, bspw. Autos, Bussen oder Yachten

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1783692A3 (fr) * 2005-10-06 2007-12-05 Siemens Aktiengesellschaft Mise en application avec des temps de cycle réduits
US7843321B2 (en) * 2007-02-15 2010-11-30 Ipt, Llc Vehicle violation enforcement system and method
CN106875719A (zh) * 2010-04-15 2017-06-20 米兰.兹洛朱特罗 车辆监控和识别系统
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

Also Published As

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

Similar Documents

Publication Publication Date Title
EP2909815B1 (fr) Procédé et installations de soulèvement de péage conditionné par le trafic
EP1088286B2 (fr) Dispositif de controle cote route pour un appareil de peage installe dans un vehicule
DE10104502B4 (de) Kontrollverfahren zur Straßengebührenerfassung
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
EP1630747A2 (fr) Système et méthode de perception des droits de péage
EP2811468B1 (fr) Procédé et dispositif de reconnaissance d'erreurs dans un système de péage
EP3991143A1 (fr) Procédé de paiement d'une taxe destiné à permettre à un véhicule d'utiliser un réseau routier soumis à des frais de péage, et système de péage destiné à la mise en oeuvre du procédé
EP3113118B1 (fr) Procede de suivi de vehicules soumis a peage dans un systeme de peage et systeme de peage
EP3113119B1 (fr) Procede de suivi de vehicules soumis a peage dans un systeme de peage
WO2007045623A1 (fr) Appareil de detection de peage et procede de detection de peage
EP2665044B1 (fr) Procédé de mesure de la capacité de puissance d'un système de péage routier
WO2009043691A1 (fr) Dispositif et procédé de détection de péage routier
EP2922031B1 (fr) Procédé et dispositifs de détection des erreurs dans un système de péage
DE102006024729A1 (de) Verfahren zur Überprüfung der Funktion einer mobilen Detektionseinheit
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
WO2002101661A2 (fr) Systeme de peage double
DE102006027191A1 (de) Verfahren und System zur automatischen Erkennung eines mautpflichtigen Verkehrsweges und zur automatischen Bezahlung der Mautgebühr
DE20321002U1 (de) Fahrzeugmanagementsystem
EP1361554B1 (fr) Appareil d'identification de véhicules
EP4163884A1 (fr) Procédé et système de contrôle automatique dans un système de péage
EP3346451B1 (fr) Procédé destinés au suivi de véhicules assujettis au péage dans un système de péage et un système de péage correspondant

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

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

APAF Appeal reference modified

Free format text: ORIGINAL CODE: EPIDOSCREFNE

APBT Appeal procedure closed

Free format text: ORIGINAL CODE: EPIDOSNNOA9E

APAM Information on closure of appeal procedure modified

Free format text: ORIGINAL CODE: EPIDOSCNOA9E

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

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

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

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

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

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

Free format text: NOT ENGLISH

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 502015016699

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

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

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

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

Ref country code: 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: 20231213

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20231213

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

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

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

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

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

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

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

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

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

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

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

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