Remote configuration method of pole-mounted circuit breaker self-healing control logic parameters

Abstract

The present application belongs to the technical field of power supply network self-healing control and power distribution automation parameter configuration, and relates to a method for remotely configuring parameters of pole-mounted circuit breaker self-healing control logic. The method acquires feeder topology, circuit breaker state, adjacent switch relationship, main power supply path and tie-in transfer path, constructs a self-healing logic diagram with pole-mounted circuit breakers as nodes, identifies power supply side protection, fault isolation, branch line branch, tie-in transfer and other topological roles, generates a fault path constraint set in combination with fault current direction, voltage loss section and adjacent device state, forms a protection action, isolation delay, reclosing, tie-in closing and locking condition parameter package accordingly, and issues the parameter package after checking topology consistency, action timing and transfer path, and enables the parameter package by matching local state, role and version on site. The method keeps remote configuration parameters consistent with actual electrical path and self-healing action chain, and reduces the risk of overstep tripping, repeated isolation, false transfer and fault closing.

Description

Technical Field

[0001] This invention belongs to the technical field of power supply and distribution network self-healing control and power distribution automation parameter configuration, and relates to a method for remotely configuring parameters of pole-mounted circuit breaker self-healing control logic. Background Technology

[0002] In the operation of distribution network feeders, pole-mounted circuit breakers are typically installed at main line sections, branch line connections, near tie points, or at the power supply side protection boundary. They are used to disconnect faulty sections in the event of short circuits, grounding, or undervoltage, and to work with adjacent switches to restore power to non-faulty sections. Current technology generally involves the master station or distribution automation terminal collecting data on the pole-mounted circuit breaker's open / close position, protection activation, fault current, undervoltage restoration, and online communication status, creating a feeder operation screen and equipment ledger on the master station side. Self-healing control logic is usually pre-written into the field controller, which performs local judgment based on protection settings, action delay, reclosing count, blocking conditions, and tie closing permission conditions. After a fault occurs, the field controller determines whether to trip, reclose, or allow the transmission of blocking or release of blocking information based on locally collected data and existing parameters. While this type of existing technology can retain local protection operation capabilities, the parameters for the self-healing logic still primarily rely on setting calculations during the design phase, operator experience, and configuration templates formed according to line type.

[0003] Existing remote configuration methods for pole-mounted circuit breaker parameters typically target a single device or a group of devices on the same feeder. The configuration terminal selects a corresponding template from a pre-set parameter library based on the device number, line name, switch type, protection function, and operating mode. It then packages and sends out information such as protection action values, fault confirmation time, isolation action time, reclosing strategy, remote blocking flag, and tie-off closing conditions. Upon receiving the information, the pole-mounted circuit breaker in the field performs message integrity verification, permission verification, and version number comparison. If the verification passes, the information is written to the operating parameter area or standby parameter area. Some existing technologies check the communication status and device online status before sending the information and require the device to return a configuration success flag afterward. The above process primarily ensures the correctness of parameter transmission and writing. The focus is on remote maintenance and batch parameter management. Protection coordination relationships, reclosing mutual exclusion relationships, power transfer closing permission relationships, and adjacent device blocking relationships between different pole-mounted circuit breakers within the same feeder are usually still manually preset at the template level.

[0004] In more conventional technologies, the configuration end introduces feeder diagrams or equipment ledgers to manually or semi-automatically associate the feeder where the pole-mounted circuit breaker is located, adjacent switches, and tie switches, and determines the basic protection coordination relationship based on the main power supply line, branch lines, and tie lines. This method generally configures the power supply side equipment with a longer operating delay, the downstream section or branch line equipment with a shorter operating delay, and the tie point equipment with the requirement that closing is allowed only after undervoltage and no fault alarm. For reclosing logic, a fixed number of times and fixed blocking conditions are usually set according to the equipment type. Although this type of existing technology adds line association information compared to pure template configuration, its processing object is still the static line level and equipment category. It does not treat the role changes of the pole-mounted circuit breaker in different fault paths, the mutual exclusion relationship of the activation of the backup power transfer path, and the action sequence of adjacent equipment as the same constraint object for unified generation and verification, making it difficult to cover the parameter adaptation requirements in scenarios such as operation mode switching, branch fault transfer, and tie path changes.

[0005] The remote configuration parameters of the self-healing control logic of pole-mounted circuit breakers lack a closed-loop binding with the actual feeder topology roles and fault path constraints. Specifically, when generating protection action parameters, isolation action delays, reclosing strategies, tie closing allowable conditions, and adjacent equipment interlocking conditions, the configuration end fails to determine the actual role of each pole-mounted circuit breaker in power supply side protection, fault isolation, branch line branching, tie transfer, or end load based on the current feeder topology. Furthermore, it fails to perform consistent verification of the action timing and transfer path within the same fault path before issuing the configuration. This results in the remote configuration being written and confirmed, but field devices may execute the self-healing logic with mismatched roles. In real fault scenarios, this leads to problems such as cascading tripping, repeated isolation, conflicts between reclosing and isolation actions, risk of closing with faults, or invalid restoration paths for non-faulty sections. Consequently, it becomes difficult for pole-mounted circuit breakers to form a stable fault isolation and power restoration chain according to the actual electrical paths. Summary of the Invention

[0006] The purpose of this invention is to provide a method for remotely configuring the parameters of the self-healing control logic of a pole-mounted circuit breaker, which can solve the problems mentioned in the background art.

[0007] To achieve the above objectives, the technical solution adopted by the present invention is as follows:

[0008] Remote configuration methods for the parameters of the self-healing control logic of pole-mounted circuit breakers include:

[0009] Acquire feeder topology data, pole-mounted circuit breaker status data, adjacent switch relationship data, main power supply path data, and interconnection transfer path data, and construct a self-healing logic graph with pole-mounted circuit breakers as nodes and electrical connection relationships as edges;

[0010] The topological role identifier of each pole-mounted circuit breaker is determined based on the self-healing logic diagram.

[0011] A fault path constraint set is generated based on the topological role identifier, fault current direction, undervoltage section, and the status of adjacent pole-mounted circuit breakers;

[0012] A remote configuration parameter package is generated based on the fault path constraint set, which includes protection action parameters, fault confirmation delay, isolation action delay, reclosing strategy, interconnection closing permission conditions, and adjacent equipment interlocking conditions.

[0013] The remote configuration parameter package is checked for topology consistency, action timing, and transfer path, and then sent to the corresponding pole-mounted circuit breaker after the checks are passed.

[0014] Preferably, the construction of the self-healing logic graph with pole-mounted circuit breakers as nodes and electrical connection relationships as edges includes:

[0015] The power supply points, trunk lines, branch lines, segment points, tie points, and load sections in the feeder topology data are mapped into graph data with power supply direction attributes.

[0016] Write the status data of the pole-mounted circuit breaker and the relationship data of the adjacent switches into the running status field of the corresponding node;

[0017] The main power supply path data and the interconnection power transfer path data are respectively marked as normal power supply side and backup power transfer side;

[0018] A mutual exclusion enable relationship is established between the normal power supply side and the backup power transfer side, and the mutual exclusion enable relationship is used as a topological constraint for the subsequent generation of self-healing control logic parameters.

[0019] Preferably, determining the topology role identifier of each pole-mounted circuit breaker based on the self-healing logic diagram includes:

[0020] Calculate the upstream path from each pole-mounted circuit breaker to the power source and the downstream path to the load section along the normal power supply side;

[0021] Calculate the tie-forward path that each pole-mounted circuit breaker can participate in along the standby transfer edge;

[0022] Based on the intersection relationship between the upstream path, the downstream path and the tie-forward path, write at least one topology role identifier among the power supply side protection boundary, fault isolation boundary, branch line boundary, tie-forward boundary or end load boundary for each pole-mounted circuit breaker.

[0023] When a circuit breaker on the same pole corresponds to multiple topology role identifiers, role priority is generated in the order of fault isolation taking precedence over interconnection and transfer.

[0024] Preferably, a fault path constraint set is generated based on the topology role identifier, fault current direction, undervoltage section, and adjacent pole-mounted circuit breaker status, including:

[0025] The set of reachable fault edges is determined based on the direction of the fault current; the set of sections to be isolated is determined based on the undervoltage section; and the set of operable nodes is determined based on the status of the adjacent pole-mounted circuit breakers.

[0026] The set of reachable fault edges, the set of sections to be isolated, and the set of actionable nodes are cross-constrained with the role priority to generate a set of fault path constraints that includes upstream blocking constraints, downstream isolation constraints, branch line priority isolation constraints, tie-line transfer prohibition constraints, and reclosing mutual exclusion constraints.

[0027] Preferably, generating a remote configuration parameter package according to the fault path constraint set includes:

[0028] The upstream blocking constraint is converted into the adjacent equipment blocking condition, the downstream isolation constraint and the branch priority isolation constraint are converted into the isolation action delay and protection action parameters, the tie-to-supply prohibition constraint is converted into the tie-to-closing allow condition, and the reclosing mutual exclusion constraint is converted into the reclosing strategy.

[0029] The converted parameters are bound according to the same fault path number, and the corresponding topology role identifier, applicable feeder version, parameter semantic summary and enable conditions are written into the remote configuration parameter package.

[0030] Preferably, the remote configuration parameter package is subjected to topology consistency verification, including:

[0031] Match the applicable feeder version carried in the remote configuration parameter package with the version of the current feeder topology data;

[0032] During version matching, the normal power supply side, backup power transfer side, pole-mounted circuit breaker node and adjacent switch relationship corresponding to the fault path number are checked item by item;

[0033] During the verification process, if any isolation action delay, interconnection closing allowable condition, or adjacent equipment interlocking condition references a node that does not belong to the same fault path number, the corresponding parameter will be marked as a topology reference anomaly.

[0034] The action timing check is only performed if no topology reference exception occurs.

[0035] Preferably, the action timing verification of the remote configuration parameter package includes:

[0036] Based on the fault path number, the corresponding protection action parameters, fault confirmation delay, isolation action delay, reclosing strategy, and adjacent equipment blocking conditions are invoked to construct the action sequence within the same fault path.

[0037] The action sequence is sorted according to the role priority, and after sorting, it is checked whether the action corresponding to the power supply side protection boundary is covered by the upstream blocking constraint, whether the action corresponding to the fault isolation boundary is earlier than the action corresponding to the interconnection transfer boundary, and whether the reclosing action and the isolation action are mutually exclusive.

[0038] A timing conflict flag is generated if any check result is not met.

[0039] Preferably, the transfer path verification of the remote configuration parameter package includes:

[0040] When there is no timing conflict marker, select the backup transfer edge adjacent to the set of sections to be isolated, and determine the enableable transfer path according to the connection closing allowable conditions;

[0041] Perform faulty section elimination processing on the available power transfer path to obtain candidate power restoration paths that do not include the set of sections to be isolated;

[0042] Verify whether all pole-mounted circuit breaker nodes on the candidate power restoration path meet the corresponding activation conditions and adjacent equipment interlocking conditions.

[0043] When any candidate power restoration path contains a blocked node or a faulty reachable edge, an abnormal power transfer path marker is generated.

[0044] Preferably, after the topology consistency check, the action timing check, and the transfer path check, the method further includes:

[0045] Based on the remote configuration parameter package that does not generate the topology reference exception, the timing conflict flag, and the transfer path exception flag, a parameter version that can be distributed is formed;

[0046] The version of the parameters that can be distributed is differentially encoded with the version of the current operating parameters of the corresponding pole-mounted circuit breaker to obtain a remote configuration incremental package that contains only the changed parameter items and their fault path numbers.

[0047] The topology role identifier, applicable feeder version, and activation conditions are retained in the remote configuration incremental package, and the unchanged neighbor device interlocking conditions are used as verification reference information.

[0048] Preferably, after sending the remote configuration incremental packet to the corresponding pole-mounted circuit breaker, the method further includes:

[0049] Receive the local adjacent switch status, local topology role identifier, and local operating parameter version returned by the pole-mounted circuit breaker;

[0050] The local adjacent switch status is matched with the activation conditions, the local topology role identifier is matched with the topology role identifier carried in the remote configuration incremental package, and the local running parameter version is matched with the verification reference information.

[0051] Write and enable the changed parameter item in the remote configuration incremental package when all three matches pass;

[0052] If any match fails, the original operating parameters are maintained, and the mismatch is associated with the corresponding fault path number and reported.

[0053] Compared with the prior art, the beneficial effects of the present invention are as follows:

[0054] 1. After adopting the above-mentioned technical invention, when the configuration terminal remotely generates the self-healing control parameters of the pole-mounted circuit breaker, it constructs a self-healing logic diagram based on feeder topology data, pole-mounted circuit breaker status data, adjacent switch relationships, main power supply path, and tie-off power transfer path, and identifies the topology role identifier of each pole-mounted circuit breaker in the diagram data. Protection action parameters, fault confirmation delay, isolation action delay, reclosing strategy, tie-off closing allowable conditions, and adjacent equipment blocking conditions no longer use independent templates, but are generated by a fault path constraint set jointly formed by the fault current direction, undervoltage section, adjacent equipment status, and topology role. Topology consistency verification is used to eliminate equipment nodes and line edges with incorrect parameter references; action timing verification is used to eliminate sequence conflicts between upstream protection, fault isolation, reclosing, and tie-off power transfer; and power transfer path verification is used to eliminate restoration paths containing fault sections or blocked nodes. Through the above constraints, the configuration terminal can detect parameters that are inconsistent with the feeder version, fault path number, or transfer boundary before the parameters are issued. This ensures that the remote configuration parameters correspond to the current feeder power supply path, fault isolation boundary, and interconnection transfer boundary, reducing the risk of over-level tripping, repeated isolation, incorrect transfer, and faulty closing caused by role misjudgment.

[0055] 2. The remote configuration parameter package carries the topology role identifier, applicable feeder version, parameter semantic summary, and activation conditions. This allows the field pole-mounted circuit breaker to compare the status of adjacent switches, the local topology role identifier, and the local operating parameter version upon receiving the package, preventing parameters from being directly activated even if the feeder configuration has changed. The distributed parameter version can be differentially encoded with the current operating parameter version to form a remote configuration incremental package. Only parameters related to the fault path number are changed, while the unchanged interlocking conditions of adjacent devices are retained as verification reference information, reducing version confusion caused by irrelevant parameters being repeatedly written. For configuration content that fails local matching, the field device maintains the original operating parameters and reports the difference items along with the fault path number, enabling the configuration end to pinpoint whether the issue is due to inconsistent topology roles, unmet activation conditions, or version reference mismatch. This process associates parameter writing, enabling, and exception receipts with the same fault path number, preventing the configuration end from mistakenly judging that parameters have adapted to the field operating status based solely on successful write receipts. Even when there is communication delay, topology model update lag, or field switch status has changed, the pole-mounted circuit breaker can still retain its original self-healing control logic, preventing inconsistent parameters from participating in fault isolation and interconnection transfer judgments, and providing a traceable data foundation for subsequent regeneration of parameter packages. Attached Figure Description

[0056] Figure 1 A flowchart of the overall method for remotely configuring parameters of the self-healing control logic of a pole-mounted circuit breaker;

[0057] Figure 2 Flowchart for constructing the self-healing logic diagram and identifying topological roles;

[0058] Figure 3 A flowchart is generated for the creation of fault path constraint sets and remote configuration parameter packages.

[0059] Figure 4 Flowchart for remote configuration parameter package verification, incremental distribution, and local activation;

[0060] Figure 5 This is a distribution map of candidate isolated nodes;

[0061] Figure 6 To constrain the hit count graph;

[0062] Figure 7 This is a distribution chart of actions. Detailed Implementation

[0063] refer to Figure 1In one embodiment, the remote configuration method for the self-healing control logic of pole-mounted circuit breakers is applied to the remote generation, verification, distribution, and activation process of self-healing control parameters for distribution feeders. The configuration terminal acquires feeder topology data, pole-mounted circuit breaker status data, adjacent switch relationship data, main power supply path data, and tie-and-transfer path data. The feeder topology data represents the electrical connection relationships between power supply points, main lines, branch lines, sectionalizing points, tie points, and load sections. The pole-mounted circuit breaker status data represents the open, closed, locked, protection activated, reclosing ready, and communication reachable status of each pole-mounted circuit breaker. The adjacent switch relationship data represents the status of adjacent poles within the same fault isolation link. The upstream and downstream relationships between circuit breakers are defined. The main power supply path data represents the power supply path from the power source to each load section under normal operating conditions. The tie-in power transfer path data represents the backup path that can be used to restore power to non-faulty sections after fault isolation. The configuration terminal converts the above data into a self-healing logic diagram with pole-mounted circuit breakers as nodes and electrical connection relationships as edges. In this self-healing logic diagram, each node includes at least the device identifier, operating status, set of adjacent nodes, feeder version, and fault path number. Each edge includes at least the connection direction, power supply attribute, whether it can be transferred, and mutual exclusion relationships. The configuration terminal determines the topology angle of each pole-mounted circuit breaker based on the self-healing logic diagram. Color-coded identifiers, specifically topology role identifiers, are used to distinguish the power supply side protection boundary, fault isolation boundary, branch line boundary, tie-forward boundary, or end load boundary of the pole-mounted circuit breaker under the current feeder operation mode. Subsequently, a fault path constraint set is generated based on the topology role identifier, fault current direction, undervoltage section, and the status of adjacent pole-mounted circuit breakers. This set limits the pole-mounted circuit breakers allowed to operate, upstream equipment that should be blocked, downstream boundaries that should be isolated, tie-forward paths that should be prohibited, and reclosing logic that should be mutually exclusive within the same fault path. The configuration terminal generates a set of protection action parameters, fault confirmation delay, isolation action delay, and reclosing parameters according to the fault path constraint set. The remote configuration parameter package includes the strategy, the connection closing permission condition, and the adjacent equipment interlocking condition. Before being sent out, the remote configuration parameter package is checked for topology consistency, action timing, and power transfer path. Only when the nodes, edges, fault path numbers, role identifiers, timing relationships, and power transfer paths referenced by the configuration parameters are consistent with the current self-healing logic diagram will the configuration terminal send the corresponding parameter package to the pole-mounted circuit breaker. In this embodiment, remote configuration does not write isolated parameters to a single device, but rather forms a closed processing chain of topology role identification, fault path constraint generation, and pre-send verification, thereby ensuring that the parameter generation basis matches the fault isolation boundary and power restoration boundary.

[0064] refer to Figure 2 Specifically, the configuration end uses a directed graph data structure to represent the feeder power supply relationship when constructing the self-healing logic diagram. Let the self-healing logic diagram be... ,in This represents the set of pole-mounted circuit breaker nodes. They represent the 1st, 2nd, ..., nth elements respectively. Indicates a pole-mounted circuit breaker Pointing pole circuit breaker Electrical connection edge, Indicates by point to The power supply connection edge is determined according to the power supply direction in the current main power supply path. If an edge belongs to the normal power supply path, it is recorded as a normal power supply edge; if an edge belongs to the tie-forward power supply path, it is recorded as a backup power supply edge. During data preprocessing, the configuration end marks the ring network opening points within the same feeder as mutually exclusive boundaries to prevent the normal power supply edge and the backup power supply edge from being activated simultaneously in the same fault path. Node status is determined by vector. It means that, among them Indicates pole-mounted circuit breaker The state of combination and separation is such that the combined position takes 1 and the separation position takes 0. The state indicates whether communication is reachable (1 for reachable, 0 for unreachable). A value of 1 indicates a locked state, and a value of 0 indicates an unlocked state. This indicates the protection is enabled; 1 indicates enabled, and 0 indicates disabled. The configuration terminal will indicate the reclosing preparation status and the availability of reclosing conditions (1 for 1, 0 for 0). Write the corresponding node, and write the edge attributes in each side. ,in This indicates whether an edge is in a connected state. This indicates the edge type, where the edge under normal power supply takes 1, and the edge under standby power supply takes 2. This indicates the mutual exclusion set number between the edge and other edges. In this embodiment, by uniformly writing the node state vector, edge attribute vector and mutual exclusion set number, the configuration terminal can simultaneously process the mutual exclusion relationships of device operating status, power supply direction and connection path in the same graph structure.

