Vehicle fault diagnosis system and method, vehicle terminal and storage medium

Abstract

The invention relates to the technical field of fault diagnosis, and discloses a vehicle fault diagnosis system and method, a vehicle terminal and a storage medium, the system comprises the vehicle terminal and an edge calculation center, the vehicle terminal is used for collecting diagnosis fault codes and vehicle operation data of the vehicle terminal, and if a first fault code is found in the diagnosis fault codes, the vehicle operation data is sent to the edge calculation center; if yes, determining a first fault result according to the first fault code; if a second fault code is found in the diagnosis fault code, an edge node is determined according to the position information of the vehicle terminal, the edge node is connected, the second fault code and second operation data corresponding to the second fault code are sent to the edge node, the edge node is at least one of edge calculation centers, and the edge calculation centers are connected to the edge node; the edge node is used for performing fault diagnosis according to a third fault code and third operation data corresponding to the third fault code if the third fault code is found in the received second fault code to obtain a second diagnosis result; through the method, a more practical and more accurate vehicle fault diagnosis system is provided.

Description

Technical Field

[0001] The present application relates to the technical field of fault diagnosis, and in particular to a vehicle fault diagnosis system, method, vehicle terminal and storage medium. Background Art

[0002] With the development of big data and artificial intelligence, vehicle-side applications and vehicle networks have become increasingly complex, accompanied by a surge in data volume, which in turn leads to problems such as difficulty in data management, complex data maintenance, and high costs. Vehicle network diagnostic data involves vehicle safety repair and maintenance, which usually have high requirements for network latency and reliability. Centralized cloud remote diagnosis cannot meet real-time requirements, and a large amount of data will cause cloud networks to become congested. Urgent data is often difficult to process efficiently. Areas with poor cloud network coverage will also affect data transmission speed and quality.

[0003] Edge computing refers to the use of an open platform that integrates network, computing, storage, and applications to provide the nearest service on the side close to the source of objects or data. Its application is initiated on the edge side, resulting in faster network service response, meeting the basic needs of the industry in terms of real-time business, application intelligence, security and privacy protection, etc. Therefore, based on the shortcomings of centralized cloud remote diagnosis in terms of network latency, network performance, and diagnostic rate, this solution provides a vehicle fault diagnosis system based on edge computing to solve at least one of the above problems.

[0004] It should be noted that the above content only provides background technical information related to the present application and does not necessarily constitute prior art. Summary of the invention

[0005] In view of the shortcomings of the prior art described above, the present application provides a vehicle fault diagnosis system, method, vehicle terminal and storage medium to reduce the transmission time and processing time of fault data, improve the real-time performance of fault diagnosis, and improve the efficiency of fault data processing.

[0006] Other features and advantages of the present application will become apparent from the following detailed description, or may be learned in part by the practice of the present application.

[0007] According to one aspect of an embodiment of the present application, a vehicle fault diagnosis system is provided, which includes a vehicle terminal and an edge computing center; the vehicle terminal is used to collect diagnostic fault codes and vehicle operation data of the vehicle terminal, and if a first fault code is found in the diagnostic fault code, a first fault result is determined according to the first fault code; if a second fault code is found in the diagnostic fault code, an edge node is determined according to location information of the vehicle terminal, the edge node is connected, and the second fault code and second operation data corresponding to the second fault code are sent to the edge node, and the edge node is at least one of the edge computing centers; the edge node is used to perform fault diagnosis according to the third fault code and third operation data corresponding to the third fault code to obtain a second diagnostic result if a third fault code is found in the received second fault code, wherein the second operation data includes the third operation data.

[0008] In one embodiment of the present application, based on the above scheme, the vehicle fault diagnosis system also includes a server side, the server side is connected to the edge node and the vehicle terminal, and the server side is used for at least one of the following: if a fourth fault code sent by the edge node and a fourth operating data corresponding to the fourth fault code are received, then a fault diagnosis is performed according to the fourth fault code and the fourth operating data to obtain a third diagnosis result, wherein the fourth fault code is obtained by the edge node from the second fault code, and the second operating data includes the fourth operating data; if a plurality of historical operating data and the fault results corresponding to each of the historical operating data are obtained; then each of the historical operating data is used as an operating data sample, and the operating data sample is labeled according to the fault result to obtain a result sample label corresponding to each of the operating data samples; the operating data samples with the result sample label are model trained to obtain a fault diagnosis model, and the fault diagnosis model is sent to the edge node; if a first diagnosis result and a second diagnosis result sent by the edge node are received, then a maintenance suggestion is generated in combination with the first diagnosis result, the second diagnosis result and the third diagnosis result, and the maintenance suggestion is sent to the vehicle terminal, wherein the first diagnosis result is sent from the vehicle terminal to the edge node.

[0009] In one embodiment of the present application, based on the aforementioned scheme, the edge node is also used for at least one of the following: preprocessing the received second fault code and the second operating data, encrypting the preprocessed second fault code and the preprocessed second operating data according to a preset encryption algorithm, and sending them to the server side, wherein the preprocessing operation includes at least one of data cleaning, anomaly detection, data compression, feature extraction and data conversion; receiving the first diagnostic result sent by the vehicle terminal, determining the vehicle operating status corresponding to the vehicle terminal according to the first diagnostic result, the second fault code and the second operating data, if the vehicle operating status is detected to be an abnormal state, generating a prompt message according to the vehicle operating status, and sending the prompt message to the vehicle terminal to prompt the user; receiving the fault diagnosis model sent by the server side, performing fault diagnosis on the third fault code and the third operating data according to the fault diagnosis model, and obtaining the second diagnostic result.

[0010] In one embodiment of the present application, based on the aforementioned scheme, the vehicle terminal activates the remote diagnosis function in the following manner: receiving a remote diagnosis activation request sent by the server side to obtain current vehicle data; matching the current vehicle data with preset vehicle data, and determining the current vehicle condition based on the matching result; if the current vehicle condition is the preset vehicle condition, activating the remote diagnosis function and sending the activation result to the server side, wherein the remote diagnosis function is to perform fault diagnosis on the fourth fault code and the fourth operating data through the server side.

[0011] In one embodiment of the present application, based on the aforementioned scheme, the vehicle fault diagnosis system turns off the remote diagnosis function in at least one of the following ways: the server side starts a first timer after turning on the remote diagnosis function, and if the first timing value of the first timer is greater than or equal to a first time threshold, the remote diagnosis function is turned off; the server side starts a second timer after sending the remote diagnosis start request, and if the second timing value of the second timer is greater than or equal to a second time threshold, the remote diagnosis function is turned off.

[0012] In one embodiment of the present application, based on the aforementioned scheme, the vehicle terminal is connected to the server side in the following manner: if the activation result is successful, the server side sends a link establishment request and a route activation request to the vehicle terminal; after the vehicle terminal receives the link establishment request and the route activation request, the vehicle terminal establishes a link and activates the route through the vehicle gateway and the electronic control unit connected to the vehicle gateway and the on-board sensor to connect the vehicle terminal to the server side.

