Vehicle remote diagnosis method and system, electronic equipment and storage medium

Abstract

The invention provides a vehicle remote diagnosis method and system, an electronic device and a storage medium, in the method, there is no need to pre-install a large AI model or a complex diagnosis program at a vehicle end, diagnosis logic and instruction generation (i.e., a diagnosis instruction sequence data packet) are completed at a cloud end, only a communication gateway is needed to execute simple instruction analysis and result feedback operation, and the vehicle remote diagnosis efficiency is improved. Occupation of vehicle end storage resources and operation resources is greatly reduced, the vehicle hardware cost is reduced, meanwhile, the tedious process of vehicle end model updating is avoided, the flexibility of a diagnosis scheme is improved, in addition, self-defined diagnosis instruction sequence editing is supported, diagnosis instructions can be flexibly configured, the limitation that only defined fault codes can be diagnosed in the traditional technology is broken through, and the diagnosis efficiency is improved. And multi-scene requirements can be covered, and the expansibility is good.

Description

Technical Field

[0001] This invention relates to the technical field of vehicle diagnostics, and in particular to a method, system, electronic device, and storage medium for remote vehicle diagnostics. Background Technology

[0002] With the continuous improvement of automotive electronics and intelligence, the complexity of vehicle fault diagnosis has also increased. Remote diagnostic technology has become an important means of vehicle after-sales maintenance because it can complete fault detection without on-site contact with the vehicle.

[0003] Currently, the main solutions for remote vehicle diagnostics include the following two types: One approach is a remote vehicle diagnostic method that combines artificial intelligence analysis with fault models. This method requires a large model file to be pre-installed on the vehicle. On the one hand, this will consume the vehicle's storage and computing resources, leading to increased hardware costs. On the other hand, updating the model file depends on the vehicle's software upgrade process, which is inflexible and difficult to adapt to different vehicle models or newly emerging fault types. Another method is remote vehicle diagnostics, which involves issuing remote diagnostic commands through a platform. This method only communicates with the server after the TBOX (Telematics Controller) obtains fault data. The diagnostic triggering condition is singular, and it can only perform diagnostics for scenarios where fault codes have been generated. It cannot meet the needs of preventive diagnostics or component performance testing when there are no fault codes. Furthermore, the fixed design of the diagnostic commands makes it impossible to flexibly adjust according to actual diagnostic needs, thus limiting its scalability.

[0004] In summary, traditional vehicle remote diagnostic methods suffer from technical problems such as consuming on-vehicle storage and computing resources, having fixed diagnostic commands, and poor scalability. Summary of the Invention

[0005] In view of this, the purpose of the present invention is to provide a method, system, electronic device and storage medium for remote vehicle diagnostics, so as to alleviate the technical problems of traditional remote vehicle diagnostics methods, such as occupying vehicle-side storage and computing resources, fixed diagnostic instructions and poor scalability.

[0006] In a first aspect, the present invention provides a method for remote vehicle diagnostics, comprising: Generate user-defined diagnostic instruction sequence data packets on the cloud platform and send them to the target vehicle via a secure link; The target vehicle's communication gateway receives and parses the diagnostic instruction sequence data packet, and then interacts with one or more ECUs of the target vehicle to perform diagnostic operations and collect diagnostic result data. The communication gateway transmits the diagnostic results data back to the cloud platform, where it is stored and visualized.

[0007] Furthermore, a user-defined diagnostic instruction sequence data package is generated on the cloud platform, including: The cloud platform provides a visual editing interface, and allows for the customization of diagnostic instruction sequences containing at least one diagnostic instruction and corresponding diagnostic parameters based on the UDS protocol; The diagnostic instruction sequence is subjected to syntax verification, and a diagnostic instruction sequence data packet is generated after the verification is passed.

[0008] Furthermore, the data is transmitted to the target vehicle via a secure link, including: The diagnostic instruction sequence data packet is sent to the TBOX of the target vehicle via an encrypted communication channel.

[0009] Furthermore, the communication gateway of the target vehicle receives and parses the diagnostic command sequence data packet, and then interacts with one or more ECUs of the target vehicle to perform diagnostic operations, including: After receiving the diagnostic instruction sequence data packet, the communication gateway decrypts and parses the diagnostic instruction sequence data packet to extract the diagnostic instruction and the corresponding diagnostic parameters. Based on the target ECU address in the diagnostic parameters, a diagnostic connection is established with the corresponding target ECU, and diagnostic commands are sent to the target ECU in the order of the diagnostic commands in the diagnostic command sequence data packet, so that the target ECU can perform diagnostic operations.

