Fault diagnosis method, system, device and medium

Abstract

This application discloses a fault diagnosis method, system, device, and medium. The method includes: receiving a vehicle diagnostic push message sent from a remote diagnosis server, the message including at least one of a diagnostic task type and diagnostic script information; obtaining a corresponding target diagnostic script file and corresponding target diagnostic conditions, which are interpreted language files obtained by converting a diagnostic database and a diagnostic sequence according to the diagnostic task type and / or diagnostic script information; and performing a fault diagnosis on a target vehicle according to the target diagnostic conditions and the target diagnostic script file. This application eliminates the need for the remote diagnosis client to analyze the diagnostic sequence and frequently read the diagnostic database, thereby reducing the load on the remote diagnosis client and improving the operation efficiency of diagnostic tasks. At the same time, by classifying diagnostic task types, diagnostic efficiency is improved.

Description

[Technical Field]

[0001] This application claims priority from a Chinese patent application bearing application number 202311105130.7, filed with the China Patent Office on August 29, 2023, the entire contents of which are incorporated herein by reference.

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

[0003] With the integration of the Internet and traditional vehicle industries, more and more automotive assemblers are finding it necessary to remotely diagnose and refresh their vehicles.

[0004] Remote vehicle diagnosis is a diagnostic technology that uses the vehicle's mobile communication capabilities (WIFI / 4G / 5G) to remotely control and diagnose the vehicle through the automaker's mobile phone app (or mobile phone application) without the need to send the vehicle to a physical dealership. Remote OTA flashing is one example of the application of remote diagnosis. Furthermore, when combined with cutting-edge technologies such as the Internet of Things, big data, and cloud computing, remote diagnosis technology can provide important support to automakers in areas such as research and development testing, production line electrical inspection, and after-sales diagnosis.

[0005] First, remote diagnosis allows for online data collection, reducing development cycles and costs. During the R&D phase, vehicles require extensive road and durability testing, but the data collection equipment deployed on test vehicles is limited. Remote diagnosis allows for timely analysis and simulation of vehicle malfunctions that occur during the testing process, providing timely feedback to R&D personnel to quickly resolve the malfunctions. Second, remote diagnosis enables cross-station initialization and functional detection during electrical testing on the production line, as well as OTA updates on the production line, enabling customized production of automotive software and satisfying the customization needs of vehicle owners. Finally, remote diagnosis periodically monitors vehicle conditions, diagnoses vehicle health in real time, and, combined with big data statistical analysis, provides early warning of vehicle malfunctions. In the background, remote diagnosis can push guidance and suggestions for vehicle maintenance and repair to the manufacturer's after-sales service center.

[0006] However, the diagnostic database is pre-configured on the vehicle side, and the cloud side directly transmits diagnostic sequence files to the vehicle side, which then analyzes the diagnostic sequence files and obtains corresponding data synthesis diagnostic commands from the diagnostic database according to the diagnostic sequence to perform diagnosis. Because data must be frequently obtained from the diagnostic database according to the diagnostic sequence, the master node on the vehicle side incurs a large resource overhead and operates with low efficiency. Furthermore, for every diagnostic task, the cloud side must first transmit diagnostic sequence files, and then the vehicle side must obtain data synthesis diagnostic commands from the diagnostic database according to the diagnostic sequence to perform diagnosis, resulting in low diagnostic efficiency. Summary of the Invention [Problem to be solved by the invention]

[0007] The present application provides a fault diagnosis method, system, device and medium for solving the technical problems of high resource overhead, low operation efficiency and low diagnosis efficiency in the related art. [Means for solving the problem]

[0008] According to one aspect of the present application, a remote diagnosis client side is provided with: receiving a vehicle diagnosis push message transmitted from a remote diagnosis server side, the vehicle diagnosis push message including at least one of a diagnostic task type and diagnostic script information; According to the diagnostic task type and / or the diagnostic script information, obtaining a corresponding target diagnostic script file and a corresponding target diagnostic condition, which are obtained by converting the diagnostic database and the diagnostic sequence and are interpreted language files; performing a fault diagnosis on the target vehicle in accordance with the target diagnostic conditions and the target diagnostic script file.

[0009] According to another aspect of the present application, there is provided a remote diagnosis client-side system, comprising: a receiving module for receiving a vehicle diagnosis push message transmitted from the remote diagnosis server side, the vehicle diagnosis push message including at least one of a diagnostic task type and diagnostic script information; an acquisition module for acquiring a corresponding target diagnostic script file and a corresponding target diagnostic condition, the script file being an interpreted language file obtained by converting the diagnostic database and the diagnostic sequence according to the diagnostic task type and / or the diagnostic script information; a diagnostic module for performing a fault diagnosis on a target vehicle in accordance with the target diagnostic conditions and the target diagnostic script file.

