ECU fault processing method and device based on domain control architecture, vehicle and medium

Abstract

The application provides an ECU fault processing method and device based on a domain control architecture, a vehicle and a medium, and belongs to the technical field of fault processing. The domain control architecture comprises at least one subnet ECU, at least one domain control ECU and a gateway ECU. The method comprises the following steps: when the subnet ECU detects a fault, the subnet ECU is controlled to generate a fault message and transmit the fault message to the domain control ECU; the domain control ECU is controlled to perform fault classification on the fault message based on a fault code classification principle, obtain multiple target messages with different fault levels, and transmit the target messages to the gateway ECU; the gateway ECU is controlled to transmit the target messages to an instrument or a central control screen of a commercial vehicle; and the instrument or the central control screen is controlled to display at least part of the target messages based on a preset display principle. The application purifies the fault display in the instrument or the central control screen, enables the user to make more accurate judgments and operations when a fault occurs, and improves the driving safety of the vehicle.

Description

Technical Field

[0001] This invention relates to the field of fault handling technology, and specifically to an ECU fault handling method, device, vehicle, and medium based on a domain control architecture. Background Technology

[0002] During the use of a car, it is inevitable that various car parts will malfunction or fail. When the vehicle's electronic control unit (ECU) detects a fault, it will usually send it to the vehicle network in the form of a fault code (DTC). The instrument panel or central control screen will collect the fault code in the vehicle network in real time, analyze the fault meaning according to the fault code definition, and display it on the main interface of the instrument panel or central control screen in real time to inform the user that the vehicle has malfunctioned and the ECU needs to stop the vehicle immediately or go to the repair shop as soon as possible.

[0003] Commercial vehicles are designed and technically designed for transporting people and goods. Compared to passenger vehicles, they operate in harsher environments and under more complex conditions, making them more prone to various component failures or malfunctions. If each electronic control unit in the vehicle detects a fault and immediately sends a fault code, broadcasting it on the instrument panel or central control screen to alert the user, it can often cause confusion or panic. Especially during driving, this can easily affect the user's normal driving and lead to serious traffic accidents.

[0004] Therefore, there is an urgent need to provide an ECU fault handling method, device, vehicle, and medium based on a domain control architecture to optimize the display of the instrument panel or central control screen, so as to avoid panic when users are informed of the fault and improve driving safety. Summary of the Invention

[0005] In view of this, it is necessary to provide an ECU fault handling method, device, vehicle and medium based on a domain control architecture to solve the technical problem that all fault codes in the prior art are displayed on the instrument panel or central control screen, causing user panic and resulting in unsafe driving.

[0006] On the one hand, to solve the above-mentioned technical problems, the present invention provides an ECU fault handling method based on a domain control architecture, wherein the domain control architecture includes at least one subnet ECU, at least one domain control ECU, and a gateway ECU, and the method includes:

[0007] When the subnet ECU detects a fault, it controls the subnet ECU to generate a fault message and transmits the fault message to the domain control ECU;

[0008] The domain control ECU classifies the fault messages based on the fault code classification principle, obtains multiple target messages with different fault levels, and transmits the target messages to the gateway ECU.

[0009] The gateway ECU is controlled to transmit the target message to the instrument panel or central control screen of the commercial vehicle;

[0010] The instrument or central control screen is controlled to display at least a portion of the target messages based on preset display principles.

[0011] In one possible implementation, the fault levels include Class A faults, Class B faults, Class C faults, and Class D faults, and the fault code classification principle is as follows:

[0012] When a fault involves safety, causes the vehicle to stop or fail to start, and requires proactive rescue and repair by a service station, the fault level is classified as Class A.

[0013] When a fault causes the vehicle to be limited in speed or torque or affects the vehicle's performance and normal operation, and the user must take the vehicle to a service station for repair, the fault level is classified as a Class B fault.

[0014] When a fault does not significantly affect vehicle performance or normal operation, and the user can repair it during routine vehicle maintenance, the fault level is classified as Class C.

[0015] When a fault is a derivative fault that only some users care about, and users can choose to repair it or not during routine vehicle maintenance, the fault level is classified as Class D fault.

[0016] In one possible implementation, the preset display principle is:

[0017] When the fault level is Class A or Class B, the indicator light on the instrument panel or central control screen will be illuminated, and a prompt text will be displayed. The prompt text is used to describe the fault parameters of the Class A or Class B fault and the guidance.

