Remote diagnosis method based on diagnosis protocol and related device

Abstract

The invention discloses a remote diagnosis method based on a diagnosis protocol, and the method comprises the steps: obtaining request data for a target electronic control unit in a target vehicle, carrying out the coding of the request data based on a preset diagnosis protocol, and obtaining a request instruction corresponding to the target electronic control unit, determining whether a first response instruction corresponding to the target electronic control unit is recorded in the equipment connector or not based on the request instruction, if yes, determining response record data corresponding to the target electronic control unit based on the first response instruction, and if not, sending the request instruction to the vehicle connector, enabling the vehicle connector to determine target response data corresponding to the target electronic control unit based on the request instruction, and enabling the target diagnostic instrument to carry out the diagnosis operation of the target electronic control unit based on the response record data or the target response data, and obtaining a diagnosis result. By adopting the embodiment of the invention, the remote diagnosis efficiency is improved.

Description

Technical Field

[0001] The present invention relates to the technical field of automotive remote diagnosis, and particularly to a remote diagnosis method and related device based on a diagnostic protocol. Background Art

[0002] With the continuous development of automotive technology, the electronic control system of vehicles has become increasingly complex, and the electronic control unit (ECU) plays a key role in vehicle operation and performance optimization. To ensure the safe and reliable operation of vehicles, it is crucial to diagnose the status and problems of vehicle electronic control units in a timely and accurate manner. With the progress of communication technology, remote diagnosis has gradually become an important development direction in the field of vehicle diagnosis. During the remote diagnosis process, due to data incompatibility, the efficiency of remote diagnosis is relatively low. How to improve the efficiency of remote diagnosis is an urgent problem to be solved. Summary of the Invention

[0003] An embodiment of the present application provides a remote diagnosis method based on a diagnostic protocol, which improves the efficiency of remote diagnosis.

[0004] In a first aspect, an embodiment of the present application provides a remote diagnosis method based on a diagnostic protocol, which is applied to a device connector. The device connector is connected to a target diagnostic instrument, and a vehicle connector is connected to a target vehicle. The target diagnostic instrument and the target vehicle are communicatively connected through the device connector and the vehicle connector. The method includes:

[0005] Obtain request data for a target electronic control unit in the target vehicle;

[0006] Encode the request data based on a preset diagnostic protocol to obtain a request instruction corresponding to the target electronic control unit;

[0007] Determine whether a first response instruction corresponding to the target electronic control unit is recorded in the device connector based on the request instruction;

[0008] If so, determine response record data corresponding to the target electronic control unit based on the first response instruction, and send the response record data to the target diagnostic instrument, so that the target diagnostic instrument performs a diagnostic operation on the target electronic control unit based on the response record data to obtain a first diagnostic result;

[0009] If not, send the request instruction to the vehicle connector, so that the vehicle connector determines target response data corresponding to the target electronic control unit based on the request instruction;

[0010] Receive the target response data from the vehicle connector and send the target response data to the target diagnostic instrument, so that the target diagnostic instrument performs a diagnostic operation on the target electronic control unit based on the target response data to obtain a second diagnostic result.

[0011] In a second aspect, an embodiment of the present application provides a remote diagnostic method based on a diagnostic protocol, which is obtained after encoding request data corresponding to a target electronic control unit in a target vehicle according to a preset diagnostic protocol;

[0012] Determine target response data corresponding to the target electronic control unit based on the request instruction;

[0013] Send the target response data to the device connector, so that the device connector sends the target response data to the target diagnostic instrument, so that the target diagnostic instrument performs a diagnostic operation on the target electronic control unit based on the target response data to obtain a target diagnostic result; the device connector is connected to the target diagnostic instrument.

[0014] In a third aspect, an embodiment of the present application provides a remote diagnostic device based on a diagnostic protocol, and the device includes: an acquisition unit and a processing unit;

[0015] The acquisition unit is used to acquire request data for a target electronic control unit in the target vehicle;

[0016] The processing unit is used to encode the request data according to a preset diagnostic protocol to obtain a request instruction corresponding to the target electronic control unit;

[0017] Determine whether a first response instruction corresponding to the target electronic control unit is recorded in the device connector based on the request instruction;

[0018] If so, determine response record data corresponding to the target electronic control unit based on the first response instruction, and send the response record data to the target diagnostic instrument, so that the target diagnostic instrument performs a diagnostic operation on the target electronic control unit based on the response record data to obtain a first diagnostic result;

[0019] If not, send the request instruction to the vehicle connector, so that the vehicle connector determines target response data corresponding to the target electronic control unit based on the request instruction;

[0020] Receive the target response data from the vehicle connector and send the target response data to the target diagnostic instrument, so that the target diagnostic instrument performs a diagnostic operation on the target electronic control unit based on the target response data to obtain a second diagnostic result.

[0021] In a fourth aspect, an embodiment of the present application provides a remote diagnosis device based on a diagnosis protocol, the device comprising: a receiving unit and a processing unit;

[0022] The receiving unit is configured to receive a request instruction from a device connector; the request instruction is obtained by encoding corresponding request data of a target electronic control unit in the target vehicle based on a preset diagnosis protocol;

[0023] The processing unit is configured to determine target response data corresponding to the target electronic control unit based on the request instruction;

[0024] Send the target response data to the device connector, so that the device connector sends the target response data to the target diagnostic instrument, so that the target diagnostic instrument performs a diagnostic operation on the target electronic control unit based on the target response data to obtain a target diagnostic result; the device connector is connected to the target diagnostic instrument.

[0025] In a fifth 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 to enable the electronic device to execute the methods of the first aspect and the second aspect.

[0026] In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium storing a computer program, which is executed by a processor to implement the methods of the first aspect and the second aspect.

[0027] In a seventh aspect, an embodiment of the present application provides a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program, so that a computer executes the methods of the first aspect and the second aspect.

[0028] Implementing the embodiments of the present application has the following beneficial effects:

[0029] It can be seen that the remote diagnosis method based on the diagnostic protocol described in the embodiments of the present application is applied to a device connector and a vehicle connector. The device connector is connected to a target diagnostic instrument, and the vehicle connector is connected to a target vehicle. The target diagnostic instrument and the target vehicle are communicatively connected through the device connector and the vehicle connector. First, the device connector obtains request data for a target electronic control unit in the target vehicle, encodes the request data based on a preset diagnostic protocol to obtain a request instruction corresponding to the target electronic control unit, and then determines whether a first response instruction corresponding to the target electronic control unit is recorded in the device connector based on the request instruction. If so, response record data corresponding to the target electronic control unit is determined based on the first response instruction, and the response record data is sent to the target diagnostic instrument, so that the target diagnostic instrument performs a diagnostic operation on the target electronic control unit based on the response record data to obtain a first diagnostic result. If not, the request instruction is sent to the vehicle connector, so that the vehicle connector determines target response data corresponding to the target electronic control unit based on the request instruction. The vehicle connector receives the request instruction from the device connector, then determines the target response data corresponding to the target electronic control unit based on the request instruction, and sends the target response data to the device connector. The device connector receives the target response data from the vehicle connector and sends the target response data to the target diagnostic instrument, so that the target diagnostic instrument performs a diagnostic operation on the target electronic control unit based on the target response data to obtain a second diagnostic result. Description of the Drawings

[0030] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the background art, the drawings required for use in the embodiments of the present application or the background art will be described below.

[0031] Figure 1 is a schematic structural diagram of a remote diagnosis system based on a diagnostic protocol provided by an embodiment of the present application;

[0032] Figure 2 is a flowchart of a remote diagnosis method based on a diagnostic protocol provided by an embodiment of the present application;

[0033] Figure 3 is a flowchart of determining a request instruction provided by an embodiment of the present application;

[0034] Figure 4 is an example diagram of a display interface for a target vehicle busy prompt message provided by an embodiment of the present application;

[0035] Figure 5It is a flowchart of another remote diagnosis method based on a diagnostic protocol provided by an embodiment of the present application;

[0036] Figure 6 It is a schematic structural diagram of a remote diagnosis device based on a diagnostic protocol provided by an embodiment of the present application;

[0037] Figure 7 It is a schematic structural diagram of another remote diagnosis device based on a diagnostic protocol provided by an embodiment of the present application;

[0038] Figure 8 It is a schematic structural diagram of an electronic device provided by an embodiment of the present application. Specific Embodiments

[0039] In order to enable those skilled in the art to better understand the solutions of the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present application without creative efforts fall within the scope of protection of the present application.

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

[0041] Referring to "embodiment" herein means that a specific feature, structure or characteristic described in connection with the embodiment can be included in at least one embodiment of the present application. The phrase appears in various places in the specification and does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment mutually exclusive with other embodiments. Those skilled in the art will explicitly and implicitly understand that the embodiments described herein can be combined with other embodiments.

[0042] First, the relevant terms involved in the present application are explained:

[0043] ECU: Electronic Control Unit (ECU) is an important component in a vehicle. It is actually a microcomputer that has the functions of processing input signals, calculating and making decisions according to preset programs, and outputting control instructions. In a vehicle, there are multiple ECUs with different functions, such as the Engine Control Unit (ECU), the Transmission Control Unit (TCU), the Anti-lock Braking System Control Unit (ABS ECU), etc. Taking the engine control unit as an example, it receives signals from various sensors (such as oxygen sensors, intake air flow sensors, throttle position sensors, etc.). These signals contain information about the engine operating state, such as speed, load, temperature, etc. The ECU calculates and analyzes based on these input signals through the control programs and algorithms stored internally, and then sends control instructions to actuators (such as fuel injectors, ignition coils, etc.) to achieve precise control of the engine, thereby optimizing the engine's performance, fuel economy, and emissions, etc.

[0044] OBD: On-Board Diagnostics (OBD) is a system used to monitor the vehicle's operating condition and diagnose vehicle faults. Through the sensors and computers in the vehicle, the on-board diagnostic system can detect and store data related to vehicle emissions, engine performance, transmission system, etc., and provide trouble codes when the vehicle has a fault, helping technicians quickly locate and repair problems.

[0045] CAN Bus: Controller Area Network (CAN) is a serial communication network that effectively supports distributed control or real-time control. The CAN bus has advantages such as high reliability, strong real-time performance, relatively long transmission distance, and strong anti-electromagnetic interference ability. It has been widely used in fields such as automotive electronics, industrial automation, and aerospace. In a vehicle, the CAN bus is used to connect various electronic control units to achieve data exchange and collaborative work between them, such as the engine control unit, the transmission control unit, the brake system control unit, etc. CANBus usually refers to the CAN bus, which is a field bus widely used in fields such as automotive and industrial control to achieve efficient and reliable data communication between each control unit. The CANBus adopts a multi-master competitive bus structure, and data is transmitted between nodes through differential signals, with high anti-interference ability and real-time performance, meeting the requirements of real-time control, and also having error detection, error notification, and error recovery mechanisms.

[0046] Please refer to Figure 1 , Figure 1 which is a schematic structural diagram of a remote diagnosis system based on a diagnostic protocol provided by an embodiment of the present application. The remote diagnosis system 10 based on the diagnostic protocol includes a target vehicle 101, a vehicle connector 102, a device connector 103, and a target diagnostic instrument 104.

[0047] In this embodiment, a CANBus filter is configured in the vehicle connector 102 to form a CANBus network, which can receive CANBus messages and achieve network communication with the device connector 103. The vehicle connector 102 can withstand various adverse factors such as vibration, temperature change, humidity, dust, and chemical substances during vehicle driving, has good corrosion resistance, and also has a high protection level and high current and high voltage carrying capacity. A CANBus termination resistor is configured in the device connector 103, which can receive the CANBus diagnostic messages of the target diagnostic instrument 104. The device connector 103 needs to be compatible with different types and brands of vehicle connectors to achieve wide application, facilitate quick connection and disconnection with the vehicle during diagnosis and testing, can stably and high-speed transmit the data signals required for diagnosis and testing, can withstand frequent plugging and unplugging operations, and is not easily damaged.

[0048] In this embodiment, the device connector 103 is connected to the target diagnostic instrument 104, and the vehicle connector 102 is connected to the target vehicle 101. The target diagnostic instrument 104 and the target vehicle 101 are communicatively connected through the device connector 103 and the vehicle connector 102. First, request data for the target electronic control unit in the target vehicle 101 is obtained through the device connector 103, and the request data is encoded based on a preset diagnostic protocol to obtain a request instruction corresponding to the target electronic control unit. Then, it is determined whether a first response instruction corresponding to the target electronic control unit is recorded in the device connector 103 based on the request instruction. If so, response record data corresponding to the target electronic control unit is determined based on the first response instruction, and the response record data is sent to the target diagnostic instrument 104, so that the target diagnostic instrument 104 performs a diagnostic operation on the target electronic control unit based on the response record data to obtain a first diagnostic result. If not, the request instruction is sent to the vehicle connector 102, so that the vehicle connector 102 determines target response data corresponding to the target electronic control unit based on the request instruction. The vehicle connector 102 receives the request instruction from the device connector 103, then determines the target response data corresponding to the target electronic control unit based on the request instruction, and sends the target response data to the device connector 103. The device connector 103 receives the target response data from the vehicle connector 102 and sends the target response data to the target diagnostic instrument 104, so that the target diagnostic instrument 104 performs a diagnostic operation on the target electronic control unit based on the target response data to obtain a second diagnostic result, improving the efficiency of remote diagnosis.

[0049] Please refer to Figure 2 , Figure 2 which is a flowchart of a remote diagnosis method based on a diagnostic protocol provided by an embodiment of the present application, including but not limited to the following steps:

[0050] S201: Obtain request data for the target electronic control unit in the target vehicle.

[0051] In this embodiment, the request data may include the channel identifier or number of the electronic control unit to clarify the target channel to be accessed, the requirements for the data transfer rate of the channel, and the request for the access privilege level of the channel, such as read-only, read-write, etc. It may also include the network address or identifier of the target electronic control unit, the specific parameter settings of the communication protocol, such as the baud rate, parity bit, timeout setting for connection, etc. It may also include the format and content of the test data packet for verifying the validity of the connection, the expected response time range, the strategy settings for error detection and recovery, etc. The request data for the target electronic control unit in the target vehicle can be obtained through the following several methods: Input through the diagnostic instrument interface: The operator manually inputs specific requests related to the target electronic control unit through the operation interface of the target diagnostic instrument, such as selecting the type of electronic control unit to be diagnosed, specifying the parameters to be read or the tests to be executed; Preset diagnostic templates: A series of common diagnostic templates are preset in the diagnostic instrument, and the user can select the template related to the target electronic control unit from them to generate the corresponding request data; Vehicle diagnostic database: Extract the request data related to the target vehicle and the target electronic control unit from the database storing vehicle models, configurations, and common fault information; Remote server push: Receive the request data customized for a specific target vehicle and electronic control unit from the remote diagnostic service server through a network connection; Trigger by the vehicle self-diagnosis system: After the vehicle's own self-diagnosis system detects an abnormality, it automatically triggers the sending of request data related to the relevant electronic control unit to the diagnostic instrument, which is not limited here.

[0052] S202: Encode the request data based on a preset diagnostic protocol to obtain a request instruction corresponding to the target electronic control unit.

[0053] In this embodiment, please refer to Figure 3 , Figure 3 is a flowchart for determining a request instruction provided by an embodiment of the present application, including but not limited to the following steps:

[0054] S301: Classify and compress the request data to obtain multiple groups of compressed data.

[0055] In this embodiment, first, the request data is analyzed and classified. The classification basis can be the type of data (such as sensor data, control instruction data, etc.), the source of the data (different electronic control units or sensors), the importance level of the data, etc. Then, the classified data is compressed. Specifically, first, redundant data is removed by checking whether there is duplicate or unnecessary information in the data and removing it. Then, data encoding compression is performed. Using specific encoding methods such as Huffman coding, run-length coding, etc., the data is re-encoded to reduce the storage space. Next, dictionary compression is carried out by establishing a dictionary of common data patterns and representing common data patterns with shorter codes. Finally, lossy compression is performed, allowing a certain degree of loss of data accuracy to achieve a higher compression ratio. After classification and selection of appropriate compression methods, each type of data is compressed separately to obtain multiple sets of compressed data. It is also possible to classify and compress based on the change frequency of the data. Data with a lower change frequency is grouped together, such as the basic configuration information of the vehicle, and compressed using a lower sampling frequency or a longer coding interval. For data with a higher change frequency, such as real-time sensor values, a more efficient compression algorithm or a higher compression frequency is used. It is also possible to classify and compress according to the numerical range of the data. The data is classified according to the value range. For example, data with a large value and a wide change range is compressed using floating-point numbers, while for cases with a small and limited value, integer compression is used. It is also possible to classify and compress based on the update period of the data. Data with a longer update period is classified separately and a relatively simple but high-compression-ratio method is used. For data that is updated frequently, the speed of compression and decompression is emphasized, and a fast compression algorithm is adopted. Prediction coding can also be used. By analyzing the historical trends and patterns of the data, the future data values are predicted, and only the difference between the actual value and the predicted value is transmitted, thereby reducing the amount of data. Block compression can also be adopted, where the data is divided into blocks of a fixed size, and each block is compressed separately. An appropriate compression method is selected according to the characteristics of the data within the block, which is not limited here.

