Fault diagnosis method, system, equipment and medium

Abstract

The present invention discloses a fault diagnosis method, system, device and medium. The method comprises: receiving a vehicle diagnosis push message sent by a remote diagnosis server; wherein the vehicle diagnosis push message comprises at least one of the following: a diagnosis task type and a diagnosis script information; obtaining a corresponding target diagnosis script file and a corresponding target diagnosis condition according to the diagnosis task type and / or the diagnosis script information; 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 interpretive language file; and performing fault diagnosis on a target vehicle according to the target diagnosis condition and the target diagnosis script file. The present invention eliminates the need for the remote diagnosis client to parse the diagnosis sequence and frequently read the diagnosis database, thereby reducing the load on the remote diagnosis client and improving the operating efficiency of the diagnosis task; at the same time, the diagnosis task type is partitioned to improve the diagnosis efficiency.

Description

Technical Field

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

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

[0003] Remote vehicle diagnosis refers to a diagnostic technology that relies on the vehicle's mobile communication capabilities (WIFI / 4G / 5G) to complete remote control and diagnostic operations on the vehicle from the OEM backend (or mobile phone APP) without the need to drive the vehicle back to the physical store. Remote OTA refresh is a scenario for remote diagnostic applications. In addition, by integrating remote diagnostic technology with cutting-edge technologies such as the Internet of Things, big data, and cloud computing, it can also provide important support for OEMs in areas such as R&D testing, production line electrical inspection, and after-sales diagnosis.

[0004] First, remote diagnosis can collect data online, reducing the development cycle and cost. During the R&D stage, vehicles need to undergo a large number of road tests and durability tests, but the test vehicles are equipped with limited data collection equipment. Through remote diagnosis, vehicle failure phenomena that occur during the test can be promptly fed back to R&D personnel for analysis and simulation, and quickly assist in solving the failure problem. Secondly, remote diagnosis can realize initialization and functional testing across workstations in the production line electrical inspection and OTA refresh of the production line, realize customized production of automotive software, and meet the customized needs of car owners. Finally, remote diagnosis can periodically monitor the vehicle status, diagnose vehicle health in real time, and combine big data statistical analysis to provide vehicle fault warnings, and push them to the manufacturer's after-sales vehicle store through the background for vehicle maintenance and repair guidance and suggestions.

[0005] However, the diagnostic database is preset 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 according to the diagnostic sequence to synthesize diagnostic instructions for diagnosis. Since data needs to be frequently obtained from the diagnostic database according to the diagnostic sequence, the resource overhead of the vehicle-side main node will be relatively large and the operating efficiency will be low. In addition, all diagnostic tasks require the diagnostic sequence file to be sent from the cloud, and the vehicle side then obtains the data from the diagnostic database according to the diagnostic sequence to synthesize diagnostic instructions for diagnosis, resulting in low diagnostic efficiency. Summary of the invention

[0006] The present invention provides a fault diagnosis method, system, device and medium to solve the technical problems of large resource consumption, low operation efficiency and low diagnosis efficiency in the prior art.

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

[0008] 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;

[0009] 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;

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

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

[0012] 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;

[0013] an acquisition module, used for acquiring a corresponding target diagnosis script file and a corresponding target diagnosis condition according to the diagnosis task type and / or the diagnosis script information; 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;

[0014] 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.

[0015] According to another aspect of the present invention, 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;

[0016] 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.

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

[0018] at least one processor; and

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

[0020] 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 invention.

[0021] According to another aspect of the present invention, 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 invention when executed.

[0022] The technical solution of the embodiment of the present invention converts the diagnostic database and diagnostic sequence into an interpreted language-based diagnostic script file that is more suitable for running on 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 running efficiency of the diagnostic task; at the same time, the diagnostic task type is partitioned to facilitate obtaining the corresponding target diagnostic script files from different databases according to the diagnostic task type, thereby improving the diagnostic efficiency.

[0023] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0025] Figure 1 is a structural block diagram of a fault diagnosis system provided by an embodiment of the present invention;

[0026] Figure 2 is a flow chart of a fault diagnosis method provided by an embodiment of the present invention;

[0027] Figure 3 It is a configuration diagram of a data structure of a diagnostic script file provided by an embodiment of the present invention;

[0028] Figure 4 is a flow chart of another fault diagnosis method provided by an embodiment of the present invention;

