A vehicle-mounted component diagnosis and flashing management method and system

Abstract

The application relates to a vehicle-mounted part diagnosis and flashing management method and system, which comprises the following steps of: storing flashing configuration information in a cloud server; requesting the flashing configuration information from the cloud server and saving the information after the vehicle-mounted T-BOX is powered on for the first time, simultaneously performing part diagnosis and reporting; when the flashing configuration information stored in the cloud server is changed, the vehicle-mounted T-BOX acquires the latest flashing configuration information from the cloud server; when the cloud server receives an upgrading requirement of a part, the cloud server issues a part upgrading flashing task to the vehicle-mounted T-BOX; the vehicle-mounted T-BOX analyzes the part identification code contained in the task, looks for corresponding flashing configuration, and then calls a flashing business module corresponding to the part type to perform a flashing operation on the corresponding part. The application realizes intelligent management, fault diagnosis and software flashing of vehicle parts.

Description

Technical Field

[0001] This invention relates to the field of vehicle management, and in particular to a method and system for diagnosing and managing vehicle components. Background Technology

[0002] With the rapid development of intelligent connected vehicles (hereinafter referred to as "intelligent vehicles"), remote management, fault diagnosis, and software flashing of vehicle components have become key requirements in intelligent vehicle technology. However, existing technologies lack a unified standardized processing mechanism for vehicle component configuration information management, diagnostic request and response processing, and flashing process management, resulting in cumbersome operations, low efficiency, and poor compatibility. Furthermore, existing systems often fail to obtain the latest configuration information in a timely manner when components are replaced or diagnostic information changes, thus affecting diagnostic accuracy and the success rate of flashing tasks. Therefore, there is an urgent need for a system and method that can dynamically manage component configuration information and support remote diagnostics and software updates. Summary of the Invention

[0003] To address the aforementioned issues, this invention proposes a method and system for diagnosing and managing vehicle components.

[0004] The specific plan is as follows:

[0005] A method for diagnosing and flashing vehicle components includes the following steps:

[0006] The flashing configuration information for all vehicle components is stored on a cloud server;

[0007] After the vehicle T-BOX is powered on for the first time, it requests the flashing configuration information of all the corresponding components of the vehicle from the cloud server;

[0008] After receiving the flashing configuration information, the vehicle-mounted T-BOX saves it, performs diagnostics on the corresponding components, and reports the diagnostic information to the cloud server for storage.

[0009] When the flashing configuration information stored on the cloud server changes, the vehicle T-BOX retrieves the latest flashing configuration information from the cloud server and updates the flashing configuration information stored locally.

[0010] When the cloud server receives an upgrade request for a component, it sends a component upgrade and flashing task to the vehicle T-BOX. This component upgrade and flashing task contains the component identification code of the component to be flashed.

[0011] When the vehicle T-BOX receives a component upgrade and flashing task, it parses the component identification code contained therein and looks up the corresponding flashing configuration from the flashing configuration information stored locally.

[0012] The vehicle-mounted T-BOX retrieves the flashing configuration and, by parsing the component identification code, calls the corresponding flashing business module for that component type to perform the flashing operation for that component.

[0013] Furthermore, the configuration information to be flashed includes: component identification code, diagnostic request ID, diagnostic response ID, diagnostic function ID, and the DID type and DID value of component feature information.

[0014] Furthermore, the component identification code includes the vehicle manufacturer code, powertrain type code, component manufacturer code, component type code, generation time, random number, and check digit.

[0015] Furthermore, the flashing configuration information stored in the cloud server is uploaded to the cloud server via the client.

[0016] Furthermore, after the vehicle-mounted T-BOX is powered on for the first time, it first connects to the cloud server via wireless communication, and then sends a request to the cloud server.

[0017] Furthermore, the in-vehicle T-BOX uses the UDS protocol when diagnosing components.

[0018] Furthermore, the diagnostic information includes: hardware version number, software version number, and vendor code.

