Fault processing method and device, electronic equipment and storage medium

Abstract

The invention provides a fault processing method and device, electronic equipment and a storage medium, and the method comprises the steps: obtaining a fault detection result; performing fault trigger detection according to the fault detection result, and determining a fault in a triggered state; constructing a fault processing action array; according to the fault processing action array, fault processing action identification is carried out on the fault with the fault state being triggered, and the fault position of the fault with the fault state being triggered is obtained; and performing fault processing according to the fault position. By implementing the application, the fault processing across the application layer and the bottom layer can be realized, the safety in the fault processing process and the function safety not limited by the bottom layer are ensured, the fault processing capability can be improved, and a guarantee is provided for the omnibearing, safe and effective processing of the fault.

Description

Technical Field

[0001] The present application relates to the technical field of fault handling, and in particular to a fault handling method, device, electronic device, and storage medium. Background Art

[0002] The fault diagnosis of the vehicle controller software mainly includes four parts: fault detection, bottom-level faults, bottom-level fault handling, and application-layer fault handling. The fault diagnosis function needs to span the application layer and the bottom layer. With the continuous advancement of application standards, the vehicle controller software is only developed at the application layer. Therefore, for functional safety certification, only the application layer is certified, and the bottom layer certification is guaranteed by the supplier. To ensure that the function can be safely certified, not only the application layer needs to achieve functional safety, but the bottom layer is also required to achieve the corresponding level of functional safety.

[0003] Therefore, fault diagnosis spans the application layer and the bottom layer, and the development and implementation of functional safety involve more fault detection and fault handling. However, the fault diagnosis methods of the existing technology cannot meet the safety certification of both the application layer and the bottom layer at the same time. In particular, the functional safety of the bottom layer cannot be substantially guaranteed. The inability of the bottom layer to achieve functional safety will affect the passing of the functional safety certification of the application layer, resulting in the inability to effectively handle faults. Summary of the Invention

[0004] The purpose of this application is to provide a fault handling method, device, electronic device and storage medium, which can realize fault handling across the application layer and the bottom layer, ensure the security of the fault handling process, are not limited by the functional safety of the bottom layer, can improve the fault handling capability, and provide guarantees for the comprehensive, safe and effective handling of faults.

[0005] In a first aspect, an embodiment of the present application provides a fault handling method, the method comprising:

[0006] Obtain fault detection results;

[0007] Performing fault trigger detection according to the fault detection result to determine that the fault state is a triggered fault;

[0008] Build an array of fault handling actions;

[0009] performing fault processing action identification on the fault whose fault status is triggered according to the fault processing action array to obtain a fault location of the fault whose fault status is triggered;

[0010] Perform fault processing according to the fault location.

[0011] In the above implementation process, after determining that a fault has been triggered, a fault handling action array is constructed to identify the fault handling action and accurately identify the specific location of the fault. This can achieve fault handling across the application layer and the underlying layer, ensuring security during the fault handling process without being restricted by the functional safety of the underlying layer. This can improve fault handling capabilities and provide guarantees for comprehensive, safe, and effective fault handling.

[0012] Furthermore, the step of performing fault trigger detection according to the fault detection result and determining that the fault state is a triggered fault includes:

[0013] Obtaining an application layer signal corresponding to each fault in the fault detection result;

[0014] constructing a first array according to the application layer signal;

[0015] The fault state is determined to be a triggered fault according to the first array.

[0016] In the above implementation process, the first array is constructed according to the application layer signal, and then the fault status is determined, which can effectively confirm whether the fault has been triggered, improve the security of the application layer and the bottom layer fault processing process, and improve the fault processing efficiency.

[0017] Furthermore, the step of constructing a first array according to the application layer signal includes:

[0018] constructing an initial first array according to the number of faults in the fault detection result;

[0019] Obtaining a sequence of fault IDs corresponding to the application layer signal;

[0020] The fault IDs are sequentially added to the initial first array to obtain the first array. In the above implementation process, the fault IDs corresponding to the application layer signals are sequentially added to the initial first array to obtain the first array, so that the first array contains more application layer information, which can improve the safety performance of the application layer in fault handling and ensure that the fault is effectively handled.

[0021] Furthermore, the step of determining the fault state as a triggered fault according to the first array includes:

[0022] Determine whether there is a first array value corresponding to the fault ID in the first array that is a first threshold;