[0018] When the fault level is Class C or Class D, the instrument or central control screen will not display anything.

[0019] In one possible implementation, the communication protocol between the subnet ECU and the domain controller ECU is a standard protocol and a custom protocol, and the communication protocol between the domain controller ECU and the gateway ECU is a standard protocol. Then the method further includes:

[0020] When the subnet ECU detects a fault, it generates a standard fault message and a custom fault message based on the standard protocol and the custom protocol, and transmits the standard fault message and the custom fault message to the domain control ECU.

[0021] The domain control ECU is controlled to parse the standard fault message and the custom fault message to obtain fault parsing data;

[0022] The domain control ECU classifies the fault based on the fault analysis data, generates multiple target fault analysis data with different fault levels, encodes the multiple target fault analysis data based on the standard protocol, generates the target message, and transmits the target message to the gateway ECU.

[0023] In one possible implementation, the target message includes a diagnostic fault code, and the method further includes:

[0024] Store the diagnostic fault codes;

[0025] The system responds to the code display request, invokes the diagnostic fault code, and displays the diagnostic fault code on the instrument panel or central control screen.

[0026] In one possible implementation, the domain control architecture further includes a vehicle-to-everything (V2X) cloud platform, and the method further includes:

[0027] The target message is transmitted to the vehicle network cloud platform for storage.

[0028] In one possible implementation, the method further includes:

[0029] Different access permissions are assigned to the target messages stored in the vehicle network cloud platform;

[0030] Respond to the access request and verify the access permission. If the verification is successful, obtain the target message corresponding to the access permission.

[0031] On the other hand, the present invention also provides an ECU fault handling device based on a domain control architecture, wherein the domain control architecture includes at least one subnet ECU, at least one domain control ECU, and a gateway ECU, and the device includes:

[0032] The first network segment transmission unit is used to control the subnet ECU to generate a fault message and transmit the fault message to the domain control ECU when the subnet ECU detects a fault.

[0033] The second network segment transmission unit is used to control the domain control ECU to classify the fault message based on the fault code classification principle, obtain multiple target messages with different fault levels, and transmit the target messages to the gateway ECU.

[0034] The third network segment transmission unit is used to control the gateway ECU to transmit the target message to the instrument panel or central control screen of the commercial vehicle;

[0035] The display unit is used to control the instrument or central control screen to display at least a portion of the target messages based on preset display principles.

[0036] On the other hand, the present invention also provides a vehicle including a memory and a processor, wherein,

[0037] The memory is used to store programs;

[0038] The processor, coupled to the memory, is used to execute the program stored in the memory to implement the steps in the ECU fault handling method based on the domain control architecture described in any of the above possible implementations.

[0039] On the other hand, the present invention also provides a computer-readable storage medium storing a program or instructions that, when executed by a processor, implement the steps in the ECU fault handling method based on a domain control architecture as described in any of the above possible implementations.

[0040] The beneficial effects of this invention are as follows: The ECU fault handling method based on domain control architecture provided by this invention classifies the fault messages generated by at least one subnet ECU by setting the domain control ECU to obtain multiple target messages, and controls the instrument panel or central control screen to display at least some of the target messages based on preset display principles. This can purify the fault display on the instrument panel or central control screen, reduce user anxiety about faults, enable users to make more accurate judgments and operations when encountering vehicle faults, reduce the risk of vehicle safety accidents caused by untimely fault handling, and improve vehicle driving safety. Attached Figure Description

[0041] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0042] Figure 1 This is a network topology diagram of a domain controller architecture provided in an embodiment of the present invention;

[0043] Figure 2 A schematic flowchart of an ECU fault handling method based on a domain control architecture provided in an embodiment of the present invention;

[0044] Figure 3 This is a schematic diagram illustrating a process for integrating messages from standard protocols and custom protocols, provided as an embodiment of the present invention.

[0045] Figure 4 A flowchart illustrating the display of diagnostic fault codes provided in an embodiment of the present invention;

[0046] Figure 5 This is a schematic diagram of a process for accessing a target message in a vehicle network cloud platform, provided by an embodiment of the present invention.

[0047] Figure 6 A schematic diagram of an embodiment of the ECU fault handling device based on a domain control architecture provided by the present invention;

