Methods and devices for transmitting fault information, and non-volatile storage media

Abstract

This application discloses a method and apparatus for transmitting fault information, as well as a non-volatile storage medium. The method includes: a target controller in a control system acquiring a first operating state of a target vehicle, wherein the target controller is any level controller in a multi-level controller system; if the first operating state indicates that the target vehicle's operating state is a fault state, determining a second operating state of the target controller, and determining a first state identifier based on the second operating state, wherein the first state identifier indicates the operating state of the target controller in the current operating cycle; determining a second state identifier to be output by the target controller based on the first operating state and the first state identifier; and sending the second state identifier to the next-level controller of the target controller in the control system. This application solves the technical problem of reduced vehicle safety caused by the inability to promptly handle faults due to communication failures between multiple controllers in a vehicle.

Description

Technical Field

[0001] This application relates to the field of electric vehicles, and more specifically, to a method and apparatus for transmitting fault information and a non-volatile storage medium. Background Technology

[0002] With the digitalization and intelligentization of automobiles, the number of controllers installed in vehicles is increasing daily; an electric vehicle typically has dozens of controllers. Each of these controllers performs different functions; for example, one controller is responsible for monitoring and identifying certain faults, while the remaining controllers are responsible for handling different types of faults. Therefore, when a communication failure occurs between the controller responsible for fault identification and the controller responsible for fault handling, it can lead to inconsistent and inconsistent fault handling measures, resulting in problems such as the inability to handle faults in a timely manner and reduced vehicle safety.

[0003] There is currently no effective solution to the above problems. Summary of the Invention

[0004] This application provides a method and apparatus for transmitting fault information, as well as a non-volatile storage medium, to at least solve the technical problem of reduced vehicle safety caused by the inability to process faults in a timely manner due to communication failures between multiple controllers in a vehicle.

[0005] According to one aspect of the embodiments of this application, a method for transmitting fault information is provided, comprising: a target controller in a control system acquiring a first operating state of a target vehicle, wherein the operating state of the target vehicle includes a normal state and a fault state, and the target controller is any level controller in a multi-level controller in the control system; if the first operating state indicates that the operating state of the target vehicle is a fault state, determining a second operating state of the target controller, and determining a first state identifier based on the second operating state, wherein the first state identifier is stored in the target controller and is used to indicate the operating state of the target controller in the current operating cycle; determining a second state identifier to be output by the target controller based on the first operating state and the first state identifier; and sending the second state identifier to the next level controller of the target controller in the control system.

[0006] Optionally, the second operating state includes: a dormant state and a non-dormant state; determining the first state identifier based on the second operating state includes: setting the first state identifier to a fault state when the second operating state is a dormant state; and setting the first state identifier to the operating state of the target controller in the previous cycle of the current operating cycle when the second operating state is a non-dormant state.

[0007] Optionally, determining the second status identifier to be output by the target controller based on the first operating state and the first status identifier includes: setting the second status identifier to a fault state when the first operating state or the first status identifier is a fault state.

[0008] Optionally, after sending the second status identifier to the next-level controller of the target controller in the control system, the method includes: determining a fourth status identifier to be output by the next-level controller based on the second status identifier and the third status identifier, wherein the third status identifier is stored in the next-level controller and is used to indicate the operating status of the target controller in the previous cycle of the current operating cycle; and determining the strategy to be executed by the next-level controller based on the fourth status identifier.

[0009] Optionally, the fourth status identifier to be output by the next-level controller is determined based on the second status identifier and the third status identifier, including: if either the second status identifier or the third status identifier is a fault status, the fourth status identifier is set to a fault status; if both the second status identifier and the third status identifier are normal statuses, the fourth status identifier is set to a normal status.

[0010] Optionally, determining the strategy executed by the control system based on the fourth state identifier includes: determining the strategy executed by the control system as a first strategy when the third state identifier is a fault state; and determining the strategy executed by the control system as a second strategy when the third state identifier is a normal state.

