EP3174015A1 - Reconnaissance d'erreurs dans une unité embarquée à bord d'une véhicule d'un système de péage - Google Patents

Reconnaissance d'erreurs dans une unité embarquée à bord d'une véhicule d'un système de péage Download PDF

Info

Publication number: EP3174015A1
Authority: EP; European Patent Office
Prior art keywords: vehicle; data; event; status information; status
Prior art date: 2015-11-27
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.): Granted

Application number

EP15003424.7A

Other languages

German (de)

English (en)

Other versions

EP3174015B1 (fr

Inventor

Thomas Lohfelder

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.)

2015-11-27

Filing date

2015-11-27

Publication date

2017-05-31

2015-11-27 Application filed by Toll Collect GmbH filed Critical Toll Collect GmbH

2015-11-27 Priority to EP15003424.7A priority Critical patent/EP3174015B1/fr

2017-05-31 Publication of EP3174015A1 publication Critical patent/EP3174015A1/fr

2025-03-12 Application granted granted Critical

2025-03-12 Publication of EP3174015B1 publication Critical patent/EP3174015B1/fr

Status Active legal-status Critical Current

2035-11-27 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 invention relates to a toll system, a vehicle device and a method for detecting errors in a vehicle-carried vehicle device of a toll system according to the preambles of the independent claims.
In-vehicle equipment used for toll collection and carried in a vehicle are accordingly adapted to detect position data of positions of the vehicle and to process the position data and / or data derived from the position data for the purpose of collecting a vehicle-related toll fee in accordance with a plurality of state variables of the vehicle device Vehicle is to be raised, which is identifiable on the basis of the detected position data.
either the vehicle device itself depending on a plurality of state variables of the vehicle device by collecting at least one used by the vehicle toll road surface based on the position data and / or from the position data derived data levy a vehicle related toll for the use of the identified traffic area by the vehicle or a central data processing device of the toll system which has received from the vehicle device the position data and / or data derived from the position data as a result of processing the position data and / or data derived from the position data based on the detected position data and / or data derived from the position data levy a vehicle-related toll for the use of the identified traffic area by the vehicle.
the state variables of the vehicle device are such that they influence the processing of the position data or the data derived from the position data-for example, enable or prevent it-in the sense that the result of the processing depends on the state variables.
a state variable may be a registered identifier of the vehicle device or the vehicle needed to obtain an allocation of a toll to the vehicle using the toll road surface.
Another state variable may be a registered operational readiness state of the vehicle device for which, in the event of a lack of operational readiness, a dedicated processing of the position data or data derived from the position data is prevented.
In-vehicle toll collection systems typically have a variety of state variables that affect toll collection.
the values of these state variables are stored in a memory of the vehicle device in the form of output data generated in response to received or generated input data.
input data of the vehicle device can be supplied via an interface or generated by the vehicle device itself.
the vehicle device can receive input data whose processing then results in a change of the output data, with the result that a changed value of the affected state variables is stored in the vehicle device.
the vehicle device in operation itself Generate input data, the processing then also has a change of the output data with the result that a changed value of the state variables concerned is stored in the vehicle device.
a particular value of a state variable may result in a toll being no longer levied or being levied incorrectly or being allocated to the correct vehicle. Such a certain value can be correct. Due to the complex processing of input data, under unforeseen circumstances that can not be remedied, such a particular value may not be correct. Thus, changing a value of a state variable without the prerequisites necessary for it - as well as maintaining a value of a state variable which has become invalid due to changed boundary conditions or input data - has an unjustified influence on the toll collection - in other words an error. In the interest of both the toll operator and the user, it must be determined in such a case that there is a mistake and, if so, in whose area of responsibility he falls. Thus, an error may be due to the vehicle equipment of the toll operator or the lack of cooperation of the user.
the present invention has set itself the task of detecting such erroneous values of a state variable of a vehicle device of a toll system.
the invention provides for the detection of erroneous state variables of a tolling vehicle device, input data from which the vehicle device output data in the form of a value of the state variables are generated in an event log and store the output data in a status protocol to then starting from to be tested
a toll collection system which comprises at least one vehicle device carried by a vehicle, which is configured to (a) detect position data of positions of the vehicle, (b) position data and / or in dependence on a plurality of state variables of the vehicle device to derive data derived from the position data for the purpose of collecting a toll related to the vehicle to be levied for the use of a traffic area by the vehicle identifiable from the acquired position data; (c) receiving or generating input data; d) generating output data, each representing a value of a state variable of the vehicle device, in dependence on the received or generated input data, and characterized in that the vehicle device is configured, (e) status information generated respectively associated with a status time value
Output data includes entering in a status log stored in the vehicle device (f) event messages that include received or generated input data associated with an event time value respectively, in an event log stored in the vehicle instrument, and the toll system is configured to (g) determine from at least one rule stored in the toll system whether i)
the feature (g) i) corresponds to a protocol check according to the invention with the search for one or more results in the form of output data in the status protocol to be expected (ie expected) by one or more triggers in the form of the input data to be checked in the event log according to the rules. and / or not expected (ie prohibited), and is referred to as "forward search".
the feature (g) ii) corresponds to a protocol check according to the invention for one or more triggers in the form of input data in the event log, which condition one or more results to be tested according to the set of rules in the form of the output data to be checked in the status protocol according to the control scheme expected to be present in the initial data to be tested) or not (and thus prohibited if the initial data to be checked are available), and is referred to as "backward search".
Expected input or output data can be both required input or output data of a single event message or status information that is required by the policy, as well as allowed input or output data of multiple event messages or status information, of which input or output data is at least one event message or status message required input or output data.
the feature (d) describes the desired state of the vehicle device according to the invention.
the feature (h) describes with the result that can result from the forward and / or reverse search, the reportable incorrect actual state of the vehicle device according to the invention.
time range in short: time range
the formulation of a given time range (in short: time range) around the respective time value of the event message or status information to be checked does not necessarily mean that the respective time value of the event message or status information to be checked must be contained in the predetermined time range (this condition applies only to the Time value of the status information (s) or event message (s) to be searched for in the exam).
the limits of the time range with two relative time intervals are defined with negative sign, if the predetermined time range entirely before each Time value of the event message or status information to be checked, and with two relative time intervals each with a positive sign, if the predetermined time range entirely after the respective time value of the event message or status information to be checked.
the respective time value of the event message or status information to be checked forms a limit, so that a relative distance is equal to zero, it is sufficient to specify a single time interval for the respective time value of the event message to be checked or status information for defining the time range.
the time ranges for the search for prohibited input or output data may be different from the time ranges for the searches for expected input or output data.
the time range for the search for prohibited input or output data may be arranged temporally according to the respective time value of the status information or event message to be checked, because on the basis of event messages or status information to be checked, certain subsequent event messages or status information should not occur, and the time range for the Search for expected input or output data to be arranged in time before the respective time value of the status information or event message to be checked, because the existence of the status information or event messages to be checked presupposes the presence of specific input or output data of preceding event messages or status information.
the time range for the search for prohibited input or output data can also be arranged before the respective time value of the status information or event message to be checked, because on the basis of event messages or status information to be checked, certain preceding event messages or status information must not occur, their forbidden input data being different Output data than the status information to be checked or their prohibited output data would have generated input data other than that of the event message to be checked.
the time range for the search nach.zu expected input or output data can be arranged in time to the respective time value of the status information or event message to be checked, because on the basis of checking event messages or status information specific subsequent event messages or status information should occur. The temporal readjustment or preposition of the time range does not rule out that the respective time value of the status information or event message to be checked forms a lower or upper limit of the relevant time range.
the toll system may be configured to determine (i) at least one event message of the event log to be tested in the status log in accordance with at least one set of rules stored and / or prohibited in the toll system at least one status information is included whose status time value is within a predetermined time interval according to the event time value of the event message to be tested and / or ii) expected at least one to be tested status information of the status log in the event log according to at least one stored in the toll system rules and / or forbidden input data are contained in at least one event message whose event time value lies within a predetermined time interval before the status time value of the status information to be checked, and (h) in the determination of a In the absence of output data to be expected in accordance with the at least one set of rules and / or expected input data and / or upon detection of the presence of output data and / or prohibited input data prohibited according to the at least one set of rules.
the set of rules preferably comprises a database in which input data of one or more event messages are linked to output data of one or more status information, the output data to be expected being the output data associated with the input data of one or more event messages to be checked and the output data to be searched for input data to be tested for one or more status information associated input data are expected input data.
a database provides the combinations of compatible input and output data.
input data of one or more event messages are linked to output data of one or more status information, with the output data associated with the input data of one or more event messages being prohibited being output data for a forward search and the output data for a backward search examining output data of one or more status information associated input data is prohibited input data.
Such a database provides the combinations of incompatible input and output data.
the duration of said time range or said time interval is one hour or less than one hour. More preferably, the duration of said time range or said time interval is less than one minute.
the duration of the said time range or the said time interval may depend on the status information to be checked or the event message (s) to be checked.
the duration of the said time range or said time interval may also depend on a status time value of status information other than that of the status information to be checked or, in addition to the status time value of the status information to be checked, also on the status time value of status information other than that of the status information to be checked.
the toll system can be configured to select a first status information from the status protocol and a second status information entered immediately below into the status protocol with regard to one and the same status variable, first output data of the first status information and second output data of the second To check status information for a change in the value of the state variables, to determine whether in the event log according to at least one rule stored in the toll system expected input data of at least one event message are included, the processing according to the processing instructions would trigger a corresponding change in the value of the state variables and their Event time value between the first status time value of the first status information and the second status time value of the second status information is and to generate the error message when determining that no expected according to the rule input data in the event log.
the backward search it is determined whether the input data relevant for a specific change of the value of a state variable from a first value to a second value are present.
the vehicle device can be designed to generate output data from input data at predetermined time intervals or upon receipt of a corresponding instruction and to write these and / or output data already generated previously into a status protocol.
This status protocol may already have been stored in the in-vehicle device before the write clock, so that status information written in the status protocol may be added to the state information already existing in the status protocol or replace it with respect to the same state variable. In the latter case, previous values of state variables are lost in the status log.
a comparison in the sense of the previously described backward search remains possible if first a first status protocol written with a first status information for each state variable by the vehicle device by means of a mobile communications device included in the vehicle device to an outside - in particular off Vehicle arranged central data processing device is sent and later transmitted a second time written second status protocol with each second status information to one state variable by the vehicle device by means of the covered by the vehicle device mobile communication device to the central data processing device, which is a possible override of the first status protocol prevented by the second.
the vehicle device may be configured to simultaneously store a plurality of status logs generated at different times with respect to the same state variables.
the toll system may be configured to select a first status information from a first status protocol written at a first time and a second status information regarding a same status variable as the first status information from a second status protocol written at a second time, first output data of the first Status information and second output data of the second status information on a change in the value of the state variables to determine whether to include in the event log according to at least one rule stored in the toll system expected input data of at least one event message, the processing according to the processing instructions a corresponding change of the value would trigger the state variable and its event time value between the first status time value of the first status information and the second status time value of the second status information is on and on the determination that no expected according to the rules input data in the event log to generate the error message.
the toll system may also be configured to select from the event log input data of a first event message and input data of a second event message, to determine whether in the status protocol according to at least an output data to be expected in the toll system of at least one status information that would result from the consecutive processing of the input data of the first event message and the input data of the second event message by the vehicle device and whose status time value lies within a predetermined time interval after the event time value of the second event message , and in the determination that no according to the rule-expected output data are included in the event log to generate the error message.
the forward search it is determined whether, for a particular event pair, the output data expected from the processing of its input data is in status information of the status protocol.
a corresponding backward search for the input data of two event messages is possible analogously starting from a status information item to be checked.
the toll system can also be configured to select input data of an event message to be checked from the event log, to determine whether the output data of at least one first status information and expected output data of at least one second status information are to be expected in the status protocol according to at least one rule stored in the toll system would result from the consecutive processing of the input data of the event message to be checked by the vehicle device and whose status time value is within a given time interval after the event time value of the second event message to be checked, and on the determination that no expected according to the rules output data in the event log are included to generate the error message.
forward search it is determined whether expected output data of a plurality of status information resulting from the processing of its input data is present in the status protocol for a specific event.
a corresponding backward search for the input data of an event message is possible analogously on the basis of several status information to be checked.
the toll system is designed to raise a vehicle-related toll for the use of the identified traffic area by the vehicle based on the plurality of state variables of the vehicle device by identifying at least one toll road used by the vehicle on the basis of the detected position data.
the toll system preferably comprises a central data processing device arranged outside the vehicle, and the vehicle device comprises a wireless communication device at least for sending data to the central data processing device.
the central data processing device is arranged away from the vehicle.
the vehicle device can send position data to the central data processing device, which can be configured to receive the position data and identify at least one used by the vehicle toll road surface based on the detected position data on the vehicle related toll for the use of the identified traffic area by the vehicle to raise.
the vehicle device may derive data derived from the position data, for example that of an identifier of a traffic area identified by the vehicle device or of a vehicle toll that the vehicle device detects by identifying at least one toll road used by the vehicle Position data has determined - to the central Send data processing device.
the central data processing device determines a toll charge from the identifier of the identified traffic area.
the toll charge received by the central data processing device or alternatively / optionally determined is allocated by the central data processing to a user account, with respect to which the central data processing sends a request for debiting the toll fee and booking to an account of the toll operator to an account management data processing device.
the vehicle device preferably sends an identifier of the vehicle device, of the vehicle or of the user together with the position data and / or the data derived from the position data to the central data processing device.
the identifier of the vehicle device or of the vehicle is used by the central data processing device to refer the raised toll charge to the vehicle from which the position data originate, in order to charge the user with a toll that actually traveled the identified traffic area.
the identifier of the vehicle device, of the vehicle or of the user in association with the account data of the user is stored in the central data processing device.
the central data processing device On the basis of the received from the vehicle device identifier of the vehicle device, the vehicle or the user the Anlagen Wegrichtograph with the position data, the identifier of the identified traffic area and / or the toll fee was sent, the central data processing device, the position data, the identifier of the identified traffic area and / or allocate the toll fee to the user account.
the identifier of the vehicle device, of the vehicle or of the user is a possible state variable of the vehicle device.
the position data processing process with which the vehicle device processes the position data and / or data derived from the position data for the purpose of collecting a toll related to the vehicle, which is to be levied for the use of a traffic area by the vehicle, which is identifiable on the basis of the detected position data, insofar as a function of the identifier of the vehicle device, the vehicle or the user, as the position data processing, the linkage of the position data and / or derived from the position data with the identification of the vehicle device, the vehicle or the User includes.
the vehicle device is designed, only for a given operational readiness of the vehicle device, the position data and / or derived from the position data for the purpose of collecting a related to the vehicle toll, which is to be raised for the use of a traffic area by the vehicle, based on the detected Position data is identifiable to process a position data processing process.
the vehicle device is designed to monitor its operational readiness state and, as a result of a change in the value of the operational readiness state from "given" to "insufficient,” to set the position data processing process, ie no longer to perform any further detection of position data. Consequently, the vehicle device can be configured alternatively or optionally, only to detect the position data of positions of the vehicle given the operational readiness of the vehicle device, which implies that in the case of a lack of operational readiness then the position data processing process also fails.
the toll system according to the invention is characterized in that a first state variable of the vehicle device is a registered identifier of the vehicle device, the vehicle or a user of the vehicle and a second state variable of the vehicle device is a registered operational readiness state of the vehicle device.
the vehicle device is preferably designed to process the position data and / or data derived from the position data for the purpose of collecting a toll related to the vehicle, depending on at least the identifier of the vehicle device, the vehicle or the user and the registered operational readiness state to be collected by the vehicle for the use of a traffic area identifiable on the basis of the recorded position data
the toll system preferably comprises a central data processing device arranged outside the vehicle and the vehicle device comprises a wireless communication device in the form of a mobile radio communication device at least for sending position data and / or data derived from the position data together with the identification of the vehicle device of the vehicle or the user to the central data processing device.
the vehicle device is designed, as part of the position data processing process of processing the position data and / or the data derived from the position data for the purpose of collecting a toll related to the vehicle, the position data and / or the data derived from the position data together with the identifier of the vehicle device , the vehicle or the user to send by means of the mobile communication device to the central data processing device.
the central data processing device is preferably designed to link the received data derived from the position data and / or data derived from the received position data, for example a toll, to an account of a user that is linked to the identifier of the vehicle device of the vehicle or the user is stored in the central data processing device.
An example of an identifier of the vehicle device is a serial number of the vehicle device.
Another example of an identification of the in-vehicle device is the mobile radio (call) number (eg MSISDN, "Mobile Subscriber Integrated Services Digital Network Number") of the mobile radio communication device of the vehicle device.
An example of an identification of the vehicle is the vehicle license plate front and reverse side of the vehicle attached license plate (colloquially "number plate”).
Another example of an identification of the vehicle is the vehicle identification number (colloquially: "VIN”) of the vehicle's registration certificate.
An example of an identifier of the user is a user identifier assigned by the toll operator or selected by the user himself, which can consist of a user name and a password.
Further state variables of the vehicle device may be: a registered vehicle class of the vehicle, a registered determination of the use or non-use of a tollable traffic area by the vehicle, a registered toll or toll collection allowance of the vehicle, a registered availability state of a particular service of the vehicle device.
the vehicle class examples are a weight class, a length class, an axle class and a pollutant class.
the amount of the toll fee as data derived from the position data in this case depends on the vehicle class or possibly on several different types of vehicle classes.
the vehicle class is also a state variable of the vehicle device according to the invention, because the position data processing process, regardless of whether the vehicle device determines the toll amount (first case) or the central data processing device, the amount of the toll from the transmitted from the vehicle device position data or derived from the position data determined (second case), is dependent on the value of the vehicle class, which is sent in the second case together with the position data or derived from the position data from the vehicle device in the position data processing to the central data processing device.
the registered determination of the use or disuse of a toll road surface by the vehicle may affect the way the position data and / or data derived from the position data are processed by the vehicle device, so that the result of the position data processing is dependent on whether the vehicle is on a toll road or not.
From a registered availability state of a particular service of the vehicle device may depend, for example, if and when, when the vehicle device sends position data or data derived from position data to a central data processing device and / or optionally to which of several central data processing devices.
the vehicle device can be designed to send the acquired position data to a central data processing device of an anonymization service instead of to a central data processing device of the toll operator, which forwards the position data with its own identifier to the central data processing device of the toll operator which, from the point of view of the central data processing device, does not allow any conclusions to be drawn about the vehicle device from which they originate.
the central data processing device of the toll operator After determining the toll fee from the position data, the central data processing device of the toll operator receives the identifier of the vehicle device, the vehicle or the user from the central data processing of the anonymization service. If the service "Anonymous position data provision" is not available, then the vehicle device sends the position data directly to the central data processing device of the toll operator.
Another possible state variable is the identifier of the toll road surface, the use of which was determined by the vehicle based on the position data by the vehicle device.
the position data or data derived from the position data in an intermediate step in the process for determining the toll area used for tolling forms the input data according to the invention in this case.
the toll system preferably has at least one central data processing device arranged outside the vehicle, and the vehicle device comprises at least one mobile radio communication device for sending and / or receiving data to and / or from the central data processing device, at least one position determining device being configured.
each individual one of the events (i) to (v) or a certain combination of these events can trigger a change in the operational readiness of the vehicle device from “ready for operation” to “not ready” after a period of occurrence of one or more of these events.
the value of the operational readiness can change from "ready for operation” to "restricted ready for operation”.
the event of receiving an instruction to change the vehicle registration number can trigger a chain of several successive events (password query, password input, authentication, sending a request to the central data processing device, the encryption of this request, etc.), which finally leads to the entry of the changed vehicle license plate into the status log.
a certain amount of toll collection that could not be communicated by the first communication device to a central data processing device of the toll system
examples of the amount of toll collection for example, the number of recognized traffic areas used
a toll amount are used calculated for traffic areas used consecutively.
Suffice a single data store to store said data; However, it is preferably a plurality of data memories: a first data memory for storing the software for processing position data and / or data derived from the position data, a second data memory for temporary storage of the position data and at least a third data memory for storing the time value of the sequence of Validity of the software used to process position data and / or position data, data of identified traffic areas and / or toll collection, vehicle registration data, and vehicle class data.
the toll system is preferably characterized by performing at least steps g) and h) based on at least one set of rules stored in the vehicle device and storing the possibly generated error message in the vehicle device and / or by means of a mobile radio device included in the vehicle device.
the vehicle device of such a toll system is further developed with decentralized error checking, event-dependent, time-dependent, location-dependent and / or random to carry out a self-test, in which the vehicle device for at least one to be examined event message of the event log steps g) i) and h) performed the event of execution of the self-test is stored as input data together with the time value of the execution of the self-test as an event message in the event log and wherein the at least one event message to be tested is defined as having an event time value delayed from the time value of the most recent self-test.
a vehicle device for example, every time you turn the vehicle device; at each re-powering of the vehicle device, at each completed hour of operation of the vehicle device, each time a contiguous road network of toll sections is re-entered, each time a 100-kilometer path is covered, and / or at random during operation of the vehicle device for a selection .an or all event messages newly registered in the event log since the last self-test have been performed, to check whether they have associated expected status information in the status log.
the vehicle device of such a toll system with decentralized error checking a mobile communication device for wireless transmission of the status protocol via at least one mobile network to at least one arranged outside the vehicle central data processing device of the toll system and is configured, the status protocol by means of the mobile communication device to the central Data processing device to send, from the central data processing device by means of the mobile communication device to receive an instruction to perform step g) ii) with respect to at least one defined by the central data processing device to be checked status information, the step g) ii) with respect to the defined by the central data processing device perform at least one status information to be checked and h) upon detection of a defect in accordance with the w At least one set of rules to be expected input data and / or in the determination of the presence of prohibited according to the at least one set of input data to generate at least one error message and to send this error message by means of the mobile communication device to the central data processing device.
the central data processing device is designed to receive the status protocol, to
the toll system is preferably characterized in that the toll system comprises at least one central data processing device arranged outside the vehicle, the vehicle device has at least one vehicle-side communication device for wireless transmission of the event log to the central data processing device and at least one vehicle-side communication device for wireless transmission at least one status information of the status protocol to the central data processing device and is configured to send the event log and at least one status information of the status protocol to the central data processing device, wherein the central data processing device is formed, the event log sent by the vehicle device and the the vehicle device sent at least receive status information and perform at least steps g) and h) based on at least one stored in the central data processing device rules.
Sends the vehicle device because it is designed accordingly - an extract of the status protocol, which includes a plurality of status information, or the entire, several status information comprehensive, status protocol, so.ist the central data processing system is formed to determine the status information from the status information of the several status information or the extract thereof which is the status information to be checked according to the invention.
Such a toll system with central error checking preferably comprises at least one DSRC communication device coupled to the central data processing device for receiving the at least one status information of the status protocol from the vehicle device, while the vehicle device is a first vehicle-side communication device in the form of a wireless communication device for wireless Sending the event log to the central data processing device via at least one mobile radio network and a second vehicle-side communication device in the form of a vehicle-side DSRC communication device for wireless transmission of at least one status information of the status protocol to the DSRC roadside communication device and is adapted to the event protocol by means of the mobile communication device via at least one mobile network to the central ver to send processing device and to send at least one status information of the status protocol by means of the vehicle-side DSRC communication device to the roadside DSRC communication device of the toll system.
the roadside DSRC communication device or a roadside control device comprising the DSRC roadside communication device may be configured to send the status information received from the vehicle device to the central data processing device - either on its own initiative or on the basis of a request from the central data processing device for status information that have been received by the DSRC communication device since the last shipment.
the DSRC roadside device or a roadside controller including the DSRC roadside communication device may be formed of the plurality of status information the status protocol or the statement thereof to determine that status information which is the status information to be checked according to the invention, and to send the specific status information to be checked to the central data processing device.
the DSRC roadside communications device or a roadside controller including the DSRC roadside communications device may be configured to send the complete received state log digest or complete status log to the central data processing device.
the toll system provides a particular advantage in the case of a check in which reference data is compared with output data of a status information received from the vehicle device for conformity by means of a roadside control device. Depending on the outcome of this comparison then there is one Causing a control-based protocol check, in which the central data processing device in a central audit or by the vehicle device in a decentralized check the status information is checked by the event log to determine whether unexpected output data on a fault of the vehicle device (ie the toll system ) or due to a mistake of the user.
the toll inspection system for this purpose comprises at least one central data processing device arranged outside the vehicle and at least one roadside control device with at least one DSRC roadside communication device for receiving at least one status information of the status protocol from the vehicle device, wherein the vehicle device has a first communication device in the form of a mobile radio communication device for wireless transmission of the event log to the central data processing device via at least one mobile network and a second communication device in the form of a vehicle-side DSRC communication device for wireless transmission of at least one status information of the status protocol to the roadside DSRC communication device and trained is the event log by means of d he mobile communication device to send at least one mobile network to the central data processing device and to send at least one status information of the status protocol by means of the vehicle-side DSRC communication device to the roadside DSRC communication device of the toll system
the roadside control device is adapted to at least one status information of the status of the protocol Receive vehicle device by means of the DSRC roadside
the DSRC roadside communications device may be configured to receive the status protocol or the status report extract with a plurality of status information Control device is formed in this case, from the status protocol to gain the status information with the output data, with which the reference data are to be compared.
the control-based toll inspection system comprises, for example, at least one central data processing device located outside the vehicle and at least one roadside controller with at least one DSRC roadside communication device for receiving at least one status information of the status protocol, the vehicle device having a first communication device a mobile radio communication device for wireless transmission of the event log to the central data processing device via at least one mobile network and a second communication device in the form of a vehicle-side DSRC communication device for wireless transmission of at least one status information of the status protocol to the DSRC roadside communication device and is configured, the event log by means of the Mobilfunk- Kommunikationsvorr sending at least one status information of the status protocol to the road-side DSRC communication device of the toll system by means of the DSRC on-board communication device, wherein the roadside control device is configured to generate at least status information of the status protocol from the in-vehicle DSRC system.
the Communications device to receive, compare output data of the at least one status information of the status protocol with reference data to match, and depending on the result of the comparison to send a problem message about the lack or given match of the output data with the reference data to the central data processing device, and the central Data processing device is formed, the problem message about the lack or given match of the respective réelled aten with the reference data together with the relevant status information from the roadside control device to receive and send an audit instruction message via at least one mobile network to the vehicle device for checking the event log regarding the status information in question, the vehicle device is also configured to the Wegsanginssnachricht means of the mobile communication device receive, in response to the Wegsanginssnachricht based on the rules to determine whether the event log an event message with expected input data is included, the processing by the vehicle device according to the rules should generate the relevant status information with the relevant output data, and / or an event message with contains prohibited input data, the processing of which by the vehicle device according to the rules does not the status information in question should generate at least a Tautsystem Communicatmeld
the DSRC roadside communications device may be configured to receive the status log or the status report digest with a plurality of status information Roadside control device is formed in this case to obtain from the status protocol, the status information with the output data, with which the reference data are to be compared.
the control-related protocol check if the output data provided by the vehicle device deviates or matches the reference data detected or provided at the control device, it can advantageously be determined whether this deviation or coincidence is due to an error of the toll system or an error of the user - for example an operator error , a behavioral error (neglect of the obligation to cooperate) or an irregular act (manipulation, falsification or impairment of data or signals) - are due.
the output data may represent a registered standby state of the vehicle device
the reference data may represent a state of inoperability of the vehicle device
the roadside control device may be configured in the case that the standby state is the inoperative state to send a problem message about the lack of operational readiness to the central data processing device.
the DSRC roadside communication device may be configured to receive the status protocol or an extract of the status report having a plurality of status information, in which case the roadside controller is configured to obtain from the status protocol the status information including the output data in the form of the registered number of the vehicle ,
Input data may be represented by data regarding the following events: (i) failure to receive signals from a Global Navigation Satellite System at the position-determining device; (ii) the absence of the generation of position data from signals of a global navigation satellite system by the position-determining device; (iii) the undershooting of a minimum quality of quality of at least one signal of a global navigation satellite system and / or at least one position determined by the position-determining device; (iv) failure to receive signals at the interface for receiving signals from a transmitter; (v) the mismatch of travel angles determined from global navigation satellite system signals and travel direction angles detected by the accelerometer / yaw rate sensor; (vi) the failure of loading the operating system from the data store to the working memory; (vii) exceeding the time value
the output data may represent an identifier of a toll road section identified last by the vehicle device as reference, the reference data representing an identifier of a toll section to be checked on which the control device is located, corresponding to the position of the control device and the road-side control device is configured, in the event that the identifier of the toll road section last identified by the vehicle device does not coincide with the identifier of the route section to be checked, a problem message about the inconsistency of the identifier of the vehicle device last Tolling section of the route identified as having traveled with the identification of the section of track to be checked to the central data to send processing device.
the DSRC roadside communication device may be configured to receive the status log or an extract of the status log having a plurality of status information, wherein the roadside control device is configured to retrieve from the status log the status information with the output data in the form of the identifier of the vehicle device last to win as a traffic-identified section of the route.
Input data may be represented by recorded position data from one or more of the identification of the most recent tolling section identified as having traveled. If the recorded position data does not correspond to the identified route section during the protocol check, a recognition error of the software for processing the position data and / or data derived from the position data must be assumed, and a toll system error message is generated. If the recorded position data correspond to the identified route section during the protocol check, an operator error is to be assumed and a user error message is generated.
the output data may represent a position last registered by the vehicle device, representing reference data of a position assigned to the control device, and the roadside control device may be configured, in the event that last of the vehicle device Registered position does not match within a permissible deviation (of, for example, 100 meters) with the control device associated position to send a problem message about the mismatch of the last registered by the vehicle device position with the control device associated position to the central data processing device.
a permissible deviation of, for example, 100 meters
the DSRC roadside communication device may be configured to receive the status log or an extract of the status log having a plurality of status information, wherein the roadside controller is configured to obtain status information with the output data in the form of the position last registered by the vehicle device from the status log to win.
a toll system with control-dependent decentralized or central protocol check may be characterized in that the road-side control device at least one image pickup device (for example, a camera) for generating at least one image capture of a license plate of the vehicle and at least one image processing device for obtaining a mark from the image recording of the license plate of the vehicle includes and is adapted to generate by means of the camera at least one image recording of a license plate of the vehicle and to win by means of the image data processing means a recorded characteristic from the image capture of the license plate of the vehicle, the output data representing a registered license plate of the vehicle and the reference data the recorded license plate of the vehicle and in the case where the r and the recorded tag are different to send a problem message about the diversity of the registered and recorded tags to the central data processing device.
the road-side control device at least one image pickup device (for example, a camera) for generating at least one image capture of a license plate of the vehicle and at least one image processing device for obtaining a mark from the image recording of the license plate of the vehicle
the DSRC roadside communication device may be configured to receive the status protocol or an extract of the status report with a plurality of status information, in which case the roadside controller is configured to retrieve from the status protocol the status information including the output data in the form of the registered vehicle number ,
a toll system with control-dependent decentralized or central protocol check may be characterized in that the roadside control device comprises at least one detection device for detecting an image and / or a contour of the vehicle and at least one classification device for determining a vehicle class of the vehicle from the acquired image and / or the has detected contour of the vehicle and is adapted to receive at least the status information with the output data in the form of the registered vehicle and / or axle class of the vehicle from the vehicle device by means of the roadside DSRC device, by means of the detection device at least one image and / or at least one To capture contour of the vehicle and to determine a detected vehicle class of the vehicle from the captured image and / or the detected contour of the vehicle by means of the classification device, the output data is a registered Fah representing the vehicle class of the vehicle, the reference data representing the detected vehicle class of the vehicle, and the roadside controller being further configured, in the case where the registered vehicle class and the detected vehicle class are different, a problem message about the diversity of the registered and the detected vehicle class to send to the central
the vehicle device is designed to send only the output data to the control device from the status information, since the output data satisfy the control device for comparison with the reference data.
the central data processing device is designed to request from the vehicle device in addition to the event log also the status time value of the status information of the output data
the Vehicle device is designed to send the status time value of the status information of the output data together with the event log to the central data processing device.
the vehicle device is designed to send only an extract of the event log with several event messages.
the said extract is also to be understood as an event log.
the volume of data in the context of the dispatch of the event log can be limited, or at least reduced.
the vehicle device is designed to delete event messages from the event log that relate to status information that is no longer up-to-date or no longer available in that out-of-date values of its state variables have been updated by current values of state variables , This can limit the scope of the event log.
the vehicle device has a vehicle-side DSRC communication device for wirelessly sending at least status information of the status protocol to the DSRC roadside communication device
the vehicle device is preferably a first device part and at least one of the first device part objected to and communication technology
the second device part coupled to the first device part, wherein the first device part has a first processor, which is at least formed, depending on a plurality of state variables of the vehicle device, the position data and / or derived from the position data for the purpose of collecting a toll related to the vehicle to process, which is to be raised for the use of a traffic area by the vehicle, which is identifiable based on the detected position data, and at least a first data memory
the second device part comprises the on-vehicle DSRC communication device having a second processor configured to control DSRC communication of the on-vehicle DSRC communication device with the DSRC roadside communication and having at least one second data memory
the vehicle device is configured Save event log in the first datastore
the status protocol or at least status information of the status protocol may be provided in the course of passing the vehicle on a DSRC roadside communication device by the vehicle device promptly for dispatch from the on-vehicle DSRC communication device to the DSRC roadside communication device.
a vehicle device for detecting positions of a vehicle carrying them, wherein the vehicle device is configured to (a) detect position data of positions of the vehicle (b) in dependence on a plurality of state variables of the vehicle device To process position data and / or data derived from the position data for the purpose of collecting a vehicle toll related to the use of a traffic area by the vehicle identifiable from the detected position data; and (d) generate output data depending on the received or generated input data, each representing a value of a state variable of the vehicle device, characterized in that the vehicle device further configured to (e) register status information, each comprising generated output data associated with a status time value, in a status log stored in the vehicle device, (f) event messages each including received or generated input data associated with an event time value in one of the in-vehicle device (g) using at least one stored in the vehicle set rules to determine whether i) are included in at least one to be tested event message of the event log in the status protocol according to the at least one set of
the invented vehicle device may be configured to determine (g) based on at least one event message of the event log to be tested in the status protocol according to the at least one set of rules expected and / or prohibited output data in at least one status information is contained whose status time value lies within a predetermined time interval after the event time value of the event message to be checked, and / or (ii) at least one status information of the status protocol to be tested in the event log according to the at least one set of rules expected and / or prohibited Input data are contained in at least one event message whose event time value lies within a predetermined time interval before the status time value of the status information to be checked, and (h) when a deficiency is detected rtenden output data and / or according to the at least one set of rules to be expected input data to generate an error message.
the in-vehicle device has a vehicle-side DSRC communication device for the wireless transmission of at least one status information of the status protocol to the DSRC roadside communication device and is in a first device part and at least one second objected by the first device part and communicatively coupled to the first device part Subdivided part of the device, wherein the first device part has a first processor which is at least configured to process the position data and / or derived from the position data for the purpose of collecting a vehicle related toll fee depending on a plurality of state variables of the vehicle device Use of a traffic area is to be raised by the vehicle, which is identifiable based on the detected position data, and at least one first data memory, wherein the second device part the f A vehicle-side DSRC communication device having a second processor configured to control the DSRC communication of the on-vehicle DSRC communication device with the DSRC roadside communication, and having at least a second data memory, and wherein the vehicle device is configured to store the event
the status protocol or at least one status information of the status protocol in the course of passing the vehicle on a roadside DSRC communication device by the Vehicle equipment according to the invention can be provided quickly for dispatch from the vehicle-side DSRC communication device to the road-side DSRC communication device.
a method for detecting faults in a vehicle-mounted vehicle device of a toll system comprising the steps of: (a) acquiring position data of positions of the vehicle by the in-vehicle device, (b) processing the position data, and / or data derived from the position data by the vehicle device in dependence on a plurality of state variables of the vehicle device for the purpose of charging a vehicle-related toll fee, which is to be levied for the use of a traffic area by the vehicle, which is identifiable from the acquired position data, (c) Receiving or generating input data by the vehicle device; and (d) generating output data, each representing a value of a state variable of the vehicle device, in response to the received or generated input data by the vehicle device, characterized by the further steps of (e) registering status information, each comprising generated output data associated with a status time value, in a status log stored in the vehicle device by the vehicle device, (f) registering event messages, each received or generated associated with an
the method may provide for the following steps: (g) determination by the vehicle device and / or by a central data processing device of the toll system, based on at least one of the rules stored in the vehicle device and / or in the central data processing device, whether (i) at least one to be tested event message of the event log in the status protocol according to the rules expected and / or prohibited output data are included in at least one status information whose status time value within a predetermined time interval after the event time value of the event message to be checked is and / or (ii) at least a status information of the status protocol to be checked in the event log according to the set of rules expected and / or prohibited input data are contained in at least one event message whose event time value within a v predetermined time interval before the status time value of the status information to be checked, by the decentralized processor and / or a central processor of a central data processing device of the toll system, the event log and and (h) generating an error message upon detection of a lack of expected output data according to the set of
the registration of event messages each comprising received or generated input data associated with an event time value, in an event log stored in a first data memory of a first device portion of the in-vehicle device, and the registration of status information comprising generated output data associated with a status time value, respectively a first processor of the first device part processing the position data and / or data derived from the position data as a function of a plurality of state variables of the first device part objected and communicatively coupled with the first device part second device part of the vehicle device
Vehicle device for the purpose of collecting a vehicle-related toll, which is to be levied for the use of a traffic area by the vehicle, based on the recorded Po sition flowers is identifiable, performs and controls a second processor of the second part of a device in the context of a DSRC communication by the second part of the device taking place sending status information.
a vehicle device 20 comprises - as shown schematically in FIG Fig. 1 illustrated - a vehicle device 10 with a decentralized processor 11 and a DSRC communication module 22 and a displacement sensor 21 (for example, an odometer or odometer), which are coupled to the vehicle device 10 in terms of data technology.
a decentralized processor 11 for example, a DSRC communication module 22 and a displacement sensor 21 (for example, an odometer or odometer), which are coupled to the vehicle device 10 in terms of data technology.
technical couplings between data coupled with each other components are in Fig. 1 illustrated by continuous connecting lines between the coupled components. They can be realized by interfaces, connecting lines or wireless communication means (eg bluetooth).
the distributed processor 11 is adapted to control and receive data from the DSRC communication module processor 22d by the execution of a computer program loaded into the random access memory 17b for execution from the data RAM.
a GNSS position determination device 12 receives signals from satellites of a Global Navigation Satellite System (GNSS), for example GPS, by means of its GNSS reception antenna 12b and determines its provisional position from the received satellite signals by means of its GNSS receiver 12a - and thus the provisional position of a vehicle 30 (FIG. please refer Fig. 2 ), from which the vehicle device 20 is carried.
the determined provisional position is further advanced by the processor 11 based on heading change values provided by a gyroscope 16 of the vehicle apparatus and relative path length values of a distance traveled in a certain time provided by the travel sensor 21
Position more precise final position hereinafter referred to only as "position" processed in the course of a known as a coupling location method.
the signals of the gyroscope 16 and the displacement sensor 21 may be directed to the GNSS position determination device 12, the GNSS position determination device 12 performing the coupling location.
the position determination by the processor 11 and the GNSS position determining device 12 is carried out repeatedly, for example, every second - in the course of the movement of the vehicle 30 by the vehicle device 20.
the remote processor 11 is coupled to a security module 18, which is formed as a stand-alone data processing unit (eg, a smart card) having at least one autonomous control module 18a and a memory area 18b, the autonomous control module 18a being configured to request data output from the memory area 18b and / or the modification or recording of data in the memory area 18b only to perform an authentication.
the authentication procedure can be carried out by analyzing a digital signature by means of a public key stored by the signer in the memory area 18b of the security module 18.
a cryptographic data memory (not shown) may be provided, in which the processor 11 can store data encrypted only with appropriate authentication and can read out in a decrypting manner.
a vehicle identifier of the vehicle 30 is stored in the memory area 18b of the security module 18 or cryptographic data memory in the form of the vehicle license plate, which is encompassed by at least one vehicle license plate of the vehicle 30.
the vehicle identifier may be stored in the data RAM 17a.
an axle class and a pollutant class are stored in the memory area 18b of the security module 18.
An initial registration or modification of the vehicle identification, the axle class and / or the pollutant class can be effected by the user by sending corresponding data and instructions to the processor via an unillustrated user interface (Bluetooth interface, USB interface, keyboard or touch-sensitive display device) 11 of the vehicle device transmitted.
Bluetooth interface Bluetooth interface
USB interface USB interface
a corresponding instruction for initial registration or modification of the vehicle identification, the Achstre and / or the vehicle class via the mobile network 40 is sent to the vehicle device 20, which receives this instruction together with the new data by means of a mobile radio transceiver 13 and processed by the decentralized processor 11.
Such incoming instructions form first input data according to the invention, which are stored by the decentralized processor 11 in an event log provided for this purpose in the data read / write memory 17a together with a first event time value of the input of the respective instruction as the first event message.
the encrypted storage of the vehicle identifier, the axle class and / or the pollutant class in the memory area 18b of the security module 18 or in the cryptographic data memory can be initiated by means of appropriate instructions by the decentralized processor 11.
These vehicle-internal instructions form second input data according to the invention, which are stored together with a second event time value in the event log as a second event message.
the autonomous control module 18a of the security module 18 from a corresponding confirmation signal from the decentralized processor 11, which is stored as inventive third input data with a third event time value in the event log by the decentralized processor 11 as a third event message.
the decentralized processor 11 causes the received vehicle identification, the received axle class and / or the received pollutant class as output data according to the invention together with a status time value in the status protocol.
This status time value may correspond to the first event time value, the third and last event time value, or a time value later than the third and last event time value and the time value corresponding to the entry of the output data in the status protocol. This is only a question of definition; However, this has an influence on the definition of the predetermined time range, in which a status information of the status log is to be searched for relevant event messages of the event log in the course of the protocol check according to the invention.
the status time value is the time value of the entry of the output data in the status protocol and is thus temporally after the first, second and third event time value.
the predetermined time interval within which the event time values of event messages, which precede the entry of the status information, must be, for example, 10 seconds for vehicle data (vehicle identification, vehicle class). This size would also apply to a time range within which the event time values of event messages that condition the registration of status information must be if the status time value did not fall after the third event time value but would, for example, fall to the first event time value; it would only be necessary to adjust the temporal position of the temporal range of the same time width as the distance accordingly.
the status protocol is stored in the DSRC communication module data read / write memory 22d of a vehicle-side DSRC communication module, which is mounted at a distance from the vehicle device 10 on the inside of the windshield of the vehicle 30 so that the DSRC transceiver 22a by means of its DSRC antenna 22b with an off-vehicle DSRC communication device 63a of a roadside controller 60 (see FIG Fig. 2 ) can communicate.
the DSRC communication carrier is microwave in the 5.8 GHz frequency range. Alternatively or optionally, infrared light (850 nm) is possible as DSRC communication carrier, for which purpose photodiodes would have to be used as receiving elements and IR light emitting diodes as transmitting elements.
the distributed processor 11 communicates wirelessly or line-wise with the DSRC communication module processor 22c of the DSRC communication module 22 via a communication link.
the processor 11 detects a position of the vehicle 30 every second and processes the detected position data of these positions for the purpose of collecting a vehicle-related toll charge to be levied for the use of a route section by the vehicle 30 Identifiable on the basis of the detected position data.
the decentralized processor 11 compares thereto position data of one or more detected positions with geographical elements of a digital map, each of which has an identifier of a route section, by means of a toll-fee determination program executed in the main memory 17b assigned. If there is sufficient geographical agreement of the acquired position data with a specific geographical element, the route section whose identifier is associated with the particular geographic element is recognized as being traveled.
the decentralized processor 11 determines a toll charge based on the identifier of the section of road identified as traveled, which depends on the axle class and the pollutant class of the vehicle 30.
axle class and pollutant class are state variables of the vehicle device according to the invention because they determine the amount of the toll charge and insofar influence the processing of the position data on a toll related to the vehicle.
the central processor 11 to the mobile radio transceiver 13, the determined toll charge together with the vehicle identification via the mobile network 40 to the central data processing device 50 of a toll center 58 (see Fig. 2 ) to send.
the central data processing device 50 of the toll center 58 assigns the toll fee on the basis of the vehicle identifier to a user account from which the toll fee is deducted by a data processing device of a bank (not shown) credited to the account of the toll operator.
the vehicle identifier is also a state variable of the vehicle device according to the invention because it determines the allocation of the toll fee to a user and insofar influences the processing of the position data on a toll related to the vehicle.
the central processor 11 by means of a running in memory 17b position data processing program the mobile radio transceiver 13, detected position data - in particular position data of several immediately detected positions - together with the vehicle identification, axle class and emission class of the vehicle 30th to send to the central data processing device 50.
the central processor 51 of the central data processing device 50 compares the received position data of one or more detected positions with geographical elements of a digital map, to each of which an identifier of a route section is assigned. If there is sufficient geographical agreement of the acquired position data with a specific geographical element, the route section whose identifier is associated with the particular geographic element is recognized as being traveled.
the central processor 51 determines a toll charge based on the identifier of the section of road identified as traveled, which depends on the axle class and the pollutant class of the vehicle 30.
Vehicle identifier, axle class and pollutant class are also state variables of the vehicle device according to the invention in this case, because they determine the amount of the toll and the allocation of the toll to a user and insofar influence the processing of the position data for a toll related to the vehicle.
the section of the route recognized as being traveled also represents a state variable of the vehicle device whose identifier is output data of status information in the status protocol as currently traveled section on the initiative of the decentralized processor 11 in the DSRC communication module data read / write memory 22d are stored.
the decentralized processor 11 is designed, upon the occurrence of a power supply of the vehicle device 10 via the power supply terminal 19 or as a result of switching on the vehicle device 10, to check the operational readiness of the vehicle device 20 and, if possible, to put the vehicle device into operation.
the decentralized processor 11 first undertakes at least an attempt to load the toll fee determination program from the data read / write memory 17a into the main memory 17b. If the loading of the toll fee determination program into the main memory 17b fails, it writes an event message about the attempt of loading and an event message about the failure of the loading into the event log stored in the data RAM 17a.
the loading is caused by the failure of the loading to set a standby state to "deficient" to present it to the user via the display device 15 and to write the storage of status information about the lack of operational readiness of the vehicle device in the status protocol, which in the DSRC communication module Data read-write memory 22d is stored. If loading of the toll fee determination program succeeds in the main memory 17b, a corresponding event message is entered in the event log.
the remote processor 11 checks whether the software comprising the toll collection program and the digital card is still valid by reading out a time value of the validity of the software from the storage area 18b of the security module 18 and a current time value of the timer 14 , for example a radio clock, compares.
the remote processor 11 If the software is invalid because the current time value of the timer is greater than the time of expiration of the software, the remote processor 11 writes an event message about the validity check and an event message about the negative result of the validation into the event log is stored in the data RAM 17a. Further, it is caused by the invalidation of the software to set a standby state vehicle device to "deficient", to present it to the user via the display device 15, and to write the storage of status information about the inoperability of the vehicle device into the status protocol, which is described in US Pat DSRC communication module data read-write memory 22d is stored. The attempt to load the toll collection program into the main memory 17b and check the validity of the software may also be in the reverse order. The status protocol may alternatively or optionally also be stored in the data read / write memory 17a of the vehicle device for storage in the DSRC communication module data read / write memory 22d.
the decentralized processor 11 After the decentralized processor 11 has commissioned the vehicle device 20 in such a way, under the condition of the successful loading and the validity of the software, it performs an internal protocol check relating to event messages and status information from a preceding operating cycle of the vehicle device as part of a self-test. These are all event messages stored in the event log, their event time values between the penultimate event of turning on or setting up a power supply of the vehicle device 20 or the vehicle device 10 via the power supply terminal 19 and the last event of turning off or removing the power of the vehicle device 20 or the vehicle device 10 are above the power supply terminal 19.
the decentralized processor 11 checks on the basis of at least one stored in the data read-write memory 17a rule, whether each event message of the event log in the status log - if determined in the rules - according to the rules expected output data are included in at least one status information whose Status time value within a predetermined time interval of, for example, 10 seconds after the event time value of the event message to be tested, and generates in the detection of a lack of expected according to the at least one rule output data an error message for their display on the display device 15 of the distributed processor no instruction to the display device 15 but to send them to the central data processing device 50 (see Fig. 2 ) the mobile radio transceiver 13 is instructed by the remote processor.
the set of rules comprises a database in which input data of one or more event messages are linked to output data of one or more status information, wherein the forward data to be expected with the input data to be tested of one or more event messages are expected output data.
the input data of the three event messages "Attempting to load the toll charging program into the working memory 17b", "Failure to load the toll charging program into the working memory 17b” and "Registration to be inoperative” are linked to the output data of status information "Lack of operational readiness”.
the protocol check according to the invention provides - and this is one of its essential advantages - that the event messages and the status information are correlated with each other over the predetermined time range. Event messages which lie outside of this predetermined time range with regard to status information are not the subject of the protocol check and can therefore not lead to an error message.
the decentralized processor 11 is adapted to make an attempt to load the toll collection program into the main memory 17b again after a lapse of a predetermined period of time from the detection of the lack of operability due to the futile attempt to load the toll collection program into the working memory 17b.
the decentralized processor 11 is designed to change the value of the status information of the operational readiness state from "inoperative readiness" to "given operational readiness” in the event of successful loading of the toll fee determination program into the main memory 17b.
the vehicle device 20 After performing this self-test, the vehicle device 20 is ready for use (if it is not in the state of lack of operational readiness) and displays this given operational readiness on the display device 15.
the vehicle device 20 receives the operating current from a rechargeable battery (accumulator as an example of a charge storage element) 19 a, which is included in the vehicle device 10 .
the decentralized processor 11 is designed to receive measured values of the charge state of the battery 19a at predetermined time intervals (of, for example, 10 minutes) and to write these together with the measurement time as event time value as an event message in the event log.
the decentralized processor 11 is designed to compare the measured value of the charge state at each measurement with a limit value of the charge state and to store the undershooting of the limit value as input data of an event message in the event log.
the decentralized processor 11 is further configured to count the entries of those immediately consecutive measurements of the state of charge whose measured values fall below the limit, set the counter to zero if, in a measurement of the state of charge, the measured value does not fall below the limit, and a lack of operability the vehicle device 20 to determine when the counter is set to three.
the counter readings are also entered by the decentralized processor 11 as input data of meter reading events in the event log such as the determination of the lack of operability, which is also subsequently written together with the time of detection as status information in the status log.
the decentralized processor 11 is configured, after a predetermined period of time has elapsed since the determination of the lack of operability due to the insufficient charge state again to detect measured values and to check whether the measured value of the charge state of the battery 19a is still below the limit.
the decentralized processor 11 is configured to change the value of the status information of the stand-by state from "lack of operational readiness" to "given operational readiness” in the event that the three immediately consecutively detected measured values of the state of charge do not fall below the limit value.
the decentralized processor 11 of the vehicle device 10 - and thus vehicle device 20 - is designed to detect preliminary position data by means of the GNSS position determination device 12 and from this provisional position data based on path length data of the encoder 21 and travel angle change data of the gyroscope 16 final position data (hereinafter referred to as "position data") and to process these position data as described above in response to a plurality of state variables of the vehicle device for the purpose of collecting a vehicle-related toll fee to be levied for the use of a toll route section by the vehicle, which is identifiable on the basis of the detected position data.
position data path length data of the encoder 21 and travel angle change data of the gyroscope 16 final position data
the processor 11 is adapted to the events, (i) the absence of the reception of signals of a global navigation satellite system at the position determining device 12, (ii) the absence of generating position data from signals of a global navigation satellite system by the position determining device 12, (iii) falling below a Minimum quality of at least one signal of a global navigation satellite system and / or at least one position determined by the position-determining device 12, (iv) absence of reception of signals at the interface for receiving signals from a travel sensor 21 and / or (v) the mismatch from driving direction angles determined from signals of a global navigation satellite system and from driving direction changes detected by the gyroscope 16, driving direction angles determine these events with corresponding input data in the event log ei nzutragen and at the one or more times - especially directly consecutive - determination of such events to set the value of the operational readiness state of the vehicle device to "lack" and enter a corresponding status information in the status log.
the decentralized processor 11 is configured, after a predetermined period of time has elapsed since the determination of the lack of operability due to the insufficient charge state again to detect measured values and to check whether the measured value of the charge state of the battery 19a is still below the limit.
the decentralized processor 11 is configured to change the value of the standby state status information from "lack of operational readiness" to "given operational readiness” in the case where three immediately-consecutively detected charge state measurements do not fall below the limit value.
the central data processing device 50 is comprised by a center 58 of the toll system and has a central communication device 53, a central processor 51, a first central data memory 56 and a second central data memory 57.
the central communication device 53 is a network interface card (network adapter) which is the interface between the PSTN, mobile network 40 and / or the Internet and the central processor 51 included in the central data processing device 50.
the first central data memory 56 includes user data associated with an identifier of the vehicle 30 (vehicle license plate), with a user account and tolls associated with identifiers of toll sections, which of the vehicle device 20 together with the vehicle license plate after recognizing the pursuit of at least one toll road section were sent to the central data processing device.
the second central data memory 57 is provided for storing status information of status records and event reports of event logs associated with the vehicle registration numbers of vehicles, such as the vehicle 30, which the central data processing device 50 receives from vehicle devices, such as the vehicle device 20.
the vehicle device 20 may be configured to receive an instruction for the transmission of the status protocol via the mobile radio network 40 by means of the mobile radio transceiver 13 and to comply with this instruction by the decentralized processor 11 of the vehicle device 10 and thus the vehicle device 20-the mobile radio device.
Transmitter 13 instructs to send the status protocol via a mobile network 40 to the arranged outside and outside the vehicle central data processing device 50.
the central processor 51 is configured to store the status protocol received via the mobile radio network 40 by means of the central communication device 53 in the second central data memory 57 and to check for the presence of exceptional status information or unusual combinations of status information.
An exceptional status information can be, for example, those whose output data represent a lack of operability of the vehicle device.
An exceptional combination of status information can be formed, for example, by two status information, in this regard a registered section of the route has been registered immediately one after the other, and its output data represents the same identifier of the section of route traveled. If the central processor 51 identifies exceptional status information or an exceptional combination of status information, it instructs the central communication device 53 to send an instruction for transmitting the event log to the vehicle device 20.
the exceptional status information and / or the status information of the extraordinary combination of status information form status information to be checked according to the invention.
the vehicle device 20 is configured to receive via the mobile radio network 40 by means of the mobile radio transceiver 13 an instruction to transmit the event log and comply with this instruction by the decentralized processor 11 of the vehicle unit 10 - and thus the vehicle device 20 - the mobile radio transceiver 13 instructs to send the event log via a cellular network 40 to the central data processing device 50 located outside and outside the vehicle.
the central data processing device 50 is designed to receive the event log sent by the vehicle device 20 and to store it in the second central data memory 57.
the central data processing device 50 is configured to determine whether input status data to be evaluated for the status protocol to be checked in the event log according to at least one set of rules stored in the first data memory 56 is contained in at least one event message whose event time value is within a predetermined time range is the status time value of the status information to be checked, and to generate an error message upon detection of a lack of expected according to the at least one set of output data and / or expected input data error message and this error message stored in the first central data memory 56 to that record that the Vehicle license plate of the vehicle 30 has.
the control device 60 has a control bridge 61, which spans the toll section section transverse to the direction of travel, so that the vehicle 30 can drive under it.
a control device 63 having a roadside DSRC communication device 63a, an image pickup device 62 and a vehicle contour detection device 64 are attached to the control bridge 61.
the image pickup device 62 captures at least one image from the approaching vehicle 30 and determines, by means of an image data processing device (not shown) from image data of the approaching vehicle image 30, the vehicle registration number of the vehicle 30 printed on the vehicle license plate 31 of the vehicle 30.
the vehicle contour detection device 64 detects the contour of the vehicle 30 and determines, by means of a classification device (not illustrated) from the detected contour, a vehicle class of the vehicle 30 - in this case an axle class of the vehicle 30, based on the number of axles of the vehicle 30.
vehicle contour detection means known to those skilled in the art, which are included in the vehicle contour detector 64, are: a radar, a LIDAR, a time-of-flight camera (TOF camera), a stereo camera assembly, a light-section sensor with structured lighting / shading of the vehicle.
the on-vehicle DSRC communication module 22 of the in-vehicle DSRC communication device 63a receives a request to send a control relevant extract of the status protocol to the roadside controller.
the control-relevant extract of the status log contains status information with output data, each of which is the value of a state variable of the vehicle device 20 in the form of a registered vehicle license plate 30, a registered axle class of the vehicle 30, a registered emission class of the vehicle 30, a registered operational readiness state of the vehicle device 20 Registered identifier of a last recognized as driving recognized toll section and a registered identifier of a last but last recognized as a traffic toll section, along with the associated status time values.
the DSRC communication module processor 22c provides the requested extract of the status protocol by accessing the DSRC communication module data RAM 22d for shipment to the onboard DSRC transceiver 22a, which sends the digest to the DSRC antenna 22b roadside DSRC communication device 63a.
the recording apparatus 63 is configured to receive the extract of the status record by means of the DSRC roadside communication device 63a as well as the recorded vehicle number of the vehicle 30 detected by the image pickup device 62 and the detected axle class of the vehicle 30 detected by the vehicle contour detection device 64, and each Register reception with a reception time.
the control device 63 assigns the recorded vehicle registration number to the registered vehicle registration number and the detected axle class of the registered axle class.
the control device 63 is initially configured to obtain from the received extract of the status protocol the status information with the output data to be compared with reference data of the control device 60. Then, the controller 63 is configured to check the vehicle standby state of the vehicle device 20 received by the vehicle device 20 to see whether it corresponds to the lack of operational readiness, and if so, a problem message about the inoperability of the vehicle device 20 together with the time of extracting the status protocol via the mobile network 40 to the central data processing device 50 send.
the controller 63 is configured to check the link detection received from the vehicle device 20 to see whether it corresponds to the link ID of the link covered by the controller, and if there is a mismatch, a message of inconsistency of the ID of the vehicle device 20 last recognized as driving toll road section with the identifier of the controlled section to the central data processing device to send.
the control device 63 is configured to check the registered vehicle registration number sent from the vehicle device 20 for compliance with the vehicle registration number recorded by the image acquisition device 62, and if inconclusive, a trouble message about the inconsistency of the received registration number with the vehicle registration number 20 to send the central data processing device.
controller 63 is configured to check the registered axle class sent from the vehicle device 20 for compliance with the axle class detected by the vehicle contour detector 64, and in case of mismatch, a problem message about the detected registration with the registered axle class of the vehicle 20 to send to the central data processing device.
the central data processing device 50 is designed to receive each of the problem messages, wherein the reception of a single problem message, the problematic status information of which in this case forms the status information to be checked, is sufficient for the central data processing device to communicate via the central communication device 53 Mobile network 40 sends a request to the vehicle device 20 to transmit the event log.
the vehicle device 20 is configured to receive via the mobile radio network 40 by means of the mobile radio transceiver 13 an instruction to transmit the event log and comply with this instruction by the decentralized processor 11 of the vehicle unit 10 - and thus the vehicle device 20 - the mobile radio transceiver 13 instructs to send the event log via a cellular network 40 to the central data processing device 50 located outside and outside the vehicle.
the central data processing device 50 is designed to receive the event log from the vehicle device 20 by means of the central communication device 53 and to store it in the second central data memory 57 in association with the status information (s) to be checked.
the central processor 51 is designed to determine for each of the status information to be checked whether input data to be expected in at least one set of rules stored in the first data memory 56 is contained in at least one event message, the event time value thereof within a predetermined time range around the status time value the status information to be checked is located.
the central processor 51 is designed to check, according to the rules, whether one or more event messages in the transmitted event log are from one lack of operational readiness triggering input data (examples are given above), the event time value is not earlier than 10 seconds before and not later than the status time value of the registered lack of operational readiness.
the central processor 51 is configured to generate a toll system error message when none or all of the event messages whose input data cause inoperability are within the first 10 second time period in the event log and generate a user error message if all event messages whose input data trigger a non-operational readiness are present in the event log in the said first time range.
the central processor 51 is configured to check according to the rules whether in the transmitted event log one or more event messages from an ineligible input data (examples are mentioned above), their event time value in a second time range of later than the Status time value of the registered lack of operational readiness and earlier than the reception time of the check-relevant extract of the status protocol by the control unit 63 is located.
the central processor 51 is configured to generate a toll system error message if there are one or more event messages in the second time range whose input data trigger the release of a malfunction, and to generate a user error message if there is no event message in the second time range whose input data is a cancellation the lack of operational readiness triggers or contributes to.
the processor 51 is designed, in particular, to generate a user error message only if all event messages which are necessary to trigger a lack of operational readiness are present in the first time range and not all event messages which are necessary to suspend a lack of operational readiness are present in the second time range.
the central processor 51 is designed to check, according to the rules, whether one or more event messages from the latter occur in the transmitted event log If the event time value is not earlier than the status time value of the registered identifier of the toll-liable route section last identified as traffic and not later than the status time value of the registered identifier of the toll-liable route section last identified as being traveled.
the central processor 51 is configured to generate a toll system error message if none or all of the event messages whose input data are a prerequisite for recognition of the last traveled route section are present in the time range between two directly registered route section identifiers in the event log, and to generate a user error message if all event messages whose input data are prerequisites for a recognition of the last traveled section of the route are present in the named time interval between two directly registered route section identifiers in the event log.
a user error in this case may be that a user of the GNSS position determining means 12 is playing false navigation satellite signals which the GNSS position determining means 12 uses to determine their position in place of the correct navigation satellite signals coming from the navigation satellites of the GNSS.
This so-called spoofing leads the vehicle device to process position data of another, for example, toll-free, route with the result of not recognizing any of the toll road sections actually to be recognized.
a similar effect can be caused by the jamming which causes the GNSS position determiner 12 not to be able to determine its position.
input data may be: a spatial and / or temporal average of positions that have been subjected to the comparison with the geographical elements of the digital map, a spatial and / or temporal mean of directions, whose positions are compared with the geographical elements have been subjected to the digital map, the geographical element identified in the comparison, a measure of the quality of the GNSS positioning of the positions subjected to the comparison with the geographical elements of the digital map.
the central processor 51 is designed to check according to the set of rules whether one or more event messages with input data leading to the registration of the registered vehicle registration number exist in the transmitted event log whose event time value is not earlier than 10 seconds before and not later than the status time value of the registered vehicle registration number.
the central processor 51 is configured to generate a toll system error message when none or all of the event messages whose input data are indicative of registration of the registered tag are present in the said 10 second time range in the event log and generate a user error message if all Event messages whose input data are authoritative for registering the registered vehicle license plate are present in the said 10-second time range in the event log.
the central processor 51 is designed to check according to the set of rules whether one or more event messages with input data leading to the registration of the registered axle class are present in the transmitted event log and whose event time value is not earlier than 10 seconds before and not later than the status time value of the registered axis class.
the central processor 51 is configured to generate a toll system error message when none or all of the event messages whose input data is authoritative for registration of the registered axle class are present in the said 10 second time range in the event log and generate a user error message if all Event messages whose input data are relevant for registering the registered axle class are present in the said 10-second time range in the event log.

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)