[0013] According to one aspect of an embodiment of the present application, a vehicle fault diagnosis method is provided, which is applied to an edge computing center, and the vehicle fault diagnosis method includes: obtaining a diagnostic fault code and vehicle operation data of a vehicle terminal, wherein the vehicle terminal is used to collect the diagnostic fault code and vehicle operation data of the vehicle terminal, and if a first fault code is found in the diagnostic fault code, a first fault result is determined according to the first fault code; if a second fault code is found in the diagnostic fault code, an edge node is determined according to location information of the vehicle terminal, the edge node is connected, and the second fault code and second operation data corresponding to the second fault code are sent to the edge node, and the edge node is at least one of the edge computing centers; if a third fault code is found in the received second fault code, fault diagnosis is performed according to the third fault code and third operation data corresponding to the third fault code to obtain a second diagnostic result, wherein the second operation data includes the third operation data.

[0014] According to one aspect of an embodiment of the present application, a vehicle fault diagnosis method is provided, which is applied to a vehicle terminal. The vehicle fault diagnosis method includes: collecting diagnostic fault codes and vehicle operation data of the vehicle terminal, and if a first fault code is found in the diagnostic fault code, determining a first fault result according to the first fault code; if a second fault code is found in the diagnostic fault code, determining an edge node according to location information of the vehicle terminal, connecting the edge node, and sending the second fault code and second operation data corresponding to the second fault code to the edge node, the edge node being at least one of the edge computing centers, and the edge node is used for performing fault diagnosis according to the third fault code and third operation data corresponding to the third fault code if a third fault code is found in the received second fault code, so as to obtain a second diagnostic result, wherein the second operation data includes the third operation data.

[0015] According to one aspect of an embodiment of the present application, a vehicle terminal is provided, which includes: one or more processors; a storage device for storing one or more programs, and when the one or more programs are executed by the one or more processors, the vehicle terminal implements the vehicle fault diagnosis method described in the above embodiments.

[0016] The present application also provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor of a computer, the computer is enabled to execute the vehicle fault diagnosis method as described in any one of the above embodiments.

[0017] Beneficial effects of the present application: The present application provides a vehicle fault diagnosis system including a vehicle terminal and an edge computing center, wherein the vehicle terminal is used to collect diagnostic fault codes and vehicle operation data of the vehicle terminal, and if a first fault code is found in the diagnostic fault code, a first fault result is determined according to the first fault code, and the diagnostic result is determined at the vehicle terminal, thereby reducing the time for data transmission and improving the efficiency of diagnosis; if a second fault code is found in the diagnostic fault code, an edge node is determined according to the location information of the vehicle terminal, the edge node is connected, and the second fault code and the second operation data corresponding to the second fault code are sent to the edge node, and the edge node is at least one of the edge computing centers; the edge node is used to If a third fault code is found in the received second fault code, a fault diagnosis is performed based on the third fault code and the third operating data corresponding to the third fault code to obtain a second diagnostic result, wherein the second operating data includes the third operating data. By determining the diagnostic result at the edge node, compared with transmitting all fault data to the cloud, the data transmission time is reduced, and the diagnostic efficiency is improved. In particular, for fault data with higher timeliness requirements, the diagnostic results can be obtained faster, avoiding safety hazards caused by long transmission time or high latency, thereby improving the user experience and satisfaction. Fault diagnosis through edge nodes close to the vehicle terminal can also reduce dependence on the network, saving bandwidth and costs.

[0018] In addition, the vehicle fault diagnosis system provided by the present application can also improve the privacy and security of data, reduce the amount of data transmitted to the server, thereby reducing the use of network bandwidth and reducing costs.

[0019] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The drawings herein are incorporated into the specification and constitute a part of the specification, showing embodiments consistent with the present application, and together with the specification, are used to explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application, and for those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative work. In the drawings:

[0021] Figure 1 is a schematic diagram of an exemplary system architecture shown in an exemplary embodiment of the present application;

[0022] Figure 2 is a block diagram of a vehicle fault diagnosis system shown in an exemplary embodiment of the present application;

[0023] Figure 3 is a schematic diagram of the architecture of a vehicle fault diagnosis system shown in an exemplary embodiment of the present application;

[0024] Figure 4 is a flow chart of a vehicle fault diagnosis method shown in an exemplary embodiment of the present application;

[0025] Figure 5 A schematic diagram of the structure of a computer system suitable for implementing an electronic device of an embodiment of the present application is shown. DETAILED DESCRIPTION

[0026] The following will describe the implementation methods of the present application with reference to the accompanying drawings and preferred embodiments. Those skilled in the art can easily understand other advantages and effects of the present application from the contents disclosed in this specification. The present application can also be implemented or applied through other different specific implementation methods, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present application. It should be understood that the preferred embodiments are only for illustrating the present application, not for limiting the scope of protection of the present application.

[0027] It should be noted that the illustrations provided in the following embodiments are only used to illustrate the basic concept of the present application in a schematic manner, and therefore the illustrations only show components related to the present application rather than being drawn according to the number, shape and size of components in actual implementation. In actual implementation, the type, quantity and proportion of each component may be changed arbitrarily, and the component layout may also be more complicated.

[0028] In the following description, a large number of details are discussed to provide a more thorough explanation of the embodiments of the present application. However, it is obvious to those skilled in the art that the embodiments of the present application can be implemented without these specific details. In other embodiments, well-known structures and devices are shown in the form of block diagrams rather than in detail to avoid making the embodiments of the present application difficult to understand.

[0029] First of all, it should be noted that MQTT (Message Queue Telemetry Transport) is a lightweight communication protocol based on the publish / subscribe model. It is built on the TCP / IP protocol and is a standard transmission protocol in the Internet of Things (IoT).

[0030] SOME / IP (Scalable service-Oriented MiddlewarE over IP) is a powerful, flexible and reliable communication protocol, mainly used in the field of automobiles and embedded systems, for the discovery, description, configuration and invocation of services in the network. SOME / IP is widely used to implement vehicle-to-vehicle communication (V2X), enabling vehicles to exchange information safely and efficiently, improving driving safety and efficiency. Through SOME / IP, vehicles can discover the services of other vehicles and infrastructure and communicate with them as needed. It can also provide scalable communication capabilities for devices, especially suitable for resource-constrained environments. As a lightweight communication protocol, SOME / IP can operate efficiently in these environments.

[0031] OTA (Over-the-Air) flashing, or air upgrade technology, is a technology that provides software updates, patches or new versions to devices through wireless networks (such as Wi-Fi or mobile data). OTA flashing refers to pushing new software versions or updates directly to devices through wireless networks without the need for physical contact with the device, thereby achieving remote software upgrades. In the automotive field, OTA flashing technology is widely used in software updates for vehicle systems such as ECUs (electronic control units).