[0011] Optionally, the first strategy includes controlling the next-level controller to execute a fault handling method; the second strategy includes controlling the target controller and the next-level controller to continue operating in their current operating states.

[0012] Optionally, after executing the first strategy, the method for transmitting fault information further includes: obtaining the fifth status identifier of the target controller output after executing the first strategy; if the fifth status identifier is a fault state, setting the third status identifier to a fault state; if the fifth status identifier is a normal state, setting the third status identifier to the operating state of the target controller in the previous cycle of the current cycle.

[0013] According to another aspect of the embodiments of this application, a fault information transmission device is also provided, comprising: an acquisition module, configured to control a target controller in the system to acquire a first operating state of a target vehicle, wherein the operating state of the target vehicle includes a normal state and a fault state, and the target controller is any level controller in a multi-level controller in the control system; a first determination module, configured to determine a second operating state of the target controller when the first operating state indicates that the operating state of the target vehicle is a fault state, and to determine a first status identifier based on the second operating state, wherein the first status identifier is stored in the target controller and is used to indicate the operating state of the target controller in the current operating cycle; a second determination module, configured to determine a second status identifier to be output by the target controller based on the first operating state and the first status identifier; and a sending module, configured to send the second status identifier to the next level controller of the target controller in the control system.

[0014] According to another aspect of the embodiments of this application, a non-volatile storage medium is also provided, which stores a computer program, wherein the above-described fault information transmission method is executed by running the computer program in the device where the non-volatile storage medium is located.

[0015] According to another aspect of the embodiments of this application, an electronic device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the above-described fault information transmission method through the computer program.

[0016] In this embodiment, a target controller in the control system is used to obtain the first operating state of the target vehicle, which includes a normal state and a fault state. The target controller is any level controller in the multi-level controllers of the control system. When the first operating state indicates that the target vehicle is in a fault state, a second operating state of the target controller is determined, and a first state identifier is determined based on the second operating state. The first state identifier is stored in the target controller and is used to indicate the operating state of the target controller in the current operating cycle. A second state identifier to be output by the target controller is determined based on the first operating state and the first state identifier. The second state identifier is sent to the next level controller of the target controller in the control system. By connecting multiple controllers in the vehicle and storing the fault flag bit of the connected upper level controller in the lower level controller, the washing machine controller can detect the fault of the upper level controller in a timely manner, thereby achieving the technical effect of timely fault handling. This solves the technical problem of reduced vehicle safety caused by the inability to handle faults in a timely manner due to communication failures between multiple controllers in the vehicle. Attached Figure Description

[0017] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0018] Figure 1 This is a hardware structure block diagram of a computer terminal (or mobile device) for implementing a method for transmitting fault information according to an embodiment of this application;

[0019] Figure 2 This is a flowchart of a fault information transmission method according to an embodiment of this application;

[0020] Figure 3 This is a schematic diagram of a control system according to an embodiment of this application;

[0021] Figure 4 This is a structural diagram of a fault information transmission device according to an embodiment of this application;

[0022] Figure 5 This is a flowchart of a target controller according to an embodiment of this application;

[0023] Figure 6 This is a flowchart of the operation of a next-level controller of a target controller according to an embodiment of this application. Detailed Implementation

[0024] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0025] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0026] In related technologies, when communication anomalies such as communication failure or communication lag occur between the controller used for fault identification and the controller used for fault handling, the controller used for fault handling cannot receive the identification results sent by the controller used for fault identification in a timely manner. Therefore, it is possible that the fault is not handled in time at the first moment of vehicle malfunction. When communication between the controller used for fault identification and the controller used for fault handling is restored, the previously detected fault may have been missed again. Thus, there is a problem of repeated fault occurrences due to untimely fault handling. To solve this problem, the embodiments of this application provide relevant solutions, which are described in detail below.