[0056] It can be seen that by classifying and compressing the request data, multiple sets of compressed data are obtained. The multiple sets of compressed data occupy less storage space, which is beneficial to storing more relevant data in the limited storage resources of the device and facilitating subsequent processing and transmission. After classification and compression, the structure of the data is more regular, and during the subsequent process of encoding and combining into request instructions, the possibility of transmission errors and data loss can be reduced. The multiple sets of data after classification and compression can be processed and integrated more quickly during the subsequent operations of encoding and combining into frames, improving the speed of the entire diagnostic process.

[0057] S302: Determine the target encoding method corresponding to the preset diagnostic protocol.

[0058] In this embodiment, first, the encoding methods supported by the diagnostic protocol, as well as the applicable scenarios and characteristics of each encoding method, are preset. Then, the characteristics of the request data are analyzed, including the data volume size, data type (such as integer, floating-point number, string, etc.), the importance and priority of the data, the data transmission frequency, etc. Then, according to the data characteristics and the requirements of the diagnostic protocol, the following factors are comprehensively considered to select the target encoding method: Encoding efficiency: Select an encoding method that can efficiently represent data within limited bandwidth and storage space to reduce the overhead of data transmission and storage; Decoding complexity: Ensure that the selected encoding method can be quickly decoded at the receiving end with reasonable computing resources without affecting the real-time performance of diagnosis; Error recovery ability: Prioritize encoding methods with certain error detection and correction capabilities to enhance the reliability of data transmission; Compatibility: Ensure that the selected encoding method is compatible with the preset diagnostic protocol, as well as the electronic control unit and diagnostic equipment of the target vehicle. Finally, the target encoding method corresponding to the preset diagnostic protocol is determined. It can be seen that the encoding method matching the diagnostic protocol helps to reduce errors in the encoding and decoding processes, ensure the integrity and accuracy of the request instruction, and can select the encoding method that saves the most storage space and computing resources according to the data characteristics, improving the overall performance and resource utilization rate of the system.

[0059] S303: Encode the multiple groups of compressed data based on the target encoding method to obtain the frame body corresponding to the request instruction.

[0060] In this embodiment, first, according to the rules and algorithms of the selected target encoding method, each group of compressed data is processed separately. For example, if the target encoding method is a specific binary encoding rule, then each group of compressed data is converted into a binary sequence that conforms to this rule. Then, details such as the bit order, byte alignment, and padding of the data are considered to ensure that the encoded result is accurate and conforms to the requirements of the preset diagnostic protocol for the frame body format. For different types and sizes of data, different processing may be required. For example, for integer-type data, it may be encoded according to a fixed bit width. For string-type data, it may be necessary to first perform character encoding conversion and then arrange it according to specific rules. At the same time, attention also needs to be paid to the encoding order and the separation identifier between data so that the original compressed data can be correctly restored during decoding. The entire encoding process needs to strictly follow the specifications of the target encoding method to ensure that the generated frame body can be correctly interpreted and processed, and finally the frame body corresponding to the request instruction is obtained.

[0061] It can be seen that the encoded frame body data is more compact, capable of transmitting more valid information in the same transmission bandwidth, reducing transmission time and resource consumption. Following a unified target encoding method ensures the consistency of data format and representation, reduces the error probability during data parsing and processing. The encoding method matching the preset diagnostic protocol can better adapt to the requirements of the protocol, ensure seamless communication with the vehicle system, and improve the reliability of diagnosis. A specific encoding method may increase the confidentiality of data, making unauthorized access and interpretation more difficult, protecting the security of vehicle diagnostic data. A suitable encoding method can introduce some error detection and correction mechanisms to detect and correct errors in a timely manner during data transmission, improving data accuracy. The unified encoding method simplifies the logic of data processing and transmission in the system, reduces the complexity of the design and implementation of the remote diagnostic system based on the diagnostic protocol, and facilitates maintenance and upgrade.

[0062] S304: Determine the frame header and frame tail corresponding to the preset diagnostic protocol.

[0063] In this embodiment, the frame header may contain information such as a start flag, protocol version number, message type identifier, etc., and the frame tail may contain information such as a checksum and an end flag for verifying data integrity and indicating the end of the frame. By reading the configuration file, using constant definitions, or directly specifying these fixed values in the code, it is ensured that the correct frame header and frame tail can be accurately added when generating the request instruction.

[0064] In this embodiment, the preset diagnostic protocol can be the SAE J2819 protocol. The SAE J2819 protocol is an automotive-related standard protocol developed by the Society of Automotive Engineers of the United States. It mainly involves the specifications and requirements for vehicle communication and diagnosis. It details various criteria for data exchange and communication between vehicle electronic systems, including but not limited to the following aspects: Communication format and coding: Defines the format, coding method, and data structure when data is transmitted in the vehicle network to ensure that different electronic control units and diagnostic devices can accurately understand and process the transmitted data; Message types and content: Clarifies the specific content and meaning of different types of messages, such as diagnostic requests, responses, status reports, etc., so that both communication parties can clearly know the purpose and use of the information being transmitted; Error handling and recovery mechanism: Specifies the handling methods when errors occur during communication and how to perform error recovery to ensure the reliability and stability of communication; Network management: Involves the management of the vehicle communication network, including rules for network topology, node joining and leaving, resource allocation, etc.; Diagnostic process and functions: Describes the specific process and functions required for vehicle diagnosis, such as the definition and interpretation of fault codes, parameter monitoring, etc.; Security and confidentiality: May include some requirements regarding communication security and data confidentiality to prevent unauthorized access and data tampering. The remote functions in the SAE J2819 protocol mainly include the following aspects: remote diagnosis, remote monitoring, remote software update, remote control, remote data collection, etc. The preset diagnostic protocol can also be the TP2.0 diagnostic protocol. The TP2.0 diagnostic protocol has been widely applied and supported in the automotive industry. It has good compatibility with many vehicle models and electronic control units, can be applied to the diagnostic needs of various vehicles, follows standardized specifications, makes the diagnostic process and data format consistent and predictable, reduces incompatibility and errors caused by protocol differences, provides comprehensive diagnostic functions, including reading fault codes, real-time data monitoring, actuator control, etc., and can meet the requirements for in-depth and comprehensive diagnosis of the target vehicle. As a mature diagnostic protocol, it has undergone long-term practical testing and optimization, and its stability and reliability are guaranteed, which can ensure the accurate acquisition and transmission of diagnostic data and provide strong support for accurate fault diagnosis and vehicle repair. The design and application of the TP2.0 diagnostic protocol may follow some general principles and standards specified in SAEJ2819 to ensure compatibility and consistency with the entire automotive diagnostic communication field. However, SAE J2819 is not necessarily limited to the TP2.0 diagnostic protocol and may also involve other relevant specifications and requirements for diagnostic communication. For example, simulate the CANBus connection between the vehicle and the diagnostic instrument to complete the simulation and data synchronization of the TP2.0 diagnostic protocol, and realize the TP2. between the vehicle and the diagnostic instrument.0Diagnostic protocol long-distance communication, the detailed steps are as follows: The vehicle connector makes a CANBus connection with the vehicle. The device connector configures the CANBus terminal resistance (60 - 120 ohms). The CAN nodes inside the device connector and the diagnostic instrument CAN node jointly form a CANBus network and make a CANBus connection with the diagnostic instrument. The diagnostic instrument sends the first instruction (channel request instruction) of the TP2.0 protocol. The device connector receives the channel request instruction and forwards it to the vehicle connector. The device connector checks if there is a channel reply record for the relevant ECU. If there is a record, the device connector directly uses the record to reply to the diagnostic instrument's channel reply. If there is no record, it waits for the vehicle's channel reply, records it, and replies with the channel reply. The vehicle connector receives the network data sent by the device connector, parses the channel request instruction, and sends it to the vehicle. The vehicle connector receives the vehicle's channel reply and sends it to the device connector through the network. The device connector and the vehicle connector record the TP2.0 sending and receiving CANBus IDs in the channel reply and create a TP2.0 diagnostic system data simulation. The diagnostic instrument sends the second instruction (connection setup) of the TP2.0 protocol. The device connector receives the connection setup and forwards it to the vehicle connector. The device connector checks if there is a connection reply record for the relevant ECU. If there is a record, the device connector directly uses the record to reply to the diagnostic instrument's connection reply. If there is no record, it waits for the vehicle's connection reply, records it, and replies with the connection reply. The vehicle connector receives the network data sent by the device connector, parses the connection setup, and sends it to the vehicle. The vehicle connector receives the vehicle's connection reply and sends it to the device connector through the network. The diagnostic instrument sends a connection test instruction of the TP2.0 protocol. The device connector receives the connection test and forwards it to the vehicle connector. The device connector checks the connection reply record of the relevant ECU and replies with the connection reply. The vehicle connector receives the network data sent by the device connector, parses the connection test, and sends it to the vehicle. The vehicle connector receives the vehicle's connection reply and sends it to the device connector through the network. The diagnostic instrument conducts TP2.0 protocol data communication with the vehicle. The data frames are divided into four types. The first type: does not require a confirmation request and is not the last frame. The device connector receives the data, records the service identifier in the data, and forwards the data to the vehicle connector. The vehicle connector receives the network data sent by the device connector, parses the data, and sends it to the vehicle. The second type: does not require a confirmation request and is not the last frame. The device connector receives the data, records the service identifier in the data, and forwards the data to the vehicle connector. The vehicle connector receives the network data sent by the device connector, parses the data, and sends it to the vehicle. The third type: does not require a confirmation request and is the last frame. The device connector receives the data and forwards the data to the vehicle connector. The device connector actively sends negative data to the diagnostic instrument, TP2.The data content is 0x80 0x00 0x7f, and the service identifier is 0x78. The function of this data is to inform the diagnostic instrument that the vehicle is busy and will reply to the subsequent data later. The vehicle connector receives the network data sent by the device connector, parses the data, and sends it to the vehicle. Fourth: A confirmation request is required, which is the last frame. The device connector receives the data and forwards it to the vehicle connector. The device connector actively sends a confirmation request to the diagnostic instrument and actively sends negative data to the diagnostic instrument. The TP2.0 data content is 0x80 0x00 0x7f, and the service identifier is 0x78. The function of this data is to inform the diagnostic instrument that the vehicle is busy and will reply to the subsequent data later. The vehicle connector receives the network data sent by the device connector, parses the data, and sends it to the vehicle. The vehicle connector receives the confirmation request from the vehicle. Finally, the diagnostic instrument sends a disconnection instruction according to the TP2.0 protocol. The device connector receives the disconnection instruction and forwards the disconnection instruction to the vehicle connector. The device connector terminates the data simulation of this system. The vehicle connector receives the network data sent by the device connector, parses the disconnection instruction, and sends it to the vehicle. The vehicle connector terminates the data simulation of this system.