[0065]

[0066]

[0067] ;

[0068] Operators This indicates that the power supply direction is from the upstream node to the downstream node. For example, there is a circuit breaker on the power supply side pole of a feeder. Main section pole-mounted circuit breakers and branch line entrance post-mounted circuit breaker Under normal power supply conditions, the power supply is provided by point to Point to again Then the corresponding edge is and If the backup path corresponding to the tie switch is... point to Then the edge Marked as a backup feeder edge. See Table 1 for the self-healing logic graph field mapping table.

[0069] Table 1. Field Mapping Table for Self-Healing Logic Diagram

[0070] pole-mounted circuit breaker node Equipment identification, open / closed status, interlocked status, protection activation status, reclosing preparation status As the carrier of protective actions, isolation actions, reclosing, and interlocking relationships. Main power supply path Directed edge Power supply direction, normal power supply side markings, and path number As the basis for calculating upstream paths, downstream paths, and faulty reachable edges. Contact and transfer path Directed edge Backup supply edge identifier, mutually exclusive set number, transferable supply identifier As a basis for verifying the conditions for connection closing and the power transfer path. Adjacent switch relationship Node adjacency list Upstream neighbors, downstream neighbors, connecting neighbors As a basis for verifying the interlocking conditions and action sequence of adjacent equipment Feeder version Image version field Image model version, operating mode version, data generation time As a basis for verifying the applicability of remote configuration parameter packages

[0071] Table 1 illustrates the field carrying methods of different original data in the self-healing logic diagram. Before generating parameters, the configuration end first completes data normalization processing according to this mapping relationship. If the same pole-mounted circuit breaker has a device number in the ledger but no adjacent edge in the topology connection relationship, the corresponding node is marked as an un-mapped node and excluded from the current configuration scope. If the same interconnection transfer path does not establish a mutually exclusive set number with the normal power supply path, the spare transfer edge is marked as an edge to be checked and does not directly participate in parameter generation. If the same adjacent switch relationship is opposite to the power supply direction in the diagram, the direction of the main power supply path is used as the power supply direction and the adjacent relationship is used as the adjacency supplementary information. This processing avoids the same device having different reference bases when generating parameters due to different sources of ledger, diagram model and operating status. The advantage of this embodiment is that it converts the scattered data required for remote configuration into unified diagram data, so that subsequent role identification and fault path constraint generation have a definite data foundation.

[0072] In one embodiment, when the configuration terminal determines the topology role identifier based on the self-healing logic diagram, it calculates the upstream path from each pole-mounted circuit breaker to the power source and the downstream path to the load section along the normal power supply side, and calculates the tie-forward paths that each pole-mounted circuit breaker can participate in along the standby transfer side. The upstream path is used to determine whether the pole-mounted circuit breaker is within the power supply side protection range or the upper-level protection boundary, the downstream path is used to determine whether there is a load section to be isolated, branch line, or end load downstream of the pole-mounted circuit breaker, and the tie-forward path is used to determine whether the pole-mounted circuit breaker may participate in the restoration of non-faulty sections after fault isolation. The configuration terminal calculates a role determination vector for each pole-mounted circuit breaker. ,in Indicates the power supply side protection boundary marking. Indicates the fault isolation boundary marker. Indicates the boundary marker of a branch line. Indicates the boundary marker for liaison and transfer. This indicates the end-load boundary marker, with each marker taking a value of 0 or 1. If the pole-mounted circuit breaker is located downstream of the power source and its upstream path length is less than that of other operable nodes within the same fault path, then... If the pole-mounted circuit breaker is located at the intersection of the fault reachable edge and the undervoltage zone boundary, then... If the pole-mounted circuit breaker is set to 1, then... If the pole-mounted circuit breaker is located at the end of the standby transfer side and its interconnection transfer path does not include the fault section, then... If the value is set to 1, and there are no other pole-mounted circuit breaker nodes downstream of the pole-mounted circuit breaker and the connected load section is not specified, then... When set to 1, if a circuit breaker on the same pole has multiple role identifiers, the configuration terminal generates role priorities in the order of fault isolation boundary, tie transfer boundary, branch line boundary, power supply side protection boundary, and end load boundary. The highest priority role is used as the main role generated by the parameters, and the remaining roles are retained in the node field as verification roles.

[0073] ;

[0074] A value of 1 indicates that the corresponding role condition is met, and a value of 0 indicates that the corresponding role condition is not met, such as a pole-mounted circuit breaker. Located at the main trunk section and downstream of the branch line, the fault current direction passes through And cause its downstream section to lose pressure, at the same time If it is not at the standby transfer end point, then it can be obtained The configuration end prioritizes fault isolation boundaries over branch boundaries. The primary role is determined as the fault isolation boundary, and the branch boundary is used as the verification role.

[0075] Preferably, the role priority is not a manually set fixed equipment category, but is jointly determined by the path relationship and fault path constraints in the current self-healing logic diagram. The configuration terminal uses the shortest upstream path, downstream load coverage, and backup power transfer connection relationship in the normal power supply side as role determination inputs. If the same equipment changes from a main section to a tie power transfer boundary under different operating modes, its topology role identifier is regenerated according to the feeder version. If the same equipment belongs to the branch boundary in the branch fault scenario and the fault isolation boundary in the main fault scenario, the configuration terminal saves the role identifier under different fault path numbers. After the role identifier is bound to the fault path number, it is written into the remote configuration parameter package. When the field pole-mounted circuit breaker receives parameters, it can match them according to the local topology role identifier, avoiding the use of old role parameters for the same equipment due to changes in line operating mode. In this embodiment, the generation of the topology role identifier depends on the combination judgment of the upstream path, downstream path, and tie power transfer path, which enables the subsequent protection action parameters, isolation action delay, blocking conditions, and power transfer conditions to be generated around the actual role of the equipment in the current electrical path.

[0076] refer to Figure 3 In one embodiment, the configuration terminal generates a fault path constraint set based on topology role identifiers, fault current direction, undervoltage sections, and adjacent pole-mounted circuit breaker states. The fault current direction is used to determine the fault reachable edge set, the undervoltage section is used to determine the isolation section set, and the adjacent pole-mounted circuit breaker states are used to determine the operable node set. The configuration terminal marks the fault current direction as the edge direction from the power source to the fault section. If a normally powered edge is located on the reachable path of the fault current direction and its upstream node is in the closed position, then the edge is included in the fault reachable edge set. If a load section is in an undervoltage state after a fault occurs and there is an operable pole-mounted circuit breaker upstream, then the load section is included in the isolation section set. If a pole-mounted circuit breaker is communicatively reachable, not blocked, and in both open and closed states and can perform actions, then the node is included in the operable node set. Subsequently, the configuration terminal combines the fault reachable edge set and the isolation section set... The set of operable nodes and their roles are cross-constrained to generate upstream blocking constraints, downstream isolation constraints, branch priority isolation constraints, tie-line transfer prohibition constraints, and reclosing mutual exclusion constraints. The upstream blocking constraint is used to limit the power supply side protection boundary from being the first-action isolation device when the downstream of the fault isolation boundary has the conditions to operate. The downstream isolation constraint is used to limit the boundary nodes of the section to be isolated from participating in the isolation action. The branch priority isolation constraint is used to limit the branch boundary from taking precedence over the main section boundary when the branch is faulty. The tie-line transfer prohibition constraint is used to limit the backup transfer path containing the fault reachable edge or the section to be isolated from participating in the closing. The reclosing mutual exclusion constraint is used to limit the reclosing strategy from being activated simultaneously with the isolation action when the fault isolation is not completed. The advantage of this embodiment is that it combines the fault current, undervoltage range, equipment operable status, and topology role into constraint objects, so that the remote configuration parameters are no longer determined solely by the equipment type.

[0077] ;

[0078] in, Indicates the first The set of fault path constraints corresponding to each fault path number. Represents the set of upstream locking constraints. Represents the set of downstream isolation constraints. This indicates the set of branch-priority isolation constraints. This indicates that the communication and transfer of information prohibits and restricts the collection of information. This represents the set of reclosing mutual exclusion constraints, such as fault path numbers. For a corresponding branch fault path, the fault current passes through the main pole-mounted circuit breaker. and branch line entrance post-mounted circuit breaker The depressurization section is located in Downstream, and If it can be acted upon, then Included by Downstream isolation constraints are enforced. Includes Upstream locking constraints, Includes and The backup power supply side connected to the downstream fault section is prohibited from being restricted.

[0079] refer to Figure 6 This diagram is used for specific explanations in engineering verification reports. The horizontal axis represents the object number, and the vertical axis represents the number of hits. The data is generated from the constraint set and associated with constraint hit records. The current data covers feeder version FV-33-18, 33 pole-mounted circuit breaker nodes, 16 fault paths, and 80 chart records. There are 78 records with values ​​greater than zero, with a maximum value of 30.000. Higher values ​​indicate that the object plays a stronger constraint, activation, or verification role in the current version; lower values ​​typically indicate that conditions were not hit, paths are unavailable, or references have not yet been formed. When reading this diagram, a comprehensive judgment should be made based on the fault path number, equipment status, communication and transfer relationships, and receipt results, rather than solely on a single pole or point. If multiple consecutive records have low values, priority should be given to checking the feeder diagram version, adjacent switch status, interlocked nodes, and sections to be isolated. This explanation also records the data source, version number, and record size, facilitating continued traceability of report definitions after exporting data files or images. The horizontal axis of the constraint hit count chart represents the object number, and the vertical axis represents the hit count. The data comes from constraint hit records, and the calculation method is generated from the constraint set. This export contains 80 detailed records, of which 78 are valid high-value records, with an average value of 5.525 and a maximum value of 30.000. The peak object is the upstream blocking of path 015. When interpreting engineering data, first observe whether high-value objects are concentrated in the same fault path, the same feeder section, or the same type of role boundary. Then, cross-confirm with equipment communication status, blocking status, protection activation status, supply path availability, and local feedback results. If there are continuous low values ​​or abnormal discrete points in the graph, it indicates that the relevant paths, nodes, or parameter packages still need to be reviewed, and it is not advisable to directly issue commands based on a single indicator.