[0048] Figure 7 A schematic diagram of an embodiment of the vehicle provided by the present invention. Detailed Implementation

[0049] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present invention, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative effort are within the scope of protection of the present invention.

[0050] It should be understood that the illustrative drawings are not drawn to scale. The flowcharts used in this invention illustrate operations implemented according to some embodiments of the invention. It should be understood that the operations in the flowcharts may be implemented out of order, and steps without logical contextual relationships may be reversed or performed simultaneously. Furthermore, those skilled in the art, guided by the content of this invention, may add one or more other operations to the flowcharts, or remove one or more operations from the flowcharts. Some block diagrams shown in the drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor systems and / or microcontroller systems.

[0051] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of the invention. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a mutually exclusive, independent, or alternative embodiment. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0052] This invention provides an ECU fault handling method, device, vehicle, and medium based on a domain control architecture, which are described below.

[0053] Before demonstrating the implementation examples, let's first introduce the domain controller architecture, such as... Figure 1 As shown, the domain control architecture includes at least one subnet ECU, at least one domain control ECU, and a gateway ECU, with the domain control ECU serving as a forwarding station between the subnet ECU and the gateway ECU.

[0054] Specifically, such as Figure 1 As shown, the domain control ECU may include different types of domain control ECUs such as body domain control ECU and powertrain domain control ECU. Each domain control ECU is used to obtain fault messages from at least one subnet ECU. Subnet ECUs include, but are not limited to, transmission control unit (TCU), electric power steering unit (EPS), vehicle stability control unit (ESC), active suspension control unit (MRC), etc.

[0055] The subnet ECU, domain control ECU, gateway ECU, and instrument panel or central control screen are connected via a CAN bus.

[0056] Based on the above domain controller architecture, such as Figure 2 As shown, the ECU fault handling method based on the domain control architecture includes:

[0057] S201. When the subnet ECU detects a fault, it controls the subnet ECU to generate a fault message and transmits the fault message to the domain control ECU.

[0058] S202, The control domain ECU classifies the fault messages based on the fault code classification principle, obtains multiple target messages with different fault levels, and transmits the target messages to the gateway ECU.

[0059] S203, The control gateway ECU transmits the target message to the instrument panel or central control screen of the commercial vehicle;

[0060] S204. The control instrument or central control screen will display at least some of the target messages based on preset display principles.

[0061] Compared with existing technologies, the ECU fault handling method based on domain control architecture provided in this invention classifies fault messages generated by at least one subnet ECU into multiple target messages by setting the domain control ECU to classify the fault messages. The instrument panel or central control screen displays at least some of the target messages based on preset display principles. This can purify the fault display on the instrument panel or central control screen, reduce user anxiety about faults, enable users to make more accurate judgments and operations when encountering vehicle faults, reduce the risk of safety accidents caused by untimely fault handling, and improve vehicle driving safety.

[0062] In a specific embodiment of the present invention, the fault levels include Class A faults, Class B faults, Class C faults, and Class D faults, and the fault code classification principle is as follows:

[0063] When a fault involves safety, causes the vehicle to stop or fail to start, and requires proactive rescue and repair by a service station, the fault level is classified as Class A.

[0064] When a fault causes the vehicle to be limited in speed or torque or affects the vehicle's performance and normal operation, and the user must take the vehicle to a service station for repair, the fault level is classified as Class B.

[0065] When a fault does not significantly affect vehicle performance or normal operation, and the user can repair it during routine vehicle maintenance, the fault level is classified as Class C.

[0066] When a fault is a derivative fault that only some users care about, and users can choose to repair it or not during routine vehicle maintenance, the fault level is Class D.

[0067] In other words, Category A faults are serious faults, rendering the vehicle unable to operate normally and requiring proactive assistance from a service station. Category B faults are high-level faults; the vehicle can be driven, but its performance is reduced, and the user can take the vehicle to a service station for repairs. Category C faults are medium-level faults; the vehicle can operate normally, but should be repaired during routine maintenance. Category D faults are low-level faults, not affecting normal vehicle operation, and can be selectively repaired.

[0068] In a specific embodiment of the present invention, the preset display principle is as follows:

[0069] When the fault level is Class A or Class B, the indicator light on the instrument panel or central control screen will be illuminated, and a prompt text will be displayed. The prompt text describes the fault parameters of Class A or Class B fault and provides guidance.

