Fault diagnosis method, system, and device, and medium

Abstract

A fault diagnosis method, system, and device, and a medium. The diagnosis method comprises: receiving a vehicle diagnosis push message sent by a remote diagnosis server (10) (S210), wherein the vehicle diagnosis push message at least comprises one of a diagnosis task type and diagnosis script information; obtaining a corresponding target diagnosis script file and a corresponding target diagnosis condition on the basis of the diagnosis task type and / or the diagnosis script information (S220), wherein the target diagnosis script file is obtained by converting a diagnosis database and a diagnosis sequence, and the target diagnosis script file is an interpreted language file; and performing fault diagnosis on a target vehicle according to the target diagnosis condition and the target diagnosis script file (S230). The operation that a remote diagnosis client (20) analyzes a diagnosis sequence and frequently reads a diagnosis database is omitted, thereby relieving the load of the remote diagnosis client (20), and improving the operation efficiency of a diagnosis task; and additionally, diagnosis task types are partitioned, thereby improving the diagnosis efficiency.

Description

Fault diagnosis method, system, equipment and medium

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on August 29, 2023, with application number 202311105130.7, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of vehicle technology, and in particular to a fault diagnosis method, system, device and medium. Background Art

[0003] With the integration of the Internet and traditional vehicle companies, more and more vehicle manufacturers need to remotely diagnose and refresh vehicles.

[0004] Remote vehicle diagnostics refers to a diagnostic technology that leverages the vehicle's mobile communications capabilities (Wi-Fi / 4G / 5G) to remotely control and diagnose the vehicle through the OEM's backend (or mobile app), without requiring the vehicle to be driven back to a physical dealership. Remote OTA (Over-The-Air) flashing is one such application of remote diagnostics. Furthermore, by integrating with cutting-edge technologies such as the Internet of Things, big data, and cloud computing, remote diagnostics can also provide important support to OEMs in areas such as R&D testing, production line electrical inspections, and after-sales diagnostics.

[0005] First, remote diagnosis can collect data online, reducing development cycles and costs. During the R&D phase, vehicles need to undergo extensive road and endurance testing, but the test vehicles are equipped with limited data collection equipment. Through remote diagnosis, vehicle failures that occur during the test can be promptly fed back to R&D personnel for analysis and simulation, quickly assisting in resolving the failures. Secondly, remote diagnosis can implement initialization and functional testing across workstations on the production line, as well as OTA refresh of the production line, enabling customized production of automotive software to meet the customized needs of car owners. Finally, remote diagnosis can periodically monitor vehicle status, diagnose vehicle health in real time, and use big data statistical analysis to provide vehicle fault warnings. This information can then be pushed to the manufacturer's after-sales vehicle store through the backend for vehicle maintenance and repair guidance.

[0006] However, the diagnostic database is pre-installed on the vehicle side, and the cloud directly sends the diagnostic sequence file to the vehicle side. The vehicle side parses the diagnostic sequence file and then obtains the corresponding data from the diagnostic database based on the diagnostic sequence to synthesize diagnostic instructions for diagnosis. Since data needs to be frequently obtained from the diagnostic database based on the diagnostic sequence, the resource overhead of the vehicle-side master node is relatively large and the operating efficiency is low. In addition, all diagnostic tasks require the diagnostic sequence file to be sent from the cloud side, and the vehicle side then obtains the data from the diagnostic database based on the diagnostic sequence to synthesize diagnostic instructions for diagnosis, resulting in low diagnostic efficiency.

[0007] Summary of the Invention

[0008] The present application provides a fault diagnosis method, system, device and medium to solve the technical problems of high resource consumption, low operating efficiency and low diagnostic efficiency in related technologies.

[0009] According to one aspect of the present application, a fault diagnosis method is provided, which is applied to a remote diagnosis client, comprising:

[0010] Receive a vehicle diagnosis push message sent by a remote diagnosis server; wherein the vehicle diagnosis push message includes at least one of the following: a diagnosis task type and a diagnosis script information;

[0011] Acquire a corresponding target diagnostic script file and a corresponding target diagnostic condition according to the diagnostic task type and / or the diagnostic script information; wherein the target diagnostic script file is obtained by converting a diagnostic database and a diagnostic sequence, and the target diagnostic script file is an interpretive language file;

[0012] Fault diagnosis is performed on a target vehicle according to the target diagnosis condition and the target diagnosis script file.

[0013] According to another aspect of the present application, a fault diagnosis device is provided, which is applied to a remote diagnosis client, comprising:

[0014] A receiving module, configured to receive a vehicle diagnosis push message sent by a remote diagnosis server; wherein the vehicle diagnosis push message includes at least one of the following: a diagnosis task type and a diagnosis script information;

[0015] an acquisition module, configured to acquire a corresponding target diagnostic script file and a corresponding target diagnostic condition according to the diagnostic task type and / or the diagnostic script information; wherein the target diagnostic script file is obtained by converting a diagnostic database and a diagnostic sequence, and the target diagnostic script file is an interpretive language file;

[0016] The diagnostic module is used to perform fault diagnosis on the target vehicle according to the target diagnostic condition and the target diagnostic script file.

