A method and device for controlling and managing the sequence of power information system fault disposal and abnormal fusing based on a model agent, an equipment and a storage medium

Abstract

The application discloses a model agent-based power information system fault disposal sequence management and control and abnormal fusing method and device, equipment and storage medium, wherein the method comprises: in the case that the power information system fails, acquiring fault disposal data corresponding to the power information system; determining label information corresponding to the fault disposal data based on a model agent, and obtaining to-be-verified fault disposal data with labeled information based on the label information; determining a fault processing step based on the to-be-verified fault disposal data; verifying the processing order of the fault processing step based on standard verification information included in a knowledge base, and obtaining a verification result; in the case that the verification result indicates that the processing order verification fails, sending an abnormal fusing instruction to a user terminal; the abnormal fusing instruction is used for indicating to stop all current fault disposal operations. By using the method, the intelligent level of the power information system fault disposal management and control can be improved.

Description

Technical Field

[0001] This application relates to the field of information technology, and in particular to a method, apparatus, equipment and storage medium for fault handling sequence control and abnormal circuit breaking in power information systems based on model-based intelligent agents. Background Technology

[0002] As power information systems develop towards intelligence and large-scale operation, the requirements for timeliness and accuracy in fault handling are increasing for various power services (such as dual-machine hot standby server operation, power data transmission, and equipment maintenance). Fault handling in power information systems must strictly adhere to power information safety regulations and operational standards. The correctness of the fault handling sequence directly determines the efficiency of fault repair and the safety of operation and maintenance. If the sequence is disordered, it may lead to business interruptions, data inconsistencies, or even trigger larger-scale power information system failures, causing serious economic losses and social impact.

[0003] Currently, fault handling in power information systems largely relies on maintenance personnel manually executing operational steps, combined with manual judgment and verification of the operational sequence. As the complexity of power information systems increases, manual operation is not only inefficient but also prone to errors in the sequence due to human negligence. Furthermore, existing fault handling and control technologies lack intelligent constraints and data verification for fault handling steps, resulting in low accuracy and efficiency in controlling the fault handling sequence. In addition, existing fault handling and control technologies cannot promptly identify and trigger circuit breakers when the fault handling sequence is disordered or violates power information security, leading to the continued execution of erroneous operations and further amplifying the impact of the fault. Therefore, the current level of intelligence in fault handling and control technologies is low.

[0004] Therefore, how to improve the intelligence level of fault management in power information systems has become an urgent problem to be solved. Summary of the Invention

[0005] This application provides a method, apparatus, equipment, and storage medium for fault handling sequence control and abnormal circuit breaking in power information systems based on model-based intelligent agents, which can improve the intelligence level of fault handling control in power information systems.

[0006] In a first aspect, embodiments of this application provide a method for fault handling sequence control and abnormal circuit breaker tripping in a power information system based on a model-based intelligent agent. The method includes:

[0007] In the event of a failure in the power information system, obtain the corresponding fault handling data of the power information system;

[0008] The model agent determines the label information corresponding to the fault handling data, and based on the label information, obtains the fault handling data to be verified with labeled information; the model agent is used to identify the label information corresponding to the input fault handling data based on multiple pre-set classification labels and output it.

[0009] Determine the fault handling steps based on the fault handling data to be verified;

[0010] Based on the standard verification information included in the knowledge base, the processing order of the fault handling steps is verified to obtain the verification results.

[0011] If the verification result indicates that the processing order verification has failed, an abnormal circuit breaker command is sent to the user terminal; the abnormal circuit breaker command is used to instruct the cessation of all current fault handling operations.

[0012] In one embodiment, determining the label information corresponding to the fault handling data based on the model agent includes: inputting the fault handling data into the feature extraction module included in the model agent to obtain the data features of the fault handling data; inputting the data features into the classification module included in the model agent to obtain the initial label information corresponding to the fault handling data; sending the initial label information to the user terminal; and receiving confirmation feedback information or correction feedback information from the user terminal regarding the initial label information to obtain the label information corresponding to the fault handling data.

[0013] In one embodiment, the standard verification information included in the knowledge base includes standard data corresponding to various fault types. The method further includes: obtaining target standard data corresponding to the current fault type from the standard data corresponding to various fault types, and performing data verification on the fault handling data to be verified based on the target standard data to obtain a data verification result; and verifying the processing order of the fault handling steps based on the standard verification information included in the knowledge base to obtain a verification result, including: if the data verification result indicates that the data verification is passed, obtaining the target standard fault handling steps corresponding to the current fault type from the standard fault handling steps corresponding to various fault types, and verifying the processing order of the fault handling steps based on the target standard fault handling steps to obtain a verification result.

[0014] In one embodiment, the fault handling data to be verified includes equipment status data and currently executed fault handling operation data. Based on the target standard data, the fault handling data to be verified is verified to obtain a data verification result, including: verifying the equipment status data based on the standard status data included in the target standard data to obtain a first verification result; verifying the currently executed fault handling operation data based on the standard handling operation data included in the target standard data to obtain a second verification result; and obtaining a data verification result based on the first verification result and the second verification result.

[0015] In one embodiment, based on the target standard fault handling steps, the processing order of the fault handling steps is verified to obtain a verification result, including: comparing the fault handling steps with the target standard fault handling steps to obtain a comparison result; if the comparison result indicates that the processing order of the fault handling steps and the target standard fault handling steps is consistent, the verification result is determined to be that the processing order verification is passed; or, if the comparison result indicates that the processing order of the fault handling steps and the target standard fault handling steps is inconsistent, the verification result is determined to be that the processing order verification is failed.

[0016] In one embodiment, the method further includes: sending an abnormal circuit breaker command and a prompt message to the user terminal if the data verification result indicates that the data verification has failed; the prompt message is used to indicate that the data verification has failed.

[0017] In one embodiment, when sending an abnormal circuit breaker command to the user terminal, the method further includes: sending a warning message to the user terminal, the warning message including at least one of the following: the cause of the abnormal circuit breaker, the fault handling steps for the error, and a suggestion for the correct fault handling steps.

