Methods, systems, storage media, and automobiles for collecting vehicle fault data

Abstract

This invention discloses a method, system, storage medium, and vehicle for collecting automotive fault data, relating to the field of automotive fault data collection. The method includes the following steps: providing a data reading interface for the device to be diagnosed to an onboard control device with data transmission capabilities; collecting diagnostic data from the device to be diagnosed corresponding to the diagnostic task through the onboard control device; and storing the diagnostic data as automotive fault data. This invention directly utilizes existing onboard control devices with data transmission capabilities to collect the operating information of the device to be diagnosed; it eliminates the need for external diagnostic instruments as in existing technologies, thereby improving collection efficiency and reducing collection costs. Simultaneously, the automotive fault data collected by this invention is automatically stored, eliminating the need for manual scanning and uploading operations as in existing technologies, thus improving the user experience.

Description

Technical Field

[0001] This invention relates to the field of automotive fault data acquisition, specifically to a method, system, storage medium, and automotive for acquiring automotive fault data. Background Technology

[0002] First, let's define the English abbreviations that will be used in this invention:

[0003] T-Box: Telematics Box, vehicle communication module;

[0004] DTC: Diagnostic Trouble Code;

[0005] LOG: also known as vehicle data log, refers to various data information recorded by the vehicle's infotainment system during vehicle operation;

[0006] CAN: Controller Area Network, is one of the most widely used fieldbuses internationally; the suffix HS (high speed) indicates a high-speed LAN, FD (flexible data rate) indicates a variable-rate LAN, and the numbers represent the LAN code.

[0007] LIN: A low-cost serial communication network defined for automotive distributed electronic systems. It complements other automotive multiplexing networks such as CAN and is suitable for applications that do not have high requirements for network bandwidth, performance, or fault tolerance.

[0008] ETH: Ethernet, or Automotive Ethernet, is a communication protocol used in the automotive industry. It enables interconnectivity between vehicles and between vehicles and infrastructure by providing high-speed, reliable data transmission. Within the car cabin, communication between hardware components sometimes relies on Ethernet.

[0009] FlexRay: A high-speed and deterministic bus technology designed specifically for automobiles, featuring fault tolerance. FlexRay systems support both time-triggered (deterministic) and event-triggered communication, combining high network utilization with system flexibility. The FlexRay network backbone is used for data communication within the vehicle.

[0010] VIN: Vehicle Identification Number. According to the ASE standard, the VIN consists of 17 characters, hence its common name, the 17-digit code. The Vehicle Identification Number is like a car's ID number; it is determined according to national vehicle management standards and includes information such as the vehicle's manufacturer, year, model, body style and code, engine code, and assembly location. New vehicle registration certificates typically print the VIN in the "Vehicle Identification Number" field.

[0011] HMI: Human Machine Interface, also known as human-machine interface, is a medium for interaction and information exchange.

[0012] VSM: Vehicle System Management.

[0013] Currently, the general method for collecting vehicle fault data is as follows: Based on the diagnostic task, the corresponding diagnostic equipment (vehicle diagnostic tool) is connected to the vehicle to obtain the corresponding vehicle diagnostic data. The user then uploads the diagnostic data to the server, which parses the data and returns it to the client. The specific process is as follows:

[0014] 1. Automotive diagnostic tools acquire diagnostic data from a vehicle through its diagnostic interface;

[0015] 2. The car diagnostic tool generates a QR code based on the diagnostic data;

[0016] 3. Users obtain scan data by scanning a QR code through the client and then upload the scan data to the server corresponding to the car diagnostic instrument;

[0017] 4. The server parses the diagnostic data to obtain the diagnostic results and returns them to the client for display.

[0018] The above-mentioned method for collecting vehicle fault data has the following drawbacks:

[0019] (1) Different diagnostic equipment needs to be connected to the vehicle for different diagnostic tasks, which not only increases the cost of data collection and reduces the efficiency of data collection (installation, disassembly and service both consume human resources costs and equipment usage costs of manufacturers or outlets), but also requires the diagnostic equipment to be installed in the vehicle for a long time for faults that are difficult to reproduce, thus occupying the space of the vehicle.

[0020] (2) Users are required to actively upload fault data by scanning a QR code, which takes up users' time and reduces user experience. Summary of the Invention

[0021] To address the shortcomings of existing technologies, the technical problem solved by this invention is: how to collect the required vehicle fault data without using external equipment, thereby reducing collection costs and improving collection efficiency.