[0070] When the fault level is Class C or Class D, the instrument panel or central control screen will not display anything.

[0071] In this embodiment of the invention, for Class A or Class B faults, the indicator lights on the instrument panel or central control screen are not only illuminated, but also prompt text is displayed to inform the user of the fault parameters and guidance. In other words, the fault indication of Class A or Class B faults is improved, eliminating the need for the user to make their own decisions on how to handle the fault, and ensuring the timeliness of the response to Class A or Class B faults.

[0072] Furthermore, this embodiment of the invention does not display Class C and Class D faults, further purifying the instrument panel or central control screen, thereby further avoiding user panic caused by Class C or Class D faults and further ensuring driving safety.

[0073] To further distinguish between Class A and Class B faults, in a specific embodiment of the present invention, a Class A fault requires the instrument panel or central control screen to illuminate a red STOP indicator light, while a Class B fault requires the instrument panel or central control screen to illuminate a yellow Warning indicator light or a system fault indicator light (red / yellow).

[0074] In a specific embodiment of the present invention, the fault parameters include the faulty system (ECU), the faulty subsystem (sensor / actuator), and the cause of the fault (e.g., abnormal pressure, abnormal power supply, etc.). The specific guidance is: Please call 400XX for assistance; please bring your device to the repair shop for maintenance as soon as possible.

[0075] To improve the communication efficiency of the domain control architecture, in some embodiments of the present invention, the communication protocols between the subnet ECU and the domain control ECU, as well as the communication protocols between the domain control ECU and the gateway ECU, are standard protocols.

[0076] By setting the communication protocols between the subnet ECU, domain control ECU, and gateway ECU to be consistent, the protocol conversion process can be eliminated, improving message transmission efficiency and thus improving fault response efficiency.

[0077] The standard protocol SAE J1939-73 defines Diagnostic Messages (DMs) and Diagnostic Trouble Codes (DTCs) for diagnostic services. The diagnostic messages include 19 types, from DM1 to DM19, providing various functions for vehicle diagnosis and repair. For example, DM1 transmits the current diagnostic fault code, DM2 transmits previous diagnostic fault codes, DM3 clears previous diagnostic fault codes, DM4 transmits parameters of the frame locked when a fault occurs, DM5 transmits information related to diagnostic readiness, DM6 transmits test results from the continuous monitoring system, DM7 requests testing of the non-continuous monitoring system, DM8 transmits test results from the non-continuous monitoring system, and DM9-DM19 transmit other functions, which will not be elaborated upon here.

[0078] Since commercial vehicles are more concerned with faults occurring in the current moment while in operation, the fault messages and target messages in this embodiment of the invention are all DM1 messages, excluding DM2-DM19 messages. This further simplifies the message information, thereby further reducing the risk of safety accidents caused by untimely fault handling and improving driving safety.

[0079] A diagnostic fault code consists of a Suspect Parameter Number (SPN), a Failure Mode Identifier (FMI), and an Occurrence Count (OC). A diagnostic fault code is composed of 4 bytes.

[0080] In a specific embodiment of the present invention, when the suspected parameter number is 91, it indicates that the suspected parameter is the accelerator pedal position; when the fault mode flag is 3, it indicates that the fault code is confirmed to be that the voltage is higher than the normal value; and when the number of fault occurrences is 5, it indicates that the fault has occurred 5 times.

[0081] However, as the number and types of subnet ECUs increase, standard protocols cannot meet the fault requirements of subnet ECUs. Therefore, in some embodiments of this invention, the communication protocol between the subnet ECU and the domain controller ECU is a standard protocol and a custom protocol, while the communication protocol between the domain controller ECU and the gateway ECU is a standard protocol. Figure 3 As shown, the ECU fault handling method based on the domain control architecture also includes:

[0082] S301. When the subnet ECU detects a fault, it generates a standard fault message and a custom fault message based on the standard protocol and the custom protocol, and transmits the standard fault message and the custom fault message to the domain control ECU.

[0083] S302, the control domain ECU parses standard fault messages and custom fault messages to obtain fault analysis data;

[0084] S303, the control domain ECU classifies the fault based on the fault analysis data, generates multiple target fault analysis data with different fault levels, encodes the multiple target fault analysis data based on the standard protocol, generates target messages, and transmits the target messages to the gateway ECU.