[0018] Secondly, this application provides a power information system fault handling sequence control and abnormal circuit breaker device based on model-based intelligent agents, the device comprising:

[0019] The acquisition module is used to acquire fault handling data corresponding to the power information system in the event of a fault in the power information system.

[0020] The determination module is used to determine the label information corresponding to the fault handling data based on the model agent, and to obtain the fault handling data to be verified with labeled information based on the label information; the model agent is used to identify the label information corresponding to the input fault handling data based on multiple pre-set classification labels and output it.

[0021] The determination module is also used to determine the fault handling steps based on the fault handling data to be verified;

[0022] The verification module is used to verify the processing order of fault handling steps based on the standard verification information included in the knowledge base, and obtain the verification result.

[0023] The sending module is used to send an abnormal circuit breaker command to the user terminal when the verification result indicates that the processing order verification has failed; the abnormal circuit breaker command is used to instruct the cessation of all current fault handling operations.

[0024] Thirdly, this application provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the method provided in the first aspect.

[0025] Fourthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method provided in the first aspect.

[0026] Fifthly, this application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps in the method provided in the first aspect.

[0027] The aforementioned model-based intelligent agent-based method, device, equipment, and storage medium for power information system fault handling sequence control and abnormal circuit breaker mechanism, in the event of a power information system fault, acquires the corresponding fault handling data of the power information system; determines the tag information corresponding to the fault handling data based on the model-based intelligent agent, and obtains fault handling data to be verified with labeled information based on the tag information; the model-based intelligent agent is used to identify and output the tag information corresponding to the input fault handling data based on multiple pre-set classification tags; determines the fault handling steps based on the fault handling data to be verified; verifies the processing order of the fault handling steps based on the standard verification information included in the knowledge base, and obtains the verification result; if the verification result indicates that the processing order verification has failed, an abnormal circuit breaker command is sent to the user terminal; the abnormal circuit breaker command is used to instruct the cessation of all current fault handling operations. This method utilizes a model agent to semi-automatically annotate fault handling data, obtaining annotated fault handling data to be verified. Then, based on this data, fault handling steps are determined, and the processing order is verified using standard verification information in a knowledge base. If the processing order verification fails, an abnormal circuit breaker mechanism is immediately triggered, stopping the current erroneous operation and issuing a warning. This enables precise control of fault handling steps, efficient data verification, and timely blocking of anomalies. Therefore, it not only improves the accuracy and efficiency of fault handling sequence control in power information systems but also promptly identifies and triggers circuit breakers, minimizing the continued execution of erroneous operations. Clearly, this method enhances the intelligence level of fault management in power information systems. Attached Figure Description

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

[0029] Figure 1 This is a flowchart illustrating a method for fault handling sequence control and abnormal circuit breaking in a power information system based on a model-based intelligent agent, provided in an embodiment of this application.

[0030] Figure 2 This is a flowchart illustrating another method for fault handling sequence control and abnormal circuit breaking in a power information system based on a model-based intelligent agent, provided in an embodiment of this application.

[0031] Figure 3 This is a schematic diagram of the structure of a power information system fault handling sequence control and abnormal fuse device based on a model intelligent agent, provided in an embodiment of this application;

[0032] Figure 4 This is a schematic diagram of another power information system fault handling sequence control and abnormal fuse device based on model intelligent agents provided in this application embodiment;

[0033] Figure 5 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application. Detailed Implementation

[0034] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0035] Please see Figure 1 , Figure 1 This is a flowchart illustrating a method for fault handling sequence control and abnormal circuit breaker tripping in a power information system based on a model-based intelligent agent, provided in an embodiment of this application. This method can be executed by a computer device. Optionally, the computer device can be a terminal device or a server. The terminal devices mentioned here can include, but are not limited to, various personal computers, laptops, smartphones, tablets, IoT devices, and portable wearable devices. IoT devices can be smart TVs, smart air conditioners, smart in-vehicle devices, projection devices, etc., and portable wearable devices can be smartwatches, smart bracelets, head-mounted devices, etc. The server mentioned here can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud computing services, etc., without limitation. The following describes the method using a server executing the method as an example. Figure 1 As shown, the fault handling sequence control and abnormal circuit breaker method for power information systems based on model-based intelligent agents may include, but is not limited to, the following steps:

[0036] S101. In the event of a fault in the power information system, obtain the corresponding fault handling data of the power information system.

[0037] Fault handling data refers to all data generated and recorded during the discovery, location, and repair process after a fault occurs in a power information system or equipment. In some embodiments, fault handling data may include, but is not limited to, the current fault type, faulty equipment identifier, equipment status data (such as synchronization rate, service status, etc.), and operation and maintenance data (such as operation instructions, operation time, etc.). The operation and maintenance data page can be referred to as fault handling steps.

[0038] In one optional implementation, when a fault occurs in the power information system, the server acquires corresponding fault handling data for the power information system. This may include: receiving a fault handling request from a user terminal and equipment status data from the faulty device; the fault handling request includes initial fault handling data; and determining the corresponding fault handling data for the power information system based on the initial fault handling data and the equipment status data. Optionally, the initial fault handling data may include, but is not limited to, the current fault type, the faulty device identifier, and the current fault handling steps.

[0039] S102. Determine the label information corresponding to the fault handling data based on the model agent, and obtain the fault handling data to be verified with annotation information based on the label information.

[0040] The model agent is used to identify and output the label information corresponding to the input fault handling data based on multiple pre-set classification labels.

[0041] Among them, the model agent refers to an intelligent model with the ability to collect, process, analyze, and make decisions based on data. It can achieve semi-automatic data labeling, verification, and command output through preset algorithms to assist in completing fault handling and management tasks. Semi-automatic data labeling refers to the process of automatically labeling data initially through the model agent, followed by manual confirmation and correction. This combination of automation and manual operation completes the data labeling process, balancing labeling efficiency and accuracy.

