Method, device, system and storage medium for analyzing vehicle diagnostic messages

Abstract

The application provides a method, device, system and storage medium for analyzing vehicle diagnosis messages. The method applied to a server comprises the following steps: receiving a message analysis instruction, wherein the message analysis instruction comprises an open diagnostic data exchange compressed file name, a diagnosis message log file name and a controller identifier to be analyzed; obtaining diagnosis messages corresponding to the controller identifier to be analyzed in the diagnosis message log file; obtaining an open diagnostic data exchange file corresponding to the controller identifier to be analyzed in the open diagnostic data exchange compressed file; finding diagnosis services associated with each diagnosis message in the open diagnostic data exchange file; obtaining a tree structure of the diagnosis services; matching the diagnosis messages with the tree structure to obtain text information as an analysis result; and sending the analysis result to a client. The application improves the analysis speed and has the function of multi-user networking.

Description

TECHNICAL FIELD

[0001] Embodiments of the present application generally relate to the field of vehicle diagnostic technology, and more particularly, to a method, device, system and storage medium for analyzing vehicle diagnostic messages. BACKGROUND

[0002] In the development, manufacturing and maintenance of vehicles, it is often necessary to analyze Controller Area Network (CAN) messages to analyze vehicle body diagnostic information. Especially for a new vehicle model, at the project start stage, software is almost used every day to analyze CAN messages.

[0003] However, the existing CAN message analysis tools are usually closed-source solutions, and their functions cannot be extended. Most of them are desktop stand-alone software, and do not have multi-user network analysis functions. In addition, there are defects such as slow analysis speed, inability to analyze some CAN messages, and errors in analyzing some CAN messages. Therefore, the existing CAN message analysis tools cannot meet the actual needs of vehicle development, manufacturing and maintenance. SUMMARY

[0004] In order to solve the above problems in the prior art, in a first aspect, embodiments of the present application provide a method for analyzing vehicle diagnostic messages, the method being applied to a server, and the method comprising: receiving a message analysis instruction from a client, wherein the message analysis instruction comprises an open diagnostic data exchange compressed file name, a diagnostic message log file name, and a to-be-analyzed controller identifier; obtaining a diagnostic message corresponding to the to-be-analyzed controller identifier in a diagnostic message log file corresponding to the diagnostic message log file name; obtaining an open diagnostic data exchange file corresponding to the to-be-analyzed controller identifier in an open diagnostic data exchange compressed file corresponding to the open diagnostic data exchange compressed file name; for each diagnostic message in the diagnostic message corresponding to the to-be-analyzed controller identifier, finding an associated diagnostic service in the open diagnostic data exchange file; obtaining a tree structure of the diagnostic service according to a reference relationship of the open diagnostic data exchange file in the open diagnostic data exchange compressed file and a node reference relationship in the open diagnostic data exchange file, wherein the tree structure of the diagnostic service comprises a pre-stored correspondence relationship between diagnostic messages and text information; performing bit-by-bit matching between data in the diagnostic message and the tree structure of the diagnostic service to obtain text information corresponding to the diagnostic message as an analysis result; and sending the analysis result to the client.

[0005] In some embodiments, the method further comprises: generating a JS object tablature format file according to the parsing result after obtaining the parsing result; and sending the parsing result to the client comprises: sending the JS object tablature format file to the client.

[0006] In some embodiments, the method further comprises: receiving the open diagnostic data exchange compressed file and the diagnostic message log file from the client; and formatting the diagnostic message log file.