[0027] According to an embodiment of this application, a method for transmitting fault information is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0028] The methods and embodiments provided in this application can be executed on mobile terminals, computer terminals, or similar computing devices. Figure 1 A hardware block diagram of a computer terminal (or mobile device) for implementing a method for transmitting fault information is shown. Figure 1 As shown, the computer terminal 10 (or mobile device 10) may include one or more processors 102 (shown as 102a, 102b, ..., 102n in the figure) 102 (processor 102 may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.), a memory 104 for storing data, and a transmission device 106 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of a BUS bus), a network interface, a power supply, and / or a camera. Those skilled in the art will understand that... Figure 1 The structure shown is for illustrative purposes only and does not limit the structure of the aforementioned electronic device. For example, computer terminal 10 may also include... Figure 1 The more or fewer components shown, or having the same Figure 1 The different configurations shown.

[0029] It should be noted that the aforementioned one or more processors 102 and / or other data processing circuits are generally referred to herein as "data processing circuits". These data processing circuits may be embodied, in whole or in part, in software, hardware, firmware, or any other combination thereof. Furthermore, the data processing circuits may be a single, independent processing module, or may be integrated, in whole or in part, into any other element within the computer terminal 10 (or mobile device). As involved in the embodiments of this application, the data processing circuits serve as a processor control mechanism (e.g., selection of a variable resistor termination path connected to an interface).

[0030] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the fault information transmission method in this embodiment. The processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, thereby realizing the aforementioned fault information transmission method. The memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to the computer terminal 10 via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0031] The transmission device 106 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the communication provider of the computer terminal 10. In one example, the transmission device 106 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 106 may be a Radio Frequency (RF) module, used for wireless communication with the Internet.

[0032] The display can be, for example, a touchscreen liquid crystal display (LCD) that allows the user to interact with the user interface of the computer terminal 10 (or mobile device).

[0033] Figure 2 This is a flowchart of a fault information transmission method provided according to an embodiment of this application, such as... Figure 2 As shown, the method includes the following steps:

[0034] In step S202, the target controller in the control system acquires the first operating state of the target vehicle, wherein the operating state of the target vehicle includes: normal state and fault state, and the target controller is any level controller in the multi-level controller of the control system.

[0035] Figure 3 This is a schematic diagram of the control system, such as... Figure 3 As shown, the control system contains multiple fault identification controllers and multiple fault handling controllers. The fault identification controller identifies whether the vehicle's operating state is normal or faulty, and transmits the identification result to the next fault handling controller connected to it. The next fault handling controller then transmits its own operating state to the next level controller connected to it. In other words, each controller stores the operating state of the previous controller it is connected to. Multiple fault handling controllers execute different processing methods based on the received information. The method provided in this application embodiment is applied to... Figure 3 In the control system shown, in step S202, the controller used to implement the fault identification function (i.e., the target controller) obtains whether the (first) operating state of its vehicle (i.e., the target vehicle) is a fault state or a normal state. The controller used to implement the fault identification function (i.e., the target controller) can be at any level in the control system. Furthermore, since the control system simultaneously has a controller for fault identification and a controller for fault handling, the controller for fault identification (i.e., the target controller) necessarily has a next-level controller for fault handling.

[0036] Step S204: If the first operating state indicates that the target vehicle is in a fault state, determine the second operating state of the target controller and determine the first state identifier based on the second operating state. The first state identifier is stored in the target controller and is used to indicate the operating state of the target controller in the current operating cycle.

[0037] In step S204, when the controller used to implement the fault identification function (i.e., the target controller) determines that its vehicle (i.e., the target vehicle) is in a fault state, the target controller first determines its own (second) operating state, and then determines the (first) status identifier stored in the target controller that indicates the operating state of the target controller in the current operating cycle based on its own operating state. The determination of the (first) status identifier stored in the target controller that indicates the operating state of the target controller in the current operating cycle based on its own operating state can be achieved by assigning a value.