[0085] This invention improves the number of communication protocols between the subnet ECU and the domain control ECU by setting the communication protocol to include both standard and custom protocols. This ensures the comprehensiveness and accuracy of faults transmitted to the domain control ECU, thereby enhancing the driving safety of commercial vehicles.

[0086] Furthermore, by setting the communication protocol between the domain control ECU and the gateway ECU to only the standard protocol, the domain control ECU can integrate standard fault messages and custom fault messages, reduce the bus load rate of the main network segment where the gateway ECU is located, reduce the message processing work of the instrument panel or central control screen, and further avoid the impact of unnecessary messages on users, thereby further improving driving safety.

[0087] It should be understood that custom messages can be designed according to different commercial vehicle manufacturers.

[0088] In a specific embodiment of the present invention, the custom protocol is a protocol used to transmit status bits, such as status bits like switch sticking.

[0089] As described in the aforementioned standard protocol, the target message includes diagnostic fault codes. These codes are only understandable to professionals familiar with numerical standard protocols. To avoid unnecessary impact on users from these diagnostic fault codes, in some embodiments of this invention, such as... Figure 4 As shown, the ECU fault handling method based on the domain control architecture also includes:

[0090] S401. Store the diagnostic fault codes;

[0091] S402. Respond to the code display request, call the diagnostic fault code, and display the diagnostic fault code on the instrument panel or central control screen.

[0092] In this embodiment of the invention, only prompt text is displayed on the instrument panel or central control screen, without displaying specific diagnostic fault codes, further simplifying the fault display on the instrument panel or central control screen. Furthermore, when professionals need to analyze faults using diagnostic fault codes, they can initiate a code display request to display the diagnostic fault codes on the instrument panel or central control screen, facilitating fault analysis.

[0093] In certain practical applications, professionals need to remotely obtain diagnostic fault codes via a client. Therefore, in some embodiments of this invention, such as... Figure 1 As shown, the domain controller architecture also includes a T-box, so step S402 can be: responding to the code display request, calling the diagnostic fault code, and displaying the diagnostic fault code on the client through the T-box.

[0094] To facilitate subsequent fault tracing and analysis, in some embodiments of the present invention, such as Figure 1 As shown, the domain control architecture also includes a vehicle-to-everything (V2X) cloud platform. Therefore, the ECU fault handling methods based on the domain control architecture also include:

[0095] The target message is transmitted to the vehicle-to-everything (V2X) cloud platform for storage.

[0096] This invention stores the target message within the vehicle network platform, which can be retrieved for subsequent tracing or analysis, providing data support for subsequent fault handling or the rationality of fault handling.

[0097] Specifically, the target message is transmitted to the vehicle networking platform in the following way: the vehicle networking terminal (T-box) transmits the target message routed by the gateway ECU to the vehicle networking cloud platform at a certain sampling frequency.

[0098] Since the target message contains high-security data, to prevent data leakage, in some embodiments of the present invention, such as... Figure 5 As shown, the ECU fault handling method based on the domain control architecture also includes:

[0099] S501. Assign different access permissions to target messages stored in the vehicle network cloud platform;

[0100] S502. Respond to the access request and verify the access permission. If the verification is successful, obtain the target message corresponding to the access permission.

[0101] This invention improves the confidentiality and security of target messages by assigning different access permissions to target messages, ensuring that only those with the appropriate permissions can obtain them.

[0102] Specifically, the recipients of the target message include, but are not limited to: R&D personnel, after-sales service personnel, and users. R&D personnel have the highest access privileges.

[0103] To better implement the ECU fault handling method based on a domain control architecture in the embodiments of the present invention, the embodiments of the present invention also provide an ECU fault handling device based on a domain control architecture, such as... Figure 6 As shown, the ECU fault handling device 600 based on a domain control architecture includes:

[0104] The first network segment transmission unit 601 is used to control the subnet ECU to generate a fault message and transmit the fault message to the domain control ECU when the subnet ECU detects a fault.

[0105] The second network segment transmission unit 602 is used to control the domain control ECU to classify fault messages based on the fault code classification principle, obtain multiple target messages with different fault levels, and transmit the target messages to the gateway ECU.

[0106] The third network segment transmission unit 603 is used to control the gateway ECU to transmit the target message to the instrument panel or central control screen of the commercial vehicle;