[0023] If so, it is determined that the fault corresponding to the fault ID whose first array value is the first threshold is a fault to be checked, and the fault to be checked is determined to be a fault whose fault status is triggered.

[0024] In the above implementation process, the fault state is determined to be a triggered fault according to the first array value of the fault ID, so that the fault information can be obtained quickly and accurately, which is convenient for subsequent positioning.

[0025] Furthermore, the step of determining that the fault to be checked is a fault whose fault state is triggered includes:

[0026] Constructing a second array, the second array including the fault trigger time, fault recovery time, fault trigger step and fault recovery step corresponding to each fault in the fault detection result;

[0027] sequentially verifying the fault trigger time, the fault recovery time, the fault trigger step length, and the fault recovery step length in the second array to obtain a fault state;

[0028] Obtaining a fault state corresponding to the fault to be verified in the fault state;

[0029] If the fault state value of the fault to be checked is a second threshold, it is determined that the fault to be checked is a fault whose fault state is triggered.

[0030] In the above implementation process, by verifying the fault trigger time, fault recovery time, fault trigger step and fault recovery step in the second array, the specific information of the fault can be accurately obtained, which is convenient for confirming the fault status and improving the performance of fault handling.

[0031] Furthermore, the step of constructing a fault handling action array includes:

[0032] Construct the third array;

[0033] The third array is calibrated according to the sequence of the fault IDs to obtain the fault processing action array.

[0034] In the above implementation process, the third array is calibrated to accurately calibrate the fault handling action of each fault, provide support for safe handling of the fault, and ensure that the fault can be handled safely and effectively.

[0035] Furthermore, the step of performing a fault handling action identification on the fault whose fault status is triggered according to the fault handling action array to obtain the fault location of the fault whose fault status is triggered includes:

[0036] Identifying the fault handling action array to obtain a fault handling action sub-array corresponding to the fault whose fault status is triggered;

[0037] Sequentially traverse the calibration values ​​in the fault handling action sub-array, and if the calibration value is a third threshold, determine that the fault handling action is a target fault handling action;

[0038] Obtaining a fault handling action signal of the target fault handling action;

[0039] The fault location corresponding to the fault processing action signal is determined to be the fault location of the fault whose fault state is triggered.

[0040] In the above implementation process, after identifying the fault handling action array, the fault handling action sub-array of the specific fault is then identified, which can quickly and accurately locate the specific location of the fault, provide a guarantee for timely handling of the fault, and at the same time improve the safety performance of fault handling.

[0041] In a second aspect, an embodiment of the present application further provides a fault handling device, the device comprising:

[0042] An acquisition module is used to obtain fault detection results;

[0043] A detection module, configured to perform fault trigger detection based on the fault detection result and determine that the fault state is a triggered fault;

[0044] Building module, used to build fault handling action array;

[0045] an identification module, configured to identify a fault processing action for the fault whose fault status is triggered according to the fault processing action array, and obtain a fault location of the fault whose fault status is triggered;

[0046] The fault processing module is used to perform fault processing according to the fault location.

[0047] In the above implementation process, after determining that a fault has been triggered, a fault handling action array is constructed to identify the fault handling action and accurately identify the specific location of the fault. This can achieve fault handling across the application layer and the underlying layer, ensuring security during the fault handling process without being restricted by the functional safety of the underlying layer. This can improve fault handling capabilities and provide guarantees for comprehensive, safe, and effective fault handling.

[0048] In a third aspect, an embodiment of the present application provides an electronic device, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the method described in any one of the first aspects when executing the computer program.

[0049] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which instructions are stored. When the instructions are executed on a computer, the computer executes the method as described in any one of the first aspects.

[0050] In a fifth aspect, an embodiment of the present application provides a computer program product, which, when running on a computer, enables the computer to execute the method as described in any one of the first aspects.

[0051] Other features and advantages of the present disclosure will be set forth in the following description, or some features and advantages may be inferred or unambiguously determined from the description, or may be learned by practicing the above-mentioned technology of the present disclosure.

[0052] It can be implemented according to the contents of the specification. The following is a detailed description of the preferred embodiments of the present application with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments of the present application. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the range values. For ordinary technicians in this field, other relevant drawings can be obtained based on these drawings without creative work.

[0054] Figure 1 A flowchart of a troubleshooting method provided in an embodiment of the present application;