[0010] According to another aspect of the present application, there is provided a remote diagnostic server side including a diagnostic management platform, a push server, and a content delivery network; and a remote diagnostic client side including a diagnostic client and a diagnostic script engine, The diagnostic management platform synthesizes the diagnostic database and the corresponding diagnostic sequence into a corresponding diagnostic script file. When the diagnostic client receives a vehicle diagnostic push message carrying a diagnostic task type and / or diagnostic script information sent from a push server, the diagnostic client receives a corresponding target diagnostic script file and corresponding target diagnostic conditions, which are interpreted language files and are obtained by the diagnostic management platform converting the diagnostic database and the corresponding diagnostic sequence based on the diagnostic task type and / or the diagnostic script information, sent from the content delivery network, and sends the target diagnostic script file to the diagnostic script engine. Thus, the diagnostic script engine analyzes the target diagnostic script file and provides a fault diagnosis system for diagnosing a target vehicle according to the target diagnostic conditions and the target diagnostic script file.

[0011] According to another aspect of the present application, at least one processor; a memory communicatively coupled to the at least one processor; The memory stores a computer program executable by the at least one processor, the computer program providing a fault diagnosis device executed by the at least one processor so that the at least one processor can execute a fault diagnosis method described in any of the embodiments of the present application.

[0012] According to another aspect of the present application, there is provided a computer-readable storage medium having stored thereon computer instructions for, when executed by a processor, implementing a fault diagnosis method according to any of the embodiments of the present application. [Effects of the Invention]

[0013] The technical solution of the embodiments of the present application involves the remote diagnostic server converting the diagnostic database and diagnostic sequence into a diagnostic script file based on an interpreted language that is more suitable for operation on the remote diagnostic client side, and then sending it to the remote diagnostic client side, thereby eliminating the need for the remote diagnostic client side to analyze the diagnostic sequence and frequently read the diagnostic database, reducing the load on the remote diagnostic client side, and improving the operation efficiency of the diagnostic task. At the same time, the diagnostic task type is classified so that the corresponding target diagnostic script file is obtained from different databases according to the diagnostic task type, thereby improving the diagnostic efficiency. [Brief explanation of the drawings]

[0014] [Figure 1] 1 is a structural block diagram of a fault diagnosis system according to an embodiment of the present application; [Figure 2] FIG. 1 is a flow diagram of a fault diagnosis method according to an embodiment of the present application. [Figure 3] FIG. 2 is a schematic diagram illustrating the configuration of a data structure of a diagnostic script file according to an embodiment of the present application. [Figure 4] FIG. 10 is a flow chart of another fault diagnosis method according to an embodiment of the present application. [Figure 5] 4 is a flow diagram of a further fault diagnosis method according to an embodiment of the present application; [Figure 6] FIG. 10 is a flow chart of yet another fault diagnosis method according to an embodiment of the present application. [Figure 7] FIG. 10 is a flow chart of yet another fault diagnosis method according to an embodiment of the present application. [Figure 8] FIG. 10 is a flow chart of yet another fault diagnosis method according to an embodiment of the present application. [Figure 9] FIG. 2 is a structural block diagram of another fault diagnosis system according to an embodiment of the present application. [Figure 10] 1 is a structural schematic diagram of a fault diagnosis device according to an embodiment of the present application; [Figure 11] 1 is a structural block diagram of a fault diagnosis device according to an embodiment of the present application; DETAILED DESCRIPTION OF THE INVENTION

[0015] Hereinafter, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the drawings in the embodiments of the present application, and it is clear that the described embodiments are only some of the embodiments of the present application, rather than all of the embodiments.

[0016] It should be noted that the terms "first," "second," etc. in the specification and claims of this application and the drawings need not be used to describe a particular order or sequence, but are merely used to distinguish between similar objects. The terms used in this application are interchangeable where appropriate, and it should be understood that the embodiments of this application described herein may be practiced in orders other than those illustrated or described herein. Furthermore, the terms "comprise" and "have," and any variations thereof, are intended to cover non-exclusive inclusions, including, for example, a process, method, system, product, or apparatus of a series of steps or units, and are not necessarily limited to those steps or units explicitly recited, but may include other steps or units not explicitly recited or inherent to the process, method, product, or apparatus.

[0017] In one embodiment, Figure 1 is a structural block diagram of a fault diagnosis system according to an embodiment of the present application. The fault diagnosis method according to the embodiment of the present application is executed by a remote diagnosis client side in the fault diagnosis system. As shown in Figure 1, the fault diagnosis system according to the embodiment of the present application includes a remote diagnosis server side 10 including a diagnostic management platform 101, a push server 102, and a content delivery network 103, and a remote diagnosis client side 20 including a diagnostic client 201 and a diagnostic script engine 202. The diagnostic management platform 101 synthesizes the diagnostic database and the corresponding diagnostic sequence into a corresponding diagnostic script file. When the diagnostic client 201 receives a vehicle diagnostic push message carrying a diagnostic task type and / or diagnostic script information sent from the push server 102, the diagnostic client 201 receives the corresponding target diagnostic script file and the corresponding target diagnostic conditions sent by the content delivery 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. The diagnostic script engine 202 then analyzes the target diagnostic script file and performs fault diagnosis on the target vehicle according to the target diagnostic conditions and the target diagnostic script file. The target diagnostic script file is an interpreted language file obtained by the diagnostic management platform 101 converting the diagnostic database and the corresponding diagnostic sequence.

[0018] In one embodiment, Figure 2 is a flow chart of a fault diagnosis method according to an embodiment of the present application, which is applicable to simple and convenient vehicle fault diagnosis. 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 located on a fault diagnosis device, which can be a remote diagnosis client. As shown in Figure 2, the method includes:

[0019] In S210, the vehicle diagnosis push message sent from the remote diagnosis server is received.

[0020] The vehicle diagnosis push message includes at least one of a diagnostic task type and diagnostic script information. The remote diagnosis server side may be referred to as a remote diagnosis server or a remote diagnosis cloud side (simply referred to as a cloud side). The vehicle diagnosis push message is related information for pushing a diagnostic task to a remote diagnosis client side, and may include a diagnostic task type and / or diagnostic script information. The diagnostic task type is used to represent different types of diagnostic tasks, and may include basic diagnosis and script diagnosis. The basic diagnosis is a diagnostic task required in one diagnostic process for the target vehicle. For example, the basic diagnosis may include, but is not limited to, a fault diagnosis for a temperature sensor in the target vehicle, a fault diagnosis for a voltage sensor in the target vehicle, and a fault diagnosis for the engine rotation speed in the target vehicle. The script diagnosis is a diagnostic task that is further tested on a certain ECU in the target vehicle after the basic diagnosis is completed. For example, the script diagnosis may include a report that the engine water temperature in the target vehicle is too high and that it is necessary to further test whether the parameters of the heat dissipation equipment or the temperature control equipment are normal. In one example, different fields can represent different diagnostic task types, for example, 00 representing basic diagnostics and 01 representing scripted diagnostics.

[0021] The diagnostic script information is attribute information related to the diagnostic script file, including, but not limited to, the size of the diagnostic script file, the download path of the diagnostic script file, and the check value of the diagnostic script file.

[0022] In an embodiment, the diagnostic management platform at the remote diagnostic server side sends a vehicle diagnostic push message including a diagnostic task to the diagnostic client at the remote diagnostic client side, and the vehicle diagnostic push message includes at least diagnostic task type and / or diagnostic script information.

[0023] In S220, according to the diagnostic task type and / or the diagnostic script information, a corresponding target diagnostic script file and a corresponding target diagnostic condition are obtained.

[0024] The target diagnostic script file is an interpreted language file obtained by converting the diagnostic database and diagnostic sequence, where the diagnostic database can be in ODX / Excel format, and the diagnostic sequence can be in OTX or customized format.

[0025] 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 schematic diagram of the data structure of a diagnostic script file according to an embodiment of the present application. As shown in Figure 3, the diagnostic script file includes diagnostic communication information and diagnostic data information. The diagnostic communication information includes at least access information for the electronic control unit (ECU) awaiting diagnosis, and the diagnostic data information includes at least a command execution sequence, diagnostic data, and operation result processing. The access information for the ECU awaiting diagnosis can be understood as connection information for the ECU to be diagnosed. For example, the access information may be a logical address, etc. The diagnostic data information is a set of diagnostic steps. The set of diagnostic steps is a set of all diagnostic steps, and one diagnostic step includes three parts: a command execution sequence, diagnostic data, and operation result processing. The operation result is used to describe the analysis processing logic for the diagnostic return data, which may include, for example, a data analysis format, a subsequent command execution sequence, an abnormality retry count, a time interval, and warning information. Of these, the data analysis format is a format for extracting data that has been returned, for example, a format for extracting data that needs to be returned to the remote diagnostic server side; the execution order of subsequent commands is the next step number according to the returned data; the number of abnormality retries is the number of retries if an abnormality occurs in this command; the time interval is the time interval between this command and the next command; and the warning information is warning information that needs to be given to the user if an abnormality occurs in this command.

[0026] The diagnostic database includes diagnostic data in the diagnostic communication information and the diagnostic data information, and the command execution sequence and operation results in the diagnostic data information are both diagnostic sequences.

[0027] In the embodiment, the target diagnostic script file is a diagnostic script that matches the current diagnostic task, and the target diagnostic condition is the operating state that the target vehicle must maintain when the target diagnostic script file is executed. The diagnostic script file and the diagnostic condition have a one-to-one correspondence, 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 may be obtained from different databases according to the diagnostic task type and / or diagnostic script information.

[0028] In S230, a fault diagnosis is performed on the target vehicle in accordance with the target diagnostic conditions and the target diagnostic script file.

[0029] In the embodiment, if the current operating state of the target vehicle satisfies the target diagnosis conditions, a fault diagnosis is performed on one or more ECUs in the target vehicle based on the target diagnosis script file.

[0030] The technical solution of this embodiment is to have the remote diagnostic server side convert the diagnostic database and diagnostic sequence into a diagnostic script file based on an interpreted language that is more suitable for operation on the remote diagnostic client side, and then send it to the remote diagnostic client side, thereby eliminating the need for the remote diagnostic client side to analyze the diagnostic sequence and frequently read the diagnostic database, reducing the load on the remote diagnostic client side and improving the operation efficiency of the diagnostic task. At the same time, the diagnostic task type is classified so that the corresponding target diagnostic script file is obtained from different databases according to the diagnostic task type, thereby improving the diagnostic efficiency.

[0031] In one embodiment, Figure 4 is a flow chart of another fault diagnosis method according to an embodiment of the present application, which explains the fault diagnosis process when the diagnostic task type is basic diagnosis based on the above embodiment. As shown in Figure 4, the method includes:

[0032] In S410, a vehicle diagnosis push message sent from the remote diagnosis server is received.

[0033] The vehicle diagnostic push message includes at least one of a diagnostic task type and diagnostic script information.

[0034] In S420, if the diagnostic task type is basic diagnosis, the pre-stored diagnostic script file and the corresponding diagnostic conditions are directly obtained from the local database on the remote diagnostic client side.

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

[0036] In S430, a pre-stored diagnostic script file and a corresponding diagnostic condition are set as a corresponding target diagnostic script file and a corresponding target diagnostic condition, respectively.

[0037] A diagnostic script file stored in advance by a diagnostic client on the remote diagnostic client side is set as a corresponding target diagnostic script file, and a diagnostic condition corresponding to the target diagnostic script file is set as a target diagnostic condition.

[0038] In S440, the corresponding target diagnostic protocol stack is invoked according to the diagnostic script logic corresponding to the target diagnostic script file.

[0039] The target diagnostic protocol stack is a diagnostic protocol stack that can be implemented by a remote diagnostic client to execute a target diagnostic script file. For example, the target diagnostic protocol stack may include, but is not limited to, a UDS or DoIP protocol stack.

[0040] In S450, if the current operating state of the target vehicle satisfies the target diagnosis conditions, the target diagnosis protocol stack is adopted and a fault diagnosis is performed on the target vehicle based on the target diagnosis script file.

[0041] If the current operating condition of the target vehicle satisfies the target diagnosis conditions, a diagnostic script engine on the remote diagnosis client side calls the target diagnosis protocol stack and executes the target diagnosis script file, thereby performing a fault diagnosis on the target vehicle.

[0042] The technical solution in this embodiment stores target diagnostic script files and target diagnostic conditions corresponding to frequently used basic diagnoses on the remote diagnostic client side in advance, thereby avoiding the need to frequently obtain target diagnostic script files from the remote diagnostic server side and improving diagnostic efficiency.

[0043] In one embodiment, Figure 5 is a flow chart of a further fault diagnosis method according to an embodiment of the present application, which explains the fault diagnosis process when the diagnostic task type is basic diagnosis based on the above embodiment. As shown in Figure 5, the method includes:

[0044] In S510, a vehicle diagnosis push message sent from the remote diagnosis server is received.

[0045] The vehicle diagnostic push message includes at least one of a diagnostic task type and diagnostic script information.

[0046] In S520, if the diagnostic task type is basic diagnosis, the update waiting status of the diagnostic script file pre-stored in the local database on the remote diagnostic client side is determined according to the diagnostic script information.

[0047] The update waiting status is used to represent 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, there is a need to update the diagnostic script file pre-stored in the local database.

[0048] In S530, if the update waiting status indicates that an update is required, the vehicle attribute information of the target vehicle is reported to the remote diagnosis server.

[0049] The vehicle attribute information is attribute information of the target vehicle itself. For example, the vehicle attribute information may include, but is not limited to, a vehicle identification number and a vehicle ECU identification number. 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. In this case, the remote diagnosis client needs to report the vehicle attribute information of the target vehicle to the remote diagnosis server.

[0050] In S540, the latest diagnostic script file and the corresponding latest diagnostic conditions that match the vehicle attribute information are received from the remote diagnosis server, and the latest diagnostic script file and the corresponding latest diagnostic conditions are set as the target diagnostic script file and the corresponding target diagnostic conditions.

[0051] After receiving the vehicle attribute information of the target vehicle reported by the remote diagnosis client, the remote diagnosis server determines whether or not there is a corresponding diagnostic script file that can be transmitted based on the vehicle attribute information. If there is, it transmits the latest diagnostic script file that matches the vehicle attribute information and the corresponding latest diagnostic conditions to the remote diagnosis client, and sets the latest diagnostic script file as the corresponding target diagnostic script file and the latest diagnostic conditions that correspond to the latest diagnostic script file as the corresponding target diagnostic conditions.

[0052] In S550, if the update waiting status indicates that update is not required, the pre-stored diagnostic script file and the corresponding diagnostic conditions are directly obtained from the local database on the remote diagnosis client side.

[0053] When a diagnostic script matches a diagnostic script file pre-stored in a local database, there is no need to update the diagnostic script file pre-stored in the local database, and the pre-stored diagnostic script file and corresponding diagnostic conditions can be directly obtained from the local database on the remote diagnosis client side.

[0054] In S560, the pre-stored diagnostic script file and the corresponding diagnostic condition are set as the corresponding target diagnostic script file and the corresponding target diagnostic condition, respectively.

[0055] A diagnostic script file stored in advance by a diagnostic client on the remote diagnostic client side is set as a corresponding target diagnostic script file, and a diagnostic condition corresponding to the target diagnostic script file is set as a target diagnostic condition.

[0056] In S570, the corresponding target diagnostic protocol stack is invoked according to the diagnostic script logic corresponding to the target diagnostic script file.

[0057] In S580, if the current operating state of the target vehicle satisfies the target diagnosis conditions, the target diagnosis protocol stack is adopted to perform fault diagnosis on the target vehicle based on the target diagnosis script file.

