Fault management method, device, equipment, medium and product
By obtaining and updating the initialization structure and fault information of each fault category, and generating and sending target fault information, the problem of false alarms and fault levels in traditional fault management methods is solved, and efficient fault management is achieved, suitable for the whole vehicle fault management at level and complex assembly levels.
Patent Information
- Application Number
- CN202411577189.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-11-06
- Publication Date
- 2025-02-07
AI Technical Summary
Traditional fault management methods are prone to false alarms, fault levels do not correspond to vehicle failures, and sudden failure protection strategies, resulting in low fault management efficiency.
By obtaining the fault information reported by each component within the initialization structure corresponding to each fault category and the preset time interval, using the preset fault attribute structure and each fault information, various variables in the initialization structure are updated and processed using the preset fault attribute structure and each fault information. , obtain the target failure information and send it to the upper computer for the upper computer to troubleshoot based on the target failure information.
The integrated screening of fault information of various parts in the vehicle is achieved, and the fault categories and information that may affect the vehicle are obtained. The attribute configuration parameters are rich and the fault management is flexible, which can effectively improve the fault management efficiency and is suitable for the vehicle level and Complex assembly-level fault management.
Smart Images
Figure CN119396126A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of fault management technology, and in particular to a fault management method, apparatus, device, medium, and product. Background Art
[0002] A vehicle failure refers to a weakened or lost function of a vehicle component, assembly, or entire vehicle. A minor vehicle failure can result in limited or no function, causing the vehicle to stop operating. Severe failures can cause the vehicle to lose stability or braking, leading to a serious traffic accident.
[0003] The fault management method in traditional technology is to use each component to evaluate its own fault level and report the evaluated fault level to the host computer, which then determines the fault handling strategy based on the fault level of each component.
[0004] However, traditional fault management methods are prone to problems such as false alarms, fault levels not corresponding to vehicle faults, and abrupt fault protection strategies, resulting in low fault management efficiency. Summary of the Invention
[0005] Based on this, it is necessary to provide a fault management method, device, equipment, medium and product that can improve management efficiency in response to the above technical problems.
[0006] In a first aspect, the present application provides a fault management method, the method comprising:
[0007] Obtain the initialization structure corresponding to each fault category and the fault information reported by each component within the preset time interval;
[0008] Using the preset fault attribute structure and each fault information, the variables in the initialization structure are updated to obtain target fault intelligence, which includes a target count array, a target suspicious parameter array, a target mode number array, and a target display information array;
[0009] The target fault information is sent to the host computer for the host computer to handle the fault based on the target fault information.
[0010] In one embodiment, the method further comprises:
[0011] For each initialization structure, the fault validity is judged based on the fault information, and the fault validity flag corresponding to the initialization structure is obtained;
[0012] For an initialization structure whose fault validity flag is valid, a process is performed to update various variables in the initialization structure using a preset fault attribute structure and various fault information to obtain target fault information.
[0013] In one embodiment, the method provides a process of updating various variables in an initialization structure with a fault validity flag set as valid using a preset fault attribute structure and various fault information to obtain target fault information, including:
[0014] Perform counting statistics on the initial count variables in the initialization structure to obtain fault count data corresponding to the initialization structure;
[0015] Perform level judgment on the fault information to obtain the initial fault level corresponding to the fault information;
[0016] Based on the fault attribute structure and the initial fault level, the variables in the initialization structure are updated to obtain the initial fault information;
[0017] The target fault information is obtained according to the fault count data and initial fault information corresponding to each initialization structure.
[0018] In one embodiment, the initial fault information in the provided method includes: a suspicious parameter number, a fault mode number, and fault display information; the process of obtaining target fault information based on the fault count data corresponding to each initialization structure and the initial fault information in the provided method includes:
[0019] Generate a fault count array, a suspicious parameter number array, a fault mode number array, and a fault display information array according to the fault count data and initial fault information corresponding to each initialized structure;
[0020] Sorting the fault display information array according to a preset sorting rule to obtain a target display information array;
[0021] Based on the target display information array, the fault count array, the suspicious parameter number array, and the fault mode number array are sorted respectively to obtain a target count array, a target suspicious parameter array, and a target mode number array.
[0022] In one embodiment, the initial fault information in the provided method includes a fault reward and punishment mode and a reward and punishment degree value corresponding to the fault reward and punishment mode, and the method further includes:
[0023] Based on the fault reward and punishment mode and the reward and punishment degree value, reward and punishment reference information is generated and sent to the host computer.
[0024] In one embodiment, the provided method further includes: when the fault valid flag is invalid, ignoring the fault information corresponding to the fault valid flag.
[0025] In a second aspect, the present application further provides a fault management device, comprising:
[0026] The information acquisition module is used to obtain the initialization structure corresponding to each fault category and the fault information reported by each component within a preset time interval;
[0027] An intelligence generation module is used to update various variables in the initialization structure using a preset fault attribute structure and various fault information to obtain target fault intelligence, which includes a target count array, a target suspicious parameter array, a target mode number array, and a target display information array;
[0028] The intelligence sending module is used to send the target fault intelligence to the host computer so that the host computer can perform fault processing based on the target fault intelligence.
[0029] In a third aspect, the present application further provides a computer device comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the method of the first aspect when executing the computer program.
[0030] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, which implements the steps of the method of the first aspect when the computer program is executed by a processor.
[0031] In a fifth aspect, the present application further provides a computer program product, comprising a computer program, which implements the steps of the method of the first aspect when executed by a processor.
[0032] The above-mentioned fault management methods, devices, equipment, media and products, on one hand, provide a fault management method including obtaining the initialization structure corresponding to each fault category and the fault information reported by each component within a preset time interval; using the preset fault attribute structure and each fault information, updating and processing each variable in the initialization structure to obtain target fault intelligence, the target fault intelligence including the target count array, the target suspicious parameter array, the target mode number array and the target display information array; sending the target fault intelligence to the host computer for the host computer to perform fault processing based on the target fault intelligence. In this way, the fault information reported by each component in the vehicle can be integrated and screened to obtain the fault category that may affect the entire vehicle and the fault information corresponding to the fault category. The attribute configuration parameters are rich and the fault management is flexible, which can realize the active management of the entire vehicle fault, has a good effect on the fault management of the entire vehicle level and the complex assembly level, and can effectively improve the efficiency of fault management. BRIEF DESCRIPTION OF THE DRAWINGS
[0033] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the following briefly introduces the drawings required for use in the embodiments or related technical descriptions. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.
[0034] FIG1 is a diagram illustrating an application environment of a fault management method according to an embodiment;
[0035] FIG2 is a schematic diagram of a flow chart of a fault management method according to an embodiment;
[0036] FIG3 is a schematic diagram of the structure of a fault attribute structure in one embodiment;
[0037] FIG4 is a flow chart showing steps for determining a fault reward and penalty mode in one embodiment;
[0038] FIG5 is a schematic flow chart of a fault management method in another embodiment;
[0039] FIG6 is a structural block diagram of a fault management device according to an embodiment;
[0040] FIG7 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION
[0041] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.
[0042] The fault management method provided in the embodiment of the present application can be applied to the application environment shown in Figure 1. Among them, the terminal 102 communicates with the server 104 through the network. The data storage system can store the data that the server 104 needs to process. The data storage system can be integrated on the server 104, or it can be placed on the cloud or other network servers. The server 104 obtains the initialization structure corresponding to each fault category and the fault information reported by each component within a preset time interval; uses the preset fault attribute structure and each fault information to update the various variables in the initialization structure to obtain the target fault intelligence, which includes a target count array, a target suspicious parameter array, a target mode number array, and a target display information array; and sends the target fault intelligence to the host computer for the host computer to perform fault processing based on the target fault intelligence.
[0043] The terminal 102 may be a sensor connected to various components in the vehicle; the server 104 may be implemented as an independent server or a server cluster consisting of multiple servers.
[0044] In an exemplary embodiment, as shown in FIG2 , a fault management method is provided, which is described by taking the method applied to the server 104 in FIG1 as an example, and includes the following steps 202 to 206 .
[0045] Step 202: Obtain the initialization structure corresponding to each fault type and the fault information reported by each component within a preset time interval.
[0046] Among them, the components in the whole vehicle include the internal combustion engine or electric motor in the power system; the gearbox or reducer in the transmission system; the braking power source, brake controller, brake actuator, etc. in the braking system; the generator, battery, relay and fuse, etc. in the power supply system.
[0047] For example, a time interval may be preset to be 30ms to 1000ms, or 40ms.
[0048] Step 204 : Using the preset fault attribute structure and each fault information, update each variable in the initialization structure to obtain target fault information.
[0049] The target fault intelligence includes a target count array, a target suspicious parameter array, a target mode number array, and a target display information array.
[0050] Among them, each variable in the initialization structure is matched with the mapping category of the fault attribute structure, and the variables in the initialization structure are respectively composed of the initial variable array. After updating and rearranging, the target count array, target suspicious parameter array, target mode number array and target display information array are obtained.
[0051] For example, the initialization structure can be updated by analyzing and processing the fault information through data mapping, or based on historical fault information and historical fault intelligence, through decision trees, neural networks and other methods to obtain updated values corresponding to various variables.
[0052] Optionally, before performing fault management, an initialization operation may be performed on the initialization structure to set various variables in the initialization structure to initial values.
[0053] In a possible implementation, as shown in FIG3 , the fault attribute structure may include but is not limited to:
[0054] Fault variable definition, used to indicate the fault level corresponding to the fault represented by the fault information;
[0055] Fault valid flag, used to indicate whether to perform fault processing on the fault;
[0056] The suspected parameter number of the fault refers to the unique number of the fault, which can be the SPN number (Suspect Parameter Number) of the entire vehicle fault;
[0057] Fault mode flag, which is the type or mode of the fault, and can be the FMI (Fault Code Information) code of the vehicle fault;
[0058] Fault count is the number of times a fault occurs. A fault that occurs after a single power-on is counted as one time. If the fault occurs again after it is eliminated, the fault count increases by one.
[0059] Fault reporting flag, indicating whether the fault of each level is displayed on the cockpit human-machine interaction interface. The fault reporting flags corresponding to faults of different levels may include fault level 1 reporting flag, fault level 2 reporting flag, fault level 3 reporting flag, and so on;
[0060] The fault light sign indicates whether the fault light is on for each level of fault. Different levels of fault may correspond to fault lights of different colors, including no fault light, yellow warning light, and red warning light. The fault light signs corresponding to different levels of fault may include fault level 1 light sign, fault level 2 light sign, fault level 3 light sign, etc.
[0061] Fault reward and punishment enable is used to determine whether to intervene in the vehicle according to the reward and punishment intensity corresponding to the fault level. The reward and punishment intensity is the intervention coefficient value;
[0062] The fault reward mode refers to the intervention measures for vehicle control enhancement corresponding to the current fault level. These measures may include enhanced heat dissipation, enhanced power generation, enhanced discharge, increased torque output, increased speed, and increased power. The fault reward modes corresponding to different fault levels may include: Fault Level 1 Reward Mode, Fault Level 2 Reward Mode, Fault Level 3 Reward Mode, and so on.
[0063] The fault penalty mode refers to the intervention measures of the vehicle suppression control corresponding to the current fault level, which may include suppressing discharge, suppressing power generation, suppressing heat dissipation, reducing speed, reducing torque, reducing power, etc. The fault penalty modes corresponding to different levels of faults may include: fault level 1 penalty mode, fault level 2 penalty mode, fault level 3 penalty mode, and so on.
[0064] Step 206: Send the target fault information to the host computer so that the host computer can perform fault processing based on the target fault information.
[0065] Among them, the target fault information can be reported through the CAN bus (Controller Area Network) based on the vehicle diagnostic protocol. The vehicle diagnostic protocol can include the J1939-73 protocol or the UDS (University Diagnostics System) protocol.
[0066] In the above fault management method, the initialization structure corresponding to each fault category and the fault information reported by each component within a preset time interval are obtained; the preset fault attribute structure and each fault information are used to update and process the various variables in the initialization structure to obtain the target fault intelligence, which includes a target count array, a target suspicious parameter array, a target mode number array, and a target display information array; the target fault intelligence is sent to the host computer for the host computer to perform fault processing based on the target fault intelligence. In this way, the fault information reported by each component in the vehicle can be integrated and screened to obtain the fault category that may affect the entire vehicle and the fault intelligence corresponding to the fault category. The attribute configuration parameters are rich, the fault management is flexible, and the active management of the entire vehicle fault can be achieved. It has a good effect on the fault management of the entire vehicle level and the complex assembly level, and can effectively improve the efficiency of fault management.
[0067] In an exemplary embodiment, based on the embodiment shown in Figure 2, the provided method also includes: for each initialization structure, performing a fault validity judgment based on the fault information to obtain a fault validity flag corresponding to the initialization structure; for the initialization structure whose fault validity flag is valid, executing a process of updating the variables in the initialization structure using a preset fault attribute structure and various fault information to obtain target fault intelligence.
[0068] Exemplarily, the validity determination includes determining the fault duration, fault operating environment, and other factors in the fault information. If the fault duration exceeds a preset threshold, the fault validity flag is determined to be valid; if it is less than or equal to the threshold, the fault validity flag is determined to be invalid. Alternatively, if the fault operating environment is in normal mode, the fault validity flag is determined to be valid, but in specific modes, such as braking or starting mode, the fault validity flag may be determined to be invalid.
[0069] In a possible implementation, when the fault valid flag is invalid, the fault information corresponding to the fault valid flag is ignored.
[0070] In an exemplary embodiment, the provided method, for an initialization structure whose fault validity flag is valid, executes an update process on each variable in the initialization structure using a preset fault attribute structure and each fault information to obtain target fault intelligence, which may further include: performing counting and statistical processing on the initial count variables in the initialization structure to obtain fault count data corresponding to the initialization structure; performing level judgment on the fault information to obtain an initial fault level corresponding to the fault information; based on the fault attribute structure and the initial fault level, updating each variable in the initialization structure to obtain initial fault intelligence; and obtaining target fault intelligence based on the fault count data and initial fault intelligence corresponding to each initialization structure.
[0071] The initial count variable can be set to 0. After the fault valid flag is determined to be valid, the fault count corresponding to the current time interval is equal to the initial count variable plus 1. In this way, if a component fails intermittently over multiple time intervals, the fault may be eliminated in a certain time interval, and the fault count data may be the same as the previous time interval. If the fault recurs in a subsequent time interval, the fault count data will be incremented by 1 again.
[0072] The initial fault level can be determined by analyzing the component identifier, component-level fault level, and the mapping relationship between the component-level fault level and the vehicle-level fault level in the fault information. This mapping relationship can be pre-stored in a data storage system on the server or be part of a fault attribute structure. The initial fault level is determined by calling the fault attribute structure.
[0073] It is understandable that the initial fault level may be inconsistent with the fault level in the fault information reported by the component. The level assigned to the fault in the fault information generated by the component may be different from the vehicle-level fault level. For example, if the temperature of the power motor on a hybrid vehicle is too high, it is a serious fault for the power motor component and the fault level is high. Since some configurations of hybrid systems have multiple driving modes, the fault does not affect the vehicle's driving or the vehicle can quickly reduce the temperature through load adjustment of the cooling system. Therefore, when the vehicle determines that the fault is a minor fault or even no fault, the fault level can be downgraded to a minor fault or even no fault.
[0074] There is a corresponding relationship between the initial fault information and the initial fault level, and the corresponding relationship is preset in the fault attribute structure. After the initial fault level is determined, the corresponding initial fault information can be determined through the fault attribute structure.
[0075] In this embodiment, fault information is redefined using the initial fault level, adjusting the fault level reported by a component to match the fault level of the entire vehicle. This avoids issues such as false alarms, mismatches between fault levels and vehicle faults, and unpredictable fault protection strategies often seen in existing component-based fault management. The fault management method provided in this embodiment offers rich attribute configuration parameters, flexible fault management, and proactive vehicle fault management and intervention control for intelligent fault suppression or elimination.
[0076] In one possible implementation, the initial fault intelligence includes a suspicious parameter number, a fault mode number, and fault display information. The process of obtaining target fault intelligence based on the fault count data and initial fault intelligence corresponding to each initialization structure may further include: generating a fault count array, a suspicious parameter number array, a fault mode number array, and a fault display information array based on the fault count data and initial fault intelligence corresponding to each initialization structure; sorting the fault display information array according to a preset sorting rule to obtain a target display information array; and sorting the fault count array, the suspicious parameter number array, and the fault mode number array based on the target display information array to obtain a target count array, a target suspicious parameter array, and a target mode number array.
[0077] Each element in the fault count array contains the fault count data for each fault category; each element in the suspicious parameter number array contains the suspicious parameter number for each fault category; each element in the fault mode number array contains the fault mode number for each fault category; and each element in the fault display information array contains the fault display information for each fault category. In the fault count array, suspicious parameter number array, fault mode number array, and fault display information array, the element with sequence number 0 represents the data for the first fault category, the element with sequence number 1 represents the data for the second fault category, and so on.
[0078] Optionally, in combination with the aforementioned embodiment, the fault display information can be fault light sign information of different colors. For example, an initial fault level of 1 indicates a minor fault level or no fault, and based on the fault attribute structure, the fault display information can be determined to be green; an initial fault level of 2 indicates a medium fault level, and based on the fault attribute structure, the fault display information can be determined to be yellow; an initial fault level of 3 indicates a severe fault level, and based on the fault attribute structure, the fault display information can be determined to be red.
[0079] In one possible implementation, the preset sorting rule is based on a bubble sorting algorithm, so that the fault display information is sorted in the order of red, yellow, and green, that is, sorted from severe to mild fault level. After obtaining the target display information array, the sorting of the other arrays is adjusted so that elements with the same sequence number in each array correspond to the same fault category.
[0080] In an exemplary embodiment, the initial fault intelligence in the provided method includes a fault reward and punishment mode and a reward and punishment degree value corresponding to the fault reward and punishment mode. The method also includes: generating reward and punishment reference intelligence based on the fault reward and punishment mode and the reward and punishment degree value, and sending the reward and punishment reference intelligence to the host computer.
[0081] In one possible implementation, in combination with the above-mentioned embodiment, for an initialization structure whose fault validity flag is valid, the fault reporting flag, fault reward and punishment enable, fault reward and punishment mode, and fault reward and punishment mode are determined based on the fault attribute structure and the initial fault level. Specifically, as shown in FIG4 , if the initial fault level is 1, the fault reporting flag is a fault level 1 reporting flag, and the fault reward and punishment enable is determined to be started, the fault level 1 reward mode, and the fault level 1 penalty mode is determined; if the initial fault level is 2, the fault reporting flag is a fault level 2 reporting flag, and the fault reward and punishment enable is determined to be started, the fault level 2 reward mode, and the fault level 2 penalty mode is determined; if the initial fault level is greater than or equal to 3, the fault reporting flag is a fault level 2 reporting flag, and the fault reward and punishment enable is determined to be started, the fault level 2 reward mode, and the fault level 2 penalty mode. For an initialization structure whose fault validity flag is invalid, the fault information is ignored.
[0082] Among them, the host computer can determine the fault handling strategy based on the reward and punishment reference information.
[0083] Exemplarily, the fault reward mode determined based on the initial fault level is the fault level 1 reward mode, and the fault penalty mode is the fault level 1 penalty mode, which specifically includes rewarding heat dissipation and punishing power reduction, and the reward and punishment degree values are both 1; the upper computer can determine the fault handling strategy based on the received reward and punishment reference information, such as thermal management of the cooling system, motor, engine, battery, etc.
[0084] In one possible implementation, the method further includes generating a reward and punishment control instruction based on the fault reward and punishment mode and the reward and punishment degree value, and sending the reward and punishment control instruction to each component, so that each component can perform fault adjustment according to the reward and punishment control instruction. In this way, for faults with a low initial fault level, proactive management and intervention can be implemented based on the fault information reported by each component, resolving the fault promptly and efficiently, thereby improving the proactiveness and efficiency of fault management.
[0085] In an exemplary embodiment, as shown in FIG5 , a fault management method is provided, which is described by taking the method applied to the server 104 in FIG1 as an example, and includes the following steps 501 to 510 . In which:
[0086] Step 501: Obtain an initialization structure corresponding to each fault type and fault information reported by each component within a preset time interval.
[0087] Step 502: For each initialization structure, a fault validity judgment is performed based on the fault information to obtain a fault validity flag corresponding to the initialization structure.
[0088] Step 503: When the fault valid flag is invalid, the fault information corresponding to the fault valid flag is ignored.
[0089] Step 504 : For the initialization structure whose fault valid flag is valid, perform counting statistics processing on the initial count variable in the initialization structure to obtain fault counting data corresponding to the initialization structure.
[0090] Step 505: Perform level judgment on the fault information to obtain an initial fault level corresponding to the fault information.
[0091] Step 506: Based on the fault attribute structure and the initial fault level, various variables in the initialization structure are updated to obtain initial fault information.
[0092] The initial fault information includes: the suspicious parameter number, the fault mode number, the fault display information, the fault reward and punishment mode, and the reward and punishment degree value corresponding to the fault reward and punishment mode.
[0093] Step 507 : Generate a fault count array, a suspicious parameter number array, a fault mode number array, and a fault display information array according to the fault count data and initial fault information corresponding to each initialization structure.
[0094] Step 508: sort the fault display information array according to a preset sorting rule to obtain a target display information array.
[0095] Step 509 : Based on the target display information array, the fault count array, the suspicious parameter number array, and the fault mode number array are sorted to obtain a target count array, a target suspicious parameter array, and a target mode number array.
[0096] Step 510 , based on the target count array, the target suspicious parameter array, the target mode number array, the fault reward and punishment mode and the reward and punishment degree value, generates reward and punishment reference information, and sends the reward and punishment reference information to the host computer.
[0097] It should be understood that, although the steps in the flowcharts of the above embodiments are shown in sequence as indicated by the arrows, these steps are not necessarily performed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be performed in other orders. Moreover, at least a portion of the steps in the flowcharts of the above embodiments may include multiple steps or multiple stages, and these steps or stages are not necessarily performed at the same time, but can be performed at different times. The execution order of these steps or stages is not necessarily to be performed in sequence, but can be performed in turn or alternately with other steps or at least a portion of steps or stages in other steps.
[0098] Based on the same inventive concept, embodiments of the present application also provide a fault management device for implementing the aforementioned fault management method. The solution provided by this device is similar to the solution described in the aforementioned method. Therefore, the specific limitations in one or more of the following embodiments of the fault management device can be found in the above-described limitations on the fault management method and are not further elaborated here.
[0099] In an exemplary embodiment, as shown in FIG6 , a fault management device is provided, including: an information acquisition module 602 , an intelligence generation module 604 , and an intelligence sending module 606 , wherein:
[0100] The information acquisition module 602 is used to obtain the initialization structure corresponding to each fault type and the fault information reported by each component within a preset time interval;
[0101] The intelligence generation module 604 is used to update the variables in the initialization structure using the preset fault attribute structure and each fault information to obtain target fault intelligence, which includes a target count array, a target suspicious parameter array, a target mode number array, and a target display information array;
[0102] The information sending module 606 is used to send the target fault information to the host computer so that the host computer can perform fault processing based on the target fault information.
[0103] In one embodiment, the intelligence generation module 604 is also used to judge the fault validity of each initialization structure based on the fault information, and obtain a fault validity flag corresponding to the initialization structure; for the initialization structure with a valid fault validity flag, the preset fault attribute structure and various fault information are used to update the variables in the initialization structure to obtain the target fault intelligence.
[0104] In one embodiment, the intelligence generation module 604 is also used to perform counting statistics on the initial counting variables in the initialization structure to obtain fault counting data corresponding to the initialization structure; perform level judgment on the fault information to obtain the initial fault level corresponding to the fault information; based on the fault attribute structure and the initial fault level, update each variable in the initialization structure to obtain initial fault intelligence; and obtain target fault intelligence based on the fault counting data and initial fault intelligence corresponding to each initialization structure.
[0105] In one embodiment, the initial fault intelligence includes: a suspicious parameter number, a fault mode number, and fault display information; the intelligence generation module 604 is further used to generate a fault count array, a suspicious parameter number array, a fault mode number array, and a fault display information array based on the fault count data and initial fault intelligence corresponding to each initialization structure; the fault display information array is sorted according to a preset sorting rule to obtain a target display information array; based on the target display information array, the fault count array, the suspicious parameter number array, and the fault mode number array are sorted respectively to obtain a target count array, a target suspicious parameter array, and a target mode number array.
[0106] In one embodiment, the initial fault intelligence includes a fault reward and punishment mode and a reward and punishment degree value corresponding to the fault reward and punishment mode. The intelligence generation module 604 is also used to generate reward and punishment reference intelligence based on the fault reward and punishment mode and the reward and punishment degree value, and send the reward and punishment reference intelligence to the host computer.
[0107] In one embodiment, the intelligence generating module 604 is further configured to ignore the fault information corresponding to the fault valid flag when the fault valid flag is invalid.
[0108] Each module in the fault management device described above may be implemented in whole or in part through software, hardware, or a combination thereof. Each module may be embedded in or independent of a processor in a computer device in hardware form, or may be stored in a memory in the computer device in software form, so that the processor can call and execute the corresponding operations of each module.
[0109] In an exemplary embodiment, a computer device is provided, which may be a server. Its internal structure may be as shown in FIG7 . The computer device includes a processor, memory, an input / output (I / O) interface, and a communication interface. The processor, memory, and I / O interface are connected via a system bus, and the communication interface is connected to the system bus via the I / O interface. The processor of the computer device provides computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operating system and computer program in the non-volatile storage medium. The database of the computer device stores initialization structures corresponding to each fault category and fault information reported by each component within a preset time interval. The I / O interface of the computer device is used to exchange information between the processor and external devices. The communication interface of the computer device is used to communicate with external terminals via a network connection. When executed by the processor, the computer program implements a fault management method.
[0110] Those skilled in the art will understand that the structure shown in FIG7 is merely a block diagram of a portion of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different arrangement of components.
[0111] In one embodiment, a computer device is further provided, including a memory and a processor. The memory stores a computer program, and the processor implements the steps in the above method embodiments when executing the computer program.
[0112] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.
[0113] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.
[0114] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.
[0115] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the above-mentioned embodiments. In particular, any reference to memory, database, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The databases involved in the various embodiments provided herein may include at least one of a relational database and a non-relational database. Non-relational databases may include, but are not limited to, distributed databases based on blockchains. The processors involved in the various embodiments provided herein may be, but are not limited to, general-purpose processors, central processing units (CPUs), graphics processing units (GPUs), digital signal processors (DSPs), programmable logic devices (PLDs), data processing logic devices based on quantum computing, and the like.
[0116] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.
[0117] The above embodiments merely illustrate several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present invention. It should be noted that a person skilled in the art may make various modifications and improvements without departing from the spirit of the present invention, all of which fall within the scope of protection of the present application. Therefore, the scope of protection of the present application shall be determined by the appended claims.
Claims
1. A fault management method, characterized in that: The method comprises: Obtain the initialization structure corresponding to each fault category and the fault information reported by each component within a preset time interval; Using the preset fault attribute structure and each of the fault information, updating the variables in the initialization structure to obtain target fault intelligence, the target fault intelligence includes a target count array, a target suspicious parameter array, a target mode number array and a target display information array; The target fault information is sent to a host computer so that the host computer can perform fault processing based on the target fault information.
2. The method according to claim 1, characterized in that The method further comprises: For each of the initialization structures, a fault validity judgment is performed based on the fault information to obtain a fault validity flag corresponding to the initialization structure; For the initialization structure whose fault validity flag is valid, the process of using the preset fault attribute structure and each fault information to update the variables in the initialization structure to obtain the target fault information is executed.
3. The method according to claim 2, characterized in that The initialization structure with the fault validity flag as valid is executed by using the preset fault attribute structure and each fault information, and updating each variable in the initialization structure to obtain target fault information, including: Performing counting statistics processing on the initial counting variables in the initialization structure to obtain fault counting data corresponding to the initialization structure; Performing level judgment on the fault information to obtain an initial fault level corresponding to the fault information; Based on the fault attribute structure and the initial fault level, updating various variables in the initialization structure to obtain initial fault information; The target fault information is obtained according to the fault counting data and the initial fault information corresponding to each of the initialization structures.
4. The method according to claim 3, characterized in that The initial fault information includes: suspicious parameter number, fault mode number and fault display information; The step of obtaining the target fault information according to the fault count data and the initial fault information corresponding to each of the initialization structures includes: Generate a fault count array, a suspicious parameter number array, a fault mode number array and a fault display information array according to the fault count data and the initial fault information corresponding to each of the initialization structures; Sorting the fault display information array according to a preset sorting rule to obtain the target display information array; Based on the target display information array, the fault count array, the suspicious parameter number array and the fault mode number array are sorted respectively to obtain the target count array, the target suspicious parameter array and the target mode number array.
5. The method according to claim 3, characterized in that: The initial fault information includes a fault reward and punishment mode and a reward and punishment degree value corresponding to the fault reward and punishment mode, and the method further includes: Based on the fault reward and punishment mode and the reward and punishment degree value, reward and punishment reference information is generated, and the reward and punishment reference information is sent to the host computer.
6. The method according to claim 2, characterized in that The method further includes: when the fault validity flag is invalid, ignoring the fault information corresponding to the fault validity flag.
7. A fault management device, characterized in that: The device comprises: An information acquisition module is used to obtain the initialization structure corresponding to each fault category and the fault information reported by each component within a preset time interval; An intelligence generation module, used to update various variables in the initialization structure using a preset fault attribute structure and each of the fault information to obtain target fault intelligence, wherein the target fault intelligence includes a target count array, a target suspicious parameter array, a target mode number array, and a target display information array; The intelligence sending module is used to send the target fault intelligence to the host computer so that the host computer can perform fault processing based on the target fault intelligence.
8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.
9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.
10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.