[0042] In one optional implementation, the server determines the label information corresponding to the fault handling data based on the model agent, which may include: inputting the fault handling data into the model agent to obtain the initial label information corresponding to the fault handling data; confirming and correcting the initial label information to obtain the label information corresponding to the fault handling data.

[0043] S103. Determine the fault handling steps based on the fault handling data to be verified.

[0044] In some embodiments, the server determines fault handling steps based on fault handling data to be verified, which may include: extracting fault handling steps from the fault handling data to be verified.

[0045] S104. Verify the processing order of the fault handling steps based on the standard verification information included in the knowledge base, and obtain the verification results.

[0046] The knowledge base pre-stores standard verification information, which may include, but is not limited to, standard fault handling steps (including sequence requirements) corresponding to various fault types, power information security rules, operating procedures, and safety prohibition lists.

[0047] Among them, the power information security rules refer to the security specifications that must be followed during the operation and maintenance of power information systems. They are used to constrain the operational behavior of operation and maintenance personnel and prevent safety accidents and the escalation of faults.

[0048] S105. If the verification result indicates that the processing order verification has failed, send an abnormal circuit breaker command to the user terminal; the abnormal circuit breaker command is used to indicate the cessation of all current fault handling operations.

[0049] In one optional implementation, if the server sends an abnormal circuit breaker command to the user terminal when the verification result indicates that the processing order verification has failed, it may include: determining whether a power information security prohibition included in the knowledge base is matched when the verification result indicates that the processing order verification has failed; if a power information security prohibition included in the knowledge base is matched, then sending an abnormal circuit breaker command to the user terminal.

[0050] For example, matching the power information security prohibitions included in the knowledge base, such as executing a switching command without performing a standby status pre-check, or matching the security prohibition that "a standby status pre-check is required before switching between two machines," etc.

[0051] In this embodiment, a model agent is used to semi-automatically annotate fault handling data to obtain fault handling data to be verified with annotated information. Then, fault handling steps are determined based on the fault handling data to be verified, and the processing order of the fault handling steps is verified based on the standard verification information included in the knowledge base. If the processing order verification fails, an abnormal circuit breaker mechanism is immediately triggered to stop the current erroneous operation and issue an early warning. In this way, precise control of fault handling steps, efficient data verification, and timely blocking of anomalies can be achieved. This not only improves the accuracy and efficiency of fault handling order control in power information systems, but also enables timely identification and triggering of circuit breakers to avoid the continuous execution of erroneous operations as much as possible. It is evident that this method can improve the intelligence level of fault control in power information systems.

[0052] In one alternative implementation, Figure 1 In step S102 of the power information system fault handling sequence control and abnormal circuit breaker method based on model intelligent agents, the method by which the server determines the tag information corresponding to the fault handling data based on the model intelligent agent may include: inputting the fault handling data into the feature extraction module included in the model intelligent agent to obtain the data features of the fault handling data; inputting the data features into the classification module included in the model intelligent agent to obtain the initial tag information corresponding to the fault handling data; sending the initial tag information to the user terminal; and receiving confirmation feedback information or correction feedback information from the user terminal regarding the initial tag information to obtain the tag information corresponding to the fault handling data.

[0053] In some embodiments, the model agent may include, but is not limited to, a data input layer, a feature extraction layer, a labeling layer, and a verification layer; wherein, the data input layer can be used to receive fault handling data (data uploaded by user terminals and faulty equipment) corresponding to the power information system; the feature extraction layer can be used to extract data features of the fault handling data (such as numerical features of equipment status data, text features of the current fault handling steps, etc.) through feature extraction networks (such as convolutional neural networks, recurrent neural networks, Transformers, etc.); the labeling layer can be used to automatically label the extracted data features based on a pre-trained classification model to generate initial label information; the verification layer can be used to compare and verify the labeled data and operation data based on standard data in the knowledge base and output the verification results.

[0054] The standard layer is based on a pre-trained classification model. It automatically labels the extracted data features and generates initial label information. For example, the data features of the device status data are input into the pre-trained classification model, and the device status data is labeled as "standby synchronization data" or "master service data", and the operation data is labeled as "pre-inspection operation" or "isolation operation".

[0055] In some embodiments, the feature extraction module of the model agent includes, but is not limited to, convolutional neural networks, recurrent neural networks, and Transformers.

[0056] In some embodiments, after the server sends initial tag information to the user terminal, the user terminal may output the initial tag information; detect confirmation feedback information or correction feedback information regarding the initial tag information; and send confirmation feedback information or correction feedback information regarding the initial tag information to the server.

[0057] The confirmation feedback information for the initial tag information can be obtained after confirming the initial tag information. For example, assuming the initial tag information is "standby machine synchronization data", and the maintenance personnel confirm "standby machine synchronization data" through the user terminal, the confirmation feedback information can be "standby machine synchronization data". In this case, the tag information corresponding to the fault handling data can include "standby machine synchronization data".

[0058] The correction feedback information for the initial tag information can be obtained after correcting the initial tag information. For example, assuming the initial tag information is "standby machine synchronization data", and the maintenance personnel change "standby machine synchronization data" to "primary machine synchronization data" through the user terminal, the correction feedback information can be "primary machine synchronization data". In this case, the tag information corresponding to the fault handling data can include "primary machine synchronization data".

[0059] This implementation method uses a model agent to perform semi-automatic assisted annotation of fault handling data to obtain initial label information for the fault handling data. The initial label information is then manually confirmed and corrected. Compared with the method of completely manual annotation, this method can not only improve the efficiency of data annotation, but also improve the accuracy of data annotation.