[0029] Figure 5 is a flow chart of another fault diagnosis method provided by an embodiment of the present invention;

[0030] Figure 6 is a flow chart of another fault diagnosis method provided by an embodiment of the present invention;

[0031] Figure 7 is a flow chart of another fault diagnosis method provided by an embodiment of the present invention;

[0032] Figure 8 is a flow chart of another fault diagnosis method provided by an embodiment of the present invention;

[0033] Fig. 9 is a structural block diagram of another fault diagnosis system provided by an embodiment of the present invention;

[0034] Fig.10 is a structural schematic diagram of a fault diagnosis device provided by an embodiment of the present invention;

[0035] Fig.11 It is a structural block diagram of a fault diagnosis device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0036] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0037] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are 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, Figure 1 is a structural block diagram of a fault diagnosis system provided by an embodiment of the present invention. The fault diagnosis method provided by an embodiment of the present invention is executed by a remote diagnosis client in the fault diagnosis system. Figure 1 As shown, 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 the 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, Figure 2 is a flow chart of a fault diagnosis method provided by an embodiment of the present invention. This embodiment is applicable to the case of simply and conveniently diagnosing a vehicle fault. The method can be executed by a fault diagnosis device. The fault diagnosis device can be implemented in the form of hardware and / or software. The fault diagnosis device can be configured in a fault diagnosis device. The fault diagnosis device can be a remote diagnosis client. Figure 2 As shown, the method includes:

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

[0042] Among them, the vehicle diagnosis push message includes at least one of the following: diagnostic task type and diagnostic script information. The remote diagnosis service end may also be called a remote diagnosis server, or a remote diagnosis cloud (referred to as the cloud). The vehicle diagnosis push message refers to the relevant information of the diagnostic task pushed to the remote diagnosis client, and the vehicle diagnosis push message may include: diagnostic task type and / or diagnostic script information. Among them, the diagnostic task type is used to characterize different types of diagnostic tasks, and the diagnostic task type may include basic diagnosis and script diagnosis. Basic diagnosis refers to the diagnostic task required for the target vehicle in a diagnostic process. For example, basic diagnosis may include but is not limited to: fault diagnosis of the temperature sensor in the target vehicle; fault diagnosis of the voltage sensor in the target vehicle; fault diagnosis of the speed of the transmitter in the target vehicle. Script diagnosis refers to a diagnostic task for further checking a certain ECU in the target vehicle after the basic diagnosis is completed. For example, the script diagnosis may include: the water temperature of the engine in the target vehicle is too high, and it is necessary to further check whether the parameters of the heat dissipation device or the temperature control device are normal. In an example, different fields can be used to represent different diagnostic task types. For example, 00 represents basic diagnosis; 01 represents script diagnosis.

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

[0044] In an embodiment, the diagnosis management platform in the remote diagnosis server sends a vehicle diagnosis push message including 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 diagnosis script file is obtained by converting the diagnosis database and the diagnosis sequence, and the target diagnosis script file is an interpretive language file. The diagnosis database can be in ODX / Excel or other formats; the diagnosis sequence can be in OTX or a custom format.

[0047] In one embodiment, the data structure of the diagnosis script file can be configured according to the characteristics of the specifically adopted interpreted language. Figure 3 FIG. 1 is a schematic diagram of the configuration of a data structure of a diagnostic script file provided by an embodiment of the present invention. Figure 3 As shown, 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, which is a collection of the entire diagnostic steps, and a diagnostic step includes: 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 pan-club protective equipment, for example, it can include: data parsing format, subsequent instruction execution order, abnormal retry number, 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 diagnostic service end; the subsequent instruction execution order refers to the step number of the next step according to the returned data; the abnormal retry number refers to the number of retries when the current instruction is abnormal; the time interval refers to the time interval between the current instruction and the next instruction; the prompt information refers to the prompt information that needs to be given to the user if the current instruction is abnormal.