[0022] To achieve the above objectives, in a first aspect, embodiments of this application provide a method for collecting automotive fault data, comprising the following steps: providing a data reading interface for a vehicle control device with data transmission capabilities to a device under test; collecting diagnostic data of the device under test corresponding to the diagnostic task through the vehicle control device, and storing the diagnostic data as automotive fault data.

[0023] In conjunction with the first aspect, in one embodiment, the process of providing a data reading interface for the device to be diagnosed to the vehicle control device with data transmission function includes: providing a network data reading interface for the vehicle control device.

[0024] In conjunction with the first aspect, in one implementation, the diagnostic task is initiated by the server, and the vehicle fault data is stored in the server's database; when the fault condition corresponding to the diagnostic task has occurred, the on-board control device stops collecting the vehicle fault data corresponding to the diagnostic task and clears the vehicle fault data corresponding to the diagnostic task from the database.

[0025] In conjunction with the first aspect, in one embodiment, the process of storing the vehicle fault data includes: storing the vehicle fault data separately in the database of the vehicle control device and the server; when the storage space of the vehicle control device reaches a specified threshold, the vehicle fault data collected later will overwrite the vehicle fault data collected earlier.

[0026] In conjunction with the first aspect, in one embodiment, the process of collecting diagnostic data of the device to be diagnosed corresponding to the diagnostic task through the vehicle control device includes: after confirming that the current vehicle is safe, sending a diagnostic task to the vehicle control device; after obtaining user authorization, the vehicle control device collects diagnostic data of the device to be diagnosed corresponding to the diagnostic task in real time.

[0027] In conjunction with the first aspect, in one implementation, the process of confirming the safety of the current vehicle includes: encrypting the identification information of the current vehicle and transmitting it to the vehicle network platform for authentication; and confirming the safety of the current vehicle upon receiving the recognition pass information returned by the vehicle network platform.

[0028] Secondly, embodiments of this application provide a storage medium storing a computer program, which, when executed, implements the method provided in the first aspect.

[0029] Thirdly, embodiments of this application provide a vehicle fault data acquisition system, which includes the vehicle control device provided in the first aspect.

[0030] In conjunction with the third aspect, in one implementation, the system also includes a server, which includes an information interaction module and a database;

[0031] The information interaction module is used to: send diagnostic tasks to the vehicle control equipment, perform safety verification on the vehicle corresponding to the diagnostic task, and receive vehicle fault data returned by the vehicle control equipment.

[0032] The database is used to store vehicle fault data returned by the vehicle control equipment.

[0033] Fourthly, embodiments of this application provide a vehicle that includes the vehicle fault data acquisition system provided in the third aspect.

[0034] Compared with the prior art, the advantages of the present invention are as follows:

[0035] (1) This invention directly utilizes existing vehicle control equipment with data transmission capabilities to collect the operating information of the device under diagnosis; it eliminates the need for external diagnostic instruments as in the prior art, thereby improving collection efficiency and reducing collection costs. At the same time, the vehicle fault data collected by this invention is automatically stored, eliminating the need for manual scanning and uploading operations as in the prior art, thus improving the user experience.

[0036] (2) Before data collection, this invention can provide corresponding data reading interfaces for the vehicle control device based on the data type corresponding to the diagnostic function. Furthermore, before data collection, this invention can provide several specified data reading interfaces for the vehicle control device (corresponding to vehicle devices that frequently require fault diagnosis); it can also provide data reading interfaces for all vehicle devices that may malfunction, thereby achieving "global diagnosis"; and when vehicle devices are updated, only the data reading interface of the newly added device needs to be provided to achieve fault diagnosis of the new device. Therefore, this invention is highly flexible and has a wide range of applications.

[0037] (3) The diagnostic task of this invention is initiated by the server. Designers can flexibly set and initiate diagnostic tasks on the server according to their needs and remotely control the vehicle control equipment to perform the work, thereby saving labor costs. The vehicle fault data is stored in the server's database, making reasonable use of the server's resources and minimizing the resource consumption of the vehicle equipment. When the fault condition corresponding to the diagnostic task has occurred, the vehicle control equipment stops collecting the vehicle fault data corresponding to the diagnostic task. At this time, comprehensive vehicle fault data from before the fault occurred to the fault occurrence process can be used for diagnostic analysis. After the analysis is completed, the vehicle fault data corresponding to the diagnostic task is cleared from the database to reduce the resource consumption of the server.