[0038] According to an optional embodiment of this application, the second operating state includes: a dormant state and a non-dormant state; determining a first state identifier based on the second operating state includes: when the second operating state is a dormant state, setting the first state identifier to a fault state; when the second operating state is a non-dormant state, setting the first state identifier to the operating state of the target controller in the previous cycle of the current operating cycle.

[0039] In this embodiment, the target controller determines its (second) operating state by: determining whether it is in a dormant state; if the target controller determines that it is in a dormant state, it sets its stored (first) state identifier to a fault state; otherwise, it sets its stored (first) state identifier to the operating state of the target controller in the previous cycle of the current operating cycle. When implementing the method of this embodiment by assignment, the steps are as follows: the identifier representing the vehicle's (first) operating state is set to 'a', the value of the fault state is set to 1, the value of the normal state is set to 0, and the identifier representing the target controller's (second) operating state in the current operating cycle (i.e., the first state identifier) ​​is set to 'b(n)', where n represents the operating cycle. When the vehicle's (first) operating state is determined to be a fault state, the value of a is assigned to 1. Based on this, the (second) operating state of the target controller in the current operating cycle is further determined. When the (second) operating state is a dormant state, the value of b(n) is assigned to the value of a, that is, the value of b(n) is assigned to 1, indicating that the vehicle's fault is that the controller is dormant. When the (second) operating state is a non-dormant state, the value of b(n) is assigned to the value of the target controller's status identifier b(n-1) when it was running in the previous cycle.

[0040] Step S206: Determine the second status identifier to be output by the target controller based on the first operating state and the first status identifier.

[0041] In step S206, after the target controller has determined the operating state of the (target) vehicle and the operating state of the controller (i.e., the target controller) used to implement the fault identification function through steps S202 and S204 respectively, the (second) status identifier to be output by the target controller is determined based on the (first) status identifier indicating the (second) operating state of the target controller in the current cycle and the (first) operating state of the (target) vehicle in the current cycle; specifically, this can be achieved through an assignment operation. The steps of the assignment operation are: set the second status identifier to be output as c, and determine the value of c to be output based on the value of a and the value of b(n).

[0042] According to an optional embodiment of this application, determining the second status identifier to be output by the target controller based on the first operating state and the first status identifier includes: setting the second status identifier to a fault state when the first operating state or the first status identifier is a fault state.

[0043] In this embodiment, the method for determining the (second) status identifier to be output by the target controller based on the (first) status identifier indicating the (second) operating state of the target controller in the current cycle and the (first) operating state of the (target) vehicle in the current cycle is as follows: If the target vehicle is in a fault state, i.e., a = 1, and the (second) operating state of the target controller is in a dormant state, i.e., b(n) = a, the value of c is assigned to a, i.e., the value of c is assigned to 1, to notify the next-level controller that the vehicle fault indicates the target controller is in a dormant state; if the target vehicle's status is... If the target vehicle is in a fault state (a = 1) and the target controller's (second) operating state is non-dormant (b(n) = b(n-1)), then the value of c is assigned to a, indicating that the vehicle has a fault. If the target vehicle is in a non-fault state (a = 0) and the target controller's (second) operating state is non-dormant (b(n) = b(n-1)), then the value of c is assigned to b(n-1). The value of c is determined based on the target vehicle's operating state in the previous cycle to prevent the failure to notify the next level controller of the fault that occurred in the target controller in the previous cycle.

[0044] Step S208: Send the second status identifier to the next level controller of the target controller in the control system.

[0045] In step S208, after the (second) status identifier to be output is determined in step S206, it is sent to the next level controller.

[0046] Through the above steps, the operating status of the upper-level controller can be stored in the lower-level controller, so as to execute fault handling methods in a timely manner when a fault occurs, improve the accuracy of the timing of intervention / exit of fault handling measures, and avoid the technical effect of reducing vehicle safety due to repeated faults.

