Remote diagnostic method and device based on vehicle ISO9141-2 protocol

Abstract

This application provides a remote diagnostic method and apparatus based on the vehicle ISO9141-2 protocol. The method includes: acquiring diagnostic address data of a diagnostic instrument and recording the diagnostic address data to obtain a first data record; sending a first network command to a vehicle connector; acquiring vehicle response data of a target vehicle; recording the vehicle response data to obtain a second data record; sending a second network command to a device connector; performing initialization of the ISO9141-2 protocol between the device connector and the diagnostic instrument, and initialization of the ISO9141-2 protocol between the vehicle connector and the target vehicle, based on the first and second data records; and performing remote diagnostics on the target vehicle to obtain a target diagnostic result. By automating the initialization process of the diagnostic protocol and performing remote diagnostics on the vehicle, the efficiency and accuracy of remote diagnostics can be improved.

Description

Technical Field

[0001] This application relates to the field of vehicle diagnostic technology, and in particular to a remote diagnostic method and device based on the vehicle ISO9141-2 protocol. Background Technology

[0002] Traditional vehicle diagnostics typically require taking the vehicle to a repair shop and using a diagnostic tool connected via a physical link. However, when a vehicle is in a remote area or is immobilized due to a malfunction, remote diagnostic technology is needed. But current remote diagnostic processes can suffer from significant network latency, reducing efficiency and accuracy.

[0003] Therefore, improving the efficiency and accuracy of remote diagnosis is an urgent issue that needs to be addressed. Summary of the Invention

[0004] This application provides a remote diagnostic method and apparatus based on the vehicle ISO9141-2 protocol. By automating the initialization process of the diagnostic protocol and performing remote diagnostics on the vehicle, it not only improves the reliability of data transmission and the overall efficiency of remote diagnostics, but also makes the remote diagnostic results of the vehicle more accurate.

[0005] In a first aspect, embodiments of this application provide a remote diagnostic method based on the vehicle ISO9141-2 protocol, applied to a server of a remote diagnostic system. The remote diagnostic system further includes a target vehicle, a vehicle connector, a device connector, and a diagnostic instrument. The target vehicle is connected to the vehicle connector via a first K-line, and the diagnostic instrument is connected to the device connector via a second K-line. The vehicle connector and the device connector are communicatively connected to the server. The method includes:

[0006] The diagnostic address data of the diagnostic instrument is obtained and recorded to obtain the first data record;

[0007] A first network command is sent to the vehicle connector; the first network command includes the first data record; the vehicle connector is used to send the first data record in the first network command to the target vehicle.

[0008] Obtain vehicle response data of the target vehicle; the vehicle response data is the response data generated by the target vehicle in response to the first data record;

[0009] The vehicle response data is recorded to obtain a second data record;

[0010] A second network command is sent to the device connector; the second network command includes the second data record; the device connector is used to send the second data record in the second network command to the diagnostic instrument.

[0011] The initialization of the ISO9141-2 protocol between the device connector and the diagnostic instrument, and the initialization of the ISO9141-2 protocol between the vehicle connector and the target vehicle are performed according to the first data record and the second data record.

[0012] The target vehicle is remotely diagnosed to obtain the target diagnosis results.

[0013] Secondly, embodiments of this application provide a remote diagnostic device based on the vehicle ISO9141-2 protocol, applied to a server of a remote diagnostic system. The remote diagnostic system further includes a target vehicle, a vehicle connector, a device connector, and a diagnostic instrument. The target vehicle is connected to the vehicle connector via a first K-line, and the diagnostic instrument is connected to the device connector via a second K-line. The vehicle connector and the device connector are communicatively connected to the server. The device includes a first acquisition module, a first transmission module, a second acquisition module, a data recording module, a second transmission module, an initialization module, and a remote diagnostic module, wherein:

[0014] The first acquisition module is used to acquire the diagnostic address data of the diagnostic instrument and record the diagnostic address data to obtain a first data record;

[0015] The first sending module is configured to send a first network command to the vehicle connector; the first network command includes the first data record; the vehicle connector is configured to send the first data record in the first network command to the target vehicle;

[0016] The second acquisition module is used to acquire vehicle response data of the target vehicle; the vehicle response data is the response data generated by the target vehicle in response to the first data record;

[0017] The data recording module is used to record the vehicle response data to obtain a second data record;

[0018] The second sending module is used to send a second network command to the device connector; the second network command includes the second data record; the device connector is used to send the second data record in the second network command to the diagnostic instrument;

[0019] The initialization module is used to perform the initialization of the ISO9141-2 protocol between the device connector and the diagnostic instrument, and the initialization of the ISO9141-2 protocol between the vehicle connector and the target vehicle, based on the first data record and the second data record.

[0020] The remote diagnostic module is used to perform remote diagnostics on the target vehicle and obtain the target diagnostic results.

[0021] Thirdly, embodiments of this application provide an electronic device, including a processor, a memory, a communication interface, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the processor, and the programs include instructions for performing steps in any method of the first aspect of this application.

[0022] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program for electronic data interchange, wherein the computer program causes a computer to perform some or all of the steps described in any method of the first aspect of this application.

[0023] Fifthly, embodiments of this application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps described in any method of the first aspect of this application. The computer program product may be a software installation package.

[0024] By implementing the embodiments of this application, the initialization process of the diagnostic protocol can be automated and the vehicle can be remotely diagnosed, which not only improves the reliability of data transmission and the overall efficiency of remote diagnosis, but also makes the remote diagnosis results of the vehicle more accurate. Attached Figure Description

[0025] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0026] Figure 1 This is a system architecture diagram of a remote diagnostic system provided in an embodiment of this application;

[0027] Figure 2 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application;

[0028] Figure 3This is a flowchart illustrating a remote diagnostic method based on the vehicle ISO9141-2 protocol provided in an embodiment of this application.

[0029] Figure 4 This is a schematic diagram of a communication protocol initialization process provided in an embodiment of this application;

[0030] Figure 5 This is a time-series flowchart of a data transmission process provided in an embodiment of this application;

[0031] Figure 6 This is a flowchart illustrating the process of determining the duration of target W4-2 according to an embodiment of this application;

[0032] Figure 7 This is a block diagram of the functional modules of a remote diagnostic device based on the vehicle ISO9141-2 protocol provided in an embodiment of this application. Detailed Implementation

[0033] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present application.

[0034] The terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or apparatuses.

[0035] It should be understood that the term "and / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document indicates that the preceding and following related objects are in an "or" relationship. In the embodiments of this application, "multiple" refers to two or more.

[0036] In the embodiments of this application, "at least one item" or its similar expression refers to any combination of these items, including any combination of a single item or a plurality of items. "One or more" means one or more, while "multiple" means two or more. For example, "at least one item" of a, b, or c can represent the following seven cases: a, b, c; a and b; a and c; b and c; a, b, and c. Each of a, b, and c can be an element or a set containing one or more elements.