[0058] For the interpretation of S570 to S580, the corresponding explanations of S440 to S450 in the above embodiment can be referred to, and will not be repeated here.

[0059] The technical solution of this embodiment obtains the corresponding diagnostic script file and diagnostic conditions from the remote diagnostic server only when the diagnostic script file pre-stored in the local database on the remote diagnostic client side needs to be updated; otherwise, it directly obtains the pre-stored diagnostic script file and corresponding diagnostic conditions from the local database on the remote diagnostic client side, thereby avoiding frequent acquisition of the target diagnostic script file from the remote diagnostic server side and improving diagnostic efficiency.

[0060] In one embodiment, Figure 6 is a flow chart of yet another fault diagnosis method according to an embodiment of the present application, which explains the fault diagnosis process when the diagnostic task type is script diagnosis based on the above embodiment. As shown in Figure 6, the method includes:

[0061] In S610, a vehicle diagnosis push message sent from the remote diagnosis server is received.

[0062] The vehicle diagnostic push message includes at least one of a diagnostic task type and diagnostic script information.

[0063] In S620, if the diagnostic task type is script diagnosis, the vehicle attribute information of the target vehicle is reported to the remote diagnosis server.

[0064] In S630, the latest diagnostic script file and the corresponding latest diagnostic conditions that match the vehicle attribute information are received from the remote diagnosis server, and the latest diagnostic script file and the corresponding latest diagnostic conditions are set as the target diagnostic script file and the corresponding target diagnostic conditions.

[0065] In S640, the corresponding target diagnostic protocol stack is invoked according to the diagnostic script logic corresponding to the target diagnostic script file.

[0066] In S650, if the current operating state of the target vehicle satisfies the target diagnosis condition, the target diagnosis protocol stack is adopted to perform fault diagnosis on the target vehicle based on the target diagnosis script file.

[0067] In addition, when the diagnostic task type is script diagnosis, the remote diagnosis client side must report the vehicle attribute information of the target vehicle to the remote diagnosis server side, receive the latest diagnostic script file and the corresponding latest diagnostic conditions that match the vehicle attribute information sent from the remote diagnosis server side, and perform fault diagnosis in accordance with the latest diagnostic script file and the corresponding latest diagnostic conditions.

[0068] In addition, 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 refer to the explanation of S530 to S540 in the above embodiment, and the interpretation of S640 to S650 can refer to the explanation in the above embodiment, and will not be repeated here.

[0069] In one embodiment, after performing a fault diagnosis on a target vehicle in accordance with the target diagnostic conditions and the target diagnostic script file, the method further includes obtaining operation results corresponding to each diagnostic command in the target diagnostic script file, analyzing the operation results based on a data analysis format matching the diagnostic commands in the target diagnostic script file to obtain corresponding diagnostic results, and reporting the diagnostic results and the operation results to the remote diagnostic server. The data analysis format is a format for analyzing the operation results. For example, certain data in the operation results is analyzed according to the data analysis format. It can be understood that the diagnostic commands and the data analysis format have a one-to-one correspondence. In this embodiment, the remote diagnostic client obtains the operation results of each diagnostic command in the target diagnostic script file, analyzes the operation results based on the corresponding data analysis format to obtain corresponding diagnostic results, buffers the operation results and the corresponding diagnostic results, and waits for the completion of the operation of all diagnostic commands in the entire target diagnostic script file before reporting the operation results and the corresponding diagnostic results corresponding to all diagnostic commands in the target diagnostic script file to the remote diagnostic server.

[0070] In one embodiment, Figure 7 is a flow chart of yet another fault diagnosis method according to an embodiment of the present application. This embodiment describes a fault diagnosis process for a vehicle as an example. As shown in Figure 7, the fault diagnosis method in this embodiment includes the following steps:

[0071] At S710, the diagnostic management platform sends a vehicle diagnostic push message via the push server.

[0072] In S720, it is determined whether or not a basic diagnosis is being performed. If it is, S730 is executed, and if it is not, S750 is executed.

[0073] In S730, it is determined whether the pre-stored diagnostic script file needs to be updated, and if it needs to be updated, S750 is executed, and if it does not need to be updated, S740 is executed.

[0074] In S740, a pre-stored diagnostic script file and diagnostic conditions are obtained.

[0075] In S750, the remote diagnosis client reports the vehicle attribute information to the remote diagnosis server.

[0076] In S760, the remote diagnosis server determines whether or not a corresponding diagnostic script file exists based on the vehicle attribute information. If it exists, S770 is executed; if it does not exist, the process ends.

[0077] At S770, the diagnostic management platform transmits the latest diagnostic script file and the corresponding latest diagnostic condition.

[0078] In S780, it is determined whether the current operating state of the target vehicle satisfies the latest diagnostic conditions. If so, S7100 is executed; if not, S790 is executed.

[0079] In S790, changes in the current operating state of the target vehicle are monitored.

[0080] In S7100, the diagnostic script file is executed by the diagnostic script engine.

[0081] In S7110, the diagnosis results and operation results are reported to the remote diagnosis server.

