Vehicle remote diagnosis method

By configuring a relational database on the cloud platform, diagnostic task packages adapted to different vehicles are automatically generated, solving the problems of low diagnostic efficiency and safety risks in existing technologies, and realizing efficient and safe remote diagnostics for multiple vehicles.

CN122284566APending Publication Date: 2026-06-26DONGFENG MOTOR GRP

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
DONGFENG MOTOR GRP
Filing Date
2026-03-11
Publication Date
2026-06-26

AI Technical Summary

Technical Problem

In existing automotive remote diagnostic technologies, diagnostic tasks need to be configured individually for different brands and models of vehicles, resulting in low diagnostic efficiency and the safety risk of false alarms.

Method used

By configuring a relational database on the cloud platform, diagnostic task packages adapted to different vehicles can be automatically generated, including basic vehicle data, component diagnostic specifications, and diagnostic strategies, enabling batch configuration of diagnostic tasks for multiple vehicles.

Benefits of technology

It improves the efficiency and safety of vehicle diagnostics, reduces human error in configuration, and ensures the accuracy and consistency of diagnostic results.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN122284566A_ABST
    Figure CN122284566A_ABST
Patent Text Reader

Abstract

This invention provides a vehicle remote diagnostic method, belonging to the field of automotive remote diagnostic technology. The method includes: configuring a vehicle remote diagnostic association database, which at least contains basic vehicle data, component diagnostic specifications, diagnostic process scripts, and diagnostic strategies; responding to an instruction to create diagnostic tasks for multiple target vehicles, automatically generating a diagnostic task package for each target vehicle based on the association database; and responding to a diagnostic task package detection request sent after vehicle startup, sending the corresponding diagnostic task package to the vehicle terminal based on the vehicle identification number in the diagnostic task package detection request for the vehicle terminal to execute the diagnostic process within the diagnostic task package. This invention proposes an adaptive dynamic configuration solution based on a remote diagnostic cloud platform, enabling batch remote fault diagnosis of vehicles of multiple brands, series, and models, effectively improving the efficiency of vehicle remote diagnostics.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of automotive remote diagnostics technology, and in particular to a method for remote vehicle diagnostics. Background Technology

[0002] With the continuous development of society, automobiles have gradually become an important means of transportation for the general public. Various brands and models of cars are emerging in large numbers, and the electronic control units (ECUs) they are equipped with are becoming increasingly complex. While enjoying the convenience that cars bring, it is also necessary to consider the issue of vehicle diagnostics when the controller's hardware or software malfunctions.

[0003] Remote vehicle diagnostics is a fault diagnosis technology that has become increasingly popular in recent years. When a car part malfunctions, the car manufacturer does not need to go to the site to perform vehicle diagnostics. Instead, online diagnostics can be performed through a DOTA (Diagnostic Over-The-Air) cloud platform to determine the location of the vehicle fault and provide repair suggestions. Summary of the Invention

[0004] The present invention aims to solve at least one of the technical problems existing in the prior art, and proposes a vehicle remote diagnostic method for adaptive dynamic configuration diagnostic tasks.

[0005] In a first aspect, embodiments of the present invention provide a vehicle remote diagnostic method, comprising: configuring a vehicle remote diagnostic association database, the association database including at least vehicle basic data, component diagnostic specifications, diagnostic process scripts, and diagnostic strategies; in response to receiving an instruction to create diagnostic tasks for multiple target vehicles, automatically generating a diagnostic task package for each target vehicle based on the association database; and in response to receiving a diagnostic task package detection request sent after vehicle startup, sending a corresponding diagnostic task package to the vehicle terminal based on the vehicle identification number in the diagnostic task package detection request so that the vehicle terminal can execute the diagnostic process in the diagnostic task package.

[0006] According to an embodiment of the present invention, configuring basic vehicle data includes: entering brand, vehicle series, vehicle model, parts, and vehicle identification number; and binding the association between vehicle model and parts.

[0007] According to an embodiment of the present invention, configuring a part diagnostic specification and a diagnostic process script includes: importing a part diagnostic specification file; parsing the part diagnostic specification file into structured diagnostic data consisting of diagnostic data identifiers, diagnostic fault codes, diagnostic parameter configurations, and input / output control information; and configuring a diagnostic process script corresponding to the structured diagnostic data.