[0007] In a second aspect, embodiments of the present application provide a method for parsing vehicle diagnostic messages, which is applied to a vehicle diagnostic message parsing system comprising a client and a server, and the method comprises: receiving, by the client, a message parsing instruction issued by a user and sending the message parsing instruction to the server, wherein the message parsing instruction comprises an open diagnostic data exchange compressed file name, a diagnostic message log file name, and a controller identifier to be parsed; performing, by the server, the following steps: receiving the message parsing instruction from the client; obtaining diagnostic messages corresponding to the controller identifier to be parsed in a diagnostic message log file corresponding to the diagnostic message log file name; obtaining an open diagnostic data exchange file corresponding to the controller identifier to be parsed in an open diagnostic data exchange compressed file corresponding to the open diagnostic data exchange compressed file name; for each diagnostic message in the diagnostic messages corresponding to the controller identifier to be parsed, finding an associated diagnostic service in the open diagnostic data exchange file; obtaining a tree structure of the diagnostic service according to a reference relationship of the open diagnostic data exchange files in the open diagnostic data exchange compressed file and a node reference relationship in the open diagnostic data exchange files, wherein the tree structure of the diagnostic service comprises a pre-stored correspondence relationship between diagnostic messages and text information; performing bitwise matching between data in the diagnostic messages and the tree structure of the diagnostic service to obtain text information corresponding to the diagnostic messages as a parsing result; sending the parsing result to the client; and displaying, by the client, the parsing result.

[0008] In some embodiments, before receiving, by the client, the message parsing instruction issued by the user, the method further comprises performing, by the client, the following steps: receiving a selection instruction of the user for the open diagnostic data exchange compressed file name and the diagnostic message log file name; obtaining associated controllers in a diagnostic message log file corresponding to the diagnostic message log file name; and displaying the associated controllers in the diagnostic message log file.

[0009] In some embodiments, after displaying the associated controllers in the diagnostic message log file, the method further comprises the following steps performed by the client: receiving a selection instruction of a user for a controller in the associated controllers in the diagnostic message log file; and displaying the user-selected controller as a controller tag.

[0010] In some embodiments, after displaying the user-selected controller as a controller tag, the method further comprises the following steps performed by the client: in response to a selection of the displayed controller tag by the user, generating the message parsing instruction, wherein the controller identifier to be parsed is the controller identifier corresponding to the user-selected controller tag.

[0011] In a third aspect, embodiments of the present application provide a device for parsing vehicle diagnostic messages, the device being applied to a server, the device comprising: a message parsing instruction receiving module configured to receive a message parsing instruction from a client, wherein the message parsing instruction comprises an open diagnostic data exchange compressed file name, a diagnostic message log file name, and a controller identifier to be parsed; a diagnostic message obtaining module configured to obtain diagnostic messages corresponding to the controller identifier to be parsed in a diagnostic message log file corresponding to the diagnostic message log file name; an open diagnostic data exchange file obtaining module configured to obtain an open diagnostic data exchange file corresponding to the controller identifier to be parsed in an open diagnostic data exchange compressed file corresponding to the open diagnostic data exchange compressed file name; a diagnostic service finding module configured to find an associated diagnostic service in the open diagnostic data exchange file for each diagnostic message in the diagnostic messages corresponding to the controller identifier to be parsed; a tree structure obtaining module configured to obtain a tree structure of the diagnostic service according to a reference relationship of the open diagnostic data exchange files in the open diagnostic data exchange compressed file and a node reference relationship in the open diagnostic data exchange file, wherein the tree structure of the diagnostic service comprises a pre-stored correspondence relationship between diagnostic messages and text information; an analysis result obtaining module configured to perform bit-by-bit matching between data in the diagnostic messages and the tree structure of the diagnostic service, and obtain text information corresponding to the diagnostic messages as an analysis result; and an analysis result sending module configured to send the analysis result to the client.

[0012] In a fourth aspect, the embodiments of the present application provide a system for analyzing vehicle diagnostic messages, which comprises a client and a server. The client is configured to receive a message analysis instruction issued by a user and send the message analysis instruction to the server, wherein the message analysis instruction comprises an open diagnostic data exchange compressed file name, a diagnostic message log file name, and a controller identifier to be analyzed; and display an analysis result received from the server. The server is configured to receive the message analysis instruction from the client; obtain a diagnostic message corresponding to the controller identifier to be analyzed in a diagnostic message log file corresponding to the diagnostic message log file name; obtain an open diagnostic data exchange file corresponding to the controller identifier to be analyzed in an open diagnostic data exchange compressed file corresponding to the open diagnostic data exchange compressed file name; find an associated diagnostic service in the open diagnostic data exchange file for each diagnostic message in the diagnostic message corresponding to the controller identifier to be analyzed; obtain a tree structure of the diagnostic service according to a reference relationship of the open diagnostic data exchange file in the open diagnostic data exchange compressed file and a node reference relationship in the open diagnostic data exchange file, wherein the tree structure of the diagnostic service comprises a pre-stored corresponding relationship between diagnostic messages and text information; perform bit-by-bit matching between data in the diagnostic message and the tree structure of the diagnostic service to obtain text information corresponding to the diagnostic message as the analysis result; and send the analysis result to the client.

