Method and system for communicating vehicle diagnostic data

Abstract

The present invention relates to a method and a system for communicating diagnostic data of a vehicle (10) comprising an OBD port (101) configured to connect a diagnostic system (11) to an on-board computer network of the vehicle (10). For this purpose, a request for access to the on-board network is transmitted to a server (110) with identification data of the vehicle (10) and OEM identification data. The server determines a subscription status to a service for accessing the diagnostic data of the vehicle (10) based on the identification data of the vehicle (10) and the OEM identification data. Depending on the subscription status, configuration data of the diagnostic system are transmitted to the diagnostic system (11) to enable the diagnostic system (11) to retrieve the diagnostic data from the on-board computer network of the vehicle (10). Figure for abstract: Figure 1

Description

Title of the invention: Method and system for communicating diagnostic data of a vehicle Technical field

[0001] The invention relates to methods and systems for communicating diagnostic data of a vehicle, in particular but not exclusively a motor vehicle. The invention relates in particular to a method and a system for activating access rights to diagnostic data for a vehicle. Technological background

[0002] Contemporary vehicles are equipped with a so-called diagnostic port configured so that a diagnostic system or tool can connect to the vehicle's computer network, also known as an on-board system. The vehicle's on-board system is equipped with an on-board diagnostic service or system, known as OBD (from the English "On-Board Diagnostic"), configured to monitor the vehicle's systems in operation, to record and transmit performance data in real time and to perform self-diagnosis in order to detect problems with the vehicle's systems and to issue fault codes, known as DTC (from the English "Data Trouble Code"). An automotive technician uses OBD systems to quickly identify problems with a vehicle. To do this, he uses a diagnostic tool or system capable of interacting with the vehicle's OBD system.The diagnostic tool is designed in particular to retrieve DTC codes generated by the vehicle's on-board system and obtain real-time data associated with one or more parameter identification numbers, known as PIDs (from the English "Process Identifier" or in French "process identifier").

[0003] While a standard set of DTCs and PIDs are defined in many vehicles, automotive manufacturers and OEMs (Original Equipment Manufacturers) typically use non-standard or OEM-specific parameters and codes. As a result, a diagnostic tool requires software that can process the proprietary parameters and decipher the codes so that a technician can effectively diagnose vehicle problems. Due to the proprietary nature of manufacturer-specific parameters and codes, diagnostic tool software is OEM-specific, and it is very expensive to acquire diagnostic tools to diagnose vehicles of different types and makes.

[0004] Furthermore, as proprietary extensions to standard DTC and PID codes are Under the direct control of manufacturers, these non-standard codes and parameters may differ between different models produced by an OEM and / or may change from year to year for the same model. Thus, software updates for diagnostic tools become necessary for technicians to properly maintain the most recent vehicle models. Often, these software updates come at a high cost, roughly equivalent to the initial investment in the software. In extreme cases, software updates may not be supported by a particular diagnostic tool. In this case, the technician must purchase a new diagnostic tool to work with the most recent vehicle models. Summary of the present invention

[0005] An object of the present invention is to solve at least one of the problems of the technological background described above.

[0006] An object of the present invention is, for example, to reduce the costs for establishing vehicle diagnostics.

[0007] According to a first aspect, the present invention relates to a method for communicating diagnostic data of a vehicle, the vehicle comprising a diagnostic port, called OBD port, the OBD port being configured to connect a diagnostic system to an on-board network of computers of the vehicle, the method comprising the following steps: - transmission, by the diagnostic system, of a request for access to the on-board network to a remote data processing device, the access request comprising vehicle identification data and identification data of an automobile manufacturer or equipment supplier, known as OEM identification data; - determination, by the remote data processing device, of a subscription status to a vehicle diagnostic data access service based on the vehicle identification data and the OEM identification data; - when the subscription status is representative of a right of access to diagnostic data, reception, by the diagnostic system from the remote data processing device, of diagnostic system configuration data, the configuration data being a function of the vehicle identification data and the OEM identification data; - configuration of the diagnostic system based on the configuration data; and - reception of diagnostic data by the diagnostic system from the vehicle's on-board computer network.

