Remote operation and maintenance management method for secondary equipment of power grid based on cloud-side cooperation

By using cloud-edge collaboration technology, a list of operating procedures for power grid secondary equipment is generated and power flow sensitivity is assessed. The path with the least risk is selected, which solves the problems of uncertainty in operation sequence and quantification of electrical safety risks in remote operation and maintenance of power grid secondary equipment, and realizes the uniqueness and traceability of operating procedures.

CN121508165APending Publication Date: 2026-02-10JIANGMEN POWER SUPPLY BUREAU OF GUANGDONG POWER GRID CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202511633984.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-11-10
Publication Date
2026-02-10

AI Technical Summary

Technical Problem

In the current remote operation and maintenance management of power grid secondary equipment, there is a lack of deterministic work chains and strong coupled, verifiable constraints, which leads to non-unique operating procedures and difficulty in quantifying and tracing electrical safety risks.

Method used

Through cloud-edge collaboration, station operation data is collected, action dependency graphs are generated and deterministically sorted, power flow sensitivity impact assessment is performed, the minimum risk path is obtained, micro-time window slicing is implemented using the evidence fingerprinting sequence slicing algorithm, zero-trust release credentials are generated, and execution record summary and verification receipt report are generated through context mirroring.

Benefits of technology

It improves the certainty and interpretability of operating procedures, ensures cross-site consistency, and enhances the success rate of operation and maintenance plans and grid security.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN121508165A_ABST
    Figure CN121508165A_ABST
Patent Text Reader

Abstract

The invention discloses a power grid secondary equipment remote operation and maintenance management method based on cloud edge collaboration, and relates to the technical field of power control, and the method comprises the steps: carrying out the impact evaluation of the operation instruction list and execution power flow sensitivity of power grid secondary equipment, and obtaining a minimum risk path; on the basis of the minimum risk path, micro time window slicing is implemented through an evidence fingerprinting sequence slicing algorithm, mirror image anchoring is carried out on station end operation data, and a zero-trust release credential is generated; a controlled session is established according to the zero-trust release credential, and execution record summarization is generated through context mirroring; and based on the execution record summarization, carrying out consistency survey and verification according to the zero-trust release credentials, and generating a verification receipt report. According to the method, the power flow sensitivity evaluation is carried out on the operation instruction list of the power grid secondary equipment, and the minimum risk path is selected through step-by-step short circuit judgment, so that the effects of explainability of sequence selection, cross-station consistency and plan one-time passing rate improvement are improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of power control technology, and in particular to a remote operation and maintenance management method for power grid secondary equipment based on cloud-edge collaboration. Background Technology

[0002] With the promotion of digital substations, remote operation and maintenance management of power grid secondary equipment has evolved from the previous decentralized, manual inspection and offline setting management to centralized monitoring and remote operation and maintenance for the entire network. As cloud computing and edge computing are implemented in the power industry, the cloud has the advantages of multi-site aggregation, policy generation and compliance auditing, while the edge has the capabilities of real-time, on-site verification and rapid response. Cloud-edge collaboration is gradually becoming the mainstream architecture for remote operation and maintenance of secondary equipment. The operation and maintenance objects and data elements are also becoming increasingly rich, including topology snapshots, secondary equipment configuration and setting area and pressure plate position status, as well as non-functional elements closely related to operability and verifiability, such as clock synchronization deviation and communication link quality.

[0003] The shortcomings of existing solutions are mainly concentrated in two aspects. On the one hand, there is a lack of deterministic work chains driven by edge contexts and capable of formal verification: traditional methods are mostly based on general processes or manual procedures, and the sequence and mutual exclusion of actions often remain at the level of experience, making it difficult to generate a unique list of operating procedures in the cloud, resulting in different execution sequences for the same context at different sites. On the other hand, there is a lack of risk pre-quantification and provable release directly aligned with electrical safety: usually only static compliance verification is performed, and power flow sensitivity and protection margin coupling indicators are rarely combined with sequence selection and release authorization, making it difficult to achieve minimum authority and traceability of "only this path, only this time, only this context" during the execution phase. Summary of the Invention

[0004] In view of the aforementioned existing problems, the present invention is proposed.

[0005] Therefore, this invention provides a remote operation and maintenance management method for power grid secondary equipment based on cloud-edge collaboration to solve the problems of insufficient determinism in operation sequences and lack of strongly coupled, verifiable constraints.

[0006] To solve the above-mentioned technical problems, the present invention provides the following technical solution:

[0007] This invention provides a remote operation and maintenance management method for power grid secondary equipment based on cloud-edge collaboration. The method includes: collecting station-side operational data; obtaining an action dependency graph through fixed-value pressure plate logic calculation and performing deterministic sorting to generate a list of operating procedures for power grid secondary equipment; performing a power flow sensitivity impact assessment on the list of operating procedures to obtain the minimum risk path; implementing micro-time window slicing based on the minimum risk path using an evidence fingerprinting sequence slicing algorithm and mirroring it with the station-side operational data to generate a zero-trust release credential; establishing a controlled session based on the zero-trust release credential and generating an execution record summary through context mirroring; and performing consistency verification and validation against the zero-trust release credential based on the execution record summary to generate a verification receipt report.

