WO2022128135A1 - Système et procédé de vérification de la précision de données de tachygraphe - Google Patents

Système et procédé de vérification de la précision de données de tachygraphe Download PDF

Info

Publication number
WO2022128135A1
WO2022128135A1 PCT/EP2020/087318 EP2020087318W WO2022128135A1 WO 2022128135 A1 WO2022128135 A1 WO 2022128135A1 EP 2020087318 W EP2020087318 W EP 2020087318W WO 2022128135 A1 WO2022128135 A1 WO 2022128135A1
Authority
WO
WIPO (PCT)
Prior art keywords
vehicle
data
tachograph
driver
public
Prior art date
Application number
PCT/EP2020/087318
Other languages
English (en)
Inventor
Martin Wennerblom
Original Assignee
Stoneridge Electronics Ab
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 Stoneridge Electronics Ab filed Critical Stoneridge Electronics Ab
Priority to EP20838485.9A priority Critical patent/EP4264575A1/fr
Priority to PCT/EP2020/087318 priority patent/WO2022128135A1/fr
Publication of WO2022128135A1 publication Critical patent/WO2022128135A1/fr

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/008—Registering or indicating the working of vehicles communicating information to a remotely located station
    • 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
    • G07C5/0841—Registering performance data
    • G07C5/085—Registering performance data using electronic data carriers