[0017] According to another aspect of the present application, a fault diagnosis system is provided, comprising: a remote diagnosis server and a remote diagnosis client; wherein the remote diagnosis server comprises: a diagnosis management platform, a push server and a content distribution network; the remote diagnosis client comprises: a diagnosis client and a diagnosis script engine;

[0018] The diagnostic database and the corresponding diagnostic sequence are synthesized into a corresponding diagnostic script file through the diagnostic management platform; when the diagnostic client receives a vehicle diagnostic push message sent by the push server carrying the diagnostic task type and / or diagnostic script information, the diagnostic client receives the corresponding target diagnostic script file and the corresponding target diagnostic condition issued by the content distribution network based on the diagnostic task type and / or the diagnostic script information, and sends the target diagnostic script file to the diagnostic script engine, so that the diagnostic script engine parses the target diagnostic script file and performs fault diagnosis on the target vehicle according to the target diagnostic condition and the target diagnostic script file; wherein, the target diagnostic script file is obtained by converting the diagnostic database and the corresponding diagnostic sequence through the diagnostic management platform, and the target diagnostic script file is an interpreted language file.

[0019] According to another aspect of the present application, a fault diagnosis device is provided, comprising:

[0020] at least one processor; and

[0021] a memory communicatively connected to the at least one processor; wherein,

[0022] The memory stores a computer program that can be executed by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the fault diagnosis method described in any embodiment of the present application.

[0023] According to another aspect of the present application, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the fault diagnosis method described in any embodiment of the present application when executed.

[0024] The technical solution of the embodiment of the present application converts the diagnostic database and diagnostic sequence into an interpreted language-based diagnostic script file that is more suitable for operation by the remote diagnostic client through the remote diagnostic server, and sends it to the remote diagnostic client, thereby eliminating the need for the remote diagnostic client to parse the diagnostic sequence and frequently read the diagnostic database, reducing the load on the remote diagnostic client and improving the operating efficiency of the diagnostic task; at the same time, the diagnostic task type is partitioned to facilitate obtaining the corresponding target diagnostic script file from different databases according to the diagnostic task type, thereby improving the diagnostic efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] FIG1 is a structural block diagram of a fault diagnosis system provided in an embodiment of the present application;

[0026] FIG2 is a flow chart of a fault diagnosis method provided by an embodiment of the present application;

[0027] FIG3 is a schematic diagram of a configuration of a data structure of a diagnostic script file provided in an embodiment of the present application;

[0028] FIG4 is a flow chart of another fault diagnosis method provided by an embodiment of the present application;

[0029] FIG5 is a flowchart of another fault diagnosis method provided in an embodiment of the present application;

[0030] FIG6 is a flowchart of another fault diagnosis method provided in an embodiment of the present application;

[0031] FIG7 is a flowchart of another fault diagnosis method provided in an embodiment of the present application;

[0032] FIG8 is a flowchart of another fault diagnosis method provided in an embodiment of the present application;

[0033] FIG9 is a block diagram of another fault diagnosis system provided in an embodiment of the present application;

[0034] FIG10 is a schematic structural diagram of a fault diagnosis device provided in an embodiment of the present application;

[0035] FIG11 is a structural block diagram of a fault diagnosis device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0036] The technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. The described embodiments are only part of the embodiments of the present application, rather than all the embodiments.

[0037] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in a sequence other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0038] In one embodiment, FIG1 is a structural block diagram of a fault diagnosis system provided by an embodiment of the present application. The fault diagnosis method provided by an embodiment of the present application is executed by a remote diagnosis client in the fault diagnosis system. As shown in FIG1 , the fault diagnosis system in the embodiment of the present application includes: a remote diagnosis server 10 and a remote diagnosis client 20; wherein the remote diagnosis server 10 includes: a diagnosis management platform 101, a push server 102 and a content distribution network 103; the remote diagnosis client 20 includes: a diagnosis client 201 and a diagnosis script engine 202;

[0039] The diagnostic database and the corresponding diagnostic sequence are synthesized into a corresponding diagnostic script file through the diagnostic management platform 101; when the diagnostic client 201 receives a vehicle diagnostic push message carrying the diagnostic task type and / or diagnostic script information sent by the push server 201, the diagnostic client 201 receives the corresponding target diagnostic script file and the corresponding target diagnostic condition issued by the content distribution network 103 based on the diagnostic task type and / or diagnostic script information, and sends the target diagnostic script file to the diagnostic script engine 202, so that the diagnostic script engine 202 parses the target diagnostic script file and performs fault diagnosis on the target vehicle according to the target diagnostic condition and the target diagnostic script file; wherein, the target diagnostic script file is obtained by converting the diagnostic database and the corresponding diagnostic sequence through the diagnostic management platform 101, and the target diagnostic script file is an interpreted language file.

[0040] In one embodiment, FIG2 is a flow chart of a fault diagnosis method provided by an embodiment of the present application. This embodiment is applicable to situations where vehicle fault diagnosis is simple and convenient. The method can be performed by a fault diagnosis device, which can be implemented in the form of hardware and / or software and can be configured in a fault diagnosis device. The fault diagnosis device can be a remote diagnosis client. As shown in FIG2 , the method includes:

[0041] S210: Receive a vehicle diagnosis push message sent by a remote diagnosis server.