[0065] It can be seen that the frame header and frame tail corresponding to the preset diagnostic protocol are determined. The frame header and frame tail corresponding to the preset diagnostic protocol are fixed and unchanged. The fixed frame header and frame tail formats enable the receiving end to quickly and accurately identify the start and end positions of the frame, so as to quickly locate and extract the valid data in the frame body, reducing the time and computing resources required for data parsing. The frame tail usually contains verification information, such as a checksum or a cyclic redundancy check value. The fixed frame tail format facilitates the receiving party to perform verification according to the predetermined rules, ensuring that the data has not been corrupted or lost during transmission, enhancing the integrity and reliability of the data. The fixed frame header and frame tail reduce the complexity and uncertainty of the protocol, making it easier for developers to understand and implement the communication protocol, reducing the difficulty of development and maintenance. The fixed frame structure helps different devices or systems to communicate according to the same rules, ensuring compatibility in various environments, promoting stable interaction between diagnostic devices and vehicle electronic control units. When a mismatch in the frame header or frame tail is detected, it can be quickly determined that there is a problem with data transmission, and corresponding error handling measures can be taken, such as retransmission or error reporting.

[0066] S305: Combine based on the frame header, the frame body, and the frame tail to obtain the request instruction for the target electronic control unit in the target vehicle.

[0067] In this embodiment, first, the byte length and arrangement order of the frame header, frame body and frame tail are clarified, which is determined in accordance with the specifications of the preset diagnostic protocol. Then, the frame header is placed at the front end in the prescribed order. Next, the frame body part is spliced ​​immediately after the frame header to ensure that the data of the frame body is completely and accurately connected after the frame header. Finally, the frame tail is added to the end of the frame body. During the combination process, attention should be paid to byte alignment and data continuity to ensure that the combined request instruction meets the requirements of the preset diagnostic protocol in format. For example, if the frame header is 2 bytes, the frame body is 10 bytes, and the frame tail is 1 byte, then the byte data of these three parts are connected in this order to form a complete 13-byte request instruction.

[0068] It can be seen that based on the combination of the frame header, the frame body and the frame tail, the request instruction for the target electronic control unit in the target vehicle is obtained, so that the entire request instruction has a clear and definite structure, which is convenient for the sending end to organize and send, and also convenient for the receiving end to quickly identify and parse each part. The receiving end can quickly determine the key information such as the type, source and importance of the data through the frame header, so as to more efficiently process subsequent data. The existence of the frame tail can be used to verify whether the data is complete and accurate during the transmission process, ensuring the integrity of the entire request instruction. The standardized data combination method reduces the risk of data confusion or loss, and improves reliability in complex vehicle communication environments. If the diagnostic protocol needs to be improved or new functions need to be added, this structured combination method is easier to adjust and expand, and follows a unified combination rule, which helps to maintain good compatibility between different vehicle diagnostic equipment and systems, and ensures that the request instruction can be processed correctly.

[0069] S203: Determine whether a first response instruction corresponding to the target electronic control unit is recorded in the device connector based on the request instruction.

[0070] In this embodiment, the generated request instruction can be used as a basis to check the storage or cache area of ​​the device connector. Since the device connector may have stored response instructions for certain specific target electronic control units in previous diagnostic operations, by comparing and matching the current request instruction with the existing records in the device connector, if a response instruction that is completely consistent with the target electronic control unit targeted by the current request instruction is found, it means that there is a record in the device connector. If no completely consistent response instruction is found after searching and comparing, it means that there is no relevant record in the device connector. Such a determination process helps to determine whether the existing response instructions in the device connector can be used directly for diagnosis, thereby improving diagnostic efficiency and reducing interaction with the vehicle connector and data transmission.

[0071] S204: Determine the response record data corresponding to the target electronic control unit based on the first response instruction, and send the response record data to the target diagnostic instrument.

[0072] In this embodiment, if so, determine the response record data corresponding to the target electronic control unit based on the first response instruction, and send the response record data to the target diagnostic instrument, so that the target diagnostic instrument performs a diagnostic operation on the target electronic control unit based on the response record data to obtain a first diagnostic result. Specifically, if the first response instruction corresponding to the target electronic control unit is recorded in the device connector, that is, if the first response instruction corresponding to the target electronic control unit is found in the device connector, then the relevant response record data needs to be further obtained based on this first response instruction. The response record data may contain diagnostic response information for the target electronic control unit before, such as various parameter values, status information, etc. Then, the obtained response record data is sent to the target diagnostic instrument. After receiving these data, the target diagnostic instrument will analyze and process these data according to the internal preset diagnostic algorithms and logics. Through this analysis and processing, the target diagnostic instrument can evaluate and judge the state, performance, or possible faults of the target electronic control unit, and finally obtain the first diagnostic result.

[0073] It can be seen that directly using the existing response record data in the device connector for diagnosis eliminates the need to request new data from the vehicle connector again, saving the time for data transmission and processing, accelerating the diagnostic process, avoiding unnecessary data transmission, reducing the burden on the vehicle communication network. Especially in the case of limited or busy network resources, it helps to maintain the stability of the system, can quickly provide the required data for the diagnostic instrument to perform diagnostic operations, enables the operator to obtain preliminary diagnostic results faster, helps to make decisions in a timely manner. Diagnosing based on past response record data can compare and analyze the differences between the current state and the historical state, provide more reference for fault troubleshooting and performance evaluation, reduce the number of interactions with the vehicle connector, and reduce errors and losses that may occur due to frequent communication, thereby reducing the diagnostic cost to a certain extent.

[0074] S205: Send the request instruction to the vehicle connector.

[0075] In this embodiment, if not, the request instruction is sent to the vehicle connector, so that the vehicle connector determines the target response data corresponding to the target electronic control unit based on the request instruction. Specifically, if the first response instruction corresponding to the target electronic control unit is not found in the device connector, the generated request instruction is passed to the vehicle connector. After receiving this request instruction, the vehicle connector will, according to the content and requirements of the instruction, communicate and interact with the target electronic control unit in the target vehicle to determine the target response data corresponding to this request instruction.