[0080] Furthermore, the set of fault path constraints can be generated using Boolean constraint expressions, and the configuration terminal assigns a number to each fault path. Establish edge reachability markers Section depressurization sign Node actionable flags and role priority ,in Representing an edge Belongs to the The reachable edges of each fault path, Indicates load section Belongs to the The underpressure section of each fault path, Represents a node In the Each fault path has the conditions for action. Represents a node In the In each fault path, the role priority value is lower, and the higher the priority, the configuration terminal selects nodes that simultaneously meet the requirements of fault reachability, connection to the undervoltage section, and having the conditions for action as candidate isolation nodes when generating isolation constraints. The action sequence of the candidate isolation nodes is determined according to the role priority. If the candidate isolation node is a branch boundary and its upstream node is a power supply side protection boundary, a blocking constraint is generated for the upstream node. If there is still a backup power transfer edge downstream of the candidate isolation node leading to the undervoltage section, a prohibition constraint is generated for the corresponding backup power transfer edge. Through this Boolean constraint generation method, the configuration terminal can transform data from different sources into verifiable logical conditions. In this embodiment, the generation process of the fault path constraint set has clear node, edge, and section reference relationships, which facilitates binding and verification according to the fault path number in the subsequent parameter package.

[0081] ;

[0082] in, Represents a node Is it the first Candidate isolation nodes for each fault path Represents a node Does it meet the conditions for action? Indicates entering the node upstream edge Is it a fault reachable edge? Represents a node The set of load segments covered downstream, Indicates load section Whether there is a loss of pressure, the multiplication sign indicates that the value is 1 if all three conditions are met simultaneously. The operation means that if any one of the multiple upstream edges or multiple downstream load segments meets the condition, the result is 1. For example, When in a closed position and able to move its upstream side When it belongs to the fault reachable edge Its downstream load section When pressure is lost ,but ,express It was selected as a candidate isolation node for fault path 3.

[0083] refer to Figure 5This diagram is used for specific explanations in engineering verification reports. The horizontal axis represents the object number, and the vertical axis represents the candidate hit value. The data is calculated and generated from candidate isolation nodes and associated with the pole-mounted circuit breaker ledger, electrical connection edge, load section, and fault path. The current data covers feeder version FV-33-18, 33 pole-mounted circuit breaker nodes, 16 fault paths, and 33 chart records. There are 4 records with values ​​greater than zero in the diagram, with a maximum value of 1.000. Higher values ​​indicate that the object plays a stronger constraint, activation, or verification role in the current version, while lower values ​​usually indicate that the condition was not hit, the path is unavailable, or the reference has not yet been formed. When reading, a comprehensive judgment should be made based on the fault path number, equipment status, communication and transfer relationships, and receipt results, rather than deciding to issue based on a single pole or point. If multiple consecutive records are at low values, the feeder diagram version, adjacent switch status, interlocked nodes, and sections to be isolated should be checked first. This explanation also records the data source, version number, and record size, which facilitates the on-duty personnel to continue tracing the report scope after exporting data files or images. The horizontal axis of the candidate isolation node distribution chart represents the object number, and the vertical axis represents the candidate hit value. The data comes from the pole-mounted circuit breaker ledger, electrical connection edges, load sections, and fault paths. The calculation method is based on candidate isolation nodes. This export contains 33 detailed records, including 4 valid high-value records with an average value of 0.121 and a maximum value of 1.000. The peak object is switch 015. When interpreting engineering data, first observe whether high-value objects are concentrated in the same fault path, the same feeder section, or the same type of role boundary. Then, cross-confirm with equipment communication status, interlocking status, protection activation status, supply path availability, and local feedback results. If there are continuous low values ​​or abnormal discrete points in the chart, it indicates that the relevant paths, nodes, or parameter packages still need to be reviewed. It is not advisable to directly issue commands based on a single indicator.

[0084] In one embodiment, when the configuration terminal generates a remote configuration parameter package according to the fault path constraint set, it converts upstream blocking constraints into adjacent equipment blocking conditions, downstream isolation constraints and branch priority isolation constraints into isolation action delays and protection action parameters, and tie-line power transfer prohibition constraints into tie-line closing allow conditions. Reclosing mutual exclusion constraints are then converted into reclosing strategies. The converted parameters are bound according to the same fault path number. Protection action parameters may include fault type identification conditions, protection start allow conditions, and action output allow conditions. Fault confirmation delays can be jointly determined by the continuous state of the fault reachable edge, the continuous state of the undervoltage section, and the stability of adjacent node states. Isolation action delays can be generated based on role priority and upstream / downstream blocking relationships. Reclosing strategies may include reclosing enable conditions, closing... The locking conditions and mutual exclusion conditions before isolation completion, and the tie-closing permission conditions can include the availability of the backup power supply side, the candidate power restoration path not including the section to be isolated, the adjacent nodes not being locked, and the corresponding feeder version being consistent. The adjacent equipment locking conditions can include upstream node locking, peer node mutual exclusion locking, and tie boundary locking. The parameter package also includes the topology role identifier, applicable feeder version, parameter semantic summary, and activation conditions. The parameter semantic summary uses machine-resolvable fields to indicate which fault path constraint each parameter originates from. The activation conditions indicate the topology role, adjacency status, and version conditions that the local state of the pole-mounted circuit breaker must meet. In this embodiment, the parameter generation process is not a simple conversion of constraint names, but rather maps each type of constraint to parameter items that can be executed by the field controller while retaining the fault path source. The fault path constraint and remote configuration parameter mapping table is shown in Table 2.

[0085] Table 2 Mapping Table of Fault Path Constraints and Remote Configuration Parameters

[0086] Upstream locking constraints Adjacent equipment interlocking conditions Upstream node identifier, fault path number, and interlock source role Local adjacent switch status, local operating parameter version Downstream isolation constraints Isolation action delay, protection action parameters Downstream boundary node, section to be isolated, fault path number Local topology role identifier and activation conditions Branch priority isolation constraints Branch boundary action conditions, trunk delay conditions Branch boundary markers and role priorities Local adjacent switch relationships and fault path numbers Contacting and transferring information is prohibited and restricted. Interconnection closing conditions Backup power supply edge, mutual exclusion set number, candidate power restoration path Local adjacent switch status, feeder version Reclosing mutual exclusion constraint Reclosing strategy Reclosing status, isolation completion flag, mutually exclusive fault paths Local reclosing preparation status and lockout status

[0087] Table 2 illustrates the conversion relationship from fault path constraints to remote configuration parameters. During the conversion, the configuration terminal does not allow the same parameter item to reference different fault path numbers simultaneously. If a pole-mounted circuit breaker belongs to multiple fault paths, parameter groups are generated separately for different fault paths in the parameter package. The enable condition distinguishes which group of parameters participates in control when the field status is met. If a tie-closing enable condition references a standby transfer side belonging to a mutually exclusive set number... If the parameter package also contains the normal power supply edge corresponding to the mutual exclusion set number, it will ensure that the subsequent transfer path verification confirms that a closed loop or faulty closing will not be formed. If a certain reclosing strategy is generated by reclosing mutual exclusion constraints, the parameter package contains its mutual exclusion isolation action identifier and fault path number. The field controller must not enable the reclosing strategy when the isolation action is not completed. In this embodiment, the parameter package maintains the reference continuity between constraint source, parameter execution and local enabling through binding fields and verification fields. After implementation, it can reduce the misuse of configuration caused by loss of parameter semantics.

[0088] Preferably, the protection action parameters, fault confirmation delay, and isolation action delay can be jointly generated by role priority and fault confirmation status, and the configuration terminal is for each candidate isolation node. Calculate action ranking value The smaller the action ranking value, the higher the ranking value. The closer a fault path is to the isolation boundary, the more important the calculation uses role priority, upstream distance, and fault confirmation status as inputs. Role priority reflects the sequential relationship between the fault isolation boundary and the power supply protection boundary. Upstream distance distinguishes different electrical locations under the same role. Fault confirmation status prevents unconfirmed fault devices from participating in isolation actions. The configuration terminal generates the relative order of isolation action delays based on the action sorting value and writes the action conditions of the upstream protection boundary into the blocking parameters. This allows the downstream isolation node to generate an action exit first when the fault confirmation and actionable conditions are met. If the downstream isolation node is inoperable or unreachable, the upstream node enters the backup isolation path according to the blocking release condition. The protection action parameters and isolation action delays are written together under the same fault path number to avoid the protection action value and action delay belonging to different logical sources. In this embodiment, the parameter calculation uses an interpretable sorting quantity and is bound to the topology role, which facilitates the field controller to perform isolation and blocking judgments according to the same logic.

[0089] ;

[0090] in, Represents a node In the Action ordering values ​​in each fault path This represents the priority value for a role. Fault isolation boundary can be set to 1, tie-line / supply boundary to 2, branch line boundary to 3, power supply side protection boundary to 4, and end-load boundary to 5. Represents a node The upstream distance to the fault boundary, calculated based on the number of edges traversed. Represents a node Is it a candidate isolation node? and Indicates the ranking weight and maintains a fixed meaning within the same configuration task, for example... For fault isolation boundary and Distance from fault boundary Candidate isolation status ,when and hour Upstream pole-mounted circuit breaker For power supply side protection boundary and ,distance Candidate isolation status ,but The configuration end will then... The order of isolation actions is as follows Before.