[0032] OBD (On Board Diagnostics) realizes information exchange and fault diagnosis between various control units inside the vehicle through standardized data interfaces and diagnostic protocols. The main function of the OBD system is to monitor the operating status and exhaust emissions of the engine to ensure that the vehicle meets environmental protection and safety standards during use. When a vehicle breaks down, the OBD system can automatically record the fault code and remind the driver to repair it in time through the MIL (malfunction indicator light) on the dashboard. OBD occupancy mainly refers to the situation where the car's OBD interface (on-board diagnostic system interface) is used or occupied by external devices.

[0033] The cockpit self-check refers to a comprehensive check of the systems, components and sensors inside the cockpit by the on-board computer system when the vehicle is started, to ensure that they can work properly and meet the safety and reliability requirements of vehicle operation. The purpose of this process is to promptly discover and deal with potential faults or problems to prevent accidents during driving. The cockpit self-check usually includes the following aspects: sensor (such as temperature sensor, pressure sensor, acceleration sensor, etc.) inspection, system (such as air conditioning system, audio system, navigation system, seat heating / ventilation system, etc.) inspection, safety equipment (including airbags, seat belts, etc.) inspection, lighting and signal (such as reading lights, ambient lights, instrument panel lights, turn signals, brake lights, etc.) inspection.

[0034] DOIP (Diagnostic Communication over Internet Protocol) is a diagnostic communication protocol based on Internet Protocol (IP) that allows remote diagnosis of vehicles over a network (such as Ethernet). The DOIP standard was developed by ISO (International Organization for Standardization) to provide a standardized method for automakers, service providers and car owners to efficiently and securely diagnose and communicate with vehicles over the network.

[0035] TBOX (Telematics BOX), also known as vehicle-mounted T-BOX, is a key component of modern Internet of Vehicles systems. It is mainly used to connect vehicles with backend systems and mobile applications (APP) to achieve real-time information transmission and remote control functions. It integrates multiple functional modules such as processors, GPS modules, 2G / 3G / 4G / 5G modules (with SIM card functions), and realizes communication and data exchange between vehicles (V2V), vehicles and infrastructure (V2I), and vehicles and the Internet (V2N) by connecting the vehicle-mounted CAN bus and the external cloud platform.

[0036] The development of communication technology and intelligent vehicle networking technology has led to the emergence of various complex applications. In order to ensure the safety of vehicles on the road, intelligent driving has emerged. More and more OEMs have launched vehicles with automatic driving functions. At present, vehicles equipped with intelligent driving functions need to be equipped with various sensors such as laser radar, millimeter wave radar, high-definition camera, GPS (Global Positioning System) positioning system, etc. to obtain real-time information about the surrounding environment. Vehicle driving data, face recognition data, AR-HUD (Augmented Reality-Head Up Display), intelligent vehicle networking and other types of data make wireless communication technology more complex. At the same time, automotive electronic and electrical components are becoming more and more complex. The probability of safety hazards in vehicles under complex working conditions will also increase. How to quickly predict vehicle driving risks and how to respond in time after the danger occurs requires vehicle fault monitoring and diagnosis. The application of edge computing in on-board remote diagnosis is based on the growing digitalization and networking needs of modern cars. With the rapid development of electronic devices and information technology in vehicles, modern cars have become highly complex network systems. Smart cars are equipped with various sensors, actuators and controllers, which can generate and process a large amount of data, including but not limited to engine operating status, vehicle position, speed, fuel consumption, passenger comfort indicators and safety-related parameters.

[0037] At present, remote fault diagnosis mainly uses the cloud to locate vehicle system services in real time, and can also support vehicle operation and maintenance monitoring, remote problem handling, customer service support, and user operations, completing the end-to-end closed-loop capability from data insight to execution. Remote fault monitoring and diagnosis are mainly achieved by using vehicle controllers and vehicle-cloud wireless communications. Specifically, remote diagnostic instructions are issued through the cloud, so that each vehicle controller can collect its data and information in real time, and upload vehicle faults to the cloud in a timely manner to achieve remote fault monitoring and diagnosis functions. At the same time, technicians can also use the cloud alarm information to troubleshoot, detect and analyze vehicle problems in real time to discover problems in advance and avoid risks. However, since modern vehicles are equipped with a large number of sensors, these sensors continuously generate data, and the amount of data surges, requiring fast and effective processing. For vehicle health monitoring and fault diagnosis, the real-time nature of data processing is crucial to ensure that possible faults can be monitored in a timely manner to avoid safety hazards. In addition, the transmission of large amounts of data poses a challenge to network bandwidth, especially in areas with poor network coverage, which may affect the speed and quality of data transmission. Edge computing, as a distributed computing paradigm, places data processing and application services as close to the data source as possible, that is, the "edge of the network." In the context of edge computing-based vehicle remote diagnostics, this means deploying computing resources inside or near the vehicle rather than relying entirely on remote cloud servers. This can reduce latency, save bandwidth, improve safety, and enhance autonomy.

[0038] Figure 1 It is a schematic diagram of an exemplary system architecture shown in an exemplary embodiment of the present application.

[0039] Reference Figure 1As shown, the system architecture may include a data acquisition device 101 and a computer device 102. The computer device 102 may be at least one of a desktop graphics processing unit (GPU) computer, a GPU computing cluster, a neural network computer, etc. The data acquisition device 101 is used to collect diagnostic trouble codes and vehicle operation data of the vehicle terminal. In this embodiment, the data acquisition device 101 obtains the above data and provides it to the computer device 102 for processing. Relevant technicians can use the computer device 102 to search for diagnostic trouble codes. If a first trouble code is found in the diagnostic trouble code, a first trouble result is determined according to the first trouble code; if a second trouble code is found in the diagnostic trouble code, an edge node is determined according to the location information of the vehicle terminal, the edge node is connected, and the second trouble code and the second operation data corresponding to the second trouble code are sent to the edge node. The edge node is at least one of the edge computing centers. If a third trouble code is found in the received second trouble code, the edge node is used to perform fault diagnosis according to the third trouble code and the third operation data corresponding to the third trouble code to obtain a second diagnostic result, wherein the second operation data includes the third operation data. It should be noted that the data acquisition device 101 and the computer device 102 provided in this embodiment are merely examples and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0040] It should be noted that the vehicle fault diagnosis method provided in the embodiment of the present application is generally executed by the computer device 102 , and accordingly, the vehicle fault diagnosis system is generally set in the computer device 102 .

[0041] Figure 2 is a block diagram of a vehicle fault diagnosis system shown in an exemplary embodiment of the present application. The system can be applied to Figure 1 The implementation environment shown in the figure is specifically configured in the computer device 102. The system can also be applied to other exemplary implementation environments and specifically configured in other devices. This embodiment does not limit the implementation environment to which the system is applicable.