[0060] In one alternative implementation, Figure 1 The power information system fault handling sequence control and abnormal circuit breaker method based on model intelligent agent shown includes standard verification information in the knowledge base, which includes standard data corresponding to various fault types. Figure 1 The method shown may further include: the server obtaining target standard data corresponding to the current fault type from standard data corresponding to various fault types, and performing data verification on the fault handling data to be verified based on the target standard data to obtain a data verification result; step S104, that is, the server verifying the processing order of the fault handling steps based on the standard verification information included in the knowledge base to obtain a verification result, may include: when the data verification result indicates that the data verification is passed, obtaining the target standard fault handling steps corresponding to the current fault type from the standard fault handling steps corresponding to various fault types, and performing processing order verification on the fault handling steps based on the target standard fault handling steps to obtain a verification result.

[0061] In some embodiments, the standard data may include, but is not limited to, standard parameters for standby status pre-inspection, operational requirements for host service isolation, standard status data corresponding to equipment status pre-inspection, and standard processing operation data corresponding to the current fault type.

[0062] In some embodiments, the fault handling data to be verified includes equipment status data and currently executed fault handling operation data. The server performs data verification on the fault handling data to be verified based on target standard data to obtain a data verification result. This verification may include: verifying the equipment status data based on standard status data included in the target standard data to obtain a first verification result; verifying the currently executed fault handling operation data based on standard processing operation data included in the target standard data to obtain a second verification result; and obtaining a data verification result based on the first and second verification results. Thus, by verifying both the equipment status data and the currently executed fault operation data, and determining the data verification result based on the verification results of both, the accuracy of data verification can be improved.

[0063] Optionally, the server verifies the device status data based on the standard status data included in the target standard data to obtain a first verification result. This can include: verifying the authenticity and completeness of the device status data based on the standard status data included in the target standard data to obtain a first verification result. The server's verification of the authenticity and completeness of the device status data can, for example, determine whether the backup machine data synchronization meets the standards or whether the service is ready.

[0064] The server verifies the authenticity and completeness of the device status data based on the standard status data included in the target standard data, and obtains a first verification result. This may include: obtaining the data threshold corresponding to the device status data from the standard status data included in the target standard data; comparing the device status data with the corresponding data threshold to obtain a comparison result; and determining the first verification result as verified if the comparison result indicates that the device status data is greater than or equal to the corresponding data threshold.

[0065] For example, assuming the device status data is the standby synchronization rate, and the data threshold corresponding to the standby synchronization rate is 95%, in this case, the server can determine the first verification result as verification passed if the device status data is greater than or equal to 95%.

[0066] Optionally, the server verifies the currently executed fault handling operation data based on the standard processing operation data included in the target standard data to obtain a second verification result. This verification may include: verifying whether the currently executed fault handling operation data matches the standard processing operation data corresponding to the current fault type based on the standard processing operation data included in the target standard data; if yes, the second verification result is determined to be verification passed; if no, the second verification result is determined to be verification failed. Specifically, the server verifies whether the currently executed fault handling operation data matches the standard processing operation data corresponding to the current fault type, for example, by verifying whether the currently executed fault handling operation data belongs to the standard processing operation data corresponding to the current fault type.

[0067] For example, suppose the standard handling operation data corresponding to the current fault type is that host service isolation requires closing a specified port. If the currently executed fault handling operation data is that host service isolation has already closed the specified port, then the server can determine that the currently executed fault handling operation data matches the standard handling operation data corresponding to the current fault type. If the currently executed fault handling operation data is that host service isolation has not closed the specified port, then the server can determine that the currently executed fault handling operation data does not match the standard handling operation data corresponding to the current fault type.

[0068] Optionally, the server obtains a data verification result based on the first verification result and the second verification result, which may include: if both the first verification result and the second verification result are verified as passed, determining that the data verification result indicates that the data verification is passed; if either the first verification result or the second verification result is verified as failed, determining that the data verification result indicates that the data verification is failed.

[0069] In some embodiments, the server may also send an abnormal circuit breaker command and a prompt message to the user terminal if the data verification result indicates that the data verification has failed; the prompt message is used to indicate that the data verification has failed. This allows maintenance personnel to be notified of data verification failure in a timely manner and take relevant measures.

[0070] Optionally, the prompt message may also include, but is not limited to, the marked abnormal data items, the reasons for the data abnormality, and correction suggestions.

[0071] In some embodiments, the server verifies the processing order of fault handling steps based on the target standard fault handling steps to obtain a verification result. This may include: comparing the fault handling steps with the target standard fault handling steps to obtain a comparison result; if the comparison result indicates that the processing order of the fault handling steps and the target standard fault handling steps is consistent, determining that the verification result is that the processing order verification is successful; or, if the comparison result indicates that the processing order of the fault handling steps and the target standard fault handling steps is inconsistent, determining that the verification result is that the processing order verification is unsuccessful.

[0072] For example, suppose the target standard fault handling steps are "standby status pre-check → primary service isolation → execute switchover command → verification / repair / redundancy". Assume the fault handling step is standby status pre-check. In this case, the server can determine that standby status pre-check is the first step, and the order is correct. At this point, the server can compare the results to indicate that the fault handling steps and the target standard fault handling steps are in the same order, thus the server can determine that the verification result is that the processing order verification passed. However, suppose the operations and maintenance personnel skip the standby status pre-check step and directly execute primary service isolation. In this case, the server can determine that the steps are incorrect. The server can then determine that the comparison results indicate that the fault handling steps and the target standard fault handling steps are incompatible, thus the server can determine that the verification result is that the processing order verification failed.

[0073] In some embodiments, the server may also send an early warning message to the user terminal when sending an abnormal circuit breaker command. The early warning message includes at least one of the following: the reason for the abnormal circuit breaker, the fault handling procedure for the error, and a suggestion for the correct fault handling procedure. This allows maintenance personnel to adjust the fault handling procedure promptly based on the early warning message output from the user terminal.

[0074] Optionally, the terminal device may output alarm information upon receiving a warning message. The alarm information is used to indicate that the fault handling steps are abnormal.

[0075] Optionally, alarm information may include, but is not limited to, light alarm information and voice alarm information. Light alarm information may include: an indicator light flashing continuously N times, where N is an integer greater than or equal to 2; the indicator light remaining constantly on for a preset duration; or the indicator light being red, etc., without limitation. Voice alarm information may include, for example, outputting the voice message "Fault handling steps are abnormal".

