Vehicle diagnosis method and system, diagnosis server, and storage medium

Abstract

The application provides a vehicle diagnosis method, a diagnosis server, a vehicle diagnosis system and a storage medium. The method comprises the following steps: a front-end interaction processor receives a service request and transmits the service request to a service processor; the service processor performs the following steps: calling a data processor to obtain communication parameter information and encoding the communication parameter information, and calling a diagnosis detector interaction processor to send the encoded communication parameter information to a vehicle diagnosis detector; calling a protocol processor to perform protocol conversion on the service request to generate a diagnosis request message, and calling the diagnosis detector interaction processor to send the diagnosis request message to the vehicle diagnosis detector; calling the diagnosis detector interaction processor to receive a diagnosis response message, and calling the protocol processor to perform protocol reverse conversion on the diagnosis response message to generate a service response; calling the front-end interaction processor to send the service response to a client; and calling the diagnosis detector interaction processor to notify the communication of an interrupt and a controller. The application can simultaneously perform remote diagnosis operation on multiple vehicles, and the maintenance cost is low.

Description

Technical Field

[0001] The embodiments of the present invention generally relate to the field of automotive electronics technology, and more specifically, to a vehicle diagnostic method, a diagnostic server, a vehicle diagnostic system, and a storage medium. Background Technology

[0002] Offboard Diagnostic Information Systems (ODIS) are widely used in pre-production vehicle manufacturing for electrical installation testing, software updates, and fault diagnosis. However, ODIS can only operate on one vehicle at a time, requires on-site operation by personnel, is difficult to maintain, and necessitates individual upgrades for each ODIS device. Summary of the Invention

[0003] To address the aforementioned problems in the prior art, in a first aspect, embodiments of the present invention provide a vehicle diagnostic method applied to a diagnostic server, wherein the diagnostic server includes a front-end interaction processor, a service processor, a protocol processor, a data processor, and a diagnostic instrument interaction processor, wherein the diagnostic instrument interaction processor is adapted to concurrently communicate with multiple vehicle diagnostic instruments via sockets and thread pools, and the data processor is adapted to communicatively connect with an open diagnostic data interaction parser. The method includes: the front-end interaction processor receiving a service request from a client and transmitting it to the service processor, wherein the service request includes a service request type and a vehicle diagnostic instrument identifier; the service processor calling the data processor to obtain communication parameter information from the open diagnostic data interaction parser and encoding the communication parameter information, and then calling the diagnostic instrument interaction processor to send the encoded communication parameter information to the vehicle diagnostic instrument corresponding to the vehicle diagnostic instrument identifier, so that the vehicle diagnostic instrument establishes communication with the controller of the vehicle to be diagnosed based on the communication parameter information; and the service processor calling the protocol processor to unify the service request. The diagnostic service protocol is converted, a diagnostic request message is generated, and the diagnostic instrument interaction processor is invoked to send the diagnostic request message to the vehicle diagnostic instrument corresponding to the vehicle diagnostic instrument identifier; the service processor invokes the diagnostic instrument interaction processor to receive the diagnostic response message sent by the vehicle diagnostic instrument; the service processor invokes the protocol processor to perform a unified diagnostic service protocol inverse conversion on the diagnostic response message to generate a service response; the service processor invokes the front-end interaction processor to send the service response to the client; the service processor invokes the diagnostic instrument interaction processor to notify the vehicle diagnostic instrument to interrupt communication with the controller of the vehicle to be diagnosed.

[0004] In some implementations, the diagnostic server further includes a configuration processor, the service request type includes a controller version verification request, and the service response includes the actual version value of the vehicle controller to be diagnosed. The method further includes: the service processor calling the configuration processor to parse the system configuration file to obtain the expected version value of the vehicle controller to be diagnosed; the service processor comparing the expected version value and the actual version value to generate a diagnostic result; and the service processor calling the front-end interaction processor to send the diagnostic result to the client.

[0005] In some implementations, the diagnostic server further includes a parsing processor, the service request type includes a vehicle controller configuration information verification request, and the service response includes the actual value of the configuration information of the vehicle controller to be diagnosed. The method further includes: the service processor calling the parsing processor to parse the controller configuration file to obtain the expected value of the configuration information of the vehicle controller to be diagnosed; the service processor comparing the expected value of the configuration information with the actual value of the configuration information to generate a diagnostic result; and the service processor calling the front-end interaction processor to send the diagnostic result to the client.

[0006] In some implementations, the service request type includes a controller configuration information write request, and the method further includes: the service processor calling the parsing processor to parse the controller configuration file and obtain controller configuration information; the service processor calling the protocol processor to perform unified diagnostic service protocol conversion on the controller configuration information, and sending the protocol-converted controller configuration information to the vehicle diagnostic instrument corresponding to the vehicle diagnostic instrument identifier via the diagnostic instrument interaction processor, so that the vehicle diagnostic instrument writes the protocol-converted controller configuration information to the vehicle controller to be diagnosed.

