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

Abstract

The invention provides a remote diagnosis method and device based on a vehicle ISO9141-2 protocol, and the method comprises the steps: obtaining diagnosis address data of a diagnosis instrument, and recording the diagnosis address data, thereby obtaining a first data record; sending a first network command to the vehicle connector; obtaining vehicle response data of the target vehicle; recording the vehicle response data to obtain a second data record; sending a second network command to the device connector; according to the first data record and the second data record, executing the initialization of the ISO9141-2 protocol of the equipment connector and the diagnostic instrument, and the initialization of the ISO9141-2 protocol of the vehicle connector and the target vehicle; and performing remote diagnosis on the target vehicle to obtain a target diagnosis result. By automatically executing the initialization process of the diagnosis protocol and remotely diagnosing the vehicle, the efficiency and accuracy of remote diagnosis can be improved.

Description

Technical Field

[0001] The present application relates to the field of vehicle diagnosis technology, and in particular to a remote diagnosis method and device based on the vehicle ISO9141-2 protocol. Background Art

[0002] In traditional vehicle diagnosis, it is usually necessary to drive the vehicle to a repair shop and use a diagnostic instrument to perform vehicle diagnosis operations through a physical connection. When the vehicle is in a remote area or cannot be driven due to a malfunction, remote diagnosis technology is required to perform vehicle diagnosis operations. However, in the existing remote diagnosis process, there may be a large network delay, which reduces the efficiency and accuracy of remote diagnosis.

[0003] Therefore, how to improve the efficiency and accuracy of remote diagnosis needs to be solved urgently. Summary of the invention

[0004] The embodiment of the present application provides a remote diagnosis method and device based on the vehicle ISO9141-2 protocol. By automating the initialization process of the diagnostic protocol and performing remote diagnosis on the vehicle, it 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.

[0005] In a first aspect, an embodiment of the present application provides a remote diagnosis method based on the vehicle ISO9141-2 protocol, which is applied to a server of a remote diagnosis system, wherein the remote diagnosis system further includes a target vehicle, a vehicle connector, a device connector, and a diagnostic instrument, wherein the target vehicle is connected to the vehicle connector via a first K line, the diagnostic instrument is connected to the device connector via a second K line, and the vehicle connector and the device connector are communicatively connected to the server, wherein the method includes:

[0006] Acquiring diagnostic address data of the diagnostic instrument, and recording the diagnostic address data to obtain a first data record;

[0007] Sending 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;

[0008] Acquire vehicle response data of a target vehicle; the vehicle response data is response data generated by the target vehicle for the first data record;

[0009] Recording the vehicle response data to obtain a second data record;

[0010] Sending 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;

[0011] 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 according to the first data record and the second data record;

[0012] The target vehicle is remotely diagnosed to obtain a target diagnosis result.

[0013] In a second aspect, an embodiment of the present application provides a remote diagnostic device based on the vehicle ISO9141-2 protocol, which is applied to a server of a remote diagnostic system, wherein the remote diagnostic system further comprises a target vehicle, a vehicle connector, a device connector, and a diagnostic instrument, wherein the target vehicle is connected to the vehicle connector via a first K line, 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, and the device comprises a first acquisition module, a first sending module, a second acquisition module, a data recording module, a second sending 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 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;

[0016] The second acquisition module is used to acquire vehicle response data of the target vehicle; the vehicle response data is 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 according to the first data record and the second data record;

[0020] The remote diagnosis module is used to perform remote diagnosis on the target vehicle to obtain a target diagnosis result.

[0021] In a third aspect, an embodiment of the present application provides an electronic device, comprising 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 program includes instructions for executing the steps of any method in the first aspect of the embodiment of the present application.

[0022] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program for electronic data exchange, wherein the computer program enables a computer to execute part or all of the steps described in any method of the first aspect of the embodiment of the present application.

[0023] In a fifth aspect, an embodiment of the present application provides a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to cause a computer to execute some or all of the steps described in any method of the first aspect of the embodiment of the present application. The computer program product may be a software installation package.

[0024] By implementing the embodiments of the present application, the initialization process of the diagnostic protocol can be automatically executed 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. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0026] Figure 1 is a system architecture diagram of a remote diagnosis system provided by an embodiment of the present application;

[0027] Figure 2 is a structural schematic diagram of an electronic device provided in an embodiment of the present application;

[0028] Figure 3It is a flowchart of a remote diagnosis method based on vehicle ISO9141-2 protocol provided in an embodiment of the present application;

[0029] Figure 4 It is a flow chart of a communication protocol initialization process provided by an embodiment of the present application;

[0030] Figure 5 It is a time series flow chart of a data sending process provided by an embodiment of the present application;

[0031] Figure 6 This is a flow chart of determining the target W4-2 duration provided by an embodiment of the present 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 the present application. DETAILED DESCRIPTION

[0033] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0034] The terms "first", "second", etc. in the specification and claims of this application and the above-mentioned drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally includes steps or units that are not listed, or optionally includes other steps or units inherent to these processes, methods, products or devices.

[0035] It should be understood that the term "and / or" in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article indicates that the associated objects before and after are in an "or" relationship. The "plurality" appearing in the embodiments of the present application refers to two or more.