[0010] Furthermore, the communication gateway transmits the diagnostic result data back to the cloud platform, where it is stored and visualized, including: The communication gateway integrates all the diagnostic result data into a diagnostic result report, and sends the diagnostic result report back to the cloud platform through an encrypted communication channel; The cloud platform parses the diagnostic result report, stores the diagnostic result data in a structured format in the database, and generates a visual diagnostic result display interface for diagnostic engineers to view.

[0011] Furthermore, the diagnostic commands include at least one of the following: fault code reading command, sensor data acquisition command, actuator test command, and ECU version query command; The diagnostic parameters include at least one of the following: target ECU address, data acquisition frequency, diagnostic timeout time, and actuator test threshold.

[0012] Furthermore, if the diagnostic command fails to execute, the communication gateway records the abnormal information and continues to send subsequent diagnostic commands so that the target ECU can continue to perform subsequent diagnostic operations.

[0013] In a second aspect, the present invention also provides a system for remote vehicle diagnostics, for implementing the method as described in any of the first aspects, the system comprising: The cloud-based diagnostic module is used to generate user-defined diagnostic instruction sequence data packets. The TSP communication module is used to establish a secure link between the cloud diagnostic module and the target vehicle, and then send the diagnostic instruction sequence data packet to the target vehicle. The vehicle TBOX module is used to receive and parse the diagnostic command sequence data packet, and then interact with one or more ECUs of the target vehicle to perform diagnostic operations, collect diagnostic result data, and send the diagnostic result data back to the cloud diagnostic module for storage and visualization. The target ECU module is used to perform the diagnostic operation.

[0014] Thirdly, the present invention also provides an electronic device, including a memory and a processor, wherein the memory stores a computer program that can run on the processor, and the processor executes the computer program to implement the method described in the first aspect.

[0015] Fourthly, the present invention also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the method described in the first aspect.

[0016] This invention provides a method for remote vehicle diagnostics, comprising: generating a user-defined diagnostic instruction sequence data packet on a cloud platform and sending it to the target vehicle via a secure link; the target vehicle's communication gateway receiving and parsing the diagnostic instruction sequence data packet, and then interacting with one or more ECUs of the target vehicle to perform diagnostic operations and collect diagnostic result data; the communication gateway transmitting the diagnostic result data back to the cloud platform, where it is stored and visualized. As described above, this method eliminates the need for pre-installing large AI models or complex diagnostic programs on the vehicle. The diagnostic logic and instruction generation (i.e., the diagnostic instruction sequence data packet) are completed in the cloud, requiring only simple instruction parsing and result feedback operations from the communication gateway. This significantly reduces the consumption of vehicle-side storage and computing resources, lowers vehicle hardware costs, avoids the cumbersome process of updating vehicle-side models, and improves the flexibility of the diagnostic solution. Furthermore, it supports custom diagnostic instruction sequence editing, allowing for flexible configuration of diagnostic instructions. This overcomes the limitations of traditional technologies that can only diagnose defined fault codes, covering multiple scenarios and offering good scalability. It alleviates the technical problems of traditional remote vehicle diagnostic methods, such as consuming vehicle-side storage and computing resources, fixed diagnostic instructions, and poor scalability. Attached Figure Description

[0017] To more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0018] Figure 1 A flowchart illustrating a method for remote vehicle diagnostics provided in an embodiment of the present invention; Figure 2 A schematic diagram of a vehicle remote diagnostic system provided in an embodiment of the present invention; Figure 3 This is a schematic diagram of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0019] The technical solution of the present invention will be clearly and completely described below with reference to the embodiments. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0020] Traditional vehicle remote diagnostic methods consume vehicle-side storage and computing resources, have fixed diagnostic commands, and poor scalability.