[0007] In some implementations, the service request type includes a vehicle controller software refresh request, and the method further includes: the service processor calling the parsing processor to parse the vehicle controller refresh software; the service processor calling the protocol processor and the diagnostic instrument interaction processor to perform a pre-refresh process, a refresh process, and a post-refresh process with the vehicle diagnostic instrument. The pre-refresh process includes the service processor calling the diagnostic instrument interaction processor to cause the vehicle diagnostic instrument to perform the following steps: causing the vehicle controller to be diagnosed to enter an extended diagnostic session; checking the refresh preset conditions of the vehicle controller to be diagnosed; disabling the diagnostic fault code reporting function of the vehicle controller to be diagnosed; and disabling non-diagnostic communication of the vehicle controller to be diagnosed. The refresh process includes the service processor calling the diagnostic instrument interaction processor to cause the vehicle diagnostic instrument to perform the following steps: causing the vehicle controller to be diagnosed to enter a refresh diagnostic session; causing the vehicle controller to be diagnosed to perform secure login; writing the vehicle controller refresh software, after protocol conversion by the protocol processor, into the vehicle controller to be diagnosed; and verifying refresh dependencies. The refresh process includes the service processor calling the diagnostic tester interaction processor to cause the vehicle diagnostic tester to perform the following: causing the vehicle controller to be diagnosed to enter an extended diagnostic session; performing a hardware restart on the vehicle controller to be diagnosed; enabling non-diagnostic communication of the vehicle controller to be diagnosed; enabling the diagnostic fault code reporting function of the vehicle controller to be diagnosed; and causing the vehicle controller to be diagnosed to enter a default diagnostic session.

[0008] In a second aspect, embodiments of the present invention provide a diagnostic server, comprising a front-end interaction processor, a service processor, a protocol processor, a data processor, and a diagnostic instrument interaction processor. The front-end interaction processor is configured to: receive a service request from a client and transmit it to the service processor, wherein the service request includes a service request type and a vehicle diagnostic instrument identifier; and, in response to a call from the service processor, send the service response to the client. The protocol processor is configured to:, in response to a call from the service processor, perform a unified diagnostic service protocol conversion on the service request to generate a diagnostic request message; and, in response to a call from the service processor, perform a unified diagnostic service protocol inverse conversion on the diagnostic response message to generate a service response. The data processor is configured to: communicatively connect to an open diagnostic data interaction parser, and, in response to a call from the service processor, obtain communication parameter information from the open diagnostic data interaction parser and encode the communication parameter information. The diagnostic instrument interaction processor is used to: communicate concurrently with multiple vehicle diagnostic instruments via sockets and thread pools; in response to the call of the service processor, send encoded communication parameter information to the vehicle diagnostic instrument corresponding to the vehicle diagnostic instrument identifier, send the diagnostic request message to the vehicle diagnostic instrument corresponding to the vehicle diagnostic instrument identifier, receive the diagnostic response message sent by the vehicle diagnostic instrument, and notify the vehicle diagnostic instrument to interrupt communication with the controller of the vehicle to be diagnosed. The service processor is configured to: call the data processor to obtain communication parameter information from the open diagnostic data interaction parser and encode the communication parameter information; then call the diagnostic instrument interaction processor to send the encoded communication parameter information to the vehicle diagnostic instrument corresponding to the vehicle diagnostic instrument identifier, so that the vehicle diagnostic instrument can establish communication with the vehicle controller to be diagnosed based on the communication parameter information; call the protocol processor to perform unified diagnostic service protocol conversion on the service request, generate a diagnostic request message, and call the diagnostic instrument interaction processor to send the diagnostic request message to the vehicle diagnostic instrument corresponding to the vehicle diagnostic instrument identifier; call the diagnostic instrument interaction processor to receive the diagnostic response message sent by the vehicle diagnostic instrument; call the protocol processor to perform unified diagnostic service protocol inverse conversion on the diagnostic response message to generate a service response; call the front-end interaction processor to send the service response to the client; and call the diagnostic instrument interaction processor to notify the vehicle diagnostic instrument to interrupt communication with the vehicle controller to be diagnosed.

[0009] In some implementations, the diagnostic server further includes a configuration processor, the service request type includes a controller version verification request, and the service response includes the actual version value of the vehicle controller to be diagnosed. The configuration processor is configured to: parse a system configuration file in response to a call from the service processor to obtain the expected version value of the vehicle controller to be diagnosed. The service processor is further configured to: call the configuration processor to parse the system configuration file to obtain the expected version value of the vehicle controller to be diagnosed; compare the expected version value with the actual version value to generate a diagnostic result; and call the front-end interaction processor to send the diagnostic result to the client.

[0010] In some implementations, the diagnostic server further includes a parsing processor, the service request type includes a vehicle controller configuration information verification request, and the service response includes the actual value of the configuration information of the vehicle controller to be diagnosed. The parsing processor is configured to: parse the controller configuration file in response to the call from the service processor to obtain the expected value of the configuration information of the vehicle controller to be diagnosed. The service processor is further configured to: call the parsing processor to parse the controller configuration file to obtain the expected value of the configuration information of the vehicle controller to be diagnosed; compare the expected value of the configuration information with the actual value of the configuration information to generate a diagnostic result; and call the front-end interaction processor to send the diagnostic result to the client.

