Fault diagnosis methods, systems, equipment, and media

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] The present application claims priority of the Chinese Patent Application filed with the National Intellectual Property Administration of China on August 29, 2023, with application number 202311105130.7, and the entire content of said application is 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 Art

[0003] With the integration of the Internet and traditional vehicle enterprises, an increasing number of automobile manufacturers need to remotely diagnose and refresh vehicles.

[0004] Remote vehicle diagnosis is a diagnostic technology that, when there is no need to transport the vehicle to an offline physical store, completes the remote control and diagnostic operation of the vehicle by the background of the automobile manufacturer (or the application program on the mobile phone terminal) by virtue of the mobile communication capability (WIFI / 4G / 5G) configured on the vehicle. Remote over-the-air (OTA) refreshing belongs to one application scenario of remote diagnosis. Furthermore, after remote diagnosis technology is integrated with cutting-edge technologies such as Internet of Things, big data and cloud computing, it can further provide important support for automobile manufacturers in the fields of research and development testing, electrical inspection of production lines, after-sales service diagnosis, etc.

[0005] First, remote diagnostics can collect data online, reducing development cycles and costs. During the research and development phase, vehicles require extensive road and durability testing, but the data collection equipment deployed on test vehicles is limited. Remote diagnostics allows for timely feedback to R&D personnel by analyzing and simulating vehicle failure phenomena that appear during the testing process, helping to quickly resolve failure problems. Second, remote diagnostics can enable cross-station initialization and function detection, as well as OTA (Over-the-Air) refresh of production lines in electrical inspections, realizing customized production of automotive software and meeting the customized needs of car owners. Finally, remote diagnostics can periodically monitor vehicle status, diagnose vehicle health in real time, and, combined with statistical analysis of big data, provide early warnings of vehicle failures. This allows manufacturers to push guidance and suggestions regarding vehicle maintenance and repair to their after-sales service vehicle dealerships.

[0006] However, the diagnostic database is pre-configured on the vehicle side, and the cloud side directly transmits a diagnostic sequence file to the vehicle side. The vehicle side then analyzes the diagnostic sequence file and retrieves corresponding data synthesis diagnostic commands from the diagnostic database according to the diagnostic sequence to perform the diagnosis. Because it is necessary to frequently retrieve data from the diagnostic database according to the diagnostic sequence, the master node on the vehicle side has a large resource overhead and low operational efficiency. Furthermore, for every diagnostic task, it is necessary to transmit a diagnostic sequence file from the cloud side and then have the vehicle side retrieve data synthesis diagnostic commands from the diagnostic database according to the diagnostic sequence to perform the diagnosis, resulting in low diagnostic efficiency. [Overview of the project] [Problems that the invention aims to solve]

[0007] This application provides a fault diagnosis method, system, equipment, and medium to solve the technical problems in related technologies, such as high resource overhead, low operational efficiency, and low diagnostic efficiency. [Means for solving the problem]

[0008] According to one aspect of this invention, it is applied to the client side of remote diagnosis, Receiving a vehicle diagnostic push message sent from the remote diagnostic server that includes at least one of the diagnostic task type and diagnostic script information, Depending on the diagnostic task type and / or the diagnostic script information, obtain the corresponding target diagnostic script file and the corresponding target diagnostic conditions, which are obtained by converting from the diagnostic database and diagnostic sequence and are interpreter-type language files. The present invention provides a fault diagnosis method that includes performing a fault diagnosis on a target vehicle in accordance with the aforementioned target diagnostic conditions and the aforementioned target diagnostic script file.

[0009] According to another aspect of this application, it is applied to the remote diagnostic client side, A receiving module for receiving vehicle diagnostic push messages sent from the remote diagnostic server side, which include at least one of the diagnostic task type and diagnostic script information, An acquisition module for obtaining a corresponding target diagnostic script file, which is an interpreter-type language file obtained by converting from the diagnostic database and diagnostic sequence, and a corresponding target diagnostic condition, depending on the diagnostic task type and / or the diagnostic script information. The present invention provides a fault diagnosis device comprising a diagnostic module for performing fault diagnosis on a target vehicle in accordance with the aforementioned target diagnostic conditions and the aforementioned target diagnostic script file.