[0042] The vehicle diagnostic push message includes at least one of the following: a diagnostic task type and diagnostic script information. The remote diagnostic server may also be referred to as a remote diagnostic server or a remote diagnostic cloud (referred to as the cloud). A vehicle diagnostic push message pushes information related to a diagnostic task to a remote diagnostic client. The vehicle diagnostic push message may include the diagnostic task type and / or diagnostic script information. The diagnostic task type represents different types of diagnostic tasks, including basic diagnostics and script diagnostics. Basic diagnostics refers to diagnostic tasks required for a diagnostic procedure on a target vehicle. For example, basic diagnostics may include, but are not limited to, fault diagnosis of the target vehicle's temperature sensor; fault diagnosis of the target vehicle's voltage sensor; and fault diagnosis of the target vehicle's engine speed. Script diagnostics refers to diagnostic tasks that, after completing basic diagnostics, further check a specific ECU in the target vehicle. For example, a script diagnostic may include: "The engine water temperature in the target vehicle is too high, and further inspection of the parameters of the cooling device or temperature control device is required." In one example, different fields may be used to represent different diagnostic task types. For example, 00 represents a basic diagnostic, while 01 represents a script diagnostic.

[0043] The diagnostic script information refers to the relevant attribute information of the diagnostic script file. For example, the diagnostic script information includes but is not limited to: the size of the diagnostic script file, the download path of the diagnostic script file, and the checksum of the diagnostic script file.

[0044] In an embodiment, the diagnosis management platform in the remote diagnosis server sends a vehicle diagnosis push message containing a diagnosis task to the diagnosis client in the remote diagnosis client, and the vehicle diagnosis push message includes at least the diagnosis task type and / or diagnosis script information.

[0045] S220 : Acquire a corresponding target diagnosis script file and a corresponding target diagnosis condition according to the diagnosis task type and / or the diagnosis script information.

[0046] The target diagnostic script file is obtained by converting the diagnostic database and the diagnostic sequence, and is an interpretive language file. The diagnostic database can be in a format such as ODX / Excel; the diagnostic sequence can be in an OTX or custom format.

[0047] In one embodiment, the data structure of the diagnostic script file can be configured according to the characteristics of the specific interpreted language used. Figure 3 is a configuration diagram of the data structure of a diagnostic script file provided by an embodiment of the present application. As shown in Figure 3, the diagnostic script file includes: diagnostic communication information and diagnostic data information; wherein, the diagnostic communication information at least includes: access information of the electronic control unit ECU to be diagnosed; the diagnostic data information at least includes: instruction execution order, diagnostic data and operation result processing. The access information of the ECU to be diagnosed can be understood as the connection information of the ECU to be diagnosed, for example, the access information can be a logical address, etc. The diagnostic data information is a diagnostic step set, and the diagnostic step set is a collection of the entire diagnostic steps, and a diagnostic step includes three parts: execution order, diagnostic data and operation result processing. Among them, the operation result is used to describe the analysis and processing logic of the diagnostic script, for example, it can include: data parsing format, subsequent instruction execution order, number of abnormal retries, time interval and prompt information. Among them, the data parsing format refers to the format for extracting the returned data, for example, which data in the extracted data needs to be returned to the remote diagnosis server; the subsequent instruction execution order refers to the next step number based on the returned data; the number of exception retries refers to the number of retries when an exception occurs in this instruction; the time interval refers to the time interval between this instruction and the next instruction; the prompt information refers to the prompt information that needs to be given to the user if an exception occurs in this instruction, etc.

[0048] The diagnostic database includes diagnostic communication information and diagnostic data in the diagnostic data information; the instruction execution sequence and operation results in the diagnostic data information are both diagnostic sequences.

[0049] In this embodiment, the target diagnostic script file refers to the diagnostic script that matches the current diagnostic task; the target diagnostic condition refers to the operating state that the target vehicle must maintain when executing the target diagnostic script file. It can be understood that there is a one-to-one correspondence between diagnostic script files and diagnostic conditions, i.e., one target diagnostic script file corresponds to one target diagnostic condition. The corresponding target diagnostic script file and target diagnostic condition can be obtained from different databases based on the diagnostic task type and / or diagnostic script information.

[0050] S230: Perform fault diagnosis on the target vehicle according to the target diagnosis conditions and the target diagnosis script file.

[0051] In an embodiment, when the current operating state of the target vehicle meets the target diagnosis condition, fault diagnosis is performed on one or more ECUs in the target vehicle based on the target diagnosis script file.

[0052] The technical solution of this embodiment converts the diagnostic database and diagnostic sequence into an interpreted language-based diagnostic script file that is more suitable for operation by the remote diagnostic client through the remote diagnostic server, and sends it to the remote diagnostic client, eliminating the need for the remote diagnostic client to parse the diagnostic sequence and frequently read the diagnostic database, thereby reducing the load on the remote diagnostic client and improving the operating efficiency of the diagnostic task; at the same time, the diagnostic task type is partitioned to facilitate obtaining the corresponding target diagnostic script file from different databases according to the diagnostic task type, thereby improving the diagnostic efficiency.

[0053] In one embodiment, FIG4 is a flow chart of another fault diagnosis method provided by an embodiment of the present application. This embodiment, based on the above embodiment, illustrates the fault diagnosis process when the diagnostic task type is basic diagnosis. As shown in FIG4, the method includes:

[0054] S410: Receive a vehicle diagnosis push message sent by a remote diagnosis server.

[0055] The vehicle diagnosis push message includes at least one of the following: diagnosis task type and diagnosis script information.

[0056] S420: When the diagnostic task type is basic diagnosis, directly obtain a pre-stored diagnostic script file and corresponding diagnostic conditions from a local database of the remote diagnostic client.

[0057] Wherein, when the diagnostic task type is basic diagnosis, the diagnostic client in the remote diagnostic client can directly obtain the pre-stored diagnostic script file and the corresponding diagnostic conditions from the local database.

[0058] S430: Use the pre-stored diagnosis script file and the corresponding diagnosis condition as the corresponding target diagnosis script file and the corresponding target diagnosis condition respectively.

[0059] The diagnostic client in the remote diagnostic client uses the pre-stored diagnostic script file as the corresponding target diagnostic script file, and the diagnostic condition corresponding to the target diagnostic script file as the target diagnostic condition.

[0060] S440. Call the corresponding target diagnosis protocol stack according to the diagnosis script logic corresponding to the target diagnosis script file.

[0061] The target diagnostic protocol stack refers to a diagnostic protocol stack that can satisfy the remote diagnostic client to execute the target diagnostic script file. Exemplarily, the target diagnostic protocol stack may include but is not limited to: UDS or DoIP protocol stack.

[0062] S450: When the current operating state of the target vehicle meets the target diagnosis condition, a target diagnosis protocol stack is used and a fault diagnosis is performed on the target vehicle based on the target diagnosis script file.

[0063] When the current running state of the target vehicle meets the target diagnosis conditions, the diagnostic script engine in the remote diagnostic client calls the target diagnostic protocol stack to execute the target diagnostic script file to perform fault diagnosis on the target vehicle.

[0064] The technical solution in this embodiment improves diagnostic efficiency by pre-storing the target diagnostic script files and target diagnostic conditions corresponding to the more frequently used basic diagnoses in the remote diagnostic client, thereby avoiding frequent acquisition of the target diagnostic script files from the remote diagnostic server.

[0065] In one embodiment, FIG5 is a flowchart of another fault diagnosis method provided by an embodiment of the present application. This embodiment, based on the above embodiment, illustrates the fault diagnosis process when the diagnostic task type is basic diagnosis. As shown in FIG5, the method includes:

[0066] S510: Receive a vehicle diagnosis push message sent by a remote diagnosis server.

[0067] The vehicle diagnosis push message includes at least one of the following: diagnostic task type and diagnostic script information;

[0068] S520: When the diagnostic task type is basic diagnosis, determine, according to the diagnostic script information, the status of the diagnostic script files pre-stored in the local database of the remote diagnostic client that need to be updated.

[0069] The pending update status is used to indicate the matching status between the diagnostic script file pre-stored in the local database and the diagnostic script information. If the diagnostic script file pre-stored in the local database matches the diagnostic script, there is no need to update the diagnostic script file pre-stored in the local database. If the diagnostic script file pre-stored in the local database does not match the diagnostic script, the diagnostic script file pre-stored in the local database needs to be updated.

[0070] S530: If the status to be updated is that an update is required, the vehicle attribute information of the target vehicle is reported to the remote diagnosis server.

[0071] Vehicle attribute information refers to the attribute information of the target vehicle. For example, this information may include, but is not limited to, the vehicle ID and the vehicle ECU ID. If the diagnostic script file pre-stored in the local database does not match the diagnostic script, the pre-stored diagnostic script file in the local database needs to be updated. In this case, the target vehicle's attribute information needs to be reported to the remote diagnostic server via the remote diagnostic client.

[0072] S540: Receive the latest diagnostic script file and the corresponding latest diagnostic conditions that match the vehicle attribute information and are sent by the remote diagnostic server, and use the latest diagnostic script file and the corresponding latest diagnostic conditions as the target diagnostic script file and the corresponding target diagnostic conditions.

[0073] After the remote diagnosis server receives the vehicle attribute information of the target vehicle reported by the remote diagnosis client, the remote diagnosis server determines whether there is a corresponding diagnosis script file that can be sent based on the vehicle attribute information; if so, the remote diagnosis server sends the latest diagnosis script file and the corresponding latest diagnosis conditions that match the vehicle attribute information to the remote diagnosis client, and uses the latest diagnosis script file as the corresponding target diagnosis script file, and uses the latest diagnosis conditions corresponding to the latest diagnosis script file as the corresponding target diagnosis conditions.

[0074] S550 : When the update status is that no update is required, directly obtain a pre-stored diagnosis script file and corresponding diagnosis conditions from a local database of the remote diagnosis client.

[0075] If the diagnostic script file pre-stored in the local database matches the diagnostic script, there is no need to update the diagnostic script file pre-stored in the local database. The pre-stored diagnostic script file and the corresponding diagnostic conditions can be directly obtained from the local database of the remote diagnostic client.

[0076] S560: Use the pre-stored diagnosis script file and the corresponding diagnosis condition as the corresponding target diagnosis script file and the corresponding target diagnosis condition respectively.