[0011] In a third aspect, embodiments of the present invention provide a vehicle diagnostic system, the system comprising a client, a diagnostic server, an open diagnostic data interaction parser, and a vehicle diagnostic instrument, wherein the diagnostic server includes a front-end interaction processor, a service processor, a protocol processor, a data processor, and a diagnostic instrument interaction processor. The client is configured to: send a service request to the front-end interaction processor and receive a service response from the front-end interaction processor. The front-end interaction processor is configured to: receive a service request from the client and transmit it to the service processor, wherein the service request includes a service request type and a vehicle diagnostic instrument identifier; and, in response to a call from the service processor, send the service response to the client. The protocol processor is configured to:, in response to a call from the service processor, perform a unified diagnostic service protocol conversion on the service request to generate a diagnostic request message; and, in response to a call from the service processor, perform a unified diagnostic service protocol inverse conversion on the diagnostic response message to generate a service response. The data processor is configured to: communicatively connect to the open diagnostic data interaction parser, and, in response to a call from the service processor, obtain communication parameter information from the open diagnostic data interaction parser and encode the communication parameter information. The diagnostic instrument interaction processor is used to: communicate concurrently with multiple vehicle diagnostic instruments via sockets and thread pools; in response to the call of the service processor, send encoded communication parameter information to the vehicle diagnostic instrument corresponding to the vehicle diagnostic instrument identifier, send the diagnostic request message to the vehicle diagnostic instrument corresponding to the vehicle diagnostic instrument identifier, receive the diagnostic response message sent by the vehicle diagnostic instrument, and notify the vehicle diagnostic instrument to interrupt communication with the controller of the vehicle to be diagnosed. The service processor is configured to: call the data processor to obtain communication parameter information from the open diagnostic data interaction parser and encode the communication parameter information; then call the diagnostic instrument interaction processor to send the encoded communication parameter information to the vehicle diagnostic instrument corresponding to the vehicle diagnostic instrument identifier; call the protocol processor to perform unified diagnostic service protocol conversion on the service request, generate a diagnostic request message, and call the diagnostic instrument interaction processor to send the diagnostic request message to the vehicle diagnostic instrument corresponding to the vehicle diagnostic instrument identifier; call the diagnostic instrument interaction processor to receive the diagnostic response message sent by the vehicle diagnostic instrument; call the protocol processor to perform unified diagnostic service protocol inverse conversion on the diagnostic response message to generate a service response; call the front-end interaction processor to send the service response to the client; and call the diagnostic instrument interaction processor to notify the vehicle diagnostic instrument to interrupt communication with the controller of the vehicle to be diagnosed.The vehicle diagnostic instrument is configured to: receive communication parameter information from the diagnostic instrument interaction processor and establish communication with the vehicle controller to be diagnosed based on the communication parameter information; receive a diagnostic request message from the diagnostic instrument interaction processor and transmit it to the vehicle controller to be diagnosed; receive a diagnostic response message from the vehicle controller to be diagnosed and transmit it to the diagnostic instrument interaction processor; and interrupt communication with the vehicle controller to be diagnosed based on an interrupt communication notification from the diagnostic instrument interaction processor.

[0012] In a fourth aspect, embodiments of the present invention provide a storage medium storing computer-readable instructions that, when executed by a processor, perform the vehicle diagnostic method according to any of the above embodiments.

[0013] The vehicle diagnostic method, diagnostic server, vehicle diagnostic system, and storage medium proposed in this invention overcome the shortcomings of the prior art. Utilizing Socket and multithreading technologies, it implements an online automotive electrical diagnostic system capable of simultaneously remotely operating multiple vehicles. It features low maintenance costs, strong scalability, and easy upgrades. It can perform remote diagnostic operations on multiple vehicles simultaneously. Attached Figure Description

[0014] The above and other objects, features, and advantages of embodiments of the present invention will become readily apparent from the following detailed description taken in conjunction with the accompanying drawings. Several embodiments of the invention are illustrated in the drawings by way of example and not limitation, wherein:

[0015] Figure 1 A flowchart of a vehicle diagnostic method according to an embodiment of the present invention is shown;

[0016] Figure 2 A block diagram of a vehicle diagnostic system according to an embodiment of the present invention is shown;

[0017] Figure 3 A block diagram of a first example of a diagnostic server according to an embodiment of the present invention is shown;

[0018] Figure 4 A block diagram of a second example of a diagnostic server according to an embodiment of the present invention is shown;

[0019] Figure 5 A block diagram of a third example of a diagnostic server according to an embodiment of the present invention is shown;

[0020] Figure 6 A flowchart of a software refresh process according to an embodiment of the present invention is shown.

[0021] In the accompanying drawings, the same or corresponding reference numerals indicate the same or corresponding parts. Detailed Implementation

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

[0023] In one aspect, embodiments of the present invention provide a vehicle diagnostic method, a diagnostic server, and a vehicle diagnostic system, wherein the vehicle diagnostic method is applied to the diagnostic server. (See reference) Figures 1-3 ,in, Figure 1 A flowchart of a vehicle diagnostic method according to an embodiment of the present invention is shown; Figure 2 A block diagram of a vehicle diagnostic system according to an embodiment of the present invention is shown; Figure 3 A block diagram of a first example of a diagnostic server according to an embodiment of the present invention is shown.

[0024] The vehicle diagnostic method according to an embodiment of the present invention will be described below in conjunction with the architecture of the vehicle diagnostic system and diagnostic server according to an embodiment of the present invention.

[0025] like Figure 2 As shown, the vehicle diagnostic system according to an embodiment of the present invention includes a client, a diagnostic server, an Open Diagnostic Data Exchange (ODX) parser, and a vehicle diagnostic instrument. As an example, the client and the diagnostic server can communicate based on the Hypertext Transfer Protocol (HTTP), and the diagnostic server and the vehicle diagnostic instrument can communicate via WiFi. The ODX parser can be deployed on the server side along with the diagnostic server, or it can be deployed on other entities, as long as the diagnostic server can call the ODX parser.

[0026] The client can be used to send business requests to the front-end interaction processor and receive business responses from it. In other words, the client is responsible for sending requests to the diagnostic server and displaying the responses returned by the diagnostic server. This functionality can be achieved through a front-end web page running on the client. As an example, the client's front-end page can be developed using JS, HTML, and CSS; for instance, JS handles the logic calculations, while HTML and CSS are used for rendering and generating the browsing interface.

[0027] A diagnostic server can be a Modular Vehicle Communication Interface (MVCI) diagnostic server. Generally, a diagnostic server is responsible for connecting other software components and handling system business processes. As an example, a diagnostic server can be developed using Java, Tomcat, or MySQL.

[0028] An ODX parser can be used to parse ODX files (collections of XML files) to provide parameter information needed for server diagnostics. As an example only, an ODX parser can be developed using Java tools.