[0076] It should be noted that before sending the request instruction to the vehicle connector, it is also necessary to judge the working state of the target vehicle. If the current target vehicle is in a busy state, the request instruction cannot be sent to the vehicle connector. Exemplarily, first, obtain the communication data between the target diagnostic instrument and the target vehicle, and determine the service identifier corresponding to the communication data. Specifically, a data acquisition device can be set at the communication interface between the target diagnostic instrument and the target vehicle to capture the transmitted data in real time. Using the built-in data recording function in the target diagnostic instrument and the vehicle communication system, the data during the communication process is stored and then extracted later. Through relevant diagnostic software or application programs, configure them to have the function of data acquisition, and capture the required data during communication. Refer to the communication protocol specification document followed by the target vehicle and the diagnostic instrument, which will clearly stipulate the service identifiers corresponding to different data formats and contents, analyze the obtained communication data, extract the identification information at specific positions or fields therein, and compare and match it with the known service identifier rules. It is also possible to automatically identify and determine its corresponding service identifier according to the characteristics, formats, and content patterns of the data. Exemplarily, the service identifier is sent to the vehicle connector, so that the vehicle connector determines the working state of the target vehicle based on the service identifier and generates a status instruction corresponding to the working state. Specifically, the obtained service identifier is passed to the vehicle connector. After receiving the service identifier, the vehicle connector will judge the working state of the target vehicle according to its meaning and the internal preset rules and logics. If the vehicle connector determines that the target vehicle is in a busy state, it will generate a target vehicle busy instruction and send it to the device connector. Exemplarily, when receiving the target vehicle busy instruction, a target vehicle busy prompt message is generated based on the target vehicle busy instruction. Specifically, when the device connector receives this busy instruction, it will generate a target vehicle busy prompt message according to this instruction to inform relevant personnel or systems that the target vehicle cannot immediately process new requests at present. Please refer to Figure 4 , Figure 4 is an example diagram of a display interface for the target vehicle busy prompt message provided by an embodiment of the present application. In Figure 4On the described target vehicle busy prompt information display interface 40, words such as "The vehicle is currently busy" and "The target vehicle is currently in a busy state, and the estimated response time is about 30 minutes. Please wait patiently" will be displayed.

[0077] If the vehicle connector determines that the target vehicle is in an idle state, it will generate a target vehicle idle instruction and send it to the device connector. Exemplarily, when receiving the target vehicle idle instruction, the step of sending the request instruction to the vehicle connector will be executed. Specifically, when receiving this idle instruction, the previously mentioned step of sending the request instruction to the vehicle connector will be executed so that the vehicle connector can further interact and process with the target vehicle according to the request instruction.

[0078] It can be seen that by timely obtaining communication data and determining the service identifier, the vehicle status can be quickly understood, unnecessary waiting and repeated operations can be avoided, thereby improving the efficiency of the overall diagnosis process. Corresponding processing is carried out according to the working status of the vehicle, giving a prompt when the vehicle is busy and sending a request instruction when it is idle, which helps to reasonably allocate diagnostic resources, avoid resource waste and conflicts, helps to timely feedback the busy or idle state of the vehicle to the user, enables the user to better plan and arrange diagnostic operations, reduces dissatisfaction caused by waiting, improves the user experience, can flexibly respond to different vehicle working states, enables the diagnostic system to effectively operate in various situations, and improves the stability and reliability of the system.

[0079] It can be seen that sending the request instruction to the vehicle connector enables the vehicle connector to determine the target response data corresponding to the target electronic control unit based on the request instruction. The vehicle connector can directly obtain the response data accurately corresponding to the target electronic control unit according to the request instruction, avoiding deviation or error in data acquisition, thereby improving the accuracy of the diagnostic result. Sending the request instruction in real time and obtaining the latest response data ensure that the data on which the diagnosis is based has good timeliness and can reflect the current state of the target electronic control unit. The vehicle connector is specifically responsible for handling communication and data interaction with the vehicle and can obtain the required data more efficiently, avoiding excessive consumption of system resources in other parts for direct communication with the vehicle. This method enables the diagnostic system to adapt to different types and configurations of vehicles. As long as the vehicle connector can correctly process the request instruction, accurate response data can be obtained.

[0080] S206: Receive the target response data from the vehicle connector and send the target response data to the target diagnostic instrument, so that the target diagnostic instrument performs a diagnostic operation on the target electronic control unit based on the target response data to obtain a second diagnostic result.

[0081] In this embodiment, the device connector undertakes the task of receiving data. It obtains the target response data from the vehicle connector. Then, the device connector transfers this part of the received target response data to the target diagnostic instrument. After receiving the target response data, the target diagnostic instrument will analyze and process these data according to the diagnostic rules, algorithms and logics set inside it. Through in-depth research and calculation of the target response data, the target diagnostic instrument can evaluate and judge aspects such as the state, performance, and whether there are faults of the target electronic control unit, and finally obtain the second diagnostic result. This second diagnostic result is generated through the diagnostic operation of the target diagnostic instrument based on the target response data provided by the vehicle connector.

[0082] It can be seen that by obtaining the target response data provided by the vehicle connector and transferring it to the target diagnostic instrument for diagnostic operations, the latest and most accurate data can be fully utilized to evaluate the state of the target electronic control unit, thereby obtaining more comprehensive and accurate diagnostic results. The division of labor between data acquisition and diagnostic operations is realized. The vehicle connector focuses on obtaining specific data, while the target diagnostic instrument focuses on diagnosing based on the data, improving the efficiency and professionalism of the entire process, and being able to handle various different diagnostic situations. Even if there is no pre-stored response data in the device connector, the required data can be obtained through interaction with the vehicle connector and the diagnosis can be completed, enhancing the adaptability and flexibility of the diagnostic system, ensuring that the target diagnostic instrument can diagnose based on the latest response data, and avoiding diagnostic errors caused by using outdated or inaccurate data. Through an effective data transfer and processing mechanism, unnecessary repeated operations and waiting times are reduced, thereby reducing the cost and time consumption of diagnosis.

[0083] Please refer to Figure 5 , Figure 5 which is a flowchart of another remote diagnostic method based on a diagnostic protocol provided by an embodiment of the present application, including but not limited to the following steps:

[0084] S501: Receive a request instruction from the device connector.

[0085] In this embodiment, the request instruction is obtained by encoding the corresponding request data of the target electronic control unit in the target vehicle based on a preset diagnostic protocol. Specifically, the request data can be classified and compressed through a device connector to obtain multiple sets of compressed data, the target encoding method corresponding to the preset diagnostic protocol is determined, the multiple sets of compressed data are encoded based on the target encoding method to obtain the frame body corresponding to the request instruction, the frame header and frame tail corresponding to the preset diagnostic protocol are determined, and the frame header, the frame body, and the frame tail are combined to obtain the request instruction for the target electronic control unit in the target vehicle. The request instruction can be a channel request instruction, a connection setting instruction, or a connection test instruction.

[0086] S502: Determine the target response data corresponding to the target electronic control unit based on the request instruction.

[0087] In this embodiment, by way of example, the vehicle identification number of the target vehicle is obtained, and the target mapping table corresponding to the target vehicle is determined from the vehicle database based on the vehicle identification number. The target mapping table is used to represent the mapping relationship between different request information and response data. Specifically, first, a connection between the vehicle connector and the vehicle database of the target vehicle is established, which can be achieved through a database access interface or a relevant database management system. Then, the obtained vehicle identification number is used as a query condition to send a query request to the database. The database performs matching and retrieval based on the received vehicle identification number, finds the storage location or identifier of the target mapping table associated with the number, and extracts and obtains the corresponding target mapping table for subsequent use of the mapping relationship therein to determine the response data. The request information can be a request for the working parameters of a specific component, a request for reading fault codes, a request for obtaining sensor data, a request for querying the system status, a request for the operation feedback of an actuator, or a request for obtaining configuration information. The response data can be the real-time operating parameters of the target electronic control unit, such as specific values of voltage, current, temperature, etc., or a fault code or fault flag bit indicating whether a fault exists and the type of the fault, or the measured values of sensors, such as the oxygen concentration of an oxygen sensor and the wheel speed of a wheel speed sensor, or the working state feedback of an actuator, such as the number of fuel injections of an injector or the opening degree of a throttle valve, or the software version information inside the control unit to determine whether an update is required or there are compatibility issues, or the historical fault records and clearance records stored in the control unit, or the index data related to vehicle performance, such as acceleration and fuel consumption rate.

[0088] Exemplarily, determine the target request information corresponding to the request instruction. Specifically, parse and disassemble the request instruction, and match and compare the key elements obtained from the parsing with known request types or templates. These request types or templates are usually predefined in advance and are associated with specific vehicle functions, parameters, or states. It is also possible to identify and classify the keywords, parameter ranges, or specific identifiers included in the request instruction, so as to infer the corresponding target request information.

[0089] Exemplarily, determine the target response data corresponding to the target request information in the target mapping table. Specifically, first, carefully analyze the characteristics and key elements of the target request information, such as the specific parameters of the request, function modules, data types, etc. Then, search for entries in the target mapping table that exactly match these characteristics. The mapping table is usually organized according to certain rules and structures, possibly through indexing, keywords, or classification, etc. During the search process, it may be necessary to perform appropriate conversion or standardization processing on the request information to ensure that it matches the format and definition in the mapping table. If there are multiple potentially matching entries, it is necessary to further screen and judge according to the detailed conditions and context of the request to determine the most accurate corresponding relationship. Once an accurately matching entry is found, the response data associated with that entry can be obtained as the target response data.