[0077] The diagnostic client in the remote diagnostic client uses the pre-stored diagnostic script file as the corresponding target diagnostic script file, and the diagnostic condition corresponding to the target diagnostic script file as the target diagnostic condition.

[0078] S570: Call the corresponding target diagnosis protocol stack according to the diagnosis script logic corresponding to the target diagnosis script file.

[0079] S580: When the current operating state of the target vehicle meets the target diagnosis conditions, a target diagnosis protocol stack is used and a fault diagnosis is performed on the target vehicle based on the target diagnosis script file.

[0080] It should be noted that, for the explanation of S570-S580, reference can be made to the corresponding description of S440-S450 in the above embodiment, which will not be repeated here.

[0081] The technical solution of this embodiment is to obtain the corresponding diagnostic script file and diagnostic conditions from the remote diagnosis server only when the diagnostic script file pre-stored in the local database of the remote diagnosis client needs to be updated; otherwise, the pre-stored diagnostic script file and corresponding diagnostic conditions are directly obtained from the local database of the remote diagnosis client, avoiding frequent acquisition of the target diagnostic script file from the remote diagnosis server, thereby improving the diagnosis efficiency.

[0082] In one embodiment, FIG6 is a flowchart of another fault diagnosis method provided by an embodiment of the present application. This embodiment, based on the above embodiment, illustrates the fault diagnosis process when the diagnostic task type is script diagnosis. As shown in FIG6, the method includes:

[0083] S610: Receive a vehicle diagnosis push message sent by a remote diagnosis server.

[0084] The vehicle diagnosis push message includes at least one of the following: diagnosis task type and diagnosis script information.

[0085] S620: When the diagnostic task type is script diagnosis, the vehicle attribute information of the target vehicle is reported to the remote diagnostic server.

[0086] S630: Receive the latest diagnostic script file and the corresponding latest diagnostic conditions that match the vehicle attribute information and are sent by the remote diagnostic server, and use the latest diagnostic script file and the corresponding latest diagnostic conditions as the target diagnostic script file and the corresponding target diagnostic conditions.

[0087] S640: Call the corresponding target diagnosis protocol stack according to the diagnosis script logic corresponding to the target diagnosis script file.

[0088] S650: When the current operating state of the target vehicle meets the target diagnosis conditions, a target diagnosis protocol stack is used and a fault diagnosis is performed on the target vehicle based on the target diagnosis script file.

[0089] It should be noted that when the diagnostic task type is script diagnosis, the remote diagnostic client is required to report the vehicle attribute information of the target vehicle to the remote diagnostic server, and receive the latest diagnostic script file and the corresponding latest diagnostic conditions issued by the remote diagnostic server that match the vehicle attribute information, and perform fault diagnosis according to the latest diagnostic script file and the corresponding latest diagnostic conditions.

[0090] It should be noted that the process of reporting the vehicle attribute information of the target vehicle to the remote diagnosis server in S620, and the process of receiving the latest diagnostic script file and the corresponding latest diagnostic conditions in S630, can be found in the description of the above embodiments S530-S540, and the explanation of S640-S650 can be found in the description of the above embodiments, which will not be repeated here.

[0091] In one embodiment, after the target vehicle is diagnosed for faults according to the target diagnostic conditions and the target diagnostic script file, the process further includes: obtaining the running results corresponding to each diagnostic instruction in the target diagnostic script file; parsing the running results based on the data parsing format that matches the diagnostic instruction in the target diagnostic script file to obtain the corresponding diagnostic results; and reporting the diagnostic results and the running results to the remote diagnostic server. The data parsing format refers to the format for parsing the running results. For example, a certain data in the running results is parsed into a corresponding meaning according to the data parsing format. It can be understood that the diagnostic instructions and the data parsing format are one-to-one corresponding. In an embodiment, the remote diagnostic client obtains the running results of each diagnostic instruction in the target diagnostic script file, and parses the running results based on the corresponding data parsing format to obtain the corresponding diagnostic results; then caches the running results and the corresponding diagnostic results; after waiting for all diagnostic instructions in the entire target diagnostic script file to complete execution, the running results and the corresponding diagnostic results corresponding to all diagnostic instructions in the target diagnostic script file are reported to the remote diagnostic server.

[0092] In one embodiment, FIG7 is a flow chart of another fault diagnosis method provided by an embodiment of the present application. This embodiment is used as an example to illustrate the fault diagnosis process of a vehicle. As shown in FIG7 , the fault diagnosis method in this embodiment includes the following steps:

[0093] S710. The diagnosis management platform sends a vehicle diagnosis push message through the push server.

[0094] S720: Is it a basic diagnosis? If so, execute S730; if not, execute S750.

[0095] S730: Whether the pre-stored diagnostic script file needs to be updated, if so, execute S750; if not, execute S740.

[0096] S740: Obtain pre-stored diagnosis script files and diagnosis conditions.

[0097] S750: The remote diagnosis client reports the vehicle attribute information to the remote diagnosis server.

[0098] S760. The remote diagnosis server determines whether a corresponding diagnosis script file exists based on the vehicle attribute information. If so, execute S770; if not, end.

[0099] S770: The diagnosis management platform sends the latest diagnosis script file and the corresponding latest diagnosis conditions.