[0076] By adopting this implementation method, when the data verification result indicates that the data verification has passed, the processing order of the fault handling steps is verified based on the target standard fault handling steps corresponding to the current fault type. In this way, through the double verification method, the order of fault handling steps can be accurately controlled, and problems such as inconsistency between business terminals and data caused by disordered fault handling steps can be avoided as much as possible.

[0077] The following is a general description of the fault handling sequence control and abnormal circuit breaker method for power information systems based on model-based intelligent agents provided in the embodiments of this application. Please refer to... Figure 2 , Figure 2 This is a flowchart illustrating another method for fault handling sequence control and abnormal circuit breaker tripping in a power information system based on a model-based intelligent agent, as provided in this application embodiment. Figure 2 As shown, the fault handling sequence control and abnormal circuit breaker method for power information systems based on model-based intelligent agents may include, but is not limited to, the following steps:

[0078] S201. The user terminal sends a fault handling request to the server. Correspondingly, the server receives the fault handling request from the user terminal, which includes initial fault handling data.

[0079] Initial fault handling data may include, but is not limited to, the current fault type, faulty device identifier, and current fault handling steps.

[0080] S202. The faulty device sends device status data to the server, and the server receives the device status data from the faulty device accordingly.

[0081] It should be noted that this application does not limit the execution order of steps S201 and S202. In other words, the server may first receive the fault handling request from the user terminal and then receive the device status data from the faulty device; the server may also first receive the device status data from the faulty device and then receive the fault handling request from the user terminal; or the server may simultaneously receive the device status data from the faulty device and the fault handling request from the user terminal.

[0082] S203. The server obtains initial fault handling data based on the fault handling request.

[0083] In one alternative implementation, the server obtains initial fault handling data based on the fault handling request, which may include: parsing the fault handling request and obtaining the initial fault handling data from the parsing result.

[0084] S204. The server determines the fault handling data based on the initial fault handling data and equipment status data.

[0085] In one optional implementation, the server determines fault handling data based on initial fault handling data and device status data, which may include: integrating the initial fault handling data and device status data to obtain fault handling data.

[0086] S205. The server inputs the fault handling data into the model agent and obtains the initial label information corresponding to the fault handling data.

[0087] In some embodiments, the server inputs fault handling data into the model agent to obtain initial label information corresponding to the fault handling data, which may include: inputting the fault handling data into the feature extraction module included in the model agent to obtain data features of the fault handling data; and inputting the data features into the classification module included in the model agent to obtain initial label information corresponding to the fault handling data.

[0088] S206. The server sends initial tag information to the user terminal, and the user terminal receives the initial tag information from the server.

[0089] S207. The user terminal detects confirmation feedback or correction feedback information for the initial tag information.

[0090] S208. The user terminal sends confirmation feedback information or correction feedback information to the server, and the server receives the confirmation feedback information or correction feedback information from the user terminal accordingly.

[0091] S209. Based on the confirmation feedback information or correction feedback information, the server determines the tag information corresponding to the fault handling data, and based on the tag information, obtains the fault handling data to be verified with annotation information.

[0092] S210. The server determines the fault handling steps based on the fault handling data to be verified.

[0093] S211. The server retrieves the target standard data corresponding to the current fault type from the standard data corresponding to various fault types included in the knowledge base.

[0094] S212. The server performs data verification on the fault handling data to be verified based on the target standard data, and obtains the data verification results.

[0095] In some embodiments, the fault handling data to be verified includes device status data and currently executed fault handling operation data; the server verifies the fault handling data to be verified based on the target standard data to obtain the data verification result in the following ways: verifying the device status data based on the standard status data included in the target standard data to obtain a first verification result; verifying the currently executed fault handling operation data based on the standard processing operation data included in the target standard data to obtain a second verification result; and obtaining the data verification result based on the first verification result and the second verification result.

[0096] Optionally, the server obtains a data verification result based on the first verification result and the second verification result, which may include: if both the first verification result and the second verification result are verified as passed, determining that the data verification result indicates that the data verification is passed; if either the first verification result or the second verification result is verified as failed, determining that the data verification result indicates that the data verification is failed.

[0097] S213. The server determines whether the data verification result indicates that the data verification has passed. If yes, then proceed to steps S214 to S218; otherwise, proceed to step S219.

[0098] S214. The server retrieves the target standard fault handling steps corresponding to the current fault type from the standard fault handling steps corresponding to various fault types included in the knowledge base.

[0099] S215. The server verifies the processing order of the fault handling steps based on the target standard fault handling steps and obtains the verification results.

[0100] In some embodiments, the server verifies the processing order of fault handling steps based on the target standard fault handling steps to obtain a verification result. This may include: comparing the fault handling steps with the target standard fault handling steps to obtain a comparison result; if the comparison result indicates that the processing order of the fault handling steps and the target standard fault handling steps is consistent, determining that the verification result is that the processing order verification is successful; or, if the comparison result indicates that the processing order of the fault handling steps and the target standard fault handling steps is inconsistent, determining that the verification result is that the processing order verification is unsuccessful.

[0101] S216. The server determines whether the verification result indicates that the processing order verification failed. If yes, then proceed to step S217; otherwise, proceed to step S218.

[0102] S217. When the server matches a security ban included in the knowledge base, it sends an abnormal circuit breaker command and warning information to the user terminal. Correspondingly, the user terminal receives the abnormal circuit breaker command and warning information from the server.

[0103] The abnormal circuit breaker command is used to instruct the cessation of all current fault handling operations; the warning information includes at least one of the following: the cause of the abnormal circuit breaker, the fault handling steps that were erroneous, and a suggestion for the correct fault handling steps.

[0104] S218. The server sends a continue operation instruction to the user terminal, and the user terminal receives the continue operation instruction from the server accordingly; the continue operation execution is used to instruct the continued execution of fault handling operations.