[0008] According to an embodiment of the present invention, configuring a diagnostic strategy includes: configuring an applicable scope; the applicable scope is characterized by brand, vehicle series or model; configuring a strategy type; the strategy type includes periodic diagnostic type and single diagnostic type; configuring triggering conditions; the triggering conditions include preconditions and execution conditions that need to be detected in real time during the diagnostic process.

[0009] According to an embodiment of the present invention, a diagnostic task package is automatically generated for each target vehicle, including: obtaining vehicle information based on a received task mode; the task mode includes execution by vehicle series or model, execution by list, and execution by sales status; generating a diagnostic task package for each target vehicle by calling the corresponding diagnostic strategy, diagnostic process script, and vehicle basic data based on the vehicle information; and releasing the diagnostic task package in response to approval by operations review personnel.

[0010] According to an embodiment of the present invention, the vehicle-side execution of the diagnostic process in the diagnostic task package includes: the vehicle-side downloading and parsing the diagnostic task package; in response to the current state of the vehicle meeting the triggering conditions in the diagnostic strategy, the vehicle-side executing the diagnostic strategy and the diagnostic process script; and the vehicle-side reporting the diagnostic results.

[0011] According to an embodiment of the present invention, the method further includes: in response to receiving a diagnostic result reported by the vehicle, parsing the diagnostic result and matching it with a maintenance case library to generate a maintenance suggestion.

[0012] This invention provides a vehicle remote diagnostic system capable of implementing the aforementioned vehicle remote diagnostic method, comprising: a configuration module for configuring a relational database for vehicle remote diagnostics, the relational database including at least vehicle basic data, component diagnostic specifications, diagnostic process scripts, and diagnostic strategies; a task module for automatically generating a diagnostic task package for each target vehicle based on the relational database in response to receiving an instruction to create diagnostic tasks for multiple target vehicles; and a diagnostic module for sending a corresponding diagnostic task package to the vehicle terminal based on the vehicle identification number in the diagnostic task package detection request after the vehicle starts, in response to receiving a diagnostic task package detection request sent after the vehicle starts, so that the vehicle terminal can execute the diagnostic process in the diagnostic task package.

[0013] A third aspect of the present invention provides an electronic device comprising: one or more processors; and a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors perform the aforementioned vehicle remote diagnostic method.

[0014] A fourth aspect of the present invention also provides a computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, cause the processor to perform the above-described vehicle remote diagnostic method.

[0015] The vehicle remote diagnostic method provided by this invention establishes an association database to collect the data foundation required for diagnostic task packages. Since a single configuration can adaptively generate diagnostic task packages for multiple vehicles in batches, it at least partially solves the technical problem of needing to reconfigure diagnostic task packages for different vehicle models, and efficiently realizes fully automated remote diagnostics from cloud configuration to vehicle-side diagnostics. Attached Figure Description

[0016] Figure 1 This is a flowchart illustrating a remote vehicle diagnostic method provided in an embodiment of the present invention.

[0017] Figure 2 This is a schematic diagram of the vehicle-side cloud process in an embodiment of the present invention;

[0018] Figure 3 This is a flowchart illustrating an optional specific implementation method of step S1 in an embodiment of the present invention;

[0019] Figure 4 This is a structural block diagram of a vehicle remote diagnostic system provided in an embodiment of the present invention;

[0020] Figure 5 This is a structural block diagram of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0021] To enable those skilled in the art to better understand the technical solutions of the present invention, exemplary embodiments of the present invention are described below in conjunction with the accompanying drawings, including various details of the embodiments of the present invention to aid understanding. These should be considered merely exemplary. Therefore, those skilled in the art should recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the present invention. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0022] Where there is no conflict, the various embodiments of the present invention and the features thereof may be combined with each other.

[0023] As used herein, the term “and / or” includes any and all combinations of one or more related enumerated entries.

[0024] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the invention. As used herein, the singular forms “a” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that when the terms “comprising” and / or “made of” are used in this specification, the presence of the stated feature, integral, step, operation, element, and / or component is specified, but the presence or addition of one or more other features, integrals, steps, operations, elements, components, and / or groups thereof is not excluded. Terms such as “connected” or “linked” are not limited to physical or mechanical connections but can include electrical connections, whether direct or indirect.