[0008] Configuring a diagnostic system based on configuration data specific and adapted to the vehicle and the OEM allows the diagnosis of any vehicle from a generic diagnostic system. Depending on the vehicle and the OEM, the generic diagnostic system is configured to be able to access and interpret diagnostic data (e.g. DTCs). Conditioning the loading of configuration data with an access right allows the OEM to verify that the diagnostic system is up to date and also allows the OEM to monetize access to diagnostic data specific to it, for example proprietary DTCs, if it wishes.

[0009] According to a variant, when the subscription status is representative of a prohibition of access to the diagnostic data, the method further comprises a step of transmitting subscription data to the diagnostic data access service to obtain the right of access.

[0010] According to another variant, the method further comprises a step of transmission, by the remote data processing device, of data activating the right of access to the on-board computer network of the vehicle.

[0011] According to another variant, the activation data further comprises data representative of a determined duration of activation of the access right.

[0012] According to an additional variant, the activation data is transmitted to the on-board computer network via a wireless link.

[0013] According to an additional variant, the activation data is transmitted to a mobile communication device in the form of a QR code via a wireless link, the method further comprising a step of reading the QR code by a camera of the vehicle.

[0014] According to a second aspect, the present invention relates to a system for communicating diagnostic data of a vehicle, the system comprising a diagnostic system, the vehicle and a remote data processing device, the diagnostic system being connected to the vehicle via a diagnostic port of the vehicle, the remote data processing device being communicatively connected to the diagnostic system, the system being configured to implement the steps of the method according to the first aspect of the present invention.

[0015] According to a variant, the remote data processing device is further connected in wireless communication to the vehicle.

[0016] According to another variant, the system further comprises a mobile communication device connected in wireless communication to the remote data processing device.

[0017] According to a third aspect, the present invention relates to a computer program which comprises instructions adapted for executing the steps of the method according to the first aspect of the present invention, in particular when the program computer is executed by at least one processor.

[0018] Such a computer program may use any programming language, and be in the form of source code, object code, or intermediate code between source code and object code, such as in a partially compiled form, or in any other desirable form.

[0019] According to a fourth aspect, the present invention relates to a computer-readable recording medium on which is recorded a computer program comprising instructions for carrying out the steps of the method according to the first aspect of the present invention.

[0020] On the one hand, the recording medium may be any entity or device capable of storing the program. For example, the medium may comprise a storage means, such as a ROM memory, a CD-ROM or a microelectronic circuit type ROM memory, or a magnetic recording means or a hard disk.

[0021] Furthermore, this recording medium may also be a transmissible medium such as an electrical or optical signal, such a signal being able to be conveyed via an electrical or optical cable, by conventional or hertzian radio or by self-directed laser beam or by other means. The computer program according to the present invention may in particular be downloaded from an Internet-type network.

[0022] Alternatively, the recording medium may be an integrated circuit in which the computer program is incorporated, the integrated circuit being adapted to perform or to be used in performing the method in question. Brief description of the figures

[0023] Other characteristics and advantages of the present invention will emerge from the description of the particular and non-limiting exemplary embodiments of the present invention below, with reference to the appended figures 1 to 3, in which:

[0024] [Fig.l] schematically illustrates a vehicle diagnostic data communication environment, according to a particular exemplary embodiment of the present invention;

[0025] [Fig.2] schematically illustrates a device of a vehicle diagnostic data communication system, according to a particular and non-limiting exemplary embodiment of the present invention.

[0026] [Fig.3] illustrates a flowchart of the different steps of a method for communicating diagnostic data from a vehicle, according to a particular and non-limiting exemplary embodiment of the present invention. Description of examples of implementation

[0027] A method and system for communicating diagnostic data of a vehicle will now be described in the following with reference to Figures 1 to 3. The same elements are identified with the same reference signs throughout the description which follows.

[0028] The terms "first(s)", "second(s)" (or "first(s)", "second(s)"), etc. are used in this document by arbitrary convention to enable different elements (such as operations, means, etc.) implemented in the embodiments described below to be identified and distinguished. Such elements may be distinct or correspond to a single element, depending on the embodiment.

[0029] [Fig. 1] schematically illustrates a diagnostic data communication environment of a vehicle 10, according to particular and non-limiting exemplary embodiments of the present invention.

