Vehicle diagnosis method and device, vehicle and storage medium

Abstract

The application relates to the technical field of vehicle diagnosis, in particular to a vehicle diagnosis method and device, a vehicle and a storage medium, which comprises the following steps: entering a corresponding diagnosis permission mode according to a user permission authentication result, generating a diagnosis service diagnosis request, and sending the diagnosis service diagnosis request to a vehicle gateway; according to a preset routing rule, forwarding the diagnosis service diagnosis request to a target control unit; executing the diagnosis service diagnosis request through the target control unit, generating a diagnosis service diagnosis response, and returning the diagnosis service diagnosis response to a vehicle diagnosis unit; analyzing the diagnosis service diagnosis response through the vehicle diagnosis unit; and displaying the execution result of the diagnosis service diagnosis response. Thus, the safety problem that the traditional diagnosis instrument relies on external entity equipment, resulting in high cost, poor portability, unstable physical connection and easy leakage of diagnosis data through external lines is solved, and the whole vehicle diagnosis can be completed on the vehicle end without external equipment.

Description

Technical Field

[0001] This application relates to the field of vehicle diagnostic technology, and in particular to a vehicle diagnostic method, apparatus, vehicle, and storage medium. Background Technology

[0002] Traditional vehicle diagnostics typically rely on external physical devices (such as laptops, tablets, or dedicated diagnostic tools). These devices need to connect to the vehicle's OBD (On-Board Diagnostics) interface via physical transmission lines or wirelessly to establish diagnostic communication with the vehicle's electronic control unit. This approach requires users to drive the problematic vehicle to an after-sales service center to perform operations such as fault code reading, data calibration, and controller software upgrades. This not only increases the time and economic costs of diagnosis and repair but also significantly reduces the user experience.

[0003] Furthermore, when existing diagnostic instruments communicate with vehicles, diagnostic data is transmitted via external connection cables, posing a risk of data leakage and threatening vehicle data security, which urgently needs to be addressed. Summary of the Invention

[0004] This application provides a vehicle diagnostic method, device, vehicle, and storage medium to solve the problems of high cost, poor portability, unstable physical connection, and easy leakage of diagnostic data when transmitted through external lines caused by the reliance on external physical equipment of traditional diagnostic instruments. It enables the completion of full vehicle diagnostics on the vehicle terminal without the need for external equipment.

[0005] The first aspect of this application provides a vehicle diagnostic method applied to a vehicle system including a vehicle diagnostic unit, a vehicle gateway, and multiple control units. The method includes the following steps: The vehicle diagnostic unit is started and user authorization authentication is performed. Based on the authentication result, the corresponding diagnostic authorization mode is entered. A diagnostic service request is generated through the vehicle diagnostic unit and sent to the vehicle gateway. The diagnostic service request is forwarded to the target control unit via the vehicle gateway according to the preset routing rules. The target control unit then executes the diagnostic service request and generates a diagnostic service response. The diagnostic service response is transmitted back to the vehicle diagnostic unit via the vehicle gateway. The vehicle diagnostic unit then parses the diagnostic service response and displays the execution result of the diagnostic service response.

[0006] According to one embodiment of this application, the diagnostic permission mode includes a first permission mode and a second permission mode, wherein the level of the second permission mode is higher than the level of the first permission mode; In the first permission mode, the diagnostic operations that are allowed to be performed include at least one of reading vehicle version information and clearing fault codes; In the second permission mode, the diagnostic operations that can be performed include at least one of controller software upgrade, component calibration and learning, input / output control, and component replacement.

[0007] According to one embodiment of this application, the step of parsing the diagnostic service response through the vehicle diagnostic unit and displaying the execution result of the diagnostic service response includes: According to the preset diagnostic protocol parsing library, the diagnostic service diagnostic response is decoded to extract diagnostic result data; Based on a preset fault code database, the fault code information in the diagnostic result data is converted into readable fault description text; Based on the data type of the diagnostic results, a corresponding visualization component is selected for display. The visualization components include a text display component, a list display component, a chart display component, and a status indicator component. The execution result of the diagnostic service diagnostic response includes at least one of the following: indication information of operation success or failure, read vehicle parameter values, fault codes and their descriptions, version information comparison results, and upgrade progress information.

[0008] According to one embodiment of this application, after performing user authorization authentication, the method further includes: The vehicle diagnostic unit sends diagnostic session requests to each control unit on the vehicle bus. Receive the response message returned by each control unit, and determine the online status of each control unit based on the response message; Based on the online status of each control unit, a vehicle diagnostic topology diagram is constructed and displayed, wherein online control units are displayed with a first identifier, and offline control units are displayed with a second identifier.

[0009] According to one embodiment of this application, after parsing the diagnostic service response through the vehicle diagnostic unit and displaying the execution result of the diagnostic service response, the method further includes: Generate diagnostic operation records and diagnostic logs, and upload the diagnostic operation records and diagnostic logs to the diagnostic server; The diagnostic operation record includes at least one of the following: operation time, operator information, diagnostic service type, target control unit identifier, and operation execution result.

