Power grid false dispatch prevention method, device, equipment, storage medium and program product

Abstract

The application relates to a power grid false operation prevention scheduling method and device, equipment, a storage medium and a program product. The method comprises the following steps: based on a scheduling command control system and an operation control system, acquiring a false operation prevention check logical rule library and multidimensional data respectively, and constructing a fusion data matrix based on the multidimensional data; based on the fusion data matrix and the false operation prevention check logical rule library, constructing a false operation prevention check matrix for false operation prevention checking; if the false operation prevention checking is passed, triggering a programmed sequential control operation of the operation control system; if the false operation prevention checking is not passed, determining a conflict item based on the false operation prevention check matrix to perform conflict tracing, matching a correction strategy according to a tracing result to correct the false operation prevention check matrix, re-performing false operation prevention checking until the false operation prevention checking is passed; and feeding back an execution result of the programmed sequential control operation to the scheduling command control system to update a scheduling instruction ticket state and the false operation prevention check logical rule library. The method can improve the accuracy of power grid false operation prevention and scheduling efficiency.

Description

Technical Field

[0001] This application relates to the field of power system automation technology, and in particular to a method, apparatus, computer equipment, computer-readable storage medium, and computer program product for preventing power grid mis-dispatch. Background Technology

[0002] With the rapid development of power systems, the scale of power grids continues to expand and their structure becomes increasingly complex, placing higher demands on the accuracy and safety of power dispatch operations. Traditional power dispatch operations mainly rely on manual review and experience-based judgment, which suffers from numerous safety hazards and low operational efficiency. Although traditional technologies have proposed verification methods based on single systems, they still struggle to achieve comprehensive and accurate verification in complex power grid operating environments. They cannot promptly detect and correct potential operational risks and lack the ability to deeply integrate and comprehensively analyze multi-source heterogeneous data. Summary of the Invention

[0003] Therefore, it is necessary to provide a power grid anti-misoperation dispatching method, device, computer equipment, computer-readable storage medium, and computer program product to address the above-mentioned technical problems. Based on multi-source fusion data, the method accurately locates and traces conflict items through an anti-misoperation verification matrix and automatically matches correction strategies, effectively improving the accuracy of power grid anti-misoperation operation and dispatching efficiency.

[0004] Firstly, this application provides a method for preventing grid mis-dispatch, including:

[0005] Based on the dispatch and command control system, the error prevention and verification logic rule base and the dispatch instruction ticket operation sequence vector are obtained. Based on the operation control system, the real-time status vector of the equipment, the topology adjacency matrix and the power flow data vector are obtained. Based on the dispatch instruction ticket operation sequence vector, the real-time status vector of the equipment, the topology adjacency matrix and the power flow data vector, a fusion data matrix is ​​constructed.

[0006] Based on the fusion data matrix and the anti-error verification logic rule base, an anti-error verification matrix is ​​constructed, and anti-error verification is performed based on the anti-error verification matrix;

[0007] If the error prevention verification passes, the programmed sequential control operation of the operation control system is triggered;

[0008] If the error prevention check fails, the conflict item is determined based on the error prevention check matrix, the conflict source is traced based on the conflict item, the corresponding correction strategy is matched according to the conflict source result, the error prevention check matrix is ​​corrected based on the correction strategy, and the error prevention check based on the error prevention check matrix is ​​re-executed until the error prevention check passes, so as to trigger the programmed sequential control operation of the operation control system.

[0009] The execution results of the programmed sequential control operation are fed back to the dispatching and command control system to instruct the dispatching and command control system to update the status of dispatching instruction tickets and the error prevention and verification logic rule base.

[0010] In one embodiment, the anti-misoperation verification logic rule base includes operation sequence constraints, protection coordination rules, topology anti-misoperation rules, and power flow safety rules.

[0011] In one embodiment, the fused data matrix further includes device environment data. Before constructing the anti-misoperation verification matrix based on the fused data matrix and the anti-misoperation verification logic rule base, the method further includes:

[0012] The error prevention verification logic rule base was adjusted based on equipment environment data.

[0013] In one embodiment, the anti-misoperation verification matrix includes a device power-on status verification item, a topology connectivity verification item, a power flow safety limit verification item, and an operation sequence verification item; if the device power-on status verification item, the topology connectivity verification item, the power flow safety limit verification item, and the operation sequence verification item all pass the verification, the anti-misoperation verification is determined to be successful.

[0014] In one embodiment, the correction strategy includes at least one of the following:

[0015] Call the remote control interface of the operation control system and force a state change through the remote control interface;

[0016] Insert load transfer instructions and update the topology adjacency matrix;

[0017] Reorder the sequence of scheduling instruction tickets.

[0018] In one embodiment, a fused data matrix is ​​constructed based on the scheduling instruction ticket operation sequence vector, the device real-time status vector, the topology adjacency matrix, and the power flow data vector, including:

[0019] Based on the effective time of the scheduling command, the real-time status vector of the equipment is compensated by a time sliding window to obtain the adjusted real-time status vector of the equipment.

[0020] Construct a unified equipment coding mapping function between the dispatching command and control system and the operation control system;

[0021] Based on the unified coding mapping function of the equipment, a fused data matrix is ​​constructed according to the scheduling instruction ticket operation sequence vector, the adjusted real-time status vector of the equipment, the topology adjacency matrix, and the power flow data vector.

[0022] Secondly, this application also provides a power grid anti-misoperation dispatching device, comprising:

[0023] The multi-source data fusion module is used to acquire the anti-misoperation verification logic rule base and the operation sequence vector of the dispatching command and control system, and to acquire the real-time status vector of the equipment, the topology adjacency matrix and the power flow data vector of the operation control system. Based on the operation sequence vector of the dispatching command and control system, the real-time status vector of the equipment, the topology adjacency matrix and the power flow data vector, a fused data matrix is ​​constructed.

[0024] The error prevention verification module is used to construct an error prevention verification matrix based on the fused data matrix and the error prevention verification logic rule base, and to perform error prevention verification based on the error prevention verification matrix; if the error prevention verification passes, it triggers the programmed sequential control operation of the operation control system;

[0025] The feedback correction module is used to identify conflict items based on the anti-misoperation verification matrix when the anti-misoperation verification fails, trace the conflict source based on the conflict items, match the corresponding correction strategy according to the conflict source result, correct the anti-misoperation verification matrix based on the correction strategy, and re-execute the steps of anti-misoperation verification based on the anti-misoperation verification matrix until the anti-misoperation verification passes, so as to trigger the programmed sequential control operation of the operation control system.

[0026] The execution module is used to feed back the execution results of the programmed sequential control operation to the dispatching and command control system, so as to instruct the dispatching and command control system to update the status of the dispatching instruction ticket and the error prevention and verification logic rule base.

[0027] Thirdly, this application also 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 of the method described in the first aspect above.

[0028] 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 described in the first aspect above.

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