[0013] In a fifth aspect, the embodiments of the present application provide a storage medium storing computer readable instructions which, when executed by a processor, perform the method for analyzing vehicle diagnostic messages according to any of the above embodiments.

[0014] The method, device, system and storage medium for analyzing vehicle diagnostic messages provided by the embodiments of the present application implement a fast message analysis solution based on B / S architecture, and can realize the function of online message analysis for multiple users.

[0015] Compared with existing message analysis tools, the message analysis solution provided by the embodiments of the present application has several times faster analysis speed, solves the pain points of incorrect or impossible analysis of part of CAN message content of existing message analysis tools, and has the function of online use by multiple users. The kernel program jar package of the CAN message analysis solution can be used in cloud diagnosis projects to realize the functions of extracting and analyzing specific information such as fault diagnosis code DTC and communication parameter ComParam, and can be applied to more scenarios in the future. BRIEF DESCRIPTION OF DRAWINGS

[0016] The above and other objects, features and advantages of embodiments of the present application will become more apparent from the following detailed description read in conjunction with the accompanying drawings, in which:

[0017] Figure 1 A flowchart of a method for parsing a vehicle diagnostic message according to an embodiment of the present application is shown;

[0018] Figure 2 A flowchart of a method for parsing a vehicle diagnostic message according to an embodiment of the present application is shown;

[0019] Figure 3 A block diagram of an apparatus for parsing a vehicle diagnostic message according to an embodiment of the present application is shown.

[0020] In the drawings, identical or corresponding reference signs indicate identical or corresponding parts. DETAILED DESCRIPTION

[0021] The principles and spirit of the present application will be described below with reference to several exemplary embodiments. It should be understood that these embodiments are given only to enable those skilled in the art to better understand and implement the present application, and do not limit the scope of the present application in any way.

[0022] In one aspect, embodiments of the present application provide a method for parsing a vehicle diagnostic message, which is applied to a server. Referring to Figure 1 A flowchart of a method 100 for parsing a vehicle diagnostic message according to an embodiment of the present application is shown.

[0023] As shown in Figure 1 , the method 100 includes steps S101-S107.

[0024] In step S101, a message parsing instruction is received from a client, wherein the message parsing instruction includes an open diagnostic data exchange compressed file (PDX) name, a diagnostic message log file name, and a controller identifier to be parsed. As an example, the diagnostic message can be a controller area network (CAN) message, or other types of messages. Taking the CAN message as an example, the controller identifier to be parsed is represented by a CAN ID, and the diagnostic message log file can also be referred to as a CAN Log file.

[0025] In step S102, the diagnostic message corresponding to the controller identifier to be parsed is obtained in the diagnostic message log file corresponding to the diagnostic message log file name.

[0026] In step S103, an Open Diagnostic Data Exchange (ODX) file, such as an EV file, corresponding to the to-be-analyzed controller identifier is obtained from an Open Diagnostic Data Exchange compressed file corresponding to the Open Diagnostic Data Exchange compressed file name.

[0027] In step S104, for each diagnostic message in the diagnostic message corresponding to the to-be-analyzed controller identifier, an associated diagnostic service (DiagService) is found in the Open Diagnostic Data Exchange file.