[0029] The vehicle diagnostic tool can be an MVCI vehicle diagnostic tool. For example, it can connect to the vehicle via an On-Board Diagnostics (OBD) interface, connect to a diagnostic server via Wi-Fi, and convert between the Transmission Control Protocol / Internet Protocol (TCP / IP) stack and the Controller Area Network (CAN) stack. As an example, it can be developed using the C programming language.

[0030] like Figure 3 As shown, a first example of a diagnostic server according to an embodiment of the present invention includes a Servlet Processor, a Job Processor, a Protocol Processor, a Data Processor, and a Dongle Processor. The Dongle Processor is adapted to communicate concurrently with multiple vehicle diagnostic instruments via sockets and a thread pool. The Data Processor is adapted to be communicatively connected to an Open Diagnostic Data Interaction Parser (ODX Parser).

[0031] The Servlet Processor is the sole interface for interacting with the client's front-end webpage. It receives business requests from the front-end webpage and returns the business results to the front-end webpage.

[0032] The Job Processor is responsible for executing business processes, such as installation and testing, and breaking down business processes; and calling other processors to perform tasks.

[0033] The Protocol Processor is responsible for generating Unified Diagnostic Services (UDS) protocol request messages and analyzing UDS protocol response messages, specifically converting text requests into binary streams and vice versa; it also invokes the Dongle Processor to communicate with the vehicle diagnostic instrument. This module can be accessed by the Job Processor.

[0034] The Data Processor obtains parameter information by calling functions of the ODX parser and encodes the obtained parameter information. This module can be accessed by the Protocol Processor and the Job Processor.

[0035] The Dongle Processor enables concurrent communication with multiple vehicle diagnostic tools (such as the MVCI vehicle diagnostic tool) via sockets and thread pools. This module can be accessed by both the Protocol Processor and the Job Processor.

[0036] After receiving a business request from a client, the Servlet Processor calls the corresponding Job Processor to process the request and returns the result to the client. Depending on the type of business, the Job Processor may perform operations such as: calling the parsing processor to parse the ODX file to obtain the required communication parameters, and performing diagnostic tests on the vehicle controller (also known as the Electronic Control Unit, ECU).

[0037] like Figure 1 As shown, the method according to an embodiment of the present invention includes steps S101-S107.

[0038] In step S101, the front-end interaction processor receives a service request from the client and transmits it to the service processor, wherein the service request includes a service request type and a vehicle diagnostic instrument identifier.

[0039] In step S102, the business processor calls the data processor to obtain communication parameter information from the open diagnostic data interaction parser and encodes the communication parameter information. Then, it calls the diagnostic instrument interaction processor to send the encoded communication parameter information to the vehicle diagnostic instrument corresponding to the vehicle diagnostic instrument identifier and configure the vehicle diagnostic instrument so that the vehicle diagnostic instrument can establish communication with the controller of the vehicle to be diagnosed according to the communication parameter information.

[0040] In step S103, the service processor calls the protocol processor to perform unified diagnostic service protocol conversion on the service request, generating a diagnostic request message, for example, converting the text request into a binary code stream, and then calls the diagnostic instrument interaction processor to send the diagnostic request message to the vehicle diagnostic instrument corresponding to the vehicle diagnostic instrument identifier. Subsequently, the vehicle diagnostic instrument can send the diagnostic request message to the controller of the vehicle to be diagnosed.

[0041] In step S104, the business processor calls the diagnostic instrument interaction processor to receive the diagnostic response message (e.g., binary code stream) sent by the vehicle diagnostic instrument.

[0042] In step S105, the service processor calls the protocol processor to perform a unified diagnostic service protocol inverse conversion on the diagnostic response message, for example, converting the binary code stream into a text response to generate a service response.

[0043] In step S106, the business processor calls the front-end interaction processor to send the business response to the client.

[0044] In step S107, after the detection and diagnosis are completed, the business processor calls the diagnostic tester interaction processor to notify the vehicle diagnostic tester to interrupt communication with the controller of the vehicle to be diagnosed.

[0045] This implementation is described from the perspective of the diagnostic server. The functions of the front-end interaction processor, business processor, protocol processor, data processor, and diagnostic instrument interaction processor are as follows.

[0046] The front-end interaction processor is used to: receive business requests from the client and transmit them to the business processor, wherein the business request includes a business request type and a vehicle diagnostic instrument identifier; and send a business response to the client in response to a call from the business processor.

[0047] The protocol processor is used to: convert business requests into a unified diagnostic service protocol in response to a call from a business processor, generating a diagnostic request message; and to convert diagnostic response messages into a unified diagnostic service protocol in response to a call from a business processor, generating a business response.

[0048] The data processor is used to: communicatively connect to the open diagnostic data interaction parser, and in response to calls from the business processor, retrieve communication parameter information from the open diagnostic data interaction parser and encode the communication parameter information.

[0049] The diagnostic instrument interaction processor is used to: communicate concurrently with multiple vehicle diagnostic instruments via sockets and thread pools; in response to calls from the business processor, send encoded communication parameter information to the vehicle diagnostic instrument corresponding to the vehicle diagnostic instrument identifier, send diagnostic request messages to the vehicle diagnostic instrument corresponding to the vehicle diagnostic instrument identifier, receive diagnostic response messages sent by the vehicle diagnostic instrument, and notify the vehicle diagnostic instrument to interrupt communication with the controller of the vehicle to be diagnosed.

[0050] The business processor is used for:

[0051] The data processor is invoked to obtain communication parameter information from the open diagnostic data interaction parser and encode the communication parameter information. Then, the diagnostic instrument interaction processor is invoked to send the encoded communication parameter information to the vehicle diagnostic instrument corresponding to the vehicle diagnostic instrument identifier, so that the vehicle diagnostic instrument can establish communication with the controller of the vehicle to be diagnosed based on the communication parameter information.