[0030] The aforementioned power grid mis-dispatch prevention method, device, computer equipment, computer-readable storage medium, and computer program product, based on the dispatch command and control system, acquire a mis-detection verification logic rule base and dispatch instruction ticket operation sequence vectors; based on the operation control system, acquire equipment real-time status vectors, topology adjacency matrices, and power flow data vectors; construct a fused data matrix based on the dispatch instruction ticket operation sequence vectors, equipment real-time status vectors, topology adjacency matrices, and power flow data vectors; construct a mis-detection verification matrix based on the fused data matrix and the mis-detection verification logic rule base, and perform mis-detection verification based on the mis-detection verification matrix; and perform mis-detection verification in the mis-detection verification process. In cases where the error prevention check fails, the programmed sequential control operation of the operation control system is triggered. If the error prevention check fails, conflict items are identified based on the error prevention check matrix, conflict sources are traced, and corresponding correction strategies are matched based on the conflict source results. The error prevention check matrix is ​​then corrected based on the correction strategies, and the error prevention check steps based on the error prevention check matrix are re-executed until the error prevention check passes, thus triggering the programmed sequential control operation of the operation control system. The execution result of the programmed sequential control operation is fed back to the dispatching and command control system to instruct it to update the dispatching instruction ticket status and the error prevention check logic rule base. Through this method, by constructing a fusion data matrix, dynamic fusion of multi-source data between the dispatching and command control system and the operation control system is achieved, effectively solving the problem of data fragmentation between the two. Based on this, identifying conflict items and tracing conflicts based on the error prevention check matrix can automatically match corresponding correction strategies, forming an active error correction mechanism, thereby reducing manual intervention and significantly lowering the risk of misoperation. Simultaneously, the execution result of the programmed sequential control operation is fed back to the dispatching and command control system in a closed loop, dynamically updating the dispatching instruction ticket status and the error prevention check logic rule base, enabling the control method to have adaptive learning capabilities. Overall, this application, based on multi-source fusion data, accurately locates and traces conflict items through an anti-misoperation verification matrix and automatically matches correction strategies, effectively improving the accuracy of power grid anti-misoperation and scheduling efficiency. Attached Figure Description

[0031] 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.

[0032] Figure 1 This is a flowchart illustrating a power grid mis-dispatch method in one embodiment;

[0033] Figure 2 This is a structural block diagram of a power grid anti-misoperation dispatching device in one embodiment;

[0034] Figure 3 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0035] 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.

[0036] It should be noted that the terms "first," "second," etc., used in this application can be used to describe various elements, but these elements are not limited by these terms. These terms are only used to distinguish the first element from the second element. The terms "comprising" and "having," and any variations thereof, used in this application, are intended to cover non-exclusive inclusion. The term "multiple" used in this application refers to two or more. The term "and / or" used in this application refers to one of the embodiments, or any combination of multiple embodiments.

[0037] In one exemplary embodiment, such as Figure 1 As shown, a method for preventing grid mis-dispatch is provided. The main implementing entity of the method is a grid mis-dispatch system, which is integrated and deployed in the grid dispatch automation system, serving as the core of collaborative control between the dispatch command and control system and the operation control system. The method includes:

[0038] Step 102: Based on the dispatching and command control system, obtain the anti-misoperation verification logic rule base and the dispatching instruction ticket operation sequence vector. Based on the operation control system, obtain the equipment real-time status vector, topology adjacency matrix and power flow data vector. Construct a fused data matrix based on the dispatching instruction ticket operation sequence vector, equipment real-time status vector, topology adjacency matrix and power flow data vector.

[0039] Specifically, based on data from the Dispatching Command and Control System (DCCS), the error prevention and verification logic rule base R and the dispatch instruction ticket operation sequence vector O are obtained; based on data from the Operational Control System (OCS), the real-time equipment status vector S, the topology adjacency matrix A, and the power flow data vector F are obtained, and a fused data matrix is ​​constructed.

[0040] Understandably, the anti-misoperation verification logic rule base is a set of predefined logic rules used to determine whether dispatching operations meet the conditions for safe operation of the power grid. The rules are built upon power system operation specifications, equipment operation constraints, topology constraints, and operational boundary conditions, covering various anti-misoperation logics, such as: operation sequence constraints (power outage operations must first disconnect the switch and then open the disconnector); protection coordination rules (when a line is transferred for maintenance, the failure protection switch must be deactivated); topology anti-misoperation rules (before a busbar is de-energized, it must be confirmed that all outgoing lines have transferred loads); and power flow safety rules (the load transfer rate must be less than 85%). This rule base can be pre-stored in the dispatching and command control system and supports dynamic updates.

[0041] The dispatch instruction ticket operation sequence vector is a structured representation of the planned operation steps in the dispatch instruction ticket. Each dimension corresponds to an operation step and includes information such as the operation object, operation type (e.g., closing, opening), and operation sequence. This vector reflects the execution plan of the dispatch operation and serves as the basic input for subsequent verification.

[0042] The real-time status vector of equipment is a structured representation of the current operating status of various devices in the power grid (such as circuit breakers, disconnectors, transformers, etc.). Each dimension corresponds to one device, and its value is the actual state of the device (such as closed, open, connected, disconnected, etc.). This vector reflects the actual operating conditions of the power grid equipment and is used for comparison and verification with planned operations.

[0043] A topology adjacency matrix describes the electrical connections between devices in a power grid. The rows and columns of the matrix correspond to power grid nodes or devices, and the matrix elements represent the connection relationships (e.g., whether they are connected) between the corresponding nodes or devices. This matrix is ​​the basis for topology error prevention verification, used to determine whether an operation would lead to non-compliant topology changes.

[0044] Power flow data vectors are vectors formed by structuring electrical quantities of the power grid under its current operating state, including node voltages, phase angles, line active power, reactive power, etc. This vector is used to determine whether dispatching operations will lead to power flow exceeding limits or failing to meet safe operating boundaries.

[0045] In an exemplary embodiment, a fused data matrix is ​​constructed based on the scheduling instruction ticket operation sequence vector, the device real-time state vector, the topology adjacency matrix, and the power flow data vector. This includes: performing time sliding window compensation on the device real-time state vector based on the effective time of the scheduling instruction to obtain an adjusted device real-time state vector; constructing a unified device coding mapping function between the scheduling command and control system and the operation control system; and constructing the fused data matrix based on the unified device coding mapping function, according to the scheduling instruction ticket operation sequence vector, the adjusted device real-time state vector, the topology adjacency matrix, and the power flow data vector.

[0046] In one alternative implementation, step 102 includes:

[0047] 1. Obtain data from the DCCS system, including:

[0048] Dispatch instruction ticket operation sequence ,in For single-step operation instructions, it is necessary to include the dual name of the equipment (such as "1# transformer 220kV bus tie 211 switch") and standard operation verbs (such as "open", "close", "engage", etc.). The total number of operation items is determined by the complexity of the operation task. For example: O = {Open the 211 switch of the 220kV South Line of Substation 1, open the 2111 disconnector of the 220kV South Line of Substation 1, and install a set of grounding wires at the 2111 disconnector of the 220kV South Line of Substation 1}. The operation items must be arranged in strict logical order. Reversing or merging items is prohibited. When multiple units are involved in the cooperation (such as operation on both sides of the line), the receiving unit must be split.

[0049] Anti-false validation logic rule base ,in For example, here is a rule type:

[0050] Operation sequence constraints When performing a power outage, the switch must be turned off first, and then the knife switch must be pulled.

[0051] Protection and Cooperation Rules When the line is being inspected and repaired, the failure protection switch must be removed.

[0052] Topology error prevention rules Before de-energizing the busbar, it must be confirmed that all outgoing lines have been relocated.

[0053] Trend Safety Rules The load transfer rate must be less than 85%.

[0054] 2. Obtain data from the OCS system, including:

[0055] Device Real-Time State Vector ,in The total number of devices, as shown in the example below:

[0056] Switch open / closed state : 1# transformer 220kV bus tie 211 switch, actual value is 1 (closed position) / 0 (open position);

[0057] knife switch position : No. 1 transformer 220kV South Line 2111 disconnect switch, actual value is 1 (closed position) / 0 (open position);

[0058] Grounding wire installation status : Grounding wire of 2111 disconnect switch of 220kV South Line of No. 1 transformer, actual value is 1 (installed) / 0 (not installed);

[0059] Protective pressure plate status : The failure protection pressure plate of switch 211 of 220kV South Line of No. 1 transformer has an actual value of 1 (in action) / 0 (out action).

[0060] Topological adjacency matrix ,in Let q represent the total number of nodes in the power grid, with a matrix dimension of q×q. An example is shown below:

[0061] Node 1: Mother I, Node 2: Mother II, Node 3: Outgoing Line 1, Node 4: Outgoing Line 2 ;

[0062] In the above matrix, This indicates that bus I and bus II are connected via a bus tie switch; This indicates that mother line II is directly connected to outgoing line 1.

[0063] Trend data vector ,in, For the first The electrical parameters of each node include active power, reactive power, voltage amplitude, and voltage phase angle.

[0064] 3. Construct a fusion data matrix for the DCCS and OCS systems, specifically including:

[0065] Based on the time the scheduling instruction takes effect Based on this, time-sliding window compensation is performed on the data from the OCS system:

[0066] ;

[0067] Where S is the original device state vector of the OCS system (dimension p×1). This represents the real-time status (such as voltage and current) of the i-th device. The dynamic sliding window size is used to compensate for data transmission latency. Let be the power flow gradient of the j-th branch, reflecting the rate of load change (unit: MW / min). The current sensitivity coefficient is set to 0.8~1.2 (empirical value range). A smaller value is used in high-load scenarios to expand the time window.

[0068] By dynamically adjusting the time window using the aforementioned power flow gradient, the time lag issue between OCS real-time data and DCCS commands is resolved. The larger the value, the stronger the adaptability to sudden load fluctuations.

[0069] Define the device uniform encoding mapping function:

[0070] ;

[0071] in, Characterization equipment and match, Characterization equipment and Mismatch The code for the i-th device in the DCCS operation ticket. This is the real-time encoding of the j-th device in the OCS system.

[0072] Constructing a fused data matrix: .

[0073] The fused data matrix unifies and aligns scheduling instruction tickets O, device status S, topology A, and power flow F, eliminating heterogeneity between systems, and is applied to subsequent conflict tracing and correction strategy execution.

[0074] Step 104: Based on the fused data matrix and the anti-error verification logic rule base, construct the anti-error verification matrix, and perform anti-error verification based on the anti-error verification matrix.

[0075] The error prevention verification matrix is ​​an intermediate data structure built upon the fused data matrix and the error prevention verification logic rule base. It systematically expresses the verification relationship between each operation step and each error prevention rule. Its construction process is as follows: A mapping relationship is established between each rule in the error prevention verification logic rule base and the relevant dimensions in the fused data matrix to determine the input data required for rule execution (such as device status, topology, power flow parameters, etc.). For each element in the fused data matrix, a corresponding verification item is generated based on the mapping relationship. Optionally, each verification item includes the applied error prevention rule, the subset of input data required for rule execution, and the expected conditions for rule fulfillment. All verification items are then structured into a two-dimensional matrix, i.e., the error prevention verification matrix.

[0076] Iterate through each check item in the error prevention check matrix. If the check item meets the rule conditions, mark it as passed; otherwise, mark it as conflicting and record the conflict type and related data. If all check items pass, the error prevention check passes; if any check item conflicts, the error prevention check fails.

[0077] In an exemplary embodiment, the anti-misoperation verification matrix includes a device power-on status verification item, a topology connectivity verification item, a power flow safety limit verification item, and an operation sequence verification item; if all three verification items pass, the anti-misoperation verification is determined to be successful.

[0078] Among them, a verification matrix for error prevention is constructed based on multi-source fusion data from the DCCS system and the OCS system:

[0079] ;

[0080] in, , , , These are the verification functions, corresponding to the equipment energized state verification item, topology connectivity verification item, power flow safety limit verification item, and operation sequence verification item, respectively.

[0081] The verification function for the equipment energized state verification item is expressed as follows: ,in, This is the equipment voltage state vector (0 = de-energized, 1 = energized). Example: Operation ticket equipment: O = ["Open the 220kV South Line 211 switch of transformer #1"], OCS real-time status: O = {s211 switch = 1, s211 disconnector = 0}. If the operation ticket equipment and OCS equipment codes match, then U11 = 1, triggering a conflict: the switch is not de-energized before the tripping operation is performed. .

[0082] The check function for the topological connectivity check term is expressed as: ,in, A non-zero trace indicates that there are no islands after the operation (k is the path length); Example:

[0083] This indicates that the initial topology, including bus I, bus II, and outgoing line 1, is fully connected. After disconnecting the bus tie switch, the update is performed. New matrix The trace is 0, forming an isolated island.

[0084] The verification function for the power flow safety limit verification item is expressed as follows: ,in The power flow vector before operation (active power P, reactive power Q, voltage V). This is the power flow vector after the simulation operation. The load factor threshold is set to 0.85. Example: Before operation, North I line... (Limited to 150MW), the southern line will be shut down, and the load will be transferred to the northern line I. The verification calculation is 150 / 140 = 93.3%. .

[0085] The check function for the operation order check item is expressed as follows: ,in This is the longest common subsequence algorithm, which matches the degree of conformity between the operation steps and the rule base. Example: When performing a power outage, the switch must be turned off first, and then the knife switch must be pulled. When the line is switched to maintenance, the failure protection switch must be deactivated; OCS real-time status: O={Open the 2111 disconnect switch on the south line, open the 211 switch on the south line, deactivate the 211 switch failure protection}; LCS algorithm detected violation (Pull the knife switch first, then disconnect the switch). .