[0008] As a preferred embodiment of the remote operation and maintenance management method for power grid secondary equipment based on cloud-edge collaboration described in this invention, the station-side operation data includes topology snapshots, secondary equipment configurations, clock synchronization deviations, and communication link status.

[0009] The operational data collected at the acquisition station is used to obtain an action dependency graph through fixed-value pressure plate logic calculation. The specific steps are as follows.

[0010] The station-side operation data is timestamped, the operation data package is obtained, and a standard consistency check is performed to generate a context field set;

[0011] Based on the context field set, the action dependency graph is generated by solving the logic through a fixed-value pressure plate and performing consistent playback calibration.

[0012] As a preferred embodiment of the remote operation and maintenance management method for power grid secondary equipment based on cloud-edge collaboration described in this invention, the generation of the power grid secondary equipment operation procedure list refers to generating the power grid secondary equipment operation procedure list by performing deterministic sorting based on the action dependency graph and using the lexicographical topological sorting method.

[0013] As a preferred embodiment of the remote operation and maintenance management method for power grid secondary equipment based on cloud-edge collaboration described in this invention, the specific steps for performing a power flow sensitivity impact assessment on the power grid secondary equipment operation procedure list are as follows:

[0014] Extract the list dependencies from the list of operating procedures for secondary equipment in the power grid, align them one by one with the context field set, and obtain the action evaluation queue.

[0015] Based on the action evaluation queue and context field set, a list of action risk tickets is generated by calculating the power flow sensitivity indicator.

[0016] As a preferred embodiment of the cloud-edge collaborative remote operation and maintenance management method for power grid secondary equipment described in this invention, the specific steps for obtaining the minimum risk path are as follows:

[0017] Extract a limited number of candidate sequences from the action risk ticket list, and obtain a sequence risk ranking table by calculating the sequence risk score;

[0018] Based on the sequence risk ranking table, the path with the least risk is obtained by step-by-step short-circuit decision-making and binding it with the timestamp of the station operation data.

[0019] As a preferred embodiment of the remote operation and maintenance management method for power grid secondary equipment based on cloud-edge collaboration described in this invention, the specific steps of implementing micro-time window slicing based on the minimum risk path and using an evidence fingerprinting sequence slicing algorithm are as follows:

[0020] Based on the least risk path and station operation data, the evidence fingerprint ID is calculated, and combined with clock synchronization deviation and communication link status, a micro time window table is obtained.

[0021] Extract the start and end times of the micro-time window for the path with the lowest risk in the micro-time window table, and combine them with the secondary equipment configuration to perform license slicing for each item, and output a time window equipment pairing list.

[0022] As a preferred embodiment of the remote operation and maintenance management method for power grid secondary equipment based on cloud-edge collaboration described in this invention, the generation of zero-trust release credentials refers to calculating the sequence verification digest based on the time window equipment pairing list and obtaining the zero-trust release credentials.

[0023] As a preferred embodiment of the remote operation and maintenance management method for power grid secondary equipment based on cloud-edge collaboration described in this invention, the step of establishing a controlled session based on zero-trust release credentials refers to comparing the evidence fingerprint ID in the zero-trust release credentials with the topology snapshot in the station operation data to generate a controlled session.

[0024] As a preferred embodiment of the remote operation and maintenance management method for power grid secondary equipment based on cloud-edge collaboration described in this invention, the specific steps for generating the execution record summary are as follows:

[0025] Based on the controlled session, locate the current step to be executed, and generate a pre-step context fingerprint by combining the station's running data;

[0026] Perform a field-by-field mirroring and verification of the context fingerprint before the step, and obtain a summary of execution records through the window sequence verification method.

[0027] As a preferred embodiment of the remote operation and maintenance management method for power grid secondary equipment based on cloud-edge collaboration described in this invention, the specific steps for summarizing execution records, comparing and verifying consistency with zero-trust release credentials, and generating a verification receipt report are as follows.

[0028] Based on the summary of execution records and zero-trust release credentials, a mapping relationship is established, and a mirror comparison is performed with the context field set to obtain the context consistency mark table;

[0029] Based on the mapping relationship, the system progressively verifies whether each tag in the context consistency tag table falls within the corresponding time window in the micro time window table, and generates a time window consistency tag table.

[0030] Perform deviation verification between the context consistency flag table and the time window consistency flag table, and generate a verification receipt report.

[0031] The beneficial effects of this invention are as follows: by performing power flow sensitivity assessment on the list of operating procedures for secondary equipment in the power grid and selecting the path with the least risk through stepwise short-circuit decision-making, the effects of interpretable sequence selection, cross-site consistency, and improved one-time pass rate of the plan are improved. Attached Figure Description

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

[0033] Figure 1 This is a flowchart of a remote operation and maintenance management method for power grid secondary equipment based on cloud-edge collaboration.

[0034] Figure 2 A flowchart for generating a list of operating procedures for secondary power grid equipment.

[0035] Figure 3 A flowchart for obtaining zero-trust clearance credentials.