[0091] refer to Figure 7 This diagram is used for specific explanations in engineering verification reports. The horizontal axis represents the object number, and the vertical axis represents the sorting value. The data is generated by action sorting calculations and associated with role identification results and fault paths. The current data covers feeder version FV-33-18, 33 pole-mounted circuit breaker nodes, 16 fault paths, and 33 chart records. There are 33 records with values ​​greater than zero, with a maximum value of 112.400. Higher values ​​indicate that the object plays a stronger constraint, activation, or verification role in the current version; lower values ​​typically indicate that conditions were not met, paths are unavailable, or references have not yet been formed. When reading this diagram, a comprehensive judgment should be made based on the fault path number, equipment status, communication and transfer relationships, and receipt results. It is not advisable to decide on issuance based solely on a single pole or point. If multiple consecutive records have low values, priority should be given to checking the feeder diagram version, adjacent switch status, interlocked nodes, and sections to be isolated. This explanation also records the data source, version number, and record size, facilitating continued traceability of report definitions after exporting data files or images. The horizontal axis of the action ranking distribution chart represents the object number, and the vertical axis represents the ranking value. The data comes from role recognition results and fault paths, and the calculation method is action ranking calculation. This export contains 33 detailed records, of which 33 are valid high-value records, with an average value of 48.479 and a maximum value of 112.400. The peak object is switch 031. When interpreting the data, first observe whether high-value objects are concentrated in the same fault path, the same feeder section, or the same type of role boundary. Then, cross-confirm with equipment communication status, interlocking status, protection activation status, supply path availability, and local feedback results. If there are continuous low values ​​or abnormal discrete points in the chart, it indicates that the relevant paths, nodes, or parameter packages still need to be reviewed, and it is not advisable to directly issue commands based on a single indicator.

[0092] refer to Figure 4In one embodiment, the configuration terminal performs a topology consistency check on the remote configuration parameter package. The check process matches the applicable feeder version carried in the parameter package with the version of the current feeder topology data. After version matching, the normal power supply side, standby transfer side, pole-mounted circuit breaker node, and adjacent switch relationship corresponding to the fault path number are checked item by item. If the isolation action delay reference node in the parameter package is... Then check if the node exists in the node set of the current self-healing logic graph. If the connection closing permission condition in the parameter package references the standby power supply side Then check if the edge exists in the current edge set. Furthermore, if the edge type is a spare supply edge, and the adjacent device locking condition in the parameter package references an adjacent node... Then check and Whether it belongs to the adjacent range corresponding to the same fault path number, if any isolation action delay, connection closing allowable condition or adjacent equipment blocking condition references a node that does not belong to the same fault path number, the corresponding parameter will be marked as topology reference abnormal. Only when no topology reference abnormality occurs will the configuration end enter the action sequence verification. In this embodiment, the topology consistency verification can eliminate parameter reference errors caused by changes in the map version, changes in equipment ledger or changes in the connection path status before the parameters are issued, so that the subsequent action sequence verification is based on the correct node and edge references.

[0093] ;

[0094] in, Indicates the first Topology consistency verification results for each fault path. This indicates that the remote configuration parameter package is related to the first... The set of all referenced objects bound to each fault path number includes nodes, normal power supply sides, backup power transfer sides, adjacent switch relationships, and mutual exclusion set numbers. Represents a reference object Does it exist in the self-healing logic diagram? And it must match the corresponding fault path number. If it exists and matches, the value is 1; otherwise, the value is 0. The product operation indicates that all referenced objects are consistent. If any referenced object is inconsistent, the value is 0. For example, in the parameter package, the reference to fault path 3 is 0. , , And the mutually exclusive set numbered 7, if , Both the mutually exclusive set number 7 and the fault path 3 exist, while It has been removed in the current feeder version. ,thereby .

[0095] Furthermore, the action sequence verification calls the corresponding protection action parameters, fault confirmation delay, isolation action delay, reclosing strategy, and adjacent equipment interlocking conditions based on the fault path number. The configuration terminal constructs the action sequence within the same fault path according to the action sorting value and role priority. The action sequence includes events such as protection start-up, fault confirmation, downstream isolation, upstream interlocking, reclosing judgment, and interconnection transfer judgment. After sorting the action sequence according to role priority, the configuration terminal checks whether the corresponding action of the power supply side protection boundary is covered by the upstream interlocking constraint. If the downstream fault isolation boundary is in an operable state but the power supply side protection boundary does not have a corresponding interlocking condition, the verification will be performed. If a timing conflict flag is generated, it checks whether the action corresponding to the fault isolation boundary is earlier than the action corresponding to the tie-and-transfer boundary. If the tie-and-close condition is met before the isolation completion flag, a timing conflict flag is generated. It then checks whether the reclosing action and the isolation action are mutually exclusive. If the reclosing policy allows execution when the isolation action is not completed within the same fault path, a timing conflict flag is generated. In this embodiment, the action timing verification is not a simple comparison of delay magnitude, but rather a verification that combines role priority, constraint source, and mutual exclusion relationship between action events to avoid logical overlap between protection actions, isolation actions, reclosing, and tie-and-transfer.

[0096] In a preferred embodiment, the action sequence verification uses an event dependency matrix to express the sequence of actions, and the configuration terminal records action events within the same fault path as follows: If the action event Must occur earlier than the action event Then write it into the dependency matrix. If there is no mandatory order between the two, then write 0, and the configuration end will then generate the actual action time sequence based on the parameter package. Verification was performed, and all requirements were met. All events must satisfy If it exists but If a timing conflict flag is generated, for example, the downstream isolation completion event must be earlier than the tie closing judgment event. If the parameter package makes the activation time of the tie closing judgment event earlier than the isolation completion event, then the fault path cannot enter the transfer path verification. In this embodiment, the sequence relationship of the self-healing control logic is transformed into a computable object through the event dependency matrix, which can cover the action sequence verification when multiple pole-mounted circuit breakers work together.

[0097] ;

[0098] in, Indicates the first Action timing verification results for each fault path Indicates the number of action events. Indicates an event Must it be earlier than the event? , and Representing events respectively and events The expected time of occurrence, Indicates when The value is 1 if the condition is met, otherwise it is 0. The product operation indicates that the condition is met when all dependencies are satisfied. For example, there is a downstream isolation completion event within the same fault path. and connection closing judgment event ,like , , If the event is 1 for the verification item, then the event is 1 for the verification item. , If the event is zero, then the check item is 0.

[0099] In one embodiment, the transfer path verification is performed when there is no timing conflict flag. The configuration terminal selects a backup transfer edge adjacent to the set of sections to be isolated and determines the enableable transfer path according to the tie closing allowable conditions. Then, the enableable transfer path is processed to eliminate faulty sections, resulting in candidate power restoration paths that do not contain the set of sections to be isolated. The faulty section elimination process includes deleting edges that coincide with faulty reachable edges from the candidate paths, deleting nodes whose downstream covers the section to be isolated, and deleting nodes marked as prohibited from participating in transfer by upstream blocking constraints. The configuration terminal verifies whether all pole-mounted circuit breaker nodes on the candidate power restoration path meet the corresponding start-up requirements. Using conditions and adjacent equipment interlocking conditions, when any candidate power restoration path contains a blocked node or a fault reachable edge, an abnormal transfer path mark is generated. If there is at least one candidate power restoration path that does not contain the set of sections to be isolated, does not contain a fault reachable edge, and all nodes meet the activation conditions, then the connection closing allowable condition can be retained in the remote configuration parameter package. If there is no candidate power restoration path that meets the conditions, then the corresponding connection closing allowable condition is marked as a parameter that cannot be issued. In this embodiment, by performing troubleshooting on the backup transfer path before issuing, the connection transfer parameters are avoided from being generated solely based on the undervoltage conditions while ignoring whether the fault isolation boundary has been established.

[0100] ;

[0101] in, Indicates the first Verification results of the transfer path for each faulty path. Indicates the first The set of candidate power restoration paths corresponding to each fault path. This indicates one of the candidate power restoration paths. Representing an edge Whether an edge is a reachable edge from a fault is determined by a value of 1 if it is, and 0 if it is not. Indicates candidate power restoration paths The set of covered load segments, Indicates load section Does it belong to the area to be quarantined? Represents a node Whether a path is blocked or not, a product result of 1 indicates that the candidate power restoration path does not contain fault reachable edges, does not cover the section to be isolated, and does not contain blocked nodes. The operation indicates that as long as there is a candidate power restoration path that meets the conditions, the power transfer path can be verified. For example, candidate power restoration path Includes edges and If neither of them is a fault-reachable edge and neither of their covered segments is a segment to be isolated, and neither of their path nodes is locked, then... The product of the two paths is 1, if the other candidate path If it contains a fault-reachable edge, then The product of these two is 0, and ultimately... .

[0102] Furthermore, after completing topology consistency verification, action timing verification, and transfer path verification, the configuration terminal generates a deployable parameter version based on remote configuration parameter packages that do not generate topology reference anomalies, timing conflict flags, or transfer path anomaly flags. If a fault path number fails any verification, the configuration terminal retains the original operating parameter version under that fault path number and generates an anomaly reference record. The parameter items that have passed verification are differentially encoded with the current operating parameter version of the corresponding pole-mounted circuit breaker to obtain a remote configuration incremental package containing only the changed parameter items and their fault path numbers. The differential encoding process compares protection action parameters, fault confirmation delay, isolation action delay, and overlap item by item. If any of the following parameters—parameter value, bound fault path number, topology role identifier, or activation condition—changes in the gate control strategy, interconnection closing permission conditions, and adjacent device interlocking conditions, that parameter item is written into the incremental package. If the parameter value remains unchanged but is referenced by other changed parameters as a verification reference for adjacent device interlocking conditions, its summary and version reference are retained in the incremental package without writing the executable parameter value. The remote configuration incremental package also retains the topology role identifier, applicable feeder version, and activation conditions, enabling local matching of the pole-mounted circuit breaker before writing. In this embodiment, differential encoding ensures that the configuration terminal only issues parameters related to the current fault path constraint change, while maintaining the integrity of the interlocking condition reference chain. See Table 3 for the remote configuration incremental package field table.