[0042] In one embodiment of the present application, Figure 2As shown, the exemplary vehicle fault diagnosis system includes: a vehicle terminal 210 and an edge computing center 220. The vehicle terminal 210 is used to collect the diagnostic fault code and vehicle operation data of the vehicle terminal 210. If the first fault code is found in the diagnostic fault code, the first fault result is determined according to the first fault code; if the second fault code is found in the diagnostic fault code, the edge node is determined according to the location information of the vehicle terminal 210, the edge node is connected, and the second fault code and the second operation data corresponding to the second fault code are sent to the edge node, and the edge node is at least one of the edge computing centers 220; the edge node is used to perform fault diagnosis according to the third fault code and the third operation data corresponding to the third fault code if a third fault code is found in the received second fault code, and obtain a second diagnostic result, wherein the vehicle operation data includes the second operation data, and the second operation data includes the third operation data.

[0043] In this embodiment, the vehicle operation data includes but is not limited to one or more of basic operation parameters, brake and safety system parameters, vehicle driving parameters, power-related parameters and vehicle dynamic data, etc. Among them, the basic operation parameters include engine parameters (including engine start and shutdown time, engine temperature, speed, throttle opening, continuous working time, etc.), transmission system parameters (such as gearbox gear, shift mode, battery voltage, etc.), driving parameters (such as vehicle driving speed, mileage, steering angle, etc.), brake and safety system parameters include brake system working state (including brake master cylinder pressure, ABS (anti-lock brake system) action, etc.), front collision warning and automatic emergency braking function state, vehicle driving parameters include vehicle real-time position, driving trajectory, working mode, etc., power-related parameters include motor operating state (including motor speed, torque, temperature, etc.), power battery voltage, etc., and vehicle dynamic data, which refers to real-time data of sensors installed on various vehicle systems (such as brake system, lighting system, engine system, etc.).

[0044] In this embodiment, the method of determining the first fault result according to the first fault code may include determining the fault information corresponding to the first fault code according to the first fault code, and determining the first fault result according to the fault information. For example, in some vehicles, if the electronic control unit (ECU) of the engine detects that a specific sensor signal exceeds the normal range, it may generate a specific fault code, and this fault code is almost always caused by the fault of the sensor itself. In this case, replacing or repairing the sensor can usually solve the problem. Among them, the first fault code is a relatively simple fault code, and the method of determining that the diagnostic fault code is the first fault code may include: determining the fault code according to a preset fault code type, if the fault code type of the diagnostic fault code is a simple fault, then determining the diagnostic fault code as the first fault code; it is also possible to directly pre-set the first fault code, match the collected diagnostic fault code with the preset first fault code, and if the match is successful, then determine the diagnostic fault code as the first fault code.

[0045] In this embodiment, the vehicle terminal obtains the diagnostic fault code of the corresponding controller and the real-time vehicle operation data, and saves the freeze frame data related to the fault, and then performs self-diagnosis on the vehicle terminal and continuously monitors the vehicle condition. Most vehicle-side sensors have built-in self-diagnosis functions, which can automatically check their own operating status and report abnormal conditions to the controller. Usually, different types of sensors and vehicles have different test standards and procedures, and the controller will also continuously monitor the corresponding sensor signal and use the preset algorithm to determine whether the signal value is correct or not to achieve fault detection. The current signal value collected can be compared with the preset signal value. If the current signal value is equal to the preset signal value, it is determined that the current signal value is correct. If the current signal value is not equal to the preset signal value, it is determined that the current signal value is wrong and the sensor is judged to be faulty.

[0046] In this embodiment, if the second fault code is found in the diagnostic fault code, the edge node is determined according to the location information of the vehicle terminal and the coverage area of ​​the edge computing center. Specifically, if the vehicle terminal is determined to be within the coverage of the edge computing center according to the location information of the vehicle terminal and the coverage area of ​​the edge computing center, the corresponding edge computing center is determined as the edge node. Applying edge computing technology to the vehicle fault diagnosis system can perform remote fault diagnosis on the vehicle in real time and efficiently.

[0047] In this embodiment, the edge node can also perform fault diagnosis on the third fault code and the third operation data by receiving the fault diagnosis model sent by the server to obtain a second diagnosis result, so as to process fault data with high timeliness requirements or data with large safety hazards. The method for determining the third fault code includes determining according to a preset fault code type, and comparing the second fault code with the preset third fault code. Among them, the diagnostic fault code includes a first fault code and a second fault code, the second fault code includes a third fault code and a fourth fault code, the vehicle operation data includes a first operation data and a second operation data, and the second operation data includes a third operation data and a fourth operation data. Edge computing deploys data processing capabilities close to the data source, which means that data does not need to be transmitted to a remote server for a long time, so near real-time diagnosis and response can be achieved, which is especially important for scenarios that require instant feedback, such as emergency faults detected during vehicle driving. Through real-time fault detection and rapid response, vehicle downtime can be reduced, and vehicle availability and driver satisfaction can be improved.

[0048] In one embodiment of the present application, the vehicle fault diagnosis system also includes a server side, which is connected to the edge node and the vehicle terminal, and the server side is used for at least one of the following: if a fourth fault code and a fourth operating data corresponding to the fourth fault code are received from the edge node, then a fault diagnosis is performed according to the fourth fault code and the fourth operating data to obtain a third diagnosis result, wherein the fourth fault code is obtained by the edge node from the second fault code, and the second operating data includes the fourth operating data; if multiple historical operating data and the fault results corresponding to each historical operating data are obtained; then each historical operating data is used as an operating data sample, and the operating data sample is labeled according to the fault result to obtain a result sample label corresponding to each operating data sample; the operating data samples with the result sample label are model trained to obtain a fault diagnosis model, and the fault diagnosis model is sent to the edge node; if the first diagnosis result and the second diagnosis result sent by the edge node are received, then a maintenance suggestion is generated in combination with the first diagnosis result, the second diagnosis result and the third diagnosis result, and the maintenance suggestion is sent to the vehicle terminal, wherein the first diagnosis result is sent from the vehicle terminal to the edge node.

[0049] In this embodiment, if the edge node finds the fourth fault code from the second fault code, the fourth fault code and the fourth operating data corresponding to the fourth fault code are sent to the server side, wherein the fault data corresponding to the fourth fault code is complex, has low timeliness requirements, and has a large amount of data. The method for determining the fourth fault code includes determining it according to a preset fault code type, and comparing the second fault code with the preset fourth fault code to determine it. The server side can perform fault diagnosis on the fourth fault code and the fourth operating data sent by the road side according to the fault diagnosis model obtained by training, and obtain a third diagnosis result to process complex fault data that has low timeliness requirements or has a large amount of data.

[0050] In this embodiment, the cloud, i.e., the server-side diagnostic center, is responsible for storing and further optimizing the vehicle-side and edge server diagnostic data (diagnostic results) and uploading the data to the maintenance decision system center to generate specific diagnostic and maintenance suggestions for users or maintenance personnel to use, visualize the diagnostic data, and also support the processing of some delay-insensitive data.