[0047] According to an optional embodiment of this application, after sending the second status identifier to the next-level controller of the target controller in the control system, the method includes: determining a fourth status identifier to be output by the next-level controller based on the second status identifier and the third status identifier, wherein the third status identifier is stored in the next-level controller and is used to indicate the operating status of the target controller in the previous cycle of the current operating cycle; and determining the strategy to be executed by the next-level controller based on the fourth status identifier.

[0048] In this embodiment, after sending the (second) status identifier c to be output to the next-level controller of the target controller, the next-level controller performs the following steps: First, it obtains the (third) status identifier d(n) stored in the controller (i.e., the next-level controller) used to implement the fault handling function, which represents the operating state of the target controller in the previous cycle; based on the received (second) status identifier c and the (third) status identifier d(n) of the target controller in the previous cycle, it determines the (fourth) status identifier e that the controller (i.e., the next-level controller) used to implement the fault handling function will send to its own next-level controller, as well as the strategy that it will execute.

[0049] According to some embodiments of this application, determining the fourth status identifier to be output by the next-level controller based on the second status identifier and the third status identifier includes: if either the second status identifier or the third status identifier is a fault state, setting the fourth status identifier to a fault state; if both the second status identifier and the third status identifier are normal states, setting the fourth status identifier to a normal state.

[0050] In some embodiments, the method for determining the (fourth) status identifier e to be sent by the next-level controller to its own next-level controller based on the received (second) status identifier c and the (third) status identifier d(n) of the target controller's operating state in the previous cycle is as follows: If the value of the (second) status identifier c is assigned a value indicating a fault state, and the (third) status identifier d(n) is assigned a value indicating a non-dormant state, the value of the (fourth) status identifier e is assigned a value indicating a fault state; if the value of the (second) status identifier c is assigned a value indicating a vehicle fault state, and the (third) status identifier d(n) is assigned a value indicating a dormant state, the value of the (fourth) status identifier e is assigned a value indicating a dormant state; If the value of (second) status identifier c is assigned to the value indicating a sleep state, and the value of (third) status identifier d(n) is assigned to the value indicating a sleep state, then the value of (fourth) status identifier e is assigned to the value indicating a sleep state; if the value of (second) status identifier c is assigned to the value indicating a non-sleep state, and the value of (third) status identifier d(n) is assigned to the value indicating a sleep state, then the value of (fourth) status identifier e is assigned to the value indicating a sleep state; if the value of (second) status identifier c is assigned to the value indicating a non-fault state (including non-sleep state and non-vehicle fault state), and the value of (third) status identifier d(n) is assigned to the value indicating a non-sleep state, then the value of (fourth) status identifier e is assigned to the value indicating a non-fault state.

[0051] According to an optional embodiment of this application, determining the strategy executed by the control system based on the fourth state identifier includes: determining the strategy executed by the control system as a first strategy when the fourth state identifier is a fault state; and determining the strategy executed by the control system as a second strategy when the fourth state identifier is a normal state.

[0052] In this embodiment, when the value of the (fourth) status identifier e is assigned a value representing a dormant state and a value representing a fault state, the control system executes a fault handling strategy (i.e., the first strategy); when the value of the (fourth) status identifier e is assigned a value representing a non-fault state, the control system executes a strategy to enable the vehicle to operate normally (i.e., the second strategy).

[0053] According to other embodiments of this application, the first strategy includes: controlling the next-level controller to execute a fault handling method; the second strategy includes: controlling the target controller and the next-level controller to continue operating in their current operating states.