[0055] Figure 2 A schematic diagram of the structure of the fault handling device provided in an embodiment of the present application;

[0056] Figure 3 A schematic diagram of the structural composition of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0057] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0058] It should be noted that similar reference numerals and letters represent similar items in the following drawings. Therefore, once an item is defined in one drawing, it does not need to be further defined or explained in subsequent drawings. At the same time, in the description of this application, the terms "first", "second", etc. are only used to distinguish the description and should not be understood as indicating or implying relative importance.

[0059] The following embodiments are used to illustrate the present invention, but are not intended to limit the scope of the present invention.

[0060] Example 1

[0061] Figure 1 This is a flowchart of the troubleshooting method provided by the embodiment of the present application. Figure 1As shown, the method includes:

[0062] S1, obtain fault detection results;

[0063] S2, performing fault trigger detection based on the fault detection result, and determining that the fault state is a triggered fault;

[0064] S3, build fault handling action array;

[0065] S4, performing a fault processing action identification on the fault whose fault status is triggered according to the fault processing action array, and obtaining the fault location of the fault whose fault status is triggered;

[0066] S5: Perform fault processing according to the fault location.

[0067] In the above implementation process, after determining that a fault has been triggered, a fault handling action array is constructed to identify the fault handling action and accurately identify the specific location of the fault. This can achieve fault handling across the application layer and the underlying layer, ensuring security during the fault handling process without being restricted by the functional safety of the underlying layer. This can improve fault handling capabilities and provide guarantees for comprehensive, safe, and effective fault handling.

[0068] In an embodiment of the present application, the fault detection result includes multiple diagnosed faults, and the number of faults is confirmed according to the "Fault Diagnosis Requirements Table". For example, the number of faults in the embodiment of the present application is 281.

[0069] Furthermore, S2 includes:

[0070] Obtain the application layer signal corresponding to each fault in the fault detection result;

[0071] constructing a first array according to the application layer signal;

[0072] The fault state is determined to be a triggered fault according to the first array.

[0073] In the above implementation process, the first array is constructed according to the application layer signal, and then the fault status is determined, which can effectively confirm whether the fault has been triggered, improve the security of the application layer and the bottom layer fault processing process, and improve the fault processing efficiency.

[0074] Furthermore, the step of constructing the first array according to the application layer signal includes:

[0075] constructing an initial first array according to the number of faults in the fault detection result;

[0076] Get the fault ID sequence corresponding to the application layer signal;

[0077] The fault IDs are sequentially added to the initial first array to obtain the first array.

[0078] In the above implementation process, the fault IDs corresponding to the application layer signals are sequentially added to the initial first array to obtain the first array, so that the first array contains more application layer information, which can improve the safety performance of the application layer in fault handling and ensure that the fault is effectively handled.

[0079] According to the fault ID sequence in the fault diagnosis requirement table, the application layer signals corresponding to the 281 faults are used as the input of the control method, an initial first array with a dimension of 281 is created, and the application layer signals of the faults are stored in bErr according to the fault ID sequence in the table (the embodiment of the present application uses bErr to represent the first array).

[0080] Furthermore, the step of determining the fault state as a triggered fault according to the first array includes:

[0081] Determine whether there is a first array value corresponding to the fault ID in the first array that is a first threshold;

[0082] If so, it is determined that the fault corresponding to the fault ID whose first array value is the first threshold is a fault to be checked, and the fault to be checked is determined to be a fault whose fault status is triggered.

[0083] In the above implementation process, the fault state is determined to be a triggered fault according to the first array value of the fault ID, so that the fault information can be obtained quickly and accurately, which is convenient for subsequent positioning.

[0084] For example, if the first array value bErr[i] of a fault with fault ID sequence ID=i becomes 1 (first threshold), it is determined to be a fault with a triggered fault state. After detecting that a fault has been triggered, further verification is required.

[0085] Furthermore, the step of determining that the fault to be checked is a fault whose fault state is triggered includes:

[0086] Constructing a second array, the second array including the fault trigger time, fault recovery time, fault trigger step length, and fault recovery step length corresponding to each fault in the fault detection result;

[0087] sequentially verifying the fault trigger time, fault recovery time, fault trigger step length, and fault recovery step length in the second array to obtain a fault state;

[0088] Obtain the fault status corresponding to the fault to be checked in the fault status;