[0019] Furthermore, the vehicle-mounted T-BOX obtains the latest flashing configuration information from the cloud server by periodically requesting the latest flashing configuration information from the cloud server.

[0020] Furthermore, the vehicle-mounted T-BOX obtains the latest flashing configuration information from the cloud server in the following way: the cloud server actively sends the latest flashing configuration information to the vehicle-mounted T-BOX when the flashing configuration information changes.

[0021] A vehicle component diagnostic and flashing management system includes a cloud server and a vehicle-mounted T-BOX, the system implementing the steps of the method described in the embodiments of the present invention.

[0022] The present invention adopts the above technical solution, which realizes intelligent management, fault diagnosis and software flashing of vehicle parts by dynamically managing the flashing configuration information of parts and combining remote diagnosis and flashing functions. Attached Figure Description

[0023] Figure 1 The diagram shown is a flowchart of a method according to an embodiment of the present invention. Detailed Implementation

[0024] To further illustrate the various embodiments, the present invention provides accompanying drawings. These drawings are part of the disclosure of the present invention, primarily used to illustrate the embodiments, and can be used in conjunction with the relevant descriptions in the specification to explain the operating principles of the embodiments. With reference to these drawings, those skilled in the art should be able to understand other possible implementations and the advantages of the present invention.

[0025] The present invention will now be further described in conjunction with the accompanying drawings and specific embodiments.

[0026] Example 1:

[0027] This invention provides a method for diagnosing and flashing vehicle components, as described in the following embodiments. Figure 1 As shown, the method includes the following steps:

[0028] S1: Store the flashing configuration information of all vehicle components in the cloud server.

[0029] Before executing S1, the user needs to first upload the flashing configuration information of all the corresponding parts of the vehicle to the cloud server through the client (such as a PC). The cloud server saves the uploaded data after receiving it.

[0030] In this embodiment, the configuration information to be flashed includes: component identification code, diagnostic request ID, diagnostic response ID, diagnostic function ID, DID type and DID value of component feature information, etc. Among them, the diagnostic request ID, diagnostic response ID and diagnostic function ID are used during flashing, and the DID (Data Identifier) ​​type and DID value of component feature information are used during diagnosis to obtain the corresponding diagnostic information.

[0031] The component identification code serves as a unique identifier for each part; every component in a vehicle has a unique identification code. In this embodiment, the component identification code includes: vehicle manufacturer code, powertrain type code, component manufacturer code, component type code, generation time, random number, and check digit, to ensure the uniqueness and traceability of the component. The identification code is 23 bits long, and its specific structure is as follows:

[0032] The first two digits represent the vehicle manufacturer's code;

[0033] The third position represents the power type (such as gasoline, diesel, electric, etc.);

[0034] The 4th and 5th digits represent the component manufacturer's code;

[0035] The 6th and 7th digits represent the component type code (such as engine, DMS (Driver Monitoring System), VCU (Vehicle Control Unit), etc.).

[0036] 8th-21st digits: represent the component creation time (format: yyyyMMddHHmmss);

[0037] 22nd digit: Random number (value range: 0-9);

[0038] 23rd bit: Check bit, used to verify the correctness of the first 22 bits.

[0039] The component identification code is designed to be both concise and contain sufficient discriminative information, enabling the in-vehicle T-BOX (Telematics Box) to quickly and accurately identify target components, while also possessing high scalability and compatibility. Furthermore, when an upgrade task is issued to the T-BOX, the T-BOX, during the flashing process, reports upgrade progress information, including the upgrade progress and the component's upgrade status (success / failure), to the cloud server. This reported upgrade progress information includes the component identification code. The cloud server can use this component identification code to locate the corresponding component and update its current upgrade progress status. Because there may be situations where an upgrade task is issued, but this task requires upgrading multiple components simultaneously, without this component identification code, the cloud server would be unable to distinguish which specific component's upgrade progress status the T-BOX is reporting.

[0040] S2: After the vehicle T-BOX is powered on for the first time, it requests the flashing configuration information of all the corresponding components of the vehicle from the cloud server.

[0041] In this embodiment, after the vehicle-mounted T-BOX is powered on for the first time, it first connects to the cloud server via wireless communication, and then sends a request to the cloud server to obtain the flashing configuration information of all the components corresponding to the vehicle.

[0042] S3: After receiving the flashing configuration information, the vehicle-mounted T-BOX saves it, performs diagnostics on the corresponding components, and reports the diagnostic information to the cloud server for storage.

[0043] This embodiment uses the Unified Diagnostic Service (UDS) protocol for diagnosis to read component characteristic information, such as hardware version number, software version number, and component supplier code. After diagnosis, the diagnostic information is reported to a cloud server for storage via wireless communication, so that users can view and analyze it later after logging in.

[0044] S4: When the flashing configuration information stored on the cloud server changes, the vehicle T-BOX obtains the latest flashing configuration information from the cloud server and updates the flashing configuration information stored locally.

[0045] The flashing configuration information stored on the cloud server changes when a user logs into the cloud server through a client and modifies the flashing configuration information stored therein.

[0046] There are two ways for the vehicle-mounted T-BOX to obtain the latest flashing configuration information from the cloud server: one is that the vehicle-mounted T-BOX periodically requests the latest flashing configuration information from the cloud server; the other is that the cloud server proactively sends the latest flashing configuration information to the vehicle-mounted T-BOX when the flashing configuration information changes. Those skilled in the art can choose the appropriate method according to their needs, and no restrictions are imposed here.

[0047] Step S4 ensures that the vehicle-mounted T-BOX always uses the latest flashing configuration information for diagnostics and flashing operations.

[0048] S5: When the cloud server receives an upgrade request for a component, it sends a component upgrade and flashing task to the vehicle T-BOX. This component upgrade and flashing task contains the component identification code of the component to be flashed.

[0049] The upgrade requests for components received by the cloud server are sent to the cloud server by the user through the client.

[0050] S6: When the vehicle T-BOX receives a component upgrade flashing task, it parses the component identification code contained therein and looks up the corresponding flashing configuration from the locally stored flashing configuration information.

[0051] S7: The vehicle-mounted T-BOX uses the found flashing configuration and the parsing of the component identification code to call the flashing business module corresponding to the component type to perform the flashing operation of the corresponding component.

[0052] Since different component types require different communication methods and flashing procedures for flashing operations, this embodiment stores the flashing service modules corresponding to each component type in the vehicle-mounted T-BOX. These modules include the communication methods and flashing procedures for each component type. This ensures that compatibility issues caused by inconsistent business process specifications between different components are properly handled, thereby ensuring the accuracy and success rate of the flashing process. The flashing service module can be an embedded software program mounted on the T-BOX. This program contains methods for flashing each component. The vehicle terminal parses the component identification code to determine the target component to be flashed and calls the corresponding flashing implementation function or program file (each component's flashing implementation can be encapsulated as a function or a C language dynamic library file).

[0053] This embodiment has the following beneficial effects:

[0054] (1) Unified management: Standardized component identification codes can uniquely identify each component in the vehicle and contain rich information such as vehicle manufacturer code, power type, component manufacturer, type, etc., providing a foundation for remote management, fault diagnosis and software flashing of components, as well as the uniqueness and traceability of components.

[0055] (2) Efficient component identification and positioning: Through concise component identification codes with rich identification information, the vehicle-mounted T-BOX can efficiently identify and locate target components, ensuring that diagnostic tasks can be completed accurately and quickly.

[0056] (3) Real-time cloud configuration information update: By distributing and dynamically updating the configuration information of components through the cloud, the vehicle T-BOX can still obtain and execute the corresponding diagnostic and flashing tasks normally after the components are replaced or upgraded, avoiding failures caused by information lag.

[0057] (4) Compatibility and scalability: The design of the component identification code and the configuration information to be flashed not only meets the current vehicle diagnostic and flashing needs, but also has good compatibility and scalability, and can adapt to the future development of intelligent connected vehicle technology.

[0058] (5) Intelligent and automated management: By combining remote diagnostics and flashing functions, intelligent and automated vehicle management is realized, which greatly improves the efficiency of fault diagnosis and reduces the need for manual intervention.

[0059] Example 2:

[0060] The present invention also provides an on-board component diagnostic and flashing management system, including a cloud server and an on-board T-BOX, wherein the system implements the steps in the above-described method embodiments of Embodiment 1 of the present invention.

[0061] Although the invention has been specifically shown and described in conjunction with preferred embodiments, those skilled in the art should understand that various changes in form and detail may be made to the invention without departing from the spirit and scope of the invention as defined in the appended claims, all of which shall be within the scope of protection of the invention.

Claims

1. A method for diagnosing and managing vehicle-mounted components, characterized in that, Includes the following steps: The flashing configuration information for all vehicle components is stored on a cloud server; After the vehicle T-BOX is powered on for the first time, it requests the flashing configuration information of all the corresponding components of the vehicle from the cloud server; After receiving the flashing configuration information, the vehicle-mounted T-BOX saves it, performs diagnostics on the corresponding components, and reports the diagnostic information to the cloud server for storage. When the flashing configuration information stored on the cloud server changes, the vehicle T-BOX retrieves the latest flashing configuration information from the cloud server and updates the flashing configuration information stored locally. When the cloud server receives an upgrade request for a component, it sends a component upgrade and flashing task to the vehicle T-BOX. This component upgrade and flashing task contains the component identification code of the component to be flashed. When the vehicle T-BOX receives a component upgrade and flashing task, it parses the component identification code contained therein and looks up the corresponding flashing configuration from the flashing configuration information stored locally. The vehicle-mounted T-BOX retrieves the flashing configuration and, by parsing the component identification code, calls the corresponding flashing business module for that component type to perform the flashing operation for that component.

2. The method for diagnosing and flashing vehicle components according to claim 1, characterized in that: The configuration information to be flashed includes: component identification code, diagnostic request ID, diagnostic response ID, diagnostic function ID, and the DID type and DID value of component feature information.

3. The method for diagnosing and flashing vehicle components according to claim 1, characterized in that: The component identification code includes the vehicle manufacturer code, powertrain type code, component manufacturer code, component type code, generation time, random number, and check digit.

4. The method for diagnosing and flashing vehicle components according to claim 1, characterized in that: The flashing configuration information stored in the cloud server is uploaded to the cloud server through the client.

5. The method for diagnosing and flashing vehicle components according to claim 1, characterized in that: After the vehicle-mounted T-BOX is powered on for the first time, it first connects to the cloud server via wireless communication, and then sends a request to the cloud server.

6. The method for diagnosing and flashing vehicle components according to claim 1, characterized in that: The vehicle-mounted T-BOX uses the UDS protocol to diagnose components.

7. The method for diagnosing and flashing vehicle components according to claim 1, characterized in that: The diagnostic information includes: hardware version number, software version number, and vendor code.

8. The method for diagnosing and flashing vehicle components according to claim 1, characterized in that: The vehicle-mounted T-BOX obtains the latest flashing configuration information from the cloud server by periodically requesting the latest flashing configuration information from the cloud server.

9. The method for diagnosing and flashing vehicle components according to claim 1, characterized in that: The vehicle-mounted T-BOX obtains the latest flashing configuration information from the cloud server in the following way: the cloud server actively sends the latest flashing configuration information to the vehicle-mounted T-BOX when the flashing configuration information changes.

10. A vehicle component diagnostic and flashing management system, characterized in that: The system includes a cloud server and an in-vehicle T-BOX, and implements the steps of the method as described in any one of claims 1 to 9.

Images