[0105] S219. The server sends an abnormal circuit breaker command and a prompt message to the user terminal. Correspondingly, the user terminal receives the abnormal circuit breaker command and prompt message from the server. The prompt message is used to indicate that the data verification failed.

[0106] As can be seen from the above description, the abnormal circuit breaker triggering conditions may include any of the following: (1) Data verification fails (such as abnormal equipment status data, operation steps not conforming to basic specifications, etc.); (2) Processing sequence verification fails and matches the safety prohibition included in the knowledge base (such as executing the switching command without performing standby status pre-check, matching the safety prohibition "dual machine switching requires pre-checking standby status first").

[0107] In some embodiments, the abnormal circuit breaker triggering condition may further include: the duration of abnormal device status data is greater than or equal to a preset duration. The preset duration may be determined based on expert experience, or it may be determined based on multiple tests, etc., and is not limited here.

[0108] The following example illustrates a scenario involving failover of a dual-machine hot standby server. Figure 2 The following example illustrates a model-based intelligent agent-based fault handling sequence control and abnormal circuit breaker method for power information systems. Specifically, this scenario involves a dual-machine hot standby server experiencing a primary server failure, requiring a switchover operation to ensure normal service operation. Dual-machine hot standby refers to the simultaneous operation of two servers (primary and backup). When the primary server fails, the backup server can quickly take over the primary server's services, ensuring uninterrupted service operation. In this scenario, the model-based intelligent agent-based fault handling sequence control and abnormal circuit breaker method for power information systems may include, but is not limited to, the following steps:

[0109] Step 1: Data collection and semi-automated annotation.

[0110] Maintenance personnel can send a dual-machine switchover fault handling request to the server through the user terminal. The user terminal uploads initial fault handling data such as "Fault Type - Dual-machine Switchover" and "Faulty Devices - Main A, Standby B". Standby B uploads device status data to the server (data synchronization rate 98%, service ready status "Yes"). After receiving the above data, the server automatically labels it with tags such as "Fault Type - Dual-machine Switchover" and "Standby Status Data - Synchronization Rate 98%, Service Ready", and pushes it to the user terminal. After the maintenance personnel confirm that the tags are correct through the user terminal, they send a confirmation feedback message to the server through the user terminal. Based on the confirmation feedback message, the server determines the tag information of the above data and completes the labeling of the above data based on the tag information.

[0111] Step 2: Data verification.

[0112] The server can call the "Dual-machine Switchover Standby Pre-inspection Standard" (data synchronization rate ≥ 95%, service ready) in the knowledge base to verify the status data of standby machine B, confirm that the verification is passed, generate a verification report, and send it to the sequence constraint verification module and the terminal.

[0113] Step 3: Sequence constraint verification.

[0114] The maintenance personnel perform the first step, "Standby Status Pre-check," via the user terminal. The server collects and labels the operation data through a model agent. The labeled operation data is then verified. If verification is successful, the labeled operation data is compared with the standard processing order. If this step is confirmed as the first step, the order is considered correct, and the next step is allowed. The maintenance personnel then perform the second step, "Host Service Isolation" (closing the service port of Host A), via the user terminal. The server collects and labels the operation data through a model agent. The labeled operation data is then verified. If verification is successful, the labeled operation data is compared with the standard processing order. If the step order is confirmed as correct, the next step is allowed. However, if the maintenance personnel skip the "Standby Status Pre-check" and directly execute the "Execute Switchover Command" via the user terminal, the server collects and labels the operation data through a model agent. The labeled operation data is then verified. If verification is successful, the labeled operation data is compared with the standard processing order. If the steps are found to be disordered and match the safety regulation prohibition "Dual-machine switchover requires standby status pre-check," then the server is confirmed to have encountered an anomaly.

[0115] Step 3: Abnormal circuit breaker failure.

[0116] If an anomaly is detected, the server can determine whether the circuit breaker condition has been triggered. If so, it sends an abnormal circuit breaker command to the user terminal to instruct the "execute switchover command" operation to stop. Simultaneously, it sends the following warning information to the user terminal: incorrect step sequence, standby status pre-check not performed, violation of power information safety regulations, operation stopped, please perform standby status pre-check first. In this case, maintenance personnel can re-execute the "standby status pre-check" steps based on the warning information, and subsequent procedures will be executed in the standard order until the fault is resolved.

[0117] In this embodiment, on the one hand, a semi-automatic annotation of fault handling data is completed through a model intelligence agent to obtain fault handling data to be verified with annotation information. Then, fault handling steps are determined based on the fault handling data to be verified, and the processing order of the fault handling steps is verified based on the standard verification information included in the knowledge base. If the processing order verification fails, an abnormal circuit breaker mechanism is immediately triggered to stop the current erroneous operation and issue an early warning. In this way, precise control of fault handling steps, efficient data verification, and timely blocking of anomalies can be achieved. This not only improves the accuracy and efficiency of fault handling order control in the power information system, but also enables timely identification and triggering of circuit breakers to avoid the continued execution of erroneous operations as much as possible. On the other hand, when the step order is disordered, a safety regulation prohibition is matched, or data verification fails, an abnormal circuit breaker mechanism is immediately triggered (a mechanism that immediately stops the current operation and issues an early warning when violations such as disordered step order or data anomalies are detected during fault handling to block the continued execution of erroneous operations). This stops the erroneous operation and issues an early warning, which can effectively block the continued execution of erroneous operations and reduce the scope of fault impact. This solves the problem that anomalies cannot be blocked in time and faults are easy to expand in the prior art.

[0118] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0119] Based on the same inventive concept, this application also provides a model-agent-based power information system fault handling sequence control and abnormal circuit breaker device for implementing the above-mentioned model-agent-based power information system fault handling sequence control and abnormal circuit breaker method. The solution provided by this device is similar to the solution described in the above method. Therefore, the specific limitations of one or more model-agent-based power information system fault handling sequence control and abnormal circuit breaker device embodiments provided below can be found in the limitations of the model-agent-based power information system fault handling sequence control and abnormal circuit breaker method described above, and will not be repeated here.