[0089] If the value of the fault state of the fault to be checked is the second threshold, it is determined that the fault to be checked is a fault whose fault state is triggered.

[0090] In the above implementation process, by verifying the fault trigger time, fault recovery time, fault trigger step and fault recovery step in the second array, the specific information of the fault can be accurately obtained, which is convenient for confirming the fault status and improving the performance of fault handling.

[0091] Create a second array containing four sub-arrays with a dimension of 281. The sub-arrays correspond to the debounce values ​​required by the 281 faults in order of fault ID. The second array contains the fault trigger time FailThd (if it increases to the debounce value, the debounce result is Failed), the fault recovery time RecThd (if it decreases to the debounce value, the debounce result is Passed), the fault trigger step IncrFail (the value that increases in each operating cycle), and the fault recovery step DecrRec (the value that decreases in each operating cycle).

[0092] After the fault bErr[i] becomes 1, after verification, the verification in the embodiment of the present application is fault debounce processing, that is, debounce processing, and the fault status bFailed[i] will be set to 1 (second threshold value). bFailed is a 281-dimensional array, which means that after bErr[i] is verified, the fault with fault ID i is determined to be triggered.

[0093] Furthermore, S3 includes:

[0094] Construct the third array;

[0095] The third array is calibrated according to the fault ID sequence to obtain a fault processing action array.

[0096] In the above implementation process, the third array is calibrated to accurately calibrate the fault handling action of each fault, provide support for safe handling of the fault, and ensure that the fault can be handled safely and effectively.

[0097] Create a third array (noDfc2Fid array) with 2809 dimensions. This array is separated by 281 labels, from noDfc2Fid[0] to noDfc2Fid

[2809] , in order of fault ID. Each label has 10 elements, representing 281 faults, each corresponding to 10 fault handling actions. The 281 labels are cfh_noType0Fid_C - cfh_noType280Fid_C. Set the variable N to 0 initially. For every i+1, N+10, N=10*i. Set the variable num to 0 initially. num=10*(i+1). num represents the maximum dimension in the noDfc2Fid[N] array that can be retrieved for a particular fault bFailed[i]. For example, when the first fault i=0, num=10, N=0, if bFailed[0]=1, it means that the fault is triggered, then the maximum dimension of the noDfc2Fid array that can be retrieved by the fault bFailed[0] is 10, and the data in the retrieved noDfc2Fid is noDfc2Fid[N]-noDfc2Fid[N+9], that is, noDfc2Fid[0]-noDfc2Fid[9], which is the calibration cfh_noType0Fid_C.

[0098] Furthermore, S4 includes:

[0099] Identify the fault handling action array and obtain the fault handling action sub-array corresponding to the fault whose fault status is triggered;

[0100] Traversing the calibration values ​​in the fault handling action sub-array in sequence, and if the calibration value is a third threshold, determining that the fault handling action is a target fault handling action;

[0101] Obtaining a fault handling action signal of a target fault handling action;

[0102] The fault location corresponding to the fault processing action signal is determined to be the fault location of the fault whose fault state is triggered.

[0103] In the above implementation process, after identifying the fault handling action array, the fault handling action sub-array of the specific fault is then identified, which can quickly and accurately locate the specific location of the fault, provide a guarantee for timely handling of the fault, and at the same time improve the safety performance of fault handling.

[0104] After bFailed[i] is set to 1, it is necessary to determine the fault handling action corresponding to the fault. In the embodiment of the present application, two loops are set to identify the specific fault location and fault handling action.

[0105] By setting up loop1 and sub-loop loop2 within loop1, find the fault handling action corresponding to the fault. The number of loops in loop1 is equal to the total number of faults, 281. The number of sub-loops in loop2 is 10, indicating that each fault corresponds to 10 fault handling actions.

[0106] For example, taking the fault bFailed[0] as an example, at this time i=0, num=10, N=0, if bFailed[0]=1, it means that the fault is triggered, then the maximum dimension of the noDfc2Fid array that can be retrieved by the fault bFailed[0] is 10, and the data retrieved in noDfc2Fid are the 10 numbers noDfc2Fid[0]-noDfc2Fid[9], which are the calibration cfh_noType0Fid_C. Through loop2, the 10 values ​​in cfh_noType0Fid_C are judged one by one. The number that is not 0 (the third threshold) indicates the fault processing action corresponding to the fault, and the number that is 0 indicates no fault processing action.