[0054] In other embodiments, the fault handling strategy (i.e., the first strategy) includes the following cases: If the value of the (second) status identifier c is set to 1, it indicates that the target controller is in a dormant state in the current operating cycle, and d(n) also indicates that the target controller was in a dormant state in the previous operating cycle. The next-level controller executes the strategy corresponding to the controller dormancy (i.e., the first strategy); If the value of the (second) status identifier c is set to 1, it indicates that the target controller is in a dormant state in the current operating cycle, but d(n) indicates that the target controller was in a non-dormant state in the previous operating cycle. The next-level controller also executes the strategy corresponding to the controller dormancy (i.e., the first strategy); If the value of the (second) status identifier c is set to a, it indicates that the vehicle has a fault, and d(n) indicates that the target controller is in a non-dormant state in the previous operating cycle. If the target controller was in a sleep state in the previous operating cycle of the current operating cycle, it is determined that the vehicle fault was caused by the target controller being in a sleep state. The next-level controller executes the strategy corresponding to the target controller's sleep state (i.e., the first strategy). If the value of the (second) status identifier c is assigned to a, it indicates that the vehicle has a fault, but d(n) indicates that the target controller was not in a sleep state in the previous operating cycle of the current operating cycle. The next-level controller determines to execute the strategy corresponding to the vehicle fault (i.e., the first strategy). If the value of the (second) status identifier c is assigned to b(n-1), and b(n-1) indicates a sleep state, regardless of whether d(n) indicates that the target controller was in a sleep state or not in a sleep state in the previous operating cycle of the current operating cycle, the next-level controller determines to execute the strategy corresponding to the target controller's sleep state (i.e., the first strategy). The strategy for enabling the vehicle to operate normally (i.e., the second strategy) is executed as follows: if the value of the (second) state identifier c is assigned to b(n-1), and b(n-1) indicates a non-dormant state, and d(n) also indicates that the target controller was in a non-dormant state in the previous operating cycle of the current operating cycle, it is determined that the vehicle is fault-free and the controller is not in a dormant state. The next level controller then determines to execute the strategy corresponding to the normal operating state (i.e., the second strategy).

[0055] According to an optional embodiment of this application, after executing the first strategy, the method for transmitting fault information further includes: obtaining a fifth status identifier of the target controller output after executing the first strategy; if the fifth status identifier is a fault state, setting a third status identifier to a fault state; if the fifth status identifier is a normal state, setting the third status identifier to the operating state of the target controller in the previous cycle of the current cycle.

[0056] In this embodiment, after the control system executes the fault handling strategy (i.e., the first strategy), it again obtains the status identifier c (i.e., the fifth status identifier) ​​output by the target controller. If the status identifier c represents a fault state (any one of the fault states, such as the hibernation state or other vehicle faults), the (third) status identifier d(n) stored in the next-level controller, which represents the operating state of the target controller in the previous operating cycle, is assigned the value of c. If the status identifier c represents a non-fault state, the (third) status identifier d(n) is assigned the value of the status identifier d(n-1) stored in the controller, which represents the operating state of the target controller in the previous operating cycle.

[0057] Figure 4 This is a structural diagram of a fault information transmission device provided in an embodiment of this application, comprising: an acquisition module 40, configured to control a target controller in the system to acquire a first operating state of a target vehicle, wherein the operating state of the target vehicle includes a normal state and a fault state, and the target controller is any level controller in a multi-level controller in the control system; a first determination module 42, configured to determine a second operating state of the target controller when the first operating state indicates that the operating state of the target vehicle is a fault state, and to determine a first status identifier based on the second operating state, wherein the first status identifier is stored in the target controller and is used to indicate the operating state of the target controller in the current operating cycle; a second determination module 44, configured to determine a second status identifier to be output by the target controller based on the first operating state and the first status identifier; and a sending module 46, configured to send the second status identifier to the next level controller of the target controller in the control system.