[0028] In step S105, according to the reference relationship of the Open Diagnostic Data Exchange file in the Open Diagnostic Data Exchange compressed file and the node reference relationship in the Open Diagnostic Data Exchange file, a tree structure of the diagnostic service is obtained, wherein the tree structure of the diagnostic service includes a pre-stored corresponding relationship of the diagnostic message and the text information. The tree structure may, for example, be in an XML (Extensible Markup Language) format.

[0029] In step S106, the data in the diagnostic message is bitwise matched with the tree structure of the diagnostic service, and text information corresponding to the diagnostic message is obtained, for example, each bit of text information is obtained as an analysis result.

[0030] In step S107, the analysis result is sent to the client.

[0031] As an embodiment of the present application, the method can further include: after obtaining the analysis result, generating a JS object notation (JSON) format file according to the analysis result. In this embodiment, sending the analysis result to the client can include: sending the JSON format file to the client.

[0032] As an embodiment of the present application, the method can further include: receiving the Open Diagnostic Data Exchange compressed file and the diagnostic message log file from the client; and formatting the diagnostic message log file. For example, only as an example, information such as time, controller identifier (CAN ID), and message code in diagnostic message log files of different formats can be unified.

[0033] In another aspect, an embodiment of the present application proposes a method for analyzing a vehicle diagnostic message, which is applied to a vehicle diagnostic message analysis system including a client and a server. Referring to Figure 2Fig. 2 shows a flow chart of a method 200 for analyzing a vehicle diagnostic message according to an embodiment of the present application applied to the vehicle diagnostic message analysis system. As shown in Fig. 2, the method 200 comprises steps S201-S209. Figure 2

[0034] In step S201, a message analysis instruction issued by a user is received by a client and sent to a server, wherein the message analysis instruction comprises an open diagnostic data exchange compressed file name, a diagnostic message log file name, and a controller identifier to be analyzed.

[0035] The following steps S202-S208 are performed by the server. S202-S208 correspond to S101-S107 in the method 100, respectively.

[0036] In step S202, the message analysis instruction is received from the client.

[0037] In step S203, the diagnostic message corresponding to the controller identifier to be analyzed is obtained in the diagnostic message log file corresponding to the diagnostic message log file name.

[0038] In step S204, the open diagnostic data exchange file corresponding to the controller identifier to be analyzed is obtained in the open diagnostic data exchange compressed file corresponding to the open diagnostic data exchange compressed file name.

[0039] In step S205, for each diagnostic message in the diagnostic message corresponding to the controller identifier to be analyzed, the associated diagnostic service is found in the open diagnostic data exchange file.

[0040] In step S206, according to the reference relationship of the open diagnostic data exchange file in the open diagnostic data exchange compressed file and the node reference relationship in the open diagnostic data exchange file, a tree structure of the diagnostic service is obtained, wherein the tree structure of the diagnostic service comprises a pre-stored corresponding relationship between the diagnostic message and the text information.

[0041] In step S207, the data in the diagnostic message is bitwise matched with the tree structure of the diagnostic service to obtain the text information corresponding to the diagnostic message as an analysis result.

[0042] In step S208, the analysis result is sent to the client.

[0043] In step S209, the analysis result is displayed by the client.

[0044] ​As an embodiment of the present application, before the client receives the message parsing instruction issued by the user, the method can further comprise the following steps performed by the client: receiving the user's selection instruction for the open diagnostic data exchange compressed file (PDX) name and the diagnostic message log file name; obtaining the associated controller in the diagnostic message log file corresponding to the diagnostic message log file name; and displaying the associated controller in the diagnostic message log file.

[0045] In the above embodiment, optionally, after displaying the associated controller in the diagnostic message log file, the method further comprises the following steps performed by the client: receiving the user's selection instruction for a controller in the associated controller in the diagnostic message log file; and displaying the user-selected controller as a controller tag. As an example, the associated controller in the diagnostic message log file can be displayed in the form of a check box, and the user can select the corresponding controller to be displayed as a controller tag by checking the check box.

[0046] In the above embodiment, optionally, after displaying the user-selected controller as a controller tag, the method further comprises the following steps performed by the client: in response to the user's selection of the displayed controller tag (e.g., clicking on the controller tag button), generating a message parsing instruction, wherein the controller identifier to be parsed is the controller identifier corresponding to the user-selected controller tag. Thus, the server will subsequently parse the message for the controller corresponding to the user-selected controller tag.