[0021] Based on this, the vehicle remote diagnostic method of the present invention does not require pre-installation of large AI models or complex diagnostic programs on the vehicle. The diagnostic logic and instruction generation (i.e., diagnostic instruction sequence data packets) are completed in the cloud. Only the communication gateway needs to perform simple instruction parsing and result feedback operations, which greatly reduces the occupation of vehicle-side storage and computing resources, reduces vehicle hardware costs, avoids the cumbersome process of updating vehicle-side models, and improves the flexibility of diagnostic solutions. In addition, it supports the editing of custom diagnostic instruction sequences, which can flexibly configure diagnostic instructions, breaking through the limitation of traditional technologies that can only diagnose defined fault codes. It can cover multiple scenario requirements and has good scalability.

[0022] To facilitate understanding of this embodiment, a method for remote vehicle diagnostics disclosed in this embodiment of the invention will first be described in detail.

[0023] Example 1: According to an embodiment of the present invention, an embodiment of a method for remote vehicle diagnostics is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0024] Figure 1 This is a flowchart of a method for remote vehicle diagnostics according to an embodiment of the present invention, such as... Figure 1 As shown, the method includes the following steps: Step S102: Generate a user-defined diagnostic instruction sequence data packet on the cloud platform and send it to the target vehicle through a secure link; Specifically, the aforementioned cloud platform is a cloud-based diagnostic platform, and the aforementioned user can be a diagnostic engineer. The process of generating diagnostic instruction sequence data packets will be described in detail below, and will not be repeated here.

[0025] In step S104, the communication gateway of the target vehicle receives and parses the diagnostic instruction sequence data packet, and then interacts with one or more ECUs of the target vehicle to perform diagnostic operations and collect diagnostic result data. Specifically, the aforementioned communication gateway is TBOX.

[0026] In step S106, the communication gateway sends the diagnostic result data back to the cloud platform, where it is stored and visualized.

[0027] This invention provides a method for remote vehicle diagnostics, comprising: generating a user-defined diagnostic instruction sequence data packet on a cloud platform and sending it to the target vehicle via a secure link; the target vehicle's communication gateway receiving and parsing the diagnostic instruction sequence data packet, and then interacting with one or more ECUs of the target vehicle to perform diagnostic operations and collect diagnostic result data; the communication gateway transmitting the diagnostic result data back to the cloud platform, where it is stored and visualized. As described above, this method eliminates the need for pre-installing large AI models or complex diagnostic programs on the vehicle. The diagnostic logic and instruction generation (i.e., the diagnostic instruction sequence data packet) are completed in the cloud, requiring only simple instruction parsing and result feedback operations from the communication gateway. This significantly reduces the consumption of vehicle-side storage and computing resources, lowers vehicle hardware costs, avoids the cumbersome process of updating vehicle-side models, and improves the flexibility of the diagnostic solution. Furthermore, it supports custom diagnostic instruction sequence editing, allowing for flexible configuration of diagnostic instructions. This overcomes the limitations of traditional technologies that can only diagnose defined fault codes, covering multiple scenarios and offering good scalability. It alleviates the technical problems of traditional remote vehicle diagnostic methods, such as consuming vehicle-side storage and computing resources, fixed diagnostic instructions, and poor scalability.

[0028] The above provides a brief overview of the vehicle remote diagnostic method of the present invention. The specific details involved are described in detail below.

[0029] In an optional embodiment of the present invention, generating a user-defined diagnostic instruction sequence data packet on a cloud platform specifically includes the following steps: (1) The cloud platform provides a visual editing interface, and a diagnostic instruction sequence containing at least one diagnostic instruction and corresponding diagnostic parameters is customized based on the UDS protocol; Specifically, diagnostic engineers can customize diagnostic command sequences based on the UDS (Unified Diagnostic Service) protocol through the visual editing interface of the cloud-based diagnostic platform. The diagnostic command sequence includes at least one diagnostic command and corresponding diagnostic parameters. The diagnostic command can be selected from one or more of the following according to diagnostic needs: fault code reading command, sensor data acquisition command, actuator test command, and ECU (Electronic Control Unit) version query command. The diagnostic parameters include at least one of the following: target ECU address, data acquisition frequency, diagnostic timeout time, and actuator test threshold.

[0030] (2) Perform syntax verification on the diagnostic instruction sequence, and generate a diagnostic instruction sequence data packet after the verification is passed.

[0031] Specifically, the cloud-based diagnostic platform performs syntax verification on the edited diagnostic instruction sequence to ensure that the diagnostic instructions are compatible with the UDS protocol and that the diagnostic parameters are in the correct format. If the verification passes, a standardized diagnostic instruction sequence data packet is generated. If the verification fails, an error message is displayed and engineers are allowed to re-edit the data.