[0025] Unless otherwise specified, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art. It will also be understood that terms such as those defined in commonly used dictionaries should be interpreted as having the meaning consistent with their meaning in the context of the relevant art and the invention, and will not be interpreted as having an idealized or overly formal meaning unless expressly so defined herein.

[0026] In the technical solution of this invention, the collection, storage, use, processing, transmission, provision, and disclosure of user personal information all comply with relevant laws and regulations and do not violate public order and good morals. The use of user data in this technical solution follows relevant national laws and regulations (e.g., the "Information Security Technology - Personal Information Security Specification"). For example: appropriate measures are taken for personal information access control; restrictions are imposed on the display of personal information; the purpose of using personal information does not exceed the scope of direct or reasonable association; and explicit identity targeting is eliminated when using personal information to avoid precisely locating a specific individual.

[0027] Existing automotive remote diagnostic technologies typically target a single ECU (Electronic Control Unit) or multiple ECUs in a specific vehicle. This is achieved by configuring diagnostic tasks and specifications in the cloud and sending them to the vehicle. The vehicle then detects the diagnostic task under specific conditions and performs fault diagnosis on the vehicle's ECUs according to the diagnostic specifications.

[0028] This remote diagnostic solution also has significant drawbacks. Because diagnostic task configuration is tailored to specific target vehicles, different brands of vehicles often require different diagnostic tasks, leading to low efficiency when performing multi-vehicle diagnostics. The market offers vehicles of various brands and models, each with different component data. Remote vehicle diagnostics necessitates personalized diagnostic task configuration for each vehicle, resulting in numerous configuration tasks, each containing different diagnostic component data. Platform operators must dedicate substantial time and effort to configuring these tasks. Incorrect configuration data can pose a safety risk of false alarms, severely impacting the user experience and damaging the vehicle manufacturer's reputation for quality.

[0029] To address the problems of existing technical solutions mentioned above, this invention proposes a multi-vehicle remote diagnostic method with adaptive dynamic configuration of diagnostic tasks, automatically generating different diagnostic tasks for different vehicles. This method pre-synchronizes basic data, including brand, vehicle series, model, and parts data, on a cloud platform. After parsing the parts diagnostic specifications, it configurates the platform and adaptively generates different diagnostic task packages by configuring a task on the platform. These packages are then pushed to target vehicles of different brands, series, and models, completing batch diagnostics for multiple vehicles. This invention significantly improves the efficiency and safety of vehicle diagnostics.

[0030] To address at least one of the technical problems existing in the aforementioned related technologies, the present invention provides a method for remote vehicle diagnostics. Figure 1 This is a flowchart illustrating a vehicle remote diagnostic method provided in an embodiment of the present invention, as shown below. Figure 1 As shown, this embodiment of the invention provides a method for remote vehicle diagnostics, comprising:

[0031] S1 configures the relational database for vehicle remote diagnostics. This database includes at least basic vehicle data, component diagnostic specifications, diagnostic process scripts, and diagnostic strategies. It standardizes and establishes relational mappings for all types of basic data, diagnostic specifications, execution scripts, and strategy rules required for vehicle remote diagnostics, forming a database that can be programmably accessed by the DOTA platform and visually managed by operations personnel.

[0032] S2, in response to receiving an instruction to create diagnostic tasks for multiple target vehicles, automatically generates a diagnostic task package for each target vehicle based on the relational database. When the DOTA platform receives an instruction from operations personnel to create diagnostic tasks for multiple target vehicles, unlike traditional technologies that configure diagnostic tasks individually for each vehicle, it automatically retrieves the corresponding core elements based on the configured relational database and the characteristics of the target vehicles, such as brand, model, and vehicle type, to adaptively generate a diagnostic task package for each target vehicle. Operations personnel only need to initiate the instruction to create multi-vehicle diagnostic tasks; there is no need for personalized configuration of individual vehicles. The platform will automatically and differentiate the generation of diagnostic task packages through the mapping logic of the relational database, achieving batch configuration of multi-vehicle diagnostic tasks.