[0090] It can be seen that by accurately obtaining the target response data corresponding to the request instruction, more accurate and targeted information can be provided for diagnosis, avoiding the interference of irrelevant or incorrect data, thereby improving the reliability of the diagnosis result. Managing the complex request and response relationship through a mapping table makes the acquisition and matching of data more orderly and efficient, reducing chaos and errors in the processing process. Regardless of how the vehicle model or configuration changes, as long as the vehicle identification number can be obtained and the corresponding relationship can be found in the mapping table, the same processing flow can be applied, facilitating the system to adapt to new vehicle models and diagnostic requirements, quickly and accurately determining the target response data, reducing the time for searching and screening in a large amount of data, and accelerating the diagnostic speed. The centralized management method of the mapping table makes the update, modification, and maintenance of data more convenient, ensuring the consistency and accuracy of the data.

[0091] S503: Send the target response data to the device connector, so that the device connector sends the target response data to the target diagnostic instrument, thereby enabling the target diagnostic instrument to perform a diagnostic operation on the target electronic control unit based on the target response data and obtain a target diagnostic result.

[0092] In this embodiment, the device linker is connected to the target diagnostic instrument. After determining the target response data corresponding to the target electronic control unit, this target response data is transmitted to the device connector. As an intermediate transmission link, the device connector receives the target response data from the previous step. Since the device connector is connected to the target diagnostic instrument, the device connector will then send the target response data to the target diagnostic instrument. After receiving the target response data, the target diagnostic instrument analyzes, calculates, and evaluates these data according to the preset diagnostic algorithms, logics, and rules inside it. Through the processing of the target response data, the target diagnostic instrument finally obtains the diagnostic result regarding the target electronic control unit. It can be seen that through the clear data transmission path, the possibility of errors or losses occurring during data transmission is reduced, ensuring that the target diagnostic instrument can receive accurate and complete target response data, improving the credibility of the diagnostic result. Different components undertake specific tasks. The device connector focuses on data transmission, and the target diagnostic instrument focuses on diagnostic analysis, each playing its professional advantages, improving the efficiency and quality of the entire diagnostic process. This modular design enables the device connector or the target diagnostic instrument to be improved individually when the system needs to be upgraded or expanded without affecting the basic architecture of the entire system. The target diagnostic instrument does not need to directly interact with multiple data sources to obtain data, but receives it uniformly through the device connector, reducing the complex processing on its part in data acquisition.

[0093] It should be noted that it is also necessary to make adaptive responses according to different characteristics of the communication data to achieve an efficient and accurate vehicle diagnosis and interaction process. First, receive the service identifier corresponding to the communication data in the device connector. The communication data is used for communication between the target diagnostic instrument and the target vehicle. The service identifier is an identification symbol or code with specific meanings and functions. It is associated with the data used for communication between the target diagnostic instrument and the target vehicle and is used to indicate the specific status, type, or characteristics of the communication. The information in the service identifier can help the system judge the current communication situation. For example, when it includes a message confirmation character, it indicates that the communication is smooth and the vehicle may be in an idle state and can receive new operations. When it includes a message end character, it implies that the communication has been completed or the vehicle is busy and cannot immediately respond to new requests. The service identifier is like a "secret signal" or "label", transmitting key information about the communication data to the receiving party through specific character combinations or encodings so that the system can make corresponding correct processing and decisions.

[0094] Exemplarily, if the service identifier includes a message confirmation character, a target vehicle idle instruction is generated based on the service identifier, and the target vehicle idle instruction is sent to the device connector, and the communication data is sent to the target vehicle, and the step of determining target response data corresponding to the target electronic control unit based on the request instruction is executed. Specifically, when the service identifier includes a message confirmation character, the vehicle connector generates a target vehicle idle instruction according to preset rules and logic. First, the vehicle connector parses and identifies the received service identifier. This parsing process may check specific character positions, character combinations, or specific encoding formats. If a character indicating message confirmation is found at a preset position or according to a predetermined encoding rule, the vehicle connector will trigger a series of instruction generation operations. This may involve extracting a template related to "target vehicle idle" from a preset instruction template library and filling or modifying certain fields in the template according to the current communication context and relevant parameters. It may also add the current timestamp, communication identification number, or specific identification information related to the vehicle, etc., to form a complete and accurate target vehicle idle instruction. Then, the target vehicle idle instruction is sent to the device connector, and the communication data is sent to the target vehicle, enabling good communication between the target vehicle and the target diagnostic instrument. The vehicle connector also executes the step of determining target response data corresponding to the target electronic control unit based on the request instruction.

[0095] Exemplarily, if the service identifier includes an end-of-message character, a target vehicle busy instruction is generated based on the service identifier and sent to the device connector, enabling the device connector to generate a target vehicle busy prompt message. Specifically, the end-of-message character is a specific character or character combination preset in the service identifier, used to indicate that the current communication has ended or the vehicle is in a busy state. The target vehicle busy instruction is an instruction signal used to notify relevant devices or components that the target vehicle is busy and unable to immediately respond to new requests. When the vehicle connector receives the service identifier, it will parse and check it. If the end-of-message character is detected in the service identifier, the vehicle connector will create a target vehicle busy instruction according to preset rules and logic. The process of generating the target vehicle busy instruction may include the following steps: First, the vehicle connector recognizes the presence of the end-of-message character and triggers the program for generating the busy instruction. Then, according to the preset instruction format and content requirements, relevant information such as vehicle identification and busy status identification is assembled. Finally, after generating the complete target vehicle busy instruction, it is sent to the device connector. After receiving the target vehicle busy instruction, the device connector generates a target vehicle busy prompt message according to its own program and function settings. The form of this prompt message may be to display text on the display screen, emit a specific sound alarm, or send a notification to other relevant systems through the network, etc., to inform relevant personnel or other systems of the busy status of the target vehicle. It should be noted that when the vehicle connector sends the target vehicle busy instruction to the device connector, it also needs to send the end-of-message character to the target diagnostic instrument to inform the target diagnostic instrument that the current vehicle is busy and will reply with data later. After receiving this end-of-message character, the target diagnostic instrument can understand that the current target vehicle is in a busy state and unable to immediately respond to the diagnostic instrument's request or provide the required data. In this way, the target diagnostic instrument can know that it needs to wait instead of continuously sending requests or expecting an immediate reply, which helps to avoid possible misjudgments, repeated requests, or other unnecessary operations caused by the target diagnostic instrument not receiving a timely response, thus making the entire diagnostic process more orderly and efficient.

[0096] It can be seen that by timely parsing the service identifier and generating corresponding instructions, the status of the vehicle can be quickly determined, unnecessary requests can be avoided when the vehicle is busy, thus saving time and resources, improving the overall efficiency of communication, allocating tasks and data transmission according to the idle or busy status of the vehicle, ensuring the reasonable utilization of resources, avoiding resource competition and congestion, being able to accurately control the communication process, reducing system errors and instability caused by incorrect request sending or data transmission, improving the reliability of the system, timely feedback the status information of the vehicle to the user, enabling the user to better plan and arrange diagnostic operations, reducing waiting and uncertainty, and enhancing the user's satisfaction with the diagnostic process. The entire process can automatically adapt to different states of the vehicle without manual intervention to determine whether the vehicle is available, realizing intelligent communication and task management.

[0097] In summary, implementing the embodiments of the present application has the following beneficial effects:

[0098] It can be seen that the remote diagnostic method based on the diagnostic protocol described in the embodiments of the present application is applied to an equipment connector and a vehicle connector. The equipment connector is connected to a target diagnostic instrument, and the vehicle connector is connected to a target vehicle. The target diagnostic instrument and the target vehicle are communicatively connected through the equipment connector and the vehicle connector. First, the equipment connector obtains request data for a target electronic control unit in the target vehicle and encodes the request data based on a preset diagnostic protocol to obtain a request instruction corresponding to the target electronic control unit. Then, based on the request instruction, it is determined whether a first response instruction corresponding to the target electronic control unit is recorded in the equipment connector. If so, response record data corresponding to the target electronic control unit is determined based on the first response instruction and sent to the target diagnostic instrument, so that the target diagnostic instrument performs a diagnostic operation on the target electronic control unit based on the response record data to obtain a first diagnostic result. If not, the request instruction is sent to the vehicle connector, so that the vehicle connector determines target response data corresponding to the target electronic control unit based on the request instruction. The vehicle connector receives the request instruction from the equipment connector, then determines the target response data corresponding to the target electronic control unit based on the request instruction, and sends the target response data to the equipment connector. The equipment connector receives the target response data from the vehicle connector and sends the target response data to the target diagnostic instrument, so that the target diagnostic instrument performs a diagnostic operation on the target electronic control unit based on the target response data to obtain a second diagnostic result.

[0099] Please refer to Figure 6 , Figure 6It is a schematic structural diagram of a remote diagnosis device based on a diagnostic protocol provided by an embodiment of the present application, which is applied to a device connector. The device connector is connected to a target diagnostic instrument, and a vehicle connector is connected to a target vehicle. The target diagnostic instrument and the target vehicle are communicatively connected through the device connector and the vehicle connector. The remote diagnosis device 600 based on the diagnostic protocol includes: an acquisition unit 601 and a processing unit 602;