[0032] In an optional embodiment of the present invention, the data is sent to the target vehicle via a secure link, specifically including the following steps: Diagnostic command sequence data packets are sent to the target vehicle's TBOX via an encrypted communication channel.

[0033] Specifically, the cloud-based diagnostic platform sends the verified diagnostic instruction sequence data packet to the target vehicle's TBOX through an encrypted communication channel between the TSP (Remote Service Platform) and the vehicle's TBOX. The encrypted communication channel uses TLS (Transport Layer Security) to encrypt the data, ensuring the security and integrity of the diagnostic instruction sequence data packet during transmission and preventing data from being tampered with or stolen.

[0034] In an optional embodiment of the present invention, the communication gateway of the target vehicle receives and parses diagnostic command sequence data packets, and then interacts with one or more ECUs of the target vehicle to perform diagnostic operations, specifically including the following steps: (1) After receiving the diagnostic instruction sequence data packet, the communication gateway decrypts and parses the diagnostic instruction sequence data packet to extract the diagnostic instruction and the corresponding diagnostic parameters; (2) Based on the target ECU address in the diagnostic parameters, establish a diagnostic connection with the corresponding target ECU, and send diagnostic commands to the target ECU in the order of the diagnostic commands in the diagnostic command sequence data packet so that the target ECU can perform diagnostic operations.

[0035] Specifically, after receiving the diagnostic command sequence data packet, the TBOX decrypts and parses the packet to extract the diagnostic commands and corresponding diagnostic parameters. Based on the target ECU address in the diagnostic parameters, the TBOX determines the target ECU. Following the order of the diagnostic commands in the sequence data packet, the TBOX establishes a diagnostic communication connection with the target ECU, sequentially sending diagnostic commands and receiving diagnostic results from the target ECU. If a diagnostic command times out or the received feedback data is abnormal (i.e., the diagnostic command fails to execute), the TBOX records the error and continues to send subsequent diagnostic commands to enable the target ECU to perform subsequent diagnostics, thus preventing the entire diagnostic process from being interrupted due to a single command issue.

[0036] In an optional embodiment of the present invention, the communication gateway transmits the diagnostic result data back to the cloud platform, where it is stored and visualized. Specifically, this includes the following steps: (1) The communication gateway integrates all diagnostic result data into a diagnostic result report and sends the diagnostic result report back to the cloud platform through an encrypted communication channel; (2) The cloud platform parses the diagnostic results report, stores the diagnostic results data in a structured manner in the database, and generates a visual diagnostic results display interface for diagnostic engineers to view.

[0037] Specifically, TBOX integrates all diagnostic command results (including normal results and abnormal information) into a diagnostic result report, which is then fed back to the cloud diagnostic platform through an encrypted communication channel. The cloud diagnostic platform parses the diagnostic result report, stores the diagnostic result data in a structured manner in the database, and generates a visual diagnostic result display interface for diagnostic engineers to view and analyze. At the same time, the cloud diagnostic platform supports exporting the diagnostic result report to PDF or Excel format, which facilitates subsequent fault analysis and after-sales record archiving.

[0038] The present invention mainly solves the following technical problems: The problem of fixed diagnostic commands and lack of scalability is that traditional remote diagnostic solutions mostly use preset fixed formats for diagnostic commands, which cannot be flexibly adjusted according to actual diagnostic needs. On the one hand, the command types are limited to basic functions such as fault code reading, and cannot be extended to complex diagnostic operations such as sensor data acquisition and actuator threshold testing. On the other hand, they do not support custom diagnostic logic. When new diagnostic codes are needed, the commands of TBOX and each ECU need to be redefined and developed, which cannot quickly respond to the market's demand for new diagnostic functions.

[0039] The current vehicle after-sales diagnostics system heavily relies on physical diagnostic tools. However, these tools suffer from high procurement costs, poor portability, and slow updates, leading to a shortage of diagnostic equipment in remote after-sales service outlets and small repair shops, making it impossible to provide timely diagnostic services to users. Furthermore, physical diagnostic tools require on-site operation by engineers and cannot be used for remote diagnostics. When a vehicle experiences a complex fault requiring professional engineer support, the user must take the vehicle to a designated service center, increasing their time and financial costs. This limits the coverage and response efficiency of after-sales diagnostic services.