[0086] Based on the calculation results of the error prevention verification matrix If the timing is right, the sequential control operation is triggered; otherwise, proceed to step 108.

[0087] Step 106: If the error prevention verification passes, trigger the programmed sequential control operation of the operation control system.

[0088] The process involves item-by-item verification based on the error prevention check matrix. If all check items pass, the error prevention check is considered successful; otherwise, it is considered unsuccessful. A successful error prevention check indicates that the current dispatching instruction ticket meets the requirements for safe power grid operation in terms of equipment status, topology, power flow parameters, and operation sequence, and is ready for execution.

[0089] Programmed sequential control refers to the process by which the operation control system automatically executes a series of equipment operations according to a predefined sequence. The operation steps can be pre-programmed into an automatically executable program, eliminating the need for manual confirmation or manual issuance of instructions. In practice, trigger instructions are sent to the operation control system via a data communication interface (such as a remote control communication protocol, message bus, or API call). After receiving the instructions, the operation control system performs authorization verification and instruction integrity checks. Once confirmed to be correct, it enters the execution preparation state.

[0090] Step 108: If the error prevention verification fails, determine the conflict item based on the error prevention verification matrix, trace the conflict source based on the conflict item, match the corresponding correction strategy according to the conflict source result, correct the error prevention verification matrix based on the correction strategy, and re-execute the error prevention verification steps based on the error prevention verification matrix until the error prevention verification passes, so as to trigger the programmed sequential control operation of the operation control system.

[0091] In one alternative implementation, step 108 includes:

[0092] 1. Conflict item identification: Based on the zero element of the verification matrix, the conflict type is located, specifically including:

[0093] Conflict items ;

[0094] in, The four-dimensional verification function values ​​(0 = conflict, 1 = pass) are respectively compared with the verification function. , , , Corresponding to the conflict type.

[0095] 2. Based on the conflict items identified in the preceding steps, perform conflict tracing, specifically including:

[0096] Device status conflict tracing: ,in, For device mapping matrix, This is the real-time status of OCS. This is the expected state of the instruction. Equipment status (0 = power off, 1 = energized). Equipment code matching. Specific example: During busbar switching operations, the bus tie switch code is 211. The middle state is 1 (closed), while The requirement is 0 (disconnected), and the XOR result points to switch 211 in a conflict.