[0036] In the embodiments of the present application, "at least one item" or similar expressions refer to any combination of these items, including any combination of single items or plural items, and refer to one or more, and multiple refers to two or more. For example, at least one item of a, b, or c can represent the following seven situations: a, b, c, a and b, a and c, b and c, a, b, and c. Among them, each of a, b, and c can be an element or a set containing one or more elements.

[0037] The "connection" that appears in the embodiments of the present application refers to various connection methods such as direct connection or indirect connection to achieve communication between devices, and the embodiments of the present application do not impose any limitations on this.

[0038] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0039] The following is an explanation of the relevant terms involved in this application, as follows:

[0040] ISO9141-2 protocol: refers to the communication protocol and electrical characteristics of the data link layer and physical layer in the vehicle diagnostic system, ensuring the compatibility and interoperability between automobile manufacturers and diagnostic equipment suppliers, so that diagnostic equipment produced by different manufacturers can perform fault diagnosis, parameter reading and control operations on various vehicles that meet the standard.

[0041] In traditional vehicle diagnosis, it is usually necessary to drive the vehicle to a repair shop and use a diagnostic instrument to perform diagnostic operations on the vehicle through a physical connection. When the vehicle is in a remote area or cannot be driven due to a malfunction, remote diagnostic technology is required to perform diagnostic operations on the vehicle. However, in the existing remote diagnosis process, there may be a large network delay, which reduces the efficiency and accuracy of remote diagnosis. Therefore, how to improve the efficiency and accuracy of remote diagnosis needs to be solved urgently.

[0042] To solve the above problems, an embodiment of the present application provides a remote diagnosis method and device based on the vehicle ISO9141-2 protocol, which is applied to a server of a remote diagnosis system. The remote diagnosis 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, the diagnostic instrument is connected to the device connector via a second K line, and the vehicle connector and the device connector are communicatively connected to the server. First, the diagnostic address data of the diagnostic instrument is obtained, and the diagnostic address data is recorded to obtain a 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 record the first data record in the first network command The device connector sends the second data record to the target vehicle; then, obtains the vehicle response data of the target vehicle; the vehicle response data is the response data generated by the target vehicle for the first data record; records the vehicle response data to obtain a second data record; 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; 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 according to the first data record and the second data record; finally, remotely diagnoses the target vehicle to obtain the target diagnostic result. By automating the initialization process of the diagnostic protocol and remotely diagnosing the vehicle, not only the reliability of data transmission and the overall efficiency of remote diagnosis are improved, but also the remote diagnosis results of the vehicle are made more accurate.

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

[0044] Among them, the target vehicles include but are not limited to cars, vans, and trucks. The target vehicles include multiple electronic control units that are managed together, covering multiple key areas such as engine control, transmission control, braking system, and body electronics. They can collect and process data from various vehicle sensors and accurately control the vehicle's operating status based on preset logic. During the remote diagnosis process, after receiving a diagnostic request from the vehicle connector, the relevant electronic control unit will quickly extract the required information from its own storage unit based on the request instruction, such as fault codes, real-time operating parameters, etc., and organize and package these data and transmit them back to other components of the diagnostic system through the vehicle connector. For example, the engine's electronic control unit can provide key data such as engine speed, throttle opening, and fuel injection amount, thereby reflecting the current working condition of the engine.

[0045] Among them, the vehicle connector can receive network commands from the server, parse the instructions and data therein, and convert them into a format that can be recognized by the electronic control unit inside the vehicle, and accurately transmit them to the target electronic control unit. The vehicle connector can also receive response data from the electronic control unit of the target vehicle, and encapsulate and format it according to the communication protocol requirements of the remote diagnosis system to ensure that the data is accurately transmitted to the server. For example, when the vehicle connector receives a fault code read request forwarded by the server, it will convert the request into an instruction that complies with the vehicle's internal communication protocol and send it to the corresponding electronic control unit, and then organize the fault code data returned by the electronic control unit into a format that can be recognized by the system and send it back to the server. It should be noted that the communication protocol of the remote diagnosis system includes but is not limited to the ISO9141-2 protocol, which is not specifically limited here.

[0046] Among them, the diagnostic instrument is the main tool for maintenance personnel to interact with the remote diagnostic system. It has an intuitive human-computer interaction interface, such as display screen, buttons or touch screen, which is convenient for maintenance personnel to operate and view diagnostic results. The diagnostic instrument has built-in rich diagnostic software and database, covering diagnostic knowledge and fault code analysis information of various vehicle brands and models. The diagnostic instrument can initiate various diagnostic requests, such as reading fault codes, real-time data monitoring, and performing specific diagnostic tests. The diagnostic instrument will generate corresponding diagnostic instructions and data based on user operations and pass them to the target vehicle through the device connector and server. After receiving the vehicle response data returned by the device connector, the diagnostic instrument deeply parses and analyzes the data based on the internal database, and presents the diagnostic results in an intuitive and easy-to-understand way, such as the cause of the fault, the location of the fault, and maintenance suggestions, to provide maintenance personnel with accurate maintenance guidance. For example, when diagnosing the vehicle engine, the diagnostic instrument displays the fault code "P0300" and prompts "random engine misfire", and gives possible causes of the fault, such as spark plug failure, fuel injector blockage, etc., as well as corresponding maintenance suggestions.