[0107] Display unit 604 is used to control the instrument or central control screen to display at least part of the target message based on preset display principles.

[0108] The ECU fault handling device 600 based on the domain control architecture provided in the above embodiments can realize the technical solutions described in the above embodiments of the ECU fault handling method based on the domain control architecture. The specific implementation principles of each module or unit can be found in the corresponding content in the above embodiments of the ECU fault handling method based on the domain control architecture, and will not be repeated here.

[0109] like Figure 7 As shown, the present invention also provides a vehicle 700. The vehicle 700 includes a processor 701, a memory 702, and a display 703. Figure 7 Only some components of vehicle 700 are shown, but it should be understood that it is not required to implement all of the components shown, and more or fewer components may be implemented instead.

[0110] In some embodiments, processor 701 may be a central processing unit (CPU), a microprocessor, or other data processing chip, used to run program code stored in memory 702 or process data, such as the ECU fault handling method based on domain control architecture in this invention.

[0111] In some embodiments of the present invention, processor 701 may be a single server or a group of servers. The server group may be centralized or distributed. In some embodiments, processor 701 may be local or remote. In some embodiments, processor 701 may be implemented on a cloud platform. In one embodiment, the cloud platform may include a private cloud, public cloud, hybrid cloud, community cloud, distributed cloud, internal cloud, multi-cloud, etc., or any combination thereof.

[0112] In some embodiments, memory 702 may be an internal storage unit of vehicle 700, such as hard disk or memory of vehicle 700.

[0113] Furthermore, the memory 702 may include both internal storage units of the vehicle 700 and external storage devices. The memory 702 is used to store application software and various types of data installed on the vehicle 700.

[0114] In some embodiments, display 703 may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, or an OLED (Organic Light-Emitting Diode) touchscreen. Display 703 is used to display information about vehicle 700 and to display a visual user interface. Components 701-703 of vehicle 700 communicate with each other via a system bus.

[0115] In some embodiments of the present invention, when the processor 701 executes the ECU fault handling program based on the domain control architecture in the memory 702, the following steps can be implemented:

[0116] When the subnet ECU detects a fault, it controls the subnet ECU to generate a fault message and transmits the fault message to the domain control ECU.

[0117] The control domain ECU classifies fault messages based on the fault code classification principle, obtains multiple target messages with different fault levels, and transmits the target messages to the gateway ECU.

[0118] The control gateway ECU transmits the target message to the commercial vehicle's instrument panel or central control screen;

[0119] The control instrument or central control screen will display at least some of the target messages based on preset display principles.

[0120] It should be understood that when the processor 701 executes the ECU fault handling program based on the domain control architecture in the memory 702, in addition to the functions mentioned above, it can also perform other functions, as can be found in the description of the corresponding method embodiments above.

[0121] It should be noted that the vehicle can be a hybrid vehicle or a non-hybrid vehicle, namely a pure electric vehicle or a fuel vehicle.

[0122] Accordingly, embodiments of the present invention also provide a computer-readable storage medium for storing computer-readable programs or instructions. When the programs or instructions are executed by a processor, they can implement the steps or functions in the ECU fault handling method based on the domain control architecture provided in the above-described method embodiments.

[0123] It should be noted that the computer-readable medium shown in the embodiments of the present invention may be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. For example, a computer-readable storage medium may be an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, optical fiber, portable compact disc read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof.

[0124] Those skilled in the art will understand that all or part of the processes of the methods described in the above embodiments can be implemented by a computer program instructing related hardware (such as a processor, controller, etc.), and the computer program can be stored in a computer-readable storage medium. The computer-readable storage medium may be a disk, optical disk, read-only memory, or random access memory, etc.

[0125] The foregoing has provided a detailed description of the ECU fault handling method, device, vehicle, and medium based on a domain control architecture provided by the present invention. Specific examples have been used to illustrate the principles and implementation methods of the present invention. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of the present invention. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of the present invention. Therefore, the content of this specification should not be construed as a limitation of the present invention.

Claims