[0040] Given the shortcomings of the aforementioned traditional technologies, there is an urgent need for a vehicle remote diagnostic solution that does not require pre-installation of large models on the vehicle, allows for flexible customization of diagnostic commands, and can cover diagnostic needs across multiple scenarios. This solution aims to address the problem of insufficient diagnostic service coverage caused by the scarcity of after-sales diagnostic equipment, while also improving the scalability of diagnostic functions to meet diverse vehicle diagnostic needs.

[0041] This invention addresses the scarcity of after-sales diagnostic equipment and insufficient scalability of diagnostic functions by enabling users to customize diagnostic commands in the cloud and send them to the vehicle terminal for execution. This results in the following beneficial effects: Solving the problem of scarcity of after-sales diagnostic equipment: This invention achieves the same diagnostic functions as ordinary diagnostic equipment through a cloud-based diagnostic platform. Diagnostic engineers do not need to rely on on-site diagnostic equipment and can complete remote vehicle diagnostics through the cloud, which greatly reduces the dependence on physical diagnostic equipment and improves the coverage of after-sales diagnostic services. It is especially suitable for after-sales service outlets in remote areas or with insufficient diagnostic equipment.

[0042] Enhanced diagnostic functionality scalability: Based on the UDS protocol, it supports custom diagnostic sequence editing, and can flexibly configure various diagnostic commands such as fault code diagnosis, sensor detection, and actuator testing. It breaks through the limitation of existing technologies that can only diagnose defined fault codes, and can cover multiple scenarios such as preventive diagnosis, component performance evaluation, and ECU version verification, adapting to the diagnostic needs of different vehicle models and different fault types.

[0043] Reduce vehicle-side resource consumption: There is no need to pre-install large AI models or complex diagnostic programs on the vehicle side. The diagnostic logic and instruction generation are all completed in the cloud. Only TBOX needs to perform simple instruction parsing and result feedback operations, which greatly reduces the occupation of vehicle-side storage and computing resources, reduces vehicle hardware costs, avoids the cumbersome process of updating vehicle-side models, and improves the flexibility of diagnostic solutions.

[0044] To ensure the stability of the diagnostic process and data security: a syntax verification mechanism is used to ensure the validity of diagnostic commands and avoid vehicle-side malfunctions caused by invalid commands; a TLS encrypted communication channel is used to ensure data transmission security and prevent diagnostic commands or result data from being tampered with; at the same time, the TBOX can continue to execute subsequent commands even when a single command is abnormal, improving the stability of the diagnostic process.

[0045] Example 2: This invention also provides a vehicle remote diagnostic system, which is mainly used to execute the vehicle remote diagnostic method provided in Embodiment 1 of this invention. The vehicle remote diagnostic system provided in this invention will be described in detail below.

[0046] Figure 2 This is a schematic diagram of a vehicle remote diagnostic system according to an embodiment of the present invention, such as... Figure 2 As shown, the system mainly includes: a cloud-based diagnostic module 10, a TSP communication module 20, a vehicle TBOX module 30, and a target ECU module 40, wherein: The cloud-based diagnostic module is used to generate user-defined diagnostic instruction sequence data packets. The TSP communication module is used to establish a secure link between the cloud diagnostic module and the target vehicle, and then send diagnostic command sequence data packets to the target vehicle. The vehicle TBOX module is used to receive and parse diagnostic command sequence data packets, and then interact with one or more ECUs of the target vehicle to perform diagnostic operations, collect diagnostic result data, and send the diagnostic result data back to the cloud diagnostic module for storage and visualization. The target ECU module is used to perform diagnostic operations.

[0047] Specifically, the modules mentioned above interact with each other through a preset communication protocol.

[0048] In the vehicle remote diagnostic system of this invention, there is no need to pre-install large AI models or complex diagnostic programs on the vehicle. The diagnostic logic and instruction generation (i.e., diagnostic instruction sequence data packets) are all completed in the cloud. Only the communication gateway needs to perform simple instruction parsing and result feedback operations, which greatly reduces the occupation of vehicle-side storage and computing resources, reduces vehicle hardware costs, avoids the cumbersome process of vehicle-side model updates, and improves the flexibility of diagnostic solutions. In addition, it supports the editing of custom diagnostic instruction sequences, which can flexibly configure diagnostic instructions. It breaks through the limitation of traditional technologies that can only diagnose predefined fault codes, can cover multiple scenario requirements, has good scalability, and alleviates the technical problems of traditional vehicle remote diagnostic methods such as occupying vehicle-side storage and computing resources, fixed diagnostic instructions, and poor scalability.