[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 the 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 needs to maintain when executing the target diagnostic script file. It can be understood that the diagnostic script file and the diagnostic condition are one-to-one corresponding, that is, one target diagnostic script file corresponds to one target diagnostic condition. The corresponding target diagnostic script file and the corresponding target diagnostic condition can be obtained from different databases according to the diagnostic task type and / or diagnostic script information.

[0050] S230: Perform fault diagnosis on the target vehicle according to the target diagnosis condition 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 running on 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 running efficiency of the diagnostic task. At the same time, the diagnostic task types are partitioned to facilitate obtaining corresponding target diagnostic script files from different databases according to the diagnostic task type, thereby improving the diagnostic efficiency.

[0053] In one embodiment, Figure 4 FIG. 1 is a flowchart of another fault diagnosis method provided by an embodiment of the present invention. This embodiment is based on the above embodiment and illustrates the fault diagnosis process when the diagnosis task type is basic diagnosis. Figure 4 As shown, 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: a diagnosis task type and a 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 diagnosis protocol stack refers to a diagnosis protocol stack that can satisfy the remote diagnosis client to execute the target diagnosis script file. Exemplarily, the target diagnosis protocol stack may include but is not limited to: UDS or DoIP protocol stack.

[0062] S450: When the current running state of the target vehicle meets the target diagnosis condition, a target diagnosis protocol stack is used to perform fault diagnosis 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 condition, the target diagnosis protocol stack is called by the diagnosis script engine in the remote diagnosis client to execute the target diagnosis 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 diagnosis client, thereby avoiding frequent acquisition of the target diagnostic script files from the remote diagnosis server.

[0065] In one embodiment, Figure 5 FIG. 1 is a flowchart of another fault diagnosis method provided by an embodiment of the present invention. This embodiment is based on the above embodiment and illustrates the fault diagnosis process when the diagnosis task type is basic diagnosis. Figure 5 As shown, 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: the diagnosis task type and the diagnosis 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 characterize 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: When 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 service end.

[0071] Among them, vehicle attribute information refers to the attribute information of the target vehicle itself. Exemplarily, vehicle attribute information may include but is not limited to: vehicle identification and vehicle ECU identification, etc. In the case where the diagnostic script file pre-stored in the local database does not match the diagnostic script, it is necessary to update the diagnostic script file pre-stored in the local database. At this time, the vehicle attribute information of the target vehicle needs to be reported to the remote diagnostic server through the remote diagnostic client.

[0072] S540, receiving 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 using 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 latest diagnosis script file and the corresponding latest diagnosis conditions that match the vehicle attribute information are sent to the remote diagnosis client, and the latest diagnosis script file is used as the corresponding target diagnosis script file, and the latest diagnosis conditions corresponding to the latest diagnosis script file are used 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] In the case where 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, and 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 running state of the target vehicle meets the target diagnosis condition, a target diagnosis protocol stack is used to perform fault diagnosis 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 the 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, Figure 6 FIG. 1 is a flowchart of another fault diagnosis method provided by an embodiment of the present invention. This embodiment is based on the above embodiment and illustrates the fault diagnosis process when the diagnostic task type is script diagnosis. Figure 6 As shown, 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: a diagnosis task type and a 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, receiving 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 using 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 running state of the target vehicle meets the target diagnosis condition, a target diagnosis protocol stack is used to perform fault diagnosis 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 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 fault diagnosed according to the target diagnostic condition and the target diagnostic script file, it also includes: obtaining the operation 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 the corresponding diagnostic result; reporting the diagnostic result and the operation result to the remote diagnostic server. Among them, the data parsing format refers to the format for parsing the operation result. For example, a certain data in the operation result is parsed into a corresponding meaning according to the data parsing format. It can be understood that the diagnostic instruction and the data parsing format are one-to-one corresponding. In an embodiment, the remote diagnostic client obtains the operation result of each diagnostic instruction in the target diagnostic script file, and parses the operation result based on the corresponding data parsing format to obtain the corresponding diagnostic result; then caches the operation result and the corresponding diagnostic result; after waiting for all diagnostic instructions in the entire target diagnostic script file to complete the operation, the operation results corresponding to all diagnostic instructions in the target diagnostic script file and the corresponding diagnostic results are reported to the remote diagnostic server.

[0092] In one embodiment, Figure 7 FIG. 1 is a flow chart of another fault diagnosis method provided by an embodiment of the present invention. This embodiment is a preferred embodiment and describes the fault diagnosis process of a vehicle. Figure 7 As shown, 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 there is a corresponding diagnosis script file 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 result and operation result to the remote diagnosis server.

[0104] In one embodiment, Figure 8 FIG. 1 is a flow chart of another fault diagnosis method provided by an embodiment of the present invention. This embodiment is a preferred embodiment and describes the fault diagnosis process of a vehicle. Figure 8 As shown, the fault diagnosis method in this embodiment includes the following steps:

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