[0052] The protocol processor is invoked to convert the business request into a unified diagnostic service protocol, generate a diagnostic request message, and then the diagnostic instrument interaction processor is invoked to send the diagnostic request message to the vehicle diagnostic instrument corresponding to the vehicle diagnostic instrument identifier.

[0053] The diagnostic instrument's interactive processor is invoked to receive diagnostic response messages sent by the vehicle's diagnostic instrument.

[0054] The protocol processor performs a reverse conversion of the diagnostic response message using the unified diagnostic service protocol to generate a business response.

[0055] The front-end interaction handler is invoked to send the business response to the client.

[0056] The diagnostic tester's interactive processor is invoked to notify the vehicle diagnostic tester to interrupt communication with the controller of the vehicle to be diagnosed.

[0057] exist Figure 2 In the system shown, the vehicle diagnostic instrument is used to: receive communication parameter information from the diagnostic instrument interaction processor and establish communication with the vehicle controller to be diagnosed based on the communication parameter information; receive diagnostic request messages from the diagnostic instrument interaction processor and transmit them to the vehicle controller to be diagnosed; receive diagnostic response messages from the vehicle controller to be diagnosed and transmit them to the diagnostic instrument interaction processor; and interrupt communication with the vehicle controller to be diagnosed based on the interrupt communication notification from the diagnostic instrument interaction processor.

[0058] refer to Figure 4 This illustrates a block diagram of a second example of a diagnostic server according to an embodiment of the present invention. As one embodiment of the invention, such as... Figure 4 As shown, the diagnostic server also includes a configuration processor. The service request type includes a controller version verification request, and the service response includes the actual version value of the controller of the vehicle to be diagnosed. The controller version may include information such as the controller part number, controller hardware version number, and controller software version number. In this embodiment, the configuration of the diagnostic server can realize the controller installation and testing process.

[0059] In this embodiment, the vehicle diagnostic method further includes:

[0060] The business processor calls the configuration processor to parse the system configuration file and obtain the expected version value of the vehicle controller to be diagnosed, such as the expected values ​​of the controller part number, controller hardware version number and controller software version number.

[0061] The protocol processor interacts with the controller of the vehicle to be diagnosed via the UDS protocol to obtain the actual values ​​of the part number, hardware version number and software version number of the controller of the vehicle to be diagnosed. This step is the same as steps S103-S105 in the above implementation, the only difference being the content included in the returned diagnostic response message.

[0062] The business processor compares the expected version value with the actual version value to generate diagnostic results.

[0063] The business processor calls the front-end interaction processor to send the diagnostic results to the client.

[0064] This implementation is described from the perspective of the diagnostic server. The configuration processor is used to: parse the system configuration file in response to a call from the business processor to obtain the expected version value of the vehicle controller to be diagnosed. The business processor is also used to: call the configuration processor to parse the system configuration file to obtain the expected version value of the vehicle controller to be diagnosed; compare the expected version value with the actual version value to generate a diagnostic result; and call the front-end interaction processor to send the diagnostic result to the client.

[0065] refer to Figure 5 This illustrates a block diagram of a third example of a diagnostic server according to an embodiment of the present invention. As one embodiment of the present invention, such as... Figure 5 As shown, the diagnostic server also includes a parsing processor. The service request type includes a vehicle controller configuration information verification request, and the service response includes the actual values ​​of the configuration information of the vehicle controller to be diagnosed. The vehicle controller configuration information may include information such as the configuration file part number, configuration file version number, and configuration data.

[0066] In this implementation, the configuration of the diagnostic server can realize the controller configuration information detection (controller configuration data verification) process.

[0067] In this embodiment, the vehicle diagnostic method may further include:

[0068] The business processor calls the parser to parse the controller configuration file (e.g., ZDC file) and obtain the expected values ​​of the configuration information of the controller of the vehicle to be diagnosed. For example, it may include the controller configuration file part number, controller configuration file version number and expected values ​​of configuration data.

[0069] The protocol processor interacts with the vehicle controller via the UDS protocol to obtain the controller configuration file part number, controller configuration file version number, and actual values ​​of configuration data. This step is the same as steps S103-S105 in the above implementation, except that the returned diagnostic response message includes the following content.

[0070] The business processor compares the expected values ​​of the configuration information with the actual values ​​of the configuration information to generate diagnostic results.

[0071] The business processor calls the front-end interaction processor to send the diagnostic results to the client.

[0072] This implementation is described from the perspective of the diagnostic server. The parsing processor is used to: parse the controller configuration file in response to a call from the business processor to obtain the expected configuration information values ​​of the vehicle controller to be diagnosed. The business processor is also used to: call the parsing processor to parse the controller configuration file to obtain the expected configuration information values ​​of the vehicle controller to be diagnosed; compare the expected configuration information values ​​with the actual configuration information values ​​to generate a diagnostic result; and call the front-end interaction processor to send the diagnostic result to the client.

[0073] The above configuration of the business processor can also realize processes such as writing controller configuration files (e.g., ZDC files) and refreshing controller software.

[0074] During the controller configuration data writing process, the business request type includes a controller configuration information write request, and the controller configuration data writing process can include:

[0075] The business processor calls the parser to parse the controller configuration file (e.g., ZDC file) and obtain controller configuration information, which may include the controller configuration file part number, controller configuration file version number, and configuration data.