[0103] Table 3. Fields of Remote Configuration Incremental Package

[0104] Basic identifier field Equipment identification, fault path number, parameter version number Comparison results of the parameter version that can be sent and the current running parameter version Used to locate the device to which the parameters to be written belong and the fault path. Change parameter fields Protection action parameters, isolation action delay, reclosing strategy, and communication closing permission conditions. Parameters that change after differential encoding After a successful local match, the data is written to the runtime parameter area. Validate referenced fields Unchanged adjacent equipment interlocking conditions summary, referenced version The locking relationship on which the parameters are changed Used to verify the version of adjacent parameters and the continuity of latching references. Applicability field Topology role identifier, applicable feeder version, and activation conditions Self-healing logic diagram and fault path constraint set Local matching is used after issuance and before activation. Receipt Field Mismatched items, abnormal fault path numbers, local running parameter versions Local reception and matching results Used for tracking reasons why configuration is not enabled.

[0105] Table 3 illustrates the composition of the remote configuration incremental package. After the configuration terminal generates the incremental package, it does not delete the parameter source information. Instead, it binds each changed parameter item with the corresponding fault path number. If the tie closing allowable condition changes and references a certain adjacent device's blocking condition, even if the blocking condition itself has not changed, the blocking condition summary will be sent as a verification reference field. The field pole-mounted circuit breaker determines whether the local blocking condition is consistent with the incremental package by using the summary and referenced version. If they are inconsistent, the corresponding tie closing allowable condition will not be enabled. If the protection action parameter changes but the topology role identifier has not changed, the field still needs to verify the applicable feeder version and enabling condition before writing it into the operating parameter area. In this embodiment, the incremental package reduces the repeated sending of irrelevant parameters and retains the dependency relationship between parameters, avoiding the inability to determine whether adjacent parameters match when only changing values ​​are sent.

[0106] In one embodiment, after the configuration terminal sends a remote configuration incremental package to the corresponding pole-mounted circuit breaker, the field pole-mounted circuit breaker returns the local adjacent switch status, local topology role identifier, and local operating parameter version. The local adjacent switch status includes the open / closed position and interlocking status of adjacent switches that have upstream, downstream, or interconnection relationships with this device. The local topology role identifier is derived from the previously configured role saved by the field device or the role parsed from the local feeder adjacency table. The local operating parameter version includes the current operating parameter version number, the interlocking condition reference version, and the fault path number. The configuration terminal or the field pole-mounted circuit breaker matches the local adjacent switch status with the activation conditions carried in the remote configuration incremental package, and matches the local topology role identifier with... The incremental package carries a topology role identifier for matching, and the local operating parameter version is matched with the verification reference information. If all three matches pass, the changed parameter item in the incremental package is written and enabled. If any match fails, the original operating parameters are maintained, and the mismatch is associated with the corresponding fault path number and reported. If the mismatch is that the local adjacent switch status is inconsistent with the enabling condition, the switch status difference is reported. If the mismatch is that the local topology role identifier is inconsistent, the role difference is reported. If the mismatch is that the local operating parameter version is inconsistent with the verification reference information, the version difference is reported. In this embodiment, successful delivery is not the same as successful activation. Parameter writing must be matched with the local status, role, and version.

[0107] ;

[0108] in, This indicates the local enabling result of the remote configuration incremental package. This indicates the matching result between the status of adjacent switches and the activation conditions. A match is represented by 1, and a non-match by 0. This indicates the matching result between the local topology role identifier and the topology role identifier carried in the incremental packet; a match is represented by 1, and a non-match by 0. This indicates the matching result between the local operating parameter version and the verification reference information. A match is returned as 1, and a non-match as 0. The multiplication sign indicates that activation is only allowed when all three conditions are met simultaneously. For example, if a pole-mounted circuit breaker receives an incremental packet from fault path 3, and the status of its local adjacent switches meets the activation conditions, then... If the local topology role identifier is consistent with the incremental package, then... However, if the local latch condition reference version is lower than the validated reference information, then... ,at this time The original operating parameters were maintained on-site, and the version differences of fault path 3 were reported.

[0109] Furthermore, local activation determination can also be completed independently at the pole-mounted circuit breaker side. The configuration terminal writes the activation condition expression into the remote configuration incremental package. The activation condition expression includes adjacent switch status conditions, topology role conditions, and version reference conditions. After receiving the incremental package, the pole-mounted circuit breaker first writes it into the pending activation area without overwriting the operating parameter area. The parameters in the pending activation area are transferred to the operating parameter area only after passing the local activation determination. If the equipment is in the process of protection start-up, reclosing execution, isolation action execution, or communication instability, the local activation determination is temporarily suspended. After the adjacent switch status stabilizes, it is re-matched. If continuous matching still fails, the pending activation area retains the incremental package and reports the mismatch item. The configuration terminal locates the corresponding topology role, activation condition, or version reference difference according to the fault path number, and regenerates the parameter package or retains the original parameters. The advantage of this embodiment is that it prevents the field equipment from activating configuration content that is inconsistent with the current electrical conditions when the operating status is not met, thus avoiding interference with the ongoing self-healing control action during the remote configuration process.

[0110] In a preferred embodiment, when the configuration terminal generates parameter packages in parallel for multiple fault path numbers, multiple sets of parameters that may exist for the same pole-mounted circuit breaker are stored in isolation using fault path numbers. The field pole-mounted circuit breaker selects the parameter group corresponding to the fault path number based on the current protection start direction, undervoltage section, and adjacent switch status. If the same fault event simultaneously meets the triggering conditions of two fault path numbers, the field controller selects the fault path number with higher priority according to the role priority and activation conditions in the parameter package. If the priorities are the same, it enters the blocking and holding state and reports the conflicting fault path number. The configuration terminal corrects the fault path constraint set based on the conflict record during the next parameter generation to avoid cross-activation of the same device in different fault path parameter groups. In this embodiment, multiple fault path parameters are managed together through number isolation, role priority, and activation conditions, which is suitable for pole-mounted circuit breaker configuration at the junction of main lines and branch lines, tie-to-supply boundaries, and multi-section lines.

[0111] In one embodiment, when the configuration terminal generates the parameter semantic summary, it writes the source constraint, bound fault path number, corresponding topology role identifier, and verification status of each parameter item into the summary field. The summary field does not participate in the field control action output, but is used for reference verification before local activation and configuration terminal traceability. If the protection action parameter comes from the downstream isolation constraint, the summary writes the corresponding set of sections to be isolated and the candidate isolation node identifier. If the adjacent equipment blocking condition comes from the upstream blocking constraint, the summary writes the blocked upstream node and the downstream node that triggered the blocking. If the tie closing permission condition comes from the transfer path verification, the summary writes the candidate power restoration path and the set of excluded sections to be isolated. The field pole-mounted circuit breaker returns the summary matching result in the receipt. The configuration terminal can use this to determine whether the mismatch item corresponds to a topology reference, timing relationship, or transfer path, avoiding manual troubleshooting based solely on configuration failure or activation failure. In this embodiment, the parameter semantic summary serves as a bridging field between configuration data and verification data, enhancing the traceability of the remote configuration process.

[0112] In a preferred embodiment, when there is a partial update to the feeder topology data, the configuration terminal does not regenerate all feeder parameters. Instead, it identifies the affected node set and edge set and extends them along the self-healing logic graph to the adjacent fault path number, forming a local recalculation range. If the newly added tie-off power transfer edge only affects the backup power transfer path and not the normal power supply edge, the configuration terminal only recalculates the tie-off closing allowable conditions and power transfer path verification results, and retains the original version references of the protection action parameters and isolation action delay. If the main power supply path changes, resulting in a change in the power supply direction, the configuration terminal recalculates the upstream path, downstream path, topology role identifier, fault path constraint set, and all associated parameters. The parameters after local recalculation still need to undergo topology consistency verification, action timing verification, and power transfer path verification, and are distributed in incremental packets. This embodiment reduces irrelevant parameter version changes by identifying the affected range, so that the pole-mounted circuit breaker can still maintain the continuity of unaffected fault path parameters when some diagrams change.

[0113] Furthermore, the configuration side uses the set of affected paths when performing local recalculation. This represents the set of fault path numbers for which parameters need to be regenerated. If the topology change object is an edge... Then it will contain The normal power supply path, with Alternate feeder paths for mutex objects and with or Adjacent fault path numbers are included If the topology change object is Then it will be with Fault path numbers for candidate isolated nodes, locked nodes, or connection boundary nodes are included. Not included The parameter group only updates the applicable feeder version reference without rewriting the execution parameter value. If the applicable feeder version changes and causes the local version of the field equipment to be incompatible, the field will maintain the original operating parameters and report the version difference. The configuration terminal will determine whether a full parameter package needs to be generated. In this embodiment, the local recalculation range is directly bound to the fault path number so that the configuration change will not spread to the unrelated self-healing logic.

[0114] In one embodiment, remote configuration messages between the configuration terminal and the field pole-mounted circuit breaker can be transmitted using a main packet plus acknowledgment receipt. The main packet includes device identifier, fault path number, available parameter version, change parameter field, verification reference field, and applicability field. The acknowledgment receipt includes write status, local enable judgment result, mismatch item, current operating parameter version, and local adjacent switch status. When the configuration terminal receives an acknowledgment indicating successful write but failed enable, it does not mark the device as configured successfully, but records it as pending consistency processing. The pending consistency processing status does not affect the already running parameters, but it prevents the tie closing permission conditions dependent on the device version within the same fault path from being sent to other devices. If multiple devices within the same fault path return successful enable, the configuration terminal updates the remote configuration status of the fault path number to enabled. In this embodiment, the remote configuration status distinguishes between three levels: write, enable, and fault path consistency, enabling the configuration terminal to identify whether the parameters have truly entered a state where they can participate in self-healing control.