[0097] Origin of topological connectivity conflicts: ,in, The topological adjacency matrix ( (Indicates node connectivity). Specific example: After disconnecting the bus tie switch, the adjacency matrix is ​​updated. ,calculate This indicates that the island has split into two isolated islands.

[0098] Power Flow Safety Conflict Origin Tracing: Based on Power Flow Safety Limit Verification Function Directly trace the source of the operation.

[0099] Operation order conflict tracing: Based on operation order matching degree verification function Directly trace the source of the operation.

[0100] 3. Based on the conflict attribution results, implement corrective strategies, specifically including:

[0101] Device status conflict correction: ,in, To correct the device voltage state vector, Inverts the conflict state. Specific example: After the location bus tie switch 211 is found to be in an abnormal state, the OCS remote adjustment interface is called to force trip the switch, and the s211 switch value is updated to 0.

[0102] Topology connectivity conflict correction adjusts topology connectivity by performing load transfer. For example, inserting a load transfer step updates the topology matrix so that outgoing line 1 is reconnected to bus II, and ΔC decreases from 1 to 0.

[0103] Power flow safety conflict correction is achieved through overload transfer adjustment based on overload rate, for example, by transferring a portion of the load to standby capacity, thereby reducing the load rate to 85%.

[0104] Operation sequence conflict correction: ,in, This is the rearranged sequence of operations for the scheduling instruction tickets. Specific examples: adjusting the operation to [disconnect switch, pull disconnect switch], and using the promotion rule. Weight adjustment operation order matching degree verification function The result is determined.

[0105] Step 110: Feedback the execution results of the programmed sequential control operation to the dispatching command and control system to instruct the dispatching command and control system to update the status of the dispatching instruction ticket and the error prevention verification logic rule base.

[0106] The execution result of the programmed sequential control operation refers to the execution status feedback data generated by the operation control system after executing the programmed sequential control operation corresponding to the dispatch instruction ticket. Optionally, the execution result includes at least the following information: operation status, indicating the execution status of the entire operation sequence, such as "fully successful", "partially successful", "execution failed", etc.; step execution details, recording the execution status of each step in the operation sequence, including execution time, execution equipment, operation action, execution result (success / failure) and failure reason (such as equipment failure to operate, condition not met, etc.); abnormal information, if an abnormality occurs during the execution process, recording the abnormality type, the step in which it occurred and related alarm information; and a snapshot of the status before and after execution, optionally including the status changes of key equipment and power grid operating parameters before and after the operation, for subsequent analysis and closed-loop updates.

[0107] Updating the status of a dispatch instruction ticket refers to the dispatch command and control system changing the status of the corresponding dispatch instruction ticket based on the received execution results. Optionally, the corresponding dispatch instruction ticket is located based on the operation status in the execution results; the status of the instruction ticket is updated to the corresponding status (such as "executed" or "execution failed"); the execution details of the steps are written into the execution record field of the instruction ticket; and the updated instruction ticket data is saved to the system database.

[0108] Updating the error prevention verification logic rule base refers to the process by which the dispatching and command control system dynamically optimizes and expands the error prevention verification logic rule base based on the execution results and actual operational characteristics discovered during execution. Optionally, this involves extracting abnormal information, failure reasons, and state change data before and after the operation from the execution results; analyzing whether there are scenarios not covered by the existing rule base or with unreasonable rule settings; if so, generating a rule adjustment plan, which is then automatically evaluated by the system or confirmed by dispatchers to correct or expand the rule base; recording rule change logs, and updating the rule base version.

[0109] By constructing a fusion data matrix to uniformly process the dispatching instruction ticket operation sequence vector O, the equipment real-time status vector S, the topology adjacency matrix A, and the power flow data vector F, a misoperation prevention verification matrix is ​​adopted to realize four-dimensional verification of equipment energized status, topology connectivity, power flow safety limits, and operation sequence. When the verification fails, a correction strategy is automatically matched based on the conflict item calibration and tracing mechanism. After the verification passes, the OCS programmed sequential control operation is triggered to update the dispatching instruction ticket status and the misoperation prevention verification logic rule base, forming a control closed loop of "verification-correction-execution-feedback", which improves the accuracy of power grid operation misoperation prevention and the efficiency of power grid dispatching.

[0110] In the aforementioned power grid mis-dispatch method, based on the dispatch command and control system, a mis-detection verification logic rule base and dispatch instruction ticket operation sequence vector are obtained. Based on the operation control system, real-time equipment status vectors, topology adjacency matrices, and power flow data vectors are obtained. A fused data matrix is ​​constructed based on the dispatch instruction ticket operation sequence vectors, real-time equipment status vectors, topology adjacency matrices, and power flow data vectors. A mis-detection verification matrix is ​​constructed based on the fused data matrix and the mis-detection verification logic rule base, and mis-detection verification is performed based on the mis-detection verification matrix. If the mis-detection verification passes, the programmed sequential control operation of the operation control system is triggered. If the mis-detection verification fails, conflict items are determined based on the mis-detection verification matrix, conflict tracing is performed based on the conflict items, and a corresponding correction strategy is matched based on the conflict tracing results. The mis-detection verification matrix is ​​corrected based on the correction strategy, and the steps of performing mis-detection verification based on the mis-detection verification matrix are re-executed until the mis-detection verification passes, thereby triggering the programmed sequential control operation of the operation control system. The execution result of the programmed sequential control operation is fed back to the dispatch command and control system to instruct the dispatch command and control system to update the dispatch instruction ticket status and the mis-detection verification logic rule base. By constructing a fusion data matrix, the dynamic fusion of multi-source data between the dispatching and command control system and the operation control system is achieved, effectively solving the problem of data fragmentation between the two. Based on this, conflict items are identified and their sources are traced using the error prevention verification matrix, automatically matching corresponding correction strategies and forming an active error correction mechanism. This reduces manual intervention and significantly lowers the risk of misoperation. Simultaneously, the execution results of programmed sequential control operations are loop-wise fed back to the dispatching and command control system, dynamically updating the status of dispatching command tickets and the error prevention verification logic rule base, enabling the control method to have adaptive learning capabilities. Overall, this application, based on multi-source fusion data, accurately locates and traces conflict items through the error prevention verification matrix, and automatically matches correction strategies, effectively improving the accuracy of power grid error prevention and dispatching efficiency.

[0111] In one exemplary embodiment, the anti-misoperation verification logic rule base includes operation sequence constraints, protection coordination rules, topology anti-misoperation rules, and power flow safety rules.

[0112] Operation sequence constraints refer to a class of rules that regulate the execution order of scheduling operation steps to prevent electrical accidents caused by incorrect sequence. Operation sequence constraints specify the logical relationship that equipment operations must follow. For example, a power outage operation must first disconnect the circuit breaker and then open the isolating switch; a power restoration operation must first close the isolating switch and then close the circuit breaker. Optionally, during the error prevention verification process, the order of operation steps in the operation sequence vector of the scheduling instruction ticket is extracted; adjacent or related operation steps are compared with the operation sequence constraint rules; if the actual operation sequence violates the constraint rules, the operation is determined to be a conflict item, and the conflict type is marked as operation sequence conflict.

[0113] Protection coordination rules refer to the error prevention rules related to the status of relay protection devices. These rules ensure that protection devices are in the correct state during dispatch operations, preventing maloperation or failure to operate. Protection coordination rules specify the adjustments required to the protection devices before certain dispatch operations. For example, when a line is transferred for maintenance, the faulty protection switch must be deactivated; before energizing a line, the corresponding protection must be activated. Optionally, during the error prevention verification process, the actual status of the current protection device is obtained from the fused data matrix; the operation steps in the dispatch instruction ticket are matched with the protection coordination rules; if the protection status corresponding to the operation steps does not meet the rule requirements, it is determined to be a conflict item, and the conflict type is marked as protection coordination conflict.

[0114] Topology error prevention rules are rules formulated based on the electrical connection relationships of the power grid to prevent abnormalities in the power grid topology caused by operations, such as asynchronous paralleling, islanding, or bus voltage loss. Topology error prevention rules specify the safety conditions that the power grid topology must meet before and after an operation. For example, before a bus de-energizes, it must be confirmed that all outgoing lines have transferred loads; before a loop closing operation, it must be confirmed that the voltage difference across the loop closing point is within the allowable range. Optionally, during the error prevention verification process, the topology adjacency matrix before the operation is obtained from the fused data matrix; the operation steps are simulated to generate the topology adjacency matrix after the operation; the topology structure after the operation is verified based on the topology error prevention rules, such as determining whether islanding has occurred, whether bus voltage loss has occurred, or whether asynchronous paralleling has occurred; if the topology structure after the operation violates the rules, it is determined as a conflict item, and the conflict type is marked as a topology error prevention conflict.

[0115] Power flow safety rules are error prevention rules formulated based on power grid electrical quantity parameters to prevent power flow exceedance issues such as equipment overload and voltage exceeding limits after operation. Power flow safety rules stipulate that power grid operating parameters must be maintained within safety boundaries after operation. For example, the load transfer rate must be less than 85%; line power must not exceed the thermal stability limit; and bus voltage must be maintained within ±5% of the rated voltage. Optionally, during the error prevention verification process, the power flow data vector before operation is obtained from the fused data matrix; the operation steps are simulated, and the power flow distribution of the power grid after operation is calculated (using static power flow calculation or sensitivity analysis-based methods); the calculated power flow data after operation is compared with the thresholds in the power flow safety rules; if any electrical quantity exceeds the safety threshold, it is determined as a conflict item, and the conflict type is marked as a power flow safety conflict.

[0116] In an exemplary embodiment, the fused data matrix further includes device environment data. Before step 104, the method further includes: adjusting the anti-misoperation verification logic rule base based on the device environment data.

[0117] In constructing the fused data matrix, in addition to the data from the existing DCCS and OCS systems, equipment environmental data can be further integrated. Optionally, equipment environmental data includes weather data and environmental data. For example, real-time weather conditions within the power grid area, including temperature, humidity, wind speed, and precipitation probability, can be obtained through an interface with a meteorological service; environmental data such as altitude, topography, and distribution of surrounding pollution sources can be obtained through a Geographic Information System (GIS). Based on this weather and environmental data, the verification rules in the anti-misoperation verification logic rule base R are adaptively adjusted. For example, under high-temperature weather conditions, the power flow safety limit verification standard for the equipment is appropriately reduced to prevent overload damage due to temperature increases; under high humidity or precipitation weather conditions, the weight of anti-misoperation verification rules related to equipment insulation performance is increased to avoid equipment failure and misoperation risks caused by humidity.

[0118] In one exemplary embodiment, the correction strategy includes at least one of the following: invoking the remote control interface of the operation control system to force a state change through the remote control interface; inserting a load transfer instruction and updating the topology adjacency matrix; and rearranging the operation sequence of the scheduling instruction ticket.

[0119] Optionally, based on the conflict items marked in the anti-misoperation verification matrix, conflict types (operation sequence conflicts, protection coordination conflicts, topology anti-misoperation conflicts, power flow safety conflicts, etc.) are identified. According to the conflict type and conflict data, an applicable correction strategy is matched from a preset correction strategy mapping table. For example, for protection coordination conflicts, strategies that force state changes are preferentially matched; for power flow safety conflicts, strategies that insert load transfer commands and update the topology adjacency matrix are preferentially matched; for operation sequence conflicts, strategies that rearrange the operation sequence are preferentially matched; and for topology anti-misoperation conflicts, strategies that insert load transfer commands and update the topology adjacency matrix are preferentially matched.

[0120] The remote adjustment interface is a remote adjustment interface provided by the operation and control system to remotely adjust the setpoints or states of power grid equipment. Forced state change refers to directly issuing control commands through the remote adjustment interface to forcibly adjust the state of a specified device to the required value. This operation does not rely on the original sequence of operation steps in the dispatch instruction ticket, but rather serves as a proactive error correction method to pre-adjust the equipment to a state that meets the anti-misoperation verification conditions. For example, conflict tracing results locate conflicts caused by equipment states not meeting rule requirements (such as protection pressure plates not being disengaged, improper transformer tap positions, etc.); a forced state change strategy is matched according to the conflict type, generating a remote adjustment command containing the target equipment, target state, and operating parameters; the command is issued to the operation and control system through the remote adjustment interface; the operation and control system executes the state change and returns the execution result; after receiving the execution result, the real-time device state vector in the fused data matrix is ​​updated, and the anti-misoperation verification is re-executed.

[0121] Load transfer instructions are additional operational steps automatically inserted into the original operation sequence to alleviate or avoid equipment overload and power flow exceeding limits caused by dispatching operations. These instructions typically involve transferring the load of a feeder or transformer to an adjacent feeder or transformer to redistribute power flow. After inserting a load transfer instruction, the power grid topology changes, requiring a synchronous update of the topology adjacency matrix to accurately reflect the new connectivity and ensure the correctness of subsequent error prevention checks and power flow calculations. For example, conflict tracing results pinpoint conflicts caused by power flow exceeding limits or topology anomalies (such as excessive load transfer rate or overload after loop closure). Based on the conflict type and the current operating state of the power grid, a load transfer instruction is automatically generated, including parameters such as the transfer path, transferred load, and target feeder. The generated load transfer instruction is inserted into the appropriate position in the original dispatching instruction ticket's operation sequence (usually before the operation that triggered the conflict). Based on the impact of the load transfer instruction on the power grid topology, the topology adjacency matrix is ​​updated, adding or modifying the connectivity relationships between corresponding nodes. The topology adjacency matrix and operation sequence vector in the fused data matrix are updated, and error prevention checks are re-executed.

[0122] Rearranging the operation sequence of a dispatch instruction ticket refers to adjusting the order of steps in the operation sequence according to operation order constraints, without adding or deleting steps, to ensure it conforms to correct electrical operation logic. For example, conflict tracing results pinpoint conflicts caused by violations of operation order constraints (such as pulling a disconnector before disconnecting a switch); extracting the operation steps involved in the conflict and related order constraints; rearranging the order of relevant steps in the operation sequence based on a topology sorting algorithm or rule engine, ensuring the adjusted sequence satisfies all operation order constraints; if the rearrangement process involves adjustments to dependencies between steps, synchronously verifying whether the adjusted sequence introduces new order conflicts; updating the dispatch instruction ticket operation sequence vector to the adjusted sequence, updating the operation sequence data in the fused data matrix, and re-executing the error prevention check.

[0123] 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 in other steps. It is understood that the steps in different embodiments can be freely combined as needed, and all non-contradictory solutions formed by such combinations are within the scope of protection of this application.

[0124] Based on the same inventive concept, this application also provides a power grid mis-dispatch device for implementing the power grid mis-dispatch method described above. The solution provided by this device is similar to the solution described in the above method; therefore, the specific limitations in one or more embodiments of the power grid mis-dispatch device provided below can be found in the limitations of the power grid mis-dispatch method described above, and will not be repeated here.

[0125] In one exemplary embodiment, such as Figure 2 As shown, a power grid anti-misoperation dispatching device is provided, comprising:

[0126] The multi-source data fusion module 202 is used to acquire the anti-misoperation verification logic rule base and the operation sequence vector of the scheduling instruction ticket based on the scheduling command and control system, and to acquire the real-time status vector of the equipment, the topology adjacency matrix and the power flow data vector based on the operation control system. It constructs a fused data matrix based on the operation sequence vector of the scheduling instruction ticket, the real-time status vector of the equipment, the topology adjacency matrix and the power flow data vector.

[0127] The error prevention verification module 204 is used to construct an error prevention verification matrix based on the fused data matrix and the error prevention verification logic rule base, and to perform error prevention verification based on the error prevention verification matrix; if the error prevention verification passes, it triggers the programmed sequential control operation of the operation control system;

[0128] The feedback correction module 206 is used to determine the conflict item based on the anti-misoperation verification matrix when the anti-misoperation verification fails, perform conflict tracing based on the conflict item, match the corresponding correction strategy according to the conflict tracing result, correct the anti-misoperation verification matrix based on the correction strategy, and re-execute the steps of anti-misoperation verification based on the anti-misoperation verification matrix until the anti-misoperation verification passes, so as to trigger the programmed sequential control operation of the operation control system.

[0129] The execution module 208 is used to feed back the execution results of the programmed sequential control operation to the dispatching command and control system, so as to instruct the dispatching command and control system to update the status of the dispatching instruction ticket and the error prevention verification logic rule base.

[0130] In the aforementioned power grid misoperation prevention and dispatching device, a fusion data matrix is ​​constructed to achieve dynamic fusion of multi-source data between the dispatching command and control system and the operation control system, effectively solving the problem of data fragmentation between the two. Based on this, conflict items are identified and their sources are traced using the misoperation prevention verification matrix, automatically matching corresponding correction strategies and forming an active error correction mechanism. This reduces manual intervention and significantly lowers the risk of misoperation. Simultaneously, the execution results of the programmed sequential control operation are fed back to the dispatching command and control system in a closed loop, dynamically updating the dispatching command ticket status and the misoperation prevention verification logic rule base, enabling the control method to have adaptive learning capabilities. Overall, this application, based on multi-source fusion data, accurately locates and traces conflict items through the misoperation prevention verification matrix and automatically matches correction strategies, effectively improving the accuracy of power grid misoperation prevention and dispatching efficiency.

[0131] In one exemplary embodiment, the anti-misoperation verification logic rule base includes operation sequence constraints, protection coordination rules, topology anti-misoperation rules, and power flow safety rules.

[0132] In one exemplary embodiment, the fused data matrix further includes device environment data, and the multi-source data fusion module 202 is also used to adjust the anti-misoperation verification logic rule base based on the device environment data.

[0133] In an exemplary embodiment, the anti-misoperation verification matrix includes a device power-on status verification item, a topology connectivity verification item, a power flow safety limit verification item, and an operation sequence verification item; if all three verification items pass, the anti-misoperation verification is determined to be successful.

[0134] In one exemplary embodiment, the correction strategy includes at least one of the following: invoking the remote control interface of the operation control system to force a state change through the remote control interface; inserting a load transfer instruction and updating the topology adjacency matrix; and rearranging the operation sequence of the scheduling instruction ticket.

[0135] In an exemplary embodiment, the multi-source data fusion module 202 is further configured to perform time sliding window compensation on the real-time state vector of the equipment based on the effective time of the scheduling instruction, so as to obtain the adjusted real-time state vector of the equipment; construct a unified coding mapping function for the equipment between the scheduling command and control system and the operation control system; and construct a fused data matrix based on the unified coding mapping function of the equipment, according to the scheduling instruction ticket operation sequence vector, the adjusted real-time state vector of the equipment, the topology adjacency matrix and the power flow data vector.

[0136] In an optional embodiment, a lockout-related control engine is introduced into the feedback correction module 206. When the conflict tracing result indicates that the execution of an operation command may lead to a serious safety accident such as a large-scale power outage or severe equipment damage, the system will automatically trigger lockout control, locking out the operation command and its associated potentially risky operation steps, prohibiting their execution under the current conditions. Simultaneously, the system will issue an emergency alarm message to remind dispatchers to intervene promptly.

[0137] In an optional embodiment, when the interlocking association control is triggered or when the feedback correction module 206 fails to verify three consecutive times, two-factor authentication is automatically activated. Two-factor authentication is used to perform a secondary verification of the operator's identity and operating permissions, ensuring the authorization and accuracy of the operation. The two-factor authentication includes the following steps:

[0138] Identity verification: Operators verify their identity using one of the following biometric methods: fingerprint, facial recognition, or iris recognition.

[0139] Operation confirmation verification: After identity verification is successful, the operator needs to confirm the operation by entering a dynamic verification code (such as SMS verification code, voice verification code, email verification code, etc.), using a one-time password generated by a hardware token, or answering a pre-set security question.

[0140] Verification result determination: If both factors of validation pass, the lockout control is released or the modified strategy is allowed to be re-executed; if either validation fails, the lockout state is maintained and the validation failure information is recorded.

[0141] In an optional embodiment, a conflict visualization module is also provided, which generates an intuitive visualization interface based on the error prevention verification matrix and conflict tracing results. This interface uses a graphical approach, such as marking the location and type of conflicting devices with different colors on a power grid topology map, and displaying specific details of the conflict through pop-ups or sidebars, including the conflict verification function and conflict tracing path. Simultaneously, it can dynamically display the execution process of correction strategies, such as simulating adjustments to the operation sequence and corrections to equipment status in animation form, enabling dispatchers to clearly see the problems in the entire error prevention dispatch process and the solutions taken by the system, thereby making more effective decisions and supervision.

[0142] Each module in the aforementioned power grid anti-misoperation dispatching device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in the processor of a computer device in hardware form or independent of it, or stored in the memory of a computer device in software form, so that the processor can call and execute the corresponding operations of each module.

[0143] In one exemplary embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 3 As shown, this computer device includes a processor, memory, input / output (I / O) interfaces, and a communication interface. The processor, memory, and I / O interfaces are connected via a system bus, and the communication interface is also connected to the system bus via the I / O 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 the environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The I / O interfaces are used for exchanging information between the processor and external devices. The communication interface is used for communication with external terminals via a network connection. When the computer program is executed by the processor, it implements a power grid mis-dispatch method.

[0144] Those skilled in the art will understand that Figure 3 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.

[0145] In one exemplary embodiment, a computer device is provided, including a memory and a processor. The memory stores a computer program, and the processor executes the computer program to perform the following steps: based on a scheduling command and control system, acquiring a fault-prevention verification logic rule base and a scheduling instruction ticket operation sequence vector; based on an operation control system, acquiring a device real-time state vector, a topology adjacency matrix, and a power flow data vector; constructing a fused data matrix based on the scheduling instruction ticket operation sequence vector, the device real-time state vector, the topology adjacency matrix, and the power flow data vector; and constructing a fault-prevention verification matrix based on the fused data matrix and the fault-prevention verification logic rule base, and based on the fault-prevention verification matrix... The system performs a fault prevention check on the matrix. If the fault prevention check passes, the programmed sequential control operation of the operation control system is triggered. If the fault prevention check fails, conflict items are identified based on the fault prevention check matrix, conflict sources are traced based on the conflict items, corresponding correction strategies are matched based on the conflict source results, the fault prevention check matrix is ​​corrected based on the correction strategies, and the fault prevention check steps based on the fault prevention check matrix are re-executed until the fault prevention check passes, thereby triggering the programmed sequential control operation of the operation control system. The execution result of the programmed sequential control operation is fed back to the dispatching command control system to instruct the dispatching command control system to update the status of the dispatching instruction ticket and the fault prevention verification logic rule base.

[0146] In one embodiment, when the processor executes the computer program, it also performs the following steps: adjusting the anti-misoperation verification logic rule base based on device environment data.

[0147] In one embodiment, when the processor executes the computer program, it further performs the following steps: using the effective time of the scheduling instruction as a reference, performing time sliding window compensation on the real-time state vector of the equipment to obtain the adjusted real-time state vector of the equipment; constructing a unified coding mapping function for the equipment between the scheduling command and control system and the operation control system; and constructing a fused data matrix based on the unified coding mapping function of the equipment, according to the scheduling instruction ticket operation sequence vector, the adjusted real-time state vector of the equipment, the topology adjacency matrix, and the power flow data vector.

[0148] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When executed by a processor, the computer program performs the following steps: based on a dispatching and command control system, acquiring a fault-prevention verification logic rule base and a dispatching instruction ticket operation sequence vector; based on an operation control system, acquiring a real-time device status vector, a topology adjacency matrix, and a power flow data vector; constructing a fused data matrix based on the dispatching instruction ticket operation sequence vector, the real-time device status vector, the topology adjacency matrix, and the power flow data vector; constructing a fault-prevention verification matrix based on the fused data matrix and the fault-prevention verification logic rule base, and performing fault-prevention verification based on the fault-prevention verification matrix. If the error prevention verification passes, the programmed sequential control operation of the operation control system is triggered. If the error prevention verification fails, conflict items are identified based on the error prevention verification matrix, conflict sources are traced based on the conflict items, corresponding correction strategies are matched based on the conflict source tracing results, the error prevention verification matrix is ​​corrected based on the correction strategies, and the error prevention verification steps based on the error prevention verification matrix are re-executed until the error prevention verification passes, thereby triggering the programmed sequential control operation of the operation control system. The execution result of the programmed sequential control operation is fed back to the dispatching command control system to instruct the dispatching command control system to update the status of dispatching instruction tickets and the error prevention verification logic rule base.

[0149] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: adjusting the anti-misoperation verification logic rule base based on device environment data.

[0150] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: using the effective time of the scheduling instruction as a reference, performing time sliding window compensation on the real-time state vector of the equipment to obtain the adjusted real-time state vector of the equipment; constructing a unified coding mapping function for the equipment between the scheduling command and control system and the operation control system; and constructing a fusion data matrix based on the unified coding mapping function of the equipment, according to the scheduling instruction ticket operation sequence vector, the adjusted real-time state vector of the equipment, the topology adjacency matrix, and the power flow data vector.

[0151] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, performs the following steps: based on a scheduling and command control system, acquiring a fault-prevention verification logic rule base and a scheduling instruction ticket operation sequence vector; based on an operation control system, acquiring a device real-time status vector, a topology adjacency matrix, and a power flow data vector; constructing a fused data matrix based on the scheduling instruction ticket operation sequence vector, the device real-time status vector, the topology adjacency matrix, and the power flow data vector; constructing a fault-prevention verification matrix based on the fused data matrix and the fault-prevention verification logic rule base, and performing fault-prevention verification based on the fault-prevention verification matrix; If the error prevention verification passes, the programmed sequential control operation of the operation control system is triggered. If the error prevention verification fails, conflict items are identified based on the error prevention verification matrix, conflict sources are traced based on the conflict items, corresponding correction strategies are matched based on the conflict source tracing results, the error prevention verification matrix is ​​corrected based on the correction strategies, and the error prevention verification steps based on the error prevention verification matrix are re-executed until the error prevention verification passes, thereby triggering the programmed sequential control operation of the operation control system. The execution result of the programmed sequential control operation is fed back to the dispatching command control system to instruct the dispatching command control system to update the status of dispatching instruction tickets and the error prevention verification logic rule base.

[0152] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: adjusting the anti-misoperation verification logic rule base based on device environment data.

[0153] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: using the effective time of the scheduling instruction as a reference, performing time sliding window compensation on the real-time state vector of the equipment to obtain the adjusted real-time state vector of the equipment; constructing a unified coding mapping function for the equipment between the scheduling command and control system and the operation control system; and constructing a fusion data matrix based on the unified coding mapping function of the equipment, according to the scheduling instruction ticket operation sequence vector, the adjusted real-time state vector of the equipment, the topology adjacency matrix, and the power flow data vector.

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

[0155] 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.

[0156] 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.

[0157] 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 preventing power grid mis-dispatch, characterized in that, The method includes: Based on the dispatch and command control system, a base of error prevention and verification logic rules and a dispatch instruction ticket operation sequence vector are obtained. Based on the operation control system, real-time status vectors of equipment, topology adjacency matrix and power flow data vectors are obtained. A fusion data matrix is ​​constructed based on the dispatch instruction ticket operation sequence vectors, the real-time status vectors of equipment, the topology adjacency matrix and the power flow data vectors. Based on the fused data matrix and the anti-error verification logic rule base, an anti-error verification matrix is ​​constructed, and anti-error verification is performed based on the anti-error verification matrix; If the error prevention verification passes, the programmed sequential control operation of the operation control system is triggered; If the error prevention verification fails, conflict items are determined based on the error prevention verification matrix, conflict sources are traced based on the conflict items, corresponding correction strategies are matched according to the conflict source results, the error prevention verification matrix is ​​corrected based on the correction strategies, and the error prevention verification based on the error prevention verification matrix is ​​re-executed until the error prevention verification passes, so as to trigger the programmed sequential control operation of the operation control system. The execution result of the programmed sequential control operation is fed back to the dispatching and command control system to instruct the dispatching and command control system to update the status of the dispatching instruction ticket and the anti-misoperation verification logic rule base.

2. The method according to claim 1, characterized in that, The anti-misoperation verification logic rule base includes operation sequence constraints, protection coordination rules, topology anti-misoperation rules, and power flow safety rules.

3. The method according to claim 1, characterized in that, The fused data matrix also includes device environment data. Before constructing the anti-misoperation verification matrix based on the fused data matrix and the anti-misoperation verification logic rule base, the method further includes: The error prevention verification logic rule base is adjusted based on the device environment data.

4. The method according to claim 1, characterized in that, The anti-misoperation verification matrix includes equipment power-on status verification items, topology connectivity verification items, power flow safety limit verification items, and operation sequence verification items; if all of the equipment power-on status verification items, the topology connectivity verification items, the power flow safety limit verification items, and the operation sequence verification items pass the verification, the anti-misoperation verification is determined to be successful.

5. The method according to claim 1, characterized in that, The correction strategy includes at least one of the following: Call the remote adjustment interface of the operation control system and force a state change through the remote adjustment interface; Insert a load transfer instruction and update the topology adjacency matrix; Reorder the sequence of scheduling instruction tickets.

6. The method according to any one of claims 1 to 5, characterized in that, The step of constructing a fused data matrix based on the scheduling instruction ticket operation sequence vector, the device real-time status vector, the topology adjacency matrix, and the power flow data vector includes: Based on the effective time of the scheduling instruction, the real-time state vector of the device is compensated by a time sliding window to obtain the adjusted real-time state vector of the device. Construct a unified equipment coding mapping function between the dispatching command and control system and the operation control system; Based on the device unified coding mapping function, a fused data matrix is ​​constructed according to the scheduling instruction ticket operation sequence vector, the adjusted device real-time status vector, the topology adjacency matrix, and the power flow data vector.

7. A power grid anti-misoperation dispatching device, characterized in that, The device includes: The multi-source data fusion module is used to acquire the anti-misoperation verification logic rule base and the operation sequence vector of the scheduling instruction ticket based on the scheduling command and control system, and to acquire the real-time status vector of the equipment, the topology adjacency matrix and the power flow data vector based on the operation control system. The module constructs a fused data matrix based on the operation sequence vector of the scheduling instruction ticket, the real-time status vector of the equipment, the topology adjacency matrix and the power flow data vector. The error prevention verification module is used to construct an error prevention verification matrix based on the fused data matrix and the error prevention verification logic rule base, and to perform error prevention verification based on the error prevention verification matrix; if the error prevention verification passes, the programmed sequential control operation of the operation control system is triggered. The feedback correction module is used to determine conflict items based on the anti-misoperation verification matrix when the anti-misoperation verification fails, perform conflict tracing based on the conflict items, match the corresponding correction strategy according to the conflict tracing results, correct the anti-misoperation verification matrix based on the correction strategy, and re-execute the step of performing anti-misoperation verification based on the anti-misoperation verification matrix until the anti-misoperation verification passes, so as to trigger the programmed sequential control operation of the operation control system. The execution module is used to feed back the execution result of the programmed sequential control operation to the dispatching command and control system, so as to instruct the dispatching command and control system to update the status of the dispatching instruction ticket and the anti-misoperation verification logic rule base.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 6.

9. 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 6.

10. A computer program product, comprising a computer program, 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 6.

Images