EP15003424.7A 2015-11-27 2015-11-27 Reconnaissance d'erreurs dans une unité embarquée à bord d'une véhicule d'un système de péage Active EP3174015B1 (fr)

Priority Applications (1)

Application Number	Priority Date	Filing Date	Title
EP15003424.7A EP3174015B1 (fr)	2015-11-27	2015-11-27	Reconnaissance d'erreurs dans une unité embarquée à bord d'une véhicule d'un système de péage

Applications Claiming Priority (1)

Application Number	Priority Date	Filing Date	Title
EP15003424.7A EP3174015B1 (fr)	2015-11-27	2015-11-27	Reconnaissance d'erreurs dans une unité embarquée à bord d'une véhicule d'un système de péage

Publications (2)

Publication Number	Publication Date
EP3174015A1 true EP3174015A1 (fr)	2017-05-31
EP3174015B1 EP3174015B1 (fr)	2025-03-12

Family

ID=54782393

Family Applications (1)

Application Number	Title	Priority Date	Filing Date
EP15003424.7A Active EP3174015B1 (fr)	2015-11-27	2015-11-27	Reconnaissance d'erreurs dans une unité embarquée à bord d'une véhicule d'un système de péage

Country Status (1)

Country	Link
EP (1)	EP3174015B1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number	Priority date	Publication date	Assignee	Title
EP3495847A1 (fr) *	2017-12-08	2019-06-12	Continental Automotive GmbH	Agencement de tachygraphe et procédé de fonctionnement d'un agencement de tachygraphe

Citations (3)

* Cited by examiner, † Cited by third party
Publication number	Priority date	Publication date	Assignee	Title
DE10104499A1 (de) *	2001-01-31	2002-08-14	Daimler Chrysler Ag	Strassengebührenerfassungssystem
EP1708143A2 (fr) *	2005-03-09	2006-10-04	MPS Solutions GmbH	Système destiné au traitement de données de position et/ou de péage pour des véhicules
EP1870302A1 (fr) *	2006-06-21	2007-12-26	AGES International GmbH & Co. KG	Personnalisation à distance d'une unité embarquée

2015
- 2015-11-27 EP EP15003424.7A patent/EP3174015B1/fr active Active

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number	Priority date	Publication date	Assignee	Title
DE10104499A1 (de) *	2001-01-31	2002-08-14	Daimler Chrysler Ag	Strassengebührenerfassungssystem
EP1708143A2 (fr) *	2005-03-09	2006-10-04	MPS Solutions GmbH	Système destiné au traitement de données de position et/ou de péage pour des véhicules
EP1870302A1 (fr) *	2006-06-21	2007-12-26	AGES International GmbH & Co. KG	Personnalisation à distance d'une unité embarquée

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number	Priority date	Publication date	Assignee	Title
EP3495847A1 (fr) *	2017-12-08	2019-06-12	Continental Automotive GmbH	Agencement de tachygraphe et procédé de fonctionnement d'un agencement de tachygraphe

Also Published As

Publication number	Publication date
EP3174015B1 (fr)	2025-03-12

Legal Events

Date	Code	Title	Description
2017-04-28	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
2017-04-28	STAA	Information on the status of an ep patent application or granted ep patent	Free format text: STATUS: THE APPLICATION HAS BEEN PUBLISHED
2017-05-31	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
2017-05-31	AX	Request for extension of the european patent	Extension state: BA ME
2017-12-08	STAA	Information on the status of an ep patent application or granted ep patent	Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE
2018-01-10	17P	Request for examination filed	Effective date: 20171130
2018-01-10	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
2019-07-27	STAA	Information on the status of an ep patent application or granted ep patent	Free format text: STATUS: EXAMINATION IS IN PROGRESS
2019-09-04	17Q	First examination report despatched	Effective date: 20190731
2024-01-17	P01	Opt-out of the competence of the unified patent court (upc) registered	Effective date: 20231207
2024-12-02	GRAP	Despatch of communication of intention to grant a patent	Free format text: ORIGINAL CODE: EPIDOSNIGR1
2024-12-02	STAA	Information on the status of an ep patent application or granted ep patent	Free format text: STATUS: GRANT OF PATENT IS INTENDED
2025-01-01	INTG	Intention to grant announced	Effective date: 20241203
2025-02-01	GRAS	Grant fee paid	Free format text: ORIGINAL CODE: EPIDOSNIGR3
2025-02-07	GRAA	(expected) grant	Free format text: ORIGINAL CODE: 0009210
2025-02-07	STAA	Information on the status of an ep patent application or granted ep patent	Free format text: STATUS: THE PATENT HAS BEEN GRANTED
2025-03-12	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
2025-03-12	REG	Reference to a national code	Ref country code: GB Ref legal event code: FG4D Free format text: NOT ENGLISH
2025-03-14	REG	Reference to a national code	Ref country code: CH Ref legal event code: EP
2025-04-03	REG	Reference to a national code	Ref country code: DE Ref legal event code: R096 Ref document number: 502015017039 Country of ref document: DE
2025-04-09	REG	Reference to a national code	Ref country code: IE Ref legal event code: FG4D Free format text: LANGUAGE OF EP DOCUMENT: GERMAN
2025-07-07	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: 20250612
2025-07-08	PG25	Lapsed in a contracting state [announced via postgrant information from national office to epo]	Ref country code: FI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250312
2025-07-10	PG25	Lapsed in a contracting state [announced via postgrant information from national office to epo]	Ref country code: ES Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250312
2025-07-10	REG	Reference to a national code	Ref country code: LT Ref legal event code: MG9D
2025-07-14	PG25	Lapsed in a contracting state [announced via postgrant information from national office to epo]	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: 20250612
2025-07-16	PG25	Lapsed in a contracting state [announced via postgrant information from national office to epo]	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: 20250312
2025-07-16	REG	Reference to a national code	Ref country code: NL Ref legal event code: MP Effective date: 20250312
2025-07-17	PG25	Lapsed in a contracting state [announced via postgrant information from national office to epo]	Ref country code: LV Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250312
2025-07-21	PG25	Lapsed in a contracting state [announced via postgrant information from national office to epo]	Ref country code: GR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250613 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: 20250312
2025-08-18	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: 20250312
2025-09-09	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: 20250312
2025-10-06	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: 20250312
2025-10-09	PG25	Lapsed in a contracting state [announced via postgrant information from national office to epo]	Ref country code: PT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250714
2025-10-15	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: 20250312 Ref country code: PL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250312
2025-10-22	PG25	Lapsed in a contracting state [announced via postgrant information from national office to epo]	Ref country code: CZ Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250312 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: 20250312
2025-10-24	PG25	Lapsed in a contracting state [announced via postgrant information from national office to epo]	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: 20250312
2025-10-27	PG25	Lapsed in a contracting state [announced via postgrant information from national office to epo]	Ref country code: SK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250312
2025-10-28	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: 20250712
2025-12-15	REG	Reference to a national code	Ref country code: DE Ref legal event code: R097 Ref document number: 502015017039 Country of ref document: DE
2026-01-08	PGFP	Annual fee paid to national office [announced via postgrant information from national office to epo]	Ref country code: DE Payment date: 20251118 Year of fee payment: 11
2026-01-13	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: 20250312
2026-01-16	PLBE	No opposition filed within time limit	Free format text: ORIGINAL CODE: 0009261
2026-01-16	STAA	Information on the status of an ep patent application or granted ep patent	Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT
2026-01-21	REG	Reference to a national code	Ref country code: CH Ref legal event code: L10 Free format text: ST27 STATUS EVENT CODE: U-0-0-L10-L00 (AS PROVIDED BY THE NATIONAL OFFICE) Effective date: 20260121
2026-02-18	26N	No opposition filed	Effective date: 20251215

Publication	Publication Date	Title
DE102006045404A1 (de)	2007-04-05	Telematikverfahren und -system
WO2015136029A2 (fr)	2015-09-17	Système télématique, unité télématique et procédé pour commander à distance ou influer sur des fonctions d'un véhicule et pour acquérir des données du véhicule
DE102007051961B4 (de)	2009-07-09	Einrichtung zum Überwachen von sich in einem ausgezeichneten Bereich, insbesondere einem Werksgelände oder einem Parkhaus befindlichen Fahrzeugen
DE102018111780A1 (de)	2018-11-22	Unfallfluchtdetektion
DE102022125933A1 (de)	2023-04-13	System und Verfahren zur Mauterhebung für ein Kraftfahrzeug
DE102010061492A1 (de)	2011-06-30	Fahrzeuginterne Fehlererkennungsvorrichtung
DE102016224351A1 (de)	2018-06-07	Konzept zum Prüfen eines Sensorsystems zum Erfassen eines Belegungszustands eines Stellplatzes auf Fehler
WO2021013508A1 (fr)	2021-01-28	Procédé de fonctionnement d'un système de réservation d'une station de charge pour un véhicule électrique
EP3355249B1 (fr)	2021-06-23	Procédé d'attribution d'un véhicule à un lieu de stationnement, installation de traitement de données et véhicule
EP3279870A1 (fr)	2018-02-07	Dispositif de traitement de donnees, systeme et procede de controle de realisation de la fonction conforme d'un dispositif de determination de position
EP3495847B2 (fr)	2024-07-17	Agencement de tachygraphe et procédé de fonctionnement d'un agencement de tachygraphe
EP3174015A1 (fr)	2017-05-31	Reconnaissance d'erreurs dans une unité embarquée à bord d'une véhicule d'un système de péage
EP3242206A1 (fr)	2017-11-08	Procede de mise a jour de la configuration d'un dispositif de vehicule, dispositif de vehicule, dispositif de traitement de donnees central et systeme de peage
EP3211605B1 (fr)	2022-05-11	Dispositif de véhicule, système, dispositif coté route et procédé d'exécution d'au moins une transaction
EP3242205A1 (fr)	2017-11-08	Procede de mise a jour de la configuration d'un dispositif de vehicule, dispositif de vehicule, dispositif de traitement de donnees central et systeme de peage
EP2772886B2 (fr)	2023-12-06	Système de tableau de bord électronique de véhicule et procédé de contrôle correspondant
WO2010070398A1 (fr)	2010-06-24	Dispositif électronique, véhicule automobile ou cycle utilisant le dispositif électronique, système de direction de la circulation ou système de surveillance de la circulation et procédé de modification de l'identité d'un usager de la route
WO2020233957A1 (fr)	2020-11-26	Procédé de validation d'une actualité de carte
EP3279692A1 (fr)	2018-02-07	Dispositif de traitement de donnees, systeme et procede de controle de realisation de la fonction conforme d'un dispositif de determination de position
DE102018212173A1 (de)	2020-01-23	Kraftfahrzeug mit einer Steuervorrichtung für ein zentrales Flottenmanagement sowie Verfahren zum Einflotten des Kraftfahrzeugs in eine Fahrzeugflotte
DE102016009199B4 (de)	2023-09-28	Verfahren zum Betreiben einer Datenerfassungseinheit zum Erfassen von mindestens einem Steuerungsereignis einer Steuerungvorrichtung eines Kraftfahrzeugs sowie eine Datenerfassungseinheit und eine Datenverarbeitungseinheit
EP1860615A2 (fr)	2007-11-28	Procédé destiné à la vérification du fonctionnement d'une unité de détection mobile
DE102023102158A1 (de)	2024-08-01	Fusionieren von Sensordaten eines Fahrzeuges mit Sensordaten einer Telekommunikationseinrichtung
DE102023203209A1 (de)	2024-10-10	Verfahren zum Detektieren einer sicherheitskritischen Situation während eines Betriebs eines Kraftfahrzeuges
DE102025104280A1 (de)	2025-08-07	Systeme und verfahren zum detektieren von fehlern bei kilometerzählerstand

EP3174015A1 - Reconnaissance d'erreurs dans une unité embarquée à bord d'une véhicule d'un système de péage - Google Patents

Info

Links

Images

Classifications

Definitions

Landscapes

Priority Applications (1)

Applications Claiming Priority (1)

Publications (2)

Family

ID=54782393

Family Applications (1)

Country Status (1)

Cited By (1)

Citations (3)

Patent Citations (3)

Cited By (1)

Also Published As

Similar Documents

Legal Events