[0076] The business processor calls the protocol processor to perform Unified Diagnostic Service (UDS) protocol conversion on the controller configuration information, and sends the protocol-converted controller configuration information to the vehicle diagnostic instrument corresponding to the vehicle diagnostic instrument identifier via the diagnostic instrument interaction processor, so that the vehicle diagnostic instrument can write the protocol-converted controller configuration information into the controller of the vehicle to be diagnosed.

[0077] Optionally, the controller configuration data writing results can be received from the vehicle diagnostic tester and sent to the client via the front-end interaction processor.

[0078] As one embodiment of the present invention, the service request type includes a vehicle controller software refresh request. (See reference...) Figure 6 The document illustrates a flowchart of a software refresh process according to an embodiment of the present invention. In this business scenario, the vehicle diagnostic method may further include: a business processor invoking a parsing processor to parse the vehicle controller refresh software; and the business processor invoking a protocol processor and a diagnostic instrument interaction processor to perform a pre-programming process, a programming process, and a post-programming process with the vehicle diagnostic instrument.

[0079] like Figure 6 As shown, the pre-flash process is responsible for preparing the vehicle network before the software flash, including the business processor calling the diagnostic tool interaction processor to cause the vehicle diagnostic tool to perform the following steps:

[0080] This allows the vehicle controller to enter an extended diagnostic session. It should be noted that the vehicle controller has different permissions in different sessions, including the default diagnostic session, the extended diagnostic session, and the programming diagnostic session.

[0081] Check the refresh preset conditions of the vehicle controller to be diagnosed. This process is an internal routine of the vehicle controller. Here, it is only necessary to start the routine.

[0082] Disable the Diagnostic Trouble Code (DTC) reporting function for the vehicle controller under test. Reporting diagnostic fault codes is meaningless during software refresh; and

[0083] Disable non-diagnostic communication for the vehicle controller to be diagnosed. Apart from the diagnostic communication required for software updates, other business communications are meaningless and will increase the burden on the ECU.

[0084] like Figure 6 As shown, the refresh process is responsible for implementing software refresh, i.e., downloading the application and data, including the business processor calling the diagnostic instrument interaction processor to cause the vehicle diagnostic instrument to perform the following steps:

[0085] This causes the controller of the vehicle to be diagnosed to enter a refresh diagnostic session;

[0086] This enables secure login to the controller of the vehicle to be diagnosed, for example, by using dynamic passwords for permission verification to prevent incorrect or malicious refreshes.

[0087] The vehicle controller refresh software, after protocol conversion by the protocol processor, is written to the vehicle controller to be diagnosed. At this point, the vehicle controller begins downloading the program and data; and

[0088] Check refresh (program) dependencies.

[0089] The steps for downloading programs and data further include: erasing memory; requesting a supported data packet size; transmitting data; determining whether the transmission is complete, and if so, ending the data transmission and checking the memory; otherwise, continuing the data transmission.

[0090] like Figure 6 As shown, the refresh process is responsible for restoring the vehicle network after the software refresh, including the business processor calling the diagnostic tool interaction processor to enable the vehicle diagnostic tool to execute:

[0091] This causes the controller of the vehicle to be diagnosed to enter an extended diagnostic session;

[0092] Perform a hardware reboot on the vehicle controller to be diagnosed so that the new software can function properly;

[0093] Enable non-diagnostic communication for the vehicle controller to be diagnosed, thereby restoring other service communications;

[0094] Enable the diagnostic fault code reporting function of the vehicle controller to be diagnosed, thereby restoring the diagnostic fault code reporting function;

[0095] This causes the controller of the vehicle to be diagnosed to enter the default diagnostic session.

[0096] After the refresh is complete, the software refresh result can be returned to the front-end interaction processor, which will then send the refresh result to the client.

[0097] In another aspect, embodiments of the present invention also provide a storage medium storing computer-readable instructions that, when executed by a processor, perform the vehicle diagnostic method described according to any of the above embodiments.

[0098] The vehicle diagnostic method, diagnostic server, vehicle diagnostic system, and storage medium proposed in this invention overcome the shortcomings of the prior art. Utilizing Socket and multithreading technologies, it implements an online automotive electrical diagnostic system capable of simultaneously remotely operating multiple vehicles. It features low maintenance costs, strong scalability, and easy upgrades. It can perform remote diagnostic operations on multiple vehicles simultaneously.

[0099] The foregoing description of embodiments of the invention has been given for illustrative purposes and is not exhaustive, nor is it intended to limit the invention to the exact forms disclosed. Those skilled in the art will understand that various changes can be made without departing from the scope of the invention, and elements therein can be substituted with equivalents. Furthermore, many modifications can be made to adapt particular situations or materials to the teachings of the invention without departing from the basic scope of the invention. Therefore, the invention is not intended to be limited to the specific embodiments disclosed as the best mode contemplated for carrying out the invention; the invention will include all embodiments falling within the scope of the appended claims.

Claims