Definitions

  • This application relates to vehicles, and more particularly to a system and method for verifying the accuracy of tachograph data.
  • Tachographs are devices commonly used by drivers of commercial vehicles to record data about operation of the vehicles, such as speed, hours of operation, etc. Government regulations require drivers of commercial vehicles to record the number of hours driven in given time period as part of maintaining an hours-of-service (HOS) log. Such logs are meant to ensure that drivers do not exceed a maximum number of permitted driving hours in the given time period. Historically, this has involved drivers maintaining cumbersome paper-based non-electronic logs. More recently, tachograph devices have been used to record vehicle operational data, which can eventually be analyzed for compliance with government regulations. For example, a tachograph device may have a multiple operational modes, such as a rest mode in which a driver is resting, and a drive mode in which the driver is operating the vehicle.
  • HOS hours-of-service
  • tachographs have generally relied on measures such as tamper proof seals, which if broken indicate that a tachograph may have been tampered with.
  • a method includes recording, by a computing device in a first vehicle and for each of a plurality of time periods, tachograph data that describes operation of the first vehicle during the time period in a private data set and a separate public data set that is different from the private data set.
  • the method includes, based on the first vehicle being within a vehicle-to-vehicle (V2V) communication range of a second vehicle, using V2V signaling to transmit one or more of the public data sets to the second vehicle and receive one or more public data sets from the second vehicle containing tachograph data that describes operation of the second vehicle.
  • the method includes uploading, by the computing device, the private data sets of the first vehicle and the one or more public sets from the second vehicle to a server for further analysis.
  • V2V vehicle-to-vehicle
  • each public data set corresponds to a private data set and is an abbreviated form of the private data set that omits one or more pieces of information from the private data set.
  • the one or more pieces of information that are omitted from the private data set for a vehicle includes at least one of an identifier of a driver of the vehicle and driver activity data for the driver.
  • the method includes the computing device digitally signing at least the one or more public data sets from the second vehicle prior to uploading the one or more public data sets to the server.
  • the V2V communication range is a Dedicated Short-Range Communication (DSRC) range and the V2V signaling includes DSRC signaling.
  • DSRC Dedicated Short-Range Communication
  • the uploading to the server includes uploading to a Roadside Unit using DSRC.
  • the private data set of the first vehicle identifies a driver of the first vehicle
  • the public data set of the first vehicle does not identify the driver of the first vehicle
  • the public data set of the second vehicle does not identify a driver of the second vehicle.
  • the tachograph data in each public and private data set for a particular time period for a vehicle includes a time stamp that indicates the particular time period, a speed of the vehicle during the particular time period, a location of the vehicle during the particular time period, and an identifier of the vehicle.
  • the tachograph data in each private data set for the particular time period for the vehicle also includes driver activity data for a driver of the vehicle, the driver activity data including at least one of the following: a distance driven by the driver during the particular time period, a time of a last break of the driver, and a time that has elapsed since a most recent rest period for the driver.
  • a method includes receiving first tachograph data from a first vehicle that describes operation of the first vehicle during a first time period, receiving second tachograph data from a second vehicle that is separate from the first vehicle wherein the second tachograph data describes operation of the first vehicle during the first time period, and analyzing accuracy of the first tachograph data based on whether the second tachograph data matches the first tachograph data.
  • a further embodiment of any of the foregoing embodiments includes further basing the analyzing on at least one of whether the first tachograph data is properly signed by the first vehicle, and whether the second tachograph data is properly signed by the second vehicle.
  • a further embodiment of any of the foregoing embodiments includes receiving third tachograph data from the first vehicle that describes operation of the second vehicle during a second time period, receiving fourth tachograph data from the second vehicle that describes operation of the second vehicle during the second time period, and analyzing accuracy of the fourth tachograph data based on whether the third tachograph data matches the fourth tachograph data.
  • the second tachograph data includes fewer types of information than the first tachograph data; and the third tachograph data includes fewer types of information than the fourth tachograph data.
  • the first tachograph data includes an identifier and driver activity data for a first driver of the first vehicle during the first time period
  • the fourth tachograph data includes an identifier and driver activity data for a second driver of the second vehicle during the second time period
  • the second tachograph data omits the identifier and driver activity data for the first driver
  • the third tachograph data omits the identifier and driver activity data for the second driver.
  • a tachograph system for a first vehicle includes a Global Navigation Satellite System (GNSS) transceiver configured to determine a location of the first vehicle, at least one wireless transceiver, memory, and processing circuitry operatively connected to the GNSS transceiver, at least one wireless transceiver, and memory.
  • the processing circuitry is configured to record, during each of a plurality of time periods, tachograph data that describes operation of the first vehicle during the time period in a private data set and a separate public data set that is different from the private data set.
  • the processing circuitry is configured to, based on the first vehicle being within a vehicle-to-vehicle (V2V) communication range of a second vehicle, use the one or more wireless transceivers to transmit one or more of the public data sets to the second vehicle, and receive one or more public data sets from the second vehicle containing tachograph data that describes operation of the second vehicle.
  • the processing circuitry is configured to utilize the at least one wireless transceiver to upload the private and public sets of the first vehicle and the one or more public sets of the second vehicle to a server for analysis.
  • the at least one wireless transceiver includes a Dedicated Short Range Communication (DSRC) transceiver
  • the processing circuitry is configured to use the DSRC transceiver for at least transmitting and receiving the public data sets with the second vehicle.
  • DSRC Dedicated Short Range Communication
  • the processing circuitry is configured to use the DSRC transceiver to upload the public and private data sets to the server via vehicle-to-infrastructure (V2I) communication.
  • V2I vehicle-to-infrastructure
  • the at least one wireless transceiver includes a cellular transceiver; and the processing circuitry is configured to use the cellular transceiver to upload the public and private data sets to the server.
  • each public data set corresponds to a private data set and is an abbreviated form of the private data set that omits one or more pieces of information from the private data set, and the one or more pieces of information that are omitted from the private data set for a vehicle includes at least one of a driver identifier and driver activity data for a driver of the vehicle.
  • the processing circuitry is configured to digitally sign at least the one or more public data sets from the second vehicle prior to uploading the one or more public data sets to the server.
  • Figure 1 is a schematic view of a system for verifying the accuracy of tachograph data.
  • Figure 2 is a schematic view of an example tachograph device of Figure 1.
  • Figure 3 is a schematic view of a server of the system of Figure 1.
  • Figure 4A schematically illustrates an example private data set for the system of Figure 1.
  • Figure 4B schematically illustrates an example public data set for the system of Figure 1.
  • Figure 5 is a flowchart of an example method of bundling tachograph data for verification by a server.
  • Figure 6 schematically illustrates two combined data sets that include tachograph data for multiple vehicles.
  • Figure 7 is a flowchart of an example method of verifying tachograph data.
  • Figure 1 is a schematic view of a system 10 for verifying the accuracy of tachograph data.
  • the system includes a plurality of vehicles 12. Although only two vehicles 12A-B are shown in Figure 1, it is understood that many more vehicles could be part of the system 10.
  • Each vehicle 12A-B includes a respective tachograph device 14A-B which is also schematically shown in Figure 1.
  • the tachograph devices 14 are operable to record data describing operation of their respective vehicles 12, such as speed, location, and driver activity data (e.g., amount of driving within a predefined time period, amount of time since a last rest, etc.).
  • the tachograph devices 14 are configured to, when the vehicles 12 are within a vehicle- to-vehicle communication range of each other (e.g., a Dedicated Short-Range Communication “DSRC” range), exchange tachograph data sets with each other.
  • Each tachograph device 14 is configured to upload its own tachograph data and that received from another vehicle to a server 16 through a wide area network (WAN) 18 such as the Internet.
  • WAN wide area network
  • the upload may occur via a base station 20 and/or road side units (RSUs) 22 through vehicle-to-infrastructure (V2I) signaling.
  • RSUs road side units
  • V2I vehicle-to-infrastructure
  • DSRC vehicle-to-infrastructure
  • FIG. 2 is a schematic view of an example tachograph device 14.
  • the tachograph device 14 includes processing circuitry 30 operatively connected to memory 32, a global navigation satellite system (GNSS) receiver 34, a cellular transceiver 36, a DSRC transceiver 38, a Bluetooth transceiver 40, an electronic display 42, and a data port 44.
  • GNSS global navigation satellite system
  • the processing circuitry 30 includes one or more microprocessors, microcontrollers, application specific integrated circuits (ASICs), or the like, for example.
  • the memory 32 stores a repository of tachograph data, and can include any one or combination of volatile memory elements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM, VRAM, etc.)) and/or nonvolatile memory elements (e.g., ROM, hard drive, tape, CD-ROM, etc.).
  • RAM random access memory
  • SRAM static random access memory
  • SDRAM Secure Digital RAM
  • VRAM electrically programmable read-only memory
  • the memory 32 may incorporate electronic, magnetic, optical, and/or other types of storage media.
  • the memory 32 can also have a distributed architecture, where various components are situated remotely from one another, but can be accessed by the processing circuitry 30.
  • the GNSS receiver 34 (e.g., a GPS receiver) is configured to determine a location of the tachograph device 14, which is indicative of a location of the vehicle 12 associated with the tachograph device 14.
  • the processing circuitry 30 is configured to use GNSS data from the GNSS receiver 34 to determine a speed of the vehicle 12.
  • the cellular transceiver 36 is configured to transmit vehicle operation data to the server 16 via the base station 20.
  • the cellular transceiver 36 is configured to communicate using a cellular communication standard, such as one or more 3 GPP standards (e.g., GSM, W-CDMA, LTE, LTE-M, LTE-A, etc.) and/or one or more IEEE standards (e.g., WiMAX).
  • 3 GPP standards e.g., GSM, W-CDMA, LTE, LTE-M, LTE-A, etc.
  • IEEE standards e.g., WiMAX
  • the DSRC transceiver 38 is configured to communicate with the RSUs 22 and/or with other vehicles 12 for exchanging tachograph data.
  • the Bluetooth transceiver 40 is configured to communicate with a mobile device of a driver (not shown), such as for authenticating the driver and determining a proper driver ID to use for tachograph data records.
  • the Bluetooth transceiver 40 is configured to communicate with other vehicles 12 for exchanging tachograph data.
  • the tachograph device 14 includes a receptacle (not shown) for receiving a smart card that identifies a driver.
  • the authentication with a mobile device may implicate a dedicated application on the mobile device, and/or biometric authentication (e.g., fingerprint, iris scan, facial recognition, etc.).
  • biometric authentication e.g., fingerprint, iris scan, facial recognition, etc.
  • the biometric information and/or authentication may be obtained through software on from the driver’s mobile device.
  • the electronic display 42 is configured to display data to a driver of the vehicle 12, such as tachograph data (e.g., an amount of time until a break is needed).
  • tachograph data e.g., an amount of time until a break is needed.
  • the data port 44 is connected to a vehicle information bus 46, such as a Controller Area Network (CAN) bus, for obtaining vehicle operation information, such as vehicle speed, engine status, etc.
  • vehicle information bus 46 such as a Controller Area Network (CAN) bus
  • vehicle operation information such as vehicle speed, engine status, etc.
  • ODB on-board diagnostics
  • RP 1226 telematics port
  • FIG 3 is a schematic view of the server 16 of Figure 1.
  • the server 16 includes processing circuitry 62 operatively connected to memory 64 and a communication interface.
  • the processing circuitry 62 and memory 64 may include any of the hardware features discussed above in connection with the processing circuitry 30 and memory 32, respectively.
  • the communication interface 66 is configured to communicate over the WAN 18, and may include a ethernet or WiFi transceiver, for example.
  • Figure 4A schematically illustrates an example private data set 70A of tachograph data
  • Figure 4B schematically illustrates an example public data set 70B of tachograph data.
  • the tachograph device 14 is operable to record tachograph data in the private data sets 70A and public data sets 70B for a plurality of time periods. In one example, this happens periodically (e.g., on the order of every 10 seconds).
  • Each data set 70 includes tachograph data that describes operation of the vehicle 12 during the time period.
  • the example private data set 70A for a vehicle includes a plurality of types of tachograph data, including a time stamp 72, a speed 74 of the vehicle 12, a location 76 of the vehicle, a vehicle identifier (ID) 78, a driver ID 80, additional vehicle details 82 (e.g., vehicle weight), and drive activity records 84 (e.g., time since last break, number of hours driven in a 24 hour period, etc.).
  • ID vehicle identifier
  • driver ID 80 e.g., vehicle weight
  • drive activity records 84 e.g., time since last break, number of hours driven in a 24 hour period, etc.
  • the example public data set 70B includes the time stamp 72, vehicle speed 74, vehicle location 76, and vehicle ID 79.
  • the public data set 70B corresponds to the private data set 70 A, but omits one or more types of information from the private data set 70A. This may include one or more types of information that identify a driver of the vehicle 12, for example.
  • the public data set 70B omits the driver ID 80, vehicle additional details 82 (e.g., vehicle weight), and driver activity records 84.
  • the server 16 uses the public data set 70B to analyze the accuracy of the tachograph data in the private data set 70 A.
  • FIG. 5 is a flowchart 100 of an example method of bundling tachograph data for verification by the server 16.
  • the tachograph device 14 of a first vehicle e.g., vehicle 12A
  • the tachograph device 14 determines whether the first vehicle is within a vehicle-to-vehicle (V2V) communication range of a second vehicle (e.g., vehicle 12B) (step 104). This may occur if the vehicles 12A-B are heading in a same direction, and one is passing the other, for example.
  • V2V vehicle-to-vehicle
  • the first vehicle uses V2V communication to exchange one or more public data sets with the second vehicle (step 106).
  • the V2V communication range is a DSRC range
  • the V2V signaling includes DSRC signaling utilizing the DSRC transceiver 38.
  • the first vehicle digitally signs at least the one or more public data sets from the second vehicle (e.g., using known public key infrastructure PKI techniques).
  • the first vehicle digitally signs one or more of the first private data sets 70 A that include its own tachograph data and also one or more of the second public data sets 70B that include tachograph data of the second vehicle in a combined data set (step 108), and uploads the combined data set to the server 16 for further analysis (step 110).
  • the upload of step 110 could be an upload to an RSU 22 through DSRC signaling by the DSRC transceiver 38 and/or an upload to the cellular base station 20 using the cellular transceiver 36, for example.
  • the first vehicle also digitally signs its own public data set that includes tachograph data of the first vehicle prior to transmitting that public data set to the second vehicle.
  • the combined data set of step 108 is a binary large object or “blob.”
  • the second vehicle can also perform the steps of Figure 5, so that each vehicle transmits its own public data set containing its own tachograph data and receives the public data set of the other vehicle containing the tachograph data of the other vehicle.
  • neither public data set identifies the driver at issue, but instead identifies the vehicle, to provide a degree of anonymity for the driver.
  • Figure 6 schematically illustrates two combined data sets 90A and 90B.
  • the combined datasets 90A-B may be blobs in one example.
  • the first combined data set 90A includes private tachograph data 92A of vehicle 12A as recorded by vehicle 12B, and also includes public tachograph data 94B of vehicle 12B that is received from tachograph device 14B (e.g., using V2V signaling).
  • the second combined data set 90B includes private tachograph data 92B of vehicle 12B as recorded by vehicle 12B, and also includes public tachograph data 94A of vehicle 12A that is received from tachograph device 14A (e.g., using V2V signaling).
  • Figure 7 is a flowchart 200 of an example method of verifying tachograph data that is performed by a computing device, such as the server 16.
  • the computing device receives first tachograph data from a first vehicle (e.g., vehicle 12A) that describes operation of the first vehicle during a first time period (step 202).
  • first vehicle e.g., vehicle 12A
  • this includes portion 92A of the combined data set 90A shown in Figure 6.
  • the computing device also receives second tachograph data from the second vehicle (e.g., vehicle 12B) that is separate from the first vehicle, the second tachograph data describing operation of the first vehicle during the first time period (step 204). In one example, this includes portion 94A of the combined data set 90B. [0060]
  • the computing device analyzes accuracy of the first tachograph data (e.g., private tachograph data 92A) based on whether the second tachograph data (e.g., public tachograph data 94A) matches the first tachograph data (step 206). The analysis may also be based on the additional data in the combined data sets (e.g., whether the tachograph data 92B is consistent with the tachograph data 92 A).
  • step 206 could include any one or combination of the following, for example:
  • Verifying that the second tachograph data (e.g., public tachograph data 94A) is also present in the first tachograph data (e.g., private tachograph data 92A).
  • Verifying that a location of the first vehicle in the first tachograph data (e.g., private tachograph data 92A) is within a predefined distance of a location of the second vehicle in the private tachograph data 92B during the time indicated by a time stamp in the tachograph data 92 A, 92B.
  • a time stamp of the tachograph data 92A and tachograph data 94A is a time period during which driver activity records 84 in the tachograph data 92A indicate that the driver was driving the vehicle.
  • the method can also be performed to analyze the accuracy of the tachograph data 92B, 94B in a reciprocal manner.
  • the computing device receives third tachograph data from the first vehicle that describes operation of the second vehicle (e.g., tachograph data 94B), and receives fourth tachograph data from the second vehicle that describes operation of the second vehicle during the second time period (e.g., tachograph data 94A), and then analyzes the accuracy of the fourth tachograph data based on whether it matches the third tachograph data.
  • the analysis of step 206 may also include verifying that tachograph data (e.g., 92A-B and/or 94A-B) is properly signed. If tachograph data is not properly signed, that may be an indicator that the data set has been tampered with and/or falsified to avoid compliance with government regulations.
  • tachograph data e.g., 92A-B and/or 94A-B
  • the computing device that performs the method 200 discards the public tachograph data 94A-B after the public tachograph data 94A-B has been used to verify its corresponding private tachograph data 92A-B (e.g., after the method of flowchart 200 is performed to verify the private tachograph data 92A and to verify the tachograph data 92B).
  • the system and methods described herein provide for a flexible, open, and secure way of verifying the accuracy of tachograph data.
  • the techniques discussed herein do not require the costly sealing and tamperproofing of physical tachograph devices that is currently performed in the prior art.
  • vendors may opt out of using centralized key management, which can be costly. These cost saving measures reduce the cost of enforcement, and can also be readily retrofitted into existing vehicles.