[0037] In this application, the term "connection" refers to various connection methods, such as direct connection or indirect connection, to achieve communication between devices. This application does not impose any limitations on this.

[0038] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0039] The following is an explanation of the relevant terms used in this application:

[0040] ISO 9141-2 protocol: refers to the communication protocols and electrical characteristics of the data link layer and physical layer in vehicle diagnostic systems. It ensures compatibility and interoperability between automobile manufacturers and diagnostic equipment suppliers, enabling diagnostic equipment from different manufacturers to perform fault diagnosis, parameter reading, and control operations on various vehicles that conform to the standard.

[0041] Traditional vehicle diagnostics typically require taking the vehicle to a repair shop and using a diagnostic tool connected via a physical link. However, when a vehicle is in a remote area or is immobilized due to a malfunction, remote diagnostic technology is needed. However, current remote diagnostic processes can suffer from significant network latency, reducing efficiency and accuracy. Therefore, improving the efficiency and accuracy of remote diagnostics is a pressing issue.

[0042] To address the aforementioned problems, this application provides a remote diagnostic method and apparatus based on the vehicle ISO9141-2 protocol, applied to a server in a remote diagnostic system. The remote diagnostic system further includes a target vehicle, a vehicle connector, a device connector, and a diagnostic instrument. The target vehicle is connected to the vehicle connector via a first K-line, and the diagnostic instrument is connected to the device connector via a second K-line. The vehicle connector and the device connector are communicatively connected to the server. First, the diagnostic address data of the diagnostic instrument is acquired and recorded to obtain a first data record. Then, a first network command is sent to the vehicle connector; the first network command includes the first data record. The vehicle connector is used to store the first data record in the first network command. The system sends a record to the target vehicle; then, it acquires the vehicle response data of the target vehicle; the vehicle response data is the response data generated by the target vehicle in response to the first data record; it records the vehicle response data to obtain a second data record; it sends a second network command to the device connector; the second network command includes the second data record; the device connector is used to send the second data record in the second network command to the diagnostic instrument; it performs the initialization of the ISO9141-2 protocol between the device connector and the diagnostic instrument, and the initialization of the ISO9141-2 protocol between the vehicle connector and the target vehicle, based on the first data record and the second data record; finally, it performs remote diagnostics on the target vehicle to obtain the target diagnostic result. By automating the initialization process of the diagnostic protocol and performing remote diagnostics on the vehicle, not only is the reliability of data transmission and the overall efficiency of remote diagnostics improved, but the remote diagnostic results of the vehicle are also made more accurate.

[0043] Please see Figure 1 , Figure 1 This is a system architecture diagram of a remote diagnostic system provided in an embodiment of this application. The remote diagnostic system includes a target vehicle, a vehicle connector, a device connector, a diagnostic instrument, and a server. The target vehicle and the vehicle connector are connected via a first K-line, and the diagnostic instrument and the device connector are connected via a second K-line. The vehicle connector and the device connector are communicatively connected to the server.

[0044] The target vehicles include, but are not limited to, cars, vans, and trucks. These vehicles are managed by multiple electronic control units (ECUs) covering key areas such as engine control, transmission control, braking systems, and body electronics. These ECUs can collect and process data from various vehicle sensors and precisely regulate the vehicle's operating status according to preset logic. During remote diagnostics, upon receiving a diagnostic request from the vehicle connector, the relevant ECUs quickly retrieve the necessary information, such as fault codes and real-time operating parameters, from their storage units, organize and package this data, and transmit it back to other components of the diagnostic system via the vehicle connector. For example, the engine's ECU can provide key data such as engine speed, throttle opening, and fuel injection quantity, reflecting the engine's current operating status.

[0045] The vehicle connector can receive network commands from the server, parse the instructions and data, and convert them into a format recognizable by the vehicle's internal electronic control unit (ECU), accurately transmitting them to the target ECU. The vehicle connector can also receive response data from the target vehicle's ECU, encapsulating and formatting it according to the remote diagnostic system's communication protocol requirements to ensure accurate data transmission to the server. For example, when the vehicle connector receives a fault code reading request forwarded by the server, it converts the request into instructions conforming to the vehicle's internal communication protocol and sends it to the corresponding ECU. Then, it organizes the fault code data returned by the ECU into a system-recognizable format and sends it back to the server. It should be noted that the communication protocols of the remote diagnostic system include, but are not limited to, the ISO 9141-2 protocol, which are not specifically limited here.

[0046] The diagnostic tool is the primary tool for technicians to interact with the remote diagnostic system. It features an intuitive human-machine interface, such as a display screen, buttons, or touchscreen, facilitating operation and viewing of diagnostic results. The diagnostic tool has built-in extensive diagnostic software and databases, covering diagnostic knowledge and fault code parsing information for various vehicle brands and models. It can initiate various diagnostic requests, such as reading fault codes, real-time data monitoring, and performing specific diagnostic tests. Based on user actions, the diagnostic tool generates corresponding diagnostic instructions and data, which are transmitted to the target vehicle via the device connector and server. Upon receiving the vehicle response data from the device connector, the diagnostic tool performs in-depth analysis and interpretation of the data using its internal database, presenting diagnostic results in an intuitive and easy-to-understand manner, such as fault causes, fault locations, and repair suggestions, providing accurate repair guidance for technicians. For example, when diagnosing a vehicle's engine, the diagnostic tool displays fault code "P0300" and indicates "random engine misfire," while providing possible causes such as spark plug failure or fuel injector blockage, along with corresponding repair suggestions.

[0047] The device connector receives diagnostic requests from the diagnostic tool, which include crucial information such as diagnostic address data. It then performs preliminary processing and recording of this data, creating corresponding data records to provide essential information for subsequent operations. Next, the device connector encapsulates the processed request data into network commands and forwards them to the vehicle connector via a server. When the device connector receives vehicle response data from the server, it accurately transmits it to the diagnostic tool, ensuring the diagnostic tool can promptly obtain relevant information about the target vehicle.

[0048] The server possesses high-performance computing capabilities and large-capacity data storage, enabling it to stably handle a large number of concurrent diagnostic requests and data transmission tasks. In terms of data transmission, the server receives diagnostic request data from the device connector and, based on the vehicle connector's network address information, quickly and accurately forwards the data to the vehicle connector. Simultaneously, the server promptly transmits the vehicle response data returned by the vehicle connector to the device connector, ensuring efficient data flow between system components. Furthermore, the server is responsible for managing and maintaining various types of data within the system, including device information, vehicle information, and diagnostic records, providing strong support for system operation and data analysis. It should be noted that network communication between the vehicle connector and the device connector includes, but is not limited to, technologies such as server data relay, P2P communication, wired network connection, and 4G / 5G network connection; specific limitations are not specified here.