[0049] Specifically, the cloud-based diagnostic module includes an instruction editing unit, a syntax verification unit, and a result storage and display unit. The instruction editing unit provides a visual interface for diagnostic engineers to edit custom diagnostic instruction sequences based on the UDS protocol. The syntax verification unit is used to verify the protocol compatibility and parameter format correctness of the diagnostic instruction sequences. The result storage and display unit is used to store diagnostic result data and generate a visual display interface.

[0050] TSP Communication Module: Serving as a communication bridge between the cloud and the vehicle, it establishes a two-way communication channel using the TLS encryption protocol to enable the distribution of diagnostic command sequence data packets and the uploading of diagnostic result reports, ensuring data transmission security.

[0051] The vehicle TBOX module includes a data decryption and parsing unit, a diagnostic execution unit, and a result integration and feedback unit. The data decryption and parsing unit is used to decrypt the diagnostic command sequence data packets sent from the cloud and extract the diagnostic commands and corresponding diagnostic parameters. The diagnostic execution unit is used to establish a connection with the target ECU, execute diagnostic commands, and receive diagnostic result data. The result integration and feedback unit is used to integrate the diagnostic result data, generate a diagnostic result report, and feed it back to the cloud.

[0052] Target ECU module: includes multiple vehicle electronic control units (such as engine ECU, transmission ECU, body control ECU, etc.), used to receive diagnostic commands sent by TBOX, execute corresponding operations and feed back diagnostic result data.

[0053] The system provided in this embodiment of the invention has the same implementation principle and technical effects as the aforementioned method embodiment. For the sake of brevity, any parts not mentioned in the system embodiment can be referred to the corresponding content in the aforementioned method embodiment.

[0054] like Figure 3As shown in the embodiment of this application, an electronic device 600 includes a processor 601, a memory 602, and a bus. The memory 602 stores machine-readable instructions executable by the processor 601. When the electronic device is running, the processor 601 communicates with the memory 602 via the bus, and the processor 601 executes the machine-readable instructions to perform the steps of the vehicle remote diagnostic method described above.

[0055] Specifically, the memory 602 and processor 601 can be general-purpose memory and processor, without any specific limitations. When the processor 601 runs the computer program stored in the memory 602, it can execute the above-mentioned method for remote vehicle diagnosis.

[0056] The processor 601 may be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method can be completed by the integrated logic circuitry in the hardware of the processor 601 or by instructions in software form. The processor 601 may be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; it may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor. The software module can reside in a mature storage medium in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. This storage medium is located in memory 602, and processor 601 reads the information from memory 602 and, in conjunction with its hardware, completes the steps of the above method.

[0057] Corresponding to the above-described method for remote vehicle diagnostics, this application also provides a computer-readable storage medium storing machine-executable instructions. When these machine-executable instructions are invoked and executed by a processor, they cause the processor to perform the steps of the above-described method for remote vehicle diagnostics.

[0058] The vehicle remote diagnostic system provided in this application embodiment can be specific hardware on a device or software or firmware installed on the device. The system provided in this application embodiment has the same implementation principle and technical effects as the aforementioned method embodiment. For the sake of brevity, any parts not mentioned in the system embodiment section can be referred to the corresponding content in the aforementioned method embodiment. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, units, and processes described above can all be referred to the corresponding processes in the above method embodiments, and will not be repeated here.

[0059] In the embodiments provided in this application, it should be understood that the disclosed systems and methods can be implemented in other ways. The system embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and there may be other division methods in actual implementation. Furthermore, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Additionally, the coupling or direct coupling or communication connection shown or discussed may be through some communication interface; the indirect coupling or communication connection between systems or units may be electrical, mechanical, or other forms.

[0060] For example, the flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than those marked in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram and / or flowchart, and combinations of blocks in block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

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