[0082] In one embodiment, Figure 8 is a flow chart of yet another fault diagnosis method according to an embodiment of the present application. This embodiment describes a fault diagnosis process for a vehicle as an example. As shown in Figure 8, the fault diagnosis method in this embodiment includes the following steps:

[0083] At S810, the diagnostic management platform sends a vehicle diagnostic push message via the push server.

[0084] In S820, it is determined whether or not a basic diagnosis is being performed. If it is, S830 is executed, and if it is not, S840 is executed.

[0085] In S830, a pre-stored diagnostic script file and diagnostic conditions are obtained.

[0086] In S840, the remote diagnosis client reports the vehicle attribute information to the remote diagnosis server.

[0087] In S850, the remote diagnosis server determines whether or not a corresponding diagnostic script file exists based on the vehicle attribute information. If it exists, S860 is executed; if it does not exist, the process ends.

[0088] At S860, the diagnostic management platform transmits the latest diagnostic script file and the corresponding latest diagnostic conditions.

[0089] In S870, it is determined whether the current operating state of the target vehicle satisfies the latest diagnostic conditions. If so, S890 is executed, and if not, S880 is executed.

[0090] In S880, changes in the current operating state of the target vehicle are monitored.

[0091] In S890, the diagnostic script file is executed by the diagnostic script engine.

[0092] In S8100, the diagnosis results and operation results are reported to the remote diagnosis server.

[0093] The fault diagnosis process shown in Fig. 8 is different from the fault diagnosis process shown in Fig. 7 in that it is not necessary to check whether the diagnostic script stored in advance in the local database needs to be updated for the basic diagnosis. In the case where the script for the basic diagnosis needs to be updated, the flow of the script diagnosis is followed in both cases.

[0094] In one embodiment, Figure 9 is a structural block diagram of another fault diagnosis system according to an embodiment of the present application. As shown in Figure 9, the fault diagnosis system in this embodiment has the following structure: The diagnostic management platform 101 (cloud side) mainly combines the diagnostic database (in formats such as ODX or Excel) and the corresponding diagnostic sequence (in OTX or customized format) into a diagnostic script file and sends it to the diagnostic client 201 located on the vehicle's master node (usually a TBox, which can be adjusted according to the specific circumstances of the actual item). The diagnostic client 201 then sends the diagnostic script to the diagnostic script engine 202, which analyzes the diagnostic script and performs a diagnosis on the associated ECU according to the diagnostic script content. The diagnostic script is written in an interpreted language (e.g., Lua or JS). The diagnostic script engine 202 integrates a corresponding virtual machine to ensure that the interpreted language code can be executed and interact with the underlying diagnostic protocol stack (UDS / DoIP) 203. While the vehicle-side diagnostic code remains unchanged, different diagnostic functions can be realized using different diagnostic script logic.

[0095] 10 is a structural diagram of a fault diagnosis device according to an embodiment of the present application, which includes a receiving module 1010, a first acquiring module 1020, and a diagnosis module 1030.

[0096] The receiving module 1010 is used to receive a vehicle diagnosis push message sent from the remote diagnosis server, the vehicle diagnosis push message including at least one of a diagnostic task type and diagnostic script information; The first acquisition module 1020 is used to acquire, according to the diagnostic task type and / or diagnostic script information, a corresponding target diagnostic script file, which is an interpreted language file obtained by converting the diagnostic database and the diagnostic sequence, and a corresponding target diagnostic condition; 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.

[0097] In one embodiment, the acquisition module: a first acquiring unit for directly acquiring a pre-stored diagnostic script file and corresponding diagnostic conditions from a local database on the remote diagnostic client side when the diagnostic task type is basic diagnosis; and a second acquisition unit for converting the pre-stored diagnostic script file and the corresponding diagnostic condition into a corresponding target diagnostic script file and a corresponding target diagnostic condition, respectively.

[0098] In one embodiment, the acquisition module: a first determination unit for determining an update waiting status of a diagnostic script file pre-stored in a local database of a remote diagnostic client according to diagnostic script information when the diagnostic task type is basic diagnosis; a first reporting unit for reporting vehicle attribute information of the target vehicle to the remote diagnosis server side when the update waiting status indicates that an update is required; The remote diagnostic server includes a first receiving unit for receiving a latest diagnostic script file and corresponding latest diagnostic conditions that match the vehicle attribute information and are sent from the remote diagnostic server, and for setting the latest diagnostic script file and corresponding latest diagnostic conditions as a target diagnostic script file and corresponding target diagnostic conditions.

[0099] In one embodiment, the acquisition module: a second reporting unit for reporting vehicle attribute information of the target vehicle to the remote diagnosis server side when the diagnostic task type is script diagnosis; and a second receiving unit for receiving the latest diagnostic script file and the corresponding latest diagnostic conditions that match the vehicle attribute information transmitted from the remote diagnostic server side, and for setting the latest diagnostic script file and the corresponding latest diagnostic conditions as the target diagnostic script file and the corresponding target diagnostic conditions.

[0100] In one embodiment, the diagnostic module comprises: a calling unit for calling a corresponding target diagnostic protocol stack according to a diagnostic script logic corresponding to the target diagnostic script file; and a diagnostic unit for employing a target diagnostic protocol stack and performing fault diagnosis on the target vehicle based on a target diagnostic script file when the current operating state of the target vehicle satisfies the target diagnostic conditions.