[0049] In one possible embodiment, the diagnostic tool, acting as the initiator of the diagnostic operation, can generate diagnostic request data containing key information such as the diagnostic address based on the user's actions. This diagnostic request data serves as the basis for performing specific diagnostic operations on the target vehicle, such as requesting to read fault codes or real-time operating parameters of the vehicle's braking system; no specific limitation is made here. The device connector, connected to the diagnostic tool, is responsible for receiving the diagnostic request data from the diagnostic tool, performing preliminary processing and encapsulation of the data, and then sending it to the server via the network. The server can receive the diagnostic request data from the device connector and, based on information such as the vehicle connector's network address, accurately forward the data to the vehicle connector. The server enables device connectors and vehicle connectors in different geographical locations to interact across network boundaries, greatly expanding the application scope of the diagnostic system and thus realizing remote vehicle diagnostics.

[0050] As can be seen, the above system architecture enables rapid data transmission over the network. After the diagnostic instrument issues a diagnostic request, it is quickly transmitted to the target vehicle via the device connector, server, and vehicle connector. The vehicle response data from the target vehicle can also be quickly transmitted back, thereby improving the efficiency of remote diagnostics.

[0051] The following is combined with Figure 2 The electronic devices in the embodiments of this application will be described. Figure 2 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application, such as... Figure 2 As shown, the electronic device includes one or more processors, a memory, a communication interface, and one or more programs. The processor is connected to the memory and the communication interface via an internal communication bus.

[0052] The processor is mainly used for:

[0053] Acquire the diagnostic address data of the diagnostic instrument and record the diagnostic address data to obtain the first data record;

[0054] A first network command is sent to the vehicle connector; the first network command includes a first data record; the vehicle connector is used to send the first data record in the first network command to the target vehicle.

[0055] Obtain the vehicle response data of the target vehicle; the vehicle response data is the response data generated by the target vehicle in response to the first data record;

[0056] The vehicle response data is recorded to obtain the second data record;

[0057] Send a second network command to the device connector; the second network command includes a second data record; the device connector is used to send the second data record in the second network command to the diagnostic instrument;

[0058] The initialization of the ISO9141-2 protocol between the device connector and the diagnostic instrument, and the initialization of the ISO9141-2 protocol between the vehicle connector and the target vehicle are performed according to the first data record and the second data record.

[0059] Perform remote diagnostics on the target vehicle and obtain the target diagnostic results.

[0060] The one or more programs are stored in the aforementioned memory and configured to be executed by the aforementioned processor, and the one or more programs include instructions for performing any step in the above method embodiments.

[0061] The processor can be, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various exemplary logic blocks, cells, and circuits described in conjunction with the disclosure of this application. The processor can also be a combination that implements computational functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc. The communication unit can be a communication interface, a transceiver, a transceiver circuit, etc., and the storage unit can be a memory.

[0062] The memory can be volatile or non-volatile, or a combination of both. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), used as an external cache. By way of example, but not limitation, many forms of random access memory (RAM) are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate synchronous DRAM (DDR SDRAM), enhanced synchronous DRAM (ESDRAM), synchronous linked DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0063] It is understood that the electronic device may include more or fewer structural elements than those shown in the block diagram above, such as a power module, physical buttons, a Wi-Fi module, a speaker, a Bluetooth module, sensors, a display module, etc., without limitation. It is understood that the electronic device may incorporate elements such as... Figure 1 The system architecture described above.

[0064] After understanding the software and hardware architecture of this application, the following will be combined with... Figure 3 This application describes a remote diagnostic method based on the vehicle ISO9141-2 protocol. Figure 3 This is a flowchart illustrating a remote diagnostic method based on the ISO9141-2 protocol for vehicles, provided in an embodiment of this application. The method is applied to a server in a remote diagnostic system. The remote diagnostic system also includes a target vehicle, a vehicle connector, a device connector, and a diagnostic instrument. The target vehicle is connected to the vehicle connector via a first K-line, and the diagnostic instrument is connected to the device connector via a second K-line. The vehicle connector and the device connector are communicatively connected to the server. The method specifically includes the following steps:

[0065] Step S301: Obtain the diagnostic address data of the diagnostic instrument and record the diagnostic address data to obtain the first data record.

[0066] Specifically, after receiving a diagnostic task set by the user, the diagnostic tool can generate diagnostic address data based on the relevant information of the target vehicle. It then creates a specific data structure in its internal storage area to record this diagnostic address data. This data structure may contain multiple fields, including not only the diagnostic address data itself but also auxiliary information such as the data acquisition timestamp, the diagnostic tool's device number, and the diagnostic task initiation time, thus obtaining the first data record.

[0067] Step S302: Send a first network command to the vehicle connector.

[0068] The first network command includes the first data record; the vehicle connector is used to send the first data record in the first network command to the target vehicle.

[0069] Specifically, the server sends the first network command to the vehicle connector. After receiving the first network command, the vehicle connector can parse the first network command, extract the first data record, identify the key information such as the diagnostic address contained therein, and then send the first data record to the target vehicle. This enables the target vehicle to obtain the diagnostic request issued by the diagnostic instrument and provides a foundation for the accuracy of subsequent remote diagnostics.

[0070] Step S303: Obtain the vehicle response data of the target vehicle.

[0071] The vehicle response data refers to the response data generated by the target vehicle in response to the first data record.

[0072] Specifically, after the target vehicle receives the first data record from the vehicle connector, its internal electronic control system parses the first data record to generate corresponding vehicle response data. The first data record contains key diagnostic information from the diagnostic tool, such as the diagnostic address. Based on this information, the target vehicle can then generate corresponding vehicle response data according to a preset program and logic.

[0073] Step S304: Record the vehicle response data to obtain a second data record.

[0074] Specifically, a database can be used to record vehicle response data, organizing it according to a preset format and structure for easy querying and retrieval. For example, indexes such as time sequence, vehicle identification, and diagnostic task number can be used to quickly locate and retrieve specific secondary data records.

[0075] Step S305: Send a second network command to the device connector.

[0076] The second network command includes the second data record; the device connector is used to send the second data record in the second network command to the diagnostic instrument.

[0077] Specifically, the server sends a second network command to the device connector. Upon receiving the second network command, the device connector parses it, extracts the second data record, identifies the vehicle response data contained within, and then sends the second data record to the diagnostic tool. The diagnostic tool can then assess the vehicle's operating status based on the vehicle response data, combined with preset diagnostic algorithms and a knowledge base, to determine whether the vehicle has a fault, and if so, the type and severity of that fault.

[0078] Step S306: Perform the initialization of the ISO9141-2 protocol between the device connector and the diagnostic instrument, and the initialization of the ISO9141-2 protocol between the vehicle connector and the target vehicle, based on the first data record and the second data record.