[0058] Figure 5 This is a flowchart of the target controller's workflow, such as... Figure 5As shown, when the above-mentioned transmission device is working, the acquisition module 40 acquires the vehicle's operating status through the controller used for fault identification (i.e., the target controller). If the vehicle has a fault, the identifier a representing the vehicle's operating status is assigned a value of 1; if the vehicle does not have a fault, the identifier a representing the vehicle's operating status is assigned a value of 0. Further, when the vehicle has a fault (i.e., when a = 1), the first determination module 42 determines whether the target controller's own operating status is in a dormant state or a non-dormant state through the target controller. If the target controller is in a dormant state, the value of the identifier a representing the vehicle's operating status is assigned to the first status identifier b(n) representing the target controller's operating status. If the target controller is not in a dormant state, the value of the identifier b(n-1) representing the target controller's operating status in the previous operating cycle is assigned to b(n). The second determination module 44 determines the second status identifier c to be output through the target controller. Specifically, the second status identifier c is assigned the value of the logical OR of b(n) and a, i.e., c = a||b(n). After determining the value of the second status identifier c, the sending module 44 outputs the second status identifier c to the next level controller of the target controller.

[0059] Figure 6 This is a flowchart of the workflow of the next level controller of the target controller, such as... Figure 6 As shown, the next-level controller receives the second status identifier c and, based on the value of its stored identifier d(n) representing the target controller's operating state in the previous cycle, jointly determines the value of the status identifier e to be output by the next-level controller. Specifically, the value of status identifier e is the logical OR of the value of the second status identifier c and d(n). After determining the value of status identifier e, it is determined whether e indicates a fault state. If e indicates a fault state, fault handling method A is executed; otherwise, fault handling method A is not executed. After executing fault handling method A, the next-level controller will again obtain the second status identifier c, determine d(n), and, if the target controller is in sleep mode, assign the value of c to d(n). If the target controller is not in sleep mode, assign the value of the operating state d(n-1) from the previous cycle to d(n).

[0060] It should be noted that the controller used for fault handling (i.e., the next-level controller), like the target controller, can also transmit a status flag indicating whether it is in sleep mode to the next-level controller connected to it.

[0061] It should be noted that, Figure 4 Preferred embodiments of the shown examples can be found in [reference needed]. Figure 2 The relevant descriptions of the embodiments shown will not be repeated here.

[0062] This application also provides a non-volatile storage medium storing a computer program, wherein the device containing the non-volatile storage medium executes the above-mentioned fault information transmission method by running the computer program.

[0063] The aforementioned non-volatile storage medium is used to store a program that performs the following functions: the target controller in the control system acquires a first operating state of the target vehicle, wherein the operating state of the target vehicle includes a normal state and a fault state, and the target controller is any level controller in the multi-level controller in the control system; if the first operating state indicates that the operating state of the target vehicle is a fault state, the target controller determines a second operating state, and determines a first state identifier based on the second operating state, wherein the first state identifier is stored in the target controller and is used to indicate the operating state of the target controller in the current operating cycle; the target controller determines a second state identifier to be output based on the first operating state and the first state identifier; and the target controller sends the second state identifier to the next level controller in the control system.

[0064] This application also provides an electronic device, including a memory and a processor. The memory stores a computer program, and the processor is configured to execute the above-mentioned fault information transmission method through the computer program.

[0065] The processor in the aforementioned electronic device is used to run a program that performs the following functions: the target controller in the control system acquires a first operating state of the target vehicle, wherein the operating state of the target vehicle includes a normal state and a fault state, and the target controller is any level controller in the multi-level controller in the control system; if the first operating state indicates that the operating state of the target vehicle is a fault state, the target controller determines a second operating state, and determines a first state identifier based on the second operating state, wherein the first state identifier is stored in the target controller and is used to indicate the operating state of the target controller in the current operating cycle; the target controller determines a second state identifier to be output based on the first operating state and the first state identifier; and the target controller sends the second state identifier to the next level controller in the control system.

[0066] It should be noted that each module in the aforementioned fault information transmission device can be a program module (e.g., a set of program instructions that implement a specific function) or a hardware module. For the latter, it can take the following forms, but is not limited to them: each of the aforementioned modules is represented by a processor, or the functions of each of the aforementioned modules are implemented by a processor.

