A method and apparatus for failure storage

Abstract

The embodiment of the application provides a fault storage method and device, the method is applied to a controller comprising a plurality of storage spaces. Specifically, when the fault storage method is executed, the controller can first acquire a first fault event, the first fault event is a fault affecting exhaust emission of a vehicle engine. If each storage space of the plurality of storage spaces stores a fault event, the controller can determine a fault event with the lowest priority from a plurality of fault events stored by the plurality of storage spaces. The fault event is referred to as a second fault event. The controller stores the first fault event through the storage space storing the second fault event. In this way, the fault events stored by the storage spaces of the controller are dynamically adjusted, so that the newly occurring fault event has sufficient storage space for storage, thereby timely limiting the output power of the engine, and avoiding environmental pollution due to engine failure.

Description

Technical Field

[0001] This application relates to the field of vehicle control, and more particularly to a method and apparatus for fault storage. Background Technology

[0002] Vehicles may experience various malfunctions during operation. Some of these malfunctions can lead to increased pollutant emissions from the engine, thereby increasing the vehicle's environmental impact. For example, if the vehicle's exhaust aftertreatment system malfunctions, the vehicle cannot properly treat the exhaust gases produced by engine combustion, resulting in untreated exhaust gases being directly emitted into the atmosphere. Untreated exhaust gases contain more pollutants, causing significant environmental pollution.

[0003] Therefore, a timer can be started after a vehicle experiences a malfunction that could seriously impact the environment, and the engine's output power can be limited after the malfunction has lasted for a certain period. By limiting the engine's output power, the rate at which the engine consumes fuel is reduced, thus decreasing the amount of exhaust gases produced per unit time. In this way, even if the aforementioned malfunction occurs, the reduced engine emissions can still keep environmental pollution within a reasonable range.

[0004] The above method requires storing fault-related information in the memory of the control system used to control the engine. However, the memory has limited storage space and may not be able to store all fault-related information, thus failing to limit the vehicle engine's output power in a timely manner. Summary of the Invention

[0005] In view of this, embodiments of this application provide a method and apparatus for fault storage, which aims to flexibly adjust the storage space of a vehicle so that fault-related information has usable storage space.

[0006] In a first aspect, embodiments of this application provide a method for fault storage, the method being applied to a controller, the controller including multiple storage spaces, including:

[0007] Obtain the first fault event;

[0008] In response to the fact that each of the plurality of storage spaces stores a fault event, a second fault event is determined from the plurality of fault events stored in the plurality of storage spaces, wherein the second fault event is the event with the lowest priority among the plurality of fault events;

[0009] The first fault event is stored in the storage space corresponding to the second fault event.

[0010] In one possible implementation, determining the second fault event from the plurality of fault events stored in the plurality of storage spaces includes:

[0011] Based on the storage priority parameter of each of the plurality of fault events, the second fault event is determined from the plurality of fault events. The second fault event is the fault event with the lowest storage priority parameter among the plurality of fault events, where the storage priority parameter represents the priority of the fault time.

[0012] In one possible implementation, determining the second fault event from the plurality of fault events based on a storage priority parameter for each fault event includes:

[0013] Based on the plurality of fault events, at least one candidate fault event is determined, wherein the fault event corresponding to the candidate fault event has ended.

[0014] The second fault event is determined from the at least one candidate fault events based on the storage priority parameter of each candidate fault event.

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

[0016] Based on the fault type corresponding to the first fault event, determine the storage priority parameters of the first fault event;

[0017] In response to the end of the first fault event, the storage priority parameter of the first fault event is adjusted according to the priority decay parameter. The priority decay parameter represents the relationship between the priority of the second fault event and time.

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

[0019] Obtain the duration of the first fault event;

[0020] It is determined that the first fault event has occurred again;

[0021] In response to the storage priority parameter of the first fault event not being equal to zero, the duration of the first fault continues to be recorded based on the duration of the first fault event.

[0022] Secondly, embodiments of this application provide a fault storage device, which is applied to a controller, the controller including multiple storage spaces, the device comprising:

[0023] Acquisition unit, used to acquire the first fault event;

[0024] A processing unit is configured to, in response to the fact that each of the plurality of storage spaces stores a fault event, determine a second fault event from the plurality of fault events stored in the plurality of storage spaces, wherein the second fault event is the event with the lowest priority among the plurality of fault events;