[0010] According to another aspect of the present invention, the invention comprises a remote diagnostic server side equipped with a diagnostic management platform, a push server, and a content distribution network, and a remote diagnostic client side equipped with 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 a diagnostic client receives a vehicle diagnostic push message sent from a push server containing the diagnostic task type and / or diagnostic script information, the diagnostic client receives a corresponding target diagnostic script file and corresponding target diagnostic conditions, which are obtained by the diagnostic management platform by converting the diagnostic database and the corresponding diagnostic sequence and are interpreter-type language files, transmitted by the content distribution network based on the diagnostic task type and / or the diagnostic script information. The diagnostic client then transmits the target diagnostic script file to the diagnostic script engine, which then analyzes the target diagnostic script file and provides a fault diagnosis system that performs fault diagnosis on the target vehicle according to the target diagnostic conditions and the target diagnostic script file.

[0011] According to another aspect of this application, At least one processor, The system comprises a memory that is communicated to at least one of the processors, The memory stores a computer program executable by the at least one processor, and the computer program provides a fault diagnosis device executed by the at least one processor so that the at least one processor can execute the fault diagnosis method described in any embodiment of the present application.

[0012] According to another aspect of the present application, a computer-readable storage medium is provided which, when executed by a processor, stores computer instructions for implementing a fault diagnosis method described in any embodiment of the present application. [Effects of the Invention]

[0013] In the technical solution of the embodiment of the present application, the remote diagnosis server converts the diagnosis database and diagnosis sequence into a diagnosis script file based on an interpreted language that is more suitable for the operation of the remote diagnosis client, and transmits the diagnosis script file to the remote diagnosis client. This eliminates the operation that the remote diagnosis client frequently parses the diagnosis sequence and reads the diagnosis database, reduces the load on the remote diagnosis client, and improves the operation efficiency of diagnosis tasks. Meanwhile, the diagnosis task types are classified such that the corresponding target diagnosis script file is obtained from different databases according to the diagnosis task type, thereby improving the diagnosis efficiency. [BRIEF DESCRIPTION OF THE DRAWINGS]

[0014] [Figure 1] FIG. 1 is a structural block diagram of a fault diagnosis system according to an embodiment of the present application. [Figure 2] FIG. 2 is a flow chart of a fault diagnosis method according to an embodiment of the present application. [Figure 3] FIG. 3 is a schematic structural diagram of a data structure of a diagnosis script file according to an embodiment of the present application. [Figure 4] FIG. 4 is a flow chart of another fault diagnosis method according to an embodiment of the present application. [Figure 5] FIG. 5 is a flow chart of a further fault diagnosis method according to an embodiment of the present application. [Figure 6] FIG. 6 is a flow chart of still another fault diagnosis method according to an embodiment of the present application. [Figure 7] FIG. 7 is a flow chart of still another fault diagnosis method according to an embodiment of the present application. [Figure 8] FIG. 8 is a flow chart of still another fault diagnosis method according to an embodiment of the present application. [Figure 9] FIG. 9 is a structural block diagram of another fault diagnosis system according to an embodiment of the present application. [Figure 10] FIG. 10 is a schematic structural diagram of a fault diagnosis apparatus according to an embodiment of the present application. [Figure 11] FIG. 11 is a structural block diagram of a fault diagnosis device according to an embodiment of the present application. [MODE FOR CARRYING OUT THE INVENTION]

[0015] Hereinafter, the technical solutions in the embodiments of the present application will be clearly and completely described with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some embodiments of the present application, rather than all embodiments.

[0016] It should be noted that the terms "first", "second", etc. in the specification, claims, and the above drawings of the present application are not necessarily used to describe a specific order or sequence, but are intended to distinguish similar objects. It should be understood that the data used in this way can be interchanged with each other when appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "comprising", "having", and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not necessarily limited to those explicitly listed steps or units, and may include other steps or units that are not explicitly listed or are inherent to the process, method, product, or device.

[0017] In one embodiment, Fig. 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 an embodiment of the present application is executed by a remote diagnosis client side in the fault diagnosis system. As shown in Fig. 1, the fault diagnosis system in the embodiment of the present application comprises a remote diagnosis server side 10 including a diagnosis management platform 101, a push server 102, and a content delivery network 103, and a remote diagnosis client side 20 including a diagnosis client 201 and a diagnosis script engine 202, The diagnostic management platform 101 synthesizes the diagnostic database and corresponding diagnostic sequences into corresponding diagnostic script files. When the diagnostic client 201 receives a vehicle diagnostic push message from the push server 102 that carries the diagnostic task type and / or diagnostic script information, the diagnostic client 201 receives the corresponding target diagnostic script file and corresponding target diagnostic conditions transmitted by the content distribution network 103 based on the diagnostic task type and / or diagnostic script information. The diagnostic client 201 then 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 target diagnostic script file. The target diagnostic script file is obtained by the diagnostic management platform 101 by converting the diagnostic database and corresponding diagnostic sequences and is an interpreter-type language file.