[0079] The first data record includes a diagnostic address, a first synchronization code, a first diagnostic keyword, and a second diagnostic keyword; the second data record includes a second synchronization code, a first response keyword, and a second response keyword. The initialization of the ISO9141-2 protocol between the device connector and the diagnostic instrument, and the initialization of the ISO9141-2 protocol between the vehicle connector and the target vehicle are performed based on the first and second data records. For easier understanding, please refer to [link to relevant documentation]. Figure 4 , Figure 4 This application provides a schematic diagram of a communication protocol initialization process, the specific steps of which include:

[0080] A1. If the first diagnostic keyword matches the first response keyword and the second diagnostic keyword matches the second response keyword, then perform a data sending operation based on the first data record.

[0081] A2. Obtain the first inverted data byte of the second diagnostic keyword of the diagnostic instrument and record the time interval of its reception to obtain the first W4-1 duration;

[0082] A3. Generate a third network command based on the first W4-1 duration, and send the third network command to the vehicle connector;

[0083] A4. Obtain historical initialization records and determine the duration of target W4-2 based on the historical initialization records;

[0084] A5. Send the second inverted data byte of the diagnostic address to the diagnostic instrument according to the target W4-2 duration;

[0085] A6. Obtain the fourth network command and update the historical initialization record according to the fourth network command to complete the initialization of the ISO9141-2 protocol between the device connector and the diagnostic instrument;

[0086] A7. Perform the initialization of the ISO9141-2 protocol between the vehicle connector and the target vehicle based on the first data record and the second data record.

[0087] In a specific embodiment, firstly, the communication information between the diagnostic tool and the device connector is accurately matched by comparing the diagnostic keyword and the response keyword. When the first diagnostic keyword matches the first response keyword successfully, and the second diagnostic keyword matches the second response keyword successfully, subsequent data transmission operations continue to ensure the accuracy and consistency of data interaction. Then, the first inverted data byte of the second diagnostic keyword from the diagnostic tool is obtained, and the time interval for receiving the first inverted data byte is recorded to obtain the first W4-1 duration. A third network command is then generated based on the first W4-1 duration and sent to the vehicle connector. Historical initialization records are obtained, including information on the W4-1 and W4-2 durations from the previous diagnostic process, and the target W4-2 duration is determined based on the historical initialization records. It should be noted that the inverted data byte is obtained by inverting each bit of the byte. For example, if the second diagnostic keyword is 10101100, each bit is inverted, i.e., 1 becomes 0 and 0 becomes 1, to obtain the first inverted data byte, which is 01010011.

[0088] Next, based on the determined target W4-2 duration, the second inverted data byte of the diagnostic address is sent to the diagnostic tool. Then, the fourth network command is obtained, and the historical initialization record is updated according to the W4-2 duration in the fourth network command, thereby completing the initialization of the ISO9141-2 protocol between the backup connector and the diagnostic tool. This allows for quick acquisition of the corresponding duration information during the next remote diagnostic operation, providing a more accurate reference for subsequent diagnostic operations. Finally, the initialization of the ISO9141-2 protocol between the vehicle connector and the target vehicle is performed based on the first and second data records.

[0089] As can be seen, by quickly performing the initialization of the ISO9141-2 protocol, a stable and reliable communication link can be established, ensuring that diagnostic information can be accurately transmitted from the vehicle to the diagnostic system, thus providing support for accurate diagnosis of vehicle faults.

[0090] The first data record further includes durations W1, W2, and W3. The specific steps for performing the data transmission operation based on the first data record include:

[0091] B1. After the keyword matching is successful, the first synchronization code is sent to the diagnostic instrument according to the time interval corresponding to the W1 duration;

[0092] B2. After sending the first synchronization code, send the first diagnostic keyword to the diagnostic instrument according to the time interval corresponding to the W2 duration;

[0093] B3. After sending the first diagnostic keyword, send the second diagnostic keyword to the diagnostic instrument according to the time interval corresponding to the W3 duration.

[0094] In a specific embodiment, after a successful keyword match, a first synchronization code is sent to the diagnostic instrument at time intervals corresponding to duration W1. The first synchronization code establishes a synchronization benchmark for subsequent data transmission, allowing the diagnostic instrument to accurately identify the start position and transmission rhythm of subsequent data. In actual communication, the accuracy of the time interval is crucial. An unreasonable time interval setting may prevent the diagnostic instrument from correctly receiving the synchronization code, thus affecting the initialization of the entire communication process. For example, if the sending time is too early, the diagnostic instrument may not be ready to receive; if the sending time is too late, the optimal synchronization opportunity may be missed. Then, after sending the first synchronization code, a first diagnostic keyword is sent to the diagnostic instrument at time intervals corresponding to duration W2. The duration W2 ensures that there is sufficient time for the diagnostic instrument to prepare to receive the first diagnostic keyword after sending the first synchronization code. A reasonable time interval can avoid data conflicts and ensure that the first diagnostic keyword can be accurately received and parsed by the diagnostic instrument. If the time interval is too short, the diagnostic instrument may still be processing the synchronization code information and cannot process the first diagnostic keyword in a timely manner; if the time interval is too long, it will increase the time overhead of the entire communication process and reduce diagnostic efficiency. Finally, after sending the first diagnostic keyword, the second diagnostic keyword is sent to the diagnostic instrument at the time interval corresponding to the W3 duration. The control of the W3 duration ensures that the second diagnostic keyword is sent at the appropriate time after the first diagnostic keyword is sent. This helps maintain the continuity and accuracy of communication, allowing the diagnostic instrument to receive and process the information from the two diagnostic keywords in the correct order. Inappropriate time intervals may cause the diagnostic instrument to receive the two keywords in a disordered order, resulting in reduced efficiency and accuracy of the diagnostic process.

[0095] For better understanding, see [link to relevant documentation]. Figure 5 , Figure 5 The time-series flowchart provided in this application embodiment illustrates a data transmission process. As can be seen, the point in time corresponding to a successful keyword match is the starting point of the entire process. Specifically, after a duration of W1 following a successful keyword match, the first synchronization code is sent. Then, after sending the first synchronization code, a duration of W2 follows, and the first diagnostic keyword is sent. Finally, after sending the first diagnostic keyword, a duration of W3 follows, and the second diagnostic keyword is sent. By performing data transmission operations according to the corresponding time intervals, the rhythm and sequence of diagnostic command transmission can be precisely controlled, ensuring accurate and stable communication between the vehicle connector and the diagnostic equipment. This efficiently obtains vehicle diagnostic information, providing a basis for subsequent fault diagnosis and repair.

[0096] Specifically, for easier understanding, please refer to [link to relevant documentation]. The step of determining the duration of target W4-2 based on the historical initialization records is described below. Figure 6 , Figure 6 A flowchart illustrating the process of determining the duration of target W4-2, as provided in this application embodiment, includes the following steps:

[0097] C1. If a reference W4-2 duration exists in the historical initialization record, and the device connector receives the reference W4-2 duration from the vehicle connector, then the target W4-2 duration is determined to be the reference W4-2 duration.

[0098] C2. If the reference W4-2 duration is not present in the historical initialization record, and / or the device connector does not receive the reference W4-2 duration from the vehicle connector, then the target W4-2 duration is determined to be a preset time interval.

[0099] In a specific embodiment, when a reference W4-2 duration exists in the historical initialization record and the device connector successfully receives the reference W4-2 duration from the vehicle connector, the reference W4-2 duration can be used as the target W4-2 duration. When a reference W4-2 duration does not exist in the historical initialization record, and / or the device connector does not receive the reference W4-2 duration from the vehicle connector, a preset time interval is used as the target W4-2 duration. The preset time interval can be 25ms, and is not specifically limited here.

[0100] It is evident that by utilizing historical data and real-time information, the target W4-2 duration can be determined according to different situations to adapt to different diagnostic scenarios and vehicle states. Furthermore, by setting a reasonable target W4-2 duration, the stability of communication between the device connector and the diagnostic instrument can be improved, thereby enhancing the reliability of remote diagnostic operations.

[0101] The specific steps of initializing the ISO9141-2 protocol between the vehicle connector and the target vehicle based on the first data record and the second data record include:

[0102] D1. If a reference W4-1 duration exists in the historical initialization record, and the vehicle connector receives the reference W4-1 duration from the device connector, then the target W4-1 duration is determined to be the reference W4-1 duration.

[0103] D2. If the reference W4-1 duration does not exist in the historical initialization record, and / or the vehicle connector does not receive the reference W4-1 duration from the device connector, then the target W4-1 duration is determined to be the preset time interval.

[0104] D3. Send the third inverted data byte of the second response keyword to the target vehicle according to the target W4-1 duration, and record the sending time of the third inverted data byte;

[0105] D4. Obtain the third network command and update the historical initialization record according to the third network command;

[0106] D5. Obtain the fourth inverted data byte of the vehicle address of the target vehicle, and record the receiving time corresponding to the fourth inverted data byte;

[0107] D6. Determine the time interval between the sending time and the receiving time as the first W4-2 duration;

[0108] D7. Generate a fourth network command based on the first W4-2 duration, and send the fourth network command to the device connector to complete the initialization of the ISO9141-2 protocol between the vehicle connector and the target vehicle.

[0109] In a specific embodiment, when a reference W4-1 duration exists in the historical initialization record and the vehicle connector successfully receives the reference W4-1 duration from the device connector, the reference W4-1 duration can be used as the target W4-1 duration. When a reference W4-1 duration does not exist in the historical initialization record, and / or the vehicle connector does not receive the reference W4-1 duration from the device connector, a preset time interval is used as the target W4-1 duration. The preset time interval can be 25ms, and is not specifically limited here. Then, according to the determined target W4-1 duration, the third inverted data byte of the second response keyword is sent to the target vehicle, and the sending time of the third inverted data byte is recorded. A third network command can be obtained, and the historical initialization record is updated according to the third network command. Then, the fourth inverted data byte of the target vehicle's vehicle address is obtained, and its receiving time is recorded. The time interval between the sending time of the third inverted data byte and the receiving time of the fourth inverted data byte is calculated and determined as the first W4-2 duration. Finally, a fourth network command is generated based on the first W4-2 duration and sent to the device connector to complete the initialization of the ISO9141-2 protocol between the vehicle connector and the target vehicle, laying the foundation for subsequent diagnostic data transmission.

[0110] It is evident that accurate timing control can ensure that data interaction between the vehicle connector and the target vehicle proceeds at a predetermined pace, enabling better synchronization between the two parties, improving communication efficiency and reliability, and avoiding errors in remote diagnostics due to network latency.

[0111] Step S307: Perform remote diagnostics on the target vehicle to obtain the target diagnostic results.

[0112] The specific steps for remotely diagnosing the target vehicle and obtaining diagnostic results include:

[0113] E1. Obtain the diagnostic requirements corresponding to the target vehicle;

[0114] E2. Generate a diagnostic request based on the diagnostic requirements and send the diagnostic request to the device connector;

[0115] E3. Generate a fifth network command based on the diagnostic request; the fifth network command includes the diagnostic request.

[0116] E4. The server sends the fifth network command to the vehicle connector; the vehicle connector is also used to send the diagnostic request in the fifth network command to the target vehicle;

[0117] E5. Obtain the diagnostic response of the target vehicle to the diagnostic request, and generate a sixth network command based on the diagnostic response; the sixth network command includes the diagnostic response;

[0118] E6. The server sends the sixth network command to the device connector; the device connector is also used to send the diagnostic response in the sixth network command to the diagnostic instrument;

[0119] E7. Determine the target diagnostic result based on the diagnostic response.

[0120] In a specific embodiment, firstly, the diagnostic requirements corresponding to the target vehicle are obtained. These requirements can be determined based on the vehicle's fault symptoms; for example, if the fault symptoms are engine vibration or abnormal fuel consumption, the diagnostic requirement could be to diagnose engine-related systems. Alternatively, the diagnostic requirements can be determined based on the user's personalized needs, such as a comprehensive inspection required during regular maintenance, without further specific limitations. Then, based on the obtained diagnostic requirements, a specific diagnostic request is generated and sent to the device connector. The diagnostic request includes the specific content and requirements of the diagnosis, such as the types of fault codes to be read and the categories of parameters to be monitored. The diagnostic request is then encapsulated into a fifth network command and sent to the vehicle connector, which can then forward the diagnostic request from the fifth network command to the target vehicle.

[0121] Next, the diagnostic response from the target vehicle to the diagnostic request is obtained and encapsulated into a sixth network command. Upon receiving the diagnostic request, the target vehicle can respond accordingly and generate a diagnostic response, which includes the vehicle's actual status information, such as fault codes and real-time parameters. Then, the server forwards the sixth network command to the device connector, which in turn sends the diagnostic response from the sixth network command to the diagnostic instrument. Finally, the diagnostic instrument analyzes and judges the target vehicle's status based on the received diagnostic response, combined with a preset diagnostic algorithm and database, ultimately determining the target diagnostic result.

[0122] As can be seen, generating diagnostic requests based on specific diagnostic needs avoids unnecessary diagnostic operations, while ensuring a comprehensive examination of key issues. Furthermore, the efficient data transmission and processing mechanism makes the diagnostic process faster, allowing users to obtain diagnostic results more quickly.

[0123] The specific steps for determining the target diagnostic result based on the diagnostic response include:

[0124] F1. Obtain the target fault code and target vehicle parameters from the diagnostic response;

[0125] F2. Based on the preset mapping relationship between fault codes and diagnostic results, determine the first diagnostic result corresponding to the target fault code;

[0126] F3. Obtain the standard parameter range corresponding to the target vehicle;