[0036] Figure 4 A flowchart for obtaining a verification receipt report. Detailed Implementation

[0037] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, the specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

[0038] Many specific details are set forth in the following description in order to provide a full understanding of the invention. However, the invention may also be practiced in other ways different from those described herein, and those skilled in the art can make similar extensions without departing from the spirit of the invention. Therefore, the invention is not limited to the specific embodiments disclosed below.

[0039] Secondly, the term "one embodiment" or "embodiment" as used herein refers to a specific feature, structure, or characteristic that may be included in at least one implementation of the present invention. The phrase "in one embodiment" appearing in different places in this specification does not necessarily refer to the same embodiment, nor is it a single or selective embodiment that is mutually exclusive with other embodiments.

[0040] Reference Figures 1-4 This is one embodiment of the present invention, which provides a remote operation and maintenance management method for power grid secondary equipment based on cloud-edge collaboration, including the following steps:

[0041] S1: Collect station-side operation data, obtain action dependency graph through fixed value pressure plate logic calculation, perform deterministic sorting, and generate a list of operation procedures for power grid secondary equipment.

[0042] S1.1: Station-side operational data includes topology snapshots, secondary equipment configurations, clock synchronization deviations, and communication link status;

[0043] Specifically, the topology snapshot is derived from the current location information and connectivity of primary and secondary switching quantities at the station. Based on the collection batch time, the status points of circuit breakers, disconnectors, and disconnectors in each bay are stitched together with the connectivity table to form a connection and disconnection diagram at that time.

[0044] The secondary equipment configuration is derived from the parameters and configuration files within the device. The device's functional settings, pressure plate position definitions, point codes, and circuit descriptions are exported in read-only mode and collected together with the equipment identification information to form a configuration list.

[0045] The clock synchronization deviation comes from the time synchronization results of the device's local time and the station's reference time source in the same batch. The time deviation of each device relative to the reference is obtained by reading the time synchronization results.

[0046] The status of the communication link is derived from the reachability and quality indicators of the links in the current batch. By reading the records of heartbeat, round-trip delay, packet loss rate, retransmission count, etc. reported by the reading device and the communication equipment in the station, the conclusions of link availability and stability are summarized.

[0047] S1.2: Unify the timestamps of the station's running data, obtain the running data packets, perform standard consistency checks, and generate a context field set;

[0048] It should be noted that the timestamp and device identifier of each record in the station operation data are read separately; the time is reported using the clock synchronization deviation and corrected one by one to align all records with the unified reference time, and the corrected time is written back to the corresponding station operation data; the data is merged according to the device identifier and timestamp to form an operation data packet containing topology snapshot, secondary device configuration, clock synchronization deviation, and communication link status.

[0049] The equipment identifier, point code, setting value number, pressure plate position name, and circuit description are directly extracted from the secondary equipment configuration and topology snapshot in the operation data package as verification benchmarks; the case and separators of the corresponding fields in the operation data package are standardized and the characters are normalized; the correspondence between the setting value number and each record in the station operation data is compared item by item within the operation data package (e.g., "low voltage protection setting value number Umin-01" corresponds to "the protection device of the third bay of the substation adopts setting zone B, and the threshold voltage is 65% of the rated voltage"), and the one-to-one correspondence between the pressure plate position name and the point code (e.g., "locking reclosing") is compared with that of the current setting value number Umin-01. The name of the pressure plate position, "In Operation," corresponds one-to-one with the text description "Reclosing function is in operation" in the operation record. The connection relationship referenced in the loop description and the connection relationship in the topology snapshot (for example, the loop description "trip loop is connected to the output relay after passing through the disconnection detection unit" is consistent with the connection sequence "trip loop → disconnection detection → output relay" in the topology snapshot, which is described as a consistent connection path) are retained if they are consistent, and removed from this batch if they are inconsistent. After verification, the set value items, pressure plate positions, points and loop relationships are extracted from the verification records according to the equipment identifier and batch time, and merged into a context field set.

[0050] S1.3: The context field set includes fixed value items, pressure plate positions, point positions and loop relationships;

[0051] Specifically, the setting items are used to provide the action threshold, action time limit and setting range information of relay protection and automation functions. The setting items directly participate in the judgment of whether a candidate action meets the input conditions, whether it touches the protection coordination boundary and the subsequent power flow sensitivity assessment.

[0052] The pressure plate position is used to represent the engaged, disengaged, and locked states. The pressure plate position directly determines the logical boundary between permitted and prohibited actions and is the main source of preconditions and mutual exclusions.

[0053] The point-to-loop relationship is used to map measurement points, control points and connected topologies one by one. The point-to-loop relationship supports the identification of the action influence range, interlocking path constraints and concurrent restrictions on the same connected branch.

[0054] S1.4: Based on the context field set, the action dependency graph is generated by solving the logic through the fixed value pressure plate and performing consistent playback calibration.

[0055] It should be noted that each "engage / retract" definition in the pressure plate position is extracted to generate a "pressure plate engagement / retract" action; each "setup area switching" definition in the setup item is extracted to generate a "setup area switching" action, and the loop identifier in the point-to-loop relationship is used to label the loop to which each action belongs;