1. An ECU fault handling method based on a domain control architecture, characterized in that, The domain control architecture includes at least one subnet ECU, at least one domain control ECU, and a gateway ECU; the method includes: When the subnet ECU detects a fault, it controls the subnet ECU to generate a fault message and transmits the fault message to the domain control ECU; The domain control ECU classifies the fault messages based on the fault code classification principle, obtains multiple target messages with different fault levels, and transmits the target messages to the gateway ECU. The gateway ECU is controlled to transmit the target message to the instrument panel or central control screen of the commercial vehicle; The instrument or central control screen is controlled to display at least a portion of the target messages based on preset display principles; The communication protocol between the subnet ECU and the domain controller ECU is a standard protocol and a custom protocol, and the communication protocol between the domain controller ECU and the gateway ECU is a standard protocol.

2. The ECU fault handling method based on domain control architecture according to claim 1, characterized in that, The fault levels include Class A, Class B, Class C, and Class D faults, and the fault code classification principle is as follows: When a fault involves safety, causes the vehicle to stop or fail to start, and requires proactive rescue and repair by a service station, the fault level is classified as Class A. When a fault causes the vehicle to be limited in speed or torque or affects the vehicle's performance and normal operation, and the user must take the vehicle to a service station for repair, the fault level is classified as a Class B fault. When a fault does not significantly affect vehicle performance or normal operation, and the user can repair it during routine vehicle maintenance, the fault level is classified as Class C. When a fault is a derivative fault that only some users care about, and users can choose to repair it or not during routine vehicle maintenance, the fault level is classified as Class D fault.

3. The ECU fault handling method based on domain control architecture according to claim 2, characterized in that, The preset display principle is as follows: When the fault level is Class A or Class B, the indicator light on the instrument panel or central control screen will be illuminated, and a prompt text will be displayed. The prompt text is used to describe the fault parameters of the Class A or Class B fault and the guidance. When the fault level is Class C or Class D, the instrument or central control screen will not display anything.

4. The ECU fault handling method based on domain control architecture according to claim 1, characterized in that, The method further includes: When the subnet ECU detects a fault, it generates a standard fault message and a custom fault message based on the standard protocol and the custom protocol, and transmits the standard fault message and the custom fault message to the domain control ECU. The domain control ECU is controlled to parse the standard fault message and the custom fault message to obtain fault parsing data; The domain control ECU classifies the fault based on the fault analysis data, generates multiple target fault analysis data with different fault levels, encodes the multiple target fault analysis data based on the standard protocol, generates the target message, and transmits the target message to the gateway ECU.

5. The ECU fault handling method based on domain control architecture according to claim 4, characterized in that, The target message includes diagnostic fault codes, and the method further includes: Store the diagnostic fault codes; The system responds to the code display request, invokes the diagnostic fault code, and displays the diagnostic fault code on the instrument panel or central control screen.

6. The ECU fault handling method based on domain control architecture according to claim 1, characterized in that, The domain control architecture also includes a vehicle-to-everything (V2X) cloud platform, and the method further includes: The target message is transmitted to the vehicle network cloud platform for storage.

7. The ECU fault handling method based on domain control architecture according to claim 6, characterized in that, The method further includes: Different access permissions are assigned to the target messages stored in the vehicle network cloud platform; Respond to the access request and verify the access permission. If the verification is successful, obtain the target message corresponding to the access permission.

8. An ECU fault handling device based on a domain control architecture, characterized in that, The domain control architecture includes at least one subnet ECU, at least one domain control ECU, and a gateway ECU. The device includes: The first network segment transmission unit is used to control the subnet ECU to generate a fault message and transmit the fault message to the domain control ECU when the subnet ECU detects a fault. The second network segment transmission unit is used to control the domain control ECU to classify the fault message according to the fault code classification principle, obtain multiple target messages with different fault levels, and transmit the target messages to the gateway ECU. The third network segment transmission unit is used to control the gateway ECU to transmit the target message to the instrument panel or central control screen of the commercial vehicle; The display unit is used to control the instrument or central control screen to display at least a portion of the target messages based on preset display principles; The communication protocol between the subnet ECU and the domain controller ECU is a standard protocol and a custom protocol, and the communication protocol between the domain controller ECU and the gateway ECU is a standard protocol.

9. A vehicle, characterized in that, Including memory and processor, among which, The memory is used to store programs; The processor, coupled to the memory, is used to execute the program stored in the memory to implement the steps in the ECU fault handling method based on the domain control architecture as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a program or instructions that, when executed by a processor, implement the steps in the ECU fault handling method based on a domain control architecture as described in any one of claims 1 to 7.

Images