[0047] Among them, the device connector receives the diagnostic request sent by the diagnostic instrument, which contains key information such as diagnostic address data, and performs preliminary processing and recording of the data to create corresponding data records, providing an important basis for subsequent operations. Then, the device connector encapsulates the processed request data into a network command and forwards it to the vehicle connector through the server. When the device connector receives the vehicle response data from the server, it will accurately pass it to the diagnostic instrument to ensure that the diagnostic instrument can obtain relevant information about the target vehicle in a timely manner.

[0048] Among them, the server has high-performance computing power and large-capacity data storage capacity, and can 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 forwards the data to the vehicle connector quickly and accurately based on the network address information of the vehicle connector. At the same time, the server promptly transmits the vehicle response data returned by the vehicle connector to the device connector to ensure efficient flow of data between the various components of the system. In addition, the server is also responsible for managing and maintaining various types of data in the system, including device information, vehicle information, diagnostic records, etc., to provide strong support for the operation of the system and data analysis. It should be noted that the network communication between the vehicle connector and the device connector includes but is not limited to: server data transfer, P2P communication, wired network connection, 4G / 5G network connection and other network communication technologies, which are not specifically limited here.

[0049] In one possible embodiment, the diagnostic instrument, as the initiator of the diagnostic operation, can generate diagnostic request data containing key information such as the diagnostic address according to the user's operation. The diagnostic request data is the basis for performing specific diagnostic operations on the target vehicle, for example, requesting to read the fault code or real-time operating parameters of the vehicle's braking system, which is not specifically limited here. The device connector is connected to the diagnostic instrument and is responsible for receiving the diagnostic request data issued by the diagnostic instrument, and performing preliminary processing and packaging on the diagnostic request data, and then sending it to the server through the network. The server can receive the diagnostic request data from the device connector, and then forward the data to the vehicle connector accurately based on information such as the network address of the vehicle connector. Among them, the server can enable device connectors and vehicle connectors in different geographical locations to exchange data across network boundaries, greatly expanding the application scope of the diagnostic system, thereby realizing remote diagnosis of vehicles.

[0050] It can be seen that through the above system architecture, data can be transmitted quickly through the network. After the diagnostic instrument issues a diagnostic request, it is quickly transmitted to the target vehicle through the device connector, server, and vehicle connector. The vehicle response data of the target vehicle can also be quickly transmitted back, thereby improving the efficiency of remote diagnosis.

[0051] Combine the following Figure 2 The electronic device in the embodiment of the present application is described. Figure 2 is a schematic diagram of the structure of an electronic device provided in an embodiment of the present 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, and the processor is communicatively connected with the memory and the communication interface via an internal communication bus.

[0052] Among them, the processor is mainly used for:

[0053] Acquiring diagnostic address data of the diagnostic instrument, and recording the diagnostic address data to obtain a first data record;

[0054] Sending a first network command 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] Acquire vehicle response data of the target vehicle; the vehicle response data is response data generated by the target vehicle for the first data record;

[0056] Recording the vehicle response data to obtain a second data record;

[0057] Sending 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] 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 according to the first data record and the second data record;

[0059] Perform remote diagnosis on the target vehicle and obtain the target diagnosis result.

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