[0056] Based on the existing information in the context field set, the "setpoint switching" action is passed to locate the relevant pressure plate position in the "pressure plate in action" state, and the relationship "relevant pressure plate position in action → setpoint switching" is recorded as the preceding edge; for the pressure plate positions marked as "pressure plate out", a mutual exclusion edge of "locked pressure plate ↔ restricted action" is established; for two actions that belong to the same loop and have opposite directions of action in the relationship between the point and the loop, a mutual exclusion edge of "two actions ↔ mutual exclusion" is established.

[0057] Based on the current input / output status of the pressure plate position and the current on / off relationship in the relationship between the position and the loop, delete the preceding edge that does not conform to the current state, delete the mutual exclusion edge that cannot be triggered due to the current loop being disconnected, and merge the duplicate edges; finally, with "action" as the node and preceding edge and mutual exclusion edge as the constraint edge, output the action dependency graph.

[0058] In a better way, the fixed-value pressure plate logic solution eliminates the ambiguity of the order of actions and ensures that the same context generates a consistent execution sequence at different stations, making the mutual exclusion and dependency relationships such as pressure plate status and fixed-value area switching computable and traceable; providing a structured and quantifiable input basis for subsequent power flow sensitivity assessment and risk path selection.

[0059] S1.5: Based on the action dependency graph, a deterministic sorting is performed using lexicographical topological sorting to generate a list of operating procedures for power grid secondary equipment.

[0060] It should be noted that the number of preceding edges for each action is counted and the injection degree is marked. An executable set is constructed from actions with an in-degree of zero and whose mutual exclusion edges have not been triggered. For actions in the executable set, the device identifiers given in the context field set are concatenated into comparison keys. All actions in the executable set are compared with the comparison keys and sorted to generate a unique ordered list. The first action in the unique ordered list is extracted and written into the power grid secondary equipment operation procedure list and the writing sequence number is recorded. After writing, all outgoing preceding edges of this action are deleted in the action dependency graph, and actions with mutual exclusion edges with this action are marked as not executable in the current round.

[0061] The in-degree of affected actions is recalculated and a new set of executable actions is updated accordingly until there are no unprocessed actions in the action dependency graph. Finally, a list of operating procedures for power grid secondary equipment is formed, arranged in a unique sequence number.

[0062] S2: Perform a power flow sensitivity impact assessment on the list of operating procedures for secondary equipment in the power grid to obtain the path with the least risk.

[0063] S2.1: Extract the list dependencies from the list of operating procedures for secondary power grid equipment, align them one by one with the context field set, and obtain the action evaluation queue;

[0064] It should be noted that the actions are read sequentially from the list of operating procedures for secondary equipment of the power grid, and the action number, sequence number and reference of the preceding action are recorded. Based on the point and loop relationship in the context field set, the control point corresponding to the action is mapped to the primary equipment branch number and the measurement and control loop identifier as the key. The set value item in the context field set is used to look up the set value number, action threshold and coordination boundary corresponding to the action function. Then, the name of the pressure plate related to the action and the current engaged, disengaged and locked status are extracted from the pressure plate position in the context field set.

[0065] The "Action Number, Sequence Number, Equipment Identifier, List of Affected Branches, Measurement and Control Circuit Identifier, Associated Setting Number and Related Thresholds, Associated Pressure Plate Name and Current Status, and Set of Preceding Actions" are merged into a single evaluation item and written into the action evaluation queue. Within the same processing, duplicate branch items generated by the same action are deduplicated and merged according to the branch number. The same process is repeated for all actions in the list of operating procedures for power grid secondary equipment, and evaluation items are generated sequentially according to the list order. Finally, the action evaluation queue is output in sequence.

[0066] S2.2: Based on the action evaluation queue and context field set, calculate the power flow sensitivity indicator and compare it with the set value to generate a list of action risk tickets;

[0067] It should be noted that, in the topology snapshot, the baseline operating conditions of the affected branches and telemetry and control loops corresponding to each evaluation item are read. Then, based on the action type recorded in the action evaluation queue and the setpoint items or pressure plate position conditions in the context field set, a virtual micro-change scenario consistent with the action is constructed for each evaluation item (e.g., setpoint area switching according to the minimum step of the setpoint item, pressure plate activation / deactivation according to the loop conduction or deactivation). At the corresponding batch time in the topology snapshot, the measured power of the branch in the station-end operation data is extracted as the branch reference power. Subsequently, the power flow sensitivity indication is calculated only around the affected branches and telemetry and control loops, with the expression as follows:

[0068] ;

[0069] in, This is a power flow sensitivity indicator. The number of affected branch roads, The index value for the number of affected branches. This represents the power change of the branch circuit. This represents the branch reference power in the topology snapshot.