[0127] F4. Compare the standard parameter range with the target vehicle parameters to obtain a second diagnostic result;

[0128] F5. Determine the target diagnostic result based on the first diagnostic result and the second diagnostic result.

[0129] In a specific embodiment, firstly, the target fault code and target vehicle parameters are extracted from the diagnostic response. The target fault code is a specific code generated when the vehicle's electronic control system detects an anomaly, indicating the approximate location or type of the fault. The target vehicle parameters include data reflecting the vehicle's real-time operating status, such as engine speed, vehicle speed, and coolant temperature. Then, based on a preset mapping relationship between fault codes and diagnostic results, the first diagnostic result corresponding to the target fault code is determined. Next, the standard parameter range corresponding to the target vehicle is obtained. Different vehicle models have their own normal standard parameter ranges for various parameters, which are crucial for determining whether the vehicle's operating status is normal. The standard parameter range is compared with the target vehicle parameters. If the target vehicle parameters exceed the standard parameter range, it can be inferred that the target vehicle may have a problem in the corresponding aspect, leading to a second diagnostic result. Finally, the first and second diagnostic results are combined to determine the final target diagnostic result. If the first and second diagnostic results are consistent, the target diagnostic result is considered relatively accurate; if there is a difference, further analysis of possible causes is needed, such as false fault code reports or parameter measurement errors. In addition, the second diagnostic result can also identify potential faults or performance abnormalities without generating fault codes. For example, if the vehicle's water temperature parameter is consistently higher than the standard parameter range even without a fault code, there may be a problem with the cooling system.

[0130] It is evident that combining fault code analysis and vehicle parameter comparison can diagnose the target vehicle from different perspectives, improving the accuracy and reliability of remote diagnostic results.

[0131] The above primarily describes the solutions of the embodiments of this application from the perspective of the method execution process. It is understood that, in order to achieve the above functions, the electronic device includes corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should readily recognize that, in conjunction with the units and algorithm steps of the various examples described in the embodiments provided herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0132] This application embodiment can divide the electronic device into functional units according to the above method example. For example, each function can be divided into a separate functional unit, or two or more functions can be integrated into one processing unit. The integrated unit can be implemented in hardware or as a software functional unit. It should be noted that the unit division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0133] When dividing each function into modules according to its corresponding function. Figure 7 This application provides a functional block diagram of a remote diagnostic device based on the vehicle ISO9141-2 protocol, applied to a server in a remote diagnostic system. The remote diagnostic system also includes a target vehicle, a vehicle connector, a device connector, and a diagnostic instrument. The target vehicle is connected to the vehicle connector via a first K-line, and the diagnostic instrument is connected to the device connector via a second K-line. The vehicle connector and the device connector are communicatively connected to the server. The remote diagnostic device 700 based on the vehicle ISO9141-2 protocol includes a first acquisition module 710, a first transmission module 720, a second acquisition module 730, a data recording module 740, a second transmission module 750, an initialization module 760, and a remote diagnostic module 770, wherein:

[0134] The first acquisition module 710 is used to acquire the diagnostic address data of the diagnostic instrument and record the diagnostic address data to obtain a first data record;

[0135] The first sending module 720 is used to send a first network command to the vehicle connector; the first network command includes the first data record; the vehicle connector is used to send the first data record in the first network command to the target vehicle;

[0136] The second acquisition module 730 is used to acquire vehicle response data of the target vehicle; the vehicle response data is the response data generated by the target vehicle in response to the first data record;

[0137] The data recording module 740 is used to record the vehicle response data to obtain a second data record;

[0138] The second sending module 750 is used to send a second network command to the device connector; the second network command includes the second data record; the device connector is used to send the second data record in the second network command to the diagnostic instrument;

[0139] The initialization module 760 is used to perform the initialization of the ISO9141-2 protocol between the device connector and the diagnostic instrument, and the initialization of the ISO9141-2 protocol between the vehicle connector and the target vehicle, according to the first data record and the second data record.

[0140] The remote diagnostic module 770 is used to perform remote diagnostics on the target vehicle and obtain the target diagnostic results.

[0141] Optionally, the first data record includes a diagnostic address, a first synchronization code, a first diagnostic keyword, and a second diagnostic keyword; the second data record includes a second synchronization code, a first response keyword, and a second response keyword. In the process of initializing the ISO9141-2 protocol between the device connector and the diagnostic instrument, and the ISO9141-2 protocol between the vehicle connector and the target vehicle, based on the first data record and the second data record, the initialization module 760 is specifically used for:

[0142] If the first diagnostic keyword matches the first response keyword and the second diagnostic keyword matches the second response keyword, then a data sending operation is performed based on the first data record.

[0143] Obtain the first inverted data byte of the second diagnostic keyword of the diagnostic instrument and record the time interval of its reception to obtain the first W4-1 duration;

[0144] A third network command is generated based on the first W4-1 duration, and the third network command is sent to the vehicle connector;

[0145] Obtain historical initialization records and determine the duration of target W4-2 based on the historical initialization records;

[0146] The second inverted data byte of the diagnostic address is sent to the diagnostic instrument according to the target W4-2 duration;

[0147] Obtain the fourth network command and update the historical initialization record according to the fourth network command to complete the initialization of the ISO9141-2 protocol between the device connector and the diagnostic instrument;

[0148] The initialization of the ISO9141-2 protocol between the vehicle connector and the target vehicle is performed based on the first data record and the second data record.

[0149] Optionally, the first data record further includes durations W1, W2, and W3. In the aspect of performing the data transmission operation based on the first data record, the initialization module 760 is specifically used for:

[0150] After a successful keyword match, the first synchronization code is sent to the diagnostic instrument according to the time interval corresponding to the W1 duration;

[0151] After sending the first synchronization code, the first diagnostic keyword is sent to the diagnostic instrument according to the time interval corresponding to the W2 duration;

[0152] After sending the first diagnostic keyword, the second diagnostic keyword is sent to the diagnostic instrument according to the time interval corresponding to the W3 duration.

[0153] Optionally, in determining the duration of target W4-2 based on the historical initialization records, the initialization module 760 is specifically used for:

[0154] If a reference W4-2 duration exists in the historical initialization record, and the device connector receives the reference W4-2 duration from the vehicle connector, then the target W4-2 duration is determined to be the reference W4-2 duration.

[0155] If the reference W4-2 duration is not present in the historical initialization record, and / or the device connector does not receive the reference W4-2 duration from the vehicle connector, then the target W4-2 duration is determined to be a preset time interval.

[0156] Optionally, in the aspect of performing the initialization of the ISO9141-2 protocol between the vehicle connector and the target vehicle based on the first data record and the second data record, the initialization module 760 is specifically used for:

[0157] If a reference W4-1 duration exists in the historical initialization record, and the vehicle connector receives the reference W4-1 duration from the device connector, then the target W4-1 duration is determined to be the reference W4-1 duration.