[0107] The embodiment of the present application is based on the existence of a triggered fault. Optionally, if no triggered fault is found, that is, bFailed[0]=0, it means that the fault is not triggered, then there is no need to determine the fault handling action, i+1, proceed to the next cycle of loop1, if bFailed[1], bFailed[2]...bFailed

[100] are all 0, then continue i+1, proceed to the next cycle of loop1, until all faults are traversed.

[0108] Through loop2, the 10 values ​​in cfh_noTypeiFid_C are judged one by one. The number 0 means no fault handling action and no processing is performed. The number a that is not 0 is the number of the fault handling action corresponding to this fault. Through the fault handling action array FID_base, search FID_base[a-1] to obtain the corresponding fault handling action signal cfh_XXX.

[0109] In the embodiments of this application, faults and fault handling methods originally associated with the vehicle controller's underlying layer are developed at the vehicle controller's application layer. Fault detection, underlying faults, underlying fault handling, and application-layer fault handling are all implemented at the application layer. This preserves all fault diagnosis functionality while eliminating the need for fault diagnosis across both the application and underlying layers. This facilitates the secure development of vehicle controller functions, freeing them from the constraints of underlying security certification.

[0110] Example 2

[0111] In order to execute the method corresponding to the above embodiment 1 to achieve the corresponding functions and technical effects, a fault handling device is provided below, such as Figure 2 As shown, the device includes:

[0112] Acquisition module 1, used to obtain fault detection results;

[0113] Detection module 2, used to perform fault trigger detection according to the fault detection result and determine that the fault state is a triggered fault;

[0114] Building module 3, used to build a fault handling action array;

[0115] Identification module 4, used for identifying the fault processing action of the fault whose fault status is triggered according to the fault processing action array, and obtaining the fault location of the fault whose fault status is triggered;

[0116] The fault processing module 5 is used to process the fault according to the fault location.

[0117] In the above implementation process, after determining that a fault has been triggered, a fault handling action array is constructed to identify the fault handling action and accurately identify the specific location of the fault. This can achieve fault handling across the application layer and the underlying layer, ensuring security during the fault handling process without being restricted by the functional safety of the underlying layer. This can improve fault handling capabilities and provide guarantees for comprehensive, safe, and effective fault handling.

[0118] Furthermore, the detection module 2 is further configured to:

[0119] Obtain the application layer signal corresponding to each fault in the fault detection result;

[0120] constructing a first array according to the application layer signal;

[0121] The fault state is determined to be a triggered fault according to the first array.

[0122] In the above implementation process, the first array is constructed according to the application layer signal, and then the fault status is determined, which can effectively confirm whether the fault has been triggered, improve the security of the application layer and the bottom layer fault processing process, and improve the fault processing efficiency.

[0123] Furthermore, the detection module 2 is further configured to:

[0124] constructing an initial first array according to the number of faults in the fault detection result;

[0125] Get the fault ID sequence corresponding to the application layer signal;

[0126] The fault IDs are sequentially added to the initial first array to obtain the first array.

[0127] In the above implementation process, the fault IDs corresponding to the application layer signals are sequentially added to the initial first array to obtain the first array, so that the first array contains more application layer information, which can improve the safety performance of the application layer in fault handling and ensure that the fault is effectively handled.

[0128] Furthermore, the detection module 2 is further configured to:

[0129] Determine whether there is a first array value corresponding to the fault ID in the first array that is a first threshold;

[0130] If so, it is determined that the fault corresponding to the fault ID whose first array value is the first threshold is a fault to be checked, and the fault to be checked is determined to be a fault whose fault status is triggered.

[0131] In the above implementation process, the fault state is determined to be a triggered fault according to the first array value of the fault ID, so that the fault information can be obtained quickly and accurately, which is convenient for subsequent positioning.

[0132] Furthermore, the detection module 2 is further configured to:

[0133] Constructing a second array, the second array including the fault trigger time, fault recovery time, fault trigger step length, and fault recovery step length corresponding to each fault in the fault detection result;

[0134] sequentially verifying the fault trigger time, fault recovery time, fault trigger step length, and fault recovery step length in the second array to obtain a fault state;

[0135] Obtain the fault status corresponding to the fault to be checked in the fault status;

[0136] If the value of the fault state of the fault to be checked is the second threshold, it is determined that the fault to be checked is a fault whose fault state is triggered.