[0070] Read the action numbers and equipment identifiers in the action evaluation queue one by one according to the order of the power grid secondary equipment operation procedure list, and locate the corresponding action thresholds and coordination boundaries in the context field set using the action number and equipment identifier. First, directly compare the power flow sensitivity indicator with the action threshold to obtain the judgment of "threshold not reached" or "threshold reached", and then directly compare it with the coordination boundary to obtain the judgment of "boundary not touched" or "boundary touched". After completing the two comparisons, merge the action number, equipment identifier, list of affected branches, power flow sensitivity indicator, action threshold comparison conclusion and coordination boundary comparison conclusion into a single action risk ticket and write it into the action risk ticket list according to the order of the power grid secondary equipment operation procedure list.

[0071] Furthermore, the action threshold refers to the minimum or maximum physical quantity condition required to trigger a protection or control action, as given in the setting items of the context field set. For example, overcurrent protection is allowed to operate when the line current reaches 1.5 times the rated current and lasts for 0.2 seconds.

[0072] Coordination boundaries are the allowable operating ranges and time and amplitude constraints between adjacent devices and upper and lower level protections given in the context field set to ensure protection coordination and selectivity. They are used to limit the boundary conditions that the operation should not exceed or precede. For example, the time limit for overcurrent protection at the feeder end is 0.3 seconds, and the time limit for overcurrent protection at the upper bus side is 0.6 seconds with a higher current setting, to ensure that the lower level operates first and the upper level operates later.

[0073] The preferred approach is to establish a direct correlation between the operation sequence and the dynamic power flow of the power grid. By quantitatively assessing the sensitivity of each operation step to the dynamic power flow of the power grid, abstract electrical risks are transformed into comparable numerical indicators. The joint verification of secondary equipment operation and power flow safety enables collaborative verification across professional fields, ensuring that operation and maintenance operations meet both the requirements of the regulations and the actual operating status of the power grid.

[0074] S2.3: Extract a limited number of candidate sequences from the action risk ticket list, and obtain a sequence risk ranking table by calculating the sequence risk score;

[0075] It should be noted that within the same batch, adjacent actions are first scanned sequentially from the list of operating procedures for secondary power grid equipment according to the action dependency graph. Then, adjacent actions are scanned one pair at a time according to the list of operating procedures for secondary power grid equipment. If all the prerequisites in the action dependency graph are included in the currently completed prefix and the context field set does not show that there is mutual exclusion or conflict of execution elements between adjacent actions, it is determined to be "no prerequisite relationship conflict and no mutual exclusion edge". All adjacent action pairs are retained to obtain a finite candidate sequence containing only a single adjacent swap.

[0076] In a finite candidate sequence, steps that "reach the boundary" are classified as high-risk steps; steps that "reach the threshold but do not reach the boundary" are classified as medium-risk steps; and steps that "do not reach the threshold but do not reach the boundary" are classified as low-risk steps. The number of high-risk steps and medium-risk steps are counted, and the position of the first occurrence of a high-risk step in the sequence and the total number of affected branches involved in the sequence are recorded. A sequence risk score is then calculated. All candidate sequences are sorted by their sequence risk scores from smallest to largest to obtain a sequence risk ranking table. The expression for calculating the sequence risk score is:

[0077] ;

[0078] in, For sequence risk scoring, For high-risk steps, For medium-risk steps, The position of the first high-risk step is N, where N is the number of affected branches. The weighting coefficient for the number of medium-risk steps. The weighting coefficient for the first high-risk step position. The weighting coefficient is the total number of affected branches.

[0079] The weighting coefficient for the number of risk steps is calculated by collecting a list of action risk tickets and using the results of step-by-step short-circuit decisions to infer the actual contribution ratio of risk steps. An exemplary value range is as follows: ;

[0080] The weighting coefficient for the location of the first high-risk step is calibrated on-site by comparing the correlation between the location of the first high-risk step and the actual risk level. An exemplary value range is as follows: ;

[0081] The weighting coefficient for the total number of affected branches is obtained by fitting the statistical relationship between the number of affected branches and the operation success rate using the least squares method. An exemplary range of values ​​is as follows: ;

[0082] S2.4: Based on the sequence risk ranking table, the path with the least risk is obtained by step-by-step short-circuit decision-making and by binding it with the timestamp of the station operation data.

[0083] It should be noted that, based on the sequence risk ranking table, the candidate sequence with the smallest value and the highest ranking in the sequence risk ranking table is selected as the unique result by comparing each item in the order of "number of high-risk steps → number of medium-risk steps → position of the first occurrence of a high-risk step → total number of affected branches".

[0084] If there are multiple unique results, the device identifier given by the context field set will be used for adjudication. After determining the unique result, the step order of the power grid secondary equipment operation procedure list will be used to pair each step in the sequence with the batch time of the same batch of station-end operation data to form a step time binding record. The unique result will be merged with all step time binding records to output the path with the least risk.

[0085] S3: Based on the minimum risk path, micro-time window slicing is implemented through the evidence fingerprinting sequence slicing algorithm, and mirrored and anchored with the station operation data to generate zero-trust release credentials.

[0086] S3.1: Based on the minimum risk path and station operation data, calculate the evidence fingerprint ID, and combine it with clock synchronization deviation and communication link status to obtain a micro time window table;