[0120] Please see Figure 3 , Figure 3 This is a schematic diagram of a fault handling sequence control and abnormal fuse device for a power information system based on a model-based intelligent agent, provided in an embodiment of this application. Figure 3 As shown, the fault handling sequence control and abnormal circuit breaker device for the power information system based on model intelligent agents may include, but is not limited to, a knowledge base module 301, a model intelligent agent module 302, a sequence constraint verification module 303, and an abnormal circuit breaker module 304.

[0121] Among them, the knowledge base module 301 is used to store data such as power information safety regulations, operation specifications, standard handling procedures (including sequence requirements) for various faults, and lists of safety regulations and prohibitions, providing data support for data verification of the model intelligent agent and sequence verification of the sequence constraint verification module.

[0122] The model intelligent agent module 302 serves as the core data processing module, responsible for the semi-automated auxiliary annotation and real-time verification of fault handling data. It receives operation data and equipment status data uploaded by user terminals, outputs verification results, and interacts with the sequence constraint verification module and the abnormal circuit breaker module.

[0123] The sequence constraint verification module 303 is used to receive the verification data output by the model agent module, combine it with the standard data of the knowledge base module, perform constraint verification on the sequence of fault handling steps, and output the verification result.

[0124] The abnormal circuit breaker module 304 is used to receive the verification result of the sequence constraint verification module, determine whether the abnormal circuit breaker condition is triggered, and if it is triggered, send a circuit breaker command to the terminal to stop the current operation and issue an early warning.

[0125] In this embodiment, the collaborative work of each module forms a closed-loop process of data acquisition, labeling, verification, sequential verification, abnormal circuit breaking, and operation adjustment, which ensures that the entire fault handling process is controllable and traceable, thereby improving the security and reliability of power information system operation and maintenance.

[0126] Please see Figure 4 , Figure 4 This is a schematic diagram of another power information system fault handling sequence control and abnormal fuse device based on a model-based intelligent agent, provided in an embodiment of this application. Figure 4 As shown, the fault handling sequence control and abnormal fuse tripping device of the power information system based on model-based intelligent agents may include, but is not limited to:

[0127] The acquisition module 401 is used to acquire the corresponding fault handling data of the power information system in the event of a fault in the power information system.

[0128] The determination module 402 is used to determine the label information corresponding to the fault handling data based on the model agent, and to obtain the fault handling data to be verified with labeled information based on the label information; the model agent is used to identify the label information corresponding to the input fault handling data based on multiple pre-set classification labels and output it.

[0129] The determination module 402 is also used to determine the fault handling steps based on the fault handling data to be verified;

[0130] The verification module 403 is used to verify the processing order of the fault handling steps based on the standard verification information included in the knowledge base, and obtain the verification result.

[0131] The sending module 404 is used to send an abnormal circuit breaker command to the user terminal when the verification result indicates that the processing order verification has failed; the abnormal circuit breaker command is used to indicate the cessation of all current fault handling operations.

[0132] In one embodiment, when determining the label information corresponding to the fault handling data based on the model agent, the determining module 402 is specifically used to: input the fault handling data into the feature extraction module included in the model agent to obtain the data features of the fault handling data; input the data features into the classification module included in the model agent to obtain the initial label information corresponding to the fault handling data; send the initial label information to the user terminal; and receive confirmation feedback information or correction feedback information from the user terminal regarding the initial label information to obtain the label information corresponding to the fault handling data.

[0133] In one embodiment, the standard verification information included in the knowledge base includes standard data corresponding to various fault types; the acquisition module 401 is further configured to acquire the target standard data corresponding to the current fault type from the standard data corresponding to various fault types; the verification module 403 is further configured to perform data verification on the fault handling data to be verified based on the target standard data, and obtain the data verification result; when the verification module 403 is used to verify the processing order of the fault handling steps based on the standard verification information included in the knowledge base and obtain the verification result, the acquisition module 401 is further configured to acquire the target standard fault handling steps corresponding to the current fault type from the standard fault handling steps corresponding to various fault types when the data verification result indicates that the data verification is passed; the verification module 403 is specifically configured to verify the processing order of the fault handling steps based on the target standard fault handling steps and obtain the verification result.

[0134] In one embodiment, the fault handling data to be verified includes equipment status data and currently executed fault handling operation data. When the verification module 403 performs data verification on the fault handling data to be verified based on the target standard data to obtain a data verification result, it is specifically used to: verify the equipment status data based on the standard status data included in the target standard data to obtain a first verification result; verify the currently executed fault handling operation data based on the standard handling operation data included in the target standard data to obtain a second verification result; and obtain a data verification result based on the first verification result and the second verification result.

[0135] In one embodiment, when the verification module 403 verifies the processing order of fault handling steps based on the target standard fault handling steps and obtains a verification result, it is specifically used to: compare the fault handling steps with the target standard fault handling steps and obtain a comparison result; if the comparison result indicates that the processing order of the fault handling steps and the target standard fault handling steps is consistent, determine that the verification result is that the processing order verification is passed; or, if the comparison result indicates that the processing order of the fault handling steps and the target standard fault handling steps is inconsistent, determine that the verification result is that the processing order verification is failed.

[0136] In one embodiment, the sending module 404 is further configured to send an abnormal circuit breaker command and a prompt message to the user terminal when the data verification result indicates that the data verification has failed; the prompt message is used to indicate that the data verification has failed.

[0137] In one embodiment, when the sending module 404 is used to send an abnormal circuit breaker command to the user terminal, it is also used to send a warning message to the user terminal. The warning message includes at least one of the following: the cause of the abnormal circuit breaker, the fault handling steps for the error, and a suggestion for the correct fault handling steps.

[0138] The modules in the aforementioned power information system fault handling sequence control and abnormal fuse device based on model-based intelligent agents can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in the processor of the terminal device in hardware form or independently of it, or stored in the memory of the terminal device in software form, so that the processor can call and execute the corresponding operations of each module.