[0033] S3, in response to receiving a diagnostic task package detection request sent after vehicle startup, sends the corresponding diagnostic task package to the vehicle based on the vehicle identification number (VIN) in the diagnostic task package detection request, allowing the vehicle to execute the diagnostic process within the task package. After the diagnostic task package is generated and published, it is stored in the DOTA cloud platform, awaiting triggering of the detection mechanism by the vehicle. When the user's vehicle starts, the vehicle obtains basic vehicle information from the DOTA cloud platform and executes the detection program, checking with the DOTA cloud platform based on the vehicle's VIN (Vehicle Identification Number) to see if the vehicle is configured with a task package. The DOTA cloud platform matches the corresponding diagnostic task package based on the VIN and sends it to the vehicle. Upon receiving the task package, the vehicle performs fault diagnosis operations according to the diagnostic process within the package.

[0034] Figure 2 This is a schematic diagram of the vehicle-to-cloud process in an embodiment of the present invention, such as... Figure 2 As shown, operators complete the following tasks on the DOTA cloud platform: manually input basic data such as brand, vehicle series, model, and parts; input parts diagnostic specifications; configure parts diagnostic processes; configure and review diagnostic strategies; configure diagnostic tasks, associate them with target vehicles, and dynamically and adaptively assemble diagnostic task packages for each target vehicle; review and publish tasks. After the vehicle is powered on, it obtains the corresponding vehicle model and parts information configured on the DOTA cloud and matches the diagnostic task package for the current vehicle based on the vehicle information. After downloading the diagnostic task package, the vehicle decrypts and verifies the signature, performs pre-diagnostic condition checks, and finally reports the diagnostic results after diagnosis. The DOTA platform parses the diagnostic results and matches them with corresponding repair cases.

[0035] Figure 3 This is a flowchart illustrating an optional specific implementation method of step S1 in an embodiment of the present invention, such as... Figure 3As shown, this specifically includes: configuring basic vehicle data; configuring component diagnostic specifications; configuring diagnostic process scripts; and configuring diagnostic strategies. The configuration process of the relational database is a prerequisite for the DOTA platform. It can be automated by synchronizing basic data from the upstream MAS system when the vehicle is offline, or it can be manually entered and supplemented by DOTA platform operators through the web management platform. This involves entering the corresponding basic data such as brand, vehicle series, model, parts, and vehicle, and binding the relationships between vehicle series / model and parts. This establishes the relationships between vehicle series / model parts, component diagnostic specifications, component diagnostic processes, and diagnostic strategies. When creating diagnostic tasks, the system can dynamically and adaptively configure tasks for each target vehicle, automatically generating task packages. This greatly improves the configuration efficiency of multi-vehicle diagnostic tasks, reduces human error, and ensures the safety of the diagnostic process.

[0036] Based on the above embodiments, configure basic vehicle data, including: entering brand, vehicle series, model, parts and vehicle identification number; and binding the association between model and parts.

[0037] In this embodiment, two data entry methods are provided: one is automated synchronization, whereby the upstream MAS system directly synchronizes the vehicle's basic data to the DOTA system when the vehicle rolls off the production line, achieving automated data collection and reducing manual data entry workload; the other is manual supplementary entry, where DOTA platform operators manually enter vehicle data that has not been automatically synchronized, newly added model data, or corrected data through the web management platform, ensuring the integrity of the basic data. The combination of these two methods achieves full and accurate entry of vehicle basic data.

[0038] Through the embodiments of the present invention, after data entry is completed, the vehicle model and parts need to be associated and bound. The association and binding relationship between the vehicle model and parts is the basis for the subsequent platform to retrieve the part diagnostic specifications and configure the diagnostic process script, ensuring that the diagnostic task of a certain vehicle model can only retrieve its exclusive part-related diagnostic elements.

[0039] Based on the above embodiments, the component diagnostic specifications and diagnostic process scripts are configured, including: importing the component diagnostic specification file; parsing the component diagnostic specification file into structured diagnostic data consisting of diagnostic data identifiers, diagnostic fault codes, diagnostic parameter configurations, and input / output control information; and configuring the diagnostic process script corresponding to the structured diagnostic data.