[0047] In yet another aspect, an embodiment of the present application further proposes an apparatus for parsing vehicle diagnostic messages, which is applied to a server. Referring to Figure 3 FIG. 1 shows a block diagram of an apparatus for parsing vehicle diagnostic messages according to an embodiment of the present application. The apparatus comprises modules 301-307.

[0048] The message parsing instruction receiving module 301 can be configured to receive the message parsing instruction from the client, wherein the message parsing instruction comprises an open diagnostic data exchange compressed file name, a diagnostic message log file name, and a controller identifier to be parsed.

[0049] The diagnostic message obtaining module 302 can be configured to obtain the diagnostic message corresponding to the controller identifier to be parsed in the diagnostic message log file corresponding to the diagnostic message log file name.

[0050] The open diagnostic data exchange file obtaining module 303 can be configured to obtain the open diagnostic data exchange file corresponding to the controller identifier to be parsed in the open diagnostic data exchange compressed file corresponding to the open diagnostic data exchange compressed file name.

[0051] The diagnostic service searching module 304 can be configured to search for the associated diagnostic service in the open diagnostic data exchange file for each of the diagnostic messages corresponding to the controller identifier to be parsed.

[0052] The tree structure obtaining module 305 can be configured to obtain the tree structure of the diagnostic service according to the reference relationship of the open diagnostic data exchange file in the open diagnostic data exchange compressed file and the node reference relationship in the open diagnostic data exchange file, wherein the tree structure of the diagnostic service comprises the corresponding relationship between the diagnostic messages and the text information stored in advance.

[0053] The parsing result obtaining module 306 can be configured to match the data in the diagnostic message with the tree structure of the diagnostic service bit by bit, and obtain the text information corresponding to the diagnostic message as the parsing result.

[0054] The parsing result sending module 307 can be configured to send the parsing result to the client.

[0055] In yet another aspect, the embodiments of the present application also propose a system for parsing vehicle diagnostic messages, which comprises a client and a server.

[0056] The client is configured to receive a message parsing instruction issued by a user and send the message parsing instruction to the server, wherein the message parsing instruction comprises an open diagnostic data exchange compressed file name, a diagnostic message log file name, and a controller identifier to be parsed; and display the parsing result received from the server.

[0057] The server is configured to:

[0058] receive the message parsing instruction from the client;

[0059] obtain the diagnostic messages corresponding to the controller identifier to be parsed in the diagnostic message log file corresponding to the diagnostic message log file name;

[0060] obtain the open diagnostic data exchange file corresponding to the controller identifier to be parsed in the open diagnostic data exchange compressed file corresponding to the open diagnostic data exchange compressed file name;

[0061] search for the associated diagnostic service in the open diagnostic data exchange file for each of the diagnostic messages corresponding to the controller identifier to be parsed;

[0062] obtain the tree structure of the diagnostic service according to the reference relationship of the open diagnostic data exchange file in the open diagnostic data exchange compressed file and the node reference relationship in the open diagnostic data exchange file, wherein the tree structure of the diagnostic service comprises the corresponding relationship between the diagnostic messages and the text information stored in advance;

[0063] The data in the diagnostic message is bitwise matched with the tree structure of the diagnostic service to obtain text information corresponding to the diagnostic message as an analysis result.

[0064] The analysis result is sent to the client.

[0065] In yet another aspect, the embodiments of the present application also propose a storage medium storing computer readable instructions, which, when executed by a processor, perform the method of analyzing a vehicle diagnostic message according to any of the above embodiments.

[0066] By way of example only, the message analysis kernel program on the server side can be implemented by Java, the program on the client side (front end) can be implemented by Node.js+Express scheme, and the program on the server side can be implemented by Tomcat+Java WebServlet scheme, and the data exchange with the front end is completed through the HTTP (Hyper Text Transport Protocol) protocol. By defining the data transmission interface between the front end and the back end, the front end sends an HTTP protocol request instruction to the back end. The back end obtains the type and corresponding parameter information of the front end instruction according to the defined interface format, jumps to the corresponding processing method according to the different instruction names, returns the execution result after executing the method, and returns the execution result to the front end again through the HTTP protocol.