[0038] (4) The basic conditions for collecting fault data in this invention are: 1. Vehicle safety verification is passed, 2. User authorization is obtained, that is, fault data is collected on the basis of vehicle safety, user awareness and user opinion, so as to effectively ensure user safety. Attached Figure Description

[0039] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0040] Figure 1 This is a schematic diagram of the system architecture in an embodiment of the present invention;

[0041] Figure 2 This is a flowchart illustrating the method for collecting vehicle fault data in an embodiment of the present invention.

[0042] Figure 3 This is a schematic diagram of the architecture in which the vehicle control device is arranged at the CAN HS7 and ETH network nodes in an embodiment of the present invention;

[0043] Figure 4 This is a schematic diagram of the architecture in which the vehicle control equipment is arranged inside the VSM in an embodiment of the present invention. Detailed Implementation

[0044] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0045] The flowchart shown in the attached diagram is for illustrative purposes only and does not necessarily include all content and operations / steps, nor does it necessarily have to be performed in the order described. For example, some operations / steps can be broken down, combined, or partially merged, so the actual execution order may change depending on the actual situation.

[0046] First, a brief introduction to the research and development process of this invention will be given.

[0047] To address the shortcomings (1) in the background technology, diagnostic equipment needs to be generalized (e.g., providing a general diagnostic equipment that can replace all external diagnostic instruments) or reused (e.g., using existing vehicle-mounted equipment for fault diagnosis).

[0048] The standardization of diagnostic equipment is difficult to achieve due to the differences in the manufacturers and operating logic of different diagnostic equipment.

[0049] Regarding the reuse of diagnostic equipment, the inventors have researched a feasible method: directly utilize vehicle-mounted components to periodically and in real-time broadcast diagnostic data acquisition commands. Moreover, upon receiving a fault code broadcast by a malfunctioning vehicle-mounted controller, the fault code is recorded and a diagnostic data acquisition command is broadcast. Then, the vehicle-mounted components read the diagnostic data from each vehicle-mounted controller.

[0050] However, the vehicle controller can only collect data after a DTC or LOG is triggered. Since DTCs or LOGs need to be preset, if a new fault occurs and there is no corresponding DTC or LOG, the corresponding diagnostic data cannot be collected (for example, the car is turned off, but the corresponding vehicle controller did not receive a DTC or LOG before the engine was turned off).

[0051] At the same time, even if DTC or LOG data is triggered, it is only the data after the DTC or LOG is triggered, which is not comprehensive enough for fault data diagnosis and analysis.

[0052] Therefore, the vehicle fault data collection method in this embodiment of the invention includes the following steps: providing a data reading interface for the device to be diagnosed to the on-board control device (which needs to have data transmission capabilities, such as a T-BOX). The device to be diagnosed corresponding to the diagnostic task is determined, and the diagnostic data (i.e., network data generated during the operation of the device to be diagnosed) of the device to be diagnosed (here, the device to be diagnosed corresponding to the diagnostic task) is collected in real time through the on-board control device, and the diagnostic data is stored as vehicle fault data.

[0053] Therefore, this invention directly utilizes existing in-vehicle control equipment with data transmission capabilities to collect the operating information of the device under diagnosis; it eliminates the need for external diagnostic instruments as in existing technologies, thereby improving collection efficiency and reducing collection costs. Simultaneously, the vehicle fault data collected by this invention is automatically stored, eliminating the need for manual scanning and uploading operations as in existing technologies, thus enhancing the user experience.

[0054] Preferably, the process of providing a data reading interface for the device to be diagnosed to the vehicle control device with data transmission function includes: providing a network data reading interface for the vehicle control device.

[0055] Therefore, this invention can provide corresponding data reading interfaces for the vehicle control device based on the data type corresponding to the diagnostic function before data collection. Furthermore, before data collection, this invention can provide several specified data reading interfaces for the vehicle control device (corresponding to vehicle devices that frequently require fault diagnosis); it can also provide data reading interfaces for all potentially faulty vehicle devices, thereby achieving "global diagnosis"; and when vehicle devices are updated, only the data reading interface of the newly added device needs to be provided to achieve fault diagnosis of the new device. Therefore, this invention is highly flexible and has a wide range of applications.

[0056] Preferably, the process of collecting diagnostic data of the device to be diagnosed corresponding to the diagnostic task in real time through the vehicle control device according to the diagnostic task includes: after confirming that the current vehicle is safe, sending a diagnostic task to the vehicle control device; after obtaining user authorization, the vehicle control device collects diagnostic data of the device to be diagnosed corresponding to the diagnostic task in real time.