[0025] The processing unit is further configured to store the first fault event in the storage space corresponding to the second fault event.

[0026] In one possible implementation, the processing unit is specifically configured to determine the second fault event from the plurality of fault events based on the storage priority parameter of each fault event among the plurality of fault events, wherein the second fault event is the fault event with the lowest storage priority parameter among the plurality of fault events, and the storage priority parameter represents the priority of the fault time.

[0027] In one possible implementation, the processing unit is specifically configured to determine at least one candidate fault event based on the plurality of fault events, wherein the fault event corresponding to the candidate fault event is a fault event that has ended; and to determine the second fault event from the at least one candidate fault event based on the storage priority parameter of each candidate fault event among the at least one candidate fault events.

[0028] In one possible implementation, the processing unit is further configured to determine a storage priority parameter for the first fault event based on the fault type corresponding to the first fault event; and to adjust the storage priority parameter of the first fault event according to a priority decay parameter in response to the end of the first fault event. The priority decay parameter represents the relationship between the priority of the second fault event and time.

[0029] In one possible implementation, the acquisition unit is further configured to acquire the duration of the first fault event;

[0030] The processing unit is further configured to determine that the first fault event occurs again; in response to the storage priority parameter of the first fault event being non-zero, to continue recording the duration of the first fault based on the duration of the first fault event.

[0031] Thirdly, embodiments of this application provide an apparatus including a memory and a processor, the memory being used to store instructions or code, and the processor being used to execute the instructions or code to cause the apparatus to perform the fault storage method described in any of the first aspects above.

[0032] Fourthly, embodiments of this application provide a computer storage medium storing code, wherein when the code is executed, a device running the code implements the fault storage method described in any of the first aspects above.

[0033] Fifthly, embodiments of this application provide a vehicle, the vehicle including an engine and a controller, the controller including a plurality of storage spaces for storing engine fault events, and the controller for adjusting the information stored in the plurality of storage spaces to implement the fault storage method described in any of the first aspects above.

[0034] This application provides a method and apparatus for fault storage. The method can be applied to a controller, which includes multiple storage spaces, each of which can be used to store vehicle fault events. Specifically, when executing the fault storage method, the controller first acquires a first fault event, which is a fault affecting vehicle engine exhaust emissions. Next, the controller determines whether there is any free storage space among the multiple storage spaces. If there is free storage space, the controller can store the first fault event and its related information in the free storage space. If each of the multiple storage spaces stores a fault event, the controller can determine the fault event with the lowest priority from the multiple fault events stored in the multiple storage spaces. This fault event is referred to as the second fault event. Then, the controller stores the first fault event in the storage space storing the second fault event. Thus, if the controller's storage space is insufficient to store a newly occurring first fault event, the controller can select the lowest priority fault event from the already stored fault events as the second fault event and replace the fault event stored in the storage space storing the second fault event with the first fault event. In this way, the fault events stored in the controller's storage space are dynamically adjusted so that newly occurring fault events have sufficient storage space to limit the engine's output power in a timely manner, thus preventing environmental pollution caused by engine failure. Attached Figure Description

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

[0036] Figure 1 A flowchart illustrating the method for fault storage provided in this application embodiment;

[0037] Figure 2 This is a schematic diagram of a fault storage device provided in an embodiment of this application. Detailed Implementation

[0038] Engine exhaust gases are a significant source of environmental pollution. Various methods exist to reduce pollution, such as adjusting engine intake and fuel injection, and treating engine exhaust gases. However, if a vehicle malfunctions, these pollution reduction methods may fail to function properly, thus hindering the reduction of pollutant emissions and consequently hindering environmental pollution control.

[0039] To address the aforementioned issues, sensors can be used to detect whether a fault has occurred. In this embodiment, the occurrence of a fault is referred to as a fault event. After a fault event is detected, its duration can be recorded. If a fault event lasts for more than a first preset duration, the controller can limit the engine's output power, for example, by limiting the engine's maximum output torque. This reduces environmental pollution by limiting the total amount of exhaust gas produced by the engine.

[0040] Furthermore, the duration of the fault event can be recorded after it ends. If, within a second time period after the end of a fault event, a fault of the same type does not recur, the controller can delete the fault event stored in memory. If, within a second time period after the end of the fault event, a fault of the same type recurs, the controller can continue recording the duration of the fault event based on the previous duration. The recording of the fault event's duration and end time can be referred to as storing the fault event, or recording the fault event.