[0040] In this embodiment, component diagnostic specifications are imported. For components across different vehicle models, xlsx or PDX files are imported and automatically parsed into content easily recognizable and viewable by the platform. This includes crucial diagnostic specification data such as diagnostic DIDs (Data Identifiers), diagnostic fault codes, diagnostic parameter configurations, and I / O control. Diagnostic results are then parsed according to these specifications. A component diagnostic process script is configured. This script is a set of task-related instructions, including reading fault codes and writing configuration information. During vehicle diagnostics, these instructions are executed sequentially according to the diagnostic process. On the DOTA cloud platform, operators create or define an executable sequence of diagnostic operations for a specific component (ECU). For example, for a diagnostic process for an Engine Control Module (ECM), the script might include instructions such as reading all current fault codes (DTCs), clearing historical fault codes, writing a calibration parameter, and rereading fault codes to confirm the operation results. When the vehicle performs a diagnostic, it strictly follows the preset order of instructions in this script, sending diagnostic requests to the corresponding ECUs sequentially to complete systematic testing or maintenance.

[0041] Through the embodiments of this invention, standardized diagnostic process scripts enable unified specifications for vehicle-side diagnostic operations, ensuring consistency in diagnostic processes for similar parts. This improves the comparability and reliability of fault diagnosis results, facilitating unified analysis and management of vehicle faults for automakers. Furthermore, both part diagnostic specifications and diagnostic process scripts are bound to vehicle models and parts, allowing the platform to quickly retrieve the corresponding diagnostic specifications and process scripts based on the target vehicle's model and parts when generating diagnostic task packages.

[0042] Based on the above embodiments, a diagnostic strategy is configured, including: configuring the scope of application; the scope of application is characterized by brand, vehicle series or model; configuring the strategy type; the strategy type includes periodic diagnostic type and single diagnostic type; configuring the triggering conditions; the triggering conditions include preconditions and execution conditions that need to be detected in real time during the diagnostic process; after configuring the diagnostic strategy, the operations personnel need to review it on the DOTA platform, and only the strategy that has passed the review can be selected and executed by the task.

[0043] In this embodiment, a diagnostic strategy for the vehicle is configured. The diagnostic strategy includes basic strategy information, strategy type, and strategy parameter settings. The basic strategy information is associated with the brand, vehicle series, and model. The strategy type can be set to periodic or once-in-a-lifetime, indicating whether the strategy is executed periodically or once. The strategy condition settings include preconditions and execution conditions. During the diagnostic process, the vehicle will periodically check whether it meets the set diagnostic conditions; otherwise, it will exit the current diagnostic execution. Preconditions refer to the basic conditions that the vehicle must meet before executing the diagnostic task, such as the vehicle being started, the vehicle speed being 0, and the battery voltage being within the normal range. Only when the vehicle meets the preconditions will the vehicle-side diagnostic process be initiated.

[0044] Through embodiments of this invention, by configuring the scope of application of diagnostic strategies based on brand, vehicle series, and model, hierarchical and precise coverage of diagnostic strategies is achieved. Operators can precisely apply diagnostic strategies to specific vehicle groups according to diagnostic needs, and uniformly create, review, modify, and delete diagnostic strategies on the DOTA platform. For example, for specific fault diagnosis of a particular vehicle model, it is only necessary to configure the scope of application of the strategy to that model, without initiating diagnostics for other models, thus reducing invalid data transmission between the cloud and the vehicle.

[0045] Based on the above embodiments, a diagnostic task package is automatically generated for each target vehicle, including: obtaining vehicle information according to the received task mode; the task mode includes execution by vehicle series or model, execution by list, and execution by sales status; based on the vehicle information, calling the corresponding diagnostic strategy, diagnostic process script, and vehicle basic data to generate a diagnostic task package for each target vehicle; and releasing the diagnostic task package in response to approval by the operations review personnel.

[0046] In this embodiment, after the diagnostic strategy is approved, the operator configures a diagnostic task on the DOTA platform, sets the task type, selects the task mode (including execution by vehicle series / model, execution by list, and execution by sales status), and then selects the target vehicle or imports a batch of vehicles. Multiple vehicle diagnostic task packages are automatically assembled based on the vehicle information, and the task package content is dynamically configured adaptively, including vehicle diagnostic strategies, diagnostic processes, diagnostic parts related to vehicle models, and other information. The information of the task package can also be adjusted online. After the task is created and submitted, it needs to be reviewed and published by the relevant operator. Only task packages in the published state can be detected and the diagnostic process executed by the vehicle.