[0061] Among them, the processor can be, for example, a central processing unit (CPU), a general 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 various exemplary logic blocks, units and circuits described in conjunction with the disclosure of this application. The processor can also be a combination that implements a computing function, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and the like. 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 may be a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memories. Among them, the nonvolatile memory may be a read-only memory (ROM), a programmable ROM (PROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of random access memory (RAM) are available, such as static RAM (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM bus random access memory (DR RAM).

[0063] It is understandable that the electronic device may include more or fewer structural elements than those in the above structural block diagram, for example, including a power module, physical buttons, Wi-Fi module, speaker, Bluetooth module, sensor, display module, etc., which are not limited here. It is understandable that the electronic device may be equipped with Figure 1 The system architecture described.

[0064] After understanding the software and hardware architecture of this application, Figure 3 A remote diagnosis method based on the vehicle ISO9141-2 protocol in an embodiment of the present application is described. Figure 3 It is a flow chart of a remote diagnosis method based on the vehicle ISO9141-2 protocol provided by an embodiment of the present application, which is applied to a server of a remote diagnosis system, wherein the remote diagnosis system further comprises a target vehicle, a vehicle connector, a device connector, and a diagnostic instrument, wherein the target vehicle is connected to the vehicle connector via a first K line, the diagnostic instrument is connected to the device connector via a second K line, and the vehicle connector and the device connector are connected to the server in communication, specifically comprising the following steps:

[0065] Step S301, obtaining the diagnostic address data of the diagnostic instrument, and recording the diagnostic address data to obtain a first data record.

[0066] Specifically, after receiving the diagnostic task set by the user, the diagnostic instrument can generate diagnostic address data according to the relevant information of the target vehicle, and then create a specific data structure in the internal storage area to record the diagnostic address data. The data structure may contain multiple fields, and in addition to the diagnostic address data itself, it may also include auxiliary information such as the timestamp of data acquisition, the device number of the diagnostic instrument, and the initiation time of the diagnostic task, thereby obtaining the first data record.

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

[0068] The first network command includes the first data record; and 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, and after receiving the first network command, the vehicle connector can parse the first network command, extract the first data record therein, identify key information such as the diagnostic address contained therein, and then send the first data record to the target vehicle, so that the target vehicle can obtain the diagnostic request issued by the diagnostic instrument, and provide a basis for the accuracy of subsequent remote diagnosis.

[0070] Step S303, obtaining vehicle response data of the target vehicle.

[0071] The vehicle response data is 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 will parse the first data record to generate corresponding vehicle response data. The first data record contains key information related to the diagnosis sent by the diagnostic instrument, such as the diagnostic address, etc. The target vehicle can generate corresponding vehicle response data according to the information and the preset program and logic.

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

[0074] Specifically, the vehicle response data can be recorded in a database and organized in a preset format and structure to facilitate query and retrieval. For example, time sequence, vehicle identification, diagnostic task number, etc. are used as indexes to facilitate rapid location and acquisition of specific second data records.

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

[0076] The second network command includes the second data record; and 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 the second network command to the device connector, and after receiving the second network command, the device connector can parse the second network command, extract the second data record therein, identify the vehicle response data contained therein, and then send the second data record to the diagnostic instrument. The diagnostic instrument can evaluate the operating status of the vehicle based on the vehicle response data, combined with a preset diagnostic algorithm and knowledge base, to determine whether the vehicle has a fault and the type and severity of the fault.

[0078] Step S306, 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 according to 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, and the second data record includes a second synchronization code, a first response keyword, and a second response keyword; the device connector and the diagnostic instrument are initialized with the ISO9141-2 protocol according to the first data record and the second data record, and the vehicle connector and the target vehicle are initialized with the ISO9141-2 protocol. For ease of understanding, please refer to Figure 4 , Figure 4 A schematic diagram of a communication protocol initialization process provided in an embodiment of the present application, wherein the specific steps include:

[0080] A1. If the first diagnosis keyword matches the first response keyword successfully, and the second diagnosis keyword matches the second response keyword successfully, then a data sending operation is performed according to the first data record;

[0081] A2, obtaining the first inverted data byte of the second diagnostic keyword of the diagnostic instrument, and recording the time interval of the receiving time to obtain the first W4-1 duration;

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

[0083] A4. Obtain historical initialization records, and determine the target W4-2 duration according to 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 a 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. Initialize the ISO9141-2 protocol between the vehicle connector and the target vehicle according to the first data record and the second data record.

[0087] In a specific embodiment, first, by comparing the diagnostic keyword and the response keyword, confirm whether the communication information between the diagnostic instrument and the device connector accurately matches. When the first diagnostic keyword matches the first response keyword successfully, and the second diagnostic keyword matches the second response keyword successfully, continue to perform subsequent data sending operations to ensure the accuracy and consistency of data interaction. Then, obtain the first inverted data byte of the second diagnostic keyword of the diagnostic instrument, and record the time interval for receiving the first inverted data byte to obtain the first W4-1 duration. Generate a third network command based on the first W4-1 duration and send it to the vehicle connector. Obtain a historical initialization record, which includes information on the W4-1 duration and W4-2 duration in the last diagnostic process, and then determine the target W4-2 duration based on the historical initialization record. It should be noted that the inverted data byte is a new byte obtained by inverting each bit of the byte bit by bit. For example, the second diagnostic keyword is 10101100. Each bit is inverted, that is, 1 becomes 0, and 0 becomes 1, thereby obtaining the first inverted data byte, which is 01010011.

[0088] Next, according to the determined target W4-2 duration, the second inverted data byte of the diagnostic address is sent to the diagnostic instrument. 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 of the backup connector and the diagnostic instrument, so that the corresponding duration information can be quickly obtained the next time a remote diagnosis is performed, providing a more accurate reference for subsequent diagnostic operations. Finally, the ISO9141-2 protocol of the vehicle connector and the target vehicle is initialized according to the first data record and the second data record.

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

[0090] The first data record further includes W1 duration, W2 duration, and W3 duration. The specific steps of performing the data sending operation according to the first data record include:

[0091] B1, after the keyword is successfully matched, sending the first synchronization code to the diagnostic instrument according to the time interval corresponding to the W1 duration;

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

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

[0094] In a specific embodiment, after the keyword is successfully matched, the first synchronization code is sent to the diagnostic instrument according to the time interval corresponding to the W1 duration. Among them, the role of the first synchronization code is to establish a synchronization reference for subsequent data transmission, so that the diagnostic instrument can accurately identify the starting position and transmission rhythm of subsequent data. In actual communication, the accuracy of the time interval is crucial. If the time interval is set unreasonably, the diagnostic instrument may not be able to correctly receive the synchronization code, thereby 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 best synchronization opportunity may be missed. Then, 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. The setting of the W2 duration ensures that after sending the first synchronization code, there is enough time for the diagnostic instrument to prepare to receive the first diagnostic keyword. Among them, 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 time; if the time interval is too long, the time overhead of the entire communication process will be increased, reducing the diagnostic efficiency. Finally, after sending the first diagnostic keyword, the second diagnostic keyword is sent to the diagnostic instrument at a time interval corresponding to the W3 duration. The control of the W3 duration ensures that the second diagnostic keyword can be sent at the appropriate time after the first diagnostic keyword is sent. This helps to maintain the continuity and accuracy of communication, allowing the diagnostic instrument to receive and process the information of the two diagnostic keywords in the correct order. If the time interval is inappropriate, the diagnostic instrument may receive the two keywords in a disordered order, resulting in reduced efficiency and accuracy of the diagnostic process.

[0095] For easier understanding, see Figure 5 , Figure 5 A time series flow chart of a data sending process provided for an embodiment of the present application shows that in the time axis, the time point corresponding to a successful keyword match is the starting point of the entire process, that is, after the keyword match is successful, the first synchronization code is sent after a duration of W1. Then, after sending the first synchronization code, the first diagnostic keyword is sent after an interval of W2 duration. Finally, after sending the first diagnostic keyword, the second diagnostic keyword is sent after a duration of W3. By performing data sending operations at corresponding time intervals, it is helpful to accurately control the sending rhythm and order of diagnostic instructions, ensure accurate and stable communication between the vehicle connector and the diagnostic equipment, thereby efficiently obtaining the vehicle's diagnostic information, and providing a basis for subsequent fault judgment and maintenance.

[0096] Wherein, the target W4-2 duration is determined according to the historical initialization record. For ease of understanding, please refer to Figure 6 , Figure 6 A flow chart of determining the target W4-2 duration provided in an embodiment of the present application, wherein the specific steps include:

[0097] C1. If the 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 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, the target W4-2 duration is determined to be a preset time interval.

[0099] In a specific embodiment, when there is a reference W4-2 duration 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 there is no reference W4-2 duration in the historical initialization record, and / or the device connector does not receive the reference W4-2 duration from the vehicle connector, the preset time interval is used as the target W4-2 duration. The preset time interval can be 25ms, which is not specifically limited here.

[0100] It can be seen 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 conditions, and by setting a reasonable target W4-2 duration, the stability of communication between the device connector and the diagnostic instrument can be improved, thereby improving the reliability of remote diagnostic operations.

[0101] 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 specifically comprises the following steps:

[0102] D1. If the 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, determining the target W4-1 duration to be the preset time interval;

[0104] D3, sending the third inverted data byte of the second response keyword to the target vehicle according to the target W4-1 duration, and recording 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 according to 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 there is a reference W4-1 duration 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 there is no reference W4-1 duration in the historical initialization record, and / or the vehicle connector does not receive the reference W4-1 duration from the device connector, the preset time interval is used as the target W4-1 duration. Among them, the preset time interval can be 25ms, which 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 at the same time. Among them, the third network command can be obtained, and the historical initialization record can be updated according to the third network command. Then, the fourth inverted data byte of the vehicle address of the target vehicle is obtained, and its receiving time is recorded. Then calculate the time interval between the sending time of the third inverted data byte and the receiving time of the fourth inverted data byte, and determine it as the first W4-2 duration. Finally, a fourth network command is generated according to 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, laying the foundation for subsequent diagnostic data transmission.

[0110] It can be seen that accurate timing control can ensure that the data interaction between the vehicle connector and the target vehicle is carried out according to the predetermined rhythm, so that the two parties can be better synchronized, improve communication efficiency and reliability, and avoid errors in remote diagnosis caused by network delays.

[0111] Step S307, remotely diagnose the target vehicle to obtain a target diagnosis result.

[0112] The step of remotely diagnosing the target vehicle to obtain a diagnosis result specifically includes:

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

[0114] E2. Generate a diagnostic request according to the diagnostic requirement, and send the diagnostic request to the device connector;

[0115] E3. Generate a fifth network command according to the diagnostic request; the fifth network command includes the diagnostic request;

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

[0117] E5. Obtaining a diagnostic response of the target vehicle to the diagnostic request, and generating a sixth network command according to the diagnostic response; the sixth network command includes the diagnostic response;

[0118] E6. Sending the sixth network command to the device connector through the server; 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 according to the diagnostic response.

[0120] In a specific embodiment, first, the diagnostic requirements corresponding to the target vehicle are obtained, wherein the diagnostic requirements can be determined according to the fault phenomenon of the vehicle. For example, if the fault phenomenon is engine shaking, abnormal fuel consumption, etc., the diagnostic requirements can be to diagnose the engine-related systems. In addition, the diagnostic requirements of the target vehicle can also be determined according to the personalized needs of the user, such as the comprehensive inspection required for regular maintenance, which is not specifically limited here. Then, based on the obtained diagnostic requirements, a specific diagnostic request is generated, and the diagnostic request is sent to the device connector. The diagnostic request includes the specific content and requirements of the diagnosis, such as the type of fault code that needs to be read, the parameter category that needs to be monitored, etc. The diagnostic request is then encapsulated into a fifth network command and sent to the vehicle connector, and the vehicle connector can send the diagnostic request in the fifth network command to the target vehicle.

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

[0122] It can be seen that generating diagnostic requests according to specific diagnostic needs avoids unnecessary diagnostic operations, while ensuring a comprehensive inspection of key issues, and making the diagnostic process faster through efficient data transmission and processing mechanisms, allowing users to obtain diagnostic results more quickly.

[0123] The step of determining the target diagnostic result according to the diagnostic response comprises:

[0124] F1. Obtaining target fault codes and target vehicle parameters in the diagnostic response;

[0125] F2. Determine a first diagnostic result corresponding to the target fault code according to a preset mapping relationship between the fault code and the diagnostic result;

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

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

[0128] F5. Determine the target diagnosis result according to the first diagnosis result and the second diagnosis result.

[0129] In a specific embodiment, first, 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 electronic control system detects an abnormality, which can indicate the approximate location or type of the fault; the target vehicle parameters include data such as engine speed, vehicle speed, water temperature, etc. that reflect the real-time operating status of the vehicle. Then, according to the mapping relationship between the preset fault code and the diagnostic result, the first diagnostic result corresponding to the target fault code is determined. Then, the standard parameter range corresponding to the target vehicle is obtained. Among them, each parameter of vehicles of different models has its normal standard parameter range, and the standard parameter range is an important basis for judging whether the vehicle operating state 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 problems in the corresponding aspects, and then the second diagnostic result is obtained. Finally, the first diagnostic result and the second diagnostic result are combined to finally determine the target diagnostic result. If the first diagnostic result and the second diagnostic result are consistent, it can be determined that the target diagnostic result is relatively accurate; if there is a difference between the two, it is necessary to further analyze the possible reasons, such as fault code false alarm, parameter measurement error, etc. In addition, the second diagnostic result can also identify potential faults or performance abnormalities without generating a fault code. For example, although no fault code appears, the vehicle's water temperature parameters are higher than the standard parameter range for a long time, then there may be a problem with the cooling system.

[0130] It can be seen that combining the two methods of fault code analysis and vehicle parameter comparison can diagnose the target vehicle from different angles and improve the accuracy and reliability of remote diagnosis results.

[0131] The above mainly introduces the scheme of the embodiment of the present application from the perspective of the execution process on the method side. It is understandable that, in order to realize the above functions, the electronic device includes a hardware structure and / or software module corresponding to the execution of each function. It should be easily appreciated by those skilled in the art that, in combination with the units and algorithm steps of each example described in the embodiments provided herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present application.

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

[0133] In the case of dividing each functional module into corresponding functional modules, Figure 7 It is a functional module composition block diagram of a remote diagnostic device based on the vehicle ISO9141-2 protocol provided by an embodiment of the present application, which is applied to a server of 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, the diagnostic instrument is connected to the device connector via a second K line, the vehicle connector and the device connector are connected to the server in communication, and the remote diagnostic device 700 based on the vehicle ISO9141-2 protocol includes a first acquisition module 710, a first sending module 720, a second acquisition module 730, a data recording module 740, a second sending 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 response data generated by the target vehicle for 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 diagnosis module 770 is used to perform remote diagnosis on the target vehicle to obtain a target diagnosis result.

[0141] Optionally, the first data record includes a diagnostic address, a first synchronization code, a first diagnostic keyword, and a second diagnostic keyword, and the second data record includes a second synchronization code, a first response keyword, and a second response keyword; in the aspect of executing the initialization of the ISO9141-2 protocol between the device connector and the diagnostic instrument according to the first data record and the second data record, and the initialization of the ISO9141-2 protocol between the vehicle connector and the target vehicle, the initialization module 760 is specifically used for:

[0142] If the first diagnosis keyword matches the first response keyword successfully, and the second diagnosis keyword matches the second response keyword successfully, performing a data sending operation according to the first data record;

[0143] Obtaining the first inverted data byte of the second diagnostic keyword of the diagnostic instrument, and recording the time interval of the receiving time, to obtain a first W4-1 duration;

[0144] generating a third network command according to the first W4-1 duration, and sending the third network command to the vehicle connector;

[0145] Obtain historical initialization records, and determine the target W4-2 duration according to the historical initialization records;

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

[0147] Obtaining a fourth network command, and updating the historical initialization record according to the fourth network command, so as to complete the initialization of the ISO9141-2 protocol between the device connector and the diagnostic instrument;

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

[0149] Optionally, the first data record further includes a W1 duration, a W2 duration, and a W3 duration. In terms of performing the data sending operation according to the first data record, the initialization module 760 is specifically used to:

[0150] After the keyword is successfully matched, 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, sending the first diagnosis keyword to the diagnostic instrument according to the time interval corresponding to the W2 duration;

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

[0153] Optionally, in determining the target W4-2 duration according to the historical initialization record, the initialization module 760 is specifically configured to:

[0154] If the 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 determining the target W4-2 duration to be the reference W4-2 duration;

[0155] If the 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, the target W4-2 duration is determined to be a preset time interval.

[0156] Optionally, in the aspect of executing 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, the initialization module 760 is specifically used for:

[0157] If the reference W4-1 duration exists in the historical initialization record, and the vehicle connector receives the reference W4-1 duration from the device connector, determining the target W4-1 duration to be the reference W4-1 duration;

[0158] 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, determining the target W4-1 duration to be the preset time interval;

[0159] Sending a third inverted data byte of the second response keyword to the target vehicle according to the target W4-1 duration, and recording the sending time of the third inverted data byte;

[0160] Obtaining the third network command, and updating the historical initialization record according to the third network command;

[0161] Obtaining a fourth inverted data byte of the vehicle address of the target vehicle, and recording a receiving time corresponding to the fourth inverted data byte;

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

[0163] A fourth network command is generated according to 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 aspect of remotely diagnosing the target vehicle and obtaining a diagnosis result, the remote diagnosis module 770 is specifically used for:

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

[0166] Generate a diagnostic request according to the diagnostic requirement, and send the diagnostic request to the device connector;

[0167] Generate a fifth network command according to the diagnostic request; the fifth network command includes the diagnostic request;

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

[0169] Obtaining a diagnostic response of the target vehicle to the diagnostic request, and generating a sixth network command according to the diagnostic response; the sixth network command includes the diagnostic response;

[0170] The sixth network command is sent to the device connector through the server; 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 according to the diagnostic response.

[0172] Optionally, in determining the target diagnostic result according to the diagnostic response, the remote diagnosis module 770 is specifically used to:

[0173] Obtaining target fault codes and target vehicle parameters in the diagnostic response;

[0174] Determining a first diagnostic result corresponding to the target fault code according to a preset mapping relationship between the fault code and the diagnostic result;

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

[0176] Comparing the standard parameter range with the target vehicle parameter to obtain a second diagnosis result;

[0177] The target diagnosis result is determined according to the first diagnosis result and the second diagnosis result.

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

[0179] It should be noted that the specific implementation of each operation can adopt the corresponding description of the method embodiment shown above. The remote diagnosis device 700 based on the vehicle ISO9141-2 protocol can be used to execute the above method embodiment of the present application, which will not be repeated here.

[0180] An embodiment of the present application also provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program for electronic data exchange, wherein the computer program enables a computer to execute part or all of the steps of any method recorded in the above method embodiments, and the above computer includes an electronic device.

[0181] The embodiment of the present application also provides a computer program product, the computer program product includes a non-transitory computer-readable storage medium storing a computer program, the computer program is operable to cause a computer to execute some or all of the steps of any method described in the method embodiment. The computer program product may be a software installation package, and the computer includes an electronic device.

[0182] It should be noted that, for the above-mentioned various embodiments, for the sake of simple description, they are all expressed as a series of action combinations. Those skilled in the art should be aware that the present application is not limited by the described order of actions, because some steps in the embodiments of the present application can be performed in other orders or simultaneously. In addition, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions, steps, modules or units involved are not necessarily required by the embodiments of the present application.

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

[0184] Those skilled in the art can understand that to implement all or part of the processes in the above-mentioned embodiments, the processes can be completed by computer programs to instruct related hardware, and the programs can be stored in computer-readable storage media. When the programs are executed, they can include the processes of the above-mentioned method embodiments. The aforementioned storage media include: ROM or random access memory RAM, magnetic disk or optical disk and other media that can store program codes.

[0185] The steps of the method or algorithm described in the embodiments of the present application can be implemented in hardware or by executing software instructions by a processor. The software instructions can be composed of corresponding software modules, and the software modules can be stored in RAM, flash memory, ROM, EPROM, electrically erasable programmable read-only memory (electrically EPROM, EEPROM), registers, hard disks, mobile hard disks, read-only compact disks (CD-ROMs) or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and the storage medium can be located in an ASIC. In addition, the ASIC can be located in a terminal device or a management device. Of course, the processor and the storage medium can also be present in a terminal device or a management device as discrete components.

[0186] Those skilled in the art should be aware that in one or more of the above examples, the functions described in the embodiments of the present application can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiments of the present application is generated in whole or in part. 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 computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, computer, server, or data center to another website site, computer, server, or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0187] The modules / units included in the devices and products described in the above embodiments may be software modules / units or hardware modules / units, or may be partially software modules / units and partially hardware modules / units. For example, for the devices and products applied to or integrated in the chip, the modules / units included therein may all be implemented in the form of hardware such as circuits, or at least some of the modules / units may be implemented in the form of software programs, which run on the processor integrated inside the chip, and the remaining (if any) modules / units may be implemented in the form of hardware such as circuits; for the devices and products applied to or integrated in the chip module, the modules / units included therein may all be implemented in the form of hardware such as circuits, and different modules / units may be located in the same component (such as a chip, circuit module, etc.) or in different components of the chip module, or at least some of the modules / units may be implemented in the form of software programs. The software programs run on the processor integrated inside the chip, and the remaining (if any) modules / units may be implemented in the form of hardware such as circuits. It is implemented in the form of a software program, which runs on a processor integrated inside the chip module, and the remaining (if any) modules / units can be implemented in hardware such as circuits; for various devices and products applied to or integrated in the terminal equipment, the various modules / units contained therein can be implemented in hardware such as circuits, and different modules / units can be located in the same component (for example, chip, circuit module, etc.) or in different components in the terminal equipment, or, at least some modules / units can be implemented in the form of a software program, which runs on a processor integrated inside the terminal equipment, and the remaining (if any) modules / units can be implemented in hardware such as circuits.

[0188] The specific implementation methods described above further illustrate the purpose, technical solutions and beneficial effects of the embodiments of the present application. It should be understood that the above description is only the specific implementation method of the embodiments of the present application and is not intended to limit the protection scope of the embodiments of the present application. Any modifications, equivalent substitutions, improvements, etc. made on the basis of the technical solutions of the embodiments of the present application should be included in the protection scope of the embodiments of the present application.

Claims

1. A remote diagnosis method based on vehicle ISO9141-2 protocol, characterized in that: A server applied to a remote diagnostic system, the remote diagnostic system further comprising 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, 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, and the method comprises: Acquiring diagnostic address data of the diagnostic instrument, and recording the diagnostic address data to obtain a first data record; Sending 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; Acquire vehicle response data of a target vehicle; the vehicle response data is response data generated by the target vehicle for the first data record; Recording the vehicle response data to obtain a second data record; Sending 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; 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 according to the first data record and the second data record; The target vehicle is remotely diagnosed to obtain a target diagnosis result.

2. The method according to 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, and 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 according to the first data record and the second data record includes: If the first diagnosis keyword matches the first response keyword successfully, and the second diagnosis keyword matches the second response keyword successfully, performing a data sending operation according to the first data record; Obtaining the first inverted data byte of the second diagnostic keyword of the diagnostic instrument, and recording the time interval of the receiving time, to obtain a first W4-1 duration; generating a third network command according to the first W4-1 duration, and sending the third network command to the vehicle connector; Obtain historical initialization records, and determine the target W4-2 duration according to the historical initialization records; Sending the second inverted data byte of the diagnostic address to the diagnostic instrument according to the target W4-2 duration; Obtaining a fourth network command, and updating the historical initialization record according to the fourth network command, so as to complete the initialization of the ISO9141-2 protocol between the device connector and the diagnostic instrument; Initialization of the ISO9141-2 protocol of the vehicle connector with the target vehicle is performed based on the first data record and the second data record.

3. The method according to claim 2, characterized in that The first data record further includes a W1 duration, a W2 duration, and a W3 duration. The performing of the data sending operation according to the first data record includes: After the keyword is successfully matched, 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, sending the first diagnosis keyword to the diagnostic instrument according to the time interval corresponding to the W2 duration; After sending the first diagnosis keyword, the second diagnosis keyword is sent to the diagnostic instrument according to the time interval corresponding to the W3 duration.

4. The method according to claim 2, characterized in that The determining of the target W4-2 duration according to the historical initialization record includes: If the 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 determining the target W4-2 duration to be the reference W4-2 duration; If the 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, the target W4-2 duration is determined to be a preset time interval.

5. The method according to claim 4, characterized in that 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 includes: If the reference W4-1 duration exists in the historical initialization record, and the vehicle connector receives the reference W4-1 duration from the device connector, determining the target W4-1 duration to be the reference W4-1 duration; 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, determining the target W4-1 duration to be the preset time interval; Sending a third inverted data byte of the second response keyword to the target vehicle according to the target W4-1 duration, and recording the sending time of the third inverted data byte; Obtaining the third network command, and updating the historical initialization record according to the third network command; Obtaining a fourth inverted data byte of the vehicle address of the target vehicle, and recording a receiving time corresponding to the fourth inverted data byte; Determine the time interval between the sending time and the receiving time as the first W4-2 duration; A fourth network command is generated according to 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 to 5, characterized in that: The remote diagnosis of the target vehicle to obtain a diagnosis result includes: Obtaining diagnostic requirements corresponding to the target vehicle; Generate a diagnostic request according to the diagnostic requirement, and send the diagnostic request to the device connector; Generate a fifth network command according to the diagnostic request; the fifth network command includes the diagnostic request; Sending the fifth network command to the vehicle connector through the server; the vehicle connector is also used to send the diagnostic request in the fifth network command to the target vehicle; Obtaining a diagnostic response of the target vehicle to the diagnostic request, and generating a sixth network command according to the diagnostic response; the sixth network command includes the diagnostic response; The sixth network command is sent to the device connector through the server; 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 according to the diagnostic response.

7. The method according to claim 6, characterized in that The determining the target diagnostic result according to the diagnostic response includes: Obtaining target fault codes and target vehicle parameters in the diagnostic response; Determining a first diagnostic result corresponding to the target fault code according to a preset mapping relationship between the fault code and the diagnostic result; Obtaining a standard parameter range corresponding to the target vehicle; Comparing the standard parameter range with the target vehicle parameter to obtain a second diagnosis result; The target diagnosis result is determined according to the first diagnosis result and the second diagnosis result.

8. A remote diagnostic device based on vehicle ISO9141-2 protocol, characterized in that: A server applied to a remote diagnosis system, the remote diagnosis system further comprising 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, 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 comprising a first acquisition module, a first sending module, a second acquisition module, a data recording module, a second sending module, an initialization module, and a remote diagnosis 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 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; The second acquisition module is used to acquire vehicle response data of the target vehicle; the vehicle response data is 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 according to the first data record and the second data record; The remote diagnosis module is used to perform remote diagnosis on the target vehicle to obtain a target diagnosis result.

9. An electronic device, characterized in that: include: A processor, a memory, a 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 comprising instructions for executing the steps in the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, wherein the computer program includes program instructions, and when the program instructions are executed by a processor, the processor is caused to perform the method according to any one of claims 1 to 7.

Images