[0100] S780: Does the current operating state of the target vehicle meet the latest diagnostic conditions? If so, execute S7100; if not, execute S790.

[0101] S790: Monitor changes in the current operating state of the target vehicle.

[0102] S7100: Execute the diagnostic script file through the diagnostic script engine.

[0103] S7110. Report the diagnosis results and operation results to the remote diagnosis server.

[0104] In one embodiment, FIG8 is a flow chart of another fault diagnosis method provided by an embodiment of the present application. This embodiment is used as an example to illustrate the fault diagnosis process of a vehicle. As shown in FIG8 , the fault diagnosis method in this embodiment includes the following steps:

[0105] S810. The diagnosis management platform sends a vehicle diagnosis push message through the push server.

[0106] S820: Is it a basic diagnosis? If so, execute S830; if not, execute S840.

[0107] S830: Obtain pre-stored diagnosis script files and diagnosis conditions.

[0108] S840: The remote diagnosis client reports the vehicle attribute information to the remote diagnosis server.

[0109] S850. The remote diagnosis server determines whether a corresponding diagnosis script file exists based on the vehicle attribute information. If so, execute S860; if not, end.

[0110] S860: The diagnosis management platform sends the latest diagnosis script file and the corresponding latest diagnosis conditions.

[0111] S870: Does the current operating state of the target vehicle meet the latest diagnostic conditions? If so, execute S890; if not, execute S880.

[0112] S880: Monitor changes in the current operating state of the target vehicle.

[0113] S890. Execute the diagnostic script file through the diagnostic script engine.

[0114] S8100 reports the diagnosis and operation results to the remote diagnosis server.

[0115] It should be noted that the fault diagnosis process shown in FIG8 differs from the fault diagnosis process shown in FIG7 in that for basic diagnosis, there is no need to check whether the pre-stored diagnostic script in the local database needs to be updated. If the basic diagnostic script needs to be updated, the script diagnosis process is used.

[0116] In one embodiment, FIG9 is a block diagram of another fault diagnosis system provided by an embodiment of the present application. As shown in FIG9 , the fault diagnosis system in this embodiment includes the following structure:

[0117] The diagnostic management platform 101 (cloud) mainly combines the diagnostic database (ODX / Excel, etc. format) and the corresponding diagnostic sequence (OTX or custom format) into a diagnostic script file, and sends it to the diagnostic client 201 on the vehicle side located at the main node (usually TBox, which can be adjusted according to the specific circumstances of the actual project). The diagnostic client 201 sends the diagnostic script to the diagnostic script engine 202, which is responsible for parsing the diagnostic script and diagnosing the relevant ECU based on the content of the diagnostic script. The diagnostic script is written in an interpreted language (Lua / JS, etc.). The corresponding virtual machine is integrated into the diagnostic script engine 202 to ensure that the code in the interpreted language can be executed and interact with the lower-level diagnostic protocol stack (UDS / DoIP) 203. Different diagnostic functions can be achieved through different diagnostic script logic without changing the vehicle-side diagnostic application code.

[0118] In one embodiment, FIG10 is a schematic diagram of a fault diagnosis device provided in an embodiment of the present application. As shown in FIG10 , the device includes: a receiving module 1010 , a first obtaining module 1020 , and a diagnosis module 1030 .

[0119] The receiving module 1010 is configured to receive a vehicle diagnosis push message sent by a remote diagnosis server; wherein the vehicle diagnosis push message includes at least one of the following: a diagnosis task type and a diagnosis script information;

[0120] A first acquisition module 1020 is configured to acquire a corresponding target diagnostic script file and a corresponding target diagnostic condition according to the diagnostic task type and / or diagnostic script information; wherein the target diagnostic script file is obtained by converting the diagnostic database and the diagnostic sequence, and the target diagnostic script file is an interpretive language file;

[0121] The diagnosis module 1030 is used to perform fault diagnosis on the target vehicle according to the target diagnosis conditions and the target diagnosis script file.

[0122] In one embodiment, the acquisition module includes:

[0123] A first obtaining unit is configured to obtain a pre-stored diagnostic script file and corresponding diagnostic conditions directly from a local database of the remote diagnostic client when the diagnostic task type is basic diagnosis;

[0124] The second acquiring unit is configured to use the pre-stored diagnostic script file and the corresponding diagnostic condition as the corresponding target diagnostic script file and the corresponding target diagnostic condition respectively.

[0125] In one embodiment, the acquisition module includes:

[0126] A first determining unit is configured to determine, when the diagnostic task type is basic diagnosis, a pending update status of a diagnostic script file pre-stored in a local database of the remote diagnostic client according to the diagnostic script information;

[0127] a first reporting unit, configured to report the vehicle attribute information of the target vehicle to the remote diagnosis server when the to-be-updated condition indicates that the vehicle attribute information needs to be updated;

[0128] The first receiving unit is used to receive the latest diagnostic script file and the corresponding latest diagnostic conditions that match the vehicle attribute information issued by the remote diagnostic server, and use the latest diagnostic script file and the corresponding latest diagnostic conditions as the target diagnostic script file and the corresponding target diagnostic conditions.

[0129] In one embodiment, the acquisition module includes:

[0130] The second reporting unit is used to report the vehicle attribute information of the target vehicle to the remote diagnosis server when the diagnosis task type is script diagnosis;

[0131] The second receiving unit is used to receive the latest diagnostic script file and the corresponding latest diagnostic conditions that match the vehicle attribute information issued by the remote diagnostic server, and use the latest diagnostic script file and the corresponding latest diagnostic conditions as the target diagnostic script file and the corresponding target diagnostic conditions.

[0132] In one embodiment, the diagnostic module includes:

[0133] A calling unit, configured to call a corresponding target diagnostic protocol stack according to the diagnostic script logic corresponding to the target diagnostic script file;

[0134] The diagnostic unit is used to use the target diagnosis protocol stack and perform fault diagnosis on the target vehicle based on the target diagnosis script file when the current operating state of the target vehicle meets the target diagnosis conditions.

[0135] In one embodiment, after performing fault diagnosis on the target vehicle according to the target diagnosis condition and the target diagnosis script file, the fault diagnosis device further includes:

[0136] The second acquisition module is used to obtain the running result corresponding to each diagnostic instruction in the target diagnostic script file;

[0137] A parsing module is used to parse the running results based on the data parsing format that matches the diagnostic instructions in the target diagnostic script file to obtain the corresponding diagnostic results;

[0138] The reporting module is used to report the diagnosis results and operation results to the remote diagnosis server.

[0139] In one embodiment, when the diagnosis script information is empty, the diagnosis task type is determined to be basic diagnosis;

[0140] When the diagnosis script information is not empty, the diagnosis task type is determined to be script diagnosis.

[0141] In one embodiment, the vehicle diagnostic script file includes: diagnostic communication information and diagnostic data information;

[0142] The diagnostic communication information includes at least: access information of the electronic control unit ECU to be diagnosed;

[0143] The diagnostic data information includes at least: instruction execution sequence, diagnostic data and operation result processing.

[0144] The fault diagnosis device provided in the embodiments of the present application can execute the fault diagnosis method provided in any embodiment of the present application, and has the corresponding functional modules and beneficial effects of the execution method.

[0145] In one embodiment, Figure 11 is a structural block diagram of a fault diagnosis device provided by an embodiment of the present application. As shown in Figure 11, a structural schematic diagram of a fault diagnosis device 10 that can be used to implement an embodiment of the present application is shown. The fault diagnosis device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The fault diagnosis device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present application described and / or required herein.

[0146] As shown in FIG11 , the fault diagnosis device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc., which is communicatively connected to the at least one processor 11. The memory stores a computer program that can be executed by the at least one processor, and the processor 11 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 12 or the computer program loaded from the storage unit 18 into the random access memory (RAM) 13. Various programs and data required for the operation of the fault diagnosis device 10 can also be stored in the RAM 13. The processor 11, ROM 12, and RAM 13 are connected to each other via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0147] Multiple components in the fault diagnosis device 10 are connected to the I / O interface 15, including an input unit 16, such as a keyboard and mouse; an output unit 17, such as various types of displays and speakers; a storage unit 18, such as a magnetic disk and optical disk; and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the fault diagnosis device 10 to exchange information / data with other devices via a computer network such as the Internet and / or various telecommunication networks.

[0148] The processor 11 may be any general-purpose and / or specialized processing component with processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various specialized artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 11 executes the various methods and processes described above, such as the fault diagnosis method.

[0149] In some embodiments, the fault diagnosis method can be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as the storage unit 18. In some embodiments, part or all of the computer program can be loaded and / or installed on the fault diagnosis device 10 via the ROM 12 and / or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the fault diagnosis method described above can be performed. Alternatively, in other embodiments, the processor 11 can be configured to perform the fault diagnosis method in any other appropriate manner (for example, by means of firmware).

[0150] Various embodiments of the systems and techniques described herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), system-on-chip systems (SOCs), programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments can include being implemented in one or more computer programs that are executable and / or interpreted on a programmable system that includes at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0151] Computer programs for implementing the methods of the present application may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when the computer program is executed by the processor, the functions / operations specified in the flowcharts and / or block diagrams are implemented. The computer program may be executed entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0152] In the context of the present application, a computer-readable storage medium can be a tangible medium that can contain or store a computer program for use by an instruction execution system, device or equipment or used in combination with an instruction execution system, device or equipment. A computer-readable storage medium can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium can be a machine-readable signal medium. A more specific example of a machine-readable storage medium can include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or 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 foregoing.

[0153] To provide interaction with a user, the systems and techniques described herein can be implemented on a fault diagnosis device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball), through which the user can provide input to the fault diagnosis device. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0154] The systems and techniques described herein can be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0155] A computing system may include clients and servers. The clients and servers are typically remote from each other and typically interact via a communication network. This client-server relationship arises through computer programs running on the respective computers, creating a client-server relationship. The server may be a cloud server, also known as a cloud computing server or cloud host. This server is a hosting product within the cloud computing service ecosystem that addresses the management difficulties and limited scalability of traditional physical hosting and VPS services.

[0156] It should be understood that the various forms of the processes shown above can be used to reorder, add, or delete steps. For example, the steps described in this application can be performed in parallel, sequentially, or in a different order, as long as the desired results of the technical solution of this application can be achieved. This is not limited herein.