[0047] Through the embodiments of the present invention, in traditional remote diagnostic technology, configuring a diagnostic task for a single vehicle requires manual completion of multiple steps, resulting in low configuration efficiency when diagnosing multiple vehicles. In contrast, in this technical solution, operators only need to select the task mode and initiate a creation command, and the platform can automatically generate exclusive diagnostic task packages for hundreds or thousands of target vehicles. The entire process does not require manual configuration of individual vehicles, thus improving the configuration efficiency of diagnostic tasks.

[0048] Based on the above embodiments, the vehicle executes the diagnostic process in the diagnostic task package, including: the vehicle downloads and parses the diagnostic task package; in response to the current state of the vehicle meeting the triggering conditions in the diagnostic strategy, the vehicle executes the diagnostic strategy and diagnostic process script; and the vehicle reports the diagnostic results.

[0049] In this embodiment, if the vehicle detects a task package, it will actively download the task package and, through decryption and signature verification, ultimately parse out the content information of the task package. Based on the policy information in the task package, it will determine whether the vehicle meets the diagnostic conditions. If it does, the vehicle's ECU components will be diagnosed according to the diagnostic policy and diagnostic process specifications. If the conditions are not met, the diagnostic mode will be exited directly.

[0050] In this embodiment of the invention, after parsing the diagnostic task package, the vehicle-side does not immediately execute the diagnostic process. Instead, it first verifies the trigger conditions of the vehicle's current state, i.e., whether the current state of the vehicle meets the preconditions configured in the diagnostic strategy. If the current state of the vehicle does not meet the preconditions, the vehicle-side will directly exit the diagnostic mode without performing any diagnostic operations. If the current state of the vehicle meets the preconditions, the vehicle-side will start the diagnostic process and strictly execute the diagnostic operations according to the order of the diagnostic process script. During the execution of the diagnostic process, the vehicle-side will monitor the current state of the vehicle in real time to determine whether the execution conditions in the diagnostic strategy are met. If the execution conditions are broken, such as the vehicle stalling or accelerating during the diagnostic process, the vehicle-side will immediately exit the current diagnostic execution, ensuring that the diagnostic operation is only performed under safe and suitable conditions. When executing the diagnostic process, the vehicle-side will use the component diagnostic specifications as the judgment standard to perform fault detection on each ECU component of the vehicle, read fault codes, configure detection parameters, and perform IO control operations to accurately determine whether a component is faulty, thus solving the problems of non-standardized diagnostic operations and inaccurate diagnostic results in traditional vehicle-side diagnostics.

[0051] Based on the above embodiments, the method further includes: in response to receiving a diagnostic result reported by the vehicle, parsing the diagnostic result and matching it with a maintenance case library to generate maintenance suggestions.

[0052] In this embodiment, after the diagnosis is completed, the vehicle will report the diagnosis results of the ECU to the DOTA cloud. After receiving the diagnosis results, the cloud will parse the specific fault information of each ECU based on information such as DTC (Diagnostic Trouble Code) and match the corresponding cases in the repair case library to provide repair suggestions. At the same time, the operators can view the vehicle's historical diagnostic records through the DOTA cloud platform.

[0053] Through the embodiments of the present invention, accurate fault location and feasible repair suggestions enable automakers to quickly develop repair plans, achieve rapid fault handling, and significantly shorten the time from fault diagnosis to resolution.

[0054] Figure 4 This is a structural block diagram of a vehicle remote diagnostic system provided in an embodiment of the present invention, such as... Figure 4 As shown, the present invention provides a vehicle remote diagnostic system 400, which can be used to implement the above-mentioned vehicle remote diagnostic method, including: a configuration module for configuring a relational library for vehicle remote diagnostics, the relational library including at least vehicle basic data, part diagnostic specifications, diagnostic process scripts and diagnostic strategies; a task module for automatically generating a diagnostic task package for each target vehicle based on the relational library in response to receiving an instruction to create diagnostic tasks for multiple target vehicles; and a diagnostic module for sending a corresponding diagnostic task package to the vehicle end based on the vehicle identification number in the diagnostic task package detection request after the vehicle starts, in response to receiving a diagnostic task package detection request sent after the vehicle starts, so that the vehicle end can execute the diagnostic process in the diagnostic task package.