[0062] In addition, the functional units in the embodiments provided in this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0063] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause an electronic device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the vehicle remote diagnostic method described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0064] It should be noted that similar labels and letters in the following figures indicate similar items. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures. In addition, the terms "first", "second", "third", etc. are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0065] Finally, it should be noted that the above-described embodiments are merely specific implementations of this application, used to illustrate the technical solutions of this application, and not to limit them. The protection scope of this application is not limited thereto. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can still modify or easily conceive of changes to the technical solutions described in the foregoing embodiments, or make equivalent substitutions for some of the technical features, within the scope of the technology disclosed in this application; and these modifications, changes, or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application. All should be covered within the protection scope of this application. Therefore, the protection scope of this application should be determined by the protection scope of the claims.

Claims

1. A method for remote vehicle diagnostics, characterized in that, include: Generate user-defined diagnostic instruction sequence data packets on the cloud platform and send them to the target vehicle via a secure link; The target vehicle's communication gateway receives and parses the diagnostic instruction sequence data packet, and then interacts with one or more ECUs of the target vehicle to perform diagnostic operations and collect diagnostic result data. The communication gateway transmits the diagnostic results data back to the cloud platform, where it is stored and visualized.

2. The method according to claim 1, characterized in that, Generate a user-defined diagnostic instruction sequence data package on the cloud platform, including: The cloud platform provides a visual editing interface, and allows users to customize a diagnostic instruction sequence that includes at least one diagnostic instruction and corresponding diagnostic parameters based on the UDS protocol. The diagnostic instruction sequence is subjected to syntax verification, and a diagnostic instruction sequence data packet is generated after the verification is passed.

3. The method according to claim 1, characterized in that, The message is sent to the target vehicle via a secure link, including: The diagnostic instruction sequence data packet is sent to the TBOX of the target vehicle via an encrypted communication channel.

4. The method according to claim 1, characterized in that, The target vehicle's communication gateway receives and parses the diagnostic command sequence data packet, and then interacts with one or more ECUs of the target vehicle to perform diagnostic operations, including: After receiving the diagnostic instruction sequence data packet, the communication gateway decrypts and parses the diagnostic instruction sequence data packet to extract the diagnostic instruction and the corresponding diagnostic parameters. Based on the target ECU address in the diagnostic parameters, a diagnostic connection is established with the corresponding target ECU, and diagnostic commands are sent to the target ECU in the order of the diagnostic commands in the diagnostic command sequence data packet, so that the target ECU can perform diagnostic operations.

5. The method according to claim 1, characterized in that, The communication gateway transmits the diagnostic result data back to the cloud platform, where it is stored and visualized. The communication gateway integrates all the diagnostic result data into a diagnostic result report, and sends the diagnostic result report back to the cloud platform through an encrypted communication channel; The cloud platform parses the diagnostic result report, stores the diagnostic result data in a structured format in the database, and generates a visual diagnostic result display interface for diagnostic engineers to view.

6. The method according to claim 2, characterized in that, The diagnostic commands include at least one of the following: fault code reading command, sensor data acquisition command, actuator test command, and ECU version query command; The diagnostic parameters include at least one of the following: target ECU address, data acquisition frequency, diagnostic timeout time, and actuator test threshold.

7. The method according to claim 4, characterized in that, If the diagnostic command fails to execute, the communication gateway records the abnormal information and continues to send subsequent diagnostic commands so that the target ECU can continue to perform subsequent diagnostic operations.

8. A system for remote vehicle diagnostics, characterized in that, The system for implementing the method as described in any one of claims 1 to 7 comprises: The cloud-based diagnostic module is used to generate user-defined diagnostic instruction sequence data packets. The TSP communication module is used to establish a secure link between the cloud diagnostic module and the target vehicle, and then send the diagnostic instruction sequence data packet to the target vehicle. The vehicle TBOX module is used to receive and parse the diagnostic command sequence data packet, and then interact with one or more ECUs of the target vehicle to perform diagnostic operations, collect diagnostic result data, and send the diagnostic result data back to the cloud diagnostic module for storage and visualization. The target ECU module is used to perform the diagnostic operation.

9. An electronic device comprising a memory and a processor, wherein the memory stores a computer program executable on the processor, characterized in that, When the processor executes the computer program, it implements the method of any one of claims 1 to 7.

10. A computer-readable storage medium storing a computer program thereon, characterized in that, The computer program is executed by the processor to perform the method of any one of claims 1 to 7.

Images