[0100] The acquisition unit 601 is configured to acquire request data for a target electronic control unit in the target vehicle;

[0101] The processing unit 602 is configured to encode the request data based on a preset diagnostic protocol to obtain a request instruction corresponding to the target electronic control unit;

[0102] Determine whether a first response instruction corresponding to the target electronic control unit is recorded in the device connector based on the request instruction;

[0103] If so, determine response record data corresponding to the target electronic control unit based on the first response instruction, and send the response record data to the target diagnostic instrument, so that the target diagnostic instrument performs a diagnostic operation on the target electronic control unit based on the response record data to obtain a first diagnostic result;

[0104] If not, send the request instruction to the vehicle connector, so that the vehicle connector determines target response data corresponding to the target electronic control unit based on the request instruction;

[0105] Receive the target response data from the vehicle connector, and send the target response data to the target diagnostic instrument, so that the target diagnostic instrument performs a diagnostic operation on the target electronic control unit based on the target response data to obtain a second diagnostic result.

[0106] In some possible implementation manners, in terms of encoding the request data based on a preset diagnostic protocol to obtain a request instruction corresponding to the target electronic control unit, the processing unit 602 is specifically configured to:

[0107] Classify and compress the request data to obtain multiple groups of compressed data;

[0108] Determine a target encoding method corresponding to the preset diagnostic protocol;

[0109] Encode the multiple groups of compressed data based on the target encoding method to obtain a frame body corresponding to the request instruction;

[0110] Determine a frame header and a frame tail corresponding to the preset diagnostic protocol;

[0111] Combining the frame header, the frame body, and the frame tail to obtain the request instruction for the target electronic control unit in the target vehicle.

[0112] In some possible implementation manners, the processing unit 602 is further specifically configured to:

[0113] Obtain communication data between the target diagnostic instrument and the target vehicle;

[0114] Determine a service identifier corresponding to the communication data;

[0115] Send the service identifier to the vehicle connector, so that the vehicle connector determines the working state of the target vehicle based on the service identifier and generates a status instruction corresponding to the working state;

[0116] When receiving a target vehicle busy instruction, generate a target vehicle busy prompt message based on the target vehicle busy instruction;

[0117] When receiving a target vehicle idle instruction, execute the step of sending the request instruction to the vehicle connector.

[0118] Please refer to Figure 7 , Figure 7 FIG. is a schematic structural diagram of another remote diagnostic device based on a diagnostic protocol provided by an embodiment of the present application, which is applied to a vehicle connector. The vehicle connector is connected to a target vehicle. The remote diagnostic device 700 based on the diagnostic protocol includes: a receiving unit 701 and a processing unit 702;

[0119] The receiving unit 701 is configured to receive a request instruction from a device connector; the request instruction is obtained by encoding corresponding request data for a target electronic control unit in the target vehicle based on a preset diagnostic protocol;

[0120] The processing unit 702 is configured to determine target response data corresponding to the target electronic control unit based on the request instruction;

[0121] Send the target response data to the device connector, so that the device connector sends the target response data to the target diagnostic instrument, so that the target diagnostic instrument performs a diagnostic operation on the target electronic control unit based on the target response data to obtain a target diagnostic result; the device connector is connected to the target diagnostic instrument.

[0122] In some possible implementation manners, in terms of determining target response data corresponding to the target electronic control unit based on the request instruction, the processing unit 702 is specifically configured to:

[0123] Obtain the vehicle identification number of the target vehicle;

[0124] Determine the target mapping table corresponding to the target vehicle from the vehicle database based on the vehicle identification number; the target mapping table is used to represent the mapping relationship between different request information and response data;

[0125] Determine the target request information corresponding to the request instruction;

[0126] Determine the target response data corresponding to the target request information in the target mapping table.

[0127] In some possible implementation manners, the processing unit 702 is further specifically configured to:

[0128] Receive a service identifier corresponding to communication data from the device connector; the communication data is used for communication between the target diagnostic instrument and the target vehicle;

[0129] If the service identifier includes a message confirmation character, generate a target vehicle idle instruction based on the service identifier, send the target vehicle idle instruction to the device connector, send the communication data to the target vehicle, and execute the step of determining the target response data corresponding to the target electronic control unit based on the request instruction;

[0130] If the service identifier includes a message end character, generate a target vehicle busy instruction based on the service identifier, send the target vehicle busy instruction to the device connector, so that the device connector generates a target vehicle busy prompt message.

[0131] Please refer to Figure 8 , Figure 8 is a schematic structural diagram of an electronic device provided by an embodiment of the present application. As Figure 8 shown, the electronic device 800 includes a transceiver 801, a processor 802, and a memory 803. They are connected by a bus 804. The memory 803 is used to store computer programs and data, and the transceiver 801 can transmit the data stored in the memory 803 to the processor 802. The above program includes instructions for performing the following steps:

[0132] Obtain request data for a target electronic control unit in the target vehicle;

[0133] Encode the request data based on a preset diagnostic protocol to obtain a request instruction corresponding to the target electronic control unit;

[0134] Based on the request instruction, determine whether a first response instruction corresponding to the target electronic control unit is recorded in the device connector;

[0135] If so, determine the response record data corresponding to the target electronic control unit based on the first response instruction, and send the response record data to the target diagnostic instrument, so that the target diagnostic instrument performs a diagnostic operation on the target electronic control unit based on the response record data to obtain a first diagnostic result;

[0136] If not, send the request instruction to the vehicle connector, so that the vehicle connector determines the target response data corresponding to the target electronic control unit based on the request instruction;

[0137] Receive the target response data from the vehicle connector, and send the target response data to the target diagnostic instrument, so that the target diagnostic instrument performs a diagnostic operation on the target electronic control unit based on the target response data to obtain a second diagnostic result.

[0138] The above program further includes instructions for performing the following steps:

[0139] Receive a request instruction from a device connector; the request instruction is obtained by encoding request data corresponding to a target electronic control unit in a target vehicle based on a preset diagnostic protocol;

[0140] Determine target response data corresponding to the target electronic control unit based on the request instruction;

[0141] Send the target response data to the device connector, so that the device connector sends the target response data to the target diagnostic instrument, so that the target diagnostic instrument performs a diagnostic operation on the target electronic control unit based on the target response data to obtain a target diagnostic result; the device connector is connected to the target diagnostic instrument.

[0142] In some possible implementation manners, in terms of encoding the request data based on a preset diagnostic protocol to obtain a request instruction corresponding to the target electronic control unit, the above program includes instructions for performing the following steps:

[0143] Classify and compress the request data to obtain multiple sets of compressed data;

[0144] Determine a target encoding method corresponding to the preset diagnostic protocol;

[0145] Encode the multiple sets of compressed data based on the target encoding method to obtain a frame body corresponding to the request instruction;

[0146] Determine a frame header and a frame tail corresponding to the preset diagnostic protocol;

[0147] Based on the combination of the frame header, the frame body, and the frame tail, the request instruction for the target electronic control unit in the target vehicle is obtained.

[0148] In some possible implementation manners, the above program includes instructions for performing the following steps:

[0149] Obtain the communication data between the target diagnostic instrument and the target vehicle;

[0150] Determine the service identifier corresponding to the communication data;

[0151] Send the service identifier to the vehicle connector, so that the vehicle connector determines the working state of the target vehicle based on the service identifier and generates a status instruction corresponding to the working state;

[0152] When receiving the target vehicle busy instruction, generate a target vehicle busy prompt message based on the target vehicle busy instruction;

[0153] When receiving the target vehicle idle instruction, execute the step of sending the request instruction to the vehicle connector.

[0154] In some possible implementation manners, in terms of determining the target response data corresponding to the target electronic control unit based on the request instruction, the above program includes instructions for performing the following steps:

[0155] Obtain the vehicle identification number of the target vehicle;

[0156] Based on the vehicle identification number, determine the target mapping table corresponding to the target vehicle in the vehicle database; the target mapping table is used to represent the mapping relationship between different request information and response data;

[0157] Determine the target request information corresponding to the request instruction;

[0158] Determine the target response data corresponding to the target request information in the target mapping table.

[0159] In some possible implementation manners, the above program includes instructions for performing the following steps:

[0160] Receive the service identifier corresponding to the communication data from the device connector; the communication data is used for communication between the target diagnostic instrument and the target vehicle;

[0161] If the service identifier includes a message confirmation character, generate a target vehicle idle instruction based on the service identifier, send the target vehicle idle instruction to the device connector, send the communication data to the target vehicle, and perform the step of determining target response data corresponding to the target electronic control unit based on the request instruction;

[0162] If the service identifier includes a message end character, generate a target vehicle busy instruction based on the service identifier, send the target vehicle busy instruction to the device connector, so that the device connector generates a target vehicle busy prompt message.