[0041] In order to effectively reduce emissions, the above-mentioned treatment plan has been implemented by vehicles in accordance with the National VI Emission Standard for Motor Vehicles (hereinafter referred to as "National VI").

[0042] However, the aforementioned controllers are typically executed by the engine's Electronic Control Unit (ECU) or the vehicle's controller. Both the ECU and the vehicle controller have limited storage space. If the vehicle experiences multiple malfunctions, the information related to these malfunctions can consume a significant amount of storage space. Once the controller's storage space is exhausted, if another malfunction requiring recording occurs, the memory cannot continue storing the malfunction events, making it impossible to promptly limit engine torque and resulting in poor emission reduction.

[0043] To make more efficient use of the controller's storage space, embodiments of this application provide a method and apparatus for fault storage.

[0044] Optionally, the technical solution provided in this application embodiment is applied to a controller, which may be an Electronic Control Unit (ECU) in a vehicle, or other devices in the vehicle with data processing capabilities for recording faults. The controller may include multiple storage spaces. Each of the multiple storage spaces can be used to record fault events. Optionally, the storage spaces can be implemented using a memory within the controller, or using a memory connected to the controller. Specifically, the aforementioned memory may be RAM or a cache.

[0045] The following describes the fault storage method provided in the embodiments of this application from the perspective of the controller. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0046] See Figure 1 , Figure 1 A flowchart of a method for fault storage provided in this application embodiment includes:

[0047] S101: Obtain the first fault event.

[0048] The controller can detect vehicle malfunctions using sensors and other devices. If the controller determines that a malfunction has occurred, it can be said that the controller has acquired a malfunction event. For ease of explanation, this embodiment of the application uses the controller acquiring a first malfunction event as an example.

[0049] In the embodiments of this application, the first fault event can correspond to different fault types. Specifically, depending on the device that malfunctions, the first fault event can be any one of the following: intake fault, fuel fault, aftertreatment fault, and communication fault. Of course, the first fault event can also correspond to other faults that may affect the amount of pollutants emitted in the vehicle engine exhaust.

[0050] After detecting the first fault, the controller can determine whether there is any free storage space among the multiple storage spaces corresponding to the controller. Free storage space includes storage space that has not recorded fault events. Alternatively, free storage space may also include storage space that has recorded fault events, but the recorded fault events have ended, and the time elapsed since the end of the fault events exceeds the time elapsed before a second preset event.

[0051] If the controller has multiple storage spaces, including free storage space, the controller stores the first fault event using the free storage space. For details on how the controller stores the first fault event, please refer to S03; it will not be elaborated here.

[0052] If none of the multiple storage spaces corresponding to the controller are free storage spaces, the controller continues to execute S102 as described below.

[0053] S102: In response to the fact that each of the plurality of storage spaces stores a fault event, a second fault event is determined from the plurality of fault events stored in the plurality of storage spaces.

[0054] After determining that there is no free storage space among the multiple storage spaces corresponding to the controller, the controller can determine the second fault event from the multiple fault events stored in the storage space. The storage space used to store the second fault event is called the target storage space. The second fault event is the lowest priority fault event among the multiple fault events stored in the multiple storage spaces.

[0055] The priority of a fault event reflects its severity, specifically indicating the probability that failing to record the fault event could lead to severe environmental pollution from vehicle exhaust. In other words, a higher priority fault event means that failing to record its continuation increases the likelihood of the vehicle's engine causing environmental pollution. Conversely, a lower priority fault event means a lower likelihood of the vehicle's engine causing environmental pollution. Therefore, designating the lowest priority fault event as the second fault event minimizes the likelihood of environmental pollution from discarding it.

[0056] Optionally, the priority of a fault event can be measured using a storage priority parameter. Specifically, when storing a fault event in storage, the controller sets an initial storage priority parameter for that fault event. Then, during the duration of the fault event, the controller maintains the storage priority parameter unchanged. After the fault event ends, the controller gradually decreases the storage priority parameter. Before the storage priority parameter decreases to zero, if a fault of the same type as the fault event occurs again, the controller increases the storage priority parameter for that fault event. After the storage priority parameter decreases to zero, the controller discards the fault event.

[0057] In some possible implementations, the aforementioned storage priority parameters can be implemented using counters. Specifically, a counter can be set for each of multiple storage spaces. The value of the counter represents the storage priority parameter of the fault event stored in the storage space corresponding to that counter.

