EP3002733B1 - Centrale d'encaissement de péage, appareil mobile et procédé d'encaissement d'un péage - Google Patents

Centrale d'encaissement de péage, appareil mobile et procédé d'encaissement d'un péage Download PDF

Info

Publication number
EP3002733B1
EP3002733B1 EP14187568.2A EP14187568A EP3002733B1 EP 3002733 B1 EP3002733 B1 EP 3002733B1 EP 14187568 A EP14187568 A EP 14187568A EP 3002733 B1 EP3002733 B1 EP 3002733B1
Authority
EP
European Patent Office
Prior art keywords
toll
position data
mobile
computing device
mobile device
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
EP14187568.2A
Other languages
German (de)
English (en)
Other versions
EP3002733A1 (fr
Inventor
Corinna Kossert
Burkhard Mende
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 EP14187568.2A priority Critical patent/EP3002733B1/fr
Priority to PL14187568.2T priority patent/PL3002733T3/pl
Publication of EP3002733A1 publication Critical patent/EP3002733A1/fr
Application granted granted Critical
Publication of EP3002733B1 publication Critical patent/EP3002733B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

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

Definitions

  • the present invention relates to a toll control center, a mobile device and a method for a toll collection method for collecting a toll for the use of a traffic area that is subject to toll by a vehicle that is subject to toll.
  • usage-based billing toll systems are dependent on recording the route taken by the respective vehicles that are subject to the toll, at least in the area that is decisive for the use of the road that is subject to the toll.
  • the vehicle positions in the toll collection system operated by the German toll operator Toll Collect GmbH are recorded at least in the area of the entrance to the respective traffic area subject to toll and the exit from this traffic area.
  • Toll data is understood here to mean data of traffic areas subject to tolls and/or toll fees, which are assigned to a user and are determined by toll identification and/or toll determination.
  • Toll-relevant data is all data that is used to determine the toll fee, such as the identifier and/or the length of the road area subject to the toll, 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 record, which, in conjunction with the other toll-relevant data, allows the total fee to be determined when the toll is collected.
  • toll recognition is understood here to mean the process of linking a used traffic area that is subject to toll and is recognized on the basis of a detected vehicle position or on the basis of a plurality of detected vehicle positions with the user. In other words, it is understood to mean that the user is linked for the first time to a used traffic area that is subject to a toll.
  • toll determination is understood here as the process of determining a toll fee from the traffic area that is used or that is likely to be used and is subject to toll, possibly taking into account vehicle data and times relevant to the toll.
  • toll collection is understood here as the process of collecting the specific toll fee from the user whose vehicle has verifiably used the toll road or will use it in the future, for example by taking cash, for example at a toll station 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 traffic area subject to toll is understood here to mean traffic areas for the use of which a toll fee is due.
  • the amount of the toll fee can be determined, for example, based on the distance traveled on the traffic area subject to toll, for example measured in meters, based on the number of toll route sections used or as a lump sum or based on the time for using a specific route network subject to toll, for example in the case of a city toll.
  • decentralized surveying systems are known in which a position determination device is provided in the vehicle, for example in a vehicle device, which is also referred to as an “on board unit” (OBU).
  • a GNSS receiver in the vehicle detects the vehicle's position via a GNSS system and a DSRC receiver in the vehicle can receive positions from roadside devices.
  • this position data is processed in the on-board device to identify any traffic areas that are subject to tolls.
  • the toll can be collected decentrally in the vehicle device, for example by debiting a prepaid credit.
  • the toll can be collected after transmission of the determined toll data to a toll center by the toll center, which carries out the debiting or invoicing.
  • the toll is collected after driving on the toll road 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, toll determination and toll collection are carried out in the toll center.
  • the toll can be determined, for example, by actually calculating the toll on the basis of a determined route length and a toll factor, or by reading out the toll due from a database based on the determined route sections.
  • 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 is recognized outside of 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 road section.
  • toll collection systems which dispense with the use of GNSS receivers and carry out position determination and toll recognition exclusively via roadside vehicle detection devices.
  • the vehicle that is subject to the toll sends a corresponding identification signal to the vehicle detection device on the road.
  • 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.
  • the toll is collected after driving on the toll road section.
  • toll center instead of a toll center, the toll can also be collected by a separate toll service.
  • the Toll Collect GmbH system has been designed to collect tolls when using the Autobahn in Germany, with roadside vehicle detection devices in the form of permanently installed control bridges spanning the road, which detect the license plate number of each passing vehicle and thus make a comparison with it enable a central database.
  • roadside vehicle detection devices in the form of permanently installed control bridges spanning the road, which detect the license plate number of each passing vehicle and thus make a comparison with it enable a central database.
  • mobile vehicle detection devices can also be provided, which serve to support the detection of the vehicles. This system can be extended to other streets.
  • vehicle-mounted toll collection devices which are also referred to as toll devices, OBUs (on-board units) or vehicle devices, have proven themselves, which have a position determination device for determining the position of the vehicle or are coupled to a position determination device provided in the vehicle are.
  • the on-board devices can accordingly determine the position of the respective vehicle that is subject to the toll and, using map material stored in the on-board device, determine whether the vehicle is in a traffic area that is subject to the toll. If this is the case, the on-board device determines a toll fee for the use of the determined toll traffic area and transmits the corresponding toll data, which include the determined fee, to a toll control center.
  • the toll data transmitted from the on-board device to the toll center can also only include information about the route traveled on the traffic area subject to toll, for example a section of the route subject to toll, with the toll due then being calculated on this basis in the toll center.
  • the toll due is billed to the respective user or deducted from an existing credit.
  • 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 emit corresponding position signals.
  • the position determination device uses these signals in a known manner to calculate its own position. Examples of such GNSS systems are the US GPS system, the Russian GLONASS, the European Galileo and the Chinese compass system, the latter of which are still in the process of being set up.
  • a speedometer, an odometer, and other sensors such as a gyroscope or an electronic compass can also be connected to the position determination device in order to enable an even more precise position determination, for example by dead reckoning. This can be particularly important if no GNSS data is available, for example in a tunnel, and an accurate position determination is still desired.
  • the transmission of the toll data to the toll control center is carried out via a communication module present in the vehicle device, which uses a known mobile radio standard and communicates the data to the toll control center via the GSM standard, for example.
  • a two-way communication is not provided, but only the toll data determined by the on-board device are transmitted to the toll center when the on-board device has completed the collection of the data.
  • the user In order to enable correct toll collection, the user must initialize the on-board unit 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 on-board unit determines the toll due for the respective journey, taking into account the position of the vehicle subject to the toll determined by the position determination device and the comparison of the position of the vehicle subject to the toll with a database in which the roads subject to the toll 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 by the position determination device over the course of the journey and recorded by the vehicle device are transmitted to the toll center continuously or when a certain criterion is met, for example when a predetermined amount of position data has been reached.
  • the toll to be paid for the vehicle that is subject to the toll for this trip is then determined and collected centrally in the toll control center based on the vehicle data and the traffic areas identified as being traveled on from the position data that are subject to the toll.
  • This method of collecting the toll data in which the user of the vehicle subject to the toll only has to initialize the on-board unit and then the route is recorded, the toll data is transmitted to the toll center and the toll is collected after initialization without any further user input referred to as the automatic method (AV).
  • AV automatic method
  • the toll is only determined after driving on the respective toll road section and is levied in that it is billed accordingly or deducted from a deposited or pre-paid balance.
  • the vehicle device carried by the vehicle subject to the toll recognizes based on the comparison of position data, which were determined using the position determination device, with map data stored in a database, whether and if so, which route section subject to the toll is being driven on.
  • Such a toll route section is then stored in a memory device of the vehicle device.
  • toll road 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 is met, for example after a predetermined number of stored road sections has been exceeded.
  • the toll determination takes place on this basis either in the toll center or in the vehicle device.
  • the toll fee to be collected is then transmitted to the toll center as toll data.
  • AV automatic procedure
  • the authorization to use the traveled, toll route section is acquired step by step after driving on each individual toll route section, with the toll being collected via the toll center after driving on the toll route section and transmission of the corresponding data to the toll center becomes.
  • the toll collection system operated by Toll Collect GmbH can also be used to log in using the so-called manual procedure (MV).
  • AV automatic procedure
  • MV manual procedure
  • the respective user can use one of the approximately 3,600 toll station terminals, which are typically set up at truck stops, rest areas or petrol 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 that consists of one or more toll route sections.
  • the user enters the planned driveway and the planned departure from the toll road at the toll station terminal or in the web service before driving on the route, whereby one or the several toll road sections of the route can be defined.
  • 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 driven 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 on the Internet, or it can be made available to registered users via the toll center in a monthly collective bill, or it can be deducted from an existing balance.
  • Booking a route using the manual method results in a fixed route that the user cannot leave without being considered a toll dodger.
  • a route change may be necessary, for example, if a section of the booked route is blocked or if a traffic jam occurs that you want to avoid. It can also happen that a user wants to stop at additional stations on the way. If the user wants to change his route after starting the journey booked using the manual method, he must do so at a stationary toll terminal so that the route actually driven remains traceable. The user then has to partially cancel the booked route and then book the new desired route.
  • the US 6,744,383 B1 describes a road system with devices for detecting and tracking vehicles by identifying a wireless device in the vehicle.
  • the WO 2013/190566 A2 describes a centralized toll collection system for tracking and monitoring vehicles using geo-enabled devices.
  • the US 2002/0067291 A1 describes a system for toll payment and traffic management.
  • a toll control center for collecting a toll from a vehicle that is subject to toll when using a traffic area that is subject to toll, comprising a central computing device and at least one central communication device which is communicatively coupled to the central computing device.
  • the central computing device is set up to receive, via the central communication device, an initiation request for initiating a toll collection process for using the traffic area that is subject to toll by the vehicle that is subject to toll from a mobile device, to initiate a toll collection process in response to the receipt of the initiation request, and in response to the Occurrence of a termination event to terminate the initiated toll collection procedure.
  • the initiated toll collection method is a manually initiated toll collection method in which the choice of route is not rigidly specified with the initiation, as is the case with the previously known manual toll collection method, but is flexible. Therefore, it is also referred to herein as a route-flexible manual toll collection method.
  • the toll for the route then known to the toll center is determined and collected only after the journey has been completed.
  • the toll collection can be carried out centrally in the toll center or by a separate toll service.
  • the toll can also be collected in the mobile device, which is loaded with a prepaid credit, for example, or which enables billing via the mobile phone bill.
  • a vehicle can use a traffic area that is subject to toll without the user having to do so beforehand the journey has to book the intended route firmly and without a vehicle-side detection device, in particular an on-board unit (OBU), having to be provided in the respective vehicle.
  • OBU on-board unit
  • vehicles that are subject to the toll can use traffic areas that are subject to the toll without the need for any special equipment in the vehicle that is subject to the toll.
  • the user can initiate the use of the toll traffic area or the toll journey by means of the mobile device as desired and the actual booking is only carried out at the end of the journey by ending the journey initiated by the user however, the user can flexibly take the route he desires. The actual route is then only determined after the journey has ended at the toll station.
  • the toll center can only contain a single computer. However, it can also be a distributed system.
  • the computing device of the toll center includes at least one processor with an internal memory.
  • the computing device is a single, preferably physically separable computer. In another embodiment, this is a distributed system, ie, multiple independent computers that 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 of the computing device then work autonomously but are functionally coordinated with one another.
  • the toll center with a computer and communicatively coupled computers located at roadside sensing devices. In this case, all steps carried out by the computing device according to the invention can be carried out by the computer of the toll center. Alternatively, one or more of these steps may be performed by a computer located at a roadside sensing device.
  • the initiation request includes start position data and the termination event includes end position data.
  • the termination event includes end position data.
  • the central computing device is set up to receive a termination event in the form of a termination request from the mobile device via the central communication device, the termination request including end position data.
  • the user can end the toll collection process by sending the end request, for example when he has left the traffic area that is subject to the toll.
  • the central computing device can be set up to receive further position data, for example via position data, of the mobile device, which corresponds to a position that is outside of a toll traffic area, following the receipt of start position data, without a termination request from the mobile device as a termination event evaluate and to interpret the further position data as end position data.
  • the central computing device can be set up to check received additional position data to determine whether they correspond to a position that is outside a toll traffic area, in order to determine the occurrence of a termination event if this is the case.
  • Start position data, end position data and via position data are, for example, data that contain at least one representation of at least one current position (start position, end position, via position) of the vehicle, for example by specifying the exact degrees of longitude and latitude.
  • the position data can represent both data from a single position of the vehicle and from multiple positions of the vehicle, preferably in direct succession, from which the central computing device generates consolidated position information, For example, a specific geographic object that is considered a start position, end position, or via position is determined.
  • Start position data, end position data, and via position data may also be represented by naming a toll road section as a corresponding start position, end position, and via position.
  • Start position data can also be represented by naming an entry into a toll traffic area as the start position, for example an entrance to one or more toll road sections.
  • End position data can also be represented by naming an exit from a traffic area subject to toll as the end position, for example a departure from one or more road sections subject to toll.
  • Via position data is position data of the vehicle received by the toll center subsequent to the start position data from either the mobile device or a roadside sensing device, respectively, and is not position data previously declared as end position data (e.g., end position data included in the termination request).
  • a message from the mobile device to the toll center can also include information about the orientation of the vehicle and/or the current direction of travel and/or the current speed and/or the time of detection.
  • the position determination device in the vehicle can be used, for example, which supplies current position information.
  • the direction of travel and the speed can also be determined.
  • the direction of travel can also be determined using an (electronic) compass.
  • the speed can also be determined from the vehicle's speedometer.
  • Messages with VIA position data of the vehicle which are sent from a roadside detection device to the toll center, can preferably also include the time of detection and/or the direction of travel of the vehicle in addition to the actual position of the determined vehicle.
  • the initiation request and/or the termination event for example a termination request, preferably also contains an indication of a means of payment and/or a Vehicle identifier and/or an indication of a user identifier.
  • a termination request preferably also contains an indication of a means of payment and/or a Vehicle identifier and/or an indication of a user identifier.
  • the identified traffic area subject to toll can be assigned to a specific user, a specific vehicle and/or a specific means of payment (e.g. credit account).
  • the initiation request and/or the termination event for example a termination request, preferably also contains vehicle-related data in the form of vehicle data on which the toll fee depends (e.g. permissible total weight, number of axles, emission class, etc.).
  • toll determination can be performed by determining the route traveled on the toll road from the start position and the end position, and taking into account the vehicle data, a toll to be paid can be determined.
  • the toll can also be collected centrally, insofar as payment information is transmitted from the mobile device to the toll center or payment information is stored centrally and a transmitted user ID can be used to allocate a means of payment in the toll center.
  • the user ID can be carried out using any ID.
  • the user identifier can preferably be provided using the license plate number of the motor vehicle that is subject to the toll, using the mobile phone number or MAC address of the mobile device, or using a customer number. If the mobile phone number is used as the user ID, the user preferably does not have to enter this separately, but this is automatically transmitted to the central communication device of the toll center via the mobile communication device of the mobile device. In this way, Via position data transmitted from the mobile device to the toll control center can also be unambiguously assigned to the toll collection method initiated by the user, so that the route used by the vehicle that is subject to the toll can be determined unambiguously.
  • Information about the intended payment behavior can be stored as payment information, for example whether the user receives an invoice or credit card information or a prepaid credit is stored so that the toll can be collected directly. It can also be stored as payment information that a prepaid credit is loaded on the mobile device, via which the toll is then collected. Furthermore, the information that the toll is billed via the mobile operator of the mobile device can also be stored as information.
  • a link can also be established between the user identifier and the vehicle identifier, for example the vehicle registration number, so that the toll collection method initiated for the respective user via the mobile device is clearly linked to the vehicle using the toll road.
  • the toll center must then be informed that the vehicle with this license plate number or this identifier is assigned to the toll collection process initiated by the user via the mobile device in order to enable correct handling of the data recorded by the roadside recording device.
  • the central computing device is set up to determine a route for the vehicle that is subject to the toll on the traffic area that is subject to the toll between a starting position defined by the start position data and an end position that is defined by the end position data, preferably taking into account received Via position data, and based on the determined route a due toll fee determine and collect the toll fee.
  • the computing device of the toll control center is set up to determine the best route between the start position and the end position according to at least one predetermined criterion using the traffic areas subject to toll.
  • the at least one predetermined criterion can be the route that costs the least toll to use, the route that is the shortest or that usually takes the least time to use.
  • a weighted evaluation of all these criteria can also be the basis for determining the best route. This is advantageous because several travel routes can be possible when determining the travel route.
  • the computing device is set up to determine a toll on the basis of the calculated route.
  • the additional information sent by the user with the initiation request is preferably also taken into account.
  • the central computing device is preferably set up to receive via position data of the vehicle that is subject to the toll from a roadside detection device. In this way, the route actually traveled by the vehicle can be determined more reliably, in particular when there are different drivable routes between the start position and the end position.
  • the Via position data of the vehicle that is subject to the toll, sent by the recording device, can be received at the central computing device via the same central communication device of the toll center via which the central computing device also receives the initiation request from the mobile device.
  • this central communication device can have different communication channels, a first of which is assigned to the receipt of messages from mobile devices, for example the receipt of initiation requests, and a second to the receipt of messages from roadside detection devices, for example the receipt of via Position data of vehicles subject to toll.
  • the toll center can be equipped with several central communication devices, each for receiving messages from only a single type of transmitter (mobile device or roadside detection device are provided.
  • the Via position data of the vehicle that is subject to the toll, sent by the recording device, can be received at the central computing device via a further central communication device of the toll center, which is included in the toll center in addition to the communication device via which the central computing device receives the initiation request from the mobile device.
  • the central computing device is set up to determine a route for the vehicle that is subject to the toll on the traffic area that is subject to the toll between a starting position and an end position, preferably taking into account received via position data, and to calculate a due toll fee on the basis of the route determined. Accordingly, a reliable determination of the actual travel route can be made.
  • the central computing device is set up to check the plausibility of the start position data according to a predefined criterion when a via position is received for the first time from a roadside detection device after receipt of the initiation request.
  • This can be used, for example, to check whether the start position data has been entered correctly by the user.
  • the check can be carried out, for example, in such a way that the distance between the starting position and the position of the roadside detection device is calculated and from this an expected travel time is calculated from a predetermined average speed and, if necessary, a safety margin, which is compared with the time actually driven by the vehicle between the Initiation request and the roadside sensing device is compared. If there is a discrepancy, it can be assumed that the starting position data was not transmitted correctly, so that the vehicle can be put out for inspection so that a roadside inspection device or an inspection vehicle can identify and check the vehicle that is subject to the toll.
  • control bridges can also be on the roadside, as can mobile control vehicles traveling along in flowing traffic or stationary control vehicles arranged above or next to the road, which can communicate with the vehicles or can establish short-distance communication.
  • roadside detection devices for example control bridges that span the respective toll traffic area, or mobile control devices, can be used to detect the respective toll vehicle that has properly initiated the toll journey via the mobile device.
  • an identifier associated with the mobile device is stored in a memory of the toll control center. This can be a license plate number, an identifier stored in an RFID chip or the like, via which a roadside detection device can detect a vehicle with the mobile device.
  • the respective recording data is also transmitted to the toll center as Via position data.
  • the advantage of this embodiment is that on the basis of Via position data, which was recorded by roadside detection devices and transmitted to the toll center, the computing device of the toll center, in the best case, the route actually driven by the vehicle subject to the toll or at least the best according to at least one predetermined criterion route can be determined.
  • the toll is then calculated on the basis of the determined route and the corresponding toll fee is debited from the stored means of payment.
  • the central computing device is preferably set up to send a status request to the mobile device in response to a predetermined event and to receive a status message from the mobile device via the central communication device, which message comprises via position data of the mobile device.
  • the predetermined event can be, for example, the receipt of an initiation request with start position data from the mobile device and/or the receipt of via position data from a roadside detection device and/or the receipt of a status message with via position data from the mobile device and/or the expiry of a predetermined and/or or calculated length of time since receiving the initiation request and/or the status message with the via location data from the mobile device and/or the via location data from the roadside sensing device. This means that the route can also be checked without using the roadside detection devices or in addition to them.
  • a predetermined event can also be present, for example, when an expected travel time between two roadside detection devices is exceeded.
  • the status message can be used to determine whether the vehicle has left the toll road without properly completing the journey, or whether the vehicle is still on the toll road and has encountered an unknown traffic disruption.
  • Such a predetermined event can occur if the vehicle cannot reach a precalculated time between the two known positions due to the existing traffic conditions, for example a traffic jam or a blocking of the respective traffic area, but needs significantly longer.
  • a further reason may be that in the meantime the vehicle—unnoticed by the roadside detection devices—has left the traffic area that is subject to the toll and accordingly can no longer be detected by the roadside detection devices. In the latter case, the user would have failed to properly end the journey.
  • the last via position data received from the mobile device are preferably those that the mobile device sends as part of a status message in response to the receipt of a status request from the toll center.
  • the central computing device can be set up to send the status request to the mobile device only after the expected period of time has elapsed, if the central computing device has still received via position data of the vehicle from a roadside detection device by the end of the expected period of time, with the status request being configured in this way is that upon receipt of the status request, the mobile device is instructed to transmit its via position without delay.
  • the central computing device can be set up to send the status request to the mobile device before the end of the expected period of time--for example in response to receiving the initiation request or a via position--the status request being designed in such a way that the mobile device is instructed sending via position data delayed by the expected period of time, and wherein the central computing device is further set up to send a cancellation message to the mobile device, with which the sent status request is canceled if the central computing device until the expected period of time has elapsed via position data of the vehicle received from a roadside sensing device.
  • the annulment message can consist of or include a new status request of this type.
  • the user of the vehicle with the mobile device may be able to select several routes starting from the last determined position, for example at a motorway junction or a motorway exit. Then all those detection devices are the closest detection devices that the mobile device (in a vehicle) can reach on a toll traffic area without first having to pass another on-road detection device.
  • the roadside detection devices located in a certain area around the last received position of the mobile device can also be determined as the next to be reached roadside detection devices. If there are several roadside detectors in the area, the one furthest from the last position received is selected, or - especially in the case where the last position received is a via position - the one closest in the direction of travel the last previously received position. If an initially determined environment contains no or only one roadside sensing device, the environment shall be expanded until at least one other roadside sensing device is contained in the expanded environment, which can be selected.
  • the computing device is set up to adapt the minimum average speed, on which the computing device bases the determination of the expected period of time, for example on the basis of current traffic information.
  • the computing device can receive information transmitted via the communication device, for example as part of the roadside detection device, or information in some other way. If the toll control center knows that there is a traffic disruption in a certain section of a toll road, the expected travel times can be adjusted accordingly.
  • the request for current position data from the toll center to the mobile device can be reduced to cases where such information about traffic disruptions is not available at the toll center or is not accurate if the original position, which was entered by the user of the respective vehicle subject to the toll at the Initiation of the toll journey specified was incorrect, or if the user forgot to properly complete the toll journey.
  • the central computing device is particularly preferably set up to calculate the route between the starting position transmitted by the mobile device or the last via position received from a roadside detection device or the last via position received from the mobile device in response to a status request and the position of the to determine the next roadside detection device to be reached and to calculate the expected duration on the basis of the average speed expected on this route, which is determined from at least one average speed stored in a memory of the central computing device, preferably with the addition of a percentage or absolute safety margin.
  • a central computing device is preferably set up to determine whether the via position of the via position data received with the status message is outside the traffic area subject to toll and, in response to the determination that the via position is outside the traffic area subject to toll, to determine the occurrence of a termination event or to send a request to send a termination request to the mobile device and preferably in response thereto to receive a termination event in the form of a termination request from the mobile device via the central communication device, the termination request more preferably comprising end position data.
  • the central computing device is set up to determine whether the via position of the via position data received with the status message is within the traffic area that is subject to toll and, in response to the determination, that the via position is within the toll Traffic area is to continue the initiated toll collection method and preferably adjust an average speed stored in a memory of the central computing device for the route section currently under consideration.
  • the transmission of a large number of status requests to other vehicles that are subject to the toll can be reduced or avoided if it turns out that the current average speed in a specific section of road is lower than previously assumed.
  • the expected journey times for other vehicles that are subject to the toll can be adjusted in this section of the route. Accordingly, the route-flexible manual toll collection process can be continued and by adjusting the average speed to the following vehicles Status requests are issued in a customized manner so that traffic can be reduced.
  • the mobile device is prompted to do so , to transmit a current position to the toll center.
  • This can be done, for example, by the mobile phone automatically transmitting its current position to the toll center, this position being determined again, for example, in the mobile device by a position determination device such as a GPS system or by evaluating the respective radio cells.
  • the mobile device can prompt the user to enter a current position, in which case the user can, for example, enter his current position from a road map or a drop-down menu, possibly supported by a selection or narrowing down of the map section or the drop-down menu. down menus. It is also possible that the user simply confirms on their mobile device that the traffic flow has been disrupted and they are still on the toll road.
  • the respective received positions contain information that is indicative of whether the received position is a start position, a via position or an end position acts.
  • the end position data can be part of a termination request
  • the via position data can be part of a status message from the mobile device or a detection message from a roadside detection device
  • the start position data can be part of an initiation request.
  • the vehicle data sent with the initiation request includes information on the registration number of the motor vehicle, the number of axles, the weight and the emission class.
  • a user ID of the respective user can be transmitted and/or a deposit of valid payment information.
  • This payment information can be stored in the toll center for a registered user and can be used accordingly when specifying the respective user ID.
  • the user if the user is not a user registered in the toll center with valid payment information stored, the user must go to Initiate the respective toll journey also deposit a valid means of payment, for example credit card information, information on a prepaid card, information on a fuel card or other payment methods that allow the toll fee to be debited after the journey has ended.
  • the toll control center after the user has properly initiated the toll journey the mobile device sends a corresponding receipt.
  • This receipt can then be used as proof that the user has properly logged the respective vehicle into the toll center and initiated the journey that is subject to the toll, and that the user is ready to pay the corresponding toll fee after completing the journey to pay the deposited means of payment.
  • the computing device is set up to check the plausibility of the start position data when a via position is received for the first time from a roadside detection device after the route-flexible toll collection method has been initiated.
  • Embodiments in which the trip is ended automatically or the user is prompted to end it are advantageous because overbookings are avoided in this way. Because if the user has failed to end the journey properly, the user can be prompted to end the journey properly by specifying his position.
  • the journey can also be ended automatically by the toll center, in which case, after the current position of the mobile device has been transferred, the exit from the traffic area subject to toll that is closest to this current position is evaluated as the exit from the traffic area subject to toll.
  • the toll center determines a route for the vehicle that is subject to the toll, which results from the position specified when initiating the journey that is subject to the toll and the position that is the closest exit from the traffic area that is subject to the toll, taking into account the position between the entrance and the exit, if necessary lying via positions, which allow the route to be adjusted accordingly, deviating from the assumed shortest route.
  • the route determined in this way is preferably displayed to the user again for confirmation, and the corresponding debiting of the toll is then initiated by the toll center.
  • Another aspect of the invention relates to a mobile device according to claim 9.
  • a mobile device preferably a mobile phone or smartphone, is proposed for use in collecting a toll for a vehicle that is subject to the toll, the mobile device having a mobile communication device and a mobile computing device which is communicatively coupled to the mobile communication device.
  • the mobile computing device is set up to send an initiation request for initiating use of the traffic area that is subject to toll by the vehicle that is subject to toll via the mobile communication device to a toll center, preferably to a toll center as described above, in order to thereby initiate a toll collection method and the mobile computing device is set up to send a termination request for ending the toll collection process using the mobile communication device to the toll center, thereby ending the toll collection process.
  • a mobile device in this sense does not require the device to be a portable device. It can also be permanently installed in a vehicle, for example. According to a preferred embodiment, however, the mobile device is a portable mobile device. For example, it is then a mobile phone or smartphone or a tablet computer, the computing device of which is set up accordingly by a computer product, for example an app, loaded into an internal memory of the computing device.
  • the initiated toll collection method is a manual toll collection method, in which the route selection is not specified with the initiation as in the previously known manual toll collection method, but is flexible. Therefore, it is also referred to herein as a route-flexible manual toll collection method. That is, the user can choose any route.
  • the user can complete the booking with the toll collection system by using his mobile device to transmit end position data to the toll collection system in order to end his journey that is subject to toll.
  • the mobile computing device is set up to determine the starting position data of the mobile device and to send the starting position data to the toll center as part of the initiation request using the mobile communication device, and the mobile computing device is set up to determine the end position data of the mobile device and to send the end position data as part of the termination request the mobile To send communication device to the toll station.
  • the mobile device preferably has a position determination device or is connected to one. The mobile computing device is then set up to determine the starting position data using the position determination device. This is advantageous because no input is required from the user or external devices.
  • the position can be determined, for example, using a GPS receiver and/or using an evaluation of neighboring WLAN and/or mobile radio cells.
  • the mobile computing device is set up to determine end position data of the mobile device and to send the end position data to the toll center as part of the end request using the mobile communication device.
  • the user can also be given the option of manually specifying his position via a user interface of the mobile device.
  • the user can, for example, mark his current position on a road map provided on the user interface or select the respective driveway from a drop-down menu.
  • the mobile device can support the user in making this selection by displaying a specific map section of the road map based on a provisional position determined using a position determination device, or by restricting the drop-down menu accordingly.
  • the mobile device has a user interface that is suitable for displaying interface elements and for receiving user inputs relating to at least one of the displayed interface elements.
  • a user interface can be, for example, a touch screen or a combination of screen or LED display and input means, such as input keys, scroll wheel, joystick, touch pad, speech recognition or mouse.
  • a destination selection option that is shown is either an already specifically predefined end position or one or more input fields, which can also be displayed consecutively, in which or in which a user can enter end position data manually.
  • the mobile computing device is preferably set up to receive a status request from the toll center via the mobile communication device and, in response to the receipt of the status request, to determine via position data of the mobile device, to generate a status report based on the via position and to transmit the status report using the to send mobile communication device to the toll center.
  • the mobile computing device is set up to determine the start position data from the start user input.
  • the computing device is set up to receive a via user input via the user interface and to determine the via position data from the via user input.
  • the mobile computing device is set up to receive an end user input via the user interface and to determine the end position data from the end user input.
  • the mobile device can independently and in the background transmit the corresponding final position data to the toll center, or it can be left to the user to specify the corresponding final position, for example with support from the mobile device, in which only a selection of possible departures or a selected map section of the road map is displayed depending on the position determined in the mobile device.
  • the mobile computing device is set up to perform the following steps in response to a predetermined event after the initiation of the toll collection method: determining a via position of the mobile device, generating a status message based on the via position, and transmitting the Status report to the toll collection system using the communication device.
  • the status report is transmitted before the initiated toll collection method has ended.
  • the mobile computing device is set up to receive a status request from the toll collection system via the communication device.
  • the predetermined event is the receipt of a status request from the toll collection system.
  • the mobile computing device of the mobile device is particularly preferably set up to receive a status request from the toll collection system via the communication device and, in response to the receipt of the status request, to transmit via position data of the mobile device determine to generate a status report based on the via position and to transmit the status report to the toll collection system by means of the communication device.
  • the toll collection system can query the position of the mobile device and thus of the vehicle if a specific event requires this. For example, if an expected travel time between two roadside detection devices is exceeded.
  • the mobile device has at least one measuring device (i.e. at least one sensor) for determining at least one physical parameter, which is communicatively coupled to the mobile computing device; the mobile computing device is set up to monitor the at least one physical parameter and to generate the predetermined event if the at least one physical parameter meets a predetermined condition.
  • at least one measuring device i.e. at least one sensor
  • the computing device monitors at least one physical parameter.
  • the at least one physical parameter preferably relates to the mobile device.
  • it can be the location or the speed of the mobile device.
  • it has at least one measuring device that is suitable for determining at least one physical parameter. If the mobile computing device determines that the at least one physical parameter satisfies a predetermined condition, then it triggers the predetermined event, which means that the position data of the mobile device are determined and transmitted to the toll center.
  • the predetermined condition can involve leaving the traffic area that is subject to the toll. This can be determined, for example, based on the location of the mobile device.
  • the speed of the mobile device can also be indicative of this.
  • the predetermined condition can also be the determination of a special traffic situation, for example a traffic jam, or stopping at a rest stop. For this purpose, the speed and, if necessary, the speed of the communication device can be used for the determination.
  • the object specified above is achieved by a method for collecting a toll from a vehicle that is subject to toll when using a traffic area that is subject to toll, this having the provision of a mobile device which has a mobile communication device and a mobile computing device which is communicatively coupled to the mobile communication device .
  • the mobile computing device sends an initiation request to initiate use of the toll traffic area the vehicle subject to the toll to a toll center via the mobile communication device in order to thereby initiate a toll collection procedure and the mobile computing device sends a termination request to end the toll collection procedure by means of the mobile communication device to the toll center in order to thereby terminate the toll collection procedure.
  • a method for collecting a toll from a vehicle that is subject to toll when using a traffic area that is subject to toll comprising the provision of a toll control center that has a central communication device and a central computing device that is communicatively coupled to the central communication device.
  • the central computing device receives an initiation request for initiating use of the toll traffic area by the toll vehicle from a mobile device via the central communication device and initiates a toll collection process in response to receipt of the initiation request, and the central computing device receives a termination request from the mobile device via the central Communication device and terminates the initiated toll collection process in response to the received termination request.
  • the methods can advantageously be further developed in accordance with the previously described, procedurally designed features of the toll control center, the mobile device and the toll collection system.
  • the methods and functions carried out by a mobile device and/or by a toll center when software code sections of one of the two computer program products are loaded in the respective internal memory of the respective computing device and are executed by the respective computing device have already been described above.
  • the computer program product itself can be a computer-readable non-transitory storage medium, for example a DVD, a CD-ROM, a flash disk or a hard disk.
  • At least one preferred exemplary embodiment of (1.) the toll collection system and (2.) the mobile device is described below. Within the scope of the description of these two products, preferred embodiments of the methods are also used describe. It closes with a description of preferred embodiments (3.) of the two computer program products.
  • Toll center 100 initially includes a central computing device 101.
  • An exemplary central computing device 101 is shown as a block diagram in figure 1 shown. Instructions, for example in the form of software code sections, are executed in this central computing device 101, so that the computing device performs one or more of the methods and functions described herein.
  • the central computing device 101 can only comprise a single computer. However, it can also be a distributed system . According to one embodiment, the central computing device 101 is a single, preferably physically separate, computer. In another embodiment, this is a distributed system, ie, multiple independent computers that 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 of the computing device then work autonomously but are functionally coordinated with one another.
  • the exemplary central processing facility 101 includes a central processor 102 (e.g., a CPU, a GPU, or both) with internal memory, a central main memory 104 and a central static memory 106 communicatively coupled to one another via a bus 108 .
  • the central computing device 101 can also be communicatively coupled to a user interface.
  • This user interface can have a display unit 110 (for example a flat screen or the like) and a first input unit 112 (for example 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 114 (e.g.
  • the user interface may include the display unit 114 and the input unit(s) in an integrated device such as a touch screen.
  • the central computing device 101 also has a central storage device 116, a signal generation device 118 and a central communication device 120, which are communicatively connected to one another via the bus 108.
  • the central storage device 116 includes a machine-readable medium 122 on which is stored portions of software code and data (e.g., instructions 124) required for the methods and functions of the computing device described herein.
  • the instructions 124 can also be loaded, at least in part, into the main memory 104 and/or into the internal memory of the processor 102, with the main memory 104 and the internal memory of the processor 102 also being machine-readable media acts.
  • the instructions 124 can also be transmitted or received via a network 126 by means of the central communication device 120, using one of the numerous known transmission protocols (e.g. HTTP).
  • HTTP HyperText Transfer Protocol
  • machine-readable medium 122 (which is preferably non-transitory) is a single medium in an exemplary embodiment, the term “machine-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 in the form of software code sections 124.
  • the term “machine-readable medium” also includes any medium capable of storing, encoding, or carrying instructions 124 . This can be a solid state memory, an optical or a magnetic memory.
  • Exemplary embodiments of the central processing facility 101 may be implemented in digital circuitry, or in computer hardware, firmware, software, or combinations thereof.
  • the figure 2 shows a schematic overview of the entire toll system 1000, which includes, among other things, the toll center 100, a mobile device 200 and preferably also at least one roadside detection device 130.
  • the toll center 100 is set up for use in a route-flexible manually initiated toll collection method. As already explained, it has the central computing device 101 and the central communication device 120 which are communicatively coupled to the central computing device 101 .
  • the central computing device 101 is set up to receive an initiation request for initiating toll use of the toll traffic area from a mobile device 200 via the central communication device 120 and to initiate a toll collection method in response to the receipt of the initiation request.
  • the initiation request received from the mobile device 200 may contain starting position data, an indication of a means of payment, an indication of a registration and/or toll-specific vehicle data.
  • the starting position data determine the position on the toll traffic area at which the vehicle begins the toll journey or at which it arrives at the toll traffic area.
  • a means of payment must be deposited at least if the user or the vehicle is not already registered in the toll center 100 with a means of payment deposited.
  • the means of payment is used in the toll control center 100 to debit the costs incurred during the journey that is subject to the toll.
  • the toll-specific vehicle data includes, for example, the vehicle registration number, the vehicle weight, the number of axles and the vehicle's emission class, so that the toll due can be calculated on this basis.
  • the receipt of the starting position data and the toll-specific vehicle data can already be interpreted by the central computing device 101 as an initiation request, so that the central computing device 101 then initiates the toll collection process in response to the receipt of the data.
  • the toll collection method then initiated is a manual toll collection method in which the choice of route is not specified with the initiation as in the previously known manual toll collection method, but can be handled flexibly. Therefore, it is also referred to herein as a route-flexible manual toll collection method.
  • the triggering of the sending of the initiation request from the mobile device 200 to the toll center 100 for initiating the toll collection method thus requires an active operation of the mobile device 200 by the User. This is understood here as a manual initiation of the toll collection method.
  • the vehicle or the user can then choose any route along the toll road and is not tied to a pre-booked route.
  • the user also terminates the toll collection method that was initiated manually in this way by actively operating the mobile device 200 after completing the journey that is subject to the toll, so that the booking in the toll center 100 can be completed as a result.
  • the user terminates the toll journey with his mobile device 200 by sending a termination request to the toll center 100.
  • the termination request can preferably also include the transmission of the current end position data, which corresponds to the position on the toll traffic area at which the journey ended or at which the toll road is left.
  • the central computing device 101 is set up to receive end position data of the mobile device 200 from the mobile device 200 via the central communication device 120 with the termination request and to terminate the initiated toll collection method in response to the received termination request.
  • the route used by the vehicle that is subject to the toll on the traffic area that is subject to the toll is then calculated in the central computing device 101 on the basis of the transmitted start position data and the transmitted end position data, and the toll due is calculated on this basis in conjunction with the toll-relevant data and debited from the stored means of payment.
  • All positions received by the central computing device 101 via its central communication device 120 can contain information which is indicative of whether the respective received position is a start position, a via position or an end position. This can be solved in that the end position data is part of a termination request from the mobile device 200 and the start position data is part of an initiation request from the mobile device 200 .
  • a via position is either part of a status message from the mobile device 200 or a detection message from a roadside detection device 130.
  • a vehicle 300 can use a traffic area that is subject to toll without the user has to book the intended route firmly before the journey and without a vehicle-side detection device, in particular an on-board unit (OBU), having to be provided in the respective vehicle 300 .
  • OBU on-board unit
  • vehicles that are subject to toll can use traffic areas that are subject to toll in a correspondingly simple manner, without the need for any special equipment in the vehicle that is subject to toll.
  • Mobile devices 200 such as cell phones or smartphones, are widespread today and are usually carried by the users of vehicles 300 that are subject to tolls. In this way, it is also possible for vehicles 300 that are not specially equipped with an OBU to use traffic areas that are subject to tolls without being considered toll dodgers.
  • the proposed method in which the user can use the mobile device 200 to initiate the use of the toll traffic area or the toll journey as desired, and only at the end of the journey is the actual booking made by ending the journey initiated by the user the user can flexibly follow the route he desires.
  • the actually on the toll The route taken in the traffic area is then determined by the toll control center 100 only after the journey has ended.
  • the central computing device 101 of the toll collection system 100 is set up to determine a route of the vehicle 300 that is subject to the toll between the starting position and the end position. This has the advantage that the central computing device 101 calculates the toll on the basis of the previously determined route.
  • the central computing device 101 of the toll control center 100 is set up to determine the best route between the starting position and the end position according to at least one predetermined criterion using the traffic areas subject to toll.
  • the predetermined criterion can be that that route is assumed to be the best, the use of which usually requires the least time or which results in the shortest route on the traffic area that is subject to tolls.
  • the central computing device 101 is set up to determine a toll on the basis of the calculated route.
  • the further toll-relevant data sent when the mobile device 200 was initiated are taken into account, which are transmitted when the manually initiated toll collection method is initiated.
  • the toll-relevant data include, for example, data from a registration of the user, the registration number 302 of the motor vehicle 300, the number of axles, the weight of the vehicle 300 and/or its emission class.
  • Payment information is stored in the toll center 100 associated with a registered user. However, if the user is not a user registered in the toll center 100 with valid payment information stored, the user must also store a valid means of payment to initiate the respective toll journey, for example credit card information, information about a prepaid card, information about a fuel card or other payment methods that allow the toll to be debited after the journey has ended.
  • a valid means of payment for example credit card information, information about a prepaid card, information about a fuel card or other payment methods that allow the toll to be debited after the journey has ended.
  • the central computing device 101 is set up to receive at least via position data of the vehicle 300 that is subject to the toll from a roadside detection device 130 via the central communication device 120 .
  • the passage of the toll vehicle 300 on the basis of the in the identifier 302 stored in the toll center 100 can be determined. Due to the manual initiation of the toll collection method by means of the mobile device 200, the toll control center 100 executes the toll collection method for this motor vehicle and is informed accordingly that the vehicle 300 that is subject to the toll is driving on a route section that is subject to the toll. In order to enable the vehicle 300 that is subject to the toll to be identified by the detection devices 130 on the road, the identifier 302 of the vehicle 300 that is subject to the toll, for which the toll collection method was initiated manually via the mobile device 200 , is stored in the toll control center 100 .
  • the vehicle 300 that is subject to the toll is therefore detected at the respective known positions of the roadside detection devices 130 in the form of the stationary or mobile control devices and the respective detection data are transmitted to the toll center 100 as Via position data via the existing or a separate communication network.
  • the respective registration data recorded by the roadside recording devices 130 are assigned to the respective vehicles 300 that are subject to the toll on the basis of the license plates 302 determined.
  • the toll center 100 knows the position and direction of travel of a toll vehicle 300 for which the toll collection method was manually initiated via the mobile device 200 via the evaluation of the detection data at the time of detection. This position and driving direction is stored in the toll control center 100 as the via position of the respective vehicle 300 that is subject to the toll.
  • the central computing device 101 of the toll control center 100 is accordingly set up to take into account the via position data received when determining the route. Accordingly, in a case in which the vehicle 300 subject to the toll is detected by at least one roadside detection device 130 after initiating the toll collection process and the position corresponding to the roadside detection devices 130 is transmitted to the toll center 100, the toll center 100 determines the best route of the vehicle 300 that is subject to the toll the starting position, the ending position and the at least one between the Start position and the end position lying via position of the roadside detection device 130. To determine the best route, the transmission and consideration of via positions is not absolutely necessary - the start position and the end position can be sufficient for this.
  • the toll control center 100 sends a corresponding document after the correct manual initiation of the journey that is subject to the toll the mobile device 200 transmits.
  • This receipt serves as proof that the user has properly logged the respective vehicle 300 into the toll control center 100 and correspondingly initiated the toll collection method for this journey of the vehicle 300 that is subject to toll.
  • the receipt is proof that the user is willing and able to pay the corresponding toll fee using the stored means of payment after completing the journey.
  • the toll center 100 can send a request to transmit the current position to the mobile device 200 .
  • the toll center 100 When determining a period of time after which the vehicle 300 subject to the toll is expected to be at the next detection device 130 on the road to be reached, the toll center 100 preferably proceeds from an average speed stored in the toll center 100 for the respective route sections, which the vehicle 300 subject to the toll is between two roadside detection devices 130 is expected to be passed through.
  • the duration can be provided with a safety margin, for example a percentage (e.g. 10% time allowance) or an absolute (e.g. 20 minutes) safety margin.
  • a safety margin for example a percentage (e.g. 10% time allowance) or an absolute (e.g. 20 minutes) safety margin.
  • Toll center 100 correspondingly calculates the length of time, for example, from the starting position to the next roadside detection device 130, or between two roadside detection devices 130 that follow one another in the direction of travel, after which it is expected that the respective subsequent roadside detection device 130 will detect vehicle 300 that is subject to the toll. If this detection does not take place, this can have various causes: Either the originally specified position of the vehicle 300 that is subject to the toll was not correct. If this is the case, then the respective motor vehicle 300 is released for suspicion by the respective authorities, for example, since there could be an attempt at fraud here.
  • the central computing device 101 is set up to check the plausibility of the specification of the start position data when it receives a via position from a roadside detection device 130 for the first time after the toll collection method has been initiated.
  • the start and via position data received from the toll center 100 are each associated with a time stamp, and the central computing device 101 of the toll collection system 100 and/or the mobile device 200 are/is set up to provide each received position with a time stamp.
  • the central computing device 101 is also set up to check the plausibility of the specification of the starting position data using the following steps: determining an actual duration of the journey based on the received starting position data and the via position received from the roadside detection device 130 . Also calculating an expected time difference between the start position and the end position based on the known track length. If the actual length of time is within or near the expected time difference, then the start position data is assumed to be correct. If the actual length of time is outside the expected time difference, then the starting position data is assumed to be incorrect. When determining the expected time difference, the central computing device 101 takes into account an assumed or empirical maximum and minimum average speed on the route length between the starting position and the via position as well as any existing traffic disruptions, such as traffic jams or construction sites, which can reduce the average speed.
  • the central computing device 101 of the toll center 100 is also set up to send a status request to the mobile device 200 in response to a predetermined event and to receive a status message from the mobile device 200 via the central communication device 120 .
  • This status message includes a via position determined by the mobile device 200 .
  • Such a predetermined event for sending a status request occurs, for example, if the vehicle 300 that is subject to the toll, due to the existing traffic conditions, for example a traffic jam or a blocking of the respective traffic area, has an expected time difference between the two known positions (between the starting position and the position of the roadside detection device or between the positions of two roadside detection devices) cannot reach, but takes longer.
  • Such an event is also present if the vehicle 300 that is subject to the toll has meanwhile left the traffic area that is subject to the toll and, accordingly, can no longer be detected by the detection devices 130 on the road, and the user has failed to properly terminate the journey by transmitting a termination request from the mobile device 200 to the toll center 100 .
  • the central computing device 101 is set up to monitor the movement of the mobile device 200 after the manual initiation and before the end of the initiated toll collection method, the monitoring comprising the following steps: determining at least one next possible roadside detection device 130 based on the last received position (start - or via position) of the mobile device 200, determining the expected time difference after which the mobile device 200 can be expected at the next possible roadside detection device 130, sending a status request to the mobile device 200 via the central communication device 120 after the expected time difference has expired, if the central computing device 101 has up to this point in time still received via position data of the vehicle 300 that is subject to the toll from the next possible roadside detection device 130, and receiving a status message from the mobile device 200 via the K communication device 120.
  • the monitoring may include the following steps: determining at least one closest possible roadside sensing device 130 based on the last received position (start or via position) of the mobile device 200, determining the expected one Time difference after which the mobile device 200 is to be expected at the next possible roadside detection device 130, sending a status request to the mobile device 200 via the central communication device 120, the status request being designed in such a way that the mobile device 200 is instructed to delay via position data by the to send the expected time difference to the toll center 100, if the central computing device 101 has received Via position data of the vehicle 300 from a roadside detection device 130 by the end of the expected time difference, send a cancellation message to cancel the sent status request.
  • the user of the vehicle with the mobile device 200 may be able to select multiple routes starting from the last determined position, for example at a freeway junction or a freeway exit. Then all those detection devices 130 are closest possible detection devices 130 that the mobile device 200 (in a vehicle) can reach on the toll road without having to pass another on-road detection device 130 beforehand.
  • a status request is sent from the toll control center 100 to the mobile device 200 if the next possible roadside detection devices 130 fail to detect the vehicle 300 subject to the toll when the expected time difference has elapsed and thus also the receipt of a via position from a roadside detection device 130 is absent.
  • the expected time difference is determined taking into account the distance between the ascertained roadside detection device 130 and the last received position of the mobile device 200 and a stored average speed as well as a possible safety margin.
  • the Mobile device 200 prompted to transmit a current position to the toll center 100.
  • the mobile phone 200 automatically transmits its current position to the toll center 100 after receiving the status request, with this position again, for example, in the Mobile device 200 can be determined by a position determination device, which makes use of a GPS system and/or the evaluation of the nearest WLAN and/or GSM radio cells.
  • the central computing device 101 is also set up to adapt the minimum average speed, on which the central computing device 101 bases the determination of the expected time difference, on the basis of current traffic information.
  • the central computing device 101 receives traffic information via the central communication device 120, for example as part of the detection messages transmitted by roadside detection devices 130.
  • the toll control center 100 accordingly knows that there is a traffic disruption in a specific section of a toll traffic area, the expected time differences are adjusted accordingly. In this way, the request for current position data from the toll center 100 to the mobile device 200 can be reduced to cases when such information about traffic disruptions is not available in the toll center 100, or it is not accurate when the starting position data, which the user of the respective toll payer vehicle when initiating the toll journey was incorrect, or if the user forgot to properly end the toll journey.
  • the central computing device 101 of the toll control center 100 is set up to determine whether the via position received as part of the status message is within the traffic area that is subject to the toll. If the answer is that the position of the via is within the traffic area subject to the toll, the initiated toll collection method is continued and preferably a (minimum) average speed stored in a memory of the toll collection system 100 that is communicatively coupled to the central computing device 101 is adjusted on the corresponding route section.
  • the central computing device 101 of the toll collection system 100 is also set up to determine whether the via position received as part of the status message is outside the toll traffic area, and in response to the determination that the via position is outside the toll traffic area, the initiated toll collection method then exit automatically.
  • This automatic termination of the initiated toll collection procedure can replace a termination request received from the mobile device 200 .
  • Terminating the initiated toll collection process in response to determining that the via location is outside the toll zone may also include sending a request to the mobile device 200 to send a termination request. Accordingly, if the user has failed to properly end the ride, the user will be prompted to properly end the ride by sending a termination request indicating his/her position. If the user terminates the journey, the toll control center 100 then determines a route for the vehicle that is subject to the toll, which results from the start position data specified when initiating the journey that is subject to the toll and the end position data that is closest to the current position sent with the termination request from the traffic area that is subject to the toll. This end position is determined, if necessary, taking into account the via positions between the driveway and the exit, which accordingly require an adjustment of the route.
  • the route determined in this way can be sent to the user again for confirmation from the toll center 100 to the mobile device 200 and displayed on it, in order to then be authorized by the user.
  • the calculation of the toll due and the corresponding debiting of the toll then take place in the central computing device 101 .
  • the central computing device 101 is also set up to determine whether the via position received as part of the status message is outside the toll traffic area and, in response to the determination that the via position is within the toll traffic area, to continue the initiated toll collection method and to adapt the (minimum) average speed stored in a memory of the toll collection system 100 that is communicatively coupled to the central computing device 101 on the corresponding route section.
  • the central computing device 101 is also set up to use the last used or determined end position data as start position data when initiating the subsequent journey.
  • the central computing device 101 of the toll collection system 100 is set up to acknowledge receipt of the start position data and/or the end position data.
  • the toll center 100 can send a receipt to the mobile device 200 after initiating the manual toll collection process and receiving the relevant data.
  • the central computing device 101 is set up to transmit an acknowledgment to the mobile device 200 in response to the receipt of the starting position data and/or in response to the receipt of a status message.
  • This receipt can be in the form of a machine-readable code, in particular a QR code. The code can advantageously be checked for authenticity by a control device.
  • a preferred embodiment of a mobile device 200 is described below.
  • This is a portable mobile device, for example a mobile phone or smartphone, whose mobile computing device 201 is set up by software code sections of a computer product, for example an app, loaded into an internal memory of the mobile computing device 201 .
  • the mobile computing device 201 can in principle be a general computing device, as has already been described with regard to the central computing device 101 of the toll control center 100 . Reference is therefore made to the top with regard to the general statements on the design of a computing device.
  • a preferred embodiment of the mobile computing device 201 of the mobile device is described below.
  • the mobile device 200 includes, among other things, a mobile computing device 201 with a mobile processor 202, a plurality of different mobile data memories 204, 216, 222, a power supply 214, and a user interface 210 in the form of a touchscreen display 215, on which the mobile processor 202 data can be displayed.
  • Mobile processor 202 is also equipped with a clock 240, a mobile communication device 220 in the form of a mobile radio transceiver, which has a corresponding mobile radio antenna 221, and a position determination device 230, which has a GNSS receiver 232 communicatively coupled to a GNSS receiving antenna 234 , communicatively coupled.
  • a first mobile data memory 222 is a read-only memory, for example a ROM, EEPROM or FLASHMEMORY, and is used to store a computer program product.
  • the toll software can be transmitted to the mobile data memory 222 via appropriate communication interfaces.
  • the mobile data memory 204 is a main memory that is communicatively connected to the mobile processor 202 in the form of a read/write memory, for example RAM, and is used to temporarily record at least parts of the toll software during the operation of the mobile device 200.
  • the mobile processor 202 loads during the Starting phase of the mobile device 200 from the mobile data memory 222 the corresponding toll software in the mobile main memory 204.
  • the read-write memory 212 is also used to record position data, which are received by the mobile processor 202 from the position determination device 230 and are processed in the mobile processor 202.
  • Another mobile data memory 216 is provided as a cryptographic memory, for example as ROM, EEPROM or RAM, and can be provided in a security module with its own processor, and is used to record booking data records of usage authorizations for using upcoming motorway sections.
  • the mobile device 200 can communicate with the toll center 100 described above via the mobile radio transceiver 220 .
  • the mobile radio antenna 221 and the GNNS receiving antenna 234 can also be provided as externally arranged antennas.
  • a computer program product can be loaded from the mobile data memory 222 into a mobile main memory 204 and an internal memory of the processor 202 . Then, when the product runs on the mobile computing device 201, the mobile computing device 201 is configured to perform the methods and functions outlined below: First, the mobile computing device 201 of the mobile device 200 is set up to initiate the toll collection method by sending an initiation request to the toll center 100 . A position of the mobile device 200 is preferably determined and transmitted to the toll center 100 as start position data together with the initiation request. The mobile computing device 201 is set up not only for determining the starting position data by means of the position determination device 230, but also to carry out the determination of via and end positions in this way. The positioning is a GNSS positioning device that determines the position of the mobile device 200 via signals from GNSS satellites 500 .
  • the mobile device 200 can automatically determine this starting position data.
  • the starting position data can also be specified or selected by the user in that the user is shown 200 possible starting positions from which he can select on the user interface of the mobile device 200 .
  • the selection can be made, for example, via a dropdown menu or the display of a map, with the mobile device 200 preferably making a preselection of the possible starting positions on the basis of the current position determined by the mobile device 200 .
  • Typical selectable starting positions are the ramps of toll route sections of a motorway network.
  • the initiated toll collection method is a manual toll collection method in which the choice of route is not rigidly specified upon initiation, but rather is flexible. That is, the user can select any route from the starting position while driving. After completing the journey that is subject to toll, the user completes the booking at the toll center 100 by using his mobile device 200 to transmit a termination request to the toll center 100 .
  • the initiation of the manual toll collection method can also include: transmitting data to identify the user, for example payment information, user registration data, the registration number 302 of the motor vehicle 300 that is subject to the toll, as well as toll-relevant data, for example the number of axles and/or the weight of the vehicle.
  • the payment information is stored in the toll center 100, for example associated with a registered user. However, if the user is not a user registered in the toll center 100 with valid payment information stored, the user must also store a valid means of payment to initiate the respective toll journey, for example credit card information, information about a prepaid card, information about a fuel card or other payment methods that allow the toll to be debited after the journey has ended.
  • Mobile computing device 201 of mobile device 200 is also set up to receive a first user input via user interface 210 and to initiate the manual toll collection method in response to the first user input by transmitting the initiation request to toll center 100 .
  • the mobile computing device 201 of the mobile device 200 is also set up to end the initiated toll collection method, the ending comprising: determining end position data of the mobile device 200 and transmitting the end position data together with a termination request to the toll center 100 by means of the mobile communication device 220.
  • the ending position data can also be selected from a drop-down menu or a map display. Typical end positions that can be selected are the exits from toll route sections of a motorway network.
  • the mobile computing device 201 of the mobile device 200 is set up to carry out the following steps in response to a predetermined event after the initiation and before the end of the toll collection method: determining a via position of the mobile device 200, generating a status message based on the via position in Response to a status request received from the toll center 100 and transmission of the status message to the toll center 100 by means of the mobile communication device 220.
  • the mobile computing device 201 of the mobile device 200 is set up to receive a status request from the toll center 100 via the central communication device 120 .
  • the computer program product itself can be a computer-readable non-transitory Are storage medium, for example, a DVD, a CD-ROM, a flash disk or a hard drive. It is preferably a DVD.

Landscapes

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

Claims (10)

  1. Centrale de péage (100) pour le prélèvement d'un péage d'un véhicule soumis au péage lors de l'utilisation d'une zone de circulation soumise au péage, comprenant un dispositif de calcul central (101) et au moins un dispositif de communication central (120), lequel est couplé de manière communicative avec le dispositif de calcul central (101), dans laquelle le dispositif de calcul central (101) est configuré pour recevoir d'un appareil mobile (200), par l'intermédiaire du dispositif de communication central (120), une demande d'initiation pour l'initiation d'un procédé de prélèvement de péage pour l'utilisation de la zone de circulation soumise au péage par le véhicule soumis au péage (300),
    en réponse à la réception de la demande d'initiation, d'initier un procédé de prélèvement de péage, et
    en réponse à l'occurrence d'un événement de terminaison sous forme d'une demande de terminaison reçue de l'appareil mobile (200) par l'intermédiaire du dispositif de communication central (120), terminer le procédé de prélèvement de péage initié,
    caractérisée en ce que
    la demande d'initiation comprend des données de position de départ et la demande de terminaison comprend des données de position finale, dans laquelle le dispositif de calcul central (101) est configuré pour recevoir des données de position via du véhicule soumis au péage (300), lesquelles sont des données de position qui sont reçues par la centrale de péage (100) à la suite des données de position de départ respectivement soit de l'appareil mobile (200) soit d'un dispositif de détection (130) côté route et ne sont pas des données de position, qui sont déclarées au préalable comme données de position finale, et, en réponse à un événement prédéterminé, pour envoyer une demande d'état à l'appareil mobile (200) et recevoir, par l'intermédiaire du dispositif de communication central (120), un message d'état de l'appareil mobile (200), lequel comprend des données de position via de l'appareil mobile (200), dans laquelle l'événement prédéterminé comprend
    - la réception d'une demande d'initiation avec des données de position de départ de l'appareil mobile (200), et/ou
    - la réception de données de position via d'un dispositif de détection côté route (130) et/ou
    - la réception d'un message d'état avec des données de position via de l'appareil mobile (200), et/ou
    - l'écoulement d'une durée prédéterminée et/ou calculée depuis la réception de la demande d'initiation et/ou du message d'état avec les données de position via de l'appareil mobile (200) et/ou les données de position via provenant du dispositif de détection côté route (130), et
    pour déterminer un itinéraire du véhicule soumis au péage (300) sur la zone de circulation soumise au péage entre une position de départ définie par des données de position de départ et une position finale définie par des données de position finale en tenant compte des données de position via reçues et, sur la base de l'itinéraire déterminé, déterminer un péage dû et prélever le péage.
  2. Centrale de péage (100) selon la revendication 1, caractérisée en ce que le dispositif de calcul central (101) est configuré pour mettre en œuvre les étapes suivantes :
    - déterminer un dispositif de détection côté route (130) à atteindre ensuite, sur la base de données de position de départ transmises de l'appareil mobile (200) et/ou de dernières données de position via reçues d'un dispositif de détection côté route (130) ou de l'appareil mobile (200),
    - déterminer une durée attendue pendant laquelle le véhicule (300) doit être attendu au dispositif de détection côté route (130),
    - envoyer une demande d'état à l'appareil mobile (200) par l'intermédiaire du dispositif de communication central (120), et
    - recevoir un message d'état de l'appareil mobile (200) par l'intermédiaire du dispositif de communication central (120) après l'écoulement de la durée attendue, dans laquelle le message d'état comprend la position via actuelle de l'appareil mobile (200), ou
    - recevoir des données de position via d'un dispositif de détection côté route (120) avant l'expiration de la durée attendue.
  3. Centrale de péage (100) selon l'une quelconque des revendications précédentes, caractérisée en ce que le dispositif de calcul central (101) est configuré pour déterminer la distance entre les données de position de départ transmises par l'appareil mobile (200) et/ou la dernière position via reçue d'un dispositif de détection côté route (130) et/ou la dernière position via reçue de l'appareil mobile (200) en réponse à une demande d'état et la position du dispositif de détection côté route (130) à atteindre ensuite, et la durée attendue sur la base de la vitesse moyenne attendue sur cette distance, laquelle est déterminée à partir d'au moins une vitesse moyenne enregistrée dans une mémoire du dispositif de calcul central (101), de préférence en ajoutant une marge de sécurité en pourcentage ou en valeur absolue.
  4. Centrale de péage (100) selon la revendication 2 ou 3, caractérisée en ce que le dispositif de calcul central (101) est configuré pour déterminer si la position via des données de position via reçues avec le message d'état se trouve hors de la zone de circulation soumise au péage et, en réponse à la détermination que la position via se trouve hors de la zone de circulation soumise au péage, générer un événement de terminaison sous forme d'une terminaison du procédé de prélèvement de péage initié et/ou envoyer une demande d'envoi d'une demande de terminaison à l'appareil mobile (200) et, de préférence, recevoir en réponse un événement de terminaison sous forme d'une demande de terminaison de l'appareil mobile (200) par l'intermédiaire du dispositif de communication central (120), dans laquelle la demande de terminaison comprend le plus préférentiellement des données de position finale.
  5. Centrale de péage (100) selon l'une quelconque des revendications 2 à 4, caractérisée en ce que le dispositif de calcul central (101) est configuré pour déterminer si la position via des données de position via reçues avec le message d'état se trouve dans la zone de circulation soumise au péage et, en réponse à la détermination que la position via se trouve dans la zone de circulation soumise au péage, poursuivre le procédé de prélèvement de péage initié et, de préférence, adapter une vitesse moyenne enregistrée dans une mémoire du dispositif de calcul central (101) pour le tronçon de parcours en cours de visualisation.
  6. Centrale de péage (100) selon l'une quelconque des revendications précédentes, dans laquelle la demande d'initiation est une demande d'initiation manuelle et/ou la demande de terminaison est une demande de terminaison manuelle.
  7. Appareil mobile (200), de préférence téléphone mobile ou smartphone, destiné à être utilisé pour le prélèvement d'un péage pour un véhicule soumis au péage (300), dans lequel l'appareil mobile (200) comprend un dispositif de communication mobile (220) et un dispositif de calcul mobile (201), lequel est couplé de manière communicative avec le dispositif de communication mobile (220), dans lequel
    le dispositif de calcul mobile (201) est configuré pour envoyer une demande d'initiation pour l'initiation d'une utilisation de la zone de circulation soumise au péage par le véhicule soumis au péage (300) par l'intermédiaire du dispositif de communication mobile (220) à une centrale de péage (100), de préférence à une centrale de péage (100) selon l'une quelconque des revendications précédentes, pour ainsi initier un procédé de prélèvement de péage, et
    le dispositif de calcul mobile (201) est configuré pour envoyer une demande de terminaison du procédé de prélèvement de péage au moyen du dispositif de communication mobile (220) à la centrale de péage (100) pour ainsi terminer le procédé de prélèvement de péage
    caractérisée en ce que
    le dispositif de calcul mobile (201) est configuré pour déterminer des données de position de départ de l'appareil mobile (200) et pour envoyer les données de position de départ en tant que partie de la demande d'initiation au moyen du dispositif de communication mobile (220) à la centrale de péage (100) et en ce que le dispositif de calcul mobile (201) est configuré pour déterminer des données de position finale de l'appareil mobile (200) et pour envoyer les données de position finale en tant que partie de la demande de terminaison au moyen du dispositif de communication mobile (220) à la centrale de péage (100), dans lequel le dispositif de calcul mobile (201) est configuré pour recevoir une demande d'état de la centrale de péage (100) par l'intermédiaire du dispositif de communication mobile (220) et, en réponse à la réception de la demande d'état, pour déterminer des données de position via de l'appareil mobile (200), pour générer un message d'état comprenant les données de position via et pour envoyer le message d'état à la centrale de péage (100) au moyen du dispositif de communication mobile (220).
  8. Procédé de prélèvement de péage pour prélever un péage auprès d'un véhicule soumis au péage lors de l'utilisation d'une zone de circulation soumise au péage, comprenant :
    la mise à disposition d'un appareil mobile (200), lequel présente un dispositif de communication mobile (220) et un dispositif de calcul mobile (201), lequel est couplé de manière communicative au dispositif de communication mobile (220), et
    la mise à disposition d'une centrale de péage (100), laquelle présente un dispositif de communication central (120) et un dispositif de calcul central (101), qui est couplé de manière communicative au dispositif de communication mobile (120), dans lequel
    le dispositif de calcul mobile (201) envoie une demande d'initiation pour l'initiation d'une utilisation de la zone de circulation soumise au péage par le véhicule soumis au péage (300) par l'intermédiaire du dispositif de communication mobile (220) au dispositif de communication central (120) de la centrale de péage (100) et le dispositif de calcul central (101) de la centrale de péage (100) initie un procédé de prélèvement de péage en réponse à la réception de la demande d'initiation,
    et
    le dispositif de calcul mobile (201) envoie une demande de terminaison pour terminer l'utilisation de la zone de circulation soumise au péage par le véhicule soumis au péage (300) par l'intermédiaire du dispositif de communication mobile (220) au dispositif de communication central (120) de la centrale de péage (100) et le dispositif de calcul central (101) termine le procédé de prélèvement de péage initié en réponse à l'occurrence d'un événement de terminaison sous forme de la demande de terminaison reçue
    caractérisée en ce que
    le dispositif de calcul mobile (201) détermine des données de position de départ de l'appareil mobile (200) et envoie les données de position de départ en tant que partie de la demande d'initiation au moyen du dispositif de communication mobile (220) à la centrale de péage (100) et le dispositif de calcul mobile (201) détermine des données de position finale de l'appareil mobile (200) et envoie les données de position finale en tant que partie de la demande d'initiation au moyen du dispositif de communication mobile (220) à la centrale de péage (100), dans lequel le dispositif de calcul mobile (201) reçoit une demande d'état de la centrale de péage (100) par l'intermédiaire du dispositif de communication mobile (220) et détermine des données de position via de l'appareil mobile (200) en réponse à la réception de la demande d'état, génère un message d'état comprenant les données de position via et envoie le message d'état au moyen du dispositif de communication mobile (220) à la centrale de péage (100), dans lequel le dispositif de calcul central (101) détermine un itinéraire du véhicule soumis au péage (300) sur la zone de circulation soumise au péage entre une position de départ définie par des données de position de départ et une position finale définie par des données de position finale en tenant compte des données de position via reçues et détermine un péage dû sur la base de l'itinéraire déterminé et prélève le péage.
  9. Programme informatique, lequel comprend des sections de code logiciel, qui peuvent être chargées dans une mémoire interne d'un dispositif de calcul mobile (201) d'un appareil mobile (200), lequel est couplé de manière communicative à un dispositif de communication mobile (220) et qui, lorsqu'elles sont exécutées par le dispositif de calcul mobile (201), amènent le dispositif de calcul mobile (201) à mettre en œuvre les étapes suivantes :
    envoyer une demande d'initiation pour initier une utilisation d'une zone de circulation soumise au péage par un véhicule soumis au péage (300) par l'intermédiaire du dispositif de communication mobile (220) à une centrale de péage (100) pour ainsi initier un procédé de prélèvement de péage, et
    envoyer une demande de terminaison pour terminer le procédé de prélèvement de péage initié par l'intermédiaire du dispositif de communication mobile (220), à la centrale de péage (100), pour ainsi terminer le procédé de prélèvement de péage,
    caractérisé par les étapes consistant à :
    déterminer des données de position de départ de l'appareil mobile (200) et envoyer les données de position de départ en tant que partie de la demande d'initiation au moyen du dispositif de communication mobile (220) à la centrale de péage (100) ;
    déterminer des données de position finale de l'appareil mobile (200) et envoyer les données de position finale en tant que partie de la demande de terminaison au moyen du dispositif de communication mobile (220) à la centrale de péage (100) ;
    recevoir une demande d'état de la centrale de péage (100) au moyen du dispositif de communication mobile (220) ;
    déterminer des données de position via de l'appareil mobile (200), générer un message d'état comprenant les données de position via au moyen du dispositif de calcul mobile (201) et envoyer le message d'état au moyen du dispositif de communication mobile (220) à la centrale de péage (100), en réponse à la réception de la demande d'état.
  10. Programme informatique, lequel comprend des sections de code logiciel, qui peuvent être chargées dans une mémoire interne d'un dispositif de calcul central (101) d'une centrale de péage (100), lequel est couplé de manière communicative à un dispositif de communication mobile et qui, lorsqu'elles sont exécutées par le dispositif de calcul central (101), amènent le dispositif de calcul central (101) à mettre en œuvre les étapes suivantes : recevoir une demande d'initiation pour initier une utilisation d'une zone de circulation soumise au péage par un véhicule soumis au péage (300) d'un appareil mobile (200) par l'intermédiaire du dispositif de communication central (120) pour initier un procédé de prélèvement de péage en réponse à la réception de la demande d'initiation, et recevoir une demande de terminaison d'un appareil mobile (200) par l'intermédiaire du dispositif de communication central (120) pour terminer le procédé de prélèvement de péage initié en réponse à l'occurrence d'un événement de terminaison sous forme de la demande de terminaison,
    caractérisée en ce que
    la demande d'initiation comprend des données de position de départ et la demande de terminaison comprend des données de position finale, et dans lequel le dispositif de calcul central (101) est en outre amené à mettre en œuvre les étapes suivantes :
    recevoir, par l'intermédiaire du dispositif central de communication (120), des données de position via du véhicule soumis au péage (300), lesquelles sont des données de position reçues par la centrale de péage (100) à la suite des données de position de départ respectivement soit de l'appareil mobile (200) soit d'un dispositif de détection côté route (130) et ne sont pas des données de position, qui sont déclarées au préalable comme données de position finale ; envoyer une demande d'état à l'appareil mobile (200) par l'intermédiaire du dispositif de communication central (120) et en réponse à un événement prédéterminé ;
    recevoir un message d'état de l'appareil mobile (200), lequel comprend des données de position via de l'appareil mobile (200) par l'intermédiaire du dispositif de communication central (120), dans lequel l'événement prédéterminé comprend
    - la réception d'une demande d'initiation avec des données de position de départ de l'appareil mobile (200), et/ou
    - la réception de données de position via d'un dispositif de détection côté route (130) et/ou
    - la réception d'un message d'état avec des données de position via de l'appareil mobile (200), et/ou
    - l'écoulement d'une durée prédéterminée et/ou calculée depuis la réception de la demande d'initiation et/ou du message d'état avec les données de position via de l'appareil mobile (200) et/ou les données de position via provenant du dispositif de détection côté route (130), et
    la détermination d'un itinéraire du véhicule soumis au péage (300) sur la zone de circulation soumise au péage entre une position de départ définie par des données de position de départ et une position finale définie par des données de position finale en tenant compte des données de position via reçues et
    la détermination d'un péage dû sur la base de l'itinéraire déterminé et le prélèvement du péage.
EP14187568.2A 2014-10-02 2014-10-02 Centrale d'encaissement de péage, appareil mobile et procédé d'encaissement d'un péage Active EP3002733B1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP14187568.2A EP3002733B1 (fr) 2014-10-02 2014-10-02 Centrale d'encaissement de péage, appareil mobile et procédé d'encaissement d'un péage
PL14187568.2T PL3002733T3 (pl) 2014-10-02 2014-10-02 Centrala do pobierania opłaty drogowej, urządzenie mobilne i sposób pobierania opłaty drogowej

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
EP14187568.2A EP3002733B1 (fr) 2014-10-02 2014-10-02 Centrale d'encaissement de péage, appareil mobile et procédé d'encaissement d'un péage

Publications (2)

Publication Number Publication Date
EP3002733A1 EP3002733A1 (fr) 2016-04-06
EP3002733B1 true EP3002733B1 (fr) 2022-06-08

Family

ID=51628072

Family Applications (1)

Application Number Title Priority Date Filing Date
EP14187568.2A Active EP3002733B1 (fr) 2014-10-02 2014-10-02 Centrale d'encaissement de péage, appareil mobile et procédé d'encaissement d'un péage

Country Status (2)

Country Link
EP (1) EP3002733B1 (fr)
PL (1) PL3002733T3 (fr)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
ES2826897T3 (es) 2017-08-25 2021-05-19 Kapsch Trafficcom Ag Método de vigilancia de un sistema de peaje
DE102018130873A1 (de) * 2018-12-04 2020-06-04 Bayerische Motoren Werke Aktiengesellschaft Erhebung von fahrzeugspezifischen Mautgebühren für ein Kraftfahrzeug
CN111599168B (zh) * 2020-04-01 2021-12-21 广东中科臻恒信息技术有限公司 基于路侧单元的道路交通信息采集方法、设备、存储介质
EP4163885A1 (fr) 2021-10-08 2023-04-12 Toll Collect GmbH Système et procédé de prélèvement du péage pour un véhicule automobile
DE202021106013U1 (de) 2021-10-08 2022-01-19 Toll Collect Gmbh System zur Mauterhebung für ein Kraftfahrzeug

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6744383B1 (en) * 2000-02-01 2004-06-01 At&T Wireless Services, Inc. Intelligent roadway system
JP2002024885A (ja) * 2000-07-03 2002-01-25 Nec Corp 通行料金決済システム、運行管理システム、方法、および記録媒体
JP2005267505A (ja) * 2004-03-22 2005-09-29 Fujitsu Ltd 交通管理システム
WO2013190566A2 (fr) * 2012-06-22 2013-12-27 Goel Sunil Suivi de péage centralisé, paiement et système de contrôle utilisant des dispositifs à capacité de géolocalisation

Also Published As

Publication number Publication date
EP3002733A1 (fr) 2016-04-06
PL3002733T3 (pl) 2022-11-21

Similar Documents

Publication Publication Date Title
EP2909815B1 (fr) Procédé et installations de soulèvement de péage conditionné par le trafic
DE102004013807B4 (de) Elektronisches Mautsystem für Verkehrswege und Verfahren zu dessen Betrieb
EP1088286B2 (fr) Dispositif de controle cote route pour un appareil de peage installe dans un vehicule
DE4310099C2 (de) Einrichtung zur Identifizierung von Wegstrecken
EP3002733B1 (fr) Centrale d'encaissement de péage, appareil mobile et procédé d'encaissement d'un péage
EP1101201B1 (fr) Procede et systeme pour controler si un appareil servant a debiter une somme d'argent fonctionne correctement
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
DE102022125933A1 (de) System und Verfahren zur Mauterhebung für ein Kraftfahrzeug
DE102006032468B3 (de) Adaptive Datenvolumen bei der Übertragung von Daten für eine zentrale Geoobjekterkennung
CH695585A5 (de) Verfahren und Vorrichtung zur automatischen Mauterhebung.
EP3210194A1 (fr) Procédé et unité embarquée (obu) pour la détermination de taxes de péage
DE102005049768A1 (de) Mauterfassungsgerät und Mauterfassungsverfahren
WO2007073748A1 (fr) Systeme et procede de determination des redevances d'utilisation de voies et/ou de zones a peage
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
EP1920411B1 (fr) Procede de controle pour detecter des divergences au niveau de geo-objets
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
WO2009043691A1 (fr) Dispositif et procédé de détection de péage routier
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
EP3211605B1 (fr) Dispositif de véhicule, système, dispositif coté route et procédé d'exécution d'au moins une transaction
DE102015000497A1 (de) Verfahren zur Erfassung von fahrtenbezogenen Informationen von Fahrgästen von öffentlichen Verkehrsmitteln mit einer fahrzeuggebunden Steuerungseinheit und einer mobilen Anzeige- und Eingabeeinheit
DE102005059284A1 (de) Verfahren zur Ermittlung von berichtigten aktuellen Positionsdaten insbesondere zur Bestimmung von aktuellen Fahrzeugpositionen
DE10258653A1 (de) Einrichtung und Verfahren zur Benutzungsgebührenerfassung

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

AK Designated contracting states

Kind code of ref document: 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

17P Request for examination filed

Effective date: 20161006

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

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

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

Ref legal event code: REF

Ref document number: 1497450

Country of ref document: AT

Kind code of ref document: T

Effective date: 20220615

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

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

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

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

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

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

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

Ref country code: FI

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

Effective date: 20220608

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

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

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

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

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

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

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

Ref country code: SM

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

Effective date: 20220608

Ref country code: SK

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

Effective date: 20220608

Ref country code: RO

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

Effective date: 20220608

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

Ref country code: EE

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

Effective date: 20220608

Ref country code: CZ

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

Effective date: 20220608

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

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 502014016274

Country of ref document: DE

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

Ref country code: AL

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

Effective date: 20220608

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

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

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

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

Ref country code: DK

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

Effective date: 20220608

26N No opposition filed

Effective date: 20230310

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

Ref country code: SI

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

Effective date: 20220608

Ref country code: MC

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

Effective date: 20220608

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

Ref country code: LU

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

Effective date: 20221002

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

Ref country code: IE

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

Effective date: 20221002

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

Ref country code: PL

Payment date: 20230920

Year of fee payment: 10

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

Effective date: 20231207

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

Ref country code: GB

Payment date: 20231025

Year of fee payment: 10

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

Ref country code: IT

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

Effective date: 20220608

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

Ref country code: FR

Payment date: 20231023

Year of fee payment: 10

Ref country code: DE

Payment date: 20231018

Year of fee payment: 10

Ref country code: CH

Payment date: 20231102

Year of fee payment: 10

Ref country code: AT

Payment date: 20231019

Year of fee payment: 10

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

Ref country code: BE

Payment date: 20231023

Year of fee payment: 10

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

Ref country code: HU

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

Effective date: 20141002

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

Ref country code: CY

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

Effective date: 20220608

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

Ref country code: MK

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

Effective date: 20220608