[0051] In one embodiment of the present application, the edge node is also used for at least one of the following: pre-processing the received second fault code and second operation data, encrypting the pre-processed second fault code and the pre-processed second operation data according to a preset encryption algorithm, and sending them to the server, wherein the pre-processing operation includes at least one of data cleaning, anomaly detection, data compression, feature extraction and data conversion; receiving the first diagnosis result sent by the vehicle terminal, determining the vehicle operation state corresponding to the vehicle terminal according to the first diagnosis result, the second fault code and the second operation data, if the vehicle operation state is detected to be an abnormal state, generating prompt information according to the vehicle operation state, and sending the prompt information to the vehicle terminal to prompt the user; receiving the fault diagnosis model sent by the server, and performing fault diagnosis on the third fault code and the third operation data according to the fault diagnosis model to obtain the second diagnosis result. Sensitive vehicle data can be encrypted and preliminarily processed on the edge device, and only necessary information is uploaded to the cloud, which reduces the risk of data leakage and improves the overall security of the data.

[0052] In this embodiment, the edge computing center mainly includes obtaining the diagnostic data of the vehicle, i.e., the first diagnostic result, and the data source, i.e., the first operating data, and encrypting these data to ensure data security and make fault diagnosis more efficient. The edge computing center generally has various machine learning algorithms built in, which can identify abnormal data and discover potential abnormal situations.

[0053] In this embodiment, the edge computing center can reduce the amount of data that needs to be transmitted to the cloud to reduce the cloud network load and save bandwidth. The edge computing center can also monitor the vehicle's operating status and driving behavior in real time based on the collected vehicle sensor data, such as engine temperature, oil pressure, speed, etc. When an abnormal situation is detected, the system can respond quickly and can automatically adjust the vehicle's driving mode or remind the driver to pay attention to potential problems; by timely discovering and solving potential problems, it helps to improve driving safety. Basic fault diagnosis and processing can also be performed offline; sensitive data can be processed locally without uploading to the cloud, which enhances data security and privacy protection; artificial intelligence and machine learning algorithms are used for data analysis and prediction.

[0054] In this embodiment, the edge computing center is equivalent to a small cloud server. Its computing power is not as strong as that of the cloud center, but it is closer to the terminal device and can process real-time and urgent data on the vehicle side to reduce the network congestion and bandwidth consumption faced by direct uploading to the cloud computing, and also reduce the task processing delay. The edge computing center can perform data preprocessing on the diagnostic data, and the data preprocessing includes but is not limited to at least one of data cleaning, anomaly detection, data compression, feature extraction, and data conversion. Among them, data cleaning is to remove invalid or erroneous data points, such as sensors may occasionally send outliers, which need to be filtered; anomaly detection is to use statistical methods or machine learning models to identify outliers or abnormal behaviors, such as by setting thresholds or using clustering algorithms to identify unusual data patterns; data compression is to compress data without affecting the quality of data analysis, reducing the bandwidth requirements for data transmission; feature extraction is to extract useful features from raw data, simplify data sets and increase the speed of subsequent processing; data conversion is to convert data into a form more suitable for further analysis as needed.

[0055] In this embodiment, the edge computing center is usually arranged close to the terminal device. For example, the edge computing roadside unit in the Internet of Vehicles refers to the edge computing devices deployed on the roadside, which can process data from vehicles and roadside sensors to support real-time or near real-time applications and services.

[0056] In one embodiment of the present application, the vehicle terminal activates the remote diagnosis function in the following manner: receiving a remote diagnosis activation request sent by the server to obtain current vehicle data; matching the current vehicle data with preset vehicle data, and determining the current vehicle condition based on the matching result; if the current vehicle condition is the preset vehicle condition, activating the remote diagnosis function, and sending the activation result to the server, wherein the remote diagnosis function is to perform fault diagnosis on the fourth fault code and the fourth operating data through the server.

[0057] In this embodiment, the current vehicle data includes but is not limited to one or more of system update status, firmware version changes, network communication data, OBD diagnostic session status, diagnostic trouble codes, communication interface status, self-test flags, dashboard indicator lights and vehicle system logs. The preset vehicle conditions include that the vehicle is not in OTA flashing, not in OBD occupancy and not in cockpit self-test status.

[0058] In one embodiment of the present application, the vehicle fault diagnosis system turns off the remote diagnosis function in at least one of the following ways: the server side starts a first timer after turning on the remote diagnosis function, and if the first timing value of the first timer is greater than or equal to the first time threshold, the remote diagnosis function is turned off; the server side starts a second timer after sending a remote diagnosis start request, and if the second timing value of the second timer is greater than or equal to the second time threshold, the remote diagnosis function is turned off.

[0059] In one embodiment of the present application, the vehicle terminal is connected to the server side in the following manner: if the activation result is successful, the server side sends a link establishment request and a route activation request to the vehicle terminal; after the vehicle terminal receives the link establishment request and the route activation request, the vehicle terminal establishes a link and activates the route through the vehicle gateway and the electronic control unit connected to the vehicle gateway and the on-board sensor to connect the vehicle terminal to the server side.

[0060] In one embodiment of the present application, the diagnosis is completed by the vehicle side, i.e., the vehicle terminal, the road side, i.e., the edge computing center, and the cloud side, i.e., the server side, but the three have different functions. The vehicle side is responsible for obtaining diagnostic data, i.e., diagnostic fault codes and vehicle operation data, the edge server is responsible for encrypting and processing the data and uploading it to the cloud center, and the cloud side is responsible for storing and further optimizing the diagnostic data. Generally speaking, sensitive data will generate encryption keys on the vehicle terminal and the edge computing node, and the keys will be distributed to the receiver using a secure channel, including the server side. At this time, the keys will be securely stored in the edge computing device, and these keys will be used for data acquisition and processing when data processing is performed. The vehicle side can also match the first fault code in the diagnostic fault code with the preset fault code, and determine the first diagnostic result according to the matching result to process simple fault data. The road side can also perform fault diagnosis on the third fault code and the third operation data by receiving the fault diagnosis model sent by the cloud side to obtain the second diagnostic result, so as to process fault data with high timeliness requirements or data with greater safety hazards, wherein the diagnostic fault code includes the first fault code and the second fault code, and the second fault code includes the third fault code and the fourth fault code. The cloud can also perform fault diagnosis on the fourth fault code and fourth operating data sent by the road end according to the trained fault diagnosis model to obtain a third diagnosis result to process complex fault data with low timeliness requirements or large data volume.