[0058] In some possible implementations, the controller gradually decreases the storage priority parameter of the fault event according to a priority decay parameter. The priority decay parameter represents the relationship between the priority of the fault event and time. Optionally, the priority decay parameter can be determined based on an initial storage priority parameter and a second preset duration. That is, if the storage priority parameter of the fault event is equal to the initial storage priority parameter, the storage priority parameter is decreased according to the priority decay parameter, and after the second preset duration, the storage priority parameter of the fault event is equal to zero.

[0059] It is understandable that different fault events may correspond to different fault types. For fault events with different fault types, their initial storage priority parameters and / or priority decay parameters may be different.

[0060] Accordingly, when determining the second fault event, the controller can select the fault event with the lowest storage priority parameter from the multiple fault events stored in multiple storage spaces as the second fault event.

[0061] Optionally, considering that fault events stored in multiple storage spaces may include the execution time of a fault, the second fault event can be determined from the fault events that have already ended. Specifically, the controller can determine at least one candidate fault event from multiple fault events based on the state of the fault event. The candidate fault event is the fault event whose corresponding fault has ended. Then, the controller selects the fault event with the smallest storage priority parameter from the at least one candidate fault event as the second fault event.

[0062] S103: Store the first fault event in the storage space corresponding to the second fault event.

[0063] After the second fault event is determined, the controller can store the first fault event in the storage space corresponding to the second fault event (i.e., the aforementioned target storage space).

[0064] If the second fault event is determined based on the storage priority parameters, the controller can set the initial storage priority parameters for the first fault event after storing the first fault event in the target storage space.

[0065] Specifically, the controller can set storage priority parameters for the first fault event based on the fault type corresponding to it. For example, if the fault type corresponding to the first fault event is an aftertreatment fault, then if the engine's output torque is not limited as soon as possible after the first fault event occurs, the pollution caused by the vehicle may be more severe. Therefore, the controller can set the initial storage priority parameters for the first fault event based on a higher storage priority parameter.

[0066] If the fault type corresponding to the first fault event is an intake-related fault, the pollution caused by the vehicle may be relatively small even if the engine's output torque is not limited as soon as possible after the first fault event occurs. Therefore, the controller can set the initial storage priority parameter for the first fault event based on the lower storage priority parameter.

[0067] Accordingly, after the first fault event ends, the controller gradually reduces the storage priority parameter of the first fault event according to the priority decay parameter of the first fault time. If the fault corresponding to the first fault event occurs again before the storage priority parameter of the first fault event is reduced to 0, the controller continues to record the continuous event of the first fault based on the continuous event of the first fault event.

[0068] This application provides a fault storage method, which can be applied to a controller. The controller includes multiple storage spaces, each of which can be used to store vehicle fault events. Specifically, when executing the fault storage method, the controller first acquires a first fault event, which is a fault affecting the vehicle's engine exhaust emissions. Next, the controller determines whether there is any free storage space among the multiple storage spaces. If there is free storage space, the controller can store the first fault event and its related information in the free storage space. If each of the multiple storage spaces stores a fault event, the controller can determine the fault event with the lowest priority from the multiple fault events stored in the multiple storage spaces. This fault event is referred to as the second fault event. Then, the controller stores the first fault event in the storage space storing the second fault event. Thus, if the controller's storage space is insufficient to store a newly occurring first fault event, the controller can select the lowest priority fault event from the already stored fault events as the second fault event and replace the fault event stored in the storage space storing the second fault event with the first fault event. In this way, the fault events stored in the controller's storage space are dynamically adjusted so that newly occurring fault events have sufficient storage space to limit the engine's output power in a timely manner, thus preventing environmental pollution caused by engine failure.

[0069] The above are some specific implementations of the fault storage method provided in the embodiments of this application. Based on this, this application also provides a corresponding apparatus. The apparatus provided in the embodiments of this application will be described below from the perspective of functional modularity.

[0070] See Figure 2 The diagram shows the structure of a fault storage device 200, which includes an acquisition unit 210 and a control unit 220.

[0071] The acquisition unit 210 is used to acquire the first fault event.

[0072] The processing unit 220 is configured to, in response to the fact that each of the plurality of storage spaces stores a fault event, determine a second fault event from the plurality of fault events stored in the plurality of storage spaces, wherein the second fault event is the event with the lowest priority among the plurality of fault events.