[0158] If the reference W4-1 duration is not present in the historical initialization record, and / or the vehicle connector does not receive the reference W4-1 duration from the device connector, then the target W4-1 duration is determined to be the preset time interval.

[0159] According to the target W4-1 duration, the third inverted data byte of the second response keyword is sent to the target vehicle, and the sending time of the third inverted data byte is recorded;

[0160] Obtain the third network command and update the historical initialization record according to the third network command;

[0161] Obtain the fourth inverted data byte of the vehicle address of the target vehicle, and record the receiving time corresponding to the fourth inverted data byte;

[0162] The time interval between the sending time and the receiving time is determined to be the first W4-2 duration;

[0163] A fourth network command is generated based on the first W4-2 duration, and the fourth network command is sent to the device connector to complete the initialization of the ISO9141-2 protocol between the vehicle connector and the target vehicle.

[0164] Optionally, in the process of remotely diagnosing the target vehicle and obtaining diagnostic results, the remote diagnostic module 770 is specifically used for:

[0165] Obtain the diagnostic requirements corresponding to the target vehicle;

[0166] A diagnostic request is generated based on the diagnostic requirements, and the diagnostic request is sent to the device connector;

[0167] A fifth network command is generated based on the diagnostic request; the fifth network command includes the diagnostic request.

[0168] The server sends the fifth network command to the vehicle connector; the vehicle connector is also used to send the diagnostic request in the fifth network command to the target vehicle;

[0169] Obtain the diagnostic response of the target vehicle to the diagnostic request, and generate a sixth network command based on the diagnostic response; the sixth network command includes the diagnostic response;

[0170] The server sends the sixth network command to the device connector; the device connector is also used to send the diagnostic response in the sixth network command to the diagnostic instrument.

[0171] The target diagnostic result is determined based on the diagnostic response.

[0172] Optionally, in determining the target diagnostic result based on the diagnostic response, the remote diagnostic module 770 is specifically configured to:

[0173] Obtain the target fault code and target vehicle parameters from the diagnostic response;

[0174] Based on the preset mapping relationship between fault codes and diagnostic results, determine the first diagnostic result corresponding to the target fault code;

[0175] Obtain the standard parameter range corresponding to the target vehicle;

[0176] The standard parameter range is compared with the target vehicle parameters to obtain a second diagnostic result;

[0177] The target diagnostic result is determined based on the first diagnostic result and the second diagnostic result.

[0178] It is evident that by automating the initialization process of the diagnostic protocol and performing remote diagnostics on the vehicle, not only is the reliability of data transmission and the overall efficiency of remote diagnostics improved, but the results of remote vehicle diagnostics are also made more accurate.

[0179] It should be noted that the specific implementation of each operation can be described in the corresponding description of the method embodiments shown above. The remote diagnostic device 700 based on the vehicle ISO9141-2 protocol can be used to execute the method embodiments of this application, and will not be described again here.

[0180] This application also provides a computer-readable storage medium storing a computer program for electronic data interchange, which causes a computer to perform some or all of the steps of any of the methods described in the above method embodiments, wherein the computer includes an electronic device.

[0181] This application also provides a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps of any of the methods described in the above method embodiments. The computer program product may be a software installation package, and the computer may include an electronic device.

[0182] It should be noted that, for the sake of simplicity, the above embodiments are all described as a series of actions. Those skilled in the art should understand that this application is not limited to the described order of actions, as some steps in the embodiments of this application can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions, steps, modules, or units involved are not necessarily essential to the embodiments of this application.

[0183] In the above embodiments, the descriptions of each embodiment in this application have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0184] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. This program can be stored in a computer-readable storage medium, and when executed, it can include the processes described in the above method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as ROM or random access memory (RAM), magnetic disks, or optical disks.

[0185] The steps of the methods or algorithms described in the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in RAM, flash memory, ROM, EPROM, electrically erasable programmable read-only memory (EEPROM), registers, hard disk, portable hard disk, read-only optical disk (CD-ROM), or any other form of storage medium well known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Furthermore, the ASIC can reside in a terminal device or management device. Alternatively, the processor and storage medium can exist as discrete components in the terminal device or management device.

[0186] Those skilled in the art will recognize that, in one or more of the examples above, the functions described in the embodiments of this application can be implemented, in whole or in part, by software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer instructions. When these computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

[0187] The modules / units included in the various devices and products described in the above embodiments can be software modules / units, hardware modules / units, or a combination of both. For example, for devices and products applied to or integrated into a chip, all modules / units can be implemented using hardware methods such as circuits, or at least some modules / units can be implemented using software programs that run on a processor integrated within the chip, while the remaining (if any) modules / units can be implemented using hardware methods such as circuits. For devices and products applied to or integrated into a chip module, all modules / units can be implemented using hardware methods such as circuits. Different modules / units can be located in the same component (e.g., chip, circuit module, etc.) or different components of the chip module, or at least some modules / units can be implemented using hardware methods such as circuits. The implementation is achieved through a software program that runs on a processor integrated within the chip module. The remaining modules / units (if any) can be implemented using hardware methods such as circuits. For various devices and products applied to or integrated into terminal equipment, each of their modules / units can be implemented using hardware methods such as circuits. Different modules / units can be located in the same component (e.g., chip, circuit module, etc.) or different components within the terminal equipment. Alternatively, at least some modules / units can be implemented using a software program that runs on a processor integrated within the terminal equipment, while the remaining modules / units (if any) can be implemented using hardware methods such as circuits.

[0188] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of the embodiments of this application. It should be understood that the above descriptions are merely specific embodiments of the embodiments of this application and are not intended to limit the protection scope of the embodiments of this application. Any modifications, equivalent substitutions, improvements, etc., made on the basis of the technical solutions of the embodiments of this application should be included within the protection scope of the embodiments of this application.

Claims

1. A remote diagnostic method based on the vehicle ISO9141-2 protocol, characterized in that, A server is used in a remote diagnostic system, the remote diagnostic system further including a target vehicle, a vehicle connector, a device connector, and a diagnostic instrument. The target vehicle is connected to the vehicle connector via a first K-line, and the diagnostic instrument is connected to the device connector via a second K-line. The vehicle connector and the device connector are communicatively connected to the server. The method includes: The diagnostic address data of the diagnostic instrument is obtained and recorded to obtain the first data record; A first network command is sent to the vehicle connector; the first network command includes the first data record; the vehicle connector is used to send the first data record in the first network command to the target vehicle. Obtain vehicle response data of the target vehicle; the vehicle response data is the response data generated by the target vehicle in response to the first data record; The vehicle response data is recorded to obtain a second data record; A second network command is sent to the device connector; the second network command includes the second data record; the device connector is used to send the second data record in the second network command to the diagnostic instrument. The initialization of the ISO9141-2 protocol between the device connector and the diagnostic instrument, and the initialization of the ISO9141-2 protocol between the vehicle connector and the target vehicle are performed according to the first data record and the second data record. The target vehicle is remotely diagnosed to obtain the target diagnosis results.