[0106] S820: Is it a basic diagnosis? If yes, execute S830; if no, 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 there is a corresponding diagnosis script file 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 diagnosis script file through the diagnosis script engine.

[0114] S8100, report the diagnosis result and operation result to the remote diagnosis server.

[0115] It should be noted that if Figure 8 The troubleshooting process shown is similar to Figure 7 The difference between the fault diagnosis process shown is that for basic diagnosis, there is no need to check whether the diagnosis script pre-stored in the local database needs to be updated. For the case where the basic diagnosis script needs to be updated, the script diagnosis process is followed.

[0116] In one embodiment, Fig. 9 FIG. 1 is a structural block diagram of another fault diagnosis system provided by an embodiment of the present invention. Fig. 9 As shown, 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 and other formats) and the corresponding diagnostic sequence (OTX or custom format) into a diagnostic script file, and sends it to the diagnostic client 201 located at the main node (usually TBox, which can be adjusted according to the specific situation of the actual project) on the vehicle side. 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 according to the content of the diagnostic script. The diagnostic script is written in an interpreted language (Lua / JS, etc.), and the corresponding virtual machine is integrated in the diagnostic script engine 202 to ensure that the code of 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 logics without changing the diagnostic application code on the vehicle side.

[0118] In one embodiment, Fig.10 FIG. 1 is a schematic diagram of the structure of a fault diagnosis device provided by an embodiment of the present invention. Fig.10 As shown, the device includes: a receiving module 1010 , a first obtaining module 1020 and a diagnosis module 1030 .

[0119] The receiving module 1010 is used 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, configured to 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; wherein the target diagnosis script file is obtained by converting the diagnosis database and the diagnosis sequence, and the target diagnosis 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 acquisition unit is used to directly acquire a pre-stored diagnosis script file and corresponding diagnosis conditions from a local database of a remote diagnosis client when the diagnosis task type is basic diagnosis;

[0124] The second acquisition unit is used to 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.

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

[0126] A first determining unit is used to determine, when the diagnostic task type is basic diagnosis, the status of the diagnostic script file to be updated pre-stored in the 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 service end when the to-be-updated condition is that the vehicle attribute information of the target vehicle 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] A second reporting unit, 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 diagnosis module includes:

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

[0134] The diagnosis 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 running state of the target vehicle meets the target diagnosis condition.

[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, used to parse the running result based on the data parsing format matching the diagnostic instruction in the target diagnostic script file to obtain the corresponding diagnostic result;

[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, determining the diagnosis task type is basic diagnosis;

[0140] When the diagnosis script information is not empty, it is determined that the diagnosis task type is 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 embodiment of the present invention can execute the fault diagnosis method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0145] In one embodiment, Fig.11 is a structural block diagram of a fault diagnosis device provided by an embodiment of the present invention, such as Fig.11As shown, a schematic diagram of the structure of a fault diagnosis device 10 that can be used to implement an embodiment of the present invention is shown. The fault diagnosis device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workbenches, 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 invention described and / or required herein.

[0146] like Fig.11 As shown, the fault diagnosis device 10 includes at least one processor 11, and a memory connected to the at least one processor 11, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc., wherein the memory stores a computer program that can be executed by 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 to the random access memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the fault diagnosis device 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other through a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0147] A number of components in the fault diagnosis device 10 are connected to the I / O interface 15, including: an input unit 16, such as a keyboard, a mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a disk, an optical disk, etc.; 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 through a computer network such as the Internet and / or various telecommunication networks.

[0148] The processor 11 may be a variety of general and / or special processing components 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 special 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 a fault diagnosis method.

[0149] In some embodiments, the fault diagnosis method may be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 18. In some embodiments, part or all of the computer program may 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 may be performed. Alternatively, in other embodiments, the processor 11 may be configured to perform the fault diagnosis method in any other appropriate manner (e.g., by means of firmware).

[0150] Various implementations of the systems and techniques described above 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), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including 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 invention 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, so that when the computer program is executed by the processor, the functions / operations specified in the flow chart and / or block diagram are implemented. The computer program may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0152] In the context of the present invention, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in combination with an instruction execution system, device or equipment. A computer-readable storage medium may 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 may be a machine-readable signal medium. A more specific example of a machine-readable storage medium may 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 may 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 a user; and a keyboard and a pointing device (e.g., a mouse or trackball), through which a user may provide input to the fault diagnosis device. Other types of devices may also be used to provide interaction with a user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).