[0030] The vehicle 10 corresponds for example to a vehicle with a thermal engine, with electric motor(s) or even a hybrid vehicle with a thermal engine and one or more electric motors. The vehicle 10 thus corresponds for example to a land vehicle, for example an automobile, a truck, a bus.

[0031] The vehicle 10 carries a set of computers forming an on-board computer network, also called the on-board system of the vehicle 10.

[0032] These computers form, for example, a multiplexed architecture for the implementation of various services useful for the proper functioning of the vehicle and for assisting the driver and / or passengers of the vehicle in controlling the vehicle 10 via the control of a set of systems embedded in the vehicle 10. The computers communicate and exchange data with each other via one or more computer buses, for example a communication bus of the CAN (Controller Area Network) type, CAN FD (Controller Area Network Flexible Data-Rate), FlexRay (according to the ISO 17458 standard), LIN (Local Interconnect Network) or Ethernet (according to the ISO / IEC 802-3 standard).

[0033] The vehicle 10 further comprises an OBD port 101 allowing a diagnostic tool or system 11 to connect to the on-board network of the vehicle 10 to obtain a set of diagnostic data, which include for example a set of DTC codes and / or PIDs generated by one or more computers of the on-board computer network of the vehicle 10. The OBD port 101 (or second generation OBD 2 port) corresponds to a connector or a wired communication interface (corresponding for example to a 16-pin port) or wireless (for example of the Bluetooth® or Wifi® type). When the OBD port is of the wired type, the latter corresponds to an OBD 2 connector of type A or type B, depending on the size of the vehicle 10. The pinout of the OBD port 101 varies for example depending on the brand of the vehicle 10, which requires a diagnostic tool or system 11 configured for each pinout. Some of the pins of the OBD port are reserved for the vehicle manufacturer 10 or for the automotive equipment manufacturers supplying the components of the vehicle 10, the manufacturer and the equipment manufacturer being grouped under the name OEM thereafter.

[0034] Such diagnostic data are for example transmitted according to a communication protocol such as the UDS protocol (from the English “Unified Diagnostic Services” or in French “unified diagnostic services”). Each computer of the on-board system of the vehicle 10 (or each computer of a part of the computers forming the on-board system) for example implements a UDS type service for the communication of diagnostic data (DTC codes for example).

