A fault processing method and device, electronic equipment and storage medium
By constructing a fault handling action array to identify the fault location, fault handling at both the application layer and the underlying layer is realized. This solves the problem that existing technologies cannot simultaneously satisfy functional safety authentication at both the application layer and the underlying layer, thus improving the security and efficiency of fault handling.
Patent Information
- Application Number
- CN202411716860.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-11-27
- Publication Date
- 2025-10-24
- Estimated Expiration
- 2044-11-27
AI Technical Summary
Existing technologies cannot simultaneously meet the functional safety certification of both the application layer and the underlying layer of the vehicle controller software, resulting in the inability to effectively handle underlying faults and affecting the passing of the functional safety certification of the application layer.
By acquiring fault detection results, constructing a fault handling action array, identifying fault locations, and handling faults, fault handling can be achieved across the application layer and the underlying layer, ensuring the safety and effectiveness of the fault handling process.
It improves the safety and efficiency of fault handling, ensuring that faults can be handled comprehensively, safely, and effectively, and meeting the security authentication requirements of the application layer and the underlying layer.
Smart Images
Figure CN119536227B_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application relates to the technical field of fault processing, in particular to a fault processing method and device, electronic equipment and storage medium. BACKGROUND
[0002] The fault diagnosis of the vehicle controller software mainly includes four parts of fault detection, bottom layer fault, bottom layer fault processing and application layer fault processing. 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 only develops the application layer. Therefore, the functional safety certification is also only for the application layer, and the bottom layer certification is guaranteed by the supplier. In order to ensure the functional safety certification, not only the application layer needs to realize functional safety, but also the bottom layer needs to realize the corresponding level of functional safety.
[0003] Therefore, the fault diagnosis spans the application layer and the bottom layer, and the development and implementation of functional safety involve more fault detection and fault processing. However, the fault diagnosis method of the prior art cannot simultaneously satisfy the safety certification of the application layer and the bottom layer, especially for the functional safety of the bottom layer, which cannot be substantially guaranteed. The bottom layer cannot realize functional safety, which will affect the passing of the application layer functional safety certification, resulting in that the fault cannot be effectively processed. SUMMARY
[0004] The purpose of the present application is to provide a fault processing method, device, electronic equipment and storage medium, which can realize fault processing spanning the application layer and the bottom layer, ensure the safety during the fault processing process, and is not limited by the functional safety of the bottom layer, so as to improve the fault processing capability and provide protection for the all-round, safe and effective processing of faults.
[0005] In a first aspect, an embodiment of the present application provides a fault processing method, which comprises:
[0006] obtaining a fault detection result;
[0007] performing fault trigger detection according to the fault detection result to determine that the fault state is a triggered fault;
[0008] constructing a fault processing action array;
[0009] performing fault processing action identification on the fault state being the triggered fault according to the fault processing action array to obtain a fault position of the fault state being the triggered fault;
[0010] performing fault processing according to the fault position.
[0011] In the implementation process, after determining the triggered fault, the fault handling action array is constructed to identify the fault handling action of the fault, the specific position of the fault is accurately identified, the fault handling across the application layer and the bottom layer can be realized, the safety in the fault handling process is ensured, the function safety of the bottom layer is not limited, the fault handling capability can be improved, and the all-around, safe and effective fault handling is ensured.
[0012] Further, the step of determining that the fault state is a triggered fault according to the fault detection result 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] Determining that the fault state is a triggered fault according to the first array.
[0016] In the implementation process, the first array is constructed according to the application layer signal, and then the fault state is determined, so that whether the fault has been triggered can be effectively confirmed, the safety in the fault handling process of the application layer and the bottom layer is improved, and the fault handling efficiency is improved.
[0017] Further, the step of constructing the 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 fault ID sequence corresponding to the application layer signal;
[0020] Adding the fault ID sequence to the initial first array to obtain the first array. In the implementation process, the fault ID sequence corresponding to the application layer signal is added to the initial first array to obtain the first array, so that more application layer information is contained in the first array, the safety performance of the application layer in the fault handling can be improved, and the fault can be effectively handled.
[0021] Further, the step of determining that the fault state is a triggered fault according to the first array includes:
[0022] Determining whether there is a first array value corresponding to a fault ID in the first array is a first threshold value;
[0023] If yes, determining that the fault corresponding to the fault ID with the first array value being the first threshold value is a to-be-verified fault, and determining that the to-be-verified fault is the fault state of the triggered fault.
[0024] In the implementation process, the fault state is determined as a triggered fault according to the first array value of the fault ID, so that the fault information can be quickly and accurately obtained, and subsequent positioning of the fault is facilitated.
[0025] Further, the step of determining the to-be-verified fault as the fault state being triggered includes:
[0026] A second array is constructed, and the second array includes a fault trigger time, a fault recovery time, a fault trigger step and a fault recovery step corresponding to each fault in the fault detection result;
[0027] The fault trigger time, the fault recovery time, the fault trigger step and the fault recovery step in the second array are sequentially verified to obtain a fault state;
[0028] A fault state corresponding to the to-be-verified fault in the fault state is obtained;
[0029] If the value of the fault state of the to-be-verified fault is a second threshold value, the to-be-verified fault is determined as the fault state being triggered.
[0030] In the implementation process, the fault trigger time, the fault recovery time, the fault trigger step and the fault recovery step in the second array are verified, so that the specific information of the fault can be accurately obtained, the fault state can be confirmed, and the performance of fault processing can be improved.
[0031] Further, the step of constructing the fault processing action array includes:
[0032] A third array is constructed;
[0033] The third array is labeled according to a fault ID sequence to obtain the fault processing action array.
[0034] In the implementation process, the third array is labeled, so that the fault processing action of each fault can be accurately labeled, the safe processing of the fault is supported, and it is ensured that the fault can be safely and effectively processed.
[0035] Further, the step of identifying the fault state being triggered according to the fault processing action array to obtain a fault position of the fault state being triggered includes:
[0036] The fault processing action array is identified to obtain a fault processing action subarray corresponding to the fault state being triggered;
[0037] The labeled values in the fault processing action subarray are sequentially traversed, and if a labeled value is a third threshold value, the fault processing action is determined as a target fault processing action.
[0038] obtain a fault handling action signal of the target fault handling action;
[0039] determine the fault position corresponding to the fault handling action signal as the fault position of the triggered fault of the fault state.
[0040] In the implementation process, after identifying the fault handling action array, the fault handling action subarray of the specific fault is identified, so that the specific position of the fault can be quickly and accurately located, the timely processing of the fault is ensured, and the safety performance of the fault handling is improved.
[0041] In a second aspect, the embodiments of the present application further provide a fault handling device, which comprises:
[0042] The acquisition module is configured to acquire a fault detection result.
[0043] The detection module is configured to perform fault triggering detection according to the fault detection result, and determine that the fault state is a triggered fault.
[0044] The construction module is configured to construct a fault handling action array.
[0045] The identification module is configured to perform fault handling action identification on the triggered fault of the fault state according to the fault handling action array, and obtain a fault position of the triggered fault of the fault state.
[0046] The fault handling module is configured to perform fault handling according to the fault position.
[0047] In the implementation process, after determining the triggered fault, the fault handling action array is constructed to perform fault handling action identification on the fault, the specific position of the fault is accurately identified, the fault handling across the application layer and the bottom layer can be implemented, the safety in the fault handling process is ensured, the fault handling capability is improved, and the all-around, safe and effective processing of the fault is ensured.
[0048] In a third aspect, the embodiments of the present application provide an electronic device, which comprises a memory, a processor, and a computer program stored in the memory and capable of running on the processor, and the processor implements the steps of the method according to any one of the first aspect when executing the computer program.
[0049] In a fourth aspect, the embodiments of the present application provide a computer readable storage medium, and instructions are stored on the storage medium, and when the instructions run on a computer, the computer executes the method according to any one of the first aspect.
[0050] In a fifth aspect, the embodiments of the present application provide a computer program product, which, when running on a computer, causes the computer to execute the method according to any one of the first aspect.
[0051] Other features and advantages of the present disclosure will be set forth in the following description, and in part will be apparent from the description, or can be learned by practice of the present disclosure, or can be realized and attained by means of the techniques disclosed in the present disclosure.
[0052] The above and other aspects of the present application will become more apparent by describing in detail the embodiments thereof with reference to the attached drawings in which: BRIEF DESCRIPTION OF DRAWINGS
[0053] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following will briefly introduce the drawings needed to be used in the embodiments of the present application. It should be understood that the following drawings only show some embodiments of the present application, and therefore should not be regarded as limiting the scope. For those skilled in the art, other related drawings can also be obtained without creative labor.
[0054] Figure 1 The flowchart of the fault processing method provided by the embodiments of the present application is shown in
[0055] Figure 2 The structural composition schematic diagram of the fault processing device provided by the embodiments of the present application is shown in
[0056] Figure 3 The structural composition schematic diagram of the electronic device provided by the embodiments of the present application is shown in DETAILED DESCRIPTION
[0057] The technical solutions of the embodiments of the present application will be described below in combination 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, and therefore, once an item is defined in one drawing, it does not need to be further defined and explained in the subsequent drawings. Meanwhile, in the description of the present application, the terms "first", "second", etc. are only used for distinguishing description, and cannot be understood as indicating or implying relative importance.
[0059] The specific embodiments of the present application will be further described in detail below in combination with the drawings and embodiments. The following embodiments are used to illustrate the present application, but not to limit the scope of the present application.
[0060] Embodiment one
[0061] Figure 1 The flowchart of the fault processing method provided by the embodiments of the present application is shown in Figure 1As shown, the method comprises:
[0062] S1, obtaining a fault detection result;
[0063] S2, performing fault trigger detection according to the fault detection result to determine that the fault state is a triggered fault;
[0064] S3, constructing a fault handling action array;
[0065] S4, performing fault handling action identification on the fault state being the triggered fault according to the fault handling action array to obtain a fault position of the fault state being the triggered fault;
[0066] S5, performing fault handling according to the fault position.
[0067] In the implementation process described above, after determining the triggered fault, the fault handling action array is constructed to perform fault handling action identification on the fault, and the specific position of the fault is accurately identified, which can realize fault handling across the application layer and the bottom layer, ensure the safety in the fault handling process, is not limited to the functional safety of the bottom layer, and can improve the fault handling capability, thereby providing protection for the all-around, safe and effective handling of the fault.
[0068] In the embodiment of the present application, the fault detection result contains a plurality of diagnosed faults, and the number of faults is confirmed according to the Fault Diagnosis Requirement Table. For example, the number of faults in the embodiment of the present application is 281.
[0069] Further, S2 comprises:
[0070] Obtaining an application layer signal corresponding to each fault in the fault detection result;
[0071] Constructing a first array according to the application layer signal;
[0072] Determining the fault state being the triggered fault according to the first array.
[0073] In the implementation process described above, the first array is constructed according to the application layer signal, and then the fault state is determined, which can effectively confirm whether the fault has been triggered, improve the safety in the fault handling process of the application layer and the bottom layer, and improve the handling efficiency of the fault.
[0074] Further, the step of constructing the first array according to the application layer signal comprises:
[0075] Constructing an initial first array according to the number of faults in the fault detection result;
[0076] Obtaining a fault ID sequence corresponding to the application layer signal;
[0077] Adding the fault ID sequence to the initial first array to obtain the first array.
[0078] In the implementation process, the fault ID corresponding to the application layer signal is 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 order in the fault diagnosis requirement table, the application layer signal corresponding to the 281 faults is taken as the input of the control method, an initial first array with a dimension of 281 is created, and the application layer signal of the fault is stored in bErr according to the fault ID order in the table (the first array is represented by bErr in the embodiment of the application).
[0080] Further, the step of determining the fault state as the triggered fault according to the first array comprises:
[0081] determining whether the first array value corresponding to the fault ID exists in the first array is the first threshold value;
[0082] If yes, it is determined that the fault corresponding to the first threshold value of the first array value is the fault to be checked, and the fault to be checked is determined as the fault state triggered fault.
[0083] In the implementation process, the fault state triggered fault is determined according to the first array value of the fault ID, which can quickly and accurately obtain the information of the fault, and facilitate subsequent positioning.
[0084] For example, the fault ID order is ID=i, and the first array value bErr[i] corresponding to the fault ID order is 1 (the first threshold value), so it is determined as the fault state triggered fault. After detecting that the fault has been triggered, it needs to be further checked.
[0085] Further, the step of determining the fault to be checked as the fault state triggered fault comprises:
[0086] constructing a second array, the second array comprising the fault trigger time, the fault recovery time, the fault trigger step and the fault recovery step corresponding to each fault in the fault detection result;
[0087] sequentially checking the fault trigger time, the fault recovery time, the fault trigger step and the fault recovery step in the second array to obtain the fault state;
[0088] obtaining the fault state corresponding to the fault to be checked in the fault state;
[0089] If the value of the fault state of the fault to be checked is the second threshold value, it is determined that the fault to be checked is the fault state triggered fault.
[0090] In the implementation process, the fault trigger time, fault recovery time, fault trigger step and fault recovery step in the second array are checked, so that the specific information of the fault can be accurately obtained, the fault state can be confirmed, and the performance of fault processing can be improved.
[0091] A second array is created, which includes four sub-arrays with a dimension of 281, corresponding to the debounce values of 281 fault requirements in order of fault ID. The second array includes the fault trigger time FailThd (the debounce result is Failed if the debounce value is increased), the fault recovery time RecThd (the debounce result is Passed if the debounce value is reduced), the fault trigger step IncrFail (the value is increased in each running period), and the fault recovery step DecrRec (the value is reduced in each running period).
[0092] After the fault bErr[i] becomes 1, after checking, the checking of the embodiment of the application is the fault debounce processing, that is, the debounce processing, and the fault state bFailed[i] is set to 1 (the second threshold value). bFailed is a 281-dimensional array, which represents that the fault with the fault ID i is determined to be triggered after bErr[i] is checked.
[0093] Further, S3 includes:
[0094] A third array is constructed.
[0095] The third array is calibrated according to the order of fault ID to obtain a fault processing action array.
[0096] In the implementation process, the third array is calibrated, so that the fault processing action of each fault can be accurately calibrated, the safe processing of the fault is supported, and it is ensured that the fault can be safely and effectively processed.
[0097] A third array (noDfc2Fid array) is created, with a dimension of 2809, i.e. from noDfc2Fid[0]-noDfc2Fid
[2809] , which is divided into 281 calibrations in the order of fault ID, with 10 elements for each fault calibration, representing 281 faults, and 10 fault handling actions for each fault. The 281 calibrations are c-fh_noType0Fid_C-c-fh_noType280Fid_C. A variable N is set, with an initial value of 0, and N+10 every time i+1, N=10*i. A variable num is set, with an initial value of 0, num=10*(i+1), num represents the maximum dimension of the noDfc2Fid[N] array that can be retrieved by a certain fault bFailed[i]. Exemplarily, when the first fault i=0, num=10 and N=0 at this time, if bFailed[0]=1, representing that the fault is triggered, the maximum dimension of the noDfc2Fid array that can be retrieved by the fault bFailed[0] is 10, and the data retrieved in the noDfc2Fid is noDfc2Fid[N]-noDfc2Fid[N+9], i.e. noDfc2Fid[0]-noDfc2Fid[9], which is the calibration c-fh_noType0Fid_C.
[0098] Further, S4 comprises:
[0099] The fault handling action array is identified to obtain a fault handling action subarray corresponding to the fault whose fault state is triggered;
[0100] The calibration values in the fault handling action subarray are sequentially traversed, and if the calibration value is the third threshold, the fault handling action is determined as the target fault handling action;
[0101] The fault handling action signal of the target fault handling action is obtained;
[0102] The fault position corresponding to the fault handling action signal is determined as the fault position of the fault whose fault state is triggered.
[0103] In the above implementation process, after the fault handling action array is identified, the fault handling action subarray of the specific fault is identified, which can quickly and accurately locate the specific position of the fault, provide guarantee for timely processing of the fault, and improve the safety performance of fault handling.
[0104] After bFailed[i] is set to 1, the fault handling action corresponding to the fault needs to be determined, and the embodiments of the present application identify the specific fault position and the fault handling action through two loops.
[0105] The loop1 loop is set, and a sub-loop loop2 is set under the loop1 to find the fault handling action corresponding to the fault. The number of the loop1 loop is the total number of all faults 281. The number of the loop2 sub-loop is 10, representing that each fault corresponds to 10 fault handling actions.
[0106] Exemplarily, taking the fault bFailed[0] as an example, at this time, i = 0, num = 10, and N = 0. If bFailed[0] = 1, the fault is triggered, 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[0]-noDfc2Fid[9] these 10 numbers, that is, the calibration cfh_noType0Fid_C. Through the loop2 loop, the 10 numbers in cfh_noType0Fid_C are judged one by one, and the number that is not 0 (the third threshold value) indicates the fault handling action corresponding to the fault, and the number that is 0 represents no fault handling action.
[0107] The embodiment of the application is based on the existence of triggered faults. Alternatively, if no triggered fault is found, that is, bFailed[0] = 0, the fault is not triggered, there is no need to judge the fault handling action, i + 1, the next loop1 loop is performed, if bFailed[1], bFailed[2]…bFailed
[100] are all 0, i + 1 is continued, and the next loop1 loop is performed, until all faults are traversed.
[0108] Through the loop2 loop, the 10 numbers in cfh_noTypeiFid_C are judged one by one, and the number that is 0 represents no fault handling action and is not processed, and the number that is not 0 a is the number corresponding to the fault handling action of this fault, and the corresponding fault handling action signal cfh_XXX can be obtained by retrieving FID_base[a-1] through the fault handling action array FID_base.
[0109] In the embodiment of the application, the original faults and fault handling modes existing in the bottom layer of the vehicle controller are developed in the application layer of the vehicle controller, and the fault detection, bottom layer fault, bottom layer fault handling and application layer fault handling are all implemented through the application layer. All functions of fault diagnosis are retained, and the fault diagnosis function does not need to cross the application layer and the bottom layer. It is conducive to the safe development of the functions of the vehicle controller, and is not subject to the safety certification of the bottom layer.
[0110] Embodiment two
[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 implementation process, the fault ID corresponding to the application layer signal is 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 processing and ensure that the fault is effectively processed.
[0128] Further, the detection module 2 is further used to:
[0129] determine whether there is a first array value corresponding to the fault ID in the first array is a first threshold value;
[0130] If yes, it is determined that the fault corresponding to the first array value of the first threshold value is a fault to be verified, and the fault to be verified is a fault with a triggered fault state.
[0131] In the implementation process, the fault state of the fault with a triggered fault state is determined according to the first array value of the fault ID, which can quickly and accurately obtain the information of the fault, and facilitate subsequent positioning.
[0132] Further, the detection module 2 is further used to:
[0133] constructing a second array, the second array including the fault trigger time, the fault recovery time, the fault trigger step and the fault recovery step corresponding to each fault in the fault detection result;
[0134] sequentially verifying the fault trigger time, the fault recovery time, the fault trigger step and the fault recovery step in the second array to obtain the fault state;
[0135] obtaining the fault state corresponding to the fault to be verified in the fault state;
[0136] If the value of the fault state of the fault to be verified is a second threshold value, it is determined that the fault to be verified is a fault with a triggered fault state.
[0137] In the implementation process, the fault trigger time, the fault recovery time, the fault trigger step and the fault recovery step in the second array are verified, which can accurately obtain the specific information of the fault, facilitate the confirmation of the fault state, and improve the performance of fault processing.
[0138] Further, the construction module 3 is further used to:
[0139] constructing a third array;
[0140] labeling the third array according to the fault ID sequence to obtain a fault processing action array.
[0141] In the implementation process, the third array is labeled, which can accurately label the fault processing action of each fault, provide support for the safe processing of the fault, and ensure that the fault can be safely and effectively processed.
[0142] Further, the identification module 4 is also used for:
[0143] identifying the fault handling action array to obtain a fault handling action subarray corresponding to the fault whose fault state is triggered;
[0144] sequentially traversing the calibration values in the fault handling action subarray, and if the calibration value is the third threshold value, determining that the fault handling action is the target fault handling action;
[0145] obtaining a fault handling action signal of the target fault handling action;
[0146] determining that the fault position corresponding to the fault handling action signal is the fault position 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 subarray of the specific fault is identified, so that the specific position of the fault can be quickly and accurately located, the timely processing of the fault is guaranteed, and the safety performance of the fault handling is improved.
[0148] The fault handling device described above can implement the method of the above embodiment one. The options in the above embodiment one are also applicable to this embodiment, and will not be described in detail here.
[0149] The remaining content of the embodiment of the present application can refer to the content of the above embodiment one. In this embodiment, it will not be described in detail.
[0150] Embodiment three
[0151] The embodiment of the present application provides an electronic device, which comprises a memory and a processor. The memory is used for storing a computer program, and the processor runs the computer program to enable the electronic device to execute the fault handling method of the above embodiment one.
[0152] Optionally, the electronic device described above can be a server.
[0153] Please refer to Figure 3 , Figure 3 The electronic device provided by the embodiment of the present application is shown in the structural composition diagram. The electronic device can include a processor 31, a communication interface 32, a memory 33 and at least one communication bus 34. Wherein, the communication bus 34 is used to realize the direct connection communication of these components. Wherein, the communication interface 32 of the device in the embodiment of the present application is used for signaling or data communication with other node devices. The processor 31 can be an integrated circuit chip with signal processing capability.
[0154] The processor 31 can be a general 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, discrete gate or transistor logic, discrete hardware components. The disclosed methods, steps and logic block diagrams in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor 31 can also be any conventional processor.
[0155] The memory 33 can 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, which, when executed by the processor 31, enable the device to perform the above Figure 1 The method embodiments involve various steps.
[0156] Optionally, the electronic device can also include a storage controller, an input output unit. The memory 33, the storage controller, the processor 31, the peripheral interface, the input output unit are directly or indirectly electrically connected to each other to realize the transmission or interaction of data. For example, these elements can be electrically connected to each other through one or more communication buses 34. The processor 31 is configured to execute the executable modules stored in the memory 33, such as software function modules or computer programs included in the device.
[0157] The input output unit is configured to provide a user with a creation task and create a selectable period or a preset execution time for starting the task to realize the interaction between the user and the server. The input output unit can be, but is not limited to, a mouse and a keyboard, etc.
[0158] It can be understood that Figure 3 The structure shown is only schematic, and the electronic device can include more or less components than those shown in the Figure 3 or have a different configuration from that shown in the Figure 3 The components shown in the Figure 3 The components shown in the embodiments of the present application can be implemented in hardware, software or a combination thereof.
[0159] In addition, the embodiment of the present application further provides a computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement the fault processing method of the embodiment one.
[0160] The embodiment of the present application further provides a computer program product, which, when running on a computer, causes the computer to execute the method described in the method embodiment.
[0161] In several embodiments provided in the present application, it should be understood that the disclosed apparatus and method can also be implemented by other manners. The apparatus embodiment described above is only schematic, for example, the flow chart and block diagram in the drawings show the possible implementation architecture, function and operation of the apparatus, method and computer program product according to the embodiments of the present application. In this regard, each block in the flow chart or block diagram can represent a module, a program segment or a part of code, which contains one or more executable instructions for implementing the specified logic function. It should also be noted that, in some alternative implementation manners, the functions noted in the blocks can also occur in different order from that noted in the drawings. For example, two consecutive blocks can actually be executed substantially in parallel, and sometimes they can also be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and / or flow chart, and the combination of blocks in the block diagram and / or flow chart, can be implemented by a dedicated hardware-based device for executing the specified function or action, or can be implemented by a combination of special-purpose hardware and computer instructions.
[0162] In addition, each functional module in the embodiments 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 such understanding, the technical solutions of the present application can be embodied in the form of a software product, and the computer software product is stored in a storage medium, and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the embodiments of the present application. The foregoing storage medium includes: U disk, mobile hard disk, ROM, RAM, magnetic disk or optical disk, and various program codes that can be stored in the medium.
[0164] The above merely provides an example of the present application, and is not intended to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application. It should be noted that similar reference numerals and letters represent similar items in the following drawings, and thus, once an item is defined in one drawing, it need not be further defined and explained in subsequent drawings.
[0165] The above merely provides an example of the present application, and is not intended to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application. It should be noted that similar reference numerals and letters represent similar items in the following drawings, and thus, once an item is defined in one drawing, it need not be further defined and explained in subsequent drawings.
[0166] It should be noted that the relational terms herein such as first and second and the like are used solely to distinguish one from another entity or action without necessarily requiring or implying any actual relationship or order between such entities or actions. Moreover, the terms "comprises", "comprising", or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but can include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element proceeded by "comprises... a" does not, without more constraints, exclude the existence of additional identical elements in the process, method, article, or apparatus that comprises the element.
Claims
1. A failure handling method characterized by, The method comprises: obtaining a fault detection result; determining a fault state as a triggered fault according to fault trigger detection of the fault detection result, comprising: obtaining an application layer signal corresponding to each fault in the fault detection result; constructing an initial first array according to a fault number of the fault detection result; obtaining a fault ID sequence corresponding to the application layer signal; adding the fault ID sequence to the initial first array to obtain a first array; determining the fault state as the triggered fault according to the first array; constructing a fault handling action array, comprising: constructing a third array; labeling the third array according to a fault ID sequence to obtain the fault handling action array; identifying a fault handling action of the fault state as the triggered fault according to the fault handling action array to obtain a fault position of the fault state as the triggered fault, comprising: identifying the fault handling action array to obtain a fault handling action subarray corresponding to the fault state as the triggered fault; sequentially traversing labeled values in the fault handling action subarray, and if a labeled value is a third threshold value, determining that the fault handling action is a target fault handling action; obtaining a fault handling action signal of the target fault handling action; determining a fault position corresponding to the fault handling action signal as the fault position of the fault state as the triggered fault; performing fault handling according to the fault position.
2. The failure handling method according to claim 1, characterized by, The step of determining the fault state as the triggered fault according to the first array comprises: determining whether a first array value corresponding to a fault ID in the first array is a first threshold value; if yes, determining that a fault corresponding to the first array value as the first threshold value is a fault to be checked, and determining that the fault to be checked is the fault state as the triggered fault.
3. The failure handling method according to claim 2, characterized by, The step of determining that the fault to be checked is the fault state as the triggered fault comprises: constructing a second array, the second array comprising a fault trigger time, a fault recovery time, a fault trigger step and a fault recovery step corresponding to each fault in the fault detection result; sequentially checking the fault trigger time, the fault recovery time, the fault trigger step and the fault recovery step in the second array to obtain a fault state; obtaining a fault state corresponding to the fault to be checked in the fault state; if a value of the fault state of the fault to be checked is a second threshold value, determining that the fault to be checked is the fault state as the triggered fault.
4. A failure handling apparatus characterized by comprising: The device comprises: an obtaining module configured to obtain a fault detection result; a detection module configured to determine a fault state as a triggered fault according to fault trigger detection of the fault detection result, and further configured to obtain an application layer signal corresponding to each fault in the fault detection result, construct an initial first array according to a fault number of the fault detection result, obtain a fault ID sequence corresponding to the application layer signal, add the fault ID sequence to the initial first array to obtain a first array, and determine the fault state as the triggered fault according to the first array. The constructing module is configured to construct a fault handling action array, and to construct a third array, and to mark the third array according to a fault ID sequence to obtain the fault handling action array; The identifying module is configured to perform fault handling action identification on a fault whose state is triggered according to the fault handling action array to obtain a fault position of the fault whose state is triggered, and to identify the fault handling action array to obtain a fault handling action subarray corresponding to the fault whose state is triggered, and to sequentially traverse marked values in the fault handling action subarray, and if a marked value is a third threshold value, to determine that the fault handling action is a target fault handling action, to obtain a fault handling action signal of the target fault handling action, and to determine that a fault position corresponding to the fault handling action signal is the fault position of the fault whose state is triggered; The fault handling module is configured to perform fault handling according to the fault position.
5. An electronic device, comprising: The electronic device comprises a memory and a processor, the memory is configured to store a computer program, and the processor is configured to run the computer program to enable the electronic device to perform the fault handling method according to any one of claims 1 to 3.
6. A storage medium, characterized by The computer program is stored in the memory and is executed by the processor to implement the fault handling method according to any one of claims 1 to 3.
Citation Information
Patent Citations
Diagnostic parameter calibration method and device
CN115114171A
Vehicle fault monitoring method and device
CN115665185A