[0055] Based on the same inventive concept, embodiments of the present invention also provide an electronic device. Figure 5 This is a structural block diagram of an electronic device provided in an embodiment of the present invention. Figure 5 As shown, an embodiment of the present invention provides an electronic device including: one or more processors 101, a memory 102, and one or more I / O interfaces 103. The memory 102 stores one or more programs, which, when executed by the one or more processors, enable the one or more processors to implement any of the vehicle remote diagnostic methods described in the above embodiments; the one or more I / O interfaces 103 are connected between the processors and the memory, configured to enable information interaction between the processors and the memory.

[0056] The processor 101 is a device with data processing capabilities, including but not limited to a central processing unit (CPU); the memory 102 is a device with data storage capabilities, including but not limited to random access memory (RAM, more specifically SDRAM, DDR, etc.), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), and flash memory (FLASH); the I / O interface (read / write interface) 103 is connected between the processor 101 and the memory 102, and can realize information interaction between the processor 101 and the memory 102, including but not limited to a data bus (Bus).

[0057] In some embodiments, the processor 101, memory 102, and I / O interface 103 are interconnected via bus 104, and thus connected to other components of the computing device.

[0058] In some embodiments, the one or more processors 101 include a field-programmable gate array.

[0059] This invention also provides a computer-readable medium. The computer-readable medium stores a computer program, which, when executed by a processor, implements the steps of any of the vehicle remote diagnostic methods described in the above embodiments. The computer-readable storage medium may be volatile or non-volatile.

[0060] This invention also provides a computer program product, including computer-readable code, or a non-volatile computer-readable storage medium carrying computer-readable code. When the computer-readable code is run in the processor of an electronic device, the processor in the electronic device executes the above-described vehicle remote diagnostic method.

[0061] Those skilled in the art will understand that all or some of the steps, systems, and apparatuses disclosed above, and their functional modules / units, can be implemented as software, firmware, hardware, or suitable combinations thereof. In hardware implementations, the division between functional modules / units mentioned above does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed collaboratively by several physical components. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit (ASIC). Such software can be distributed on a computer-readable storage medium, which may include computer storage media (or non-transitory media) and communication media (or transient media).

[0062] As is known to those skilled in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information, such as computer-readable program instructions, data structures, program modules, or other data. Computer storage media includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), static random access memory (SRAM), flash memory or other memory technologies, portable compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical disc storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible to a computer. Furthermore, it is known to those skilled in the art that communication media typically contain computer-readable program instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.

[0063] The computer-readable program instructions described herein can be downloaded from computer-readable storage media to various computing / processing devices, or downloaded via a network, such as the Internet, local area network, wide area network, and / or wireless network, to an external computer or external storage device. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards them to the computer-readable storage media in the respective computing / processing device.

[0064] The computer program instructions used to perform the operations of this invention may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Smalltalk, C++, etc., and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The computer-readable program instructions may be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or may be connected to an external computer (e.g., via the Internet using an Internet service provider). In some embodiments, electronic circuitry, such as programmable logic circuitry, field-programmable gate arrays (FPGAs), or programmable logic arrays (PLAs), is personalized by utilizing state information from the computer-readable program instructions. This electronic circuitry can execute the computer-readable program instructions to implement various aspects of the invention.

[0065] The computer program product described herein can be implemented specifically through hardware, software, or a combination thereof. In one alternative embodiment, the computer program product is specifically embodied in a computer storage medium; in another alternative embodiment, the computer program product is specifically embodied in a software product, such as a software development kit (SDK), etc.

[0066] Various aspects of the present invention are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-readable program instructions.

[0067] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that, when executed by the processor of the computer or other programmable data processing apparatus, they create means for implementing the functions / actions specified in one or more blocks of the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium that causes a computer, programmable data processing apparatus, and / or other device to operate in a particular manner; thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing aspects of the functions / actions specified in one or more blocks of the flowchart and / or block diagram.