[0057] Therefore, the basic conditions for collecting fault data in this invention are: 1. Vehicle safety verification is passed, and 2. User authorization is obtained. That is, fault data is collected on the basis of vehicle safety, user awareness, and user perception, which effectively ensures user safety.

[0058] Specifically, the process for confirming the safety of the current vehicle includes: encrypting the vehicle's identification information (mainly VIN) (including signature authentication, communication encryption, and data encryption) and transmitting it to the vehicle network platform for authentication. Upon receiving the recognition pass information returned by the vehicle network platform, the safety of the current vehicle is confirmed.

[0059] Preferred:

[0060] (1) The diagnostic task in the above method is initiated by the server. Designers can flexibly set up and initiate diagnostic tasks on the server according to their needs and remotely control the vehicle control equipment to work, thereby saving manpower costs.

[0061] (2) The vehicle fault data in the above method is stored in the database of the server (either locally or in the cloud), which makes reasonable use of the server's resources and consumes very little resources of the vehicle equipment.

[0062] (3) When the fault condition corresponding to the diagnostic task has occurred, the vehicle control equipment stops collecting the vehicle fault data corresponding to the diagnostic task. At this time, the comprehensive vehicle fault data from before the fault occurred to the fault occurrence process can be used for diagnostic analysis. After the analysis is completed, the vehicle fault data corresponding to the diagnostic task is cleared in the database to reduce the resource consumption of the server.

[0063] Based on this, the process of storing vehicle fault data in the above method includes: storing the vehicle fault data separately in the databases of the on-board control device and the server. Thus, when a communication failure occurs with the server, the on-board control device can resend the vehicle fault data to the server when communication is restored. When the storage space of the on-board control device reaches a specified threshold, the previously collected vehicle fault data will be overwritten by the later collected vehicle fault data (this can be done by storing all existing data first, or by using a first-in-first-out queue for "gradual overwriting"). This allows the on-board control device to collect vehicle fault data through automatic cyclic overwriting, thereby achieving data collection while adapting to the operating logic of on-board control devices with limited storage space.

[0064] The method of the present invention will be described below through specific embodiments.

[0065] See Figure 1 As shown, the server in this embodiment includes a research and development end and an enterprise platform. The work of the enterprise platform can be divided into security management and task management. Security management mainly authenticates vehicles to the vehicle networking platform through data signing and encryption / decryption. Task management includes user management, log management, vehicle management, forwarding diagnostic tasks, receiving data, and storing data. The main tasks of the vehicle control equipment include: security management, HMI management, receiving diagnostic tasks, data acquisition, data storage, data transmission, data forwarding, and remote control.

[0066] See Figure 1 and Figure 2 As shown, the specific process of this embodiment includes:

[0067] S1: Based on the data requested by the customer, the designer uses their computer on the R&D side to issue a diagnostic task to the enterprise platform and performs the corresponding configurations to enable the data reading interface of the device to be diagnosed. This may include setting the CAN bus rate, selecting the frame ID to be collected, filtering conditions, communication protocols, etc. For details, see [link to documentation]. Figure 3 As shown, if the diagnostic task requires CAN HS7 and ETH networks, the on-board control equipment can be deployed at the CAN HS7 and ETH network nodes (in this design, the on-board control equipment is...). Figure 3 84G9 (i.e., remote control unit); see also Figure 4 As shown, if the diagnostic task requires CAN, ETH, or LIN networks, the on-board control equipment can be built into the VSM.

[0068] S2: Based on the diagnostic task, the enterprise platform encrypts the corresponding vehicle identification information (including signature authentication, communication encryption, and data encryption) and transmits it to the vehicle network platform for authentication. Upon receiving authentication success information from the vehicle network platform, the enterprise platform confirms the current vehicle's safety. At this point, the enterprise platform forwards the diagnostic task to the corresponding on-board control device.

[0069] S3: After receiving the diagnostic task, the vehicle control device requests the customer's permission to record diagnostic data on the vehicle device (human-machine interaction system: such as infotainment controller, touch screen); if the user agrees, proceed to S4; if the user does not agree, the vehicle control device clears the diagnostic task and reports back to the enterprise platform, which then reports back to the designer, and the process ends.