[0067] The method, device, system and storage medium for analyzing a vehicle diagnostic message proposed by the embodiments of the present application implement a fast message analysis solution based on the B / S architecture, and can realize the function of online message analysis of multiple users.

[0068] Compared with the existing message analysis tool, the message analysis solution proposed by the embodiments of the present application has several times faster analysis speed, solves the pain points of incorrect or impossible analysis of part of CAN message content of the existing message analysis tool, and has the function of multi-user networking. The kernel program jar package of the CAN message analysis solution can be used in a cloud diagnosis project to realize the functions of extracting and analyzing specific information (such as fault diagnosis code DTC / communication parameter ComParam, etc.), and can be applied to more scenes in the future.

[0069] The foregoing description of implementations of the application has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the application to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. It is intended that the scope of the application be limited not with this detailed description, but rather by the claims appended hereto.

Claims

1. A method of parsing a vehicle diagnostic message, the method comprising: The method is applied to a server, and the method comprises: receiving a message analysis instruction from a client, wherein the message analysis instruction comprises an open diagnostic data exchange compressed file name, a diagnostic message log file name, and a controller identifier to be analyzed; obtaining diagnostic messages corresponding to the controller identifier to be analyzed in a diagnostic message log file corresponding to the diagnostic message log file name; obtaining an open diagnostic data exchange file corresponding to the controller identifier to be analyzed in an open diagnostic data exchange compressed file corresponding to the open diagnostic data exchange compressed file name; for each diagnostic message in the diagnostic messages corresponding to the controller identifier to be analyzed, finding an associated diagnostic service in the open diagnostic data exchange file; obtaining a tree structure of the diagnostic service according to a reference relationship of the open diagnostic data exchange files in the open diagnostic data exchange compressed file and a node reference relationship in the open diagnostic data exchange files, wherein the tree structure of the diagnostic service comprises a correspondence relationship between diagnostic messages and text information stored in advance; performing bit-by-bit matching between data in the diagnostic messages and the tree structure of the diagnostic service to obtain text information corresponding to the diagnostic messages as an analysis result; and sending the analysis result to the client.

2. The method of claim 1, wherein, The method further comprises: generating a JS object tablature format file according to the analysis result after obtaining the analysis result; and sending the JS object tablature format file to the client.

3. The method of claim 1, wherein, The method further comprises: receiving the open diagnostic data exchange compressed file and the diagnostic message log file from the client; and formatting the diagnostic message log file.

4. A method of parsing a vehicle diagnostic message, the method comprising: The method is applied to a vehicle diagnostic message analysis system, and the vehicle diagnostic message analysis system comprises a client and a server, and the method comprises: receiving a message analysis instruction issued by a user by the client and sending the message analysis instruction to the server, wherein the message analysis instruction comprises an open diagnostic data exchange compressed file name, a diagnostic message log file name, and a controller identifier to be analyzed; performing the following steps by the server: receiving the message analysis instruction from the client; obtaining diagnostic messages corresponding to the controller identifier to be analyzed in a diagnostic message log file corresponding to the diagnostic message log file name; obtaining an open diagnostic data exchange file corresponding to the controller identifier to be analyzed in an open diagnostic data exchange compressed file corresponding to the open diagnostic data exchange compressed file name; for each diagnostic message in the diagnostic messages corresponding to the controller identifier to be analyzed, finding an associated diagnostic service in the open diagnostic data exchange file; obtaining a tree structure of the diagnostic service according to a reference relationship of the open diagnostic data exchange files in the open diagnostic data exchange compressed file and a node reference relationship in the open diagnostic data exchange files, wherein the tree structure of the diagnostic service comprises a correspondence relationship between diagnostic messages and text information stored in advance; performing bit-by-bit matching between data in the diagnostic messages and the tree structure of the diagnostic service to obtain text information corresponding to the diagnostic messages as an analysis result; and sending the analysis result to the client. bit-by-bit match the data in the diagnostic message with the tree structure of the diagnostic service to obtain the literal information corresponding to the diagnostic message as the analysis result; send the analysis result to the client; and display the analysis result by the client.