[0018] In one embodiment, Figure 2 is a flowchart of a fault diagnosis method according to an embodiment of the present invention, which is applicable when performing fault diagnosis on a vehicle in a simple and convenient manner, the method is executable by a fault diagnosis device, the fault diagnosis device can be implemented in hardware and / or software form, and the fault diagnosis device can be installed in a fault diagnosis device. The fault diagnosis device may be on the remote diagnosis client side. As shown in Figure 2, the method includes the following:

[0019] In S210, vehicle diagnostic push messages sent from the remote diagnostic server are received.

[0020] Among these, the vehicle diagnostic push message includes at least one of the diagnostic task type and diagnostic script information. The remote diagnostic server side may be called the remote diagnostic server or the remote diagnostic cloud side (simply called the cloud side). The vehicle diagnostic push message is the relevant information that pushes a diagnostic task to the remote diagnostic client side, and the vehicle diagnostic push message may include the diagnostic task type and / or diagnostic script information. Among these, the diagnostic task type is used to represent different types of diagnostic tasks, and the diagnostic task type may include basic diagnostics and script diagnostics. Basic diagnostics are the diagnostic tasks required in a single diagnostic process for the vehicle under test, and for example, basic diagnostics may include, but are not limited to, fault diagnosis of temperature sensors in the vehicle under test, fault diagnosis of voltage sensors in the vehicle under test, and fault diagnosis of engine rotation speed in the vehicle under test. Script diagnostics are diagnostic tasks that further examine a particular ECU in the vehicle under test after the completion of basic diagnostics, and for example, script diagnostics may include checking whether the engine water temperature in the vehicle under test is too high and whether the parameters of the heat dissipation equipment or temperature control equipment are normal. For example, different fields can represent different diagnostic task types; for instance, 00 could represent a basic diagnostic and 01 could represent a scripted diagnostic.

[0021] Diagnostic script information refers to the attribute information associated with a diagnostic script file. For example, diagnostic script information may include, but is not limited to, the size of the diagnostic script file, the download path of the diagnostic script file, and the check values ​​of the diagnostic script file.

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

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

[0024] Of these, the target diagnostic script file is an interpreted language file obtained by converting from the diagnostic database and diagnostic sequence. The diagnostic database may be in a format such as ODX / Excel, and the diagnostic sequence may be in an 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 interpreter-type language specifically adopted. Figure 3 is a schematic diagram of the configuration 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, of which the diagnostic communication information includes at least access information of electronic control units (ECUs) awaiting diagnosis, and the diagnostic data information includes at least the instruction execution order, diagnostic data, and operation result processing. The access information of ECUs awaiting diagnosis can be understood as connection information of the ECUs that need to be diagnosed, and for example, the access information may be a logical address, etc. The diagnostic data information is, i.e., a set of diagnostic steps, and the set of diagnostic steps is a set of all diagnostic steps, and one diagnostic step includes three parts: instruction execution order, diagnostic data, and operation result processing. Of which, the operation result may include, for example, a data analysis format, the order of subsequent instruction execution, the number of abnormal retries, a time interval, and caution information, and is used to describe the analysis processing logic for the data returned by the diagnosis. Among these, the data analysis format is the format used to extract data from the returned data, for example, a format for extracting data that needs to be returned to the remote diagnostic server; the subsequent instruction execution order is the number of the next step according to the returned data; the number of abnormal retries is the number of retries if an abnormality occurs in this instruction; the time interval is the time interval between this instruction and the next instruction; and the warning information is warning information that needs to be given to the user if an abnormality occurs in this instruction.

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

[0027] In this 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. There is a one-to-one correspondence between the diagnostic script file and the diagnostic condition; that is, one target diagnostic script file corresponds to one target diagnostic condition. Depending on the diagnostic task type and / or the diagnostic script information, the corresponding target diagnostic script file and the corresponding target diagnostic condition may be obtained from different databases.

[0028] In the S230, fault diagnosis is performed on the target vehicle according to the target diagnostic conditions and target diagnostic script file.

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

[0030] The proposed technology of this embodiment involves the remote diagnostic server converting the diagnostic database and diagnostic sequence into a diagnostic script file based on an interpreter-type language more suitable for operation on the remote diagnostic client side, and sending it to the remote diagnostic client side. This eliminates the need for the remote diagnostic client side to frequently analyze the diagnostic sequence and read the diagnostic database, thereby reducing the load on the remote diagnostic client side and improving the operational efficiency of the diagnostic task. At the same time, it improves diagnostic efficiency by classifying the diagnostic task type so that the corresponding target diagnostic script file is obtained from a different database depending on the diagnostic task type.