[0087] It should be noted that, step number, device identifier and step time binding record are extracted one by one in the step order of the least risk path, and corresponding connectivity summary, functional value and point code summary are extracted from topology snapshot and secondary equipment configuration. The "step number, device identifier, step time binding record, connectivity summary, functional value and point code summary" are concatenated into fingerprint material sequence as evidence fingerprint ID;

[0088] Locate the entry with the same timestamp in the clock synchronization deviation record of the station-side operation data according to the step number and device identifier in the minimum risk path, and directly read the relative reference deviation and round-trip delay in the communication link status in the entry; take the difference between the step time binding record and the relative reference deviation as the start time based on the round-trip delay in the communication link status; take the sum of the step time binding record and the relative reference deviation as the end time; summarize all micro time window rows from the start time to the end time according to the step number to generate a micro time window table.

[0089] S3.2: Extract the start and end times of the micro-time window for the minimum risk path in the micro-time window table, and output the time window device pairing list in combination with the secondary device configuration;

[0090] It should be noted that, firstly, the corresponding record is located in the micro-time window table by step number, and the start and end times of the micro-time window are read. Then, the corresponding device entry is retrieved in the secondary device configuration by the device identifier of the same step record in the minimum risk path, and the function setting reference and point code related to the device action are obtained. The "step number, start time, end time, device identifier, function setting reference, and point code" are assembled into a pairing record and written into the list. After all steps are processed, they are sorted in order according to step number to generate a time window device pairing list.

[0091] S3.3: Based on the device pairing list within the time window, generate license slices item by item, and obtain zero-trust release credentials by calculating the order verification digest.

[0092] It should be noted that, based on the time window device pairing list, the “step number, start time, end time, device identifier, function setting reference and point code” are read sequentially from the time window device pairing list according to the step number, serialized into a single license slice in a fixed order and uniform format, and immediately written into the license slice sequence.

[0093] The evidence fingerprint ID is placed at the beginning of the sequence of the license slice as binding information. Then, all serialized content is concatenated at once according to the order of the license slices in the sequence to obtain the license slice content and license slice order. The license slice content and license slice order are then normalized and concatenated with fixed delimiters, and the digest of the previous slice is also included to generate the order verification digest.

[0094] The evidence fingerprint ID, sequential verification digest, and permission slice sequence are encapsulated together, and the start and end times recorded in each permission slice are directly used as the effective time limit for the corresponding step, forming a zero-trust release credential that only covers all steps of the minimum risk path and is subject to time window restrictions.

[0095] The superior evidence fingerprinting sequence slicing algorithm establishes a spatiotemporal binding between the operation sequence and the physical device, and ensures that each operation step can only be executed on a specific device within a specific time window through micro time window slicing; and creates verifiable digital identity credentials, and the zero-trust release credential generated based on the sequential verification digest has uniqueness and tamper-proof properties.

[0096] S4: Establish a controlled session based on zero-trust release credentials and generate an execution record summary through context mirroring.

[0097] S4.1: Compare the evidence fingerprint ID in the zero-trust release credential with the topology snapshot in the station operation data to generate a controlled session;

[0098] It should be noted that the first "step number, device identifier, location code, function setting reference, start time, and end time" in the evidence fingerprint ID and permission slice sequence are read from the zero-trust release credential. The topology snapshot and secondary device configuration are located in the station-side running data and "step number, device identifier, step time binding record, connectivity summary, function setting and location code summary" are concatenated in a fixed field order to generate the fingerprint material row.

[0099] Extract single-step fingerprints from the fingerprint material row and concatenate the remaining single-step fingerprints in step order to generate a recalculated evidence fingerprint ID. When the recalculated evidence fingerprint ID is completely consistent with the evidence fingerprint ID in the zero-trust release credential, and the current time falls within the "start time - end time" interval of the first license slice after clock synchronization deviation correction, the controlled session is obtained.

[0100] S4.2: Based on the controlled session, locate the current step to be executed, and generate a pre-step context fingerprint by combining the station's running data;

[0101] It should be noted that the step number, device identifier, and corresponding point code, function setting reference, start time, and end time are read from the controlled session. The pressure plate position status, loop on / off status, and function setting content are extracted item by item from the station operation data according to the device identifier and point code. At the same time, the clock synchronization deviation is read to perform a one-time correction on the current time. Then, the "step number, corrected current time, device identifier, point code, function setting reference and function setting content, pressure plate position status, loop on / off status, start time, and end time" are uniformly encoded into a context byte sequence as a pre-step context fingerprint according to a fixed field order.

[0102] S4.3: Perform field-by-field mirroring and verification on the context fingerprint before the step, and obtain the summary of execution records through window sequence verification method.

[0103] It should be noted that the "step number, corrected current time, device identifier, location code, function setting reference, function setting content, pressure plate position status, loop on / off status, start time, and end time" in the pre-step context fingerprint are used to locate the corresponding license slice by step number in the zero-trust release credential and extract the "device identifier, location code, function setting reference, start time, and end time". The context is considered consistent if the device identifier, location code, function setting reference, function setting content, pressure plate position status, and loop on / off status are consistent.