[0070] S4: The vehicle control equipment collects diagnostic data from the device under test in real time, stores the diagnostic data as vehicle fault data, and periodically uploads the vehicle fault data to the enterprise platform. When a communication failure occurs with the enterprise platform, the vehicle control equipment resends the vehicle fault data to the enterprise platform when communication is restored. When the storage space of the vehicle control equipment is full, the data in the storage space is automatically overwritten in a loop.

[0071] S5: The enterprise platform stores the received vehicle fault data in a cloud database.

[0072] S6: When the fault condition corresponding to the diagnostic task has occurred, the designer performs a diagnostic analysis on the R&D side based on comprehensive vehicle fault data from before the fault occurred until the fault occurred. After the analysis is completed, the on-board control equipment is remotely controlled through the enterprise platform to stop collecting and storing the vehicle fault data corresponding to the diagnostic task, and the vehicle fault data corresponding to the diagnostic task is cleared from the database.

[0073] This invention also provides a storage medium storing a computer program, which, when executed by a processor, implements the above-described method. It should be noted that the storage medium includes various media capable of storing program code, such as a USB flash drive, a portable hard drive, ROM (Read-Only Memory), RAM (Random Access Memory), a magnetic disk, or an optical disk.

[0074] This invention also provides an electronic device, including a memory and a processor, wherein the memory stores a computer program that runs on the processor, and the processor executes the computer program to implement the above-described method.

[0075] Those skilled in the art will understand that all or some of the steps, systems, and apparatuses disclosed above, and their functional modules / units, can be implemented as software, firmware, hardware, or suitable combinations thereof. In hardware implementations, the division between functional modules / units mentioned above does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed collaboratively by several physical components. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit (ASIC). Such software can be distributed on a computer-readable storage medium, which may include computer-readable storage media (or non-transitory media) and communication media (or transient media).

[0076] As is known to those skilled in the art, the term computer-readable storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer-readable storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible to a computer. Furthermore, it is known to those skilled in the art that communication media typically contain computer-readable instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.

[0077] For example, the computer-readable storage medium may be an internal storage unit of the electronic device described in the foregoing embodiments, such as a hard disk or memory of the electronic device. The computer-readable storage medium may also be an external storage device of the electronic device, such as a plug-in hard disk, smart media card (SMC), secure digital card (SD), flash card, etc., provided on the electronic device.

[0078] The above are merely specific embodiments of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in the present invention, and these modifications or substitutions should all be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention should be determined by the scope of the claims.

Claims

1. A method for collecting vehicle fault data, characterized in that, The method includes the following steps: providing a data reading interface for the device to be diagnosed to an on-board control device with data transmission capabilities; Diagnostic data from the device to be diagnosed, corresponding to the diagnostic task, is collected through the onboard control equipment. The vehicle's identification information is encrypted and transmitted to the vehicle network platform for authentication. If the vehicle network platform returns a verification message, the vehicle's security is confirmed. A diagnostic task is sent to the vehicle control device. After obtaining user authorization, the vehicle control device collects diagnostic data of the device to be diagnosed in real time, which corresponds to the diagnostic task. Vehicle fault data is stored separately in the on-board control device and the server's database; when the storage space of the on-board control device reaches a specified threshold, the vehicle fault data collected later will overwrite the vehicle fault data collected earlier. The diagnostic task is initiated by the server, and the vehicle fault data is stored in the server's database. When the fault condition corresponding to the diagnostic task has occurred, the vehicle control device stops collecting the vehicle fault data corresponding to the diagnostic task and clears the vehicle fault data corresponding to the diagnostic task from the database.

2. The method for collecting vehicle fault data as described in claim 1, characterized in that: The process of providing a data reading interface for the device to be diagnosed to the vehicle control device with data transmission function includes: providing a network data reading interface for the vehicle control device.

3. A storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, it implements the method of claim 1 or 2.

4. A vehicle fault data acquisition system, characterized in that: The system includes the on-board control device in the vehicle fault data acquisition method according to claim 1 or 2.

5. The vehicle fault data acquisition system as described in claim 4, characterized in that: The system also includes a server, which comprises an information interaction module and a database; The information interaction module is used to: send diagnostic tasks to the vehicle control equipment, perform safety verification on the vehicle corresponding to the diagnostic task, and receive vehicle fault data returned by the vehicle control equipment. The database is used to store vehicle fault data returned by the vehicle control equipment.

6. A car, characterized in that: The vehicle includes the vehicle fault data acquisition system as described in claim 4.

Images