[0031] In one embodiment, Figure 4 is a flowchart of another fault diagnosis method according to an embodiment of the present invention, and this embodiment describes 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 the following.

[0032] In S410, vehicle diagnostic push messages sent from the remote diagnostic server are received.

[0033] Of these, vehicle diagnostic push messages include at least one of the following: diagnostic task type and diagnostic script information.

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

[0035] In the case where the diagnostic task type is basic diagnosis, the diagnostic client on the remote diagnostic client side can directly retrieve pre-stored diagnostic script files and corresponding diagnostic conditions from the local database.

[0036] In S430, the pre-stored diagnostic script file and its corresponding diagnostic conditions are designated as the corresponding target diagnostic script file and its corresponding target diagnostic conditions, respectively.

[0037] On the remote diagnostic client side, the diagnostic script file pre-stored by the diagnostic client is designated as the target diagnostic script file, and the diagnostic conditions corresponding to the target diagnostic script file are designated as the target diagnostic conditions.

[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] Among these, the target diagnostic protocol stack is a diagnostic protocol stack that can satisfy the requirement that the remote diagnostic client execute the 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 target vehicle's current operating status meets the target diagnostic conditions, the target diagnostic protocol stack is adopted, and fault diagnosis is performed on the target vehicle based on the target diagnostic script file.

[0041] If the target vehicle's current operating status meets the diagnostic conditions, the diagnostic script engine on the remote diagnostic client side calls the target diagnostic protocol stack and executes the target diagnostic script file to perform fault diagnosis on the target vehicle.

[0042] The proposed technology in this embodiment improves diagnostic efficiency by pre-storing target diagnostic script files and target diagnostic conditions corresponding to frequently used basic diagnostics on the remote diagnostic client side, thereby avoiding the need to frequently retrieve target diagnostic script files from the remote diagnostic server side.

[0043] In one embodiment, Figure 5 is a flowchart of a further fault diagnosis method according to an embodiment of the present invention, and this embodiment describes 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 the following.

[0044] In S510, vehicle diagnostic push messages sent from the remote diagnostic server are received.

[0045] Of these, vehicle diagnostic push messages include at least one of the following: diagnostic task type and diagnostic script information.

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

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

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

[0049] Of these, vehicle attribute information refers to the attribute information possessed by the target vehicle itself. For example, vehicle attribute information may include, but is not limited to, vehicle identification numbers and vehicle ECU identification numbers. If the diagnostic script file stored in the local database does not match the diagnostic script, it is necessary to update the diagnostic script file stored in the local database. At this time, the remote diagnostic client needs to report the vehicle attribute information of the target vehicle to the remote diagnostic server.

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

[0051] The remote diagnostic server receives vehicle attribute information of the target vehicle reported by the remote diagnostic client, and then determines whether a corresponding diagnostic script file exists that can be transmitted based on the vehicle attribute information. If such a file exists, it transmits the latest diagnostic script file that matches the vehicle attribute information and the corresponding latest diagnostic conditions to the remote diagnostic client. The latest diagnostic script file is designated as the target diagnostic script file, and the latest diagnostic conditions corresponding to the latest diagnostic script file are designated as the target diagnostic conditions.

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

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

[0054] In S560, pre-stored diagnostic script files and their corresponding diagnostic conditions are designated as the corresponding target diagnostic script files and their corresponding target diagnostic conditions, respectively.

[0055] On the remote diagnostic client side, the diagnostic script file pre-stored by the diagnostic client is designated as the target diagnostic script file, and the diagnostic conditions corresponding to the target diagnostic script file are designated as the target diagnostic conditions.