5. The method of claim 4, wherein, Before receiving the message analysis instruction issued by the user by the client, the method further comprises the following steps performed by the client: receiving the selection instruction of the user for the ODX compressed file name and the diagnostic message log file name; obtaining the associated controller in the diagnostic message log file corresponding to the diagnostic message log file name; displaying the associated controller in the diagnostic message log file.

6. The method of claim 5, wherein, After displaying the associated controller in the diagnostic message log file, the method further comprises the following steps performed by the client: receiving the selection instruction of the user for the controller in the associated controller in the diagnostic message log file; displaying the user-selected controller as a controller tag.

7. The method of claim 6, wherein, After displaying the user-selected controller as a controller tag, the method further comprises the following steps performed by the client: in response to the selection of the user for the displayed controller tag, generating the message analysis instruction, wherein the controller identifier to be analyzed is the controller identifier corresponding to the user-selected controller tag.

8. An apparatus for parsing a vehicle diagnostic message, the apparatus comprising: The device is applied to a server, and the device comprises: a message analysis instruction receiving module configured to receive a message analysis instruction from a client, wherein the message analysis instruction comprises an ODX compressed file name, a diagnostic message log file name, and a controller identifier to be analyzed; a diagnostic message obtaining module configured to obtain a diagnostic message corresponding to the controller identifier to be analyzed in a diagnostic message log file corresponding to the diagnostic message log file name; an ODX file obtaining module configured to obtain an ODX file corresponding to the controller identifier to be analyzed in an ODX compressed file corresponding to the ODX compressed file name; a diagnostic service finding module configured to find an associated diagnostic service in the ODX file for each diagnostic message in the diagnostic message corresponding to the controller identifier to be analyzed; a tree structure obtaining module configured to obtain a tree structure of the diagnostic service according to the reference relationship of the ODX file in the ODX compressed file and the node reference relationship in the ODX file, wherein the tree structure of the diagnostic service comprises a pre-stored corresponding relationship between a diagnostic message and literal information; an analysis result obtaining module configured to bit-by-bit match the data in the diagnostic message with the tree structure of the diagnostic service to obtain the literal information corresponding to the diagnostic message as the analysis result; an analysis result sending module configured to send the analysis result to the client.

9. A system for parsing vehicle diagnostic messages, the system comprising: The system comprises a client and a server, the client is configured to: receive a message analysis instruction issued by a user and send the message analysis instruction to a server, wherein the message analysis instruction comprises an open diagnostic data exchange compressed file name, a diagnostic message log file name, and a to-be-analyzed controller identifier; display an analysis result received from the server, the server is configured to: receive the message analysis instruction from the client; obtain diagnostic messages corresponding to the to-be-analyzed controller identifier in a diagnostic message log file corresponding to the diagnostic message log file name; obtain an open diagnostic data exchange file corresponding to the to-be-analyzed controller identifier in an open diagnostic data exchange compressed file corresponding to the open diagnostic data exchange compressed file name; for each diagnostic message in the diagnostic messages corresponding to the to-be-analyzed controller identifier, find an associated diagnostic service in the open diagnostic data exchange file; obtain a tree structure of the diagnostic service according to a reference relationship of the open diagnostic data exchange files in the open diagnostic data exchange compressed file and a node reference relationship in the open diagnostic data exchange files, wherein the tree structure of the diagnostic service comprises a pre-stored corresponding relationship between diagnostic messages and text information; perform bit-by-bit matching between data in the diagnostic messages and the tree structure of the diagnostic service, obtain text information corresponding to the diagnostic messages as an analysis result; send the analysis result to the client.

10. A storage medium storing computer readable instructions which, when executed by a processor, perform the method of any one of claims 1-7.

Images