[0061] Figure 3 is a schematic diagram of the architecture of a vehicle fault diagnosis system shown in an exemplary embodiment of the present application, such as Figure 3 As shown, in an exemplary embodiment, the vehicle fault diagnosis system mainly includes three ends: the vehicle end (vehicle terminal), the road end (edge ​​computing center), and the cloud end (server end). The three ends have a total of six parts, among which the cloud end includes the maintenance decision system center, the remote diagnosis management platform, and the remote diagnosis data processing center. The vehicle end includes the vehicle-mounted network terminal and the vehicle-end control center. The road end includes the edge processing center. The maintenance decision system center mainly generates specific vehicle maintenance suggestions based on the analysis results of the remote diagnosis data processing center, and sends them to the maintenance decision system center, so that users or operation and maintenance personnel can view the diagnosis report and maintenance suggestions in the maintenance decision system center, so as to take corresponding measures in time; the remote diagnosis management platform is mainly responsible for issuing remote diagnosis instructions to the vehicle-mounted network terminal and real-time collection and monitoring of vehicle-side fault alarms, and obtaining remote diagnosis instructions fed back by the vehicle end; the remote diagnosis data processing center is mainly responsible for processing and optimizing the pre-processing analysis diagnosis data uploaded by the edge processing center, and timely uploading the diagnosis results to the maintenance decision system center for users to view; the vehicle-mounted network terminal is mainly responsible for sending remote diagnosis The instructions in the MQTT protocol format issued by the fault management platform are converted into instructions in the SOME / IP protocol format and passed to the diagnostic task management center of the vehicle-side control center. At the same time, the fault information and alarm messages uploaded by the vehicle-side domain controller are also forwarded. The vehicle-side control center includes the diagnostic task management center, the diagnostic command filtering center and the diagnostic gateway. It is mainly responsible for coordinating the diagnostic needs of various electronic control units and controllers, and is also responsible for actively uploading the alarm messages of the domain controller to the remote diagnostic data processing center; the edge processing center is mainly responsible for receiving the diagnostic data uploaded by the vehicle-mounted sensors and pre-processing the data to reduce the load on the cloud server, reduce network dependence, save bandwidth and cost, and improve the real-time performance of diagnosis to meet low latency requirements.

[0062] In this embodiment, the main functions that can be realized by the vehicle fault diagnosis system include: big data monitoring, online monitoring of fault alarms, remote online diagnosis of vehicle faults, remote online reading of vehicle data streams, and remote online clearing of vehicle faults, etc. Its main functional modules include remote fault diagnosis wake-up strategy, remote fault diagnosis on and off, remote fault diagnosis execution, remote diagnosis management, and remote fault monitoring of edge servers.

[0063] In this embodiment, the remote diagnosis management platform uses the MQTT protocol to send a remote diagnosis start request to the vehicle-mounted network terminal, and then converts the start request instruction into an instruction of the SOME / IP protocol and sends it to the vehicle. After receiving the remote diagnosis start request from the cloud, the vehicle needs to perform a vehicle condition check, such as checking whether the vehicle is in OTA flashing, whether it is in OBD occupation, whether it is in the cockpit self-inspection state, etc. If the vehicle-side condition checks meet the preset vehicle conditions, the remote diagnosis start response is fed back to the vehicle-mounted network terminal, in response to the remote diagnosis start success instruction, that is, the start result is successful, and then forwarded to the cloud to start the remote diagnosis instruction.

[0064] In this embodiment, the cloud port and the vehicle port use DOIP protocol instructions to establish links and activate routes. At the same time, the vehicle control center needs to establish DOIP links and activate routes with its multiple electronic control units and on-board sensors through the diagnostic gateway.

[0065] In this embodiment, the vehicle-side control center receives the diagnostic request sent from the cloud and routes it to the corresponding electronic control unit node and the on-board sensor. The destination node executes the diagnostic request and replies with an affirmative or negative response. The diagnostic response is fed back to the cloud using the same routing path, and then the remote diagnostic management platform parses and presents the remote fault diagnosis results.

[0066] In this embodiment, after the vehicle-side control center receives the relevant configuration created by the remote diagnosis management platform, the vehicle-side needs to carry the current configuration version of the vehicle itself when logging into the cloud and verify the configuration version with the cloud. After receiving the corresponding configuration and initializing the alarm-related master control service, the vehicle-side domain controller will filter and encapsulate its own fault information and alarm messages, and upload them to the maintenance decision system center in real time, and the maintenance decision system center will parse and display the alarm information.

[0067] In this embodiment, sensors inside and outside the vehicle are used to collect various data and upload these data to the edge server, i.e., the edge processing center, which can be a small computer installed on the vehicle. The edge server is responsible for real-time processing and analysis of the data uploaded by the vehicle, and the edge computing center can perform preliminary data cleaning, anomaly detection, and data identification, reducing the amount of data that needs to be transmitted to the cloud, improving response speed, and reducing network bandwidth requirements.

[0068] In this embodiment, both the cloud and the vehicle support shutting down the remote fault monitoring and diagnosis tasks, that is, shutting down the remote diagnosis function. After the vehicle receives the remote fault diagnosis start command, it starts the first local timer on the vehicle. If the vehicle conditions do not meet the preset vehicle conditions, it performs a rollback operation, disconnects the link, and sends the remote diagnosis shutdown command to the vehicle-mounted network terminal and forwards it to the cloud to shut down the remote diagnosis function. After the cloud sends the remote diagnosis start request, the cloud will start the second timer. If the cloud does not receive the remote diagnosis start response within the second time threshold, the cloud will send a remote fault diagnosis shutdown request to the vehicle-mounted network terminal to shut down the remote diagnosis function.

[0069] Figure 4 is a flow chart of a vehicle fault diagnosis method shown in an exemplary embodiment of the present application. The vehicle fault diagnosis method can be executed by a computing and processing device. The computing and processing device can be Figure 1 The computer device 102 shown in FIG. Figure 4 As shown, the vehicle fault diagnosis method at least includes steps S1 to S8, which are described in detail as follows:

[0070] In step S1, after the vehicle wakes up and TBOX logs in to the cloud, the remote diagnosis management platform uses the MQTT protocol to send a remote diagnosis start request to TBOX. At the same time, TBOX converts to the SOMEIP protocol to send a remote diagnosis start request to the vehicle. At this time, the vehicle starts the vehicle condition check and feeds back the start result to the cloud.

[0071] In step S2, after the vehicle-side remote diagnosis function is turned on, the successful response will be forwarded by TBOX to the remote diagnosis management platform, and then the remote diagnosis center will send a link establishment request and a routing activation request to the vehicle-side control center through the instructions of the port DOIP protocol.

[0072] In step S3, after receiving the route activation request and link establishment request, the vehicle-side control center performs route activation and link establishment processing, and sends DOIP protocol instructions to each electronic control unit and sensor through the diagnostic gateway to enable the remote diagnostic function.

[0073] In step S4, after the remote diagnosis function is turned on, the corresponding sensor on the vehicle side starts fault detection and uploads the diagnostic data to the edge computing center through a wireless link for preprocessing, where the diagnostic data includes diagnostic fault codes and vehicle operation data.