[0068] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to perform the functions / actions specified in one or more boxes of a flowchart and / or block diagram.

[0069] 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 the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of an instruction, which contains one or more executable instructions for implementing a specified logical function. In some alternative implementations, the functions marked in the blocks may occur in a different order than those shown 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 the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may 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.

[0070] Example embodiments have been disclosed herein, and while specific terminology has been used, it is for illustrative purposes only and should be construed as such, and is not intended to be limiting. In some instances, it will be apparent to those skilled in the art that features, characteristics, and / or elements described in conjunction with particular embodiments may be used alone, or in combination with features, characteristics, and / or elements described in conjunction with other embodiments, unless otherwise expressly indicated. Therefore, those skilled in the art will understand that various changes in form and detail may be made without departing from the scope of the invention as set forth in the appended claims.

Claims

1. A method for remote vehicle diagnostics, characterized in that, include: Configure a relational database for remote vehicle diagnostics, which includes at least basic vehicle data, component diagnostic specifications, diagnostic process scripts, and diagnostic strategies. In response to receiving an instruction to create diagnostic tasks for multiple target vehicles, a diagnostic task package is automatically generated for each target vehicle based on the association database. In response to receiving a diagnostic task package detection request sent after the vehicle starts, the corresponding diagnostic task package is sent to the vehicle terminal based on the vehicle identification number in the diagnostic task package detection request so that the vehicle terminal can execute the diagnostic process in the diagnostic task package.

2. The method according to claim 1, wherein, Configure basic vehicle data, including: Enter the brand, model, vehicle type, part number, and vehicle identification number; The association between the vehicle model and the part is established.

3. The method according to claim 1, wherein, Configure part diagnostic specifications and diagnostic process scripts, including: Import the component diagnostic specification file; The component diagnostic specification file is parsed into structured diagnostic data consisting of diagnostic data identifiers, diagnostic fault codes, diagnostic parameter configurations, and input / output control information. Configure the diagnostic workflow script corresponding to the structured diagnostic data.

4. The method according to claim 1, wherein, Configure diagnostic strategies, including: Scope of application; the scope of application is characterized by brand, vehicle series, or model. Configure policy types; the policy types include periodic diagnostics and single diagnostics; Configure trigger conditions; the trigger conditions include preconditions and execution conditions that need to be detected in real time during the diagnostic process.

5. The method according to claim 1, wherein, The automatic generation of diagnostic task packages for each target vehicle includes: Based on the received task mode, vehicle information is obtained; the task mode includes execution by vehicle series or model, execution by list, and execution by sales status. Based on the vehicle information, the corresponding diagnostic strategy, diagnostic process script and vehicle basic data are invoked to generate a diagnostic task package for each target vehicle. Once the operational reviewers approve the diagnostic task package, it will be released.

6. The method according to claim 1, wherein, The vehicle executes the diagnostic process in the diagnostic task package, including: The vehicle downloads and parses the diagnostic task package; If the current state of the vehicle meets the triggering conditions in the diagnostic strategy, the vehicle will execute the diagnostic strategy and diagnostic process script. The vehicle reports the diagnostic results.

7. The method according to claim 1, wherein, The method further includes: In response to receiving the diagnostic results reported by the vehicle, the diagnostic results are parsed and matched with the repair case library to generate repair suggestions.

8. A vehicle remote diagnostic system, characterized in that, Capable of implementing the vehicle remote diagnostic method as described in claim 1, comprising: The configuration module is used to configure the association database for remote vehicle diagnostics. The association database includes at least vehicle basic data, component diagnostic specifications, diagnostic process scripts, and diagnostic strategies. The task module is used to automatically generate a diagnostic task package for each target vehicle based on the association database when a command to create diagnostic tasks for multiple target vehicles is received. The diagnostic module is used to respond to a diagnostic task package detection request sent after the vehicle starts, and then send the corresponding diagnostic task package to the vehicle end based on the vehicle identification number in the diagnostic task package detection request so that the vehicle end can execute the diagnostic process in the diagnostic task package.

9. An electronic device, characterized in that, include: One or more processors; Memory, used to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1 to 7.

10. A computer-readable medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method as described in any one of claims 1 to 7.