[0115] In a preferred embodiment, for pole-mounted circuit breakers that are temporarily unreachable by communication, the configuration terminal sets the node's operational flag when generating the fault path constraint set. The value is set to 0, while retaining its locking reference and adjacency relationship. If the node was originally a candidate isolation node, the configuration terminal finds a backup isolation node based on the upstream path and writes the corresponding locking condition and delayed isolation condition for the backup isolation node in the remote configuration parameter package. If the pole-mounted circuit breaker returns to the local state after communication is restored and the topology role identifier is consistent with the configuration terminal, the configuration terminal regenerates an incremental packet containing the node and removes the backup isolation parameter or adjusts the enable condition for the associated upstream node. In this embodiment, unreachable nodes will not be incorrectly configured as actionable isolation boundaries, but their topology position is still retained in the constraint set, which can maintain the integrity of the fault path boundary calculation.

[0116] Furthermore, after receiving the remote configuration incremental packet, the field pole-mounted circuit breaker can establish a local shadow copy of the changed parameter items and verification reference fields in the area to be activated. The local shadow copy includes the current operating parameter value, the parameter value to be activated, the fault path number, the activation condition expression, and the reference version summary. The device recalculates the data after each change in the status of a local adjacent switch. ,like If the device is not in a protection activation or action execution state, the parameters to be activated will be written to the operating parameter area. If the shadow copy remains unchanged and the original operating parameters are used, the new shadow copy will overwrite the old shadow copy if a new remote configuration incremental packet arrives and the fault path number is the same. If the fault path number is different, the parameters will be saved in parallel but not enabled at the same time. In this embodiment, the receiving, verification and operating status are distinguished by the area to be enabled and the local shadow copy, so that the remote parameters will not directly enter the action logic when the field status does not match.

[0117] In one embodiment, when the configuration terminal generates the fault confirmation delay and isolation action delay, it does not use an isolated fixed template. Instead, it generates a relative delay relationship based on the fault confirmation status, the candidate isolation node ranking value, and the adjacent device blocking conditions. The fault confirmation delay is bound to the fault reachable edge and the continuous status of the undervoltage section. The isolation action delay is bound to the candidate isolation node and role priority. The upstream blocking condition is bound to the operable status of the downstream candidate isolation node. If the downstream candidate isolation node meets the fault confirmation and can operate, the upstream power supply side protection boundary enters the blocking waiting state. If the downstream candidate isolation node cannot operate, the upstream node participates in standby isolation after the blocking release condition is met. The reclosing strategy uses the isolation completion flag as the activation prerequisite. If the isolation action is not completed or the transfer path verification fails, the reclosing strategy remains blocked. The parameter generation method of this embodiment makes the protection action, isolation delay, blocking relationship, and reclosing strategy all generated around the same fault path number, avoiding the disruption of the self-healing action chain by changes in a single parameter.

[0118] In a preferred embodiment, if the mismatch returned by the pole-mounted circuit breaker is that the local topology role identifier is inconsistent with the topology role identifier carried in the remote configuration incremental package, the configuration terminal first reads the self-healing logic diagram version and device adjacency relationship of the corresponding fault path number, and then compares the adjacent switch status reported by the field with the adjacency table in the diagram. If the field status shows that the connection boundary has changed, the configuration terminal adds the fault path number and the adjacent connection transfer path to the local recalculation range. If the field status shows that the main power supply direction is inconsistent with the direction in the diagram, the configuration terminal marks the affected feeder version as the version to be updated and stops sending parameter packages dependent on this version to the relevant devices. If it is only a single device local role record lag, the configuration terminal sends role verification information without changing the action parameters. In this embodiment, the mismatch is used to distinguish between three types of situations: topology change, field status change, and local record lag, so that subsequent configuration processing has a clear basis.

[0119] Furthermore, if the mismatch returned by the pole-mounted circuit breaker is that the local operating parameter version is inconsistent with the verification reference information, the configuration terminal checks whether the blocking conditions of the adjacent devices on which the device depends have formed a new version of the parameters that can be issued. If the blocking condition version of the adjacent device is lower, an incremental packet for the corresponding adjacent device is generated first. After the adjacent device is successfully enabled, the connection closing permission condition of the current device is reissued. If the adjacent device has been enabled but the local version of the current device is not synchronized, the configuration terminal resends an incremental packet containing the verification reference field. If multiple devices in the same fault path have inconsistent versions, the configuration terminal keeps the connection closing permission condition of the fault path disabled and retains the original reclosing strategy. In this embodiment, inconsistent version references will not cause the device to directly enable incomplete parameters. Instead, the continuity of references for adjacent blocking conditions and transfer conditions is ensured by processing the order of dependent versions.

[0120] In one embodiment, the self-healing logic diagram, fault path constraint set, remote configuration parameter package, and local acknowledgment record generated by the configuration end can be archived according to the same fault path number. The archived content includes feeder version, topology role identifier, candidate isolation node, upstream locking constraint, backup transfer edge, action timing verification result, transfer path verification result, incremental package field, and on-site activation acknowledgment. When the same feeder undergoes a diagram model change or parameter review, the configuration end retrieves the historical archived record according to the fault path number and checks whether the generated role identifier and constraint set have changed. If only the version number has changed but the path constraints have not changed, a lightweight incremental package containing only the applicable feeder version can be generated. If the path constraints have changed, parameter conversion, three types of verification, and local activation determination are re-executed. In this embodiment, the archived record is not used to replace real-time verification, but to maintain the traceability of the parameter generation basis and the consistency of parameter version evolution within the same fault path.

[0121] In a preferred embodiment, the configuration terminal establishes fault path numbers for three typical scenarios: branch line faults, trunk line faults, and interconnection power transfer restrictions. In the branch line fault scenario, the branch line boundary and fault isolation boundary are given priority in the candidate isolation node calculation, and upstream blocking constraints are generated for the upstream pole-mounted circuit breaker of the trunk line. In the trunk line fault scenario, the configuration terminal prioritizes the segment boundary nodes at both ends of the fault to form isolation parameters, and writes the spare edge containing the fault reachable edge in the interconnection power transfer path into the prohibition constraint. In the interconnection power transfer restriction scenario, the configuration terminal retains the isolation action parameters and adds the interconnection closing permission conditions to the candidate power restoration path verification reference. If the candidate power restoration path contains the section to be isolated or the blocked node, the enableable interconnection closing parameters are not generated. In this embodiment, different fault scenarios are not constructed as new processes, but are expressed under the same method framework through fault path numbers, role priorities, and constraint sets.

[0122] Furthermore, when processing the reclosing strategy, the configuration terminal binds the reclosing conditions with the isolation completion flag, the adjacent device lockout status, and the fault path number. If the reclosing mutual exclusion constraint in the fault path constraint set indicates that the isolation action has not been completed, the reclosing strategy is written into the lockout state. If the fault isolation boundary has been formed and the transfer path verification has passed, the reclosing strategy can enter the pending judgment state according to the local reclosing preparation state. If the adjacent device lockout condition reference version does not match, the reclosing strategy remains locked to avoid the reclosing action from intersecting with the isolation action or the communication closing action. In this embodiment, the reclosing strategy is not an independent parameter, but is bound together with the fault path constraint set, action timing verification, and local version reference, which can maintain the consistency of the self-healing control action chain.

[0123] In one embodiment, before the configuration terminal sends out the parameter package, it can write three types of verification results into the read-only verification field of the parameter package. The read-only verification field includes topology consistency verification value, action timing verification value, transfer path verification value, verification time, and applicable feeder version. After receiving the data, the field pole-mounted circuit breaker does not directly execute the control action based on the read-only verification field. Instead, it writes the read-only verification field and the local activation determination result together into the receipt. If the read-only verification field shows that the configuration terminal passed the verification but the local activation determination failed, the receipt contains both the configuration terminal verification value and the local mismatch item. The configuration terminal uses this to determine whether the difference occurred during the pre-send diagram verification stage or during the post-send field status change stage. If the read-only verification field is missing or inconsistent with the parameter version, the field pole-mounted circuit breaker refuses to activate the parameter package. In this embodiment, the read-only verification field provides a clear version correspondence between the configuration terminal verification and the field activation.

[0124] Furthermore, if communication is interrupted during parameter packet distribution, the field pole-mounted circuit breaker only saves the remote configuration incremental packets that have been fully received and verified. The parameter segments that have not been fully received are not written into the pending activation area. After communication is restored, the configuration terminal decides to continue or retransmit based on the current pending activation parameter version and the operating parameter version in the receipt. If there is already an old incremental packet with the same fault path number in the pending activation area and the new incremental packet has a higher version, the field will replace the old version with the new version and re-perform the local activation determination. If the new and old incremental packets correspond to different fault path numbers and the mutual exclusion set numbers are different, the field can save them in parallel but only activate them when the corresponding activation conditions are met. In this embodiment, communication anomalies will not cause half-packet parameters to enter the operating parameter area, and the execution boundary of remote configuration remains within the two conditions of complete parameter packet and local activation determination.

[0125] In one embodiment, each data object in the parameter generation, verification, and activation process has a single meaning. The fault path number is used to bind the fault reachable edge, the section to be isolated, the candidate isolation node, the constraint set, and the parameter group. The topology role identifier is used to indicate the electrical role of the pole-mounted circuit breaker in the corresponding fault path. The applicable feeder version is used to indicate the graphical basis of the self-healing logic diagram. The activation condition is used to indicate the conditions that must be met by the local adjacent switch status, topology role, and version reference. The verification reference information is used to indicate the blocking conditions or adjacent device versions that have not changed but are depended on by the changed parameters. The mismatch item in the field receipt is used to indicate the specific field where the local activation determination failed. In this embodiment, through the fixed reference relationship between the above data objects, the configuration terminal can generate parameters from the feeder topology, perform verification from the parameters, form incremental packets from the verification, and perform local activation determination from the incremental packets, forming a remote configuration closed chain.