[0074] In step S5, the edge computing center pre-processes the diagnostic data and uploads the diagnostic data analysis results to the remote diagnostic data processing center.

[0075] In step S6, the remote diagnosis data processing center stores and further optimizes the diagnosis data and then uploads the data to the maintenance decision system center to generate specific diagnosis and maintenance suggestions for users or maintenance personnel to use.

[0076] In step S7, users and maintenance personnel may receive diagnostic reports and maintenance suggestions through the maintenance decision system center to support vehicle problem optimization.

[0077] In step S8, the cloud and the vehicle side need to start their own timers after turning on the remote diagnosis. After the timer condition is reached, the cloud and the vehicle side support turning off the remote diagnosis and disconnecting the link.

[0078] This application reduces the reliance on the network through edge computing. Even when the network is unstable or disconnected, preliminary diagnosis can be performed locally. Edge computing can pre-process data locally and only transmit key data to the cloud, so it can significantly reduce the use of network bandwidth and thus reduce costs. Edge computing can also better adapt to large-scale deployments because each edge device can process data independently, reducing the burden on the central server and making the entire system easier to expand. At the same time, it can provide personalized diagnosis and maintenance recommendations based on the specific situation of each vehicle, such as predicting possible future failures based on the vehicle's usage patterns and historical records.

[0079] This application reduces the time it takes for data to travel to and from the cloud, and the advantage is more obvious when network latency is high, which is particularly important for emergency situations. The on-board diagnostic data is also uploaded to the edge server for preprocessing and preliminary analysis, which can greatly improve the efficiency of system data processing. At the same time, edge computing can process and upload only key information in real time, greatly reducing transmission time and processing time. This application also combines the advantages of edge computing, placing data processing and computing power at the edge of the network, reducing the risk of data leakage, enhancing data privacy protection, and also reducing cloud load and improving resource utilization.

[0080] In one embodiment of the present application, a vehicle fault diagnosis method is provided, which is applied to an edge computing center. The vehicle fault diagnosis method includes: obtaining a diagnostic fault code and vehicle operation data of a vehicle terminal, wherein the vehicle terminal is used to collect the diagnostic fault code and vehicle operation data of the vehicle terminal, and if a first fault code is found in the diagnostic fault code, a first fault result is determined according to the first fault code; if a second fault code is found in the diagnostic fault code, an edge node is determined according to location information of the vehicle terminal, the edge node is connected, and the second fault code and second operation data corresponding to the second fault code are sent to the edge node, which is at least one of the edge computing centers; if a third fault code is found in the received second fault code, a fault diagnosis is performed according to the third fault code and the third operation data corresponding to the third fault code to obtain a second diagnostic result, wherein the second operation data includes the third operation data.

[0081] In one embodiment of the present application, a vehicle fault diagnosis method is provided, which is applied to a vehicle terminal. The vehicle fault diagnosis method includes: collecting diagnostic fault codes and vehicle operation data of the vehicle terminal. If a first fault code is found in the diagnostic fault code, a first fault result is determined according to the first fault code; if a second fault code is found in the diagnostic fault code, an edge node is determined according to location information of the vehicle terminal, the edge node is connected, and the second fault code and the second operation data corresponding to the second fault code are sent to the edge node. The edge node is at least one of the edge computing centers. If a third fault code is found in the received second fault code, the edge node is used to perform fault diagnosis according to the third fault code and the third operation data corresponding to the third fault code to obtain a second diagnostic result, wherein the second operation data includes the third operation data.

[0082] It should be noted that the vehicle fault diagnosis method provided in the above embodiment and the vehicle fault diagnosis system provided in the above embodiment belong to the same concept, and the specific operation mode of each step has been described in detail in the system embodiment, which will not be repeated here. In practical applications, the vehicle fault diagnosis system provided in the above embodiment can allocate the above functions to different functional modules as needed, that is, divide the internal structure of the device into different functional modules to complete all or part of the functions described above, and this is not limited here.

[0083] The embodiment of the present application also provides an electronic device, including: one or more processors; a storage device for storing one or more programs, when the one or more programs are executed by the one or more processors, the electronic device implements the vehicle fault diagnosis method provided in each of the above embodiments. In this embodiment, the electronic device includes a vehicle terminal.

[0084] Figure 5The structure diagram of the computer system suitable for implementing the electronic device of the embodiment of the present application is shown. It should be noted that: Figure 5 The computer system 500 of the electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0085] like Figure 5 As shown, the computer system 500 includes a central processing unit (CPU) 501, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 502 or the program loaded from the storage part 508 to the random access memory (RAM) 503, such as executing the methods provided in the above-mentioned various embodiments. In the RAM 503, various programs and data required for system operation are also stored. The CPU 501, the ROM 502 and the RAM 503 are connected to each other through the bus 504. The input / output (I / O) interface 505 is also connected to the bus 504.

[0086] The following components are connected to the I / O interface 505: an input section 506 including a keyboard, a mouse, etc.; an output section 507 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker; a storage section 508 including a hard disk, etc.; and a communication section 509 including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication section 509 performs communication processing via a network such as the Internet. A drive 510 is also connected to the I / O interface 505 as needed. A removable medium 511, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 510 as needed so that a computer program read therefrom is installed into the storage section 508 as needed.

[0087] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a computer program for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication section 509, and / or installed from a removable medium 511. When the computer program is executed by a central processing unit (CPU) 501, various functions defined in the system of the present application are executed.

[0088] It should be noted that the computer-readable medium shown in the embodiment of the present application can be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium can be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media can include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, wherein a computer-readable computer program is carried. This propagated data signal can take a variety of forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. A computer program contained on a computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0089] The flowchart and block diagram in the accompanying drawings illustrate the possible architecture, functions and operations of the system, method and computer program product according to various embodiments of the present application. Wherein, each box in the flowchart or block diagram can represent a module, a program segment, or a part of the code, and the above-mentioned module, program segment, or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0090] The units involved in the embodiments described in this application may be implemented by software or hardware, and the units described may also be set in a processor. The names of these units do not, in some cases, constitute limitations on the units themselves.

[0091] Another aspect of the present application further provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor of a computer, the computer executes the vehicle fault diagnosis method provided in the above embodiments. The computer-readable storage medium may be included in the electronic device described in the above embodiments, or may exist independently without being assembled into the electronic device.

[0092] It should be noted that, although several modules or units of the equipment for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present application, the features and functions of two or more modules or units described above can be embodied in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into being embodied by multiple modules or units.

[0093] Another aspect of the present application also provides a computer program product or a computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the vehicle fault diagnosis method provided in each of the above embodiments.

[0094] Through the description of the above implementation methods, it is easy for those skilled in the art to understand that the example implementation methods described here can be implemented by software or by combining software with necessary hardware. Therefore, the technical solution according to the implementation methods of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, a touch terminal, or a network device, etc.) to execute the method according to the implementation methods of the present application.