[0073] The processing unit 220 is also configured to store the first fault event in the storage space corresponding to the second fault event.

[0074] This application provides a fault storage apparatus. The method can be applied to a controller, which includes multiple storage spaces, each of which can be used to store vehicle fault events. Specifically, when executing the fault storage method, the controller first acquires a first fault event, which is a fault affecting vehicle engine exhaust emissions. Next, the controller determines whether there is any free storage space among the multiple storage spaces. If there is free storage space, the controller can store the first fault event and its related information in the free storage space. If each of the multiple storage spaces stores a fault event, the controller can determine the fault event with the lowest priority from the multiple fault events stored in the multiple storage spaces. This fault event is referred to as the second fault event. Then, the controller stores the first fault event in the storage space storing the second fault event. Thus, if the controller's storage space is insufficient to store a newly occurring first fault event, the controller can select the lowest priority fault event from the already stored fault events as the second fault event and replace the fault event stored in the storage space storing the second fault event with the first fault event. In this way, the fault events stored in the controller's storage space are dynamically adjusted so that newly occurring fault events have sufficient storage space to limit the engine's output power in a timely manner, thus preventing environmental pollution caused by engine failure.

[0075] Optionally, in some possible implementations, the processing unit 220 is specifically configured to determine the second fault event from the plurality of fault events based on the storage priority parameter of each fault event among the plurality of fault events, wherein the second fault event is the fault event with the lowest storage priority parameter among the plurality of fault events, and the storage priority parameter represents the priority of the fault time.

[0076] Optionally, in some possible implementations, the processing unit 220 is specifically configured to determine at least one candidate fault event based on the plurality of fault events, wherein the fault event corresponding to the candidate fault event has ended; and to determine the second fault event from the at least one candidate fault event based on the storage priority parameter of each candidate fault event among the at least one candidate fault events.

[0077] Optionally, in some possible implementations, the processing unit 220 is further configured to determine a storage priority parameter for the first fault event based on the fault type corresponding to the first fault event; and adjust the storage priority parameter of the first fault event according to a priority decay parameter in response to the end of the first fault event. The priority decay parameter represents the relationship between the priority of the second fault event and time.

[0078] Optionally, in some possible implementations, the acquisition unit 210 is further configured to acquire the duration of the first fault event.

[0079] The processing unit 220 is further configured to determine that the first fault event occurs again; in response to the storage priority parameter of the first fault event not being equal to zero, to continue recording the duration of the first fault based on the duration of the first fault event.

[0080] This application also provides corresponding devices, computer storage media, and vehicles for implementing any of the fault storage methods provided in this application.

[0081] The device includes a memory and a processor. The memory is used to store instructions or code, and the processor is used to execute the instructions or code to cause the device to perform the fault storage method described in any embodiment of this application.

[0082] The computer storage medium stores code, and when the code is executed, the device running the code implements the fault storage method described in any embodiment of this application.

[0083] A vehicle includes an engine and a controller, the controller including a plurality of storage spaces for storing engine malfunction events, and the controller for adjusting the information stored in the plurality of storage spaces to implement the malfunction storage method described in any embodiment of this application.

[0084] In the embodiments of this application, the terms "first" and "second" (if they exist) are used only as name identifiers and do not represent the order of first and second.

[0085] As can be seen from the above description of the embodiments, those skilled in the art can clearly understand that all or part of the steps in the methods of the above embodiments can be implemented by means of software plus a general-purpose hardware platform. Based on this understanding, the technical solution of this application can be embodied in the form of a software product. This computer software product can be stored in a storage medium, such as a read-only memory (ROM) / RAM, magnetic disk, optical disk, etc., including several instructions to cause a computer device (which may be a personal computer, a server, or a network communication device such as a router) to execute the methods described in various embodiments or some parts of the embodiments of this application.

[0086] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on its differences from other embodiments. In particular, the apparatus embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0087] The above description is merely an exemplary implementation of this application and is not intended to limit the scope of protection of this application.

Claims