[0126] Furthermore, during engineering deployment, the method can be implemented by configuration software, distribution automation master station, or edge configuration service to generate and verify parameters. The controller of the pole-mounted circuit breaker in the field performs reception, storage for activation, local matching, and acknowledgment reporting. The configuration end does not change the structure of the pole-mounted circuit breaker itself, nor does it require the addition of product-independent acquisition hardware. The required data all come from distribution self-healing control related data such as feeder topology, equipment status, adjacent switch relationships, main power supply path, and interconnection transfer path. If the field controller only supports fixed parameter tables, the configuration end converts the remote configuration incremental package into parameter table fields that the controller can recognize and retains the fault path number and verification reference summary. If the field controller supports multiple sets of parameters, they are written into different parameter groups according to the fault path number. In this embodiment, the method can adapt to different remote configuration data formats while keeping the core logic of topology role recognition, fault path constraints, three types of verification, and local activation determination unchanged.

[0127] In one embodiment, after the configuration terminal completes remote configuration, when a real fault occurs, the pole-mounted circuit breaker reads the corresponding parameter group according to the enabled fault path number. After the local protection is started, it matches the fault path number according to the fault current direction and the undervoltage section. If the match is successful, it performs self-healing control according to the protection action parameters, isolation action delay, reclosing strategy, tie closing allowable conditions, and adjacent equipment blocking conditions in the parameter group. If the match fails, it is processed according to the original operating parameters or conservative blocking strategy and the unmatched fault path information is reported. After the fault is handled, the configuration terminal can archive the actual action record and the corresponding parameter version to check whether the parameter package is still applicable to the new feeder version. In this embodiment, the topology role and fault path number generated in the remote configuration stage are still used for parameter group selection in the operation stage, and the parameter generation basis and the field execution basis are consistent.

[0128] In a preferred embodiment, when the configuration terminal periodically reviews the enabled parameters, it reacquires feeder topology data, pole-mounted circuit breaker status data, adjacent switch relationship data, main power supply path data, and tie-in power transfer path data, and constructs a new self-healing logic diagram. This diagram is then compared with the applicable feeder version corresponding to the enabled parameters. If the topology role identifier remains unchanged, the fault path constraint set remains unchanged, and the three types of checks still pass, the configuration terminal does not reissue the parameters. If the topology role identifier changes or any fault path constraint changes, a new remote configuration incremental package is generated. If only the status of adjacent switches changes temporarily but the diagram version remains unchanged, the configuration terminal waits for the status to stabilize before performing local enable matching. This embodiment avoids the disconnect between feeder diagrams, operating modes, and parameter versions during long-term operation through the review process, ensuring that the remote configuration parameters continuously correspond to the current self-healing logic diagram.

[0129] In one embodiment, the complete implementation process of the method can be summarized as follows: the configuration end generates a self-healing logic diagram from multi-source power distribution data, determines the topology role identifier of the pole-mounted circuit breaker in the diagram, generates a fault path constraint set based on the fault current direction, undervoltage section, and adjacent equipment status, converts the constraints into a remote configuration parameter package, performs topology consistency verification, action timing verification, and power transfer path verification on the parameter package, forms a parameter version that can be issued and performs differential encoding, and the field pole-mounted circuit breaker performs three matchings on the local adjacent switch status, topology role identifier, and operating parameter version after receiving the incremental package. If the matching is successful, the changed parameter item is written and enabled; if the matching fails, the original operating parameters are maintained and the mismatch item is reported. In this embodiment, the above processing unifies the parameter generation basis, pre-issuance verification basis, and field activation basis of the remote configuration to the same feeder topology and the same fault path number, so that the remote configuration of the pole-mounted circuit breaker self-healing control logic can form an executable fault isolation and power supply restoration parameter chain around the actual electrical path.

Claims

1. A method for remotely configuring parameters of the self-healing control logic of a pole-mounted circuit breaker, characterized in that, include: Acquire feeder topology data, pole-mounted circuit breaker status data, adjacent switch relationship data, main power supply path data, and tie-in power transfer path data; construct a self-healing logic graph with pole-mounted circuit breakers as nodes and electrical connection relationships as edges, including: The power supply points, trunk lines, branch lines, segment points, tie points, and load sections in the feeder topology data are mapped into graph data with power supply direction attributes. Write the status data of the pole-mounted circuit breaker and the relationship data of the adjacent switches into the running status field of the corresponding node; The main power supply path data and the interconnection power transfer path data are respectively marked as normal power supply side and backup power transfer side; A mutual exclusion enable relationship is established between the normal power supply side and the backup power transfer side, and the mutual exclusion enable relationship is used as a topological constraint for the subsequent generation of self-healing control logic parameters. Based on the self-healing logic diagram, the topology role identifier of each pole-mounted circuit breaker is determined, including: Calculate the upstream path from each pole-mounted circuit breaker to the power source and the downstream path to the load section along the normal power supply side; Calculate the tie-forward path that each pole-mounted circuit breaker can participate in along the standby transfer edge; Based on the intersection relationship between the upstream path, the downstream path and the tie-forward path, write at least one topology role identifier among the power supply side protection boundary, fault isolation boundary, branch line boundary, tie-forward boundary or end load boundary for each pole-mounted circuit breaker. When a circuit breaker on the same pole corresponds to multiple topology role identifiers, role priority is generated in the order of fault isolation taking precedence over interconnection and transfer. A fault path constraint set is generated based on the topology role identifier, fault current direction, undervoltage section, and adjacent pole-mounted circuit breaker status, including: The set of reachable fault edges is determined based on the direction of the fault current; the set of sections to be isolated is determined based on the undervoltage section; and the set of operable nodes is determined based on the status of the adjacent pole-mounted circuit breakers. The set of reachable fault edges, the set of sections to be isolated, and the set of operable nodes are cross-constrained with the role priority to generate a set of fault path constraints that includes upstream blocking constraints, downstream isolation constraints, branch line priority isolation constraints, tie-line transfer prohibition constraints, and reclosing mutual exclusion constraints. A remote configuration parameter package is generated based on the fault path constraint set, including protection action parameters, fault confirmation delay, isolation action delay, reclosing strategy, interconnection closing permission conditions, and adjacent equipment interlocking conditions, comprising: The upstream blocking constraint is converted into the adjacent equipment blocking condition, the downstream isolation constraint and the branch priority isolation constraint are converted into the isolation action delay and protection action parameters, the tie-to-supply prohibition constraint is converted into the tie-to-closing allow condition, and the reclosing mutual exclusion constraint is converted into the reclosing strategy. The converted parameters are bound according to the same fault path number, and the corresponding topology role identifier, applicable feeder version, parameter semantic summary and activation conditions are written into the remote configuration parameter package; The remote configuration parameter package is checked for topology consistency, action timing, and transfer path, and then sent to the corresponding pole-mounted circuit breaker after the checks are passed.

2. The method for remotely configuring parameters of the self-healing control logic of a pole-mounted circuit breaker according to claim 1, characterized in that, Perform topology consistency verification on the remote configuration parameter package, including: Match the applicable feeder version carried in the remote configuration parameter package with the version of the current feeder topology data; During version matching, the normal power supply side, backup power transfer side, pole-mounted circuit breaker node and adjacent switch relationship corresponding to the fault path number are checked item by item; During the verification process, if any isolation action delay, interconnection closing allowable condition, or adjacent equipment interlocking condition references a node that does not belong to the same fault path number, the corresponding parameter will be marked as a topology reference anomaly. The action timing check is only performed if no topology reference exception occurs.

3. The method for remotely configuring parameters of the self-healing control logic of a pole-mounted circuit breaker according to claim 2, characterized in that, Perform action timing verification on the remote configuration parameter package, including: Based on the fault path number, the corresponding protection action parameters, fault confirmation delay, isolation action delay, reclosing strategy, and adjacent equipment blocking conditions are invoked to construct the action sequence within the same fault path. The action sequence is sorted according to the role priority, and after sorting, it is checked whether the action corresponding to the power supply side protection boundary is covered by the upstream blocking constraint, whether the action corresponding to the fault isolation boundary is earlier than the action corresponding to the interconnection transfer boundary, and whether the reclosing action and the isolation action are mutually exclusive. A timing conflict flag is generated if any check result is not met.

4. The method for remotely configuring parameters of the self-healing control logic of a pole-mounted circuit breaker according to claim 3, characterized in that, The remote configuration parameter package is subjected to a transfer path verification, including: When there is no timing conflict marker, select the backup transfer edge adjacent to the set of sections to be isolated, and determine the enableable transfer path according to the connection closing allowable conditions; Perform faulty section elimination processing on the available power transfer path to obtain candidate power restoration paths that do not include the set of sections to be isolated; Verify whether all pole-mounted circuit breaker nodes on the candidate power restoration path meet the corresponding activation conditions and adjacent equipment interlocking conditions. When any candidate power restoration path contains a blocked node or a faulty reachable edge, an abnormal power transfer path marker is generated.

5. The method for remotely configuring parameters of the self-healing control logic of a pole-mounted circuit breaker according to claim 4, characterized in that, After the topology consistency check, the action timing check, and the transfer path check, the following is also included: Based on the remote configuration parameter package that does not generate the topology reference exception, the timing conflict flag, and the transfer path exception flag, a parameter version that can be distributed is formed; The version of the parameters that can be distributed is differentially encoded with the version of the current operating parameters of the corresponding pole-mounted circuit breaker to obtain a remote configuration incremental package that contains only the changed parameter items and their fault path numbers. The topology role identifier, applicable feeder version, and activation conditions are retained in the remote configuration incremental package, and the unchanged neighbor device interlocking conditions are used as verification reference information.

6. The method for remotely configuring parameters of the self-healing control logic of a pole-mounted circuit breaker according to claim 5, characterized in that, After sending the remote configuration incremental packet to the corresponding pole-mounted circuit breaker, the following is also included: Receive the local adjacent switch status, local topology role identifier, and local operating parameter version returned by the pole-mounted circuit breaker; The local adjacent switch status is matched with the activation conditions, the local topology role identifier is matched with the topology role identifier carried in the remote configuration incremental package, and the local running parameter version is matched with the verification reference information. Write and enable the changed parameter item in the remote configuration incremental package when all three matches pass; If any match fails, the original operating parameters are maintained, and the mismatch is associated with the corresponding fault path number and reported.

Images