[0095] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the embodiments disclosed herein. The present application is intended to cover any variations, uses or adaptations of the present application, which follow the general principles of the present application and include common knowledge or customary technical means in the art that are not disclosed in the present application.

[0096] The above embodiments are merely illustrative of the principles and effects of the present application, and are not intended to limit the present application. Anyone familiar with the technology may modify or change the above embodiments without violating the spirit and scope of the present application. Therefore, all equivalent modifications or changes made by a person of ordinary skill in the art without departing from the spirit and technical ideas disclosed in the present application shall still be covered by the claims of the present application.

Claims

1. A vehicle fault diagnosis system, characterized in that: The vehicle fault diagnosis system includes a vehicle terminal and an edge computing center; The vehicle terminal is used to collect diagnostic trouble codes and vehicle operation data of the vehicle terminal, and if a first trouble code is found in the diagnostic trouble codes, determine a first trouble result according to the first trouble code; If a second fault code is found in the diagnostic fault code, an edge node is determined according to the location information of the vehicle terminal, the edge node is connected, and the second fault code and second operation data corresponding to the second fault code are sent to the edge node, the edge node being at least one of the edge computing centers; The edge node is used to perform fault diagnosis according to the third fault code and third operating data corresponding to the third fault code to obtain a second diagnosis result if a third fault code is found in the received second fault code, wherein the second operating data includes the third operating data.

2. The vehicle fault diagnosis system according to claim 1, characterized in that: The vehicle fault diagnosis system further includes a server end, which is connected to the edge node and the vehicle terminal, and is used for at least one of the following: If a fourth fault code and fourth operating data corresponding to the fourth fault code sent by the edge node are received, a fault diagnosis is performed according to the fourth fault code and the fourth operating data to obtain a third diagnosis result, wherein the fourth fault code is obtained by the edge node from the second fault code, and the second operating data includes the fourth operating data; If multiple historical operation data and the fault results corresponding to each of the historical operation data are obtained; each of the historical operation data is used as an operation data sample, and the operation data sample is labeled according to the fault result to obtain the result sample label corresponding to each of the operation data samples; the operation data samples with the result sample label are trained on the model to obtain a fault diagnosis model, and the fault diagnosis model is sent to the edge node; If a first diagnostic result and a second diagnostic result sent by the edge node are received, a maintenance suggestion is generated by combining the first diagnostic result, the second diagnostic result and the third diagnostic result, and the maintenance suggestion is sent to the vehicle terminal, wherein the first diagnostic result is sent from the vehicle terminal to the edge node.

3. The vehicle fault diagnosis system according to claim 2, characterized in that: The edge node is also used for at least one of the following: Performing a preprocessing operation on the received second fault code and the second operation data, encrypting the preprocessed second fault code and the preprocessed second operation data according to a preset encryption algorithm, and sending them to the server, wherein the preprocessing operation includes at least one of data cleaning, anomaly detection, data compression, feature extraction, and data conversion; receiving the first diagnostic result sent by the vehicle terminal, determining a vehicle operating state corresponding to the vehicle terminal according to the first diagnostic result, the second fault code and the second operating data, and if it is detected that the vehicle operating state is an abnormal state, generating prompt information according to the vehicle operating state, and sending the prompt information to the vehicle terminal to prompt a user; The fault diagnosis model sent by the server is received, and fault diagnosis is performed on the third fault code and the third operating data according to the fault diagnosis model to obtain the second diagnosis result.

4. The vehicle fault diagnosis system according to claim 2, characterized in that: The vehicle terminal starts the remote diagnosis function in the following ways: Receiving a remote diagnosis start request sent by the server and obtaining current vehicle data; Matching the current vehicle data with preset vehicle data, and determining the current vehicle condition according to the matching result; If the current vehicle condition is a preset vehicle condition, the remote diagnosis function is turned on and the turn-on result is sent to the server side, wherein the remote diagnosis function performs fault diagnosis on the fourth fault code and the fourth operating data through the server side.

5. The vehicle fault diagnosis system according to claim 4, characterized in that: The vehicle fault diagnosis system disables the remote diagnosis function by at least one of the following methods: The server starts a first timer after starting the remote diagnosis function, and if a first timing value of the first timer is greater than or equal to a first time threshold, the remote diagnosis function is turned off; The server starts a second timer after sending the remote diagnosis start request, and if a second timing value of the second timer is greater than or equal to a second time threshold, the remote diagnosis function is turned off.

6. The vehicle fault diagnosis system according to claim 4, characterized in that: The vehicle terminal is connected to the server in the following manner: If the activation result is successful, the server sends a link establishment request and a routing activation request to the vehicle terminal; After receiving the link establishment request and the route activation request, the vehicle terminal establishes a link and activates the route through the vehicle gateway, the electronic control unit connected to the vehicle gateway and the vehicle-mounted sensor to connect the vehicle terminal to the server.

7. A vehicle fault diagnosis method, characterized in that: Applied to the edge computing center, the vehicle fault diagnosis method includes: Acquire a diagnostic trouble code and vehicle operation data of a vehicle terminal, wherein the vehicle terminal is used to collect the diagnostic trouble code and vehicle operation data of the vehicle terminal, and if a first trouble code is found in the diagnostic trouble code, determine a first trouble result according to the first trouble code; if a second trouble code is found in the diagnostic trouble code, determine an edge node according to the location information of the vehicle terminal, connect to the edge node, and send the second trouble code and second operation data corresponding to the second trouble code to the edge node, wherein the edge node is at least one of the edge computing centers; If the third fault code is found in the received second fault code, fault diagnosis is performed according to the third fault code and third operating data corresponding to the third fault code to obtain a second diagnosis result, wherein the second operating data includes the third operating data.

8. A vehicle fault diagnosis method, characterized in that: Applied to a vehicle terminal, the vehicle fault diagnosis method comprises: The diagnostic trouble code and vehicle operation data of the vehicle terminal are collected. If a first trouble code is found in the diagnostic trouble code, a first trouble result is determined according to the first trouble code. If a second trouble code is found in the diagnostic trouble code, an edge node is determined according to the location information of the vehicle terminal, the edge node is connected, and the second trouble code and the second operation data corresponding to the second trouble code are sent to the edge node. The edge node is at least one of the edge computing centers. If a third trouble code is found in the received second trouble code, the edge node is used to perform fault diagnosis according to the third trouble code and the third operation data corresponding to the third trouble code to obtain a second diagnostic result, wherein the second operation data includes the third operation data.

9. A vehicle terminal, characterized in that: The vehicle terminal comprises: one or more processors; A storage device for storing one or more programs, which, when executed by the one or more processors, enables the vehicle terminal to implement the vehicle fault diagnosis method as described in claim 8.

10. A computer-readable storage medium, characterized in that: A computer program is stored thereon, and when the computer program is executed by a processor of a computer, the computer is caused to execute the vehicle fault diagnosis method described in claim 7 or 8.

Images