[0163] It should be understood that the electronic devices in this application may include remote diagnostic devices based on diagnostic protocols, smart phones (such as Android phones, iOS phones, Windows Phone phones, etc.), tablet computers, palm computers, laptop computers, mobile Internet devices MID (Mobile Internet Devices, abbreviated as: MID) or wearable devices, or servers, edge computing nodes, etc. The above-mentioned electronic devices are only examples, not exhaustive, and include but are not limited to the above-mentioned electronic devices.

[0164] The embodiments of the present application also provide a computer-readable storage medium. The computer-readable storage medium stores a computer program, and the computer program is executed by a processor to implement part or all of the steps of any one of the remote diagnostic methods based on diagnostic protocols described in the above method embodiments.

[0165] The embodiments of the present application also provide a computer program product. 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 part or all of the steps of any one of the remote diagnostic methods based on diagnostic protocols described in the above method embodiments.

[0166] It should be noted that for the foregoing method embodiments, for the sake of simple description, they are all expressed as a series of action combinations. However, those skilled in the art should know that the present application is not limited by the described action sequence, because according to the present application, certain steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily essential to the present application.

[0167] In the above embodiments, the descriptions of the various embodiments have their own emphases. For the parts not detailed in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0168] In several embodiments provided by the present application, it should be understood that the disclosed device can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed coupling or direct coupling or communication connection between each other can be through some interfaces. The indirect coupling or communication connection of devices or units can be in electrical or other forms.

[0169] The units described as separate components may or may not be physically separated. The components shown as units may or may not be physical units, that is, they can be located in one place or distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0170] In addition, in each embodiment of the present application, each functional unit can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software program modules.

[0171] If the integrated unit is implemented in the form of a software program module and sold or used as an independent product, it can be stored in a computer-readable memory. Based on such an understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a memory and includes several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods in each embodiment of the present application. And the aforementioned memory includes: USB flash drives, read-only memories (ROM, Read-Only Memory), random access memories (RAM, Random Access Memory), mobile hard disks, magnetic disks, or optical disks and other media that can store program codes.

[0172] Those of ordinary skill in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructing relevant hardware through a program. The program can be stored in a computer-readable memory. The memory can include: flash drives, read-only memories (abbreviation: ROM), random access memories (abbreviation: RAM), magnetic disks, or optical disks, etc.

[0173] The above has introduced the embodiments of the present application in detail. Specific examples are used herein to elaborate on the principle and embodiments of the present application. The description of the above embodiments is only for helping to understand the method and its core idea of the present application; at the same time, for those of ordinary skill in the art, according to the idea of the present application, there will be changes in the specific embodiments and application scope. In summary, the content of this specification should not be construed as a limitation to the present application.

Claims

1. A remote diagnosis method based on a diagnosis protocol, characterized in that: Applied to a device connector, the device connector is connected to a target diagnostic instrument, the vehicle connector is connected to a target vehicle, the target diagnostic instrument and the target vehicle are connected to each other through the device connector and the vehicle connector, and the method includes: obtaining request data for a target electronic control unit in the target vehicle; Encoding the request data based on a preset diagnostic protocol to obtain a request instruction corresponding to the target electronic control unit; Determining whether a first response instruction corresponding to the target electronic control unit is recorded in the device connector based on the request instruction; If so, determining the response record data corresponding to the target electronic control unit based on the first response instruction, and sending the response record data to the target diagnostic instrument, so that the target diagnostic instrument performs a diagnostic operation on the target electronic control unit based on the response record data to obtain a first diagnostic result; If not, sending the request instruction to the vehicle connector so that the vehicle connector determines the target response data corresponding to the target electronic control unit based on the request instruction; The target response data is received from the vehicle connector, and the target response data is sent to the target diagnostic instrument, so that the target diagnostic instrument performs a diagnostic operation on the target electronic control unit based on the target response data to obtain a second diagnostic result.

2. The method according to claim 1, characterized in that The step of encoding the request data based on a preset diagnostic protocol to obtain a request instruction corresponding to the target electronic control unit includes: Classify and compress the request data to obtain multiple groups of compressed data; Determining a target coding method corresponding to the preset diagnostic protocol; Encoding the plurality of groups of compressed data based on the target encoding method to obtain a frame body corresponding to the request instruction; Determine the frame header and frame tail corresponding to the preset diagnostic protocol; The request instruction for the target electronic control unit in the target vehicle is obtained by combining the frame header, the frame body and the frame tail.

3. The method according to claim 2, characterized in that The method further comprises: Acquiring communication data between the target diagnostic instrument and the target vehicle; determining a service identifier corresponding to the communication data; sending the service identifier to the vehicle connector, so that the vehicle connector determines the working state of the target vehicle based on the service identifier and generates a state instruction corresponding to the working state; When a target vehicle busy instruction is received, generating target vehicle busy prompt information based on the target vehicle busy instruction; When the target vehicle idle instruction is received, the step of sending the request instruction to the vehicle connector is performed.

4. A remote diagnosis method based on a diagnosis protocol, characterized in that: Applied to a vehicle connector, the vehicle connector is connected to a target vehicle, the method comprising: Receiving a request instruction from a device connector; the request instruction is obtained by encoding corresponding request data of a target electronic control unit in the target vehicle based on a preset diagnostic protocol; determining target response data corresponding to the target electronic control unit based on the request instruction; The target response data is sent to the device connector, so that the device connector sends the target response data to the target diagnostic instrument, thereby enabling the target diagnostic instrument to perform a diagnostic operation on the target electronic control unit based on the target response data to obtain a target diagnostic result; the device connector is connected to the target diagnostic instrument.

5. The method according to claim 4, characterized in that The determining, based on the request instruction, target response data corresponding to the target electronic control unit comprises: Obtaining a vehicle identification number of the target vehicle; Determine a target mapping table corresponding to the target vehicle from a vehicle database based on the vehicle identification number; the target mapping table is used to characterize the mapping relationship between different request information and response data; Determine target request information corresponding to the request instruction; Determine the target response data corresponding to the target request information in the target mapping table.

6. The method according to claim 5, characterized in that The method further comprises: receiving a service identifier corresponding to communication data from the device connector; the communication data is used for communication between the target diagnostic instrument and the target vehicle; If the service identifier includes a message confirmation character, generating a target vehicle idle instruction based on the service identifier, sending the target vehicle idle instruction to the device connector, sending the communication data to the target vehicle, and performing the step of determining the target response data corresponding to the target electronic control unit based on the request instruction; If the service identifier includes a message end character, a target vehicle busy instruction is generated based on the service identifier, and the target vehicle busy instruction is sent to the device connector, so that the device connector generates target vehicle busy prompt information.

7. A remote diagnostic device based on a diagnostic protocol, characterized in that: The remote diagnostic device based on the diagnostic protocol is used to execute instructions of the steps in the method according to any one of claims 1 to 3, and the device comprises: an acquisition unit and a processing unit; The acquisition unit is used to acquire request data for a target electronic control unit in the target vehicle; The processing unit is used to encode the request data based on a preset diagnostic protocol to obtain a request instruction corresponding to the target electronic control unit; Determining whether a first response instruction corresponding to the target electronic control unit is recorded in the device connector based on the request instruction; If so, determining the response record data corresponding to the target electronic control unit based on the first response instruction, and sending the response record data to the target diagnostic instrument, so that the target diagnostic instrument performs a diagnostic operation on the target electronic control unit based on the response record data to obtain a first diagnostic result; If not, sending the request instruction to the vehicle connector so that the vehicle connector determines the target response data corresponding to the target electronic control unit based on the request instruction; The target response data is received from the vehicle connector, and the target response data is sent to the target diagnostic instrument, so that the target diagnostic instrument performs a diagnostic operation on the target electronic control unit based on the target response data to obtain a second diagnostic result.

8. A remote diagnostic device based on a diagnostic protocol, characterized in that: The remote diagnostic device based on the diagnostic protocol is used to execute instructions of the steps in the method according to any one of claims 4 to 6, and the device comprises: a receiving unit and a processing unit; The receiving unit is used to receive a request instruction from a device connector; the request instruction is obtained by encoding corresponding request data of a target electronic control unit in the target vehicle based on a preset diagnostic protocol; The processing unit is used to determine target response data corresponding to the target electronic control unit based on the request instruction; The target response data is sent to the device connector, so that the device connector sends the target response data to the target diagnostic instrument, thereby enabling the target diagnostic instrument to perform a diagnostic operation on the target electronic control unit based on the target response data to obtain a target diagnostic result; the device connector is connected to the target diagnostic instrument.

9. An electronic device, characterized in that: The method comprises 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 one or more programs include methods for executing any one of claims 1-6.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and the computer program is executed by a processor to implement the method according to any one of claims 1 to 6.

Images