[0104] If the current time after context consistency falls between the start and end times, and the step number to be executed in the controlled session record (the difference between the license slice sequence number in the zero-trust release credential within the controlled session and the number of completed steps in the execution record summary) equals the step number, then it is determined to be in order within the window. In order means that the step number in the execution record summary matches the step number of the corresponding license slice in the zero-trust release credential. In window means that the execution timestamp falls within the closed interval of the start and end times of the corresponding micro-time window. The criteria for in order and in window are defined as follows: "Simultaneous fulfillment of conditions" is marked as a consistency indicator. For example, in a zero-trust release credential, the permitted slice is "step number = 5, micro time window = 10:02:00~10:02:30". The controlled session currently has "step number to be executed = 5" and the actual execution time in the execution record summary is "10:02:12". Therefore, the step number is consistent and the time falls within 10:02:00~10:02:30, which is judged as "in order and in window". If either condition is missing, it is recorded as inconsistent and the release verification of subsequent step numbers is rejected.

[0105] The conclusions that are consistent with the context and the conclusions that are in the window and in order are merged into a single-step result, and the entry time and exit time are recorded. The results are then appended sequentially according to the step number to generate an execution record summary.

[0106] S5: Based on the summary of execution records, perform consistency verification and validation against the zero-trust release credentials, and generate a verification receipt report.

[0107] S5.1: Based on the summary of execution records and zero-trust release credentials, establish a mapping relationship and perform a mirror comparison with the context field set to obtain the context consistency mark table;

[0108] It should be noted that the device identifier, location code, and function setting reference for the corresponding step are read from the zero-trust release credential. The same step is located in the execution record summary, and the function setting content, pressure plate position status, and circuit on / off status are recorded. The step number and device identifier form a connection key, and a one-to-one match is performed between the zero-trust release credential and the execution record summary. For example, if the zero-trust release credential gives "step=3, device=protection device A, location=trip command, function setting reference=section fault setting D1", the corresponding entry is found in the execution record summary, all matching results are counted, and a mapping relationship is established.

[0109] Based on the mapping relationship, a mirror comparison is performed field by field in the context field set using the device identifier and the location code. If the device identifier matches, it is recorded as "device matches / no"; if the location code matches, it is recorded as "location matches / no"; if the function setting referenced by the function setting matches the function setting content in the execution record summary, it is recorded as "setting matches / no"; if the pressure plate position allowed status given by the context field set matches the pressure plate position status in the execution record summary, it is recorded as "pressure plate matches / no"; if the loop continuity expectation given by the context field set matches the loop continuity status in the execution record summary, it is recorded as "loop matches / no".

[0110] After the comparison is completed, write a row of tags in the order of the fields "step number, equipment consistency / no, location consistency / no, setting consistency / no, pressure plate consistency / no, and circuit consistency / no", and summarize them into a context consistency tag table in the order of step number.

[0111] S5.2: Based on the mapping relationship, step by step verify whether each tag in the context consistency tag table falls into the corresponding time window in the micro time window table, and generate the time window consistency tag table.

[0112] It should be noted that, based on the mapping relationship, the current step in the context consistency flag table is located to the entry time and exit time in the execution record summary; the start time and end time are read in the micro time window table according to the same step number; it is determined whether the entry time and exit time fall between the start time and end time, and whether the entry time is earlier than the exit time; then it is determined whether the step number is continuously incremented with the previous passed step number recorded in the mapping relationship; when both determinations are true, the current step is marked as "in window and in order", and when either determination is false, it is marked as "out of window or out of order", and the specific fields and time values ​​that are not satisfied are recorded;

[0113] Generate a time window consistency flag table by assigning "step number, entry time, exit time, start time, end time, and in window in order / out of window or out of order" to a fixed field order.

[0114] S5.3: Perform deviation verification between the context consistency flag table and the time window consistency flag table, and generate a verification receipt report.

[0115] It should be noted that the context consistency flag table and the time window consistency flag table are aligned one by one using the step number as the index, and fields such as "equipment consistency / no", "location consistency / no", "set value consistency / no", "pressure plate consistency / no", "loop consistency / no" and "in window in sequence / out of window or out of sequence" are read to generate single-step deviation flags;

[0116] If any context field is "inconsistent" or the time window field is "out of window or out of order", then write "step number, specific inconsistent field name, corresponding comparison value, entry time, exit time, start time and end time" into the deviation list; if all are consistent and are "in window and in order", then write them into the pass list.

[0117] Based on the deviation list and the pass list, the number of passed steps, the number of steps with inconsistent context, and the number of steps that are out of window or out of order are counted, and the step number of the first deviation is located. At the same time, the evidence fingerprint ID, the sequence verification summary, and the summary information of the execution record summary in the zero trust release credential are read, and "pass" or "fail" is given according to "whether the deviation list is empty", and the verification receipt report is output.

[0118] In summary, this invention improves the interpretability of sequence selection, cross-site consistency, and the planned first-pass rate by performing power flow sensitivity assessment on the list of operating procedures for secondary equipment in the power grid and selecting the least risk path through stepwise short-circuit decision-making.