[0154] The systems and techniques described herein may be implemented in a computing system that includes backend 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 frontend components (e.g., a user computer with a graphical user interface or a 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 backend components, middleware components, or frontend components. The components of the system may 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 a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The client and server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services.

[0156] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps described in the present invention can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution of the present invention can be achieved, and this document does not limit this.

[0157] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A fault diagnosis method, characterized in that: Applicable to remote diagnosis clients, including: 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; Performing fault diagnosis on a target vehicle according to the target diagnosis condition and the target diagnosis script file; The vehicle diagnosis push message is information related to the diagnosis task pushed to the remote diagnosis client; the diagnosis task type is used to characterize different types of diagnosis tasks, and the diagnosis task types include basic diagnosis and script diagnosis; the diagnosis script information is the attribute information related to the diagnosis script file, and the diagnosis script information includes: the size of the diagnosis script file, the download path of the diagnosis script file, and the checksum of the diagnosis script file; Wherein, the obtaining of the corresponding target diagnosis script file and the corresponding target diagnosis condition according to the diagnosis task type and / or the diagnosis script information includes: Acquire corresponding target diagnosis script files and corresponding target diagnosis conditions from different databases according to the diagnosis task type and / or diagnosis script information; The step of acquiring 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; Receiving the latest diagnostic script file and the corresponding latest diagnostic condition that match the vehicle attribute information and are sent by the remote diagnostic service end, and using the latest diagnostic script file and the corresponding latest diagnostic condition as the target diagnostic script file and the corresponding target diagnostic condition; The pending update status is used to characterize the matching status between the diagnostic script file pre-stored in the local database and the diagnostic script information; the determining the pending update status of the diagnostic script file pre-stored in the local database of the remote diagnostic client according to the diagnostic script information includes: If the diagnosis script file pre-stored in the local database matches the diagnosis script information, there is no need to update the diagnosis script file pre-stored in the local database; If the diagnosis script file pre-stored in the local database does not match the diagnosis script information, the diagnosis script file pre-stored in the local database needs to be updated.

2. The method according to claim 1, characterized in that 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, characterized in that 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.

4. The method according to claim 1, characterized in that: 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.

5. The method according to any one of claims 1 to 4, characterized in that After the target vehicle is subjected to fault diagnosis according to the target diagnosis condition and the target diagnosis script file, the method further includes: 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.

6. The method according to any one of claims 1 to 4, characterized in that 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.

7. The method according to any one of claims 1 to 4, characterized in that 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.

8. A fault diagnosis system, characterized in that: include: 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 sent by the push server and 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; The vehicle diagnosis push message is information related to the diagnosis task pushed to the remote diagnosis client; the diagnosis task type is used to characterize different types of diagnosis tasks, and the diagnosis task types include basic diagnosis and script diagnosis; the diagnosis script information is the attribute information related to the diagnosis script file, and the diagnosis script information includes: the size of the diagnosis script file, the download path of the diagnosis script file, and the checksum of the diagnosis script file; 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, including: Acquire corresponding target diagnosis script files and corresponding target diagnosis conditions from different databases according to the diagnosis task type and / or diagnosis 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, including: 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; Receiving the latest diagnostic script file and the corresponding latest diagnostic condition that match the vehicle attribute information and are sent by the remote diagnostic service end, and using the latest diagnostic script file and the corresponding latest diagnostic condition as the target diagnostic script file and the corresponding target diagnostic condition; The pending update status is used to characterize the matching status between the diagnostic script file pre-stored in the local database and the diagnostic script information; the determining the pending update status of the diagnostic script file pre-stored in the local database of the remote diagnostic client according to the diagnostic script information includes: If the diagnosis script file pre-stored in the local database matches the diagnosis script information, there is no need to update the diagnosis script file pre-stored in the local database; If the diagnosis script file pre-stored in the local database does not match the diagnosis script information, the diagnosis script file pre-stored in the local database needs to be updated.

9. A fault diagnosis device, characterized in that: The fault diagnosis device comprises: at least one processor; and 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 perform the fault diagnosis method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the fault diagnosis method according to any one of claims 1 to 7 when executed.

Images