2. The method as described in claim 1, characterized in that, The first data record includes a diagnostic address, a first synchronization code, a first diagnostic keyword, and a second diagnostic keyword; the second data record includes a second synchronization code, a first response keyword, and a second response keyword; the initialization of the ISO9141-2 protocol between the device connector and the diagnostic instrument, and the initialization of the ISO9141-2 protocol between the vehicle connector and the target vehicle, based on the first and second data records, includes: If the first diagnostic keyword matches the first response keyword and the second diagnostic keyword matches the second response keyword, then a data sending operation is performed based on the first data record. Obtain the first inverted data byte of the second diagnostic keyword of the diagnostic instrument and record the time interval of its reception to obtain the first W4-1 duration; A third network command is generated based on the first W4-1 duration, and the third network command is sent to the vehicle connector; Obtain historical initialization records and determine the duration of target W4-2 based on the historical initialization records; The second inverted data byte of the diagnostic address is sent to the diagnostic instrument according to the target W4-2 duration; Obtain the fourth network command and update the historical initialization record according to the fourth network command to complete the initialization of the ISO9141-2 protocol between the device connector and the diagnostic instrument; The initialization of the ISO9141-2 protocol between the vehicle connector and the target vehicle is performed based on the first data record and the second data record.

3. The method as described in claim 2, characterized in that, The first data record also includes durations W1, W2, and W3. The step of performing a data transmission operation based on the first data record includes: After a successful keyword match, the first synchronization code is sent to the diagnostic instrument according to the time interval corresponding to the W1 duration; After sending the first synchronization code, the first diagnostic keyword is sent to the diagnostic instrument according to the time interval corresponding to the W2 duration; After sending the first diagnostic keyword, the second diagnostic keyword is sent to the diagnostic instrument according to the time interval corresponding to the W3 duration.

4. The method as described in claim 2, characterized in that, The step of determining the duration of target W4-2 based on the historical initialization records includes: If a reference W4-2 duration exists in the historical initialization record, and the device connector receives the reference W4-2 duration from the vehicle connector, then the target W4-2 duration is determined to be the reference W4-2 duration. If the reference W4-2 duration is not present in the historical initialization record, and / or the device connector does not receive the reference W4-2 duration from the vehicle connector, then the target W4-2 duration is determined to be a preset time interval.

5. The method as described in claim 4, characterized in that, The initialization of the ISO9141-2 protocol between the vehicle connector and the target vehicle based on the first data record and the second data record includes: If a reference W4-1 duration exists in the historical initialization record, and the vehicle connector receives the reference W4-1 duration from the device connector, then the target W4-1 duration is determined to be the reference W4-1 duration. If the reference W4-1 duration is not present in the historical initialization record, and / or the vehicle connector does not receive the reference W4-1 duration from the device connector, then the target W4-1 duration is determined to be the preset time interval. According to the target W4-1 duration, the third inverted data byte of the second response keyword is sent to the target vehicle, and the sending time of the third inverted data byte is recorded; Obtain the third network command and update the historical initialization record according to the third network command; Obtain the fourth inverted data byte of the vehicle address of the target vehicle, and record the receiving time corresponding to the fourth inverted data byte; The time interval between the sending time and the receiving time is determined to be a first W4-2 duration; A fourth network command is generated based on the first W4-2 duration, and the fourth network command is sent to the device connector to complete the initialization of the ISO9141-2 protocol between the vehicle connector and the target vehicle.

6. The method according to any one of claims 1-5, characterized in that, The remote diagnostics of the target vehicle, and the resulting diagnostic results, include: Obtain the diagnostic requirements corresponding to the target vehicle; A diagnostic request is generated based on the diagnostic requirements, and the diagnostic request is sent to the device connector; A fifth network command is generated based on the diagnostic request; the fifth network command includes the diagnostic request. The server sends the fifth network command to the vehicle connector; the vehicle connector is also used to send the diagnostic request in the fifth network command to the target vehicle; Obtain the diagnostic response of the target vehicle to the diagnostic request, and generate a sixth network command based on the diagnostic response; the sixth network command includes the diagnostic response; The server sends the sixth network command to the device connector; the device connector is also used to send the diagnostic response in the sixth network command to the diagnostic instrument. The target diagnostic result is determined based on the diagnostic response.

7. The method as described in claim 6, characterized in that, Determining the target diagnostic result based on the diagnostic response includes: Obtain the target fault code and target vehicle parameters from the diagnostic response; Based on the preset mapping relationship between fault codes and diagnostic results, determine the first diagnostic result corresponding to the target fault code; Obtain the standard parameter range corresponding to the target vehicle; The standard parameter range is compared with the target vehicle parameters to obtain a second diagnostic result; The target diagnostic result is determined based on the first diagnostic result and the second diagnostic result.

8. A remote diagnostic device based on the vehicle ISO9141-2 protocol, characterized in that, A server is used in a remote diagnostic system. The remote diagnostic system also includes a target vehicle, a vehicle connector, a device connector, and a diagnostic instrument. The target vehicle is connected to the vehicle connector via a first K-line, and the diagnostic instrument is connected to the device connector via a second K-line. The vehicle connector and the device connector are communicatively connected to the server. The device includes a first acquisition module, a first transmission module, a second acquisition module, a data recording module, a second transmission module, an initialization module, and a remote diagnostic module, wherein: The first acquisition module is used to acquire the diagnostic address data of the diagnostic instrument and record the diagnostic address data to obtain a first data record; The first sending module is configured to send a first network command to the vehicle connector; the first network command includes the first data record; the vehicle connector is configured to send the first data record in the first network command to the target vehicle; The second acquisition module is used to acquire vehicle response data of the target vehicle; the vehicle response data is the response data generated by the target vehicle in response to the first data record; The data recording module is used to record the vehicle response data to obtain a second data record; The second sending module is used to send a second network command to the device connector; the second network command includes the second data record; the device connector is used to send the second data record in the second network command to the diagnostic instrument; The initialization module is used to perform the initialization of the ISO9141-2 protocol between the device connector and the diagnostic instrument, and the initialization of the ISO9141-2 protocol between the vehicle connector and the target vehicle, based on the first data record and the second data record. The remote diagnostic module is used to perform remote diagnostics on the target vehicle and obtain the target diagnostic results.

9. An electronic device, characterized in that, include: Processor, memory, communication interface, and one or more programs; The one or more programs are stored in the memory and configured to be executed by the processor, the programs including instructions for performing the steps of the method as described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, the computer program including program instructions that, when executed by a processor, cause the processor to perform the method as described in any one of claims 1-7.

Images