[0119] It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention, and all such modifications or substitutions should be covered within the scope of the claims of the present invention.

Claims

1. A remote operation and maintenance management method for power grid secondary equipment based on cloud-edge collaboration, characterized in that: include, The system collects operational data from the acquisition station, obtains an action dependency graph through the logic calculation of the fixed-value pressure plate, performs deterministic sorting, and generates a list of operating procedures for power grid secondary equipment. For the list of operating procedures for secondary equipment in the power grid, conduct a power flow sensitivity impact assessment to obtain the least risky path; Based on the minimum risk path, micro-time window slicing is implemented through the evidence fingerprinting sequence slicing algorithm, and mirrored and anchored with the station operation data to generate zero-trust release credentials. A controlled session is established based on zero-trust release credentials, and an execution log summary is generated through context mirroring. Based on the summary of execution records, a consistency check and verification is performed against the zero-trust release credential, and a verification receipt report is generated.

2. The remote operation and maintenance management method for power grid secondary equipment based on cloud-edge collaboration as described in claim 1, characterized in that: The station-side operational data includes topology snapshots, secondary equipment configurations, clock synchronization deviations, and communication link status. The specific steps for obtaining the action dependency graph through fixed-value pressure plate logic calculation are as follows. The station-side operational data is timestamped and a standard consistency check is performed to generate a context field set; Based on the context field set, the action dependency graph is generated by solving the logic through a fixed-value pressure plate and performing consistent playback calibration.

3. The remote operation and maintenance management method for power grid secondary equipment based on cloud-edge collaboration as described in claim 2, characterized in that: The process of generating the list of operating procedures for secondary power grid equipment refers to generating the list of operating procedures for secondary power grid equipment by performing deterministic sorting based on the action dependency graph and using the lexicographical topological sorting method.

4. The remote operation and maintenance management method for power grid secondary equipment based on cloud-edge collaboration as described in claim 3, characterized in that: The aforementioned list of operating procedures for secondary power grid equipment includes a power flow sensitivity impact assessment, with the specific steps outlined below. Extract the list dependencies from the list of operating procedures for secondary equipment in the power grid, and align them with the context field set by numbering to obtain the action evaluation queue. Based on the action evaluation queue and context field set, the power flow sensitivity indicator is calculated, and quadrant risk level mapping is performed to generate a list of action risk tickets.

5. The remote operation and maintenance management method for power grid secondary equipment based on cloud-edge collaboration as described in claim 4, characterized in that: The specific steps for obtaining the minimum risk path are as follows: Extract a limited number of candidate sequences from the action risk ticket list, calculate the sequence risk score, and aggregate them in a fixed order to obtain a sequence risk ranking table; Based on the sequence risk ranking table, the path with the least risk is obtained by step-by-step short-circuit decision-making and binding it with the timestamp of the station operation data.

6. The remote operation and maintenance management method for power grid secondary equipment based on cloud-edge collaboration as described in claim 5, characterized in that: The method for implementing micro-time window slicing based on the minimum risk path and using the evidence fingerprinting sequence slicing algorithm involves the following specific steps. Based on the minimum risk path and station operation data, the evidence fingerprint ID is calculated, and the delay joint calibration slice is performed by combining clock synchronization deviation and communication link status to obtain the micro time window table. Extract the start and end times of the micro-time window for the path with the lowest risk in the micro-time window table, and combine them with the secondary device configuration. Perform item-by-item licensing slices through the start and end time configuration mapping, and output a list of time window device pairings.

7. The remote operation and maintenance management method for power grid secondary equipment based on cloud-edge collaboration as described in claim 6, characterized in that: The process of generating zero-trust release credentials involves calculating the sequential verification digest and performing step increments based on the device pairing list within the time window to obtain zero-trust release credentials.

8. The remote operation and maintenance management method for power grid secondary equipment based on cloud-edge collaboration as described in claim 7, characterized in that: The establishment of a controlled session based on zero-trust release credentials refers to comparing the evidence fingerprint ID in the zero-trust release credentials with the topology snapshot in the station operation data to generate a controlled session.

9. The remote operation and maintenance management method for power grid secondary equipment based on cloud-edge collaboration as described in claim 8, characterized in that: The specific steps for generating the execution record summary are as follows. Based on the controlled session, locate the current step to be executed, and generate a pre-step context fingerprint by combining the station's running data; Perform a field-by-field mirroring and verification of the context fingerprint before the step, and obtain a summary of execution records through the window sequence verification method.

10. The remote operation and maintenance management method for power grid secondary equipment based on cloud-edge collaboration as described in claim 9, characterized in that: The process of summarizing execution records, comparing them against zero-trust release credentials for consistency verification, and generating a verification receipt report involves the following steps: Based on the summary of execution records and zero-trust release credentials, a mapping relationship is established, and a mirror comparison is performed with the context field set to obtain the context consistency mark table; Based on the mapping relationship, the system verifies step by step whether each tag in the context consistency tag table falls into the corresponding time window in the micro time window table, and generates a time window consistency tag table. Perform deviation verification between the context consistency flag table and the time window consistency flag table, and generate a verification receipt report.