[0067] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0068] In the above embodiments of this application, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0069] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For instance, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling, direct coupling, or communication connection may be through some interfaces; the indirect coupling or communication connection between units or modules may be electrical or other forms.

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

[0071] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

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

[0073] The above description is only a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A method for transmitting fault information, characterized in that, include: The target controller in the control system acquires the first operating state of the target vehicle, wherein the operating state of the target vehicle includes: normal state and fault state, and the target controller is any one level controller in the multi-level controller of the control system; When the first operating state indicates that the operating state of the target vehicle is the fault state, the second operating state of the target controller is determined, and a first state identifier is determined based on the second operating state, wherein the first state identifier is stored in the target controller and is used to indicate the operating state of the target controller in the current operating cycle; The second status identifier to be output by the target controller is determined based on the first operating state and the first status identifier; The second status identifier is sent to the next level controller of the target controller in the control system.

2. The method according to claim 1, characterized in that, The second operating state includes: hibernation state and non-hibernation state; Determining the first state identifier based on the second operating state includes: When the second operating state is the hibernation state, the first state identifier is set to the fault state; When the second operating state is the non-dormant state, the first state identifier is set to the operating state of the target controller in the previous cycle of the current operating cycle.

3. The method according to claim 1, characterized in that, Determining the second status identifier to be output by the target controller based on the first operating state and the first status identifier includes: setting the second status identifier to the fault state when the first operating state or the first status identifier is the fault state.

4. The method according to claim 1, characterized in that, After sending the second status identifier to the next-level controller of the target controller in the control system, the method includes: The fourth status identifier to be output by the next-level controller is determined based on the second status identifier and the third status identifier, wherein the third status identifier is stored in the next-level controller and is used to indicate the operating status of the target controller in the previous cycle of the current operating cycle; The strategy to be executed by the next-level controller is determined based on the fourth state identifier.

5. The method according to claim 4, characterized in that, The fourth status identifier to be output by the next-level controller is determined based on the second and third status identifiers, including: If either the second status identifier or the third status identifier is the fault state, then the fourth status identifier is set to the fault state. If both the second and third status identifiers are in the normal state, the fourth status identifier is set to the normal state.

6. The method according to claim 4, characterized in that, Determining the strategy executed by the control system based on the fourth state identifier includes: When the fourth state is identified as the fault state, the strategy executed by the control system is determined to be the first strategy; When the fourth state is identified as the normal state, the strategy executed by the control system is determined to be the second strategy.

7. The method according to claim 6, characterized in that, The first strategy includes: controlling the next-level controller to execute a fault handling method; The second strategy includes controlling the target controller and the next-level controller to continue operating in their current state.

8. The method according to claim 7, characterized in that, After executing the first strategy, the method further includes: Obtain the fifth state identifier of the target controller output after the first strategy is executed; If the fifth state identifier is the fault state, then the third state identifier is set to the fault state; If the fifth state identifier is the normal state, the third state identifier is set to the operating state of the target controller in the previous cycle of the current cycle.

9. A fault information transmission device, characterized in that, include: The acquisition module is used to acquire the first operating state of the target vehicle in the control system target controller, wherein the operating state of the target vehicle includes: normal state and fault state, and the target controller is any one level controller in the multi-level controller of the control system; The first determining module is configured to determine the second operating state of the target controller when the first operating state indicates that the operating state of the target vehicle is the fault state, and to determine the first state identifier based on the second operating state, wherein the first state identifier is stored in the target controller and is used to indicate the operating state of the target controller in the current operating cycle; The second determining module is used to determine the second state identifier to be output by the target controller based on the first operating state and the first state identifier; The sending module is used to send the second status identifier to the next-level controller of the target controller in the control system.

10. A non-volatile storage medium, characterized in that, The non-volatile storage medium stores a computer program, wherein the device containing the non-volatile storage medium executes the fault information transmission method according to any one of claims 1 to 8 by running the computer program.

Images