1. A vehicle diagnostic method, characterized in that, The method is applied to a diagnostic server, which includes a front-end interaction processor, a business processor, a protocol processor, a data processor, a diagnostic instrument interaction processor, and a parsing processor. The diagnostic instrument interaction processor is adapted to communicate concurrently with multiple vehicle diagnostic instruments via sockets and a thread pool. The data processor is adapted to communicatively connect to an open diagnostic data interaction parser. The method includes: The front-end interaction processor receives a service request from the client and transmits it to the service processor. The service request includes a service request type and a vehicle diagnostic tester identifier. The service request type includes a vehicle controller configuration information verification request. The business processor calls the data processor to obtain communication parameter information from the open diagnostic data interaction parser and encodes the communication parameter information. Then, the diagnostic instrument interaction processor calls the diagnostic instrument interaction processor to send the encoded communication parameter information to the vehicle diagnostic instrument corresponding to the vehicle diagnostic instrument identifier, so that the vehicle diagnostic instrument can establish communication with the controller of the vehicle to be diagnosed according to the communication parameter information. The service processor calls the protocol processor to convert the service request into a unified diagnostic service protocol, generate a diagnostic request message, and calls the diagnostic instrument interaction processor to send the diagnostic request message to the vehicle diagnostic instrument corresponding to the vehicle diagnostic instrument identifier. The business processor calls the diagnostic instrument interaction processor to receive the diagnostic response message sent by the vehicle diagnostic instrument; The service processor calls the protocol processor to perform a unified diagnostic service protocol inverse conversion on the diagnostic response message to generate a service response, which includes the actual value of the configuration information of the vehicle controller to be diagnosed. The business processor invokes the front-end interaction processor to send the business response to the client; The business processor calls the diagnostic instrument interaction processor to notify the vehicle diagnostic instrument to interrupt communication with the controller of the vehicle to be diagnosed; The business processor calls the parsing processor to parse the controller configuration file and obtain the expected configuration information of the vehicle controller to be diagnosed. The service processor compares the expected value of the configuration information with the actual value of the configuration information to generate a diagnostic result. The business processor calls the front-end interaction processor to send the diagnostic results to the client.

2. The method according to claim 1, characterized in that, The diagnostic server also includes a configuration processor, the service request type includes a controller version verification request, and the service response includes the actual version value of the vehicle controller to be diagnosed. The method further includes: The business processor calls the configuration processor to parse the system configuration file and obtain the expected version value of the vehicle controller to be diagnosed; The business processor compares the expected value of the version with the actual value of the version to generate a diagnostic result; The business processor calls the front-end interaction processor to send the diagnostic results to the client.

3. The method according to claim 1, characterized in that, The business request type includes a controller configuration information write request, and the method further includes: The service processor calls the parsing processor to parse the controller configuration file and obtain the controller configuration information; The service processor calls the protocol processor to perform unified diagnostic service protocol conversion on the controller configuration information, and sends the protocol-converted controller configuration information to the vehicle diagnostic instrument corresponding to the vehicle diagnostic instrument identifier via the diagnostic instrument interaction processor, so that the vehicle diagnostic instrument writes the protocol-converted controller configuration information into the vehicle controller to be diagnosed.

4. The method according to claim 1, characterized in that, The service request type includes a vehicle controller software refresh request, and the method further includes: The business processor calls the parsing processor to parse the vehicle controller refresh software; The service processor invokes the protocol processor and the diagnostic instrument interaction processor to perform the pre-refresh process, the refresh process, and the post-refresh process with the vehicle diagnostic instrument, wherein... The pre-refresh process includes the business processor calling the diagnostic instrument interaction processor to cause the vehicle diagnostic instrument to perform the following steps: This causes the vehicle controller to enter an extended diagnostic session; Check the refresh preset conditions of the vehicle controller to be diagnosed; Disable the diagnostic fault code reporting function of the vehicle controller to be diagnosed; and Enable non-diagnostic communication for the vehicle controller to be diagnosed. The refresh process includes the business processor invoking the diagnostic instrument interaction processor to cause the vehicle diagnostic instrument to perform the following steps: This causes the vehicle controller to enter a refresh diagnostic session; Enables the controller of the vehicle to be diagnosed to log in securely; The vehicle controller refresh software, after protocol conversion by the protocol processor, is written into the vehicle controller to be diagnosed; and Check refresh dependencies. The refresh process includes the business processor invoking the diagnostic instrument interaction processor to cause the vehicle diagnostic instrument to execute: This causes the vehicle controller to enter an extended diagnostic session; Perform a hardware reboot on the vehicle controller to be diagnosed; Enable non-diagnostic communication for the vehicle controller to be diagnosed; Enable the diagnostic fault code reporting function of the vehicle controller to be diagnosed; This causes the vehicle controller to enter the default diagnostic session.

5. A diagnostic server, characterized in that, The diagnostic server includes a front-end interaction processor, a business processor, a protocol processor, a data processor, a diagnostic instrument interaction processor, and a parsing processor. The front-end interaction processor is used to: receive a service request from the client and transmit it to the service processor, wherein the service request includes a service request type and a vehicle diagnostic tester identifier, and the service request type includes a vehicle controller configuration information verification request. In addition, in response to the call of the service processor, a service response is sent to the client, the service response including the actual value of the configuration information of the vehicle controller to be diagnosed; The protocol processor is configured to: in response to a call from the service processor, perform a unified diagnostic service protocol conversion on the service request to generate a diagnostic request message; and in response to a call from the service processor, perform a unified diagnostic service protocol inverse conversion on the diagnostic response message to generate a service response. The data processor is configured to: communicatively connect to an open diagnostic data interaction parser, and in response to a call from the service processor, obtain communication parameter information from the open diagnostic data interaction parser and encode the communication parameter information; The diagnostic instrument interaction processor is used to: communicate concurrently with multiple vehicle diagnostic instruments via sockets and thread pools; in response to the call of the service processor, send encoded communication parameter information to the vehicle diagnostic instrument corresponding to the vehicle diagnostic instrument identifier, send the diagnostic request message to the vehicle diagnostic instrument corresponding to the vehicle diagnostic instrument identifier, receive the diagnostic response message sent by the vehicle diagnostic instrument, and notify the vehicle diagnostic instrument to interrupt communication with the controller of the vehicle to be diagnosed. The service processor is used for: The data processor is invoked to obtain communication parameter information from the open diagnostic data interaction parser and encode the communication parameter information. Then, the diagnostic instrument interaction processor is invoked to send the encoded communication parameter information to the vehicle diagnostic instrument corresponding to the vehicle diagnostic instrument identifier, so that the vehicle diagnostic instrument can establish communication with the controller of the vehicle to be diagnosed according to the communication parameter information. The protocol processor is invoked to convert the service request into a unified diagnostic service protocol, generate a diagnostic request message, and the diagnostic instrument interaction processor is invoked to send the diagnostic request message to the vehicle diagnostic instrument corresponding to the vehicle diagnostic instrument identifier. The diagnostic instrument's interactive processor is invoked to receive the diagnostic response message sent by the vehicle diagnostic instrument; The protocol processor is invoked to perform a reverse conversion of the diagnostic response message using the unified diagnostic service protocol to generate a business response. The front-end interaction processor is invoked to send the business response to the client; The diagnostic instrument's interactive processor is invoked to notify the vehicle diagnostic instrument to interrupt communication with the controller of the vehicle to be diagnosed; The parsing processor is invoked to parse the controller configuration file and obtain the expected configuration information of the controller of the vehicle to be diagnosed. The expected value of the configuration information is compared with the actual value of the configuration information to generate a diagnostic result; The front-end interaction processor is invoked to send the diagnostic results to the client; The parsing processor is used to: parse the controller configuration file in response to the call of the business processor, and obtain the expected value of the configuration information of the vehicle controller to be diagnosed.