[0137] In the above implementation process, by verifying the fault trigger time, fault recovery time, fault trigger step and fault recovery step in the second array, the specific information of the fault can be accurately obtained, which is convenient for confirming the fault status and improving the performance of fault handling.

[0138] Furthermore, building block 3 is also used to:

[0139] Construct the third array;

[0140] The third array is calibrated according to the fault ID sequence to obtain a fault processing action array.

[0141] In the above implementation process, the third array is calibrated to accurately calibrate the fault handling action of each fault, provide support for safe handling of the fault, and ensure that the fault can be handled safely and effectively.

[0142] Furthermore, the identification module 4 is further configured to:

[0143] Identify the fault handling action array and obtain the fault handling action sub-array corresponding to the fault whose fault status is triggered;

[0144] Traversing the calibration values ​​in the fault handling action sub-array in sequence, and if the calibration value is a third threshold, determining that the fault handling action is a target fault handling action;

[0145] Obtaining a fault handling action signal of a target fault handling action;

[0146] The fault location corresponding to the fault processing action signal is determined to be the fault location of the fault whose fault state is triggered.

[0147] In the above implementation process, after identifying the fault handling action array, the fault handling action sub-array of the specific fault is then identified, which can quickly and accurately locate the specific location of the fault, provide a guarantee for timely handling of the fault, and at the same time improve the safety performance of fault handling.

[0148] The above-mentioned fault handling device can implement the method of the above-mentioned embodiment 1. The optional items in the above-mentioned embodiment 1 are also applicable to this embodiment and will not be described in detail here.

[0149] The rest of the contents of the embodiment of this application can refer to the contents of the above-mentioned embodiment 1, and will not be repeated in this embodiment.

[0150] Example 3

[0151] An embodiment of the present application provides an electronic device, including a memory and a processor, wherein the memory is used to store a computer program, and the processor runs the computer program to enable the electronic device to execute the fault handling method of embodiment 1.

[0152] Optionally, the above-mentioned electronic device may be a server.

[0153] See Figure 3 , Figure 3 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. The electronic device may include a processor 31, a communication interface 32, a memory 33, and at least one communication bus 34. The communication bus 34 is used to enable direct communication between these components. The communication interface 32 of the device in the embodiment of the present application is used to communicate signaling or data with other node devices. The processor 31 may be an integrated circuit chip with signal processing capabilities.

[0154] The processor 31 can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. It can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of this application. A general-purpose processor can be a microprocessor, or the processor 31 can also be any conventional processor.

[0155] The memory 33 may be, but is not limited to, a random access memory (RAM), a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), etc. The memory 33 stores computer-readable instructions. When the computer-readable instructions are executed by the processor 31, the device can perform the above-mentioned operations. Figure 1 The various steps involved in the method embodiment.

[0156] Optionally, the electronic device may further include a memory controller and an input / output unit. The memory 33, memory controller, processor 31, peripheral interface, and input / output unit are electrically connected to each other, directly or indirectly, to enable data transmission or interaction. For example, these components may be electrically connected to each other via a communication bus 34. The processor 31 is configured to execute executable modules stored in the memory 33, such as software function modules or computer programs included in the device.

[0157] The input and output unit is used to provide users with the ability to create tasks and to create optional start time periods or preset execution times for the tasks to enable interaction between the user and the server. The input and output unit can be, but is not limited to, a mouse and keyboard.

[0158] I understand. Figure 3 The structure shown is only for illustration, and the electronic device may also include Figure 3 More or fewer components than shown, or with Figure 3 Different configurations shown. Figure 3 Each component shown in the figure can be implemented by hardware, software or a combination thereof.

[0159] In addition, an embodiment of the present application further provides a computer-readable storage medium storing a computer program, which implements the fault handling method of embodiment 1 when executed by a processor.

[0160] An embodiment of the present application further provides a computer program product, which, when running on a computer, enables the computer to execute the method described in the method embodiment.

[0161] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can also be implemented in other ways. The device embodiments described above are merely illustrative. For example, the flowcharts and block diagrams in the accompanying drawings show the possible architectures, functions and operations of the devices, methods and computer program products according to the multiple embodiments of the present application. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a portion of code, and the module, program segment or a portion of code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in an order different from that marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of boxes in the block diagram and / or flowchart, can be implemented using a dedicated hardware-based device that performs the specified function or action, or can be implemented using a combination of dedicated hardware and computer instructions.