Claims

1. A fault diagnosis method, applied to a remote diagnosis client, comprising: Receiving a vehicle diagnosis push message sent by a remote diagnosis server; wherein the vehicle diagnosis push message includes at least one of the following: a diagnosis task type and a diagnosis script information; Acquire a corresponding target diagnostic script file and a corresponding target diagnostic condition according to the diagnostic task type and / or the diagnostic script information; wherein the target diagnostic script file is obtained by converting a diagnostic database and a diagnostic sequence, and the target diagnostic script file is an interpreted language file; Fault diagnosis is performed on the target vehicle according to the target diagnosis condition and the target diagnosis script file.

2. The method according to claim 1, wherein: The obtaining of a corresponding target diagnosis script file and a corresponding target diagnosis condition according to the diagnosis task type includes: In the case where the diagnostic task type is basic diagnosis, directly obtaining a pre-stored diagnostic script file and corresponding diagnostic conditions from a local database of the remote diagnostic client; The pre-stored diagnosis script file and the corresponding diagnosis condition are used as the corresponding target diagnosis script file and the corresponding target diagnosis condition respectively.

3. The method according to claim 1, wherein: The obtaining a corresponding target diagnosis script file and a corresponding target diagnosis condition according to the diagnosis task type and the diagnosis script information includes: In the case where the diagnostic task type is basic diagnosis, determining, according to the diagnostic script information, a pending update status of a diagnostic script file pre-stored in a local database of the remote diagnostic client; When the to-be-updated condition is that an update is required, reporting the vehicle attribute information of the target vehicle to the remote diagnosis service end; Receive the latest diagnostic script file and the corresponding latest diagnostic conditions that match the vehicle attribute information and are sent by the remote diagnostic service end, and use the latest diagnostic script file and the corresponding latest diagnostic conditions as the target diagnostic script file and the corresponding target diagnostic conditions.

4. The method according to claim 1, wherein: The obtaining a corresponding target diagnosis script file and a corresponding target diagnosis condition according to the diagnosis task type and the diagnosis script information includes: When the diagnostic task type is script diagnosis, reporting the vehicle attribute information of the target vehicle to the remote diagnostic service end; Receive the latest diagnostic script file and the corresponding latest diagnostic conditions that match the vehicle attribute information and are sent by the remote diagnostic service end, and use the latest diagnostic script file and the corresponding latest diagnostic conditions as the target diagnostic script file and the corresponding target diagnostic conditions.

5. The method according to claim 1, wherein: The performing fault diagnosis on the target vehicle according to the target diagnosis condition and the target diagnosis script file includes: Calling the corresponding target diagnosis protocol stack according to the diagnosis script logic corresponding to the target diagnosis script file; In the case that the current running state of the target vehicle meets the target diagnosis condition, the target diagnosis protocol stack is adopted, and fault diagnosis is performed on the target vehicle based on the target diagnosis script file.

6. The method according to any one of claims 1 to 5, after performing fault diagnosis on the target vehicle according to the target diagnosis condition and the target diagnosis script file, further comprising: Obtaining the running result corresponding to each diagnostic instruction in the target diagnostic script file; Parsing the operation result based on the data parsing format matching the diagnostic instruction in the target diagnostic script file to obtain a corresponding diagnostic result; The diagnostic result and the operation result are reported to the remote diagnostic service end.

7. The method according to any one of claims 1 to 5, wherein: In the case where the diagnosis script information is empty, determining the diagnosis task type as a basic diagnosis; When the diagnosis script information is not empty, it is determined that the diagnosis task type is script diagnosis.

8. The method according to any one of claims 1 to 5, wherein: The diagnostic script file includes: diagnostic communication information and diagnostic data information; Wherein, the diagnostic communication information at least includes: access information of the electronic control unit ECU to be diagnosed; The diagnostic data information includes at least: instruction execution sequence, diagnostic data and operation result processing.

9. A fault diagnosis system comprising: A remote diagnosis server and a remote diagnosis client; wherein the remote diagnosis server includes: a diagnosis management platform, a push server and a content distribution network; the remote diagnosis client includes: a diagnosis client and a diagnosis script engine; The diagnostic database and the corresponding diagnostic sequence are synthesized into a corresponding diagnostic script file through the diagnostic management platform; when the diagnostic client receives a vehicle diagnostic push message carrying the diagnostic task type and / or diagnostic script information sent by the push server, the diagnostic client receives the corresponding target diagnostic script file and the corresponding target diagnostic condition issued by the content distribution network based on the diagnostic task type and / or the diagnostic script information, and sends the target diagnostic script file to the diagnostic script engine, so that the diagnostic script engine parses the target diagnostic script file, and performs fault diagnosis on the target vehicle according to the target diagnostic condition and the target diagnostic script file; wherein the target diagnostic script file is obtained by converting the diagnostic database and the corresponding diagnostic sequence through the diagnostic management platform, and the target diagnostic script file is an interpreted language file.

10. A fault diagnosis device comprising: at least one processor; as well as a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the fault diagnosis method according to any one of claims 1 to 8.

11. A computer-readable storage medium storing computer instructions, wherein the computer instructions are used to enable a processor to implement the fault diagnosis method according to any one of claims 1 to 8 when executed.

Images