[0101] In one embodiment, after performing a fault diagnosis on a target vehicle in accordance with the target diagnostic conditions and the target diagnostic script file, the fault diagnosis device a second acquisition module for acquiring operation results corresponding to each diagnostic command in the target diagnostic script file; an analysis module for analyzing the operation results according to a data analysis format matching the diagnostic instructions in the target diagnostic script file, and obtaining corresponding diagnostic results; The vehicle further includes a reporting module for reporting the diagnosis results and operation results to the remote diagnosis server side.

[0102] In one embodiment, if the diagnostic script information is empty, determining that the diagnostic task type is basic diagnostic; If the diagnostic script information is not empty, determine that the diagnostic task type is script diagnostic.

[0103] In one embodiment, the vehicle diagnostic script file includes diagnostic communication information and diagnostic data information; The diagnostic communication information includes at least access information of the electronic control unit ECU waiting for diagnosis; The diagnostic data information includes at least the command execution sequence, the diagnostic data, and the operation result processing.

[0104] The fault diagnosis device according to the embodiments of the present application can execute the fault diagnosis method according to any embodiment of the present application, and has corresponding functional modules and beneficial effects for executing the method.

[0105] In one embodiment, FIG. 11 is a structural block diagram of a fault diagnosis device according to an embodiment of the present application. As shown in FIG. 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 types 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 types of mobile devices, such as personal digital assistants, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components, their connections and relationships, and their functions shown herein are merely exemplary and are not intended to limit the implementation of the present application as described and / or claimed herein.

[0106] As shown in Figure 11, the fault diagnosis device 10 includes at least one processor 11 and memory, such as a read-only memory (ROM) 12 and a random access memory (RAM) 13, communicatively coupled to the at least one processor 11, wherein the memory stores computer programs executable by the at least one processor, and the processor 11 can perform various appropriate operations and processes in accordance with the computer programs stored in the read-only memory (ROM) 12 or loaded into the random access memory (RAM) 13 from a storage unit 18. The RAM 13 can also store various programs and data required for the operation of the fault diagnosis device 10. The processor 11, the ROM 12, and the RAM 13 are interconnected by a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0107] The I / O interface 15 is connected to several components of the fault diagnosis apparatus 10, including an input unit 16, e.g., a keyboard, a mouse, etc., an output unit 17, e.g., various types of displays, speakers, etc., a storage unit 18, e.g., a magnetic disk, an optical disk, etc., and a communication unit 19, e.g., a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 enables the fault diagnosis apparatus 10 to exchange information / data with other devices, e.g., via a computer network of the Internet and / or various telecommunication networks.

[0108] Processor 11 may be a general-purpose and / or special-purpose processing component having various processing and computing capabilities. Some examples of 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 algorithms for machine learning models, digital signal processors (DSPs), and any suitable processor, controller, microcontroller, etc. Processor 11 executes the methods and processes described above, such as the fault diagnosis method.

[0109] In some embodiments, the fault diagnosis method can be embodied as a computer program, which is tangibly included in a computer-readable storage medium, such as storage unit 18. In some embodiments, the computer program can be partially or completely loaded and / or installed in fault diagnosis equipment 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, it can perform one or more steps of the fault diagnosis method described above. Alternatively, in other embodiments, processor 11 may be configured to perform the fault diagnosis method in any other suitable manner (e.g., by firmware).

[0110] Various embodiments of the systems and techniques described herein may be realized in digital electronic circuitry systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific general purpose products (ASSPs), systems on a chip (SOCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. Each of these embodiments may include being embodied in one or more computer programs that can be executed and / or interpreted by a programmable system including at least one programmable processor, which may be a special-purpose or general-purpose programmable processor, capable of receiving data and instructions from, and transmitting data and instructions to, a memory system, at least one input device, and at least one output device.

[0111] Computer programs for implementing the methods of the present application may be written using 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 apparatus, so that when the computer program is executed by the processor, the functions / operations specified in the flowcharts and / or block diagrams are performed. The computer program may be executed entirely on the device, partially on the device, as a separate software package, partially on the device and partially on a remote device, or entirely on a remote device or server.

[0112] In the context of this application, a computer-readable storage medium may be a tangible medium that contains or can store a computer program for use in or in connection with an instruction execution system, device, or apparatus. A computer-readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or apparatus, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include an electrical connection of 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 disc read-only memory (CD-ROM), an optical memory device, a magnetic memory device, or any suitable combination of the foregoing.

[0113] To provide for user interaction, the systems and techniques described herein can be implemented in a diagnostic device that has a display device (e.g., a cathode ray tube (CRT) or liquid crystal display (LCD) monitor) for displaying information to a user, and a keyboard and pointing device (e.g., a mouse or trackball) through which a user can provide input to the diagnostic device. Other types of devices can be used to provide for user interaction; 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 sound, speech, or tactile input).

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

[0115] A computer system may include a client terminal and a server. The client terminal and server are generally separate and typically communicate via a communications network. The relationship between the client terminal and the server is established by a computer program running on the corresponding computer, which establishes a client-server relationship between them. The server may also be called a cloud computing server or cloud host, which is a hosting product within a cloud computing service system and addresses the shortcomings of traditional physical hosts and VPS services, such as difficult management and limited business deployment.