1. A method for fault storage, characterized in that, The method is applied to a vehicle controller, which includes multiple storage spaces, including: Obtain a first fault event, wherein the first fault event is a fault affecting the exhaust emissions of the vehicle engine; In response to the fact that each of the plurality of storage spaces stores a fault event, the priority of the fault events is measured by a storage priority parameter, and a second fault event is determined from the plurality of fault events stored in the plurality of storage spaces. The second fault event is the event with the lowest priority among the plurality of fault events. Each of the plurality of storage spaces is equipped with a counter, and the value of the counter represents the storage priority parameter of the fault event stored in the storage space corresponding to the counter. Measuring the priority of the fault event by the storage priority parameter includes: setting an initial storage priority parameter for the fault event when storing it in the storage space; maintaining the storage priority parameter of the fault event unchanged during the duration of the fault event; decreasing the storage priority parameter of the fault event after the fault event ends; and increasing the storage priority parameter of the fault event if a fault of the type corresponding to the fault event occurs again before the storage priority parameter decreases to zero. The first fault event is stored in the storage space corresponding to the second fault event.

2. The method according to claim 1, characterized in that, Determining the second fault event from the plurality of fault events stored in the plurality of storage spaces includes: Based on the storage priority parameter of each of the plurality of fault events, the second fault event is determined from the plurality of fault events. The second fault event is the fault event with the lowest storage priority parameter among the plurality of fault events, where the storage priority parameter represents the priority of the fault event.

3. The method according to claim 2, characterized in that, Determining the second fault event from the plurality of fault events based on the storage priority parameter of each fault event includes: Based on the plurality of fault events, at least one candidate fault event is determined, wherein the fault event corresponding to the candidate fault event has ended. The second fault event is determined from the at least one candidate fault events based on the storage priority parameter of each candidate fault event.

4. The method according to claim 2, characterized in that, The method further includes: Based on the fault type corresponding to the first fault event, determine the storage priority parameters of the first fault event; In response to the end of the first fault event, the storage priority parameter of the first fault event is adjusted according to the priority decay parameter, which represents the relationship between the priority of the second fault event and time.

5. The method according to any one of claims 2-4, characterized in that, The method further includes: Obtain the duration of the first fault event; It is determined that the first fault event has occurred again; In response to the storage priority parameter of the first fault event not being equal to zero, the duration of the first fault continues to be recorded based on the duration of the first fault event.

6. A fault storage device, characterized in that, The device is applied to a vehicle controller, the vehicle controller including multiple storage spaces, and the device includes: The acquisition unit is used to acquire a first fault event, wherein the first fault event is a fault affecting the exhaust emissions of the vehicle engine; A processing unit is configured to, in response to the fact that each of the plurality of storage spaces stores a fault event, measure the priority of the fault events using a storage priority parameter, and determine a second fault event from the plurality of fault events stored in the plurality of storage spaces, wherein the second fault event is the event with the lowest priority among the plurality of fault events; wherein each of the plurality of storage spaces is provided with a counter, the value of the counter representing the storage priority parameter of the fault event stored in the storage space corresponding to the counter; the step of measuring the priority of the fault event using the storage priority parameter includes: setting an initial storage priority parameter for the fault event when storing the fault event in the storage space; keeping the storage priority parameter of the fault event unchanged during the duration of the fault event; decreasing the storage priority parameter of the fault event after the fault event ends; and increasing the storage priority parameter of the fault event if a fault of the type corresponding to the fault event occurs again before the storage priority parameter decreases to zero. The processing unit is further configured to store the first fault event in the storage space corresponding to the second fault event.

7. The apparatus according to claim 6, characterized in that, The processing unit is specifically configured to determine the second fault event from the plurality of fault events based on the storage priority parameter of each fault event among the plurality of fault events, wherein the second fault event is the fault event with the lowest storage priority parameter among the plurality of fault events, and the storage priority parameter represents the priority of the fault event.

8. The apparatus according to claim 7, characterized in that, The processing unit is specifically configured to determine at least one candidate fault event based on the plurality of fault events, wherein the fault event corresponding to the candidate fault event has ended. The second fault event is determined from the at least one candidate fault events based on the storage priority parameter of each candidate fault event.

9. The apparatus according to claim 7, characterized in that, The processing unit is further configured to determine the storage priority parameter of the first fault event according to the fault type corresponding to the first fault event; and adjust the storage priority parameter of the first fault event according to the priority decay parameter in response to the end of the first fault event, wherein the priority decay parameter represents the relationship between the priority of the second fault event and time.

10. The apparatus according to any one of claims 6-9, characterized in that, The acquisition unit is further configured to acquire the duration of the first fault event; The processing unit is further configured to determine that the first fault event occurs again; in response to the storage priority parameter of the first fault event being non-zero, to continue recording the duration of the first fault based on the duration of the first fault event.

Images