6. The diagnostic server according to claim 5, characterized in that, The diagnostic server also includes a configuration processor, the service request type includes a controller version verification request, and the service response includes the actual version value of the vehicle controller to be diagnosed. The configuration processor is used to: parse the system configuration file in response to the call of the service processor, and obtain the expected version value of the vehicle controller to be diagnosed; The service processor is also used for: The configuration processor is invoked to parse the system configuration file and obtain the expected version value of the vehicle controller to be diagnosed. The expected value of the version is compared with the actual value of the version to generate a diagnostic result; The front-end interaction processor is invoked to send the diagnostic results to the client.

7. A vehicle diagnostic system, characterized in that, The system includes a client, a diagnostic server, an open diagnostic data interaction parser, and a vehicle diagnostic testing instrument. The diagnostic server includes a front-end interaction processor, a business processor, a protocol processor, a data processor, a diagnostic testing instrument interaction processor, and a parsing processor. The client is used to: send service requests to the front-end interaction processor and receive service responses from the front-end interaction processor; The front-end interaction processor is configured to: receive a service request from the client and transmit it to the service processor, wherein the service request includes a service request type and a vehicle diagnostic tester identifier, and the service request type includes a vehicle controller configuration information verification request; and, in response to a call from the service processor, send a service response to the client, wherein the service response includes the actual value of the configuration information of the vehicle controller to be diagnosed. The protocol processor is configured to: in response to a call from the service processor, perform a unified diagnostic service protocol conversion on the service request to generate a diagnostic request message; and in response to a call from the service processor, perform a unified diagnostic service protocol inverse conversion on the diagnostic response message to generate a service response. The data processor is configured to: communicatively connect to an open diagnostic data interaction parser, and in response to a call from the service processor, obtain communication parameter information from the open diagnostic data interaction parser and encode the communication parameter information; The diagnostic instrument interaction processor is used to: communicate concurrently with multiple vehicle diagnostic instruments via sockets and thread pools; in response to the call of the service processor, send encoded communication parameter information to the vehicle diagnostic instrument corresponding to the vehicle diagnostic instrument identifier, send the diagnostic request message to the vehicle diagnostic instrument corresponding to the vehicle diagnostic instrument identifier, receive the diagnostic response message sent by the vehicle diagnostic instrument, and notify the vehicle diagnostic instrument to interrupt communication with the controller of the vehicle to be diagnosed. The service processor is used for: The data processor is invoked to obtain communication parameter information from the open diagnostic data interaction parser and encode the communication parameter information. Then, the diagnostic instrument interaction processor is invoked to send the encoded communication parameter information to the vehicle diagnostic instrument corresponding to the vehicle diagnostic instrument identifier. The protocol processor is invoked to convert the service request into a unified diagnostic service protocol, generate a diagnostic request message, and the diagnostic instrument interaction processor is invoked to send the diagnostic request message to the vehicle diagnostic instrument corresponding to the vehicle diagnostic instrument identifier. The diagnostic instrument's interactive processor is invoked to receive the diagnostic response message sent by the vehicle diagnostic instrument; The protocol processor is invoked to perform a reverse conversion of the diagnostic response message using the unified diagnostic service protocol to generate a business response. The front-end interaction processor is invoked to send the business response to the client; The diagnostic instrument's interactive processor is invoked to notify the vehicle diagnostic instrument to interrupt communication with the controller of the vehicle to be diagnosed; The parsing processor is invoked to parse the controller configuration file and obtain the expected configuration information of the controller of the vehicle to be diagnosed. The expected value of the configuration information is compared with the actual value of the configuration information to generate a diagnostic result; The front-end interaction processor is invoked to send the diagnostic results to the client; The parsing processor is used to: parse the controller configuration file in response to the call of the business processor, and obtain the expected value of the configuration information of the vehicle controller to be diagnosed; The vehicle diagnostic instrument is configured to: receive communication parameter information from the diagnostic instrument interaction processor and establish communication with the vehicle controller to be diagnosed based on the communication parameter information; receive a diagnostic request message from the diagnostic instrument interaction processor and transmit it to the vehicle controller to be diagnosed; receive a diagnostic response message from the vehicle controller to be diagnosed and transmit it to the diagnostic instrument interaction processor; and interrupt communication with the vehicle controller to be diagnosed based on an interrupt communication notification from the diagnostic instrument interaction processor.

8. A storage medium storing computer-readable instructions that, when executed by a processor, perform the method according to any one of claims 1-4.

Images