[0162] In addition, the functional modules in each embodiment of the present application can be integrated together to form an independent part, or each module can exist independently, or two or more modules can be integrated to form an independent part.

[0163] If the functions are implemented in the form of software function modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

[0164] The foregoing is merely an embodiment of the present application and is not intended to limit the scope of protection of the present application. For those skilled in the art, the present application may have various modifications and variations. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application should be included within the scope of protection of the present application. It should be noted that similar numbers and letters represent similar items in the following figures. Therefore, once an item is defined in one figure, it does not need to be further defined or explained in subsequent figures.

[0165] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included within the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

[0166] It should be noted that, in this document, relational terms such as first and second, etc., are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply the existence of any such actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or device comprising the element.

Claims

1. A fault handling method, characterized in that: The method comprises: Obtain fault detection results; Performing fault trigger detection according to the fault detection result to determine that the fault state is a triggered fault; Build an array of fault handling actions; performing fault processing action identification on the fault whose fault status is triggered according to the fault processing action array to obtain the fault location of the fault whose fault status is triggered; Fault processing is performed according to the fault location.

2. The fault handling method according to claim 1, characterized in that: The step of performing fault trigger detection according to the fault detection result and determining that the fault state is a triggered fault includes: Obtaining an application layer signal corresponding to each fault in the fault detection result; constructing a first array according to the application layer signal; The fault state is determined to be a triggered fault according to the first array.

3. The fault handling method according to claim 2, characterized in that: The step of constructing a first array according to the application layer signal comprises: Constructing an initial first array according to the number of faults in the fault detection result; Obtaining a fault ID sequence corresponding to the application layer signal; The fault IDs are sequentially added to the initial first array to obtain the first array.

4. The fault handling method according to claim 2, characterized in that: The step of determining the fault state as a triggered fault according to the first array comprises: Determine whether there is a first array value corresponding to the fault ID in the first array that is a first threshold; If so, determine that the fault corresponding to the fault ID whose first array value is the first threshold is a fault to be checked, and determine that the fault to be checked is a fault whose fault state is triggered.

5. The fault handling method according to claim 4, characterized in that: The step of determining that the fault to be checked is a fault whose fault state is triggered includes: Constructing a second array, the second array including a fault trigger time, a fault recovery time, a fault trigger step length, and a fault recovery step length corresponding to each fault in the fault detection result; sequentially verifying the fault trigger time, the fault recovery time, the fault trigger step length, and the fault recovery step length in the second array to obtain a fault state; Obtaining a fault state corresponding to the fault to be verified in the fault state; If the value of the fault state of the fault to be checked is a second threshold, it is determined that the fault to be checked is a fault whose fault state is triggered.

6. The fault handling method according to claim 1, characterized in that: The step of constructing a fault handling action array includes: Construct the third array; The third array is calibrated according to the sequence of fault IDs to obtain the fault processing action array.

7. The fault handling method according to claim 1, characterized in that: The step of performing a fault processing action identification on the fault whose fault status is triggered according to the fault processing action array to obtain the fault location of the fault whose fault status is triggered includes: Identify the fault processing action array to obtain a fault processing action sub-array corresponding to the fault whose fault status is triggered; Traversing the calibration values ​​in the fault handling action sub-array in sequence, and if the calibration value is a third threshold, determining that the fault handling action is a target fault handling action; Obtaining a fault handling action signal of the target fault handling action; The fault position corresponding to the fault processing action signal is determined to be the fault position of the fault triggered by the fault state.

8. A fault handling device, characterized in that: The device comprises: An acquisition module, used to obtain fault detection results; A detection module, used to perform fault trigger detection according to the fault detection result, and determine that the fault state is a triggered fault; Building module, used to build fault handling action array; an identification module, configured to identify the fault whose fault status is triggered according to the fault processing action array, and obtain the fault position of the fault whose fault status is triggered; The fault processing module is used to perform fault processing according to the fault location.

9. An electronic device, characterized in that: The electronic device comprises a memory and a processor, wherein the memory is used to store a computer program, and the processor runs the computer program to enable the electronic device to execute the fault handling method according to any one of claims 1 to 7.

10. A storage medium, characterized in that: It stores a computer program, which, when executed by a processor, implements the fault handling method as claimed in any one of claims 1 to 7.

Images