[0139] In one exemplary embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 5 As shown, the computer device includes a processor, memory, input / output interfaces, a communication interface, a display unit, and an input device. The processor, memory, and input / output interfaces are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interfaces. The processor provides computational and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The input / output interfaces are used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, Near Field Communication (NFC), or other technologies. When the computer program is executed by the processor, it implements a model-based intelligent agent-based method for managing the fault handling sequence and abnormal circuit breaking in a power information system. The display unit of the computer device is used to form a visually visible image and can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen. The input device of the computer device can be a touch layer covering the display screen, or buttons, trackballs, or touchpads set on the casing of the computer device, or external keyboards, touchpads, or mice, etc.

[0140] Those skilled in the art will understand that Figure 5 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0141] In one exemplary embodiment, this application provides a computer device including a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the steps in the above-described model-based intelligent agent-based power information system fault handling sequence control and abnormal circuit breaker method.

[0142] In one exemplary embodiment, this application provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the steps in the above-described method for fault handling sequence control and abnormal circuit breaking in a power information system based on model-intelligent agents.

[0143] In one exemplary embodiment, this application provides a computer program product, including a computer program that, when executed by a processor, implements the steps in the above-described model-based intelligent agent-based power information system fault handling sequence control and abnormal circuit breaker method.

[0144] It should be noted that the data involved in this application (including but not limited to acquired data, data used for analysis, and stored data) are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with relevant regulations.

[0145] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory 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 many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0146] The technical features of the above embodiments can be combined in any way. For the sake of brevity, 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 application.

[0147] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A method for fault handling sequence control and abnormal circuit breaker tripping in a power information system based on model-based intelligent agents, characterized in that, The method includes: In the event of a failure in the power information system, acquire the corresponding failure handling data of the power information system; The model agent determines the label information corresponding to the fault handling data, and obtains the fault handling data to be verified with labeled information based on the label information; the model agent is used to identify the label information corresponding to the input fault handling data based on multiple pre-set classification labels and output it. Based on the fault handling data to be verified, determine the fault handling steps; Based on the standard verification information included in the knowledge base, the processing order of the fault handling steps is verified to obtain the verification result. If the verification result indicates that the processing sequence verification has failed, an abnormal circuit breaker command is sent to the user terminal; the abnormal circuit breaker command is used to instruct the cessation of all current fault handling operations.

2. The method according to claim 1, characterized in that, The step of determining the tag information corresponding to the fault handling data based on the model-based intelligent agent includes: The fault handling data is input into the feature extraction module included in the model agent to obtain the data features of the fault handling data; The data features are input into the classification module included in the model agent to obtain the initial label information corresponding to the fault handling data; Send the initial tag information to the user terminal; The system receives confirmation or correction feedback from the user terminal regarding the initial tag information, and obtains the tag information corresponding to the fault handling data.

3. The method according to claim 1, characterized in that, The knowledge base includes standard verification information, which includes standard data corresponding to various fault types. The method further includes: From the standard data corresponding to the various fault types, obtain the target standard data corresponding to the current fault type, and based on the target standard data, perform data verification on the fault handling data to be verified to obtain the data verification result; The processing order of the fault handling steps is verified based on the standard verification information included in the knowledge base, and the verification results are obtained, including: If the data verification result indicates that the data verification is successful, the target standard fault handling step corresponding to the current fault type is obtained from the standard fault handling steps corresponding to the various fault types respectively, and the processing order of the fault handling steps is verified based on the target standard fault handling step to obtain the verification result.

4. The method according to claim 3, characterized in that, The fault handling data to be verified includes equipment status data and currently executed fault handling operation data; the data verification of the fault handling data to be verified based on the target standard data, to obtain the data verification result, includes: Based on the standard status data included in the target standard data, the equipment status data is verified to obtain a first verification result; Based on the standard processing operation data included in the target standard data, the currently executed fault processing operation data is verified to obtain a second verification result; Based on the first verification result and the second verification result, the data verification result is obtained.

5. The method according to claim 3, characterized in that, The step of verifying the processing order of the fault handling steps based on the target standard fault handling steps, and obtaining the verification result, includes: The fault handling steps are compared with the target standard fault handling steps to obtain the comparison results; If the comparison result indicates that the processing order of the fault handling steps and the target standard fault handling steps is consistent, the verification result is determined to be that the processing order verification is passed; or, If the comparison result indicates that the processing order of the fault handling steps and the target standard fault handling steps is inconsistent, the verification result is determined to be that the processing order verification failed.

6. The method according to claim 3, characterized in that, The method further includes: If the data verification result indicates that the data verification has failed, an abnormal circuit breaker command and a prompt message are sent to the user terminal; the prompt message is used to indicate that the data verification has failed.

7. The method according to any one of claims 1 to 6, characterized in that, When sending the abnormal circuit breaker command to the user terminal, the method further includes: Send a warning message to the user terminal. The warning message includes at least one of the following: the cause of the abnormal circuit breaker failure, the fault handling steps for the error, and a suggestion for the correct fault handling steps.

8. A fault handling sequence control and abnormal fuse tripping device for a power information system based on a model-based intelligent agent, characterized in that, The device includes: The acquisition module is used to acquire fault handling data corresponding to the power information system in the event of a fault in the power information system. The determination module is used to determine the label information corresponding to the fault handling data based on the model agent, and to obtain the fault handling data to be verified with labeled information based on the label information; the model agent is used to identify the label information corresponding to the input fault handling data based on multiple pre-set classification labels and output it. The determining module is also used to determine fault handling steps based on the fault handling data to be verified; The verification module is used to verify the processing order of the fault handling steps based on the standard verification information included in the knowledge base, and obtain the verification result. The sending module is used to send an abnormal circuit breaker command to the user terminal when the verification result indicates that the processing order verification has failed; the abnormal circuit breaker command is used to instruct the cessation of all current fault handling operations.

9. A computer device, comprising a memory and a processor, characterized in that, The memory stores a computer program; when the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.

Images