[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 target vehicle's current operating status meets the target diagnostic conditions, the target diagnostic protocol stack is adopted, and fault diagnosis is performed on the target vehicle based on the target diagnostic script file.

[0058] The interpretation of S570 to S580 can be found by referring to the corresponding explanations of S440 to S450 in the above embodiment, and will not be explained again here.

[0059] The proposed technology of this embodiment improves diagnostic efficiency by avoiding frequent retrieval of the target diagnostic script file from the remote diagnostic server. This is achieved by retrieving the corresponding diagnostic script file and diagnostic conditions from the remote diagnostic server only when the diagnostic script file pre-stored in the remote diagnostic client's local database needs to be updated, and otherwise directly retrieving the pre-stored diagnostic script file and corresponding diagnostic conditions from the remote diagnostic client's local database.

[0060] In one embodiment, Figure 6 is a flowchart of yet another fault diagnosis method according to an embodiment of the present invention, and this embodiment describes 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 the following.

[0061] In S610, vehicle diagnostic push messages sent from the remote diagnostic server are received.

[0062] Of these, vehicle diagnostic push messages include at least one of the following: diagnostic task type and diagnostic script information.

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

[0064] In the S630, the latest diagnostic script file and corresponding latest diagnostic conditions that match the vehicle attribute information transmitted from the remote diagnostic server are received, and the latest diagnostic script file and corresponding latest diagnostic conditions are designated as the target diagnostic script file and 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 target vehicle's current operating status meets the target diagnostic conditions, the target diagnostic protocol stack is adopted, and fault diagnosis is performed on the target vehicle based on the target diagnostic script file.

[0067] Furthermore, if the diagnostic task type is script-based diagnostics, the remote diagnostic client must report the vehicle attribute information of the target vehicle to the remote diagnostic server, receive the latest diagnostic script file and corresponding latest diagnostic conditions that match the vehicle attribute information transmitted from the remote diagnostic server, and perform fault diagnosis according to the latest diagnostic script file and corresponding latest diagnostic conditions.

[0068] Furthermore, the process in S620 for reporting the vehicle attribute information of the target vehicle to the remote diagnostic server, and the process in S630 for receiving the latest diagnostic script file and corresponding latest diagnostic conditions can be explained by referring to the descriptions of S530 to S540 in the above embodiment, and the interpretation of S640 to S650 can be explained by referring to the descriptions in the above embodiment, and will not be explained again here.

[0069] In one embodiment, after performing a fault diagnosis on the target vehicle according to the target diagnostic conditions and target diagnostic script file, the following steps are taken: obtaining the operation results corresponding to each diagnostic command in the target diagnostic script file; analyzing the operation results based on a data analysis format that matches the diagnostic commands in the target diagnostic script file to obtain the corresponding diagnostic results; and reporting the diagnostic results and operation results to the remote diagnostic server. The data analysis format is the format used to analyze the operation results. For example, a certain data in the operation results is analyzed to have a corresponding meaning according to the data analysis format. It can be understood that there is a one-to-one correspondence between the diagnostic command and the data analysis format. In the embodiment, the remote diagnostic client obtains the operation results for each diagnostic command in the target diagnostic script file, analyzes the operation results based on the corresponding data analysis format to obtain the corresponding diagnostic results, buffers the operation results and the corresponding diagnostic results, waits for the completion of the operation of all diagnostic commands in the entire target diagnostic script file, and then reports 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 flowchart of yet another fault diagnosis method according to an embodiment of the present application. This embodiment describes the fault diagnosis process of a vehicle. As shown in Figure 7, the fault diagnosis method in this embodiment includes the following steps.

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

[0072] In S720, it is determined whether or not it is a basic diagnostic test. If it is a basic diagnostic test, S730 is executed; otherwise, S750 is executed.

[0073] In S730, it is determined whether or not the pre-stored diagnostic script file needs to be updated. If it does, S750 is executed; otherwise, S740 is executed.

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

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

[0076] In S760, the remote diagnostic server determines whether a corresponding diagnostic script file exists based on the vehicle attribute information. If it exists, it executes S770; otherwise, it terminates.

[0077] In S770, the diagnostic management platform transmits the latest diagnostic script files and corresponding latest diagnostic conditions.

[0078] In S780, it is determined whether the current operating status of the target vehicle meets the latest diagnostic conditions. If it does, S7100 is executed; otherwise, S790 is executed.

[0079] In S790, the current operating status of the target vehicle is monitored for changes.

[0080] In the S7100, the diagnostic script engine executes the diagnostic script file.

[0081] In S7110, the diagnostic results and operational results are reported to the remote diagnostic server.

[0082] In one embodiment, Figure 8 is a flowchart of yet another fault diagnosis method according to an embodiment of the present invention. This embodiment describes the fault diagnosis process of a vehicle. As shown in Figure 8, the fault diagnosis method in this embodiment includes the following steps.

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

[0084] In S820, it is determined whether or not it is a basic diagnostic test. If it is a basic diagnostic test, S830 is executed; otherwise, S840 is executed.

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

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

[0087] In S850, the remote diagnostic server determines whether a corresponding diagnostic script file exists based on the vehicle attribute information. If it exists, it executes S860; otherwise, it terminates.

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

[0089] In S870, it is determined whether the current operating status of the target vehicle meets the latest diagnostic conditions. If it does, S890 is executed; otherwise, S880 is executed.

[0090] In S880, the system monitors changes in the current operating status of the target vehicle.

[0091] In the S890, the diagnostic script engine executes the diagnostic script file.

[0092] In the S8100, diagnostic results and operational results are reported to the remote diagnostic server.

[0093] The fault diagnosis process shown in Figure 8 differs from the fault diagnosis process shown in Figure 7 in that, for basic diagnosis, it does not require checking whether the diagnostic script pre-stored in the local database needs to be updated. In cases where the basic diagnosis script needs to be updated, both follow the script diagnosis flow.

[0094] In one embodiment, Figure 9 is a structural block diagram of another fault diagnosis system according to an embodiment of the present invention. As shown in Figure 9, the fault diagnosis system in this embodiment has the following structure: The diagnostic management platform 101 (cloud side) primarily synthesizes the diagnostic database (in ODX / Excel format, etc.) and corresponding diagnostic sequences (in OTX or customized format) into a diagnostic script file, and transmits it to the diagnostic client 201 located on the vehicle's master node (usually a TBox, which can be adjusted according to the specific situation of the actual items). The diagnostic client 201 sends the diagnostic script to the diagnostic script engine 202, which parses the diagnostic script and performs diagnostics on the relevant ECUs 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 within the diagnostic script engine 202, ensuring that the interpreted language code can be executed and interact with the lower-layer diagnostic protocol stack (UDS / DoIP) 203. If the code applied to the vehicle's diagnostics remains unchanged, different diagnostic functions can be realized by different diagnostic script logic.

[0095] In one embodiment, Figure 10 is a schematic diagram of the structure of a fault diagnosis device according to an embodiment of the present invention. As shown in Figure 10, the device comprises a receiving module 1010, a first acquisition module 1020, and a diagnostic module 1030.

[0096] Of these, the receiving module 1010 is used to receive vehicle diagnostic push messages sent from the remote diagnostic server side, which include at least one of the diagnostic task type and diagnostic script information. The first acquisition module 1020 is used to acquire the corresponding target diagnostic script file and the corresponding target diagnostic conditions, which are obtained by converting from the diagnostic database and diagnostic sequence and are interpreter-type language files, depending on the diagnostic task type and / or diagnostic script information. The diagnostic module 1030 is used to perform fault diagnosis on the target vehicle according to the target diagnostic conditions and target diagnostic script file.

[0097] In one embodiment, the acquisition module is: If the diagnostic task type is basic diagnostics, a first acquisition unit is used to directly retrieve the pre-stored diagnostic script file and corresponding diagnostic conditions from the local database on the remote diagnostic client side. It comprises a second acquisition unit for converting pre-stored diagnostic script files and corresponding diagnostic conditions into corresponding target diagnostic script files and corresponding target diagnostic conditions, respectively.

[0098] In one embodiment, the acquisition module is: If the diagnostic task type is basic diagnosis, a first decision unit is used to determine the update waiting status of the diagnostic script file, which is pre-stored in the local database on the remote diagnostic client side, according to the diagnostic script information. If the update status indicates that an update is required, a first reporting unit is used to report the vehicle attribute information of the target vehicle to the remote diagnostic server, The system includes a first receiving unit that receives the latest diagnostic script file and corresponding latest diagnostic conditions that match vehicle attribute information transmitted from the remote diagnostic server, and sets the latest diagnostic script file and corresponding latest diagnostic conditions as the target diagnostic script file and corresponding target diagnostic conditions.

[0099] In one embodiment, the acquisition module is: If the diagnostic task type is script diagnostic, a second reporting unit is provided to report the vehicle attribute information of the target vehicle to the remote diagnostic server, The system includes a second receiving unit that receives the latest diagnostic script file and corresponding latest diagnostic conditions that match the vehicle attribute information transmitted from the remote diagnostic server, and sets the latest diagnostic script file and corresponding latest diagnostic conditions as the target diagnostic script file and corresponding target diagnostic conditions.

[0100] In one embodiment, the diagnostic module is A call unit for calling the corresponding target diagnostic protocol stack according to the diagnostic script logic corresponding to the target diagnostic script file, The system includes a diagnostic unit that, if the current operating status of the target vehicle meets the target diagnostic conditions, employs a target diagnostic protocol stack and performs fault diagnosis on the target vehicle based on a target diagnostic script file.

[0101] In one embodiment, after performing a fault diagnosis on the target vehicle according to the target diagnostic conditions and the target diagnostic script file, the fault diagnosis device performs the following: A second acquisition module for obtaining the operational results corresponding to each diagnostic command in the target diagnostic script file, An analysis module for analyzing operational results based on a data analysis format that matches the diagnostic commands in the target diagnostic script file, and obtaining corresponding diagnostic results, It further includes a reporting module for reporting diagnostic results and operational results to a remote diagnostic server.

[0102] In one embodiment, if the diagnostic script information is empty, it is determined that the diagnostic task type is basic diagnostics. If the diagnostic script information is not empty, the diagnostic task type is determined to be a script diagnostic.

[0103] In one embodiment, the vehicle diagnostic script file includes diagnostic communication information and diagnostic data information. Of these, the diagnostic communication information includes at least access information for electronic control units (ECUs) awaiting diagnosis. Diagnostic data information includes at least the command execution order, diagnostic data, and operation result processing.

[0104] The fault diagnosis device according to the embodiment of the present application is capable of performing the fault diagnosis method according to any embodiment of the present application and is equipped with a functional module and beneficial effects corresponding to the performance of the method.

[0105] In one embodiment, Figure 11 is a structural block diagram of a fault diagnosis device according to an embodiment of the present application, and as shown in Figure 11, a schematic diagram of the structure of a fault diagnosis device 10 that can be used to carry out an embodiment of the present application is shown. The fault diagnosis device is intended to represent various forms of digital computers, e.g., laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The fault diagnosis device can further represent various forms of mobile devices, e.g., personal digital processing, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are illustrative and are not intended to limit the realization of the present application as described and / or required herein.

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

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

[0108] The processor 11 may be a general-purpose and / or dedicated processing component having various 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 dedicated artificial intelligence (AI) computing chips, processors that run various machine learning model algorithms, digital signal processors (DSPs), and any suitable processor, controller, microcontroller, etc. The processor 11 performs some of the methods and processes described above, such as fault diagnosis methods.

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

[0110] In this specification, various embodiments of the systems and technologies described above can be implemented as digital electronic circuit 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 implemented in one or more computer programs, which can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor capable of receiving data and instructions from a memory system, at least one input device, and at least one output device, and transmitting data and instructions to the memory system, the at least one input device, and the at least one output device.

[0111] Computer programs for carrying out the method of the present invention may be written using any combination of one or more programming languages. These computer programs can be provided to the processor of a general-purpose computer, a dedicated computer, or other programmable data processing device, so that when the computer program is executed by the processor, the functions / operations defined in the flowchart and / or block diagram are performed. The computer programs may be executed entirely on a device, partially on a device, as a standalone software package, partially on a 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 computer programs used in or in combination with an instruction execution system, device, or apparatus. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or apparatus, or any appropriate combination of the above. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include one or more line-based electrical connections, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical memory devices, magnetic memory devices, or any appropriate combination of the above.

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

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

[0115] A computer system may include client terminals and servers. Client terminals and servers are generally geographically separated and typically interact via a communication network. The relationship between client terminals and servers is established through corresponding computer operation and computer programs that have a client-server relationship with each other. The server may also be a cloud server, also called a cloud computing server or cloud host, which is a hosting product within a cloud computing service system, designed to address the shortcomings of traditional physical hosts and VPS services, such as difficulty in management and limited operational flexibility.

[0116] It should be understood that the steps can be rearranged, added, or deleted using the various forms of flows described above. For example, each step described herein may be performed in parallel, sequentially, or in a different order, as long as the desired results of the present invention are achieved, and is not limited to these in this specification.

Claims

1. Applied to the client side of remote diagnostics, Receiving a vehicle diagnostic push message sent from the remote diagnostic server that includes at least one of the diagnostic task type and diagnostic script information, Depending on the diagnostic task type and / or the diagnostic script information, obtain the corresponding target diagnostic script file and the corresponding target diagnostic conditions, which are obtained by converting from the diagnostic database and diagnostic sequence and are interpreter-type language files. This includes performing a fault diagnosis on the target vehicle in accordance with the aforementioned target diagnostic conditions and the aforementioned target diagnostic script file, The diagnostic script information is attribute information related to the diagnostic script file, and the diagnostic script information includes the size of the diagnostic script file, the download path of the diagnostic script file, and the check value of the diagnostic script file. Depending on the diagnostic task type and the diagnostic script information, obtaining the corresponding target diagnostic script file and the corresponding target diagnostic conditions is: If the diagnostic task type is a basic diagnostic, the following steps are taken: determine the update waiting status of the diagnostic script file pre-stored in the 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, report the vehicle attribute information of the target vehicle to the remote diagnostic server; receive the latest diagnostic script file and corresponding latest diagnostic conditions that match the vehicle attribute information transmitted from the remote diagnostic server side, and set the latest diagnostic script file and corresponding latest diagnostic conditions as the target diagnostic script file and corresponding target diagnostic conditions, or If the diagnostic task type is a script diagnostic, the process includes reporting the vehicle attribute information of the target vehicle to the remote diagnostic server, receiving the latest diagnostic script file and corresponding latest diagnostic conditions that match the vehicle attribute information transmitted from the remote diagnostic server, and setting the latest diagnostic script file and corresponding latest diagnostic conditions as the target diagnostic script file and corresponding target diagnostic conditions. Troubleshooting methods.

2. Depending on the diagnostic task type, obtaining the corresponding target diagnostic script file and the corresponding target diagnostic conditions is: If the diagnostic task type is a basic diagnosis, the diagnostic script file and corresponding diagnostic conditions are directly retrieved from the local database on the remote diagnostic client side. This includes making the pre-stored diagnostic script file and corresponding diagnostic conditions the corresponding target diagnostic script file and corresponding target diagnostic conditions, respectively. The fault diagnosis method according to claim 1.

3. Performing a fault diagnosis on the target vehicle in accordance with the aforementioned target diagnostic conditions and the aforementioned target diagnostic script file is: In accordance with the diagnostic script logic corresponding to the aforementioned target diagnostic script file, the corresponding target diagnostic protocol stack is invoked, If the current operating status of the target vehicle satisfies the target diagnostic conditions, the target diagnostic protocol stack is adopted, and a fault diagnosis is performed on the target vehicle based on the target diagnostic script file, including: The fault diagnosis method according to claim 1.

4. After performing a fault diagnosis on the target vehicle in accordance with the aforementioned target diagnostic conditions and the aforementioned target diagnostic script file, To obtain the operation results corresponding to each diagnostic command in the aforementioned target diagnostic script file, The operation results are analyzed based on a data analysis format that matches the diagnostic command in the target diagnostic script file, and a corresponding diagnostic result is obtained. The following is further included: reporting the aforementioned diagnostic results and the aforementioned operational results to the remote diagnostic server. A fault diagnosis method according to any one of claims 1 to 3.

5. If the diagnostic script information is not empty, determine that the diagnostic task type is a script diagnostic. A fault diagnosis method according to any one of claims 1 to 3.

6. The aforementioned diagnostic script file is At least diagnostic communication information including access information for electronic control units (ECUs) awaiting diagnosis, Includes at least the order of command execution, diagnostic data, and diagnostic data information including the processing of the operation result, A fault diagnosis method according to any one of claims 1 to 3.

7. The system comprises a remote diagnostic server side equipped with a diagnostic management platform, a push server, and a content distribution network, and a remote diagnostic client side equipped with 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 a diagnostic client receives a vehicle diagnostic push message from a push server containing the diagnostic task type and / or diagnostic script information, the diagnostic client receives a corresponding target diagnostic script file and corresponding target diagnostic conditions, which are obtained by the diagnostic management platform by converting the diagnostic database and the corresponding diagnostic sequence and are interpreter-type language files, transmitted by the content distribution network, based on the diagnostic task type and / or the diagnostic script information. The diagnostic client then transmits the target diagnostic script file to the diagnostic script engine, which 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 diagnostic script information includes the relevant attribute information of the diagnostic script file, the size of the diagnostic script file, the download path of the diagnostic script file, and the check values ​​of the diagnostic script file. The remote diagnostic client is configured to acquire the corresponding target diagnostic script file and the corresponding target diagnostic conditions according to the diagnostic task type and the diagnostic script information. Depending on the diagnostic task type and the diagnostic script information, obtaining the corresponding target diagnostic script file and the corresponding target diagnostic conditions is: If the diagnostic task type is a basic diagnostic, the following steps are taken: determine the update waiting status of the diagnostic script file pre-stored in the 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, report the vehicle attribute information of the target vehicle to the remote diagnostic server; receive the latest diagnostic script file and corresponding latest diagnostic conditions that match the vehicle attribute information transmitted from the remote diagnostic server side, and set the latest diagnostic script file and corresponding latest diagnostic conditions as the target diagnostic script file and corresponding target diagnostic conditions, or If the diagnostic task type is a script diagnostic, the process includes reporting the vehicle attribute information of the target vehicle to the remote diagnostic server, receiving the latest diagnostic script file and corresponding latest diagnostic conditions that match the vehicle attribute information transmitted from the remote diagnostic server, and setting the latest diagnostic script file and corresponding latest diagnostic conditions as the target diagnostic script file and corresponding target diagnostic conditions. Fault diagnosis system.

8. At least one processor, The system comprises a memory that is communicated to at least one of the processors, 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 in such a way that the at least one processor can perform the fault diagnosis method described in any one of claims 1 to 3. Fault diagnosis equipment.

9. When executed by the processor, computer instructions for implementing the fault diagnosis method described in any one of claims 1 to 3 are stored. Computer-readable storage medium.

Images