[0116] It should be understood that steps can be rearranged, added, or deleted using the various types of flows shown above. For example, the steps described herein may be performed in parallel, sequentially, or in a different order, as long as the desired results of the technical solution of the present application are achieved, and this specification is not limited thereto.

Claims

1. Remote diagnostics is applied to the client side, receiving a vehicle diagnosis push message transmitted from a remote diagnosis server side, the vehicle diagnosis push message including at least one of a diagnostic task type and diagnostic script information; According to the diagnostic task type and / or the diagnostic script information, obtaining a corresponding target diagnostic script file and a corresponding target diagnostic condition, which are obtained by converting the diagnostic database and the diagnostic sequence and are interpreted language files; performing a fault diagnosis on the target vehicle in accordance with the target diagnostic conditions and the target diagnostic script file. Fault diagnosis method.

2. According to the diagnostic task type, acquiring a corresponding target diagnostic script file and a corresponding target diagnostic condition includes: If the diagnostic task type is basic diagnosis, directly obtain a pre-stored diagnostic script file and corresponding diagnostic conditions from a local database on the remote diagnostic client side; and setting the pre-stored diagnostic script file and the corresponding diagnostic condition as a corresponding target diagnostic script file and a corresponding target diagnostic condition, respectively. The method of claim 1.

3. acquiring a corresponding target diagnostic script file and a corresponding target diagnostic condition according to the diagnostic task type and the diagnostic script information, If the diagnostic task type is basic diagnosis, determining an update waiting status of a diagnostic script file pre-stored in a local database on the remote diagnostic client side according to the diagnostic script information; If the update waiting status indicates that an update is required, reporting the vehicle attribute information of the target vehicle to the remote diagnosis server side; receiving a latest diagnostic script file and corresponding latest diagnostic conditions that match the vehicle attribute information transmitted from the remote diagnosis server side, and setting the latest diagnostic script file and corresponding latest diagnostic conditions as a target diagnostic script file and corresponding target diagnostic conditions; The method of claim 1.

4. acquiring a corresponding target diagnostic script file and a corresponding target diagnostic condition according to the diagnostic task type and the diagnostic script information, If the diagnostic task type is script diagnosis, reporting vehicle attribute information of the target vehicle to the remote diagnosis server side; receiving a latest diagnostic script file and corresponding latest diagnostic conditions that match the vehicle attribute information transmitted from the remote diagnosis server side, and setting the latest diagnostic script file and corresponding latest diagnostic conditions as a target diagnostic script file and corresponding target diagnostic conditions; The method of claim 1.

5. performing a fault diagnosis on a target vehicle in accordance with the target diagnostic conditions and the target diagnostic script file, Invoking a corresponding target diagnostic protocol stack in response to diagnostic script logic corresponding to the target diagnostic script file; When the current operating state of the target vehicle satisfies the target diagnosis condition, employing the target diagnosis protocol stack and performing a fault diagnosis on the target vehicle based on the target diagnosis script file. The method of claim 1.

6. After performing a fault diagnosis on the target vehicle in accordance with the target diagnostic conditions and the target diagnostic script file, Obtaining operation results corresponding to each diagnostic command in the target diagnostic script file; Analyzing the operation result according to a data analysis format matching the diagnostic command in the target diagnostic script file to obtain a corresponding diagnostic result; and reporting the diagnosis result and the operation result to the remote diagnosis server side. The method according to any one of claims 1 to 5.

7. If the diagnostic script information is empty, determine that the diagnostic task type is basic diagnostic; If the diagnostic script information is not empty, determine that the diagnostic task type is script diagnostic; The method according to any one of claims 1 to 5.

8. The diagnostic script file diagnostic communication information including at least access information of an electronic control unit ECU waiting to be diagnosed; and diagnostic data information including at least command execution sequence, diagnostic data, and operation result processing. The method according to any one of claims 1 to 5.

9. A remote diagnostic server side includes a diagnostic management platform, a push server, and a content distribution network; and a remote diagnostic client side includes a diagnostic client and a diagnostic script engine; The diagnostic management platform synthesizes the diagnostic database and the corresponding diagnostic sequence into a corresponding diagnostic script file; when the diagnostic client receives a vehicle diagnostic push message carrying a diagnostic task type and / or diagnostic script information sent from a push server, the diagnostic client receives a corresponding target diagnostic script file and corresponding target diagnostic conditions, which are interpreted language files and are obtained by converting the diagnostic database and the corresponding diagnostic sequence by the diagnostic management platform according to the diagnostic task type and / or the diagnostic script information, sent from a content delivery network; and sends the target diagnostic script file to the diagnostic script engine; thereby, the diagnostic script engine analyzes the target diagnostic script file and performs fault diagnosis on the target vehicle according to the target diagnostic conditions and the target diagnostic script file. Fault diagnosis system.

10. at least one processor; a memory communicatively coupled to the at least one processor; 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. Fault diagnosis equipment.

11. A computer program product storing computer instructions for implementing the fault diagnosis method according to any one of claims 1 to 8 when executed by a processor. A computer-readable storage medium.

Images