[0035] The diagnostic tool or system 11 is connected or linked in wired or wireless communication to a computing device 12 of the computer type, which is connected to one or more remote data processing devices 110 (for example of the server type), via the “cloud” 100 (or “cloud” in French), by means of a wired or wireless network infrastructure, or via a mixed infrastructure comprising wireless communication means (for example of the WLAN type (from the English “Wireless Local Area Network” or in French “network local sans fil”, for example Wifi®) and wired communication means (for example of the Ethernet type).

[0036] According to an alternative embodiment, the diagnostic system groups together the diagnostic tool 11 and the calculation device 12, the diagnostic tool 11 being for example implemented in the form of an application installed on the calculation device 12 and executed by the calculation device 12.

[0037] According to a particular embodiment, the vehicle 10 is connected in communication to the remote data processing device 110 via the “cloud” 100, for example through a wireless communication infrastructure (for example of the Wifi® type or of the terrestrial cellular network type, for example of the LTE 4G or 5G type).

[0038] According to another particular embodiment, the remote data processing device 110 is further connected in wireless communication (Wifi® and / or terrestrial cellular network) with one or more mobile communication devices (not shown in [Fig.l]), for example of the smartphone or tablet type.

[0039] Examples of hardware implementations of the various devices forming the communication system of [Fig.l] are described in more detail below with reference to [Fig.2],

[0040] A process for communicating diagnostic data of the vehicle 10 is advantageously implemented by one or more processors of the devices forming the communication system, namely the vehicle 10, the diagnostic system 11 (and / or the computing device 12) and the data processing device 110. According to an alternative embodiment, the communication system further comprises a mobile communication device, for example a smartphone.

[0041] In a first operation of the process, identification data of the vehicle 10 and identification data of an automobile manufacturer or equipment supplier (called OEM identification data) are entered via a human-machine interface (HMI), for example a graphical HMI of a diagnostic software application acting as a diagnostic tool 11 executed on the computing device 12.

[0042] The OEM identification data is representative of the manufacturer of the vehicle 10 or the equipment manufacturer that designed the OBD system of the vehicle 10.

[0043] The equipment or manufacturer, noted OEM, is for example selected from a list of OEMs available in a drop-down list of the HMI.

[0044] The identification data of the vehicle 10 comprises, for example, data identifying the type of the vehicle 10 and / or data identifying the make of the vehicle 10. According to another example, the identification data of the vehicle 10 corresponds to the VIN of the vehicle 10.

[0045] In a second operation, the vehicle identification data 10 and the OEM identification data are transmitted by the diagnostic system 11 (for example a diagnostic software application), via the computing device 12, by means of a wired and / or wireless connection, to the “cloud” 100 and more particularly to a remote data processing device 110, for example a server. The vehicle identification data 10 and the OEM identification data are included in a request for access to the on-board network of the vehicle 10 transmitted by the diagnostic system 11 to the remote device 110.

[0046] The remote device 110 corresponds for example to a server controlling the access rights to the diagnostic data of the vehicle 10, the remote device 110 being controlled by the OEM. The remote device 110 is for example identified from the OEM identification data.

[0047] In a third operation of the process, the remote device 110 determines a subscription status to a diagnostic data access service of the vehicle 10 based on the identification data of the vehicle 10 and the received OEM identification data.

[0048] The remote device 110 checks, for example, whether the rights associated with the diagnostic system 11 allow access to the OBD system / on-board computer network of the vehicle 10 to obtain and interpret the diagnostic data of the vehicle 10.

[0049] The remote device 110 thus checks, for example, whether a subscription to a service access to diagnostic data is up to date, i.e. whether the subscription fees have been paid and the associated access conditions (e.g. duration of use of the diagnostic application, number of users who can simultaneously access the vehicle type corresponding to vehicle 10, etc.).

[0050] The information on the access licenses is for example stored in one or more tables, for example of the LUT type (from the English “Look-Up Table” or in French “correspondence table”) storing an identifier of the diagnostic system (for example transmitted with the access request and identifying the subscriber to the access service) and the access conditions associated with the access license (license paid or not, rights or level of access according to the license, duration of activation of the access right, etc.).

[0051] When the subscription status is representative of a right or an authorization to access the diagnostic data of the vehicle 10, that is to say when the access license is up to date with payment, then the remote device 110 transmits configuration data of the diagnostic system to the diagnostic system 11 (for example the diagnostic software application) via the computing device 12 by means of the wired and / or wireless connection connecting the remote device 110 to the diagnostic system 11 or to the computing device 12 which receives them.

[0052] The configuration data are provided to configure the diagnostic system 11, which corresponds to a standard or generic diagnostic system, in such a way that the diagnostic system 11 can access the diagnostic data of the vehicle 10 specific to and particular to the OBD system of the vehicle 10 (generated by the OEM of the vehicle 10 and / or the OBD system of the vehicle 10) and interpret this diagnostic data to determine any faults or failures of the on-board systems of the vehicle 10 reported by the DTC codes of the diagnostic data.

[0053] In a fourth operation of the process, the diagnostic system 11 is configured from the configuration data received in the third operation. The configuration of the generic diagnostic system 11 (intended to be configured to access the OBD system of any type of vehicle after updating its configuration) is updated from the received configuration data to be able to access the OBD system of the vehicle 10 and interpret the diagnostic data of the vehicle 10, including fault codes specific to the vehicle 10 or its OBD system.

[0054] When the subscription status is representative of a prohibition on accessing the diagnostic data of the vehicle 10, that is to say when the access license is not up to date with payment, the remote device 110 transmits data representative of the refusal to validate the right of access to the OBD system of the vehicle 10 to the diagnostic system 11.

[0055] A 1THM dialog window of the diagnostic system 11 is activated for example upon receipt of this data of refusal of validation of the right of access to inform the user of the diagnostic system 11 that he does not have the rights to access the OBD system of the vehicle 10 and to invite the latter to pay the rights by paying the amount associated with the license necessary to access this service.

[0056] If in response the amount associated with the license is paid (by any known remote or online payment means), then the process resumes with the third and fourth operations, i.e. the configuration data is transmitted and the diagnostic system is configured to access the OBD system of the vehicle 10 and interpret the diagnostic data.

[0057] If the user does not pay the license fee, then the process ends.

[0058] In a fifth operation of the process, the newly configured diagnostic system 11 accesses the OBD system of the vehicle 10 and retrieves the diagnostic data of the vehicle 10 for analysis and interpretation.

[0059] The communication of diagnostic data between the vehicle 10 and the diagnostic system 11 is for example according to the UDS protocol (from the English “Unified Diagnostic Services” or in French “unified diagnostic services”).

[0060] According to a particular embodiment of the invention, the process further comprises an activation of the access rights to the OBD system of the vehicle 10, i.e. to the diagnostic data of the vehicle 10.

[0061] The activation of access rights is implemented in parallel with the configuration of the diagnostic system 11.

[0062] The activation of access rights is for example implemented by the remote device 110 in communication with the vehicle 10, in particular with the OBD system of the vehicle 10 or the on-board computer network.

[0063] The verification of the access rights to the OBD system of the vehicle 10 is for example implemented via cryptographic keys and a certificate management system. For this purpose, a client of the MQTT (Message Queuing Telemetry Transport), LWM2M (LightWeight Machine-to-Machine) or DDS (Data Distribution Service) type is installed at the level of the on-board computer network of the vehicle 10 to control the communication of the diagnostic data with the diagnostic system 11, the use of certificates / cryptographic keys making it possible to control the access rights to the on-board network of the vehicle 10 for the communication of the diagnostic data.The control of access rights via certificate management is for example implemented by the remote device 110 which checks which access rights are associated with the diagnostic system 11.

[0064] According to another example, the verification of the access rights comprises the transmission of activation data for access to the OBD system of the vehicle 10 and / or to the on-board computer network of the vehicle 10 to the vehicle 10 by the remote device 110 according to the result of the verification of the access rights associated with the diagnostic system. The activation data comprises, for example, OBD port control data for opening the OBD port 101 for a determined duration to the diagnostic system 11, the duration of opening the OBD port 101 being, for example, a function of the access rights associated with the license stored in the remote device 110 and controlled by the latter. According to another example, the activation data comprises control data for the OBD system of the vehicle 10 or the OBD service implemented by each computer to authorize access to the diagnostic data of the vehicle 10 to the diagnostic system 11 for a determined duration.

[0065] According to yet another example, the access right activation data are for example transmitted to a mobile communication device, for example the smartphone identified by the remote device 110 as being associated with the diagnostic system 11 (or with the user of the system 11), via a wireless connection connecting the remote device 110 to the mobile communication device. The activation data correspond for example to data making it possible to display a QR code (from the English “QR code” or “Quick Response code”) on the screen of the mobile communication device.

[0066] According to this example, the user of the diagnostic system 11 positions the screen of the mobile communication device displaying the QR code in the field of vision of an on-board camera of the vehicle 10, for example a camera of a driver attention monitoring system, known as DMS (from the English "Driver Monitoring System" or in French "Système de surveillance du conduire") or DAA (from the English "Driver Attention Alert" or in French "Alerte d'attention chauffeur") or a front camera (also called windshield camera, from the English "Windshield camera"), such a front camera being arranged in the passenger compartment of the vehicle 10 under the windshield and at the top and in the middle of this windshield.

[0067] The vehicle 10, for example a computer of the vehicle 10, decodes the activation data encoded in the QR code. The OBD port 101 is then controlled according to the activation data to open the OBD port 101 for a determined duration to the diagnostic system 11, the duration of opening of the OBD port 101 being for example a function of the access rights associated with the license stored in the remote device 110 and controlled by the latter. According to another example, the activation data comprises control data of the OBD system of the vehicle 10 or of the OBD service implemented by each computer to authorize access to the diagnostic data. from vehicle 10 to diagnostic system 11 for a specified period.

[0068] Such a process thus makes it possible to authorize access to the diagnostic data of any type of vehicle and vehicle of any brand from a generic or universal diagnostic tool or system. Such an advantage is obtained by allowing the generic / universal diagnostic tool or system to be configured with configuration data obtained from a server, for example under license conditions, the configuration data being provided by the OEM of the vehicle identified via identification data. The control of licenses or access rights by the OEM further allows the OEM to control and / or monetize access to the vehicle diagnostic system and / or the vehicle's on-board system.

[0069] The user of the diagnostic system can further access the OBD system of any vehicle from a single, universal diagnostic system, simply by configuring the diagnostic system with configuration data adapted to each type of vehicle, which data is provided by the vehicle OEM.

[0070] [Fig. 2] schematically illustrates a device 2 of a diagnostic data communication system of a vehicle, for example of the vehicle 10, according to particular and non-limiting exemplary embodiments of the present invention.

[0071] The device 2 corresponds for example to a vehicle computer, a TCU unit, the diagnostic tool 11, the computing device 12, the server 110 or even a mobile communication device.

[0072] The device 2 is for example configured for the implementation of the operations described with regard to [Fig. 1] and / or the steps of the method described with regard to [Fig. 3]. Examples of such a device 2 include, but are not limited to, on-board electronic equipment such as an on-board computer of a vehicle, an electronic calculator such as an ECU (“Electronic Control Unit”), a smartphone, a tablet, a laptop, a computer, a server, a diagnostic device. The elements of the device 2, individually or in combination, can be integrated in a single integrated circuit, in several integrated circuits, and / or in discrete components. The device 2 can be produced in the form of electronic circuits or software (or computer) modules or even a combination of electronic circuits and software modules.

[0073] The device 2 comprises one (or more) processor(s) 21 configured to execute instructions for carrying out the steps of the method and / or for executing the instructions of the software(s) embedded in the device 2. The processor 21 may include integrated memory, an input / output interface, and various circuits known to those skilled in the art. The device 2 further comprises at least one memory 22 corresponding for example to a volatile and / or non-volatile memory and / or comprises a memory storage device which may comprise memory volatile and / or non-volatile, such as EEPROM, ROM, PROM, RAM, DRAM, SRAM, flash, magnetic or optical disk.

[0074] The computer code of the embedded software(s) comprising the instructions to be loaded and executed by the processor is for example stored in the memory 22.

[0075] According to various particular and non-limiting embodiments, the device 2 is coupled in communication with other similar devices or systems and / or with communication devices, for example a TCU (from the English “Telematic Control Unit” or in French “Telematic Control Unit”), for example via a communication bus or through dedicated input / output ports.

[0076] According to a particular and non-limiting exemplary embodiment, the device 2 comprises a block 24 of interface elements for communicating with external devices. The interface elements of the block 24 comprise one or more of the following interfaces: - RF radio frequency interface, for example Wi-Fi® type (according to IEEE 802.11), for example in the 2.4 or 5 GHz frequency bands, or Bluetooth® type (according to IEEE 802.15.1), in the 2.4 GHz frequency band, or Sigfox type using UBN (Ultra Narrow Band) radio technology, or LoRa in the 868 MHz frequency band, LTE (Long-Term Evolution), LTE-Advanced; - USB interface (from the English “Universal Serial Bus” or “Universal Serial Bus” in French); - HDMI interface (from the English “High Definition Multimedia Interface” or “High Definition Multimedia Interface” in French); - LIN interface (from the English “Local Interconnect Network”).

[0077] According to another particular and non-limiting exemplary embodiment, the device 2 comprises a communication interface 24 which makes it possible to establish communication with other devices (such as other computers of the on-board system) via a communication channel 240. The communication interface 24 corresponds for example to a transmitter configured to transmit and receive information and / or data via the communication channel 240. The communication interface 24 corresponds for example to a wired network of the CAN (Controller Area Network) type, CAN FD (Controller Area Network Flexible Data-Rate), FlexRay (standardized by the ISO 17458 standard) or Ethernet (standardized by the ISO / IEC 802-3 standard).

[0078] According to a particular and non-limiting exemplary embodiment, the device 2 can provide output signals to one or more external devices, such as a display screen 250, touch-sensitive or not, one or more speakers 260 and / or other peripherals 270 (projection system) via output interfaces 25, 26 and 27 respectively. According to a variant, one or other of the external devices is integrated into the device 2.

[0079] [Fig.3] illustrates a flowchart of the different stages of a communication process communication of diagnostic data of a vehicle, for example of the vehicle 10, according to a particular and non-limiting exemplary embodiment of the present invention. The method is for example implemented by a communication system comprising a diagnostic system such as the system 11, a vehicle such as the vehicle 10 and a remote data processing device such as the server 110, the diagnostic system being connected to the vehicle via a diagnostic port of the vehicle, the remote data processing device being connected in communication with the diagnostic system, each of the elements of the system corresponding to an exemplary embodiment of the device 2 of [Fig. 2].

[0080] In a first step 31, the diagnostic system transmits a request for access to the on-board network to the remote data processing device, the access request comprising vehicle identification data and identification data of an automobile manufacturer or equipment supplier, called OEM identification data.

[0081] In a second step 32, the remote data processing device determines a subscription status to a vehicle diagnostic data access service based on the vehicle identification data and the OEM identification data.

[0082] In a third step 33, the diagnostic system receives configuration data of the diagnostic system from the remote data processing device when the subscription state is representative of a right of access to the diagnostic data, the configuration data being a function of the vehicle identification data and the OEM identification data.

[0083] In a fourth step 34, the diagnostic system is configured according to the configuration data.

[0084] In a fifth step 35, diagnostic data are received by the diagnostic system from the vehicle's on-board computer network.

[0085] According to a variant, the variants and examples of the operations described in relation to [Fig.l] apply to the steps of the method of [Fig.3].

[0086] Of course, the present invention is not limited to the exemplary embodiments described above but extends to a method and a device for diagnosing a vehicle by analyzing the diagnostic data obtained as described above.

[0087] The present invention also relates to the diagnostic data communication system comprising the diagnostic system 11, the vehicle 10 and the remote data processing device 110, the diagnostic system 11 being connected to the vehicle 10 via a diagnostic port 101 of the vehicle 10, the remote data processing device 110 being communicatively connected to the diagnostic system 11.

Claims

Claims

1. Method for communicating diagnostic data of a vehicle (10), said vehicle (10) comprising a diagnostic port (101), called OBD port, said OBD port (101) being configured to connect a diagnostic system (11) to an on-board computer network of said vehicle (10), said method comprising the following steps: - transmission (31), by said diagnostic system (11), of a request for access to said on-board network to a remote data processing device (110), said access request comprising identification data of the vehicle (10) and identification data of an automobile manufacturer or equipment supplier, called OEM identification data; - determination (32), by said remote data processing device (110), of a subscription status to a service for accessing the diagnostic data of the vehicle (10) as a function of said identification data of the vehicle (10) and said OEM identification data;- when said subscription status is representative of a right of access to said diagnostic data, reception (33), by said diagnostic system (11) from said remote data processing device (110), of configuration data of said diagnostic system (11), said configuration data being a function of said vehicle identification data (10) and said OEM identification data; - configuration (34) of said diagnostic system (11) as a function of said configuration data; and - reception (35) of said diagnostic data by said diagnostic system (11) from said on-board computer network of the vehicle (10).;

2. The method of claim 1, wherein when said subscription status is representative of a prohibition of access to said diagnostic data, said method further comprises a step of transmitting subscription data to said diagnostic data access service to obtain said access right.

3. Method according to claim 1 or 2, further comprising a step of transmitting, by said remote data processing device (110), data for activating said right of access to the on-board computer network of the vehicle (10).

4. Method according to claim 3, for which said activation data further comprises data representative of a determined duration of activation of said access right.

5. Method according to claim 3 or 4, for which said activation data is transmitted to the on-board computer network via a wireless link.

6. A method according to claim 3 or 4, wherein said activation data is transmitted to a mobile communication device in the form of a QR code via a wireless link, said method further comprising a step of reading said QR code by a camera of said vehicle (10).

7. Computer program comprising instructions for implementing the method according to any one of the preceding claims, when these instructions are executed by at least one processor.

8. A system for communicating diagnostic data of a vehicle (10), said system comprising a diagnostic system (11), the vehicle (10) and a remote data processing device (110), said diagnostic system being connected to said vehicle via a diagnostic port of the vehicle, said remote data processing device being connected in wireless communication with said diagnostic system, said system being configured to implement the steps of the method according to any one of claims 1 to 4.

9. The system of claim 8, wherein said remote data processing device (110) is further connected in wireless communication to said vehicle (10), said system being configured to implement the steps of the method according to any one of claims 1 to 5

10. 1 a J. System according to claim 8 or 9, further comprising a mobile communication device connected in wireless communication to said remote data processing device (110), said system being configured to implement the steps of the method according to any one of claims 1 to 6.

Images