[0010] According to the vehicle diagnostic method provided in this application, the system enters the corresponding diagnostic permission mode based on the user authorization authentication result, generates a diagnostic service request, and sends the request to the vehicle gateway. Based on preset routing rules, the request is forwarded to the target control unit, which executes the request and generates a diagnostic service response, which is then sent back to the vehicle diagnostic unit. The vehicle diagnostic unit parses the response and displays its execution result. This solves the problems of high cost, poor portability, unstable physical connection, and data leakage associated with traditional diagnostic tools that rely on external physical devices. It enables full vehicle diagnostics to be completed on the vehicle's own system without the need for external equipment.

[0011] A second aspect of this application provides a vehicle diagnostic device applied to a vehicle system including a vehicle diagnostic unit, a vehicle gateway, and multiple control units. The device includes: The authentication module is used to start the vehicle diagnostic unit and perform user authorization authentication. Based on the authentication result, it enters the corresponding diagnostic authorization mode, generates a diagnostic service request through the vehicle diagnostic unit, and sends the diagnostic service request to the vehicle gateway. The generation module is used to forward the diagnostic service request to the target control unit through the vehicle gateway according to the preset routing rules, execute the diagnostic service request through the target control unit, and generate a diagnostic service response. The diagnostic module is used to transmit the diagnostic service response back to the vehicle diagnostic unit via the vehicle gateway, and the vehicle diagnostic unit parses the diagnostic service response and displays the execution result of the diagnostic service response.

[0012] According to one embodiment of this application, the diagnostic permission mode includes a first permission mode and a second permission mode, wherein the level of the second permission mode is higher than the level of the first permission mode; In the first permission mode, the diagnostic operations that are allowed to be performed include at least one of reading vehicle version information and clearing fault codes; In the second permission mode, the diagnostic operations that can be performed include at least one of controller software upgrade, component calibration and learning, input / output control, and component replacement.

[0013] According to one embodiment of this application, the diagnostic module is used for: According to the preset diagnostic protocol parsing library, the diagnostic service diagnostic response is decoded to extract diagnostic result data; Based on a preset fault code database, the fault code information in the diagnostic result data is converted into readable fault description text; Based on the data type of the diagnostic results, a corresponding visualization component is selected for display. The visualization components include a text display component, a list display component, a chart display component, and a status indicator component. The execution result of the diagnostic service diagnostic response includes at least one of the following: indication information of operation success or failure, read vehicle parameter values, fault codes and their descriptions, version information comparison results, and upgrade progress information.

[0014] According to one embodiment of this application, after the user authorization authentication is performed, the authentication module is further configured to: The vehicle diagnostic unit sends diagnostic session requests to each control unit on the vehicle bus. Receive the response message returned by each control unit, and determine the online status of each control unit based on the response message; Based on the online status of each control unit, a vehicle diagnostic topology diagram is constructed and displayed, wherein online control units are displayed with a first identifier, and offline control units are displayed with a second identifier.

[0015] According to one embodiment of this application, after parsing the diagnostic service response through the vehicle diagnostic unit and displaying the execution result of the diagnostic service response, the diagnostic module is further configured to: Generate diagnostic operation records and diagnostic logs, and upload the diagnostic operation records and diagnostic logs to the diagnostic server; The diagnostic operation record includes at least one of the following: operation time, operator information, diagnostic service type, target control unit identifier, and operation execution result.

[0016] According to the vehicle diagnostic device provided in this application embodiment, the device enters the corresponding diagnostic permission mode based on the user permission authentication result, generates a diagnostic service request, and sends the diagnostic service request to the vehicle gateway. Based on preset routing rules, the diagnostic service request is forwarded to the target control unit, which executes the diagnostic service request, generates a diagnostic service response, and sends it back to the vehicle diagnostic unit. The vehicle diagnostic unit parses the diagnostic service response and displays the execution result. This solves the problems of high cost, poor portability, unstable physical connection, and easy leakage of diagnostic data when transmitted through external lines, which are inherent problems with traditional diagnostic instruments that rely on external physical devices. It enables full vehicle diagnostics to be completed on the vehicle's own terminal without the need for external devices.

[0017] A third aspect of this application provides a vehicle, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the vehicle diagnostic method as described in the above embodiments.

[0018] A fourth aspect of this application provides a computer-readable storage medium storing computer instructions for causing the computer to perform the vehicle diagnostic method as described in the above embodiments.

[0019] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0020] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, wherein: Figure 1 This is a flowchart of a vehicle diagnostic method provided according to an embodiment of this application; Figure 2 This is a schematic diagram of a logic diagram of an in-vehicle diagnostic method based on UDS diagnostic services according to an embodiment of this application; Figure 3 This is a schematic diagram of the logic for reading controller fault codes using an in-vehicle diagnostic tool based on UDS diagnostic services according to an embodiment of this application. Figure 4 This is a block diagram of a vehicle diagnostic device according to an embodiment of this application; Figure 5 This is a structural schematic diagram of the vehicle provided in an embodiment of this application. Detailed Implementation

[0021] The embodiments of this application are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this application.

[0022] Those skilled in the art will understand that the current mainstream automotive diagnostic solutions are mainly divided into three categories: inexpensive OBD code readers used by car owners, portable diagnostic instruments used by repair shops, and highly specialized original factory diagnostic instruments used by 4S stores.

