Standardized failure record automatic generation method, system and visual terminal
By storing multiple fault handling processes in a shared storage area and dynamically migrating the processes based on fault categories, the problem of low fault handling efficiency in existing technologies is solved, achieving efficient fault record generation and data accuracy.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- DEZHOU POWER SUPPLY COMPANY OF STATE GRID SHANDONG ELECTRIC POWER
- Filing Date
- 2022-05-16
- Publication Date
- 2026-05-29
AI Technical Summary
Existing technologies fail to adequately consider the specific information of different types of faults in fault handling, resulting in low processing efficiency. In particular, when generating fault record outputs for subsequent analysis, the existing processing methods cannot meet the actual needs.
Multiple fault handling processes are stored in a shared storage area. By parsing the fault information category, the handling processes are dynamically migrated to match the actual resource status and generate fault records.
It improves fault handling efficiency, avoids process blockage or idleness, and ensures timely generation of fault records and data accuracy.
Smart Images
Figure CN115248753B_ABST
Abstract
Description
Technical Field
[0001] This invention belongs to the field of fault handling technology, and in particular relates to a standardized fault record automatic generation method, system and visualization terminal. Background Technology
[0002] Currently, most fault records are still in the manual entry stage. For example, for distribution network fault records, the inspection results of on-site inspectors still need to be reported by telephone and manually entered into the OMS duty log. The records are delayed and prone to omissions, and the efficiency of fault command and handling needs to be improved.
[0003] To address this, existing technologies have proposed various automated intelligent fault handling and generation techniques. For example, application number CN201910605357.5 (classification numbers G06F16 / 36; G16H40 / 40) proposes a knowledge base for storing device fault records, and a method and system for using it to assist in locating device faults. By continuously expanding maintenance experience through the maintenance knowledge base, it can assist in locating faults in medical equipment, greatly improving processing efficiency and saving manpower.
[0004] However, the inventors discovered that existing technologies use a unified fault handling process or fault handling model to perform fault response, but different types of faults require different handling methods; or they simply use a multi-process model for fault load balancing, without fully considering the specific information of the fault type and the possible blocking or idle states of each process area, resulting in low fault handling efficiency; especially when considering the need to generate fault record output for subsequent analysis, the existing technology's handling method cannot meet the actual needs. Summary of the Invention
[0005] To address the aforementioned technical problems, this invention proposes a standardized method, system, and visualization terminal for automatically generating fault records.
[0006] In a first aspect of the invention, a standardized fault log automatic generation method is proposed, the method being implemented based on at least one shared storage area, each of which stores multiple fault processing processes;
[0007] Specifically, the method includes the following steps:
[0008] S1: Obtain the currently received fault information;
[0009] S2: Analyze the fault information to obtain the category of the fault information;
[0010] S3: Based on the category of the fault information, determine the target fault handling process corresponding to the category;
[0011] S4: Based on the target fault handling process, determine multiple target shared storage areas;
[0012] S5: Process the currently received fault information based on the status of all fault handling processes stored in each of the shared storage areas;
[0013] S6: Generate fault record output.
[0014] In the initial state, each of the shared storage areas stores multiple fault handling processes, and each fault handling process corresponds to different categories of fault information.
[0015] In the technical solution of the present invention, the state of the shared storage area is dynamically changing. After it is started from the initial state, the state is changed by performing process migration based on the state of all fault handling processes stored in the shared storage area. Then, according to the actual dynamic changes in resource state parameters, the initial state can be restored, and the above process is repeated.
[0016] More specifically, in step S2, after parsing the fault information and obtaining the category of the fault information, the fault information category is broadcast to all shared storage areas through a broadcast process;
[0017] Then, based on the category of the fault information, the target fault handling process corresponding to the category is determined;
[0018] Next, based on the target fault handling process, multiple target shared storage areas are determined.
[0019] More specifically, taking multiple target shared storage areas including a first target shared storage area and a second target shared storage area as an example, the first target shared storage area contains a first target fault handling process corresponding to the category; the second target shared storage area contains a second target fault handling process corresponding to the category;
[0020] Then, in step S5, based on the status of all fault handling processes stored in each of the shared storage areas, the first target fault handling process or the second target fault handling process is migrated.
[0021] After the migration is complete, the target shared storage area is determined to receive the currently received fault information and automatically generate fault records. This target shared storage area is the shared storage area that the target fault handling process migrates into.
[0022] At this point, step S5 further includes:
[0023] Based on the status of all fault handling processes stored in each of the shared storage areas, a target shared storage area is determined for receiving the currently received fault information and automatically generating fault records.
[0024] Determine the target status of all target fault handling processes contained in the target shared storage area, and based on all target statuses, determine whether to perform the initialization operation of the target shared storage area.
[0025] In a second aspect of the invention, a standardized fault record automatic generation system is provided, the system comprising multiple processor groups, each processor group containing multiple processing cores.
[0026] In terms of specific structure, the system also includes:
[0027] Fault information receiving unit, used to receive fault information;
[0028] A fault information parsing unit is used to parse the fault information to obtain the fault category;
[0029] The fault category broadcasting unit is used to broadcast the fault category parsed by the fault information parsing unit to each processor group;
[0030] The target processing core determination unit is used to determine the target processing core in each processor group based on the received fault category;
[0031] The target processor group determination unit is used to determine whether each processor group is a target processor group based on the target processing cores.
[0032] The process migration unit is used to migrate running processes on at least one target processing core based on the resource usage of each processing core in each target processor group.
[0033] The fault information is processed in the target processor group receiving the migration process, and a fault record is generated and output.
[0034] As a further improvement, the processor group initialization unit is used to initialize the processes running on the processors contained in each processor group, the initialization causing each processor contained in each processor group to run a different type of fault handling process.
[0035] As a further improvement, the system also includes a processor group initialization determination unit;
[0036] The processor group initialization judgment unit is used to determine whether the target processor group of the receiving migration process meets the initialization conditions. If it does meet the conditions, the processor group initialization unit is called to perform initialization on the target processor group of the receiving migration process.
[0037] In the above two technical solutions, the fault category includes any combination of the following categories (1) and (2):
[0038] Category (1): Periodic errors, occasional errors, and frequent errors;
[0039] Category (2): Response error and non-response error.
[0040] All of the methods described above in this invention can be implemented automatically using computer program instructions. Therefore, this invention can also be implemented as a computer storage medium storing computer program instructions, which are executed by a processor to achieve the method described in the first aspect.
[0041] In addition, to facilitate field application, the present invention also provides a visual handheld portable terminal, which includes a memory and a processor. The processor processes the received fault information by executing the standardized fault record automatic generation method described in the first aspect by running executable instruction code stored in the memory, and generates fault records that are displayed on the human-computer interaction interface of the visual handheld portable terminal.
[0042] The technical solution of this invention stores multiple fault handling processes of different categories in a shared storage area. After receiving fault information, the fault category is parsed, and then multiple target processing processes corresponding to different shared storage areas are determined. Process migration is performed based on the actual running state, ensuring that the running process in the shared storage area used to handle the current fault category is always in the most efficient and optimal state. While ensuring that the current type of fault can be processed in a timely manner and fault records are generated, process blocking or process idleness is avoided, thus improving fault handling efficiency. At the same time, the setting method of periodically judging the status of the target shared storage area and performing initialization and recovery can also avoid data accumulation errors.
[0043] Further advantages of the present invention will be further detailed in the Specific Embodiments section in conjunction with the accompanying drawings. Attached Figure Description
[0044] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0045] Figure 1 This is a schematic diagram illustrating the steps of a standardized fault record automatic generation method according to an embodiment of the present invention;
[0046] Figure 2 yes Figure 1 A flowchart illustrating the process nodes of the standardized fault record automatic generation method implemented using a computer process.
[0047] Figure 3 yes Figure 1 A flowchart of a first preferred embodiment of a standardized fault record automatic generation method;
[0048] Figure 4 yes Figure 1 A flowchart of a second preferred embodiment of the standardized fault record automatic generation method;
[0049] Figure 5 It is to achieve Figure 1 The module architecture diagram of the standardized fault record automatic generation system described in the method;
[0050] Figure 6 yes Figure 5 A schematic diagram of a preferred embodiment of the standardized fault record automatic generation system. Detailed Implementation
[0051] The invention will now be further described in conjunction with the accompanying drawings and specific embodiments.
[0052] Before introducing the technical solution and various embodiments of the present invention, the source of the relevant issues will be introduced first, so as to better understand the inventiveness of the present invention and its improvement over the prior art.
[0053] In various embodiments of the present invention, fault information is continuously received.
[0054] For example, fault information can be uploaded in real time by field equipment or terminals when a fault is detected, or it can be uploaded according to a preset cycle based on the frequency of fault occurrence.
[0055] As an example, a terminal may terminate due to an error during runtime. In this case, fault information is generated and uploaded in real time, and the terminal waits for a fault response. This type of fault is called a response error, which means that after a fault occurs, a fault response is required before the terminal can continue to run.
[0056] As another example, the device can log fault information, which is usually a non-response error, meaning the error can be skipped and does not affect the current task execution process of the device or terminal. It is just a common error that occurs unexpectedly, and the log is saved for subsequent optimization.
[0057] Based on the frequency of occurrence, faults can also be divided into periodic errors, occasional errors, and frequent errors.
[0058] Among them, periodic errors refer to errors that occur periodically based on historical data analysis; occasional errors refer to errors that rarely occur based on historical data analysis; and frequent errors refer to errors that occur more frequently than a threshold within a preset time period.
[0059] Understandably, the classification of periodic errors, occasional errors, and frequent errors is not fixed, and some types can transform into one another. For example, a frequent error may evolve into a periodic error, and a current occasional error may evolve into a frequent error, and so on.
[0060] Therefore, in various embodiments of the present invention, the fault category includes one or any combination of the following categories (1) and (2):
[0061] Category (1): Periodic errors, occasional errors, and frequent errors;
[0062] Category (2): Response error and non-response error.
[0063] Therefore, the fault categories include at least:
[0064] 1. Periodic response error, 2. Periodic non-response error, 3. Occasional response error, 4. Occasional non-response error, 5. Frequent response error, 6. Frequent non-response error;
[0065] or:
[0066] A. Periodic errors, B. Occasional errors, C. Frequent errors, D. Response errors, and E. Non-response errors.
[0067] The inventors discovered that different types of faults require different handling methods. For example, response errors need to be handled in real time and recorded and fed back promptly, while non-response errors may be handled later and will not affect the system process. Frequent errors require calling frequency analysis models and prediction models to predict the time of the next fault occurrence and generate records to remind the user, while occasional errors do not require special handling. Periodic response errors may require periodic analysis models and efforts to eliminate or extend the period, and so on.
[0068] However, in existing technologies, most fault response is performed using a unified fault handling process or fault handling model, or simply using a multi-process model for fault load balancing. These technologies do not fully consider the specific information of the fault category or the possible blocking or idle states of each process area, resulting in low fault handling efficiency. In particular, when considering the need to generate fault record output for subsequent analysis, this approach in existing technologies cannot meet the actual needs.
[0069] To address the aforementioned technical problems, various embodiments of the present invention are as follows. For ease of description, in some places, "fault" and "error" have the same meaning, unless the context otherwise specifies otherwise.
[0070] Figure 1 This is a schematic diagram illustrating the steps of a standardized fault record automatic generation method according to an embodiment of the present invention.
[0071] Figure 1 The flowchart includes steps S1-S6, and each step is implemented as follows:
[0072] S1: Obtain the currently received fault information;
[0073] S2: Analyze the fault information to obtain the category of the fault information;
[0074] S3: Based on the category of the fault information, determine the target fault handling process corresponding to the category;
[0075] S4: Based on the target fault handling process, determine multiple target shared storage areas;
[0076] S5: Process the currently received fault information based on the status of all fault handling processes stored in each of the shared storage areas;
[0077] S6: Generate fault record output.
[0078] The method is implemented based on at least one shared storage area, and each shared storage area stores multiple fault handling processes.
[0079] In implementing the method, it can be based on multiple many-core processor groups, each of which includes multiple processor cores.
[0080] In actual execution, one fault handling process runs on each processor core, and multiple fault handling processes run on multiple processor cores of a processor group. A processor group constitutes a shared memory area.
[0081] In embodiments of the present invention, "shared storage" means that all processor cores in a processor group share each other's state and process category information.
[0082] In this sense, shared storage can also be called "shared mapping," meaning that information about the same fault category will be mapped to all processor cores. For example... Figure 2 The shared mapping area.
[0083] In the initial state, each of the shared storage areas stores multiple fault handling processes, and each fault handling process corresponds to different categories of fault information.
[0084] Specifically, taking the aforementioned error (fault) categories as an example,
[0085] If the fault category is: 1. Periodic response error, 2. Periodic non-response error, 3. Occasional response error, 4. Occasional non-response error, 5. Frequent response error, 6. Frequent non-response error;
[0086] In the initial state, each of the shared storage areas stores 6 fault handling processes, which handle the above 6 types of faults respectively;
[0087] For example, fault handling process 1 is used to handle periodic response errors, which includes a periodic analysis model and an algorithm to eliminate or extend the period; the other fault handling processes 2-6 also correspond to the corresponding fault types.
[0088] or:
[0089] If the fault category is: A. Periodic error, B. Occasional error, C. Frequent error, D. Response error, and E. Non-response error,
[0090] In the initial state, each of the shared storage areas stores 5 fault handling processes, which handle the above 5 types of faults respectively.
[0091] For example, fault handling process D is used to handle response errors. It performs fault error handling in real time and provides timely log feedback; other fault handling processes AC / E also correspond to the corresponding fault types.
[0092] To better explain Figure 1 The execution process of the method is as follows: Figure 1 Based on this, see Figure 2 . Figure 2 yes Figure 1 The flowchart of the standardized fault record automatic generation method implemented using computer processes is shown in the diagram.
[0093] exist Figure 2 The system includes a fault information receiving node and a fault information parsing node (output node). Figure 2 The fault categories in the process and the broadcast process node are broadcast to all fault handling processes through the broadcast process node, and then the migration process performs the migration of the fault handling process.
[0094] Combination Figure 2 Step S2 further includes broadcasting the fault information category to all shared storage areas.
[0095] based on Figures 1-2 , Figures 3-4 Two different preferred embodiments of the method are shown respectively.
[0096] exist Figure 3 The method is specifically implemented as follows:
[0097] S31: Obtain the currently received fault information;
[0098] S32: Analyze the fault information to obtain the category of the fault information;
[0099] S33: Broadcast the fault information category to all shared storage (mapping) areas;
[0100] S34: Determine the target fault handling process corresponding to the category;
[0101] S35: Determine the first target shared storage (mapping) area and the second target shared storage (mapping) area;
[0102] S36: Migrate the first target fault handling process or the second target fault handling process;
[0103] S37: Determine the target shared storage area for receiving currently received fault information and automatically generating fault records;
[0104] S38: Generate fault record output.
[0105] It is worth noting that, as previously stated, each of the shared storage areas stores multiple fault handling processes. Specifically, each of the shared storage areas stores N fault handling processes, where N > 2, such as the N = 5 or N = 6 category classification mentioned in the previous embodiments. Of course, fault categories can also be divided into other numbers of categories.
[0106] Step S3 determines the target fault handling process corresponding to the category based on the category of the fault information;
[0107] Then, step S4 determines multiple target shared storage areas based on the target fault handling process.
[0108] It is understandable that, in the initial case, since each of the shared storage areas stores multiple fault handling processes, and each fault handling process corresponds to different types of fault information, all shared storage areas are target storage areas at this time, but they will change and migrate dynamically in the future.
[0109] For ease of description, the following embodiments will be described using the multiple target shared storage areas determined in step S4, including the first target shared storage area and the second target shared storage area, as an example.
[0110] Clearly, the "first target shared storage area and the second target shared storage area" here refer to any two "target shared storage areas" and do not specifically refer to any two target shared storage areas.
[0111] The first target shared storage area contains a first target fault handling process corresponding to the category;
[0112] The second target shared storage area contains a second target fault handling process corresponding to the category. Taking the fault information category parsed from the currently received fault information as a periodic response error as an example, both the first target shared storage area and the second target shared storage area contain a first target fault handling process 1 (fault handling process 1, used to handle periodic response errors, which includes a periodic analysis model and an algorithm to eliminate or extend the period) and a second target fault handling process 1 (fault handling process 1, used to handle periodic response errors, which includes a periodic analysis model and an algorithm to eliminate or extend the period).
[0113] Next, step S5 includes:
[0114] Based on the status of all fault handling processes stored in each of the shared storage areas, migrate the first target fault handling process or the second target fault handling process.
[0115] Then, determine the target shared storage area for receiving the currently received fault information and automatically generating fault records; generate fault record output.
[0116] Specifically, in this embodiment, after the migration is completed, a target shared storage area is determined for receiving the currently received fault information and automatically generating fault records. This target shared storage area is the shared storage area that the target fault handling process migrates into.
[0117] For specific implementation examples, please refer to Figure 5 , Figure 5 Another embodiment of the method is fully illustrated below:
[0118] S51: Obtain the currently received fault information;
[0119] S52: Analyze the fault information to obtain the category of the fault information;
[0120] S53: Broadcast the fault information category to all shared storage areas;
[0121] S54: Determine the target fault handling process corresponding to the category;
[0122] S55: Determine the first target shared memory area and the second target shared memory area;
[0123] S56: Determine the first resource occupancy ratio R1 of the first target fault handling process in the first target shared memory area and determine the second resource occupancy ratio R2 of the second target fault handling process in the second target shared memory area;
[0124] S57: Determine whether R1 > R2 is true.
[0125] If so, the second target fault handling process is migrated from the second target shared storage area to the first target shared storage area; the first target shared storage area receives the currently received fault information and automatically generates fault records;
[0126] If not, the first target fault handling process is migrated from the first target shared storage area to the second target shared storage area, where the second target shared storage area receives the currently received fault information and automatically generates fault records.
[0127] S58: Generate fault record output.
[0128] In the above embodiment, step S5 further includes:
[0129] Based on the status of all fault handling processes stored in each of the shared storage areas, a target shared storage area is determined for receiving the currently received fault information and automatically generating fault records. That is, the target shared storage area is the shared storage area to which the target fault handling process migrates.
[0130] At this point, it can be understood that the target shared storage area contains at least two identical target fault handling processes that process the same type of fault information.
[0131] The target shared storage area receives the current fault information and, according to the load balancing principle, distributes the current fault information to multiple target fault processing processes corresponding to the current fault category information to automatically generate fault records.
[0132] Next, step S5 further includes:
[0133] Determine the target status of all target fault handling processes contained in the target shared storage area, and based on all target statuses, determine whether to perform the initialization operation of the target shared storage area.
[0134] Here, the target states of all target fault handling processes refer to the resource utilization rate of each target handling process.
[0135] If the resource occupancy rate of all target fault handling processes contained in the target shared storage area exceeds a preset value, then the initialization operation is performed to restore the target shared storage area where the target fault handling process is located to the processing state.
[0136] It is understandable that if the resource utilization rate of a certain type of fault handling process remains high for a long period of time, it will greatly affect the handling of other types of errors (faults), resulting in an increase in the overall cumulative error.
[0137] Therefore, the embodiments of the present invention are further improved in that if the resource occupancy rate of the target fault handling process contained in the target shared storage area exceeds a preset value, the initialization operation is performed so that the target shared storage area where the target fault handling process is located is restored to the processing state. This is another improvement of the present invention.
[0138] The foregoing Figures 1-4 The technical solution of the present invention has been described in the method section. See below for further details. Figure 5 Figures 6 and 7 respectively illustrate a specific embodiment of an automated fault log generation system for performing the method.
[0139] See Figure 5 This paper illustrates a standardized fault log automatic generation system, which includes multiple processor groups, each containing multiple processing cores.
[0140] In terms of specific structure, the system also includes:
[0141] Fault information receiving unit, used to receive fault information;
[0142] A fault information parsing unit is used to parse the fault information to obtain the fault category;
[0143] The fault category broadcasting unit is used to broadcast the fault category parsed by the fault information parsing unit to each processor group;
[0144] The target processing core determination unit is used to determine the target processing core in each processor group based on the received fault category;
[0145] The target processor group determination unit is used to determine whether each processor group is a target processor group based on the target processing cores.
[0146] The process migration unit is used to migrate running processes on at least one target processing core based on the resource usage of each processing core in each target processor group.
[0147] The fault information is processed in the target processor group receiving the migration process, and a fault record is generated and output.
[0148] Further, see Figure 6 The system further includes a processor group initialization unit and a processor group initialization judgment unit;
[0149] The processor group initialization unit is used to initialize the processes running on the processors contained in each processor group, and the initialization enables each processor contained in each processor group to run different types of fault handling processes.
[0150] The processor group initialization judgment unit is used to determine whether the target processor group of the receiving migration process meets the initialization conditions. If it does meet the conditions, the processor group initialization unit is called to perform initialization on the target processor group of the receiving migration process.
[0151] The fault categories include any combination of the following categories (1) and (2):
[0152] Category (1): Periodic errors, occasional errors, and frequent errors;
[0153] Category (2): Response error and non-response error.
[0154] Further embodiments of the present invention include a visualization terminal, the visualization terminal comprising a memory and a processor, the processor executing executable instruction code stored in the memory to perform... Figures 1-4 The standardized fault record automatic generation method processes the received fault information and generates fault records that are displayed on the visualization terminal.
[0155] Understandable. Figure 5 or Figure 6 The corresponding system units can execute Figures 1-4 Therefore, the relevant steps of the corresponding method embodiment can also be incorporated into the method. Figure 5 or Figure 6 In the embodiments described herein, further details will not be provided here.
[0156] To address the problem of low fault handling efficiency caused by existing technologies that use a unified fault handling process or model for fault response, or simply employ a multi-process model for fault load balancing without fully considering the specific information of the fault category and the potential blocking or idle states of each process area, the technical solution of this invention stores multiple fault handling processes of different categories in a shared storage area. After receiving fault information, the fault category is parsed, and then multiple target processing processes corresponding to different shared storage areas are determined. Process migration is performed based on the actual running state, ensuring that the running process in the shared storage area used to handle the current fault category is always in a state of maximum efficiency and optimal adaptation. This ensures that the current type of fault can be processed in a timely manner and fault records can be generated, while avoiding process blocking or idle processes, thus improving fault handling efficiency. At the same time, the setting method of periodically judging the status of the target shared storage area and performing initialization and recovery can also avoid data accumulation errors.
[0157] It should be noted that the present invention can solve multiple technical problems or achieve corresponding technical effects, but it is not required that every embodiment of the present invention solves all technical problems or achieves all technical effects. An embodiment that solves one or several technical problems or obtains one or more improved effects also constitutes a separate technical solution.
Claims
1. A standardized fault log automatic generation method, the method being implemented based on at least one shared storage area, each of the shared storage areas storing multiple fault handling processes; characterized in that: The method includes the following steps: S1: Obtain the currently received fault information; S2: Parse the fault information and obtain the category of the fault information; further includes: broadcasting the fault information category to all shared storage areas; in the initial state, each shared storage area stores multiple fault handling processes, and each fault handling process corresponds to a different category of fault information; S3: Based on the category of the fault information, determine the target fault handling process corresponding to the category; S4: Based on the target fault handling process, determine multiple target shared storage areas, wherein each target shared storage area contains a target fault handling process corresponding to the category; the target shared storage area includes a first target shared storage area and a second target shared storage area, wherein the first target shared storage area contains a first target fault handling process corresponding to the category; and the second target shared storage area contains a second target fault handling process corresponding to the category. S5: Based on the status of all fault handling processes stored in each of the shared storage areas, migrate the first target fault handling process or the second target fault handling process, and process the currently received fault information, wherein the status includes resource occupancy rate; S6: Generate fault record output.
2. The standardized fault record automatic generation method as described in claim 1, characterized in that: The step of migrating the first target fault handling process or the second target fault handling process based on the status of all fault handling processes stored in each of the shared storage areas specifically includes: Determine the first resource occupancy ratio of the first target fault handling process in the first target shared storage area; Determine the second resource occupancy ratio of the second target fault handling process in the second target shared storage area; If the first resource occupancy ratio is greater than the second resource occupancy ratio, then the second target fault handling process is migrated from the second target shared storage area to the first target shared storage area; the first target shared storage area receives the currently received fault information and automatically generates fault records. If the first resource occupancy ratio is less than the second resource occupancy ratio, the first target fault handling process is migrated from the first target shared storage area to the second target shared storage area; the second target shared storage area receives the currently received fault information and automatically generates fault records.
3. The standardized fault record automatic generation method as described in claim 1, characterized in that: Step S5 further includes: Based on the status of all fault handling processes stored in each of the shared storage areas, a target shared storage area is determined for receiving the currently received fault information and automatically generating fault records. Determine the target status of all target fault handling processes contained in the target shared storage area, and based on all target statuses, determine whether to perform the initialization operation of the target shared storage area.
4. A visualization terminal, the visualization terminal comprising a memory and a processor, wherein the processor executes executable instruction code stored in the memory to process received fault information by executing the standardized fault record automatic generation method according to any one of claims 1-3, and generates fault records to be displayed on the visualization terminal.