Landscapes

  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Traffic Control Systems (AREA)
  • Time Recorders, Dirve Recorders, Access Control (AREA)

Abstract

Un procédé selon un exemple de la présente divulgation consiste à enregistrer, par un dispositif informatique dans un premier véhicule et pour chacune d'une pluralité de périodes, des données de tachygraphe qui décrivent le fonctionnement du premier véhicule pendant la période dans un ensemble de données privées et un ensemble de données publiques distinct qui est différent de l'ensemble de données privées. Le procédé consiste, sur la base du premier véhicule qui se trouve dans une plage de communication V2V d'un second véhicule, à utiliser une signalisation V2V permettant de transmettre un ou plusieurs des ensembles de données publiques au second véhicule et de recevoir un ou plusieurs ensembles de données publiques du second véhicule contenant des données de tachygraphe qui décrivent le fonctionnement du second véhicule. Le procédé consiste à télécharger, par le dispositif informatique, les ensembles de données privées du premier véhicule et du ou des ensembles publics du second véhicule vers un serveur pour une analyse ultérieure.
PCT/EP2020/087318 2020-12-18 2020-12-18 Système et procédé de vérification de la précision de données de tachygraphe WO2022128135A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20838485.9A EP4264575A1 (fr) 2020-12-18 2020-12-18 Système et procédé de vérification de la précision de données de tachygraphe
PCT/EP2020/087318 WO2022128135A1 (fr) 2020-12-18 2020-12-18 Système et procédé de vérification de la précision de données de tachygraphe

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2020/087318 WO2022128135A1 (fr) 2020-12-18 2020-12-18 Système et procédé de vérification de la précision de données de tachygraphe

Publications (1)

Publication Number Publication Date
WO2022128135A1 true WO2022128135A1 (fr) 2022-06-23

Family

ID=74141528

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2020/087318 WO2022128135A1 (fr) 2020-12-18 2020-12-18 Système et procédé de vérification de la précision de données de tachygraphe

Country Status (2)

Country Link
EP (1) EP4264575A1 (fr)
WO (1) WO2022128135A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1271448A1 (fr) * 2001-06-20 2003-01-02 Siemens Aktiengesellschaft Procédé pour un tachygraphe de véhicule au moyen de communication radio
WO2009015989A1 (fr) * 2007-07-30 2009-02-05 Robert Bosch Gmbh Procédé de contrôle d'un message de position du véhicule émis par un véhicule et un émetteur-récepteur destiné à être utilisé dans un véhicule
EP2472270A1 (fr) * 2011-01-04 2012-07-04 Scania CV AB Procédé et système de vérification de vitesse

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1271448A1 (fr) * 2001-06-20 2003-01-02 Siemens Aktiengesellschaft Procédé pour un tachygraphe de véhicule au moyen de communication radio
WO2009015989A1 (fr) * 2007-07-30 2009-02-05 Robert Bosch Gmbh Procédé de contrôle d'un message de position du véhicule émis par un véhicule et un émetteur-récepteur destiné à être utilisé dans un véhicule
EP2472270A1 (fr) * 2011-01-04 2012-07-04 Scania CV AB Procédé et système de vérification de vitesse

Also Published As

Publication number Publication date
EP4264575A1 (fr) 2023-10-25

Similar Documents

Publication Publication Date Title
US11386431B1 (en) Driver activity and vehicle operation logging and reporting
US11763607B2 (en) Automatically identifying drivers
US20220351557A1 (en) Telematics authentication
CN111295862B (zh) 用于密码地保证车辆身份的系统和方法
US11335130B2 (en) Method for checking toll transactions and components therefor
US8653953B2 (en) Odometer verification and reporting using a telematics-equipped vehicle
US11657704B2 (en) Event data collections for accidents
US7117075B1 (en) Driver activity and vehicle operation logging and reporting
US20120166018A1 (en) Method for data communication between a vehicle and fuel pump
US11869093B2 (en) Driving patterns
US20150371457A1 (en) Method and system for retrieving vehicular parameters from a vehicle data bus
EP3021288B1 (fr) Procédé et appareil d'enregistrement de confiance dans un système de péage routier
NO20160003A1 (en) System and Method for charging means of transport
JP4046013B2 (ja) 車両用ドライブレコーダ，車両分析装置、および鍵管理方法
WO2022128135A1 (fr) Système et procédé de vérification de la précision de données de tachygraphe
EP3858807A1 (fr) Procédé et système de gestion de données générées de véhicule
CN113240828A (zh) 一种基于WiFi/蓝牙的汽车行驶记录仪查验检验方法及装置
US20240061917A1 (en) Driving record authentication method, electronic device, storage medium
KR20200076570A (ko) 스마트 앱 기반 차량 운행기록 관리 시스템
KR102313616B1 (ko) 모바일 dtg를 통한 차량 운행기록 제공 시스템 및 그 방법
TW202409958A (zh) 行駛記錄認證方法、電子設備、儲存介質、交通工具
NZ605057B2 (en) A driver related data storage system and method

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20838485

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020838485

Country of ref document: EP

Effective date: 20230718