[0023] However, the aforementioned traditional diagnostic methods generally have the following drawbacks: First, the diagnostic and repair costs are high, requiring the purchase of hardware such as laptops, tablets, and connecting cables, as well as the installation of specialized software. Furthermore, the number of such devices is limited. If only the controller software needs upgrading, the vehicle owner must drive the vehicle to an after-sales service point, incurring additional time costs and impacting the user experience. Second, there are significant information security risks. Diagnostic data is transmitted via external connecting cables, posing a risk of leakage from the vehicle. Once leaked, vehicle data could be compromised, threatening both the OEM and the user. Third, existing diagnostic tools communicate with the vehicle via physical connecting cables. If the connection is lost, diagnostic communication may be interrupted. For routine diagnostics, reconnecting to the vehicle is sufficient, but this affects diagnostic efficiency. If a physical connection is interrupted during controller software upgrades, it may damage the controller. Finally, traditional diagnostic tools often require heavy equipment, making them inconvenient to carry and lacking portability.

[0024] To address the aforementioned problems, this invention proposes an in-vehicle diagnostic method based on UDS diagnostic services. By integrating diagnostic functions into the vehicle's infotainment system, diagnostic operations can be completed within the vehicle without the need to purchase external equipment, ensuring that diagnostic data does not leave the vehicle. Furthermore, by using the vehicle's infotainment system to communicate with each ECU via a gateway through an internal communication path, the risk of physical connection interruption is avoided, thereby significantly improving diagnostic efficiency, safety, and convenience.

[0025] Before introducing the vehicle diagnostic method of the embodiments of this application, let me first introduce the vehicle diagnostic system of this application.

[0026] The system includes a vehicle diagnostic unit, a vehicle gateway, and multiple control units, and needs to meet the following requirements: Vehicle-mounted chip: It adopts a high-performance automotive-grade SOC (System on Chip) chip, which is the most important part of the entire in-vehicle diagnostic instrument. It is mainly responsible for forwarding diagnostic commands, scheduling between various commands, and data processing.

[0027] Vehicle Gateway (GW): It needs to forward diagnostic commands sent from the vehicle's infotainment system to the corresponding controller. It generally needs to support four communication protocols: DOIP (Diagnostic over Internet Protocol), CANFD (CAN with Flexible Data-Rate), CAN (Controller Area Network), and LIN (Local Interconnect Network), so as to achieve communication with all diagnostic nodes in the vehicle.

[0028] Authorization Management and Authentication: Diagnostic operations can only be performed after authorization and authentication. The in-vehicle entertainment system and the vehicle control system are physically and electrically isolated and logically isolated, and are divided into low-level permissions and high-level permissions. Low-level permissions can be granted to users to perform some simple information reading, clearing fault codes, etc., while high-level permissions are only granted to internal R&D and after-sales personnel.

[0029] Vehicle in-vehicle diagnostic nodes: must support UDS related protocols: ISO 14229, ISO 15765, ISO 13400 (DOIP nodes must support).

[0030] Display and data storage: The large screen displays the UI interface of the in-vehicle diagnostic tool, and related diagnostic operations can be performed through touch, file transfer, etc. The data storage unit needs to pre-store the vehicle matching database, general fault code library, etc. For example, when a DTC (Diagnostic Trouble Code) is read, the meaning of the DTC needs to be displayed. In addition, the logs when executing diagnostic commands need to be stored and supported for export.

[0031] TBOX (Vehicle Wireless Communication): Requires support for connecting the in-vehicle diagnostic tool to the diagnostic server and diagnostic database, and support for downloading software packages from the diagnostic server.

[0032] This invention's in-vehicle diagnostic tool connects within the vehicle. Diagnostic commands are sent to a gateway via the vehicle's infotainment system, which then forwards them to the relevant ECUs. Under normal vehicle conditions, there is no communication interruption, significantly improving the efficiency and stability of vehicle diagnostics and greatly ensuring the security of vehicle diagnostic data. This diagnostic tool can be used for troubleshooting off-line electrical problems in automotive manufacturing plants and for after-sales service. By integrating diagnostic functions into the vehicle's infotainment system, it overcomes the drawback of traditional diagnostic tools that require a physical device for vehicle diagnosis.

[0033] The in-vehicle diagnostic method based on UDS diagnostic services of this invention aims to solve the problem that traditional diagnostic equipment relies on external devices to connect to the vehicle. It enables diagnostic communication with the vehicle solely through the in-vehicle infotainment system, ensuring that diagnostic data is not acquired by external devices, guaranteeing the security of vehicle diagnostic data, and achieving one-stop full-vehicle diagnostics at the in-vehicle infotainment system. It plays an important role in R&D, manufacturing, and after-sales service.

[0034] The following can be performed on the vehicle's infotainment system using the in-vehicle diagnostic system: (1) Reading and clearing fault codes: quickly locate vehicle problems through fault codes and improve the convenience of fault diagnosis; (2) Perform calibration and learning of some components without relying on production line electrical inspection or special calibration equipment; (3) Upgrades to the controller software are available in various ways; (4) When replacing after-sales parts, the one-click replacement process is executed through the in-vehicle diagnostic tool, and various operations required after the controller is replaced are automatically performed, such as key filling and configuration information writing. (5) I / O input / output control, which is performed by the in-vehicle diagnostic tool; (6) Simplify after-sales maintenance operations, save the cost of purchasing traditional diagnostic instruments, and significantly reduce the number of traditional diagnostic instruments; (7) Some basic information can be developed for users, and users can perform some basic diagnostics on the vehicle system, such as reading version information and clearing fault codes.

[0035] The vehicle diagnostic method, apparatus, vehicle, and storage medium of this application are described below with reference to the accompanying drawings.

[0036] Specifically, Figure 1 This is a schematic flowchart of a vehicle diagnostic method provided in an embodiment of this application.

[0037] like Figure 1 As shown, the vehicle diagnostic method includes the following steps: In step S101, the vehicle diagnostic unit is started and user authorization authentication is performed. Based on the authentication result, the corresponding diagnostic authorization mode is entered. The vehicle diagnostic unit generates a diagnostic service request and sends the diagnostic service request to the vehicle gateway.

[0038] In step S102, the diagnostic service request is forwarded to the target control unit through the vehicle gateway according to the preset routing rules. The target control unit executes the diagnostic service request and generates a diagnostic service response.

[0039] In step S103, the diagnostic service response is sent back to the vehicle diagnostic unit via the vehicle gateway. The vehicle diagnostic unit then parses the diagnostic service response and displays the execution result of the diagnostic service response.

[0040] Specifically, the process begins by accessing the in-vehicle diagnostic tool interface. The vehicle's infotainment system then starts the diagnostic tool and performs authorization management and authentication. Based on the verification results, it grants either low-level or high-level access. Low-level access only allows partial read functionality, while high-level access allows for all operations.

[0041] Furthermore, diagnostic command forwarding is performed: various diagnostic commands can be issued on the vehicle's infotainment system and passed to the gateway, which then forwards them to the corresponding controller according to the corresponding diagnostic ID.

[0042] Furthermore, the vehicle controller communication status is displayed: the in-vehicle diagnostic tool sends diagnostic session requests to all nodes on the vehicle bus, and controllers that respond are considered online and displayed on the large screen.

[0043] Further, fault code reading is performed: the in-vehicle diagnostic tool reads fault information from all controllers in the vehicle and displays it on a large screen. By clicking on a fault code, you can select to read the snapshot information and extended frame data of that fault code.

[0044] Finally, the controller version information is read and compared, and the software is upgraded: the in-vehicle diagnostic tool reads the version information of all controllers in the vehicle and compares it with the latest version information on the diagnostic server. If it is not the latest version information, it prompts for an upgrade. If the operator selects to upgrade, the in-vehicle diagnostic tool downloads the relevant software package from the diagnostic tool server and performs the upgrade action.

[0045] In addition, the in-vehicle diagnostic tool can also perform a series of operations such as key learning, tire pressure matching, and motion testing.

[0046] This invention offers three significant advantages over traditional diagnostic tools. First, it boasts higher integration, requiring no external devices and utilizing the vehicle's existing central control screen for a complete vehicle check. This not only completely replaces bulky external diagnostic tools but also saves on hardware costs associated with purchasing traditional tools, effectively reducing user maintenance expenses. Second, it offers enhanced security, as all diagnostic data flows within the vehicle, truly eliminating the need for data to leave the vehicle. Furthermore, by defining low-privilege and high-privilege operating modes, it ensures that low-privilege users cannot perform high-privilege operations, further guaranteeing the security of vehicle diagnostic data. Third, it provides a completely upgraded interactive experience. Traditional diagnostic tools can only be displayed and operated via a computer screen, while this invention supports voice interaction, making the diagnostic process more convenient and intelligent.

[0047] Furthermore, in some embodiments, the diagnostic permission mode includes a first permission mode and a second permission mode, wherein the level of the second permission mode is higher than that of the first permission mode; in the first permission mode, the diagnostic operations allowed to be performed include at least one of reading vehicle version information and clearing fault codes; in the second permission mode, the diagnostic operations allowed to be performed include at least one of controller software upgrade, component calibration and learning, input / output control, and component replacement.

[0048] Specifically, this invention divides diagnostic permissions into a first permission mode and a second permission mode, with the second permission mode having a higher level than the first permission mode. The first permission mode is a low-permission mode, primarily open to ordinary users. In this mode, the diagnostic operations allowed are limited to information reading functions, such as reading version information of various vehicle controllers and clearing fault codes—basic operations that do not involve modifying vehicle control parameters or performing complex diagnostic tasks. The second permission mode is a high-permission mode, authorized only to internal R&D personnel and after-sales service personnel. In this mode, more in-depth and critical diagnostic operations are allowed, including but not limited to controller software upgrades, component calibration and learning, input / output control (i.e., I / O control), and one-click replacement procedures after component replacement.

[0049] Furthermore, in some embodiments, the diagnostic service response is parsed by the vehicle diagnostic unit, and the execution result of the diagnostic service response is displayed. This includes: decoding the diagnostic service response according to a preset diagnostic protocol parsing library to extract diagnostic result data; converting the fault code information in the diagnostic result data into readable fault description text according to a preset fault code database; selecting corresponding visualization components for display according to the data type of the diagnostic result data, including text display components, list display components, chart display components, and status indicator components; the execution result of the diagnostic service response includes at least one of the following: operation success or failure indication information, read vehicle parameter values, fault codes and their description information, version information comparison results, and upgrade progress information.

[0050] Specifically, firstly, the received diagnostic service response is decoded using a pre-defined diagnostic protocol parsing library to extract structured diagnostic result data. Based on a pre-defined fault code database, the fault code information in the diagnostic result data is converted into user-readable fault description text, facilitating operator understanding of the fault meaning. Depending on the data type of the diagnostic result data, corresponding visualization components are selected for display. Text display components present textual information, list display components list multiple data items, chart display components plot curves or statistical graphs, and status indicator components visually display states such as on / off or normal / abnormal. The final displayed execution result includes at least one of the following: operation success or failure indication information, read vehicle parameter values, fault codes and their descriptions, version information comparison results, and upgrade progress information, thus presenting the diagnostic execution status to the user in a clear and intuitive manner.

[0051] Furthermore, in some embodiments, after user authorization authentication, the method further includes: sending a diagnostic session request to each control unit on the vehicle bus through the vehicle diagnostic unit; receiving a response message returned by each control unit and determining the online status of each control unit based on the response message; constructing and displaying a vehicle diagnostic topology diagram based on the online status of each control unit, wherein online control units are displayed with a first identifier and offline control units are displayed with a second identifier.

[0052] Specifically, after user authentication is completed, the in-vehicle diagnostic process automatically enters the vehicle diagnostic topology construction phase. Specifically, the vehicle diagnostic unit sends a diagnostic session request to each control unit on the vehicle bus to probe the communication status of each node. The vehicle diagnostic unit receives response messages from each control unit and determines the online status of each control unit based on whether a valid response is received. Based on this result, the vehicle diagnostic unit constructs and displays a diagnostic topology diagram of the entire vehicle. Online control units are displayed with a first identifier (e.g., highlighted green), indicating normal communication and diagnostic interaction, while offline control units are displayed with a second identifier (e.g., grayed out), indicating that the node is unresponsive or has communication abnormalities.

[0053] Furthermore, in some embodiments, after parsing the diagnostic service response through the vehicle diagnostic unit and displaying the execution result of the diagnostic service response, the method further includes: generating diagnostic operation records and diagnostic logs, and uploading the diagnostic operation records and diagnostic logs to the diagnostic server; wherein, the diagnostic operation records include at least one of operation time, operator information, diagnostic service type, target control unit identifier, and operation execution result.

[0054] After completing the diagnostic operation and displaying the diagnostic results, the vehicle diagnostic unit automatically generates corresponding diagnostic operation records and diagnostic logs. The diagnostic operation record includes at least one of the following: operation time, operator information, diagnostic service type, target control unit identifier, and operation execution result, to fully trace the subject, object, and result of each diagnostic action.

[0055] The diagnostic log records detailed raw message data, communication timing, and anomaly information during the diagnostic interaction process, providing data support for subsequent fault analysis and technical backtracking. Subsequently, the vehicle diagnostic unit uploads the above operation records and diagnostic logs to the diagnostic server via the vehicle's wireless communication module, greatly improving the efficiency of after-sales technical support and fault analysis.

[0056] The following is about Figure 2 and Figure 3 A detailed explanation will be provided.

[0057] like Figure 2As shown, the following are the specific implementation steps and methods of this in-vehicle diagnostic method based on UDS diagnostic services: (1) Functions that each part needs to implement: User / Operator: The person who uses the in-vehicle diagnostic tool, i.e., the person who inputs various diagnostic commands on the vehicle's infotainment system.

[0058] In-vehicle diagnostic tool (CDC): This is the large screen on the vehicle's infotainment system, responsible for displaying the diagnostic tool's UI interface. The operator directly enters diagnostic commands or clicks on relevant windows on the UI interface. The CDC transmits the diagnostic commands to the VDC / VIU0, receives the diagnostic response from the ECU, and displays the diagnostic results on the large screen.

[0059] VDC / VIU0: This is the vehicle gateway, a bridge for communication between the in-vehicle diagnostic tool and various ECUs in the vehicle. It is responsible for routing diagnostic messages, routing diagnostic requests to specific ECUs according to their diagnostic IDs, and routing diagnostic responses to the in-vehicle diagnostic tool.

[0060] In-vehicle ECU: This is the in-vehicle diagnostic node, responsible for executing relevant diagnostic commands. If it involves self-learning, calibration, or other operations, it may require driving actuators to perform the relevant operations.

[0061] TBOX: Responsible for connecting the vehicle to the diagnostic server. It needs to download data from the diagnostic server to the in-vehicle diagnostic tool, and some diagnostic execution results or logs need to be uploaded to the diagnostic server.

[0062] Diagnostic server: Responsible for storing software packages, diagnostic ODX files, etc. The diagnostic server may need to interface with the MES system to obtain vehicle-related diagnostic data, such as vehicle diagnostic topology.

[0063] (2) Specific implementation steps: Step 1: Activate the diagnostic module, verify user identity and enter permission authentication, and determine whether to enter high-privilege or low-privilege diagnostic mode. Step 2: The in-vehicle diagnostic tool automatically scans all the vehicle's ECUs, attempting to communicate with all diagnostic nodes. A common method is sending 0x1001. If a controller responds, it is considered online. The vehicle diagnostic topology is constructed based on the responses from all controllers. Online controllers are highlighted in green, while offline controllers are grayed out. The CDC requires at least two processing chips, each with a diagnostic module. The ECUs are interconnected via an internal CAN bus and a gateway. Step 3: Read fault codes and fault code snapshot data from each ECU in the vehicle. This requires data parsing from a cloud-based diagnostic server. After the in-vehicle diagnostic tool parses the fault codes, it displays the fault codes and their specific meanings on the vehicle's infotainment screen and generates a vehicle health report. Users can click on the fault codes to view relevant repair suggestions, or choose to view or export the vehicle health report. The advantage of this approach is that the diagnostic tool only needs to establish a connection with the vehicle controllers once to obtain fault information from all controllers in the vehicle, eliminating the need to read fault codes from individual controllers and improving diagnostic communication efficiency.

[0064] Step 4: Special Diagnostic Operations: 1) If an ECU in the vehicle is damaged and replaced, the in-vehicle diagnostic tool can perform all replacement operations for that ECU with a single click, such as writing the VIN code, self-learning, calibration, etc. If only self-learning or calibration fails, a specific step can be selected for operation, and the results will be displayed on the vehicle's infotainment screen. The advantage of this approach is that it integrates and encapsulates a series of diagnostic commands, allowing the operator to perform a series of diagnostic operations simply by clicking on a window. This improves the efficiency of after-sales operations.

[0065] Step 5: Cloud storage of diagnostic operation records and logs. After the vehicle completes the relevant diagnostic operations, the in-vehicle diagnostic instrument will upload the operation records and logs to the cloud. The advantages of doing this are: 1) Some diagnostic operations can be traced back to their source, preventing inconvenience for subsequent personnel to troubleshoot problems due to improper operation by the operator; 2) There is no need to export logs from the vehicle, and they can be viewed directly on the diagnostic server.

[0066] Furthermore, such as Figure 3 As shown, the user or operator first authenticates through the vehicle diagnostic tool (CDC). The system grants either high-level or low-level permissions based on the authentication result. After obtaining permissions, the CDC sends a diagnostic request (such as a request to read internal ECU fault codes at address 1902FF) to the vehicle gateway (VDC / VIU0). The gateway routes the diagnostic request to the corresponding in-vehicle ECU. After the ECU performs the diagnostic operation, it returns a diagnostic response (such as a response containing DTC fault codes at address 5902FF). The gateway then routes the diagnostic response back to the CDC, and finally, the CDC displays the diagnostic results on the screen to the user, thus completing a full in-vehicle diagnostic interaction process.

[0067] Therefore, the main technical innovations of this invention are reflected in the following aspects. First, it achieves native integration, completely eliminating external diagnostic equipment. The DOIP, CAN, and LIN communication units, diagnostic protocol stack, and security isolation unit are all natively integrated into the vehicle's mainboard, requiring no external traditional diagnostic tools. Second, it adopts a direct bus connection architecture, with the diagnostic module directly connected to the vehicle's DOIP network, resulting in more stable communication and a latency reduction of over 50%. Third, it offers higher security, with diagnostic data transmitted entirely within the vehicle, eliminating the risk of leakage. Furthermore, it enhances security by differentiating diagnostic permissions. In addition, this invention natively implements a series of advanced diagnostic functions, including motion testing (actively driving actuators such as oil pumps, fans, and solenoid valves, allowing for device quality assessment without vehicle disassembly), topology scanning (automatically generating ECU communication topology diagrams to quickly locate bus open or short circuits), coding and flashing (supporting ECU firmware upgrades, anti-theft matching, and enabling hidden functions), as well as new energy-specific functions (such as battery cell voltage and temperature monitoring, SOC / SOH assessment, insulation detection, and equalization control), comprehensively covering the diagnostic needs of both traditional and new vehicles.

[0068] According to the vehicle diagnostic method proposed in this application, the system enters the corresponding diagnostic permission mode based on the user authorization authentication result, generates a diagnostic service request, and sends the request to the vehicle gateway. Based on preset routing rules, the request is forwarded to the target control unit, which executes the request and generates a diagnostic service response, which is then sent back to the vehicle diagnostic unit. The vehicle diagnostic unit parses the response and displays its execution result. This solves the problems of high cost, poor portability, unstable physical connection, and data leakage associated with traditional diagnostic tools that rely on external physical devices. It enables full vehicle diagnostics to be completed on the vehicle's own system without the need for external equipment.

[0069] Next, the vehicle diagnostic device proposed according to an embodiment of this application is described with reference to the accompanying drawings.

[0070] Figure 4 This is a block diagram of a vehicle diagnostic device according to an embodiment of this application.

[0071] In this embodiment, the vehicle diagnostic device is applied to a vehicle system that includes a vehicle diagnostic unit, a vehicle gateway, and multiple control units.

[0072] like Figure 4 As shown, the vehicle diagnostic device 10 includes: an authentication module 100, a generation module 200, and a diagnostic module 300.

[0073] The system includes an authentication module 100, which initiates the vehicle diagnostic unit, performs user authentication, enters the corresponding diagnostic permission mode based on the authentication result, generates a diagnostic service request through the vehicle diagnostic unit, and sends the diagnostic service request to the vehicle gateway. The generation module 200 forwards the diagnostic service request to the target control unit through the vehicle gateway according to preset routing rules, executes the diagnostic service request through the target control unit, and generates a diagnostic service response. The diagnostic module 300 transmits the diagnostic service response back to the vehicle diagnostic unit through the vehicle gateway, parses the diagnostic service response, and displays the execution result of the diagnostic service response.

[0074] Furthermore, in some embodiments, the diagnostic permission mode includes a first permission mode and a second permission mode, wherein the level of the second permission mode is higher than that of the first permission mode; in the first permission mode, the diagnostic operations allowed to be performed include at least one of reading vehicle version information and clearing fault codes; in the second permission mode, the diagnostic operations allowed to be performed include at least one of controller software upgrade, component calibration and learning, input / output control, and component replacement.

[0075] Furthermore, in some embodiments, the diagnostic module 300 is configured to: decode the diagnostic service response according to a preset diagnostic protocol parsing library and extract diagnostic result data; convert the fault code information in the diagnostic result data into readable fault description text according to a preset fault code database; select corresponding visualization components for display according to the data type of the diagnostic result data, the visualization components including text display components, list display components, chart display components, and status indication components; the execution result of the diagnostic service response includes at least one of the following: operation success or failure indication information, read vehicle parameter values, fault codes and their description information, version information comparison results, and upgrade progress information.

[0076] Furthermore, in some embodiments, after user authorization authentication, the authentication module 100 is also used to: send a diagnostic session request to each control unit on the vehicle bus through the vehicle diagnostic unit; receive a response message returned by each control unit and determine the online status of each control unit based on the response message; and construct and display a vehicle diagnostic topology diagram based on the online status of each control unit, wherein online control units are displayed with a first identifier and offline control units are displayed with a second identifier.

[0077] Furthermore, in some embodiments, after parsing the diagnostic service response through the vehicle diagnostic unit and displaying the execution result of the diagnostic service response, the diagnostic module 300 is further configured to: generate diagnostic operation records and diagnostic logs, and upload the diagnostic operation records and diagnostic logs to the diagnostic server; wherein, the diagnostic operation records include at least one of operation time, operator information, diagnostic service type, target control unit identifier, and operation execution result.

[0078] It should be noted that the foregoing explanation of the vehicle diagnostic method embodiment also applies to the vehicle diagnostic device of this embodiment, and will not be repeated here.

[0079] The vehicle diagnostic device proposed in this application enters the corresponding diagnostic permission mode based on the user authorization authentication result, generates a diagnostic service request, and sends the diagnostic service request to the vehicle gateway. According to preset routing rules, the diagnostic service request is forwarded to the target control unit, which executes the diagnostic service request, generates a diagnostic service response, and sends it back to the vehicle diagnostic unit. The vehicle diagnostic unit parses the diagnostic service response and displays the execution result. This solves the problems of high cost, poor portability, unstable physical connection, and easy leakage of diagnostic data when transmitted through external lines, which are inherent problems with traditional diagnostic instruments that rely on external physical devices. It enables full vehicle diagnostics to be completed on the vehicle's own terminal without the need for external devices.

[0080] Figure 5 A schematic diagram of the structure of a vehicle provided in an embodiment of this application. The vehicle may include: The memory 501, the processor 502, and the computer program stored on the memory 501 and capable of running on the processor 502.

[0081] When the processor 502 executes the program, it implements the vehicle diagnostic method provided in the above embodiments.

[0082] Furthermore, the vehicle also includes: Communication interface 503 is used for communication between memory 501 and processor 502.

[0083] The memory 501 is used to store computer programs that can run on the processor 502.

[0084] Memory 501 may include high-speed RAM memory, and may also include non-volatile memory, such as at least one disk storage device.

[0085] If the memory 501, processor 502, and communication interface 503 are implemented independently, then the communication interface 503, memory 501, and processor 502 can be interconnected via a bus to complete communication between them. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 5 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0086] Optionally, in a specific implementation, if the memory 501, processor 502, and communication interface 503 are integrated on a single chip, then the memory 501, processor 502, and communication interface 503 can communicate with each other through an internal interface.

[0087] Processor 502 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application.

[0088] This application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the vehicle diagnostic method described above.

[0089] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0090] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "N" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0091] Any process or method description in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or more N executable instructions for implementing custom logic functions or processes, and the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved, as should be understood by those skilled in the art to which embodiments of this application pertain.

[0092] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-included system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of computer-readable media include: an electrical connection having one or more wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Alternatively, the computer-readable medium may be paper or other suitable media on which the program can be printed, since the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in a computer memory.

[0093] It should be understood that the various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, the N steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0094] Those skilled in the art will understand that all or part of the steps of the methods in the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, the program includes one or a combination of the steps of the method embodiments.

[0095] Furthermore, the functional units in the various embodiments of this application can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into a module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium.

[0096] The storage medium mentioned above can be a read-only memory, a disk, or an optical disk, etc. Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of this application.

Claims

1. A vehicle diagnosis method characterized by, Applied to a vehicle system including a vehicle diagnostic unit, a vehicle gateway, and multiple control units, the method includes the following steps: The vehicle diagnostic unit is started and user authorization authentication is performed. Based on the authentication result, the corresponding diagnostic authorization mode is entered. A diagnostic service request is generated through the vehicle diagnostic unit and sent to the vehicle gateway. The diagnostic service request is forwarded to the target control unit via the vehicle gateway according to the preset routing rules. The target control unit then executes the diagnostic service request and generates a diagnostic service response. The diagnostic service response is transmitted back to the vehicle diagnostic unit via the vehicle gateway. The vehicle diagnostic unit then parses the diagnostic service response and displays the execution result of the diagnostic service response.

2. The method according to claim 1, characterized in that, The diagnostic permission mode includes a first permission mode and a second permission mode, wherein the level of the second permission mode is higher than the level of the first permission mode; In the first permission mode, the diagnostic operations that are allowed to be performed include at least one of reading vehicle version information and clearing fault codes; In the second permission mode, the diagnostic operations that can be performed include at least one of controller software upgrade, component calibration and learning, input / output control, and component replacement.

3. The method according to claim 1, characterized in that, The step of parsing the diagnostic service response through the vehicle diagnostic unit and displaying the execution result of the diagnostic service response includes: According to the preset diagnostic protocol parsing library, the diagnostic service diagnostic response is decoded to extract diagnostic result data; Based on a preset fault code database, the fault code information in the diagnostic result data is converted into readable fault description text; Based on the data type of the diagnostic results, a corresponding visualization component is selected for display. The visualization components include a text display component, a list display component, a chart display component, and a status indicator component. The execution result of the diagnostic service diagnostic response includes at least one of the following: indication information of operation success or failure, read vehicle parameter values, fault codes and their descriptions, version information comparison results, and upgrade progress information.

4. The method according to claim 1, characterized in that, After performing user authorization authentication, the following is also included: The vehicle diagnostic unit sends diagnostic session requests to each control unit on the vehicle bus. Receive the response message returned by each control unit, and determine the online status of each control unit based on the response message; Based on the online status of each control unit, a vehicle diagnostic topology diagram is constructed and displayed, wherein online control units are displayed with a first identifier, and offline control units are displayed with a second identifier.

5. The method according to claim 1, characterized in that, After parsing the diagnostic service response through the vehicle diagnostic unit and displaying the execution result of the diagnostic service response, the method further includes: Generate diagnostic operation records and diagnostic logs, and upload the diagnostic operation records and diagnostic logs to the diagnostic server; The diagnostic operation record includes at least one of the following: operation time, operator information, diagnostic service type, target control unit identifier, and operation execution result.

6. A vehicle diagnostic device, characterized in that, The device, applicable to a vehicle system including a vehicle diagnostic unit, a vehicle gateway, and multiple control units, comprises: The authentication module is used to start the vehicle diagnostic unit and perform user authorization authentication. Based on the authentication result, it enters the corresponding diagnostic authorization mode, generates a diagnostic service request through the vehicle diagnostic unit, and sends the diagnostic service request to the vehicle gateway. The generation module is used to forward the diagnostic service request to the target control unit through the vehicle gateway according to the preset routing rules, execute the diagnostic service request through the target control unit, and generate a diagnostic service response. The diagnostic module is used to transmit the diagnostic service response back to the vehicle diagnostic unit via the vehicle gateway, and the vehicle diagnostic unit parses the diagnostic service response and displays the execution result of the diagnostic service response.

7. The apparatus according to claim 6, characterized in that, The diagnostic permission mode includes a first permission mode and a second permission mode, wherein the level of the second permission mode is higher than the level of the first permission mode; In the first permission mode, the diagnostic operations that are allowed to be performed include at least one of reading vehicle version information and clearing fault codes; In the second permission mode, the diagnostic operations that can be performed include at least one of controller software upgrade, component calibration and learning, input / output control, and component replacement.

8. The apparatus according to claim 6, characterized in that, The diagnostic module is used for: According to the preset diagnostic protocol parsing library, the diagnostic service diagnostic response is decoded to extract diagnostic result data; Based on a preset fault code database, the fault code information in the diagnostic result data is converted into readable fault description text; Based on the data type of the diagnostic results, a corresponding visualization component is selected for display. The visualization components include a text display component, a list display component, a chart display component, and a status indicator component. The execution result of the diagnostic service diagnostic response includes at least one of the following: indication information of operation success or failure, read vehicle parameter values, fault codes and their descriptions, version information comparison results, and upgrade progress information.

9. A vehicle, characterized in that, include: A memory, a processor, and a computer program stored in the memory and capable of running on the processor, the processor executing the computer program to implement the vehicle diagnostic method as described in any one of claims 1-5.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, The computer program is executed by a processor to implement the vehicle diagnostic method as described in any one of claims 1-5.

Images