EP3789971B1 - Validation de données fournies par un système de diagnostic embarqué - Google Patents

Validation de données fournies par un système de diagnostic embarqué

Info

Publication number
EP3789971B1
EP3789971B1 EP19195618.4A EP19195618A EP3789971B1 EP 3789971 B1 EP3789971 B1 EP 3789971B1 EP 19195618 A EP19195618 A EP 19195618A EP 3789971 B1 EP3789971 B1 EP 3789971B1
Authority
EP
European Patent Office
Prior art keywords
vehicle
data
data element
board diagnostics
diagnostics system
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP19195618.4A
Other languages
German (de)
English (en)
Other versions
EP3789971A1 (fr
Inventor
John Newman
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.)
Audi AG
Original Assignee
Audi AG
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Audi AG filed Critical Audi AG
Priority to EP19195618.4A priority Critical patent/EP3789971B1/fr
Publication of EP3789971A1 publication Critical patent/EP3789971A1/fr
Application granted granted Critical
Publication of EP3789971B1 publication Critical patent/EP3789971B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00—Registering or indicating the working of vehicles
    • G07C5/08—Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time

Definitions

  • the invention is concerned with a method for validating data provided by an on-board diagnostics system of a vehicle.
  • obtaining vehicle data plays a critical role in a variety of economically important activities. Such an activity is, for example, vehicle valuation, vehicle fleet management, or a vehicle related diagnostics and repair action.
  • vehicle valuation for example, vehicle valuation, vehicle fleet management, or a vehicle related diagnostics and repair action.
  • most vehicles in use are either completely unconnected to other vehicles or only have a limited connectivity possibility due to a lack of a corresponding communication device on board of such a vehicle.
  • One way to obtain vehicle data from such an unconnected or only limitedly connected vehicle involves a connection device to establish a wired connection between a data reading device and the vehicle via the connection device. This is often referred to as a dongle solution. This means that the connection device is plugged into an on-board diagnostics (OBD) systems port.
  • OBD on-board diagnostics
  • An OBD system is a vehicle self-diagnostics and reporting system that is designed to give a vehicle owner or repair technician access to the status of various vehicle subsystems.
  • the vehicle data provided by the OBD system can be read via the installed connection device, for example, by establishing a wired communication connection to the connection device in a dealer workshop, via a Bluetooth connection between a mobile communication device and the connection device, and/or via a built-in subscriber identity module (SIM) card in the connection device itself.
  • SIM subscriber identity module
  • Another method to access vehicle data obtained from the OBD system involves retrofitting a vehicle with a physical device capable of reading data from this vehicle.
  • Document US 9,393,958 B2 discloses a method for validating information, wherein a first information item is detected continuously, at least for the duration of its relevance, by a vehicle-to-X communication device.
  • a second information item is detected at the same time as the first information item by a sensor, wherein the sensor is coupled at the data level to the vehicle-to-X communication device.
  • the first and second information items are validated by reconciling an information content of the first and second information item in the case of corresponding information content.
  • Exploiting Insurance Telematics for Fun and Profit (Guan, L., Xu, J., Wang, S., Xing, X., Lin, L., Huang, H., Liu, P., and Lee, W. (2016). Exploiting Insurance Telematics for Fun and Profit. ArXiv, abs/1609.02234 .) describes a method to validate OBD data of a vehicle by using a statistic model.
  • the statistic model predicts a velocity range for a given acceleration value measured by a tamper-resistant sensor of the vehicle. If velocity data of the OBD system of the vehicle match the predicted velocity range, the OBD-data is not considered manipulated.
  • Another method for validating data provided by an on-board diagnostics system of a vehicle according to the state of the art is disclosed by US 2017/294054 A1 .
  • the inventive method is based on the assumption that in a typical potential application concerning analysis and process of vehicle data integrity of vehicle data provided by a vehicle is paramount.
  • a potential application is for example a user base vehicle insurance, a characterization of a current vehicle status, and/or a characterization of both vehicle status and vehicle performance.
  • the reason for this is that it is difficult nowadays to guarantee the integrity of data, as one cannot easily distinguish between data generated by the vehicle itself and artificial vehicle data.
  • Artificial vehicle data is, for example, vehicle data that was created based on authentic vehicle data by manipulating the authentic vehicle data. In this context, such artificial, manipulated data can be referred to as spoofed data.
  • Such spoofed data is often even created intentionally, e.g., by a software developer who creates vehicle-like data by an off-vehicle computer to imitate data received from an OBD system. This can be done, for example, to simulate driving behavior of a vehicle but also, if the created data is transmitted to the OBD system of a vehicle, to manipulate data provided by this very OBD system. Based on such simulations functioning of a driver assistance system for a vehicle could be improved. It is therefore important to provide a method with which confidence in vehicle data coming from either a retrofit solution or a connection device for an OBD system can be stablished. Such a method could preferably be based on cross validation by correlating received vehicle data of different data type.
  • the inventive method for validating data provided by an OBD system of a vehicle therefore comprises receiving data related to the vehicle.
  • the received data comprise a first data element provided by the OBD system of the vehicle.
  • the OBD system i.e., the first data element, is typically accessible by connecting the OBD system or a respective vehicle part with a connector device.
  • a connection between the connector device and a device requesting vehicle data provided by the OBD system can be established as a wireless or as a wired connection.
  • One way to obtain vehicle data via a wired connection involves installing the so-called dongle solution as connector. This means that a physical device, which can be referred to as a dongle device, is plugged into an OBD port of the vehicle.
  • vehicle data provided by the OBD system of the vehicle can be downloaded and read.
  • a wireless connection between, for example, a mobile communication device as device requesting vehicle data and the OBD system can be established via a Bluetooth connection and/or a wireless local network such as a wireless local area network (WLAN).
  • WLAN wireless local area network
  • SIM subscriber identity module
  • the OBD system preferably offers a OBD2 port for data extraction.
  • the received data comprise at least one further data element.
  • the first data element and the at least one further data element are acquired simultaneously.
  • This first step of a method is performed by an off-vehicle device such as a server unit that is not located on board of a vehicle.
  • the off-vehicle server unit is designed as a computer such as a network host.
  • the server unit receives a set of data wherein all data received is related to one particular vehicle.
  • the first data element that is provided by the OBD system of the vehicle could be for example (according to an aspect different from the claimed invention) an odometer reading value giving information on the total distance driven by the vehicle so far. This value is provided by the OBD system and can be transmitted as described above.
  • the at least one further data element is retrieved in the same way and is thus as well data provided by the OBD system of the vehicle.
  • the at least one further data element could be characterizing a throttle position, a fuel flow, a fuel consumption, an average vehicle gear selection over time, and/or a rotational speed of a vehicle engine as a revolutions per minute value.
  • different data connected to the engine of the vehicle are received as at least one further data element.
  • evaluating of the received data is performed.
  • odometer reading value which is the first data element in this example
  • a specific range of, for example, the rotational speed of the vehicle engine as a revolutions per minute value as well as the current vehicle gear selection over time value is given, respectively.
  • a respective value range is defined for fuel consumption, throttle position and fuel flow is given for each specific odometer reading value.
  • first of all the different data elements i.e., the first data element and the at least one further data element are correlated with each other.
  • a distribution function is given for every possible odometer reading value connecting the respective odometer reading value with the respective range of any of the named further data elements.
  • the correlation rule thus provides a clear definition whenever the given odometer reading value seems probable after performing a cross validation with the different further data elements.
  • This cross validation is based on the idea that a digital physical model of the vehicle exists in which details are defined that describe how individual parts of the vehicle are connected in a specific vehicle situation such as a driving, accelerating, braking or stopping situation.
  • This digital model hence describes how a throttle position value describing the throttle position of the engine is mathematically connected to the respective other at least one further data element and/or the first data element.
  • the provided probability value is in a specific probability value range
  • validation of the data provided by the OBD system is confirmed by creating a certification signal indicating that the data provided by the OBD system is confirmed valid.
  • specific probability value range is could be prescribed that if the provided probability value is between 70 and 100 percent, the provided vehicle data is confirmed as real and therefore trustworthy vehicle data. This means that if the probability value indicates that the first data element is actually a true first data element that has not been manipulated with and therefore was not artificially forged this information is taken into account to estimate if the provided specific probability value is high enough to confirm reliability of the data from the OBD system.
  • the first data element is accepted or rejected as a trustworthy signal recovered from the OBD system if it is appropriately mathematically related to other internal signals, i.e., to the further data elements.
  • These further data elements are produced for example by the vehicle itself when the first data element is being measured. This means that if one is interested in measuring the total length of distance driven by the vehicle, then the reported odometer reading value of an odometer reading device of the vehicle should be highly correlated to the described further data elements. As the odometer reading value should be correlated to fuel consumption, and fuel consumption correlated to throttle position and fuel flow.
  • the integral of different signals over time related to generation of motion should be correlated to motion measurements, whereby motion measurements are here the first data elements as the odometer reading value.
  • the different data elements related to the generation of motion are either connected to each other on a physical basis, e.g., each depending on gear tuning, or on a chemical basis, e.g., each dependent on fuel consumption. Those values are summed up as the at least one further data element.
  • the first data element as well as the at least one further data element could each be checked for plausibility. This is done in consideration of a respective predefined minimal and/or maximal value of the first data element and the at least one further data element. This can result in rejecting any data element as non-valid if this data element indicates that, for example, the vehicle has been driving at a speed greater than a maximal speed of the vehicle or at a non-land based location.
  • a sanity check is performed on the first data element and/or the at least one further data element, respectively, to immediately recognize obviously manipulated vehicle data. Even if the provided probability value is in the specific probability value range, validation of the data provided by the OBD system is then not confirmed due to the failed sanity check.
  • a fast and reliable additional mechanism to identify manipulated vehicle data is provided.
  • the created certification signal is kept for retrieval stored in a memory unit.
  • the memory unit can be comprised by or connected to the off-vehicle device such as an off-vehicle server unit.
  • This off-vehicle server unit can be the server unit in which the previously described steps of the method are conducted.
  • the created certification signal can be stored in a different server unit that is independent of the server unit that performs the above-mentioned steps.
  • the memory unit can be designed as an in-vehicle device. If this is the case, retrieval of the stored certification signal is possible in an environment without communication connection to the off-vehicle memory unit, i.e., to the off-vehicle device.
  • the certification signal is stored in an encrypted manner on the in-vehicle device to decrease susceptibility to manipulation attempt on the created and stored certification signal.
  • the created certification signal can be used to create a vehicle curriculum vitae (CV).
  • CV vehicle curriculum vitae
  • the reason behind this is that there is a lot of fraud associated with the false reporting of how many kilometers a vehicle has been driven.
  • correlating different data elements with the odometer reading value from the vehicle as first data element can be used to build confidence in data reported by vehicle because in the end all data provided by the OBD system can be validated with the described method. This is for example of interest when the vehicle is supposed to be sold or bought by a person. Because as advantage, confidence is built into the vehicle data provided by the OBD system meaning that reliable data for example regarding the odometer reading value of a vehicle are available and stored in the memory unit which is in this example an off-vehicle server unit.
  • the at least one further data element is provided by the OBD system of the vehicle.
  • the further data element is, just like the first data element, provided by the OBD system. If this is the case, at least the further data elements describing physically or chemically a motion or other engine correlated activities within the vehicle can be taken into account to make sure that the first data element in question can be validated as manipulation-free.
  • position data of the vehicle provided by a satellite navigation system with global coverage i.e., a global navigation satellite system (GNSS) such as the global positioning system (GPS) and/or temperature data of a temperature sensor device of the vehicle can be considered as at least one further data element provided by the OBD system.
  • GNSS global navigation satellite system
  • GPS global positioning system
  • temperature data of a temperature sensor device of the vehicle can be considered as at least one further data element provided by the OBD system.
  • the at least one further data element is provided by an off-vehicle equipment.
  • This off-vehicle equipment is particularly designed as an off-vehicle sensor device. It is hence possible to consider additional data such as weather data provided by an external weather station as at least one further data element and not just in-vehicle data provided by the OBD system.
  • additional data such as weather data provided by an external weather station as at least one further data element and not just in-vehicle data provided by the OBD system.
  • a traffic camera, a velocity measurement device located on a road, and/or a public or private rain sensor device can function as an respective off-vehicle equipment.
  • the first data element is GNSS data provided by the OBD system, and data provided by a local weather station is taken into account as further data elements.
  • data on total rain fall and current temperature are provided by both the OBD system as well as by the weather station.
  • This weather information from the off-vehicle equipment, i.e., the weather station is then cross-correlated to the weather information from OBD system, as the vehicle, for example, also detects an event of rain with a rain sensor positioned at a windshield of the vehicle as well as measures temperature data with an outdoor temperature sensor. If it is determined that the GNSS data, the rain sensor measurement data and the temperature sensor measurement data are not correlated to the external weather information data provided by the weather station it could be concluded that the GNSS signal may not be authentic.
  • the OBD system data is confirmed valid and therefore the certification signal is created and stored in the memory unit. It is therefore possible to further increase reliability of the described validation method by additionally taking data provided by off-vehicle equipment into account.
  • to the method comprises verifying the odometer reading value as first data element by cross-validating it with the GNSS data provided by the OBD system based on which the total length driven with the vehicle could be estimated. Because if the GNSS data has been proven to be valid, the validity of the odometer reading value is derived from this result as well.
  • the method comprises that an off-vehicle device receives and evaluates the first data element and the further data elements.
  • the different steps described above therefore do not take place within the vehicle that provides the OBD system data in question but in a device that is separated from the vehicle. Therefore the data comprising the first data element and the at least one further data element are first transmitted to the off-vehicle device where evaluation of these data elements takes place. This makes the described method less susceptible for fraud and manipulation and allows the possibility to detect tempered with OBD system data by performing the described steps.
  • the invention also comprises embodiments that provide features which afford additional technical advantages.
  • data that is collected and provided by another vehicle as at least one further data element.
  • the server unit can receive data directly from the other vehicle or data can be received via vehicle-to-vehicle communication by the vehicle and then be transmitted to the server unit together with the first data element.
  • sensor data for example, from another vehicle that is driving in a certain specified distance to the vehicle of which OBD data is investigated can be used to evaluate the probability value.
  • the at least one further data element could then be sensor data provided by a sensor device the other vehicle and/or OBD system data provided by the other vehicle. It is therefore not given that the process of authentication of the vehicle data from the OBD system only depends on data from the authenticating party, meaning the vehicle that provides the OBD system data. It is furthermore possible to have proprietary access to external corroborating data, such as data from the off-vehicle equipment but also data from the other vehicle. Such access may come from exclusive access to environmental sensors but also from sensors from other vehicles that are either produced by the same manufacturer as the vehicle in question or by other vehicle manufacturers. Finally, this further increases reliability in the result of the validation procedure for the data provided by the OBD system of the vehicle.
  • an embodiment of a method comprises as the off-vehicle device an analysis device connected with a OBD system, a mobile communication device, and/or a server unit.
  • the described dongle solution is realized by plugging the connection device, i.e., the dongle device into the OBD2 port of the vehicle.
  • the connection device i.e., the dongle device into the OBD2 port of the vehicle.
  • some sort of analysis device referred to as the dongle device
  • this connection can be built-up with the help of a mobile communication device, for example, the mobile communication device of a workshop worker or an owner of the vehicle.
  • the connection between the mobile communication device and the OBD system could then be achieved by a Bluetooth connection.
  • the analysis device connected with the OBD system can also contain a build-in SIM card in order to be able to access the OBD system data of the vehicle. Furthermore the data can be directly sent to the server unit as described above.
  • the off-vehicle device can therefore be chosen from a variety of possible off-vehicle devices. Essential is, that the off-vehicle device is capable of performing the evaluation steps as described above. This offers numerous opportunities for implementation of the described method.
  • the data related to the vehicle is only received on demand of a request signal.
  • data related to the vehicle is sent to, for example, the server unit as off-vehicle device in order to evaluate the first data element and the at least one further data element according to the correlation rule.
  • the request signal can, for example, be provided by a vehicle selling platform or a manufacture that sends an electronic request signal to the server unit so that the server unit asks for data related to the vehicle from the OBD system and, if necessary, from the source of the at least one further data element, i.e., the off-vehicle equipment and/or the other vehicle.
  • a request signal could also be provided by a person who provides the request signal by sending a request via an application of a mobile communication device to the off-vehicle device asking for validation of data provided by the OBD system of a specific vehicle. This means that the method only takes place once it has been activated manually or automatically by transmitting the request signal. This allows a potential buyers or sellers or a manufacturer of the vehicle to request a validation of the vehicle data provided by a specific vehicle. It is therefore easy and comfortably executable within reach for a person to ask for validation of an identity of the designated vehicle.
  • the request signal is created at a randomly selected point in time. This means, it is possible to randomly check if the data provided by an OBD system of the specific vehicle is valid or not. This allows for spontaneous review and examination of the data provided by a specific vehicle without warning in advance. This increases reliability of the described method because potential manipulation of the vehicle data cannot be deleted before the validation step takes place due to a previously known time stating when the validation method is supposed to take place. This results in a particularly reliable vehicle CV that can be provided for a specific vehicle and its vehicle data.
  • the vehicle that provides OBD system data is designed as a motor vehicle, in particular as a passenger vehicle or a truck, or as a bus or a motorcycle.
  • the invention also discloses a not claimed system for validating data provided by an on-board diagnostics system of a vehicle.
  • the system comprises the vehicle with the OBD system, a memory unit and an off-vehicle device.
  • the system is designed to conduct the method as described above.
  • the invention also comprises not claimed embodiments of the system that comprise features that correspond to features as they have already been described in connection with the embodiments of the inventive method. For this reason, the corresponding features of the embodiments of the system are not described here again.
  • the vehicle of the system is preferably designed as a motor vehicle, in particular as a passenger vehicle or a truck, or as a bus or a motorcycle.
  • the invention also provides a processing unit for a server unit comprising at least one processor and a data memory coupled to the at least one processor, wherein the processing unit is designed to perform corresponding steps for the server unit of an embodiment of the inventive method.
  • the at least one processor may each be based on one of a microprocessor and a microcontroller and an ASIC (application specific integrated circuit).
  • the data memory may comprise computer readable instructions that -when executed by the at least one processor- cause the at least one processor to perform the embodiment of the inventive method.
  • the processing unit may comprise one or more microprocessors and/or one or more microcontrollers. Further, the processing unit may comprise program code that is designed to perform the described method when executed by the processing unit. The program code may be stored in a data storage of the processing unit.
  • the invention also comprises the combinations of the features of the different embodiments.
  • FIG. 1 shows a schematic illustration of a method for validating data provided by an on-board diagnostic system of a vehicle.
  • a method for validating data provided by an on-board diagnostic (OBD) system 10 of a vehicle 12 are sketched.
  • OBD on-board diagnostic
  • Most steps of this method are conducted by an off-vehicle device 14, which is sketched as an off-vehicle server unit.
  • the off-vehicle device 14 receives data related to the vehicle 12.
  • the received data comprise a first data element 16.
  • the first data element 16 is provided by the OBD system 10 of the vehicle 12. It is received by the off-vehicle device 14, which can be designed as an analysis device connected with the OBD system 10.
  • the first data element 16 can be received by a mobile communication device 42 and/or by the off-vehicle server unit, as it is sketched in the only Fig.
  • the data related to the vehicle 12 received by the off-vehicle device 14 also comprises a further data element 18.
  • Further data element 18 is also provided by the OBD system 10.
  • an evaluation step is taking place in step S2.
  • This evaluating step takes place in an evaluation unit 20 of the server unit as off-vehicle device 14.
  • the first data element 16 and the further data element 18 are evaluated according to a correlation rule 22. This is done in order to provide a probability value 24 that characterizes a probability with which the first data element 16 is manipulation-free.
  • the correlation rule 22 comprises a specific data element value range for the data element 18 that is correlated with a first data element value of the received first data element 16.
  • the first data element 16 is here as an example an odometer reading value given by the OBD system 10.
  • the further data element 18 is here a position value provided by a global navigation satellite system (GNSS) describing at least one position to which the vehicle 12 has been travelled. Based on GNSS data as further data elements 18, the total distance driven by the vehicle 12 can be approximated, i.e., the odometer reading value. There should thus be a correlation between the value of the further data element 18 and the first data element 16.
  • GNSS global navigation satellite system
  • the corresponding probability value 24 characterizes that the first data element 16 is supposed to be manipulation-free. Because if the provided probability value 24 is in a specific probability value range 26, the validation of the data provided by the OBD system 10 is confirmed. This takes place in step S3. In the only Fig., the specific probability value range 26 is sketched as a value range of a data graph between two dashed lines. In situation A, the probability value 24 is in the specific probability value range 26. Hence, validation of the data provided by the OBD system 10 is given in situation A.
  • a certification signal 28 is created in step S4.
  • the certification signal 28 indicates that data provided by the OBD system 10 is confirmed valid.
  • the created certification signal 28 is kept for retrieval stored in a memory unit 30.
  • the memory unit 30 is the off-vehicle device 14, i.e., the server unit. More precisely, the created certification signal 28 is stored in the memory unit 30 of the off-vehicle device 14.
  • the validation of the data provided by the OBD system 10 cannot be confirmed. This can result in creating a warning signal 32 indicating the data provided by the OBD system 10 is not confirmed valid and thus confirmed invalid.
  • the warning signal 32 can also be stored in the memory unit 30 for further retrieval.
  • the off-vehicle equipment 34 is preferably an off-vehicle sensor device like a weather station.
  • This weather station can provide additional further data elements 18' that are for example a measured rainfall volume value as well as a measured temperature.
  • another vehicle 36 can provide sensor data from a sensor unit 38 of the other vehicle 36. This could be a temperature data measured by the other sensor unit 38 of the other vehicle 36 that is provided as further data element 18". This data can now additionally be taken into account.
  • GNSS data as a further data element 18 also temperature data measured by a sensor of the vehicle 12 as well as rain indication data signaling that rain has been monitored to be fallen on a windshield of the vehicle 12 are also taken into account.
  • additional vehicle data are both provided as further data elements 18 provided by the OBD system 10 of the vehicle 12. All of this allows for cross-validation of the temperature data determined by the other vehicle 36 (i.e. further data element 18") with the temperature data provided by the OBD system 10 of the vehicle 12 as well as cross-validation of the information on rainfall in general provided by the OBD system 10 (i.e. further data element 18) with the data from the weather station as off-vehicle equipment 34 (i.e. further data element 18'). If now still all information match meaning that the evaluation step S2 and S3 result in a positive result as it is the case in situation A, an especially reliable certification signal 28 can be provided for the vehicle 12.
  • the data related to the vehicle 12 is only received by the off-vehicle device 14 upon receiving a request signal 40.
  • the request signal 40 can be provided by the mobile communication device 42 of a person. Alternatively, it could also be provided as an automatically generated request signal 40 generated by a vehicle seller platform, a manufacturer, and/or the server unit.
  • the request signal 40 could also be created at a randomly selected point in time 44 meaning that there is no indication for an upcoming request signal 40 so that the time when the data related to the vehicle 12 is received and evaluated is not known in advance.

Landscapes

  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Traffic Control Systems (AREA)

Claims (4)

  1. Procédé de validation de données fournies par un système de diagnostic embarqué (10) d'un véhicule (12), le procédé comprenant :
    - la réception de données relatives au véhicule (12), lesdites données reçues comprenant un premier élément de données (16), qui est constitué de données GNSS fournies par le système de diagnostic embarqué (10) du véhicule (12), ainsi que des éléments de données supplémentaires (18), lesdits éléments de données supplémentaires (18) étant des données relatives aux précipitations totales et à la température actuelle fournies par le système de diagnostic embarqué (10) du véhicule (12) et une station météorologique locale, le premier élément de données (16) et les éléments de données supplémentaires (18) étant acquis simultanément (S1) ;
    - l'évaluation du premier élément de données (16) et des éléments de données supplémentaires (18) selon une règle de corrélation (22) afin de fournir une valeur de probabilité (24) caractérisant une probabilité que le premier élément de données (16) soit exempt de manipulation, le procédé comprenant une corrélation croisée entre les données relatives aux précipitations totales et à la température actuelle provenant de la station météorologique locale, et les données relatives aux précipitations totales et à la température actuelle provenant du système de diagnostic embarqué (10), et la règle de corrélation (22) comprenant une plage de valeurs spécifique d'élément de données pour les éléments de données supplémentaires (18), ladite plage étant fonction d'une valeur actuelle du premier élément de données reçu (S2) ;
    - si la valeur de probabilité (24) fournie se situe dans une plage spécifique de valeurs de probabilité (26),
    • la confirmation de la validation des données fournies par le système de diagnostic embarqué (10) (S3) par la création d'un signal de certification (28) indiquant que les données fournies par le système de diagnostic embarqué (10) sont confirmées comme étant valides (S4) et la conservation du signal de certification (28) créé dans une unité de mémoire (30) pour qu'il puisse être récupéré ultérieurement (S5), et
    • la vérification, en outre, d'une valeur du relevé de l'odomètre fournissant des informations sur la distance totale parcourue par le véhicule (12) jusqu'à présent, par validation croisée avec les données GNSS fournies par le système de diagnostic embarqué (10), sur la base desquelles une longueur totale parcourue avec le véhicule (12) est estimée,
    dans lequel un dispositif non embarqué (14), conçu comme un ordinateur, reçoit et évalue le premier élément de données (16) et les éléments de données supplémentaires (18).
  2. Procédé selon la revendication 1, dans lequel le dispositif non embarqué (14) est un dispositif d'analyse connecté au système de diagnostic embarqué (10), un dispositif de communication mobile (42) et/ou une unité serveur (14).
  3. Procédé selon l'une quelconque des revendications précédentes, dans lequel les données relatives au véhicule (12) ne sont reçues que sur demande/après réception d'un signal de requête (40).
  4. Procédé selon la revendication 3, dans lequel le signal de requête (40) est créé à un instant choisi de manière aléatoire (44).
EP19195618.4A 2019-09-05 2019-09-05 Validation de données fournies par un système de diagnostic embarqué Active EP3789971B1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP19195618.4A EP3789971B1 (fr) 2019-09-05 2019-09-05 Validation de données fournies par un système de diagnostic embarqué

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
EP19195618.4A EP3789971B1 (fr) 2019-09-05 2019-09-05 Validation de données fournies par un système de diagnostic embarqué

Publications (2)

Publication Number Publication Date
EP3789971A1 EP3789971A1 (fr) 2021-03-10
EP3789971B1 true EP3789971B1 (fr) 2025-11-05

Family

ID=67874340

Family Applications (1)

Application Number Title Priority Date Filing Date
EP19195618.4A Active EP3789971B1 (fr) 2019-09-05 2019-09-05 Validation de données fournies par un système de diagnostic embarqué

Country Status (1)

Country Link
EP (1) EP3789971B1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040225557A1 (en) * 2003-05-06 2004-11-11 Joseph Phelan Motor vehicle operating data collection and analysis
DE102018101523A1 (de) * 2018-01-24 2019-07-25 Bayerische Motoren Werke Aktiengesellschaft Verfahren und Vorrichtung zum Speichern von Wegstreckendaten

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101860966B1 (ko) 2010-06-23 2018-07-05 콘티넨탈 테베스 아게 운트 코. 오하게 가속 물체 인식 및/또는 가속 물체 속성 인식을 위한 방법 및 시스템 그리고 그 방법의 이용
US9830662B1 (en) * 2013-03-15 2017-11-28 State Farm Mutual Automobile Insurance Company Split sensing method
US20150088618A1 (en) * 2013-08-26 2015-03-26 Ims Solutions, Inc. Road tolling
US10181228B2 (en) * 2016-02-08 2019-01-15 Allstate Insurance Company Telematics authentication
EP3229437A1 (fr) * 2016-04-07 2017-10-11 Walter Steven Rosenbaum Dispositif de communication et procédé de protection d'un système de communication contre l'application d'un code non autorisé

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040225557A1 (en) * 2003-05-06 2004-11-11 Joseph Phelan Motor vehicle operating data collection and analysis
DE102018101523A1 (de) * 2018-01-24 2019-07-25 Bayerische Motoren Werke Aktiengesellschaft Verfahren und Vorrichtung zum Speichern von Wegstreckendaten

Also Published As

Publication number Publication date
EP3789971A1 (fr) 2021-03-10

Similar Documents

Publication Publication Date Title
EP3262618B1 (fr) Procédés et systèmes pour générer et délivrer des scripts d'essai de conduite pour des véhicules
CN110300686B (zh) 数据分析装置及存储介质
US8653953B2 (en) Odometer verification and reporting using a telematics-equipped vehicle
US6732031B1 (en) Wireless diagnostic system for vehicles
US11240211B2 (en) System and method to leverage EDR, ECU, CAN and OBD data from vehicles by means of blockchain technology
US20110093159A1 (en) System for processing data acquired from vehicle diagnostic interface for vehicle inventory monitoring
CN107944899A (zh) 基于远程信息处理的车辆价值报告
CN112805687B (zh) 信息处理装置、异常分析方法以及记录介质
US20090150118A1 (en) Method and apparatus for secure wireless tracking and control
CA2689110A1 (fr) Compilation de donnees d'origine provenant du systeme informatique d'un vehicule automobile et configuration d'un module de telematique
EP2930697A1 (fr) Procédé et dispositif pour traiter des données d'état d'un véhicule
US20200160407A1 (en) Server apparatus and information providing method
CN113011852A (zh) 车辆保养提醒方法、装置、车载设备及存储介质
US20170262820A1 (en) Smart transport solution
KR20200057620A (ko) 서버 장치 및 정보 제공 방법
EP3789970B1 (fr) Procédé de validation d'identité associé à un véhicule
US20200159199A1 (en) Server apparatus and information providing method
EP3789968B1 (fr) Procédé de validation de données d'un véhicule désigné
EP3789971B1 (fr) Validation de données fournies par un système de diagnostic embarqué
JP2023022757A (ja) サーバ、システム、及び端末装置のプログラム
KR20050117076A (ko) 스마트카드를 이용한 자동차 가치 산정 시스템 및 방법
CN115451997B (zh) 里程检测方法、装置、电子设备及计算机存储介质
EP3142078B1 (fr) Unité centrale, système de péage routier et procédés pour faire fonctionner un système de péage routier et une unité centrale
DK2772886T3 (en) Electronic onboard-vehicle system and test method thereof
CN113037854A (zh) 机动车尾气的监测方法、装置、设备及存储介质

Legal Events

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

Free format text: ORIGINAL CODE: 0009012

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

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20200429

AK Designated contracting states

Kind code of ref document: A1

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

AX Request for extension of the european patent

Extension state: BA ME

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

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20210611

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

Effective date: 20230529

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

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

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20250807

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

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

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

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

REG Reference to a national code

Ref country code: CH

Ref legal event code: F10

Free format text: ST27 STATUS EVENT CODE: U-0-0-F10-F00 (AS PROVIDED BY THE NATIONAL OFFICE)

Effective date: 20251105

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602019077678

Country of ref document: DE

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20251105

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

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

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

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

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

Ref country code: AT

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

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

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

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1855237

Country of ref document: AT

Kind code of ref document: T

Effective date: 20251105

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

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

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

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

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

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

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