Method for constructing generalized honeycomb power distribution network topology structure model

Abstract

The application discloses a construction method of a generalized honeycomb power distribution network topology structure model, and particularly relates to the fields of power distribution network topology modeling and fault self-healing control technology, and is used for solving the problem of difficult convergence of power supply path reconstruction range caused by unbalanced topology model granularity, disconnection between operation constraints and topology in the fault self-healing process of a complex power distribution network, and insufficient calculation efficiency and decision traceability. A honeycomb unit satisfying homologous feeding, voltage level, protection partition and spatial adjacent constraints is constructed based on a honeycomb reference grid in a power distribution area, and a multi-layer topology structure covering a combination of a transformer substation and a feeder, the honeycomb unit and specific equipment and line sections is formed, the topology updating range under a fault scene is limited by a topology state anchor point and its influence domain, and candidate power supply paths are screened in an operation constraint field, so that the technical effects of converging the calculation range, improving the response speed and constraint satisfaction in the process of power distribution network fault isolation and power supply path reconstruction are achieved.

Description

Technical Field

[0001] This invention relates to the field of distribution network topology modeling and fault self-healing control technology, specifically a method for constructing a generalized cellular distribution network topology model. Background Technology

[0002] In distribution network operation, with the increase in urban load density, the proliferation of ring network structures, and the large-scale integration of distributed power sources, the frequency of operation mode adjustments, switch status changes, fault isolation, and power supply path reconfiguration has significantly increased. In current engineering practice, the topology of distribution networks largely relies on production data systems and geographic information systems, based on substations, feeders, and primary equipment. Device-level topology models are constructed through the electrical connections between these devices. These models can reflect the current network connectivity and, in conjunction with distribution automation systems, can be used for routine power flow analysis and outage range assessment. Some research and engineering applications have further introduced boundaries such as zones, feeder segments, or administrative regions to divide the distribution network into several power supply units for coarse-grained operational statistics and dispatch management.

[0003] However, in applications aimed at fault self-healing, the aforementioned device-level topology models and partitioning methods based on administrative divisions or feeder segments have significant limitations in engineering implementation. On the one hand, device-level topology uses individual switches, line segments, and transformers as nodes, resulting in excessively fine granularity. When there are multiple interconnecting switches, ring network switches, and complex wiring configurations in the network structure, each fault isolation and power supply path reconstruction often requires traversing the entire topology map again over a large area. The computational load increases rapidly with the network size, making it difficult to provide a stable and reliable power supply solution under strict time constraints. On the other hand, while coarse-grained partitioning based on feeder segments or administrative regions is convenient for management, its unit boundaries often do not completely correspond to the actual electrical connectivity range, making it difficult to accurately reflect the impact of switch state changes on local connectivity. In self-healing scenarios, it is difficult to directly use this to limit the topology update range for fault handling.

[0004] On the other hand, existing topology modeling methods typically focus on reflecting the "current primary system structure," while insufficiently considering the correlation between operational constraints, switch state combinations, and model evolution. In actual operation, constraints such as the power flow capacity of lines and transformers, voltage permissible ranges, and protection setting combinations directly determine the feasibility of a power supply path under given operating conditions. However, traditional practices often store these constraints in independent operating procedures, setting sheets, or business systems, lacking a unified version management and evidence retention mechanism with the topology model. After a fault occurs, dispatchers or self-healing algorithms need to manually or programmatically piece together topology, constraint, and state information across different systems, increasing the complexity of the decision-making process and making it difficult to trace and review the basis for subsequent power supply path selection.

[0005] In summary, existing technologies in complex distribution network self-healing scenarios lack a topology model construction method that establishes a unit-level topology expression with clear electrical meaning and stable boundaries between the feeder layer and the device layer, closely links this unit-level topology with switch states and operational constraints, can converge the calculation range to a finite region during faults, and has version management and evidence retention capabilities. As a result, existing technologies still have significant shortcomings in terms of response efficiency, constraint satisfaction, and traceability of decision-making processes in fault isolation and power supply path reconfiguration. Summary of the Invention

[0006] To address the shortcomings of existing technologies, this invention provides a method for constructing a generalized cellular distribution network topology model, thereby resolving the problems mentioned in the background section.

[0007] To achieve the above objectives, the present invention provides the following technical solution: a method for constructing a generalized cellular distribution network topology model, comprising:

[0008] S1. Obtain basic data of the distribution network, overlay a honeycomb reference grid on the distribution area, classify the line switching power supply load into the grid cell, and register the unit to protect the feeder voltage level of the substation.

[0009] S2. Based on the same source feed, voltage level, protection zone and adjacent relationship, the grid cells are aggregated to generate honeycomb cells, the load density difference area is split, and the line across the honeycomb cell is identified as the tie edge;

[0010] S3. Construct upper-level nodes using substation feeders, middle-level nodes using honeycomb units, and lower-level nodes using equipment lines. Generate a topology graph based on electrical connections and establish bidirectional indexes for node edges.

[0011] S4. Select the feeder section switch, tie switch, and ring network switch as the topology state anchor point, bind the state anchor point to the corresponding honeycomb unit edge, and register the connectivity range under different states as the influence domain.

[0012] S5. Attach power flow capacity range, voltage permissible range, protection tripping combination, and prohibition switch combination to the honeycomb unit node and the line edge to form an operation constraint field;

[0013] S6. During fault isolation and power supply path reconfiguration, the topology update range is limited based on the state anchor point influence domain. On the honeycomb unit and tie edge, the connectivity relationship is updated using the topology graph and the operation constraint field, and feasible power supply paths are selected to form a generalized honeycomb distribution network topology model.

[0014] Furthermore, S1 includes:

[0015] Within the power distribution area, equipment and operational information are collected from production materials systems, geographic information systems, and power distribution automation systems.

[0016] Under a unified unit system and geographic coordinate system, the line name, equipment number, and switch name are aligned according to the naming mapping table;

[0017] Abnormal records are removed according to the inspection rules, and missing load capacity, voltage level and protection zone number are supplemented and registered in the chain of evidence;

[0018] Based on this, the power distribution area is discrete using a honeycomb reference grid. Lines, switches and load access points are assigned to grid cells according to their geographical location. The substation, feeder, voltage level and protection zone attributes of the grid cells are also registered.

[0019] The modeling tasks within the same observation window are limited by a combination of power distribution area identifier, task identifier, and model version number.

[0020] Furthermore, S2 includes:

[0021] Within the observation window, starting with the combination of substations and feeders, adjacent grid cells are selected and aggregated into candidate honeycomb cells according to the substation, feeder, voltage level, and protection zone attributes.

[0022] When a grid cell has a load density and distributed power generation capacity that are different from those of its neighboring grid cells and reach a preset difference value, the grid cell and its neighboring grid cells are separated from the candidate honeycomb cells to form a new candidate honeycomb cell.

[0023] The occurrence frequency of honeycomb unit partitioning schemes is counted within multiple observation windows, and partitioning schemes whose occurrence frequency reaches a threshold are written into the model library as honeycomb unit partitioning results;

[0024] The lines connecting different cellular units and their switches are registered as tie sides, and the upstream and downstream cellular unit identifiers, substation names, feeder names and line numbers of the tie sides are also registered.

[0025] Furthermore, S3 includes:

[0026] Within the power distribution area, upper-level nodes are generated by combining substations and feeders, and the substation name, feeder name, voltage level, and power distribution area identifier are registered.

[0027] Intermediate nodes are generated using honeycomb units, and the honeycomb unit identifier, substation name, feeder name, protection zone number, and the total load capacity and distributed power generation capacity within the honeycomb unit are registered.

[0028] The lower-level devices generate lower-level nodes and register the device's unique identifier, device type, associated line identifier, and adjacent device identifier;

[0029] Establish relationships between upper-level nodes and middle-level nodes, as well as between middle-level nodes and lower-level nodes, and generate index entries for each node. Write the index entries into the model library according to the model version number and power distribution area identifier.

[0030] Furthermore, S4 includes:

[0031] Select feeder sectionalizing switches, tie switches, and ring network switches from the lower-level nodes as topology state anchor points;

[0032] For each topology status anchor point, register its associated cellular unit identifier, upstream line identifier, downstream line identifier, substation name, and feeder name;

[0033] On the edges between the middle-layer honeycomb units, each topology state anchor point is bound to the corresponding honeycomb unit edge, so that the topology state anchor point corresponds one-to-one with the corresponding honeycomb unit, as well as the relevant substation and feeder in the multi-layer topology structure.

[0034] Furthermore, based on the registration and binding of topology state anchors, the generation and management of the influence domain of topology state anchors include:

[0035] Within a preset time window, a connectivity search is performed for each topology state anchor point under a set of preset switch state combinations. The set of cellular cells reachable from the cellular cell where the topology state anchor point is located along the connecting edge and the internal lines of the cellular cell is registered as the influence domain.

[0036] For each influence domain, register the topological state anchor point identifier, state flag, honeycomb cell division version, and influence domain version number, and write the record into the evidence chain record;

[0037] After the new affected domain passes the integrity check, a batch version switch is performed on related affected domains within the same power distribution area;

[0038] When an inconsistency is detected between the switch type, line identifier, and location of a topology status anchor and the asset data, a status anchor configuration conflict event is recorded, a configuration conflict error code is returned, and the call to the corresponding affected domain of that topology status anchor is suspended.

[0039] Furthermore, S5 includes:

[0040] Register the power flow capacity range, current allowable range, and voltage allowable range for each line;

[0041] Register the corresponding power flow capacity range, current allowable range, and voltage allowable range for each transformer;

[0042] Register the protection setting group number and the permitted combinations of protection setting groups on the protection devices associated with the lines and transformers;

[0043] Register allowed tripping combinations and prohibited switch combinations in the logical relationships involving the coordinated operation of multiple switches;

[0044] The version number of the operational constraint rule formed by the above registration is stored in the configuration library.

[0045] Furthermore, a list of constraint entries is established for each cellular unit node, each connecting edge, and each line edge;

[0046] Each constraint entry records a unified constraint identifier, constraint name, applicable working conditions, numerical range, and priority.

[0047] And by using a unified constraint identifier, each honeycomb unit node, connection edge, and line edge is associated with a corresponding constraint entry;

[0048] During the fault isolation and power supply path reconfiguration process, candidate power supply paths that do not meet the requirements of power flow capacity range, voltage permissible range, protection setting group combination, allowed tripping combination, and prohibited switch combination are eliminated based on the operation constraint field, and a set of power supply paths that meet the operation constraint field is formed from the remaining candidate power supply paths.

[0049] Furthermore, S6 includes:

[0050] Within the configured observation window, acquire switch status, fault markers, and current and voltage values, and generate an operational snapshot;

[0051] Based on the multi-layer topology, faulty honeycomb units are located according to the fault markers of lower-layer nodes, and the influence domain of the topology state anchor point associated with the honeycomb unit is called to limit the scope of topology update.

[0052] Within a defined scope, candidate power supply paths from upstream power sources to power-destroyed cellular units are selected based on operational constraints, and the connectivity relationships between the cellular unit layer and the device layer are updated to generate power reconfiguration suggestions.

[0053] The topology update results and power supply path screening results are stored as topology model snapshots in the model library, and the power distribution area identifier and observation window number are registered.

[0054] The model version combination, along with the distribution area identifier and observation window number, forms an idempotent key to control repeated modeling of fault events, and the idempotent key information is registered in the evidence chain record.

[0055] Compared with the prior art, the present invention has the following beneficial effects:

[0056] 1. By constructing honeycomb units based on a honeycomb reference grid within the distribution area to satisfy constraints such as co-source feed, voltage level, protection zone, and spatial adjacency, a multi-layer topology covering substations and feeder combinations, honeycomb units, and specific equipment and line segments is further formed. The topology update range under fault scenarios is limited by the topology state anchor point and its pre-deduced influence domain. Candidate power supply paths are screened within the operational constraint field. This achieves the technical effects of significantly narrowing the calculation range, improving the response speed and feasibility of topology update and path screening in the process of fault isolation and power supply path reconstruction in complex distribution networks, maintaining the stability and consistency of the electrical meaning of the unit layer, and supporting the long-term reuse of self-healing decisions.

[0057] 2. By introducing observation windows, model version combinations, idempotent keys, and evidence chain records throughout the entire process of honeycomb cell partitioning, multi-layer topology construction, topology state anchor point influence domain generation, and operational constraint field attachment, the effective versions, call results, and fault handling processes of various structures and constraints are uniformly identified and traced. This achieves the technical effect of ensuring that every power supply path recommendation and fault handling has a clear source and responsibility boundary, facilitating post-event review and verification by dispatchers, and maintaining consistency and controllable risks in model updates and path decision-making behaviors even in scenarios with fluctuating communication status or incomplete basic data. Attached Figure Description

[0058] Figure 1 This is a flowchart illustrating the method for constructing the generalized honeycomb distribution network topology model of the present invention. Detailed Implementation

[0059] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0060] Example: Figure 1 A flowchart illustrating the construction method of the generalized cellular distribution network topology model of the present invention is provided. The construction method of the generalized cellular distribution network topology model includes:

[0061] S1. Obtain basic data of the distribution network, overlay a honeycomb reference grid on the distribution area, classify the line switching power supply load into the grid cell, and register the unit to protect the feeder voltage level of the substation.

[0062] S2. Based on the same source feed, voltage level, protection zone and adjacent relationship, the grid cells are aggregated to generate honeycomb cells, the load density difference area is split, and the line across the honeycomb cell is identified as the tie edge;

[0063] S3. Construct upper-level nodes using substation feeders, middle-level nodes using honeycomb units, and lower-level nodes using equipment lines. Generate a topology graph based on electrical connections and establish bidirectional indexes for node edges.

[0064] S4. Select the feeder section switch, tie switch, and ring network switch as the topology state anchor point, bind the state anchor point to the corresponding honeycomb unit edge, and register the connectivity range under different states as the influence domain.

[0065] S5. Attach power flow capacity range, voltage permissible range, protection tripping combination, and prohibition switch combination to the honeycomb unit node and the line edge to form an operation constraint field;

[0066] S6. During fault isolation and power supply path reconfiguration, the topology update range is limited based on the state anchor point influence domain. On the honeycomb unit and tie edge, the connectivity relationship is updated using the topology graph and the operation constraint field, and feasible power supply paths are selected to form a generalized honeycomb distribution network topology model.

[0067] The technical connections and implementation logic of the six steps are as follows:

[0068] In step S1, basic data of the distribution network is acquired within the distribution area and overlaid with a cellular reference grid. Lines, switches, power sources, and loads are assigned to grid cells, completing the unitized registration of substations, feeders, voltage levels, and protection zones, providing a unified spatial and attribute carrier for subsequent modeling. In step S2, based on co-source feeds, voltage levels, protection zones, and spatial adjacency, grid cells are aggregated and split to form cellular cells with stable electrical meaning. Lines crossing cellular cells are identified as connecting edges, thus clarifying the operational boundaries and connection relationships at the cell level. In step S3, upper-level nodes are constructed using substations and feeders, middle-level nodes are constructed using cellular cells, and lower-level nodes are constructed using equipment and lines. A multi-layer topology graph is generated based on electrical connections, and nodes and edges at each level are linked through a bidirectional index, establishing a traceable and searchable topology foundation. In step S4, data from lower-level equipment is analyzed. Feeder sectionalizing switches, tie switches, and ring network switches are selected as topology state anchor points. These anchor points are bound to the edges between corresponding cellular units, and the connectivity range under different switch states is registered as the influence domain, establishing a quantifiable mapping between switch states and cellular unit connectivity. In step S5, power flow capacity ranges, voltage permissible ranges, protection tripping combinations, and prohibited switch combinations are attached to cellular unit nodes and various line edges to form an operational constraint field acting on the topology graph, enabling the multi-layer topology structure to express safety boundaries. In step S6, under fault isolation and power supply path reconfiguration scenarios, the topology update range is limited based on the influence domain of the topology state anchor points. Within this limited range, the connectivity of cellular units and tie edges is updated using the multi-layer topology graph and operational constraint field, and feasible power supply paths are selected. This forms a generalized cellular distribution network topology model that meets the self-healing decision-making requirements within a unified model framework.

[0069] S1. Obtain basic data of the distribution network, overlay a honeycomb reference grid on the distribution area, classify the line switching power supply load into the grid cell, and register the cell for the protection zone of the feeder voltage level of the substation. The specific implementation is as follows:

[0070] In this invention, it is preferable to first carry out basic information collation and cellular reference grid construction within a defined power distribution area. The power distribution area refers to the power supply service range covered by at least one substation and several feeders. This range can be defined based on the power supply zoning, operation and maintenance jurisdiction or dispatching unit of the power grid company and uniquely marked by the area identifier.

[0071] Within the power distribution area, basic information related to the primary equipment and operating status of the power distribution network is obtained from the production materials system, geographic information system, and power distribution automation system. The production materials system preferably provides static asset information such as line name, switch name, equipment number, cable length, conductor type, and equipment commissioning status. The geographic information system preferably provides spatial information such as substation location, line route, tower location, load access point location, and distributed power source access point location. The power distribution automation system preferably provides operating status information such as real-time switch status, telemetry values, and operating mode markings. Among the above information, the substation name is used to uniquely identify the substation entity; the feeder name is used to identify each distribution line under the same substation; the voltage level is used to identify the voltage level range to which the line and equipment belong; the protection zone number is used to identify the protection range boundary defined by the relay protection configuration; the cable length and conductor type characterize the physical length and transmission capacity of the line; and the load access point and distributed power source access point are used to identify the user load and power source access location.

[0072] To ensure consistency in the numerical specifications of physical quantities provided by different systems, it is preferable to require that the aforementioned length-related quantities carry the unit label of meters or kilometers, voltage-related quantities carry the unit label of kilovolts, current-related quantities carry the unit label of amperes, and capacity-related quantities carry the unit label of kilovolt-amperes or megavolt-amperes. A unified unit conversion rule should be established within the system to maintain a consistent dimensional system during subsequent modeling and calculations. Regarding time rhythms, static data can be set to be synchronously updated from the production data system and the geographic information system on a daily or weekly cycle; switch status can be set to be periodically collected on a time scale of several seconds; and load estimates can be set to be updated on a time scale of several minutes, thus achieving a balance between operational accuracy and communication overhead.

[0073] Before incorporating the aforementioned multi-source information into this method module, it is preferable to unify the geographic coordinate systems of different systems. Spatial information using different projection methods or coordinate origins is mapped to a unified geographic coordinate system through preset coordinate transformation rules. For identifying fields such as line names, equipment numbers, and switch names, alignment is achieved through a pre-maintained name mapping table, unifying historical, local, and standardized names into a unique internal identifier. Regarding data quality control, it can be configured to judge the reasonableness of various values ​​according to preset quality inspection rules. These rules preferably include upper and lower limits for fields such as line length, voltage level, equipment capacity, and geographical location. When a record's value exceeds the corresponding reasonable range, the record is marked as an abnormal record and registered in the quality inspection log. Abnormal records that cannot be automatically corrected by the rules can be temporarily excluded from this modeling scope, and an error code indicating an anomaly in the basic data can be returned to the upstream system. For missing load capacity, voltage level, or protection zone number, it can be set to be filled in according to the average value of similar equipment, the standard value of upstream substation, or the default value given in the planning documents. The filling field, the reference source used, and the effective time of filling should be registered in the evidence chain record so as to trace the filling behavior and its basis afterward.

[0074] After completing the above basic information processing, a honeycomb reference grid is superimposed on the geographical boundary of the power distribution area under a unified coordinate system. The honeycomb reference grid refers to a set of interconnected grid cells that spatially discretize the power distribution area. Preferably, an approximately hexagonal geometric shape is adopted to balance spatial coverage balance and the stability of adjacency relationships. Each grid cell has a unique grid identifier in the system. The grid side length can be configured according to the regional characteristics. In urban areas with high load density or concentrated distribution of switching equipment, it can be set to several hundred meters or several tens of meters. In suburban areas with sparse load or long line spans, the side length can be appropriately increased to reduce the number of grids and computational complexity. After alignment and cleaning, the lines, switches, cable segments, transformers, load connection points, and distributed power supply connection points are projected onto the honeycomb reference grid according to their geographical coordinates. Each element is assigned to the corresponding grid cell based on the coordinate falling relationship. In each grid cell, the substation, feeder, voltage level, and protection zone attributes are registered. At the same time, a list of equipment, a list of line segments, and statistical indicators such as load capacity and distributed power supply installed capacity within the cell are generated for subsequent aggregation judgment and operation characteristic analysis of the honeycomb cells.

[0075] To ensure the traceability of the cellular reference mesh construction process and the consistency of results under repeated triggering, each mesh construction task for a specific power distribution area in this invention uses a combination of area identifier, task identifier, and model version number as a unique identifier. This combination is used as an idempotent key in this method. The idempotent key refers to the unique identifier combination used to identify whether the same power distribution area belongs to a repeated modeling task within the same observation window. When the same idempotent key reappears within the same observation window due to repeated triggering or resending requests from the upstream system, the most recently successfully constructed cellular reference mesh and its attribute results are preferably reused directly, without re-executing the entire modeling process, and the idempotent key hit is recorded in the evidence chain record. In this invention, the observation window refers to a time range set around a certain modeling moment. The state and parameters collected within this time range are considered as a consistent snapshot of the same time period. The length of the observation window can be set to several seconds to several minutes and can be adjusted by configuration parameters to adapt to different business scenarios. When a modeling task detects that the proportion of missing basic data exceeds a preset threshold according to the quality check rules, such as when the missing rate of key line attributes exceeds the proportion set in the configuration and has affected the determination of topology connectivity, this method can be set to return an error code for insufficient basic data and stop the current modeling task. At the same time, the missing field list and trigger threshold information are listed in the evidence chain record to prompt the operation and maintenance personnel or data management personnel to manually supplement the missing data. Modeling is triggered again after the missing data is supplemented and passes the quality check.

[0076] While the preferred geometry of the honeycomb reference grid is a honeycomb-shaped grid to maintain consistency with the unit layer representation of the subsequent generalized honeycomb distribution network topology model, square or triangular grids can also be used for spatial discretization in certain engineering scenarios. As long as the grid unit layer still carries the aforementioned equipment attribution attributes and statistical indicators, and participates in subsequent honeycomb unit aggregation and topology construction, it can be considered an equivalent implementation of the invention, without departing from the overall concept of constructing a generalized honeycomb distribution network topology model based on grid units. Through the above steps, a honeycomb reference grid base layer with a unified coordinate system, unified naming conventions, unified unit system, and the ability to perform quality checks and record evidence chains is formed within the distribution area. This provides a structurally stable, traceable, and idempotent control-enabled foundation for subsequent honeycomb unit partitioning, multi-layer topology graph construction, topology state anchor point registration, and operational constraint attachment. This gives the construction of the generalized honeycomb distribution network topology model a clear starting point and a repeatable execution capability.

[0077] S2. Based on the same source feed, voltage level, protection zone, and adjacency relationship, the grid cells are aggregated to generate honeycomb cells. Areas with different load densities are split, and lines crossing honeycomb cells are identified as tie edges. The specific implementation is as follows:

[0078] After the cellular reference grid is constructed, to ensure that the generalized cellular distribution network topology model has stable electrical meaning and computable boundaries at the unit level, cellular unit partitioning is carried out on the grid units corresponding to each substation and feeder combination within the same distribution area, preferably within a configurable observation window. In this invention, a cellular unit refers to an electrical operating unit formed by aggregating several grid units according to rules of shared feed, consistent voltage level, consistent protection zone, and spatial adjacency. Each cellular unit has a unique cellular unit identifier within the system and serves as the carrier of unit-level nodes in the subsequent topology structure. Shared feed in this invention refers to the feed relationship where power is supplied by the same feeder from the same substation. The observation window in this invention refers to the time range set around the time of cellular unit partitioning. Grid attributes and operating status collected within this time range are considered as a consistent snapshot of the same period. Its length can be set to several seconds to several minutes and is determined through parameter configuration during the engineering deployment phase.

[0079] Specifically, the configuration can be set up with a substation and feeder combination as the dividing point. Within an observation window, the substation, feeder, voltage level, and protection zone attributes marked in the cellular reference grid are read. Grid cells that are adjacent to existing cells on the same plane and located in the same substation, feeder, voltage level, and protection zone from upstream to downstream are selected sequentially. Grid cells that meet the above conditions are merged into the same candidate cellular cell. When a significant difference is detected between a grid cell and its adjacent grid cells in terms of load density or distributed power generation capacity, a splitting rule can be triggered to separate the grid cell and its necessary adjacent grid cells from the original candidate cellular cells and form a new candidate cellular cell. The threshold for determining significant differences is preferably determined based on historical operation records and power grid planning indicators, and is set through parameter configuration during the configuration process. Representative values ​​can be further given in the preferred embodiment and stored in the configuration library as rule version numbers so that the currently used aggregation and splitting rules can be traced when the rules are adjusted.

[0080] Within a power distribution area, there can be multiple alternative partitioning schemes for the mapping relationship between grid cells and honeycomb cells. To obtain a partitioning result that balances operational stability and engineering rationality, the above aggregation and splitting rules can be repeatedly executed within several consecutive observation windows. After each execution, a honeycomb cell partitioning scheme covering the entire area is formed, and the occurrence frequency of each partitioning scheme is accumulated and statistically analyzed within the system. When the occurrence frequency of a specific partitioning scheme in a preset number of observation windows reaches a pre-set threshold, the partitioning scheme is solidified as the currently effective honeycomb cell partitioning, and its corresponding honeycomb cell identifier and grid cell set relationship are written into the model library as the latest version. The remaining unselected partitioning schemes, along with their occurrence frequency and generation time, are recorded in the evidence chain record as alternative schemes. In this invention, the evidence chain record refers to a structured record set used to trace the honeycomb cell partitioning, rule version selection, and related operational decision-making basis. The representative values ​​of the number of observation windows and the threshold can be further shown in the preferred embodiment and adjusted through parameter configuration during the engineering deployment phase.

[0081] If, within the preset number of observation windows, the partitioning schemes generated under different rule combinations consistently fail to converge to the same result (i.e., no scheme's occurrence count reaches the set threshold), an error code for returning a cellular unit partitioning conflict can be set. Simultaneously, the previous version of the cellular unit partitioning can continue to serve as a temporary effective scheme within the power distribution area to avoid affecting subsequent topology construction and operational decisions due to partitioning instability. The time of the conflict, the list of rule version numbers used, and the frequency distribution of each partitioning scheme should be written into the evidence chain record so that maintenance personnel or planners can manually evaluate and adjust the rule settings.

[0082] After the results of the honeycomb unit division are solidified, the present invention further identifies the connection relationship across honeycomb units between the grid unit layer and the equipment and line layer. For the lines connecting two different honeycomb units and the switches installed on the lines, a tie edge mark is assigned. In the present invention, a tie edge refers to the line segment and its key switches that connect different honeycomb units and have electrical connectivity. Each tie edge has a unique tie edge identifier in the system and registers its upstream honeycomb unit identifier, downstream honeycomb unit identifier, substation name, feeder name and line number.

[0083] The aforementioned cellular unit identifiers and tie-edge identifiers are preferably encoded using the same naming rules as the unit-level nodes and line edges in the subsequent multi-layer topology construction steps. This allows for direct association of the corresponding cellular unit and tie-edge through the identifiers when constructing upper-level nodes of substations and feeders, middle-level nodes of cellular units, and lower-level nodes of equipment and lines. This enables link tracing and change synchronization from the grid unit layer to the topology layer. When the cellular unit partitioning version is updated, the system can be configured to update the upstream and downstream cellular unit identifiers of the tie-edges item by item according to the mapping relationship between the old and new cellular unit identifiers. The update operation and the version number used are included in the evidence chain record, thereby ensuring that the partitioning boundary of the generalized cellular distribution network topology model at the unit layer remains consistent with the physical network structure and operating characteristics. While possessing adjustable rules and version management capabilities, the system maintains the stability of the unit-level view provided to the outside world over a certain period of time.

[0084] S3. Construct upper-level nodes using substation feeders, middle-level nodes using honeycomb units, and lower-level nodes using equipment lines. Generate a topology graph based on electrical connections and establish bidirectional indexes for node edges. The specific implementation is as follows:

[0085] After the cellular unit partitioning is stabilized, in order to establish a clear hierarchical relationship and searchability between the station level, unit level and equipment level in the generalized cellular distribution network topology model, a multi-layer topology can be constructed within the same distribution area. In this invention, the multi-layer topology refers to a hierarchical topology representation composed of upper-level nodes, middle-level nodes, lower-level nodes and their electrical connections. In this invention, upper-level nodes refer to node entities used to represent the combination of substations and feeders, middle-level nodes refer to node entities used to represent cellular units, and lower-level nodes refer to node entities used to represent primary equipment such as switches, line segments, transformers, power supplies and loads and their connections.

[0086] Specifically, after the honeycomb unit partitioning results are solidified, corresponding upper-level nodes are generated based on the combination of each substation and its feeder within the distribution area. The upper-level nodes preferably record the substation name, feeder name, voltage level, and distribution area identifier, so as to segment the topology construction task according to the power supply boundary in the future. The honeycomb unit is used as the middle-level node, which preferably records the honeycomb unit identifier, the name of the substation it belongs to, the name of the feeder it belongs to, the protection zone number, and the total load capacity and distributed power generation capacity within the honeycomb unit. Specific switches, line segments, transformers, power sources, and loads are used as lower-level nodes, which preferably record the unique equipment identifier, equipment type, the line identifier it belongs to, and the identifier of adjacent equipment, thereby forming a multi-level node set covering the station level, unit level, and equipment level in the system. Based on the aforementioned basic information organization and the electrical connection relationship registered in the honeycomb unit division stage, it can be set to establish the association relationship between the substation and feeder combination and its subordinate honeycomb units between the upper-level nodes and the middle-level nodes, and establish the association relationship between the honeycomb unit and its contained specific equipment and line segments between the middle-level nodes and the lower-level nodes, so that the multi-layer topology can trace to the specific equipment from top to bottom, and can also trace back from the equipment to the honeycomb unit and its upstream substation and feeder.

[0087] To improve retrieval efficiency, this invention preferably generates index entries for each upper-level node and its associated middle-level nodes during the topology construction process, and for each middle-level node and its contained lower-level nodes. In this invention, an index entry refers to a structured record unit that records the node identifier, its level, and the list of hierarchical associations. Each index entry uses a unified field format to facilitate rapid navigation and positioning between different levels using the node identifier. After the multi-layer topology structure and its index entries are constructed, they are preferably encapsulated in a model library using the model version number and the distribution area identifier. In this invention, the model library refers to a persistent storage set used to store different distribution areas and different versions of the generalized cellular distribution network topology model. Simultaneously, a multi-layer topology view of the currently active version is maintained in memory for each distribution area to facilitate rapid retrieval in self-healing scenarios such as fault isolation and power supply path reconfiguration.

[0088] To control computing resource consumption and accommodate both large-area and small-area scenarios, the multi-layer topology construction task can be divided into multiple segments based on power distribution area or substation. The corresponding multi-layer topology structure can be constructed independently within each segment. The upper limit of the number of concurrent construction tasks and the topology update delay can be set for each segment. When the number of construction requests received in a certain period exceeds the preset limit, they are queued and executed in the order of arrival within that segment, thereby avoiding excessive instantaneous pressure on computing resources. The upstream dispatching master station and the distribution automation system preferably interact with the method of the present invention through a unified platform interface. The registration interface for initiating the construction may include fields such as task identifier, distribution area identifier or substation identifier, observation window number, view type, and trigger reason. In this invention, the view type is used to indicate the range of topology levels that the caller expects to return, such as only station-level and unit-level views, or a complete view including equipment-level views. The query interface for obtaining topology results may include fields such as model identifier, version combination, and view type. In this invention, the version combination indicates a combination identifier of information such as the honeycomb unit partition version, operating constraint version, and state anchor point influence domain version associated with the current topology view, so that the caller can clearly understand the version basis on which the current view is based when using the topology view.

[0089] When a mismatch is found between the specified or default honeycomb cell partitioning version used in this call and the currently configured running constraint version or other version information that needs to be consistent during the multi-layer topology construction process, it can be set to abort the current topology construction and return a topology version conflict error code, prompting the caller to use the previous stable version of the multi-layer topology view, or to coordinate the relationship between versions at the configuration level. At the same time, the task identifier, distribution area identifier, model identifier and related version combination information corresponding to this conflict are written into the evidence chain record. In this invention, the evidence chain record refers to a structured record set used to trace the basis of honeycomb cell partitioning, multi-layer topology construction, version selection and operation decision, thereby ensuring the consistency and auditability of the generalized honeycomb distribution network topology model in hierarchical expression and version management, and maintaining the stability of the cell layer and its upper and lower layer views provided to the outside world over a period of time while having the ability to adjust rules and manage versions.

[0090] S4. Select the feeder section switch, tie switch, and ring network switch as the topology state anchor point, bind the state anchor point to the corresponding cellular unit edge, and register the connectivity range under different states as the influence domain. The specific implementation is as follows:

[0091] After the multi-layer topology stabilizes, in order to establish a control mechanism within the distribution area that can accurately characterize the relationship between switch states and connectivity, this invention can be configured to select key switches with segmentation and interconnection functions from lower-level nodes to construct topology state anchor points. In this invention, topology state anchor points refer to a set of landmark nodes in the multi-layer topology used to characterize the impact of switch state changes on the connectivity of cellular units, preferably including feeder segmentation switches, interconnection switches, and ring network switches. After selecting the topology state anchor points, the system registers the cellular unit identifier, upstream and downstream line identifiers, and associated upper-level substation and feeder names for each topology state anchor point. A binding relationship is established between the edges between middle-level cellular units and the topology state anchor point, so that each topology state anchor point in the multi-layer topology can be traced back to a specific device and line segment, and can also be associated with its own cellular unit, upper-level substation, and feeder.

[0092] To avoid large-scale real-time searches during online self-healing after changes in the network structure or switch configuration, this invention preferably performs offline, batch-wise simulations of the connectivity range of each topology state anchor point under different on-state conditions within a pre-defined time window. The representative length of the time window can be given in the preferred embodiment and can be configured according to the size of the power distribution area and the scheduling strategy. Specifically, it can be set to perform connectivity searches under several preset combinations of on- or off-state conditions for each topology state anchor point within a certain power distribution area, starting from the cellular unit where the anchor point is located in the multi-layer topology structure, based on the connection edge relationship between intermediate nodes and the line connectivity relationship within the cellular unit. The set of cellular units reachable from the cellular unit where the topology state anchor point is located along the connection edge and internal line under a given combination of states is registered as the influence domain of the topology state anchor point in that state. In this invention, the influence domain refers to the set of cellular units that maintain electrical connectivity with a certain topology state anchor point under a specific combination of switch states.

[0093] When forming an influence domain, the system records the corresponding topology state anchor point identifier, state flag, simulation completion time, and the honeycomb cell partitioning version used for each influence domain. An influence domain version number is assigned to each influence domain, uniquely identifying the honeycomb cell partitioning and simulation rule version upon which the influence domain record is based. This information is written into the evidence chain record in a structured form for subsequent tracing of the basis for self-healing decisions. When a round of offline simulation has not yet covered all topology state anchor points or traversed all preset state combinations, it can be configured to continue using the previous version of the influence domain record for the incomplete update, and mark the old version in the usage record. After the new version of the influence domain is calculated and passes the integrity check, all relevant influence domain versions within the corresponding distribution area are replaced with the new version in a batch switching manner, thereby ensuring internal consistency of the influence domain version combination used in the same distribution area at any given time.

[0094] To balance the granularity of the influence domain with the consumption of computing and storage resources, this invention preferably controls the number of topology state anchors and their influence domains within a range that matches the scale of the power distribution area and the complexity of the self-healing scenario. For example, in a substation and its power distribution area with a rated voltage level of 10 kV, dozens to hundreds of topology state anchors can be selected so that the range of affected cellular units is not too large in representative fault and reconfiguration scenarios, thereby controlling the subsequent self-healing calculation time based on the influence domain to the level of several seconds. The specific number range and control strategy can be further shown in the preferred embodiment.

[0095] When the system discovers a significant inconsistency between the configuration of a topology state anchor and the upstream asset data or multi-layer topology structure during the updating or use of topology state anchors and their influence domains, such as discrepancies in switch type, line identifier, or location affiliation with the basic data, it can be configured to record a state anchor configuration conflict event. The topology state anchor identifier, relevant substation name, feeder name, cellular unit identifier, and detected inconsistencies of this event are written into the evidence chain record, and a configuration conflict error code for the topology state anchor is returned to the caller. Calls to the corresponding influence domain record of the topology state anchor are suspended until the error is resolved to avoid making self-healing path decisions based on incorrect configurations. This ensures that the generalized cellular distribution network topology model has rapid fault response capabilities while maintaining consistency and auditability between state anchors and actual network assets.

[0096] S5. Attach power flow capacity range, voltage permissible range, protection tripping combinations, and prohibited switch combinations to the honeycomb unit nodes and line edges to form an operational constraint field, specifically implemented as follows:

[0097] After the multi-layer topology and the topology state anchor point influence domain are prepared, in order to ensure that the generalized cellular distribution network topology model has a constrained safety boundary in self-healing decision-making and scheduling assistance, it can be set to attach operational constraint information item by item to the cellular unit nodes and the tie edges and line edges in the intermediate topology. In this invention, the operational constraint field refers to a set of constraints attached to the cellular unit nodes and line edges to limit the boundaries of power flow, voltage and protection actions.

[0098] Specifically, it can be configured to register the power flow capacity range, current allowable range, and voltage allowable range for each line and each transformer, register the protection setting group number and the set group combination allowed under different operating conditions for the related protection devices, and register the allowed tripping combination and prohibited switch combination for the logical relationship involving the coordinated operation of multiple switches. The range and combination adopted are preferably determined by engineering rules based on the equipment nameplate parameters, planning and design documents, and approved operating procedures, and stored in the configuration library in the form of operating constraint rule version number so that they can be switched by version when the operating procedures or planning conditions are adjusted.

[0099] For suggested values ​​such as the upper limit of power flow and the target voltage range generated by the short-term load forecasting model or the optimization calculation module, they can be set as temporary values ​​in the corresponding constraint entries. In this invention, a constraint entry refers to a structured record unit that records the constraint name, applicable conditions, numerical range and priority. The applicable time period and applicable spatial range of the temporary value are registered in the entry, such as being limited to a specific distribution area or a specific set of cellular units within a certain observation window. At the same time, the source and version information of the temporary value are separately registered in the evidence chain record to prevent the long-term use of constraints that exceed the compliance boundary when the forecasting conditions have changed.

[0100] Each cellular unit node and each interconnection edge and line edge preferably maintains a list of constraint entries. Each entry in the list records a unified constraint identifier, constraint name, applicable operating conditions, numerical range, and priority. In this invention, the unified constraint identifier is used to associate a specific topology node or edge with its corresponding constraint entry during operation, so that the upstream self-healing decision module or dispatcher interface can quickly retrieve and determine the relevant capacity range, voltage range, and protection combination through the constraint identifier when evaluating the power supply path.

[0101] To ensure the safety of control boundaries and the clarity of responsibility division, the method of this invention does not directly issue switch operation commands. Instead, it forms a set of candidate power supply paths that meet the operational constraints under the current model version combination by calling the operational constraint field and the topology state anchor point influence domain. These paths are then selected and executed by the upstream self-healing decision module or the dispatcher interface. When all candidate power supply paths are excluded due to capacity range, voltage permissible range, or protection tripping combination constraints in the operational constraint field during a fault isolation and power supply path reconfiguration scenario, the method can be set to return only the path and switch state suggestions used to achieve fault isolation, along with an error code indicating that the constraints are too strict. This suggests the need for manual evaluation and appropriate relaxation at the planning, protection setting, or operation procedure level. Simultaneously, the version number of the operational constraint rule, the honeycomb unit partitioning version number, and the influence domain version number used in this decision are written into the evidence chain record.

[0102] The version information of the operating constraint field, together with the version of the cellular unit partition and the version of the topology state anchor point influence domain, constitute the model version combination. In this invention, the model version combination refers to the combination identifier used to identify the version of the generalized cellular distribution network topology model that is effective in the three aspects of topology level, state influence domain and operating constraints at a certain moment. This combination is uniformly written into the evidence chain record for the traceability and auditability of the self-healing decision process, the basis for power supply path selection and the setting of safety boundaries after the fact.

[0103] S6. During fault isolation and power supply path reconfiguration, the topology update range is limited based on the state anchor point influence domain. Connectivity relationships are updated and feasible power supply paths are selected on the cellular unit and tie edges using the topology graph and operational constraint field, forming a generalized cellular distribution network topology model. The specific implementation is as follows:

[0104] When a power distribution automation system detects signals such as protection device activation, sudden current changes, or voltage exceeding limits indicating a fault in a certain line or equipment segment, it can be configured to collect the current switch status, fault markers, and measured values ​​such as current and voltage related to the fault area within a pre-configured observation window. In this invention, the observation window refers to a time range set around the fault detection time; the status and values ​​collected within this range are considered as a snapshot of the operation for the same period. After obtaining the operational snapshot, the system first locates the fault to the corresponding cellular unit based on the aforementioned multi-layer topology structure, using the fault markers of lower-level nodes and adjacent electrical connections as clues, and retrieves the set of topology state anchor points associated with that cellular unit. Subsequently, based on the influence domain of each topology state anchor point under the current switch status combination, the scope of this topology update is limited to the faulty cellular unit and the cellular units and interconnecting edges covered by its influence domain. The topology relationships of cellular units and line edges outside this scope are not modified, thereby reducing the calculation range and controlling the topology update time while maintaining the accuracy of fault area characterization.

[0105] Within the defined update scope, this invention can be configured to enumerate several candidate power supply paths from the upstream power source to the power-outage cellular unit on a multi-layer topology, and check the operational constraint entries attached to each cellular unit node and line edge on the path one by one. The operational constraint entries include power flow capacity range, current allowable range, voltage allowable range, protection setting group combination, and allowed tripping combination and prohibited switch combination, etc. The system preferably eliminates candidate paths that may cause power flow to exceed capacity range, voltage to exceed allowable range, protection tripping combination not allowed, or prohibited switch combination to be violated at any cellular unit or line edge, and retains only several power supply path schemes that meet the operational constraint field. On this basis, the connectivity relationship between the cellular unit layer and the equipment layer is updated within the defined scope, the cellular unit where the faulty component is located is isolated from the normal power supply link, and corresponding power supply reconfiguration suggestions are given for the cellular unit that has lost power due to the fault.

[0106] The topology update results and power supply path selection results generated under the current observation window together constitute a new snapshot of the generalized cellular distribution network topology model. This snapshot is stored in the model library in a structured form and includes metadata such as distribution area identifier, observation window number, cellular unit division version, operating constraint rule version, topology state anchor point influence domain version, fault identifier, and generation time. The model version combination, which consists of the version information, is used to identify the complete model basis on which this snapshot is based. The system pushes the model snapshot identifier, recommended power supply path set, and model version combination to the self-healing decision module and the dispatcher interface through the aforementioned unified platform interface to support subsequent automatic or manual decision-making.

[0107] To avoid multiple model modifications when the same fault event is repeatedly triggered within the same observation window, this invention can be configured to combine the distribution area identifier, observation window number, and model version to form an idempotent key. In this invention, the idempotent key refers to a unique identifier combination used to identify whether they belong to the same modeling task. When a fault event with the same idempotent key is received again within the same observation window, the system directly returns the previously generated model snapshot and recommended path result, and records the current idempotent key hit in the evidence chain record to ensure the consistency of the fault handling process. When the upstream distribution automation system fails to provide the latest status snapshot covering the current observation window within a preset time limit, or when the communication quality monitoring module determines that the current communication status is unstable, the system can be configured to reuse the most recently successfully built model snapshot generation path suggestion for a short period of time within a limited time, and attach historical model markers and communication instability error codes to the returned results, prompting the caller to manually and carefully confirm the recommended path.

[0108] Preferably, in a distribution network scenario with a rated voltage level of 10 kV, the delay of a single topology update can be controlled within a few seconds, and the number of recommended power supply paths can be controlled within a few, so as to balance the computing load and the availability of human-machine interaction. The entire method is preferably deployed as a decision support module in the dispatch master station or distribution automation platform, and asset data and operation records are read only when the necessary access permissions are obtained. Records involving personal information are masked or anonymized, thereby improving self-healing efficiency and power supply reliability while meeting the requirements of enterprises in terms of safety management and compliance management.

[0109] All calculations involved in the embodiments are dimensionless numerical calculations, and the preset parameters and thresholds in the calculations are set by those skilled in the art according to the actual situation.

[0110] It should be noted that this invention can be deployed on the device itself to realize embedded applications, or it can run on a PC or other terminal with a user interface, thereby meeting various hardware environments and usage requirements.

[0111] The above embodiments can be implemented, in whole or in part, by software, hardware, firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wireless or wired transmission; wired transmission methods include optical fiber, twisted pair, coaxial cable, etc.; wireless transmission includes infrared, microwave, etc. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center containing one or more sets of available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. A semiconductor medium can be a solid-state drive.

[0112] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and modules described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0113] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or modules may be electrical, mechanical, or other forms.

[0114] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0115] In addition, the functional modules in the various embodiments of this application can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module.

[0116] If the aforementioned functions are implemented as software functional modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0117] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0118] In conclusion, the above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A method for constructing a generalized cellular distribution network topology model, characterized in that, include: S1. Obtain basic data of the distribution network, overlay a honeycomb reference grid on the distribution area, classify lines, switches, power sources and loads into grid cells, and register the cell counterparts for substations, feeders, voltage levels and protection zones. S2. Based on the same source feed, voltage level, protection zone and adjacent relationship, the grid cells are aggregated to generate honeycomb cells, the load density difference area is split, and the line across the honeycomb cell is identified as the tie edge; S3. Construct upper-level nodes using substations and feeders, middle-level nodes using honeycomb units, and lower-level nodes using equipment lines. Generate a topology graph based on electrical connections and establish bidirectional indexes for node edges. S4. Select feeder sectionalizing switches, tie switches, and ring network switches as topology state anchor points, bind the state anchor points to the corresponding honeycomb unit edges, and register the connectivity range under different states as the influence domain; select feeder sectionalizing switches, tie switches, and ring network switches as topology state anchor points from the lower-level nodes; For each topology state anchor point, register the cell unit identifier, upstream line identifier, downstream line identifier, substation name, and feeder name; establish a binding relationship between each topology state anchor point and the corresponding cell unit edge on the edge between the middle-layer cell units, so that the topology state anchor point corresponds one-to-one with the corresponding cell unit, as well as the relevant substation and feeder in the multi-layer topology structure. S5. Attach power flow capacity range, voltage permissible range, protection tripping combination, and prohibition switch combination to the honeycomb unit node and the line edge to form an operation constraint field; S6. During fault isolation and power supply path reconfiguration, the topology update range is limited based on the state anchor point influence domain. On the cellular unit and tie edge, the connectivity relationship is updated using the topology graph and operational constraint field, and feasible power supply paths are selected to form a generalized cellular distribution network topology model. Within the configured observation window, the switch status, fault markers, and current and voltage values ​​are acquired and an operational snapshot is formed. Based on the multi-layer topology, the faulty cellular unit is located according to the fault markers of the lower-level nodes, and the topology state anchor point influence domain associated with the cellular unit is called to limit the topology update range. Within the limited range, candidate power supply paths from the upstream power source to the power-out cellular unit are selected according to the operational constraint entries, and the connectivity relationship of the cellular unit layer and the equipment layer is updated to generate power supply reconfiguration suggestions. The topology update results and power supply path selection results are stored in the model library as topology model snapshots, and the distribution area identifier and observation window number are registered. The model version combination with the distribution area identifier and observation window number is used to form an idempotent key to control the repeated modeling of fault events, and the idempotent key information is registered in the evidence chain record.

2. The method for constructing the generalized cellular distribution network topology model according to claim 1, characterized in that, S1 includes: Within the power distribution area, equipment and operational information are collected from production materials systems, geographic information systems, and power distribution automation systems. Under a unified unit system and geographic coordinate system, the line name, equipment number, and switch name are aligned according to the naming mapping table; Abnormal records are removed according to the inspection rules, and missing load capacity, voltage level and protection zone number are supplemented and registered in the chain of evidence; Based on this, the power distribution area is discrete using a honeycomb reference grid. Lines, switches and load access points are assigned to grid cells according to their geographical location. The substation, feeder, voltage level and protection zone attributes of the grid cells are also registered. The modeling tasks within the same observation window are limited by a combination of power distribution area identifier, task identifier, and model version number.

3. The method for constructing a generalized cellular distribution network topology model according to claim 1, characterized in that, S2 include: Within the observation window, starting with the combination of substations and feeders, adjacent grid cells are selected and aggregated into candidate honeycomb cells according to the substation, feeder, voltage level, and protection zone attributes. When a grid cell has a load density and distributed power generation capacity that are different from those of its neighboring grid cells and reach a preset difference value, the grid cell and its neighboring grid cells are separated from the candidate honeycomb cells to form a new candidate honeycomb cell. The occurrence frequency of honeycomb unit partitioning schemes is counted within multiple observation windows, and partitioning schemes whose occurrence frequency reaches a threshold are written into the model library as honeycomb unit partitioning results; The lines connecting different cellular units and their switches are registered as tie sides, and the upstream and downstream cellular unit identifiers, substation names, feeder names and line numbers of the tie sides are also registered.

4. The method for constructing a generalized cellular distribution network topology model according to claim 1, characterized in that, S3 include: Within the power distribution area, upper-level nodes are generated by combining substations and feeders, and the substation name, feeder name, voltage level, and power distribution area identifier are registered. Intermediate nodes are generated using honeycomb units, and the honeycomb unit identifier, substation name, feeder name, protection zone number, and the total load capacity and distributed power generation capacity within the honeycomb unit are registered. The lower-level devices generate lower-level nodes and register the device's unique identifier, device type, associated line identifier, and adjacent device identifier; Establish relationships between upper-level nodes and middle-level nodes, as well as between middle-level nodes and lower-level nodes, and generate index entries for each node. Write the index entries into the model library according to the model version number and power distribution area identifier.

5. The method for constructing the generalized cellular distribution network topology model according to claim 1, characterized in that: Based on the registration and binding of topology state anchors, the generation and management of the influence domain of topology state anchors include: Within a preset time window, a connectivity search is performed for each topology state anchor point under a set of preset switch state combinations. The set of cellular cells reachable from the cellular cell where the topology state anchor point is located along the connecting edge and the internal lines of the cellular cell is registered as the influence domain. For each influence domain, register the topological state anchor point identifier, state flag, honeycomb cell division version, and influence domain version number, and write the record into the evidence chain record; After the new affected domain passes the integrity check, a batch version switch is performed on related affected domains within the same power distribution area; When an inconsistency is detected between the switch type, line identifier, and location of a topology status anchor and the asset data, a status anchor configuration conflict event is recorded, a configuration conflict error code is returned, and the call to the corresponding affected domain of that topology status anchor is suspended.

6. The method for constructing a generalized cellular distribution network topology model according to claim 1, characterized in that, S5 include: Register the power flow capacity range, current allowable range, and voltage allowable range for each line; Register the corresponding power flow capacity range, current allowable range, and voltage allowable range for each transformer; Register the protection setting group number and the permitted combinations of protection setting groups on the protection devices associated with the lines and transformers; Register allowed tripping combinations and prohibited switch combinations in the logical relationships involving the coordinated operation of multiple switches; The version number of the operational constraint rule formed by the above registration is stored in the configuration library.

7. The method for constructing the generalized cellular distribution network topology model according to claim 1, characterized in that: Establish a list of constraint entries for each cellular unit node, each connecting edge, and each line edge; Each constraint entry records a unified constraint identifier, constraint name, applicable working conditions, numerical range, and priority. And by using a unified constraint identifier, each honeycomb unit node, connection edge, and line edge is associated with a corresponding constraint entry; During the fault isolation and power supply path reconfiguration process, candidate power supply paths that do not meet the requirements of power flow capacity range, voltage permissible range, protection setting group combination, allowed tripping combination, and prohibited switch combination are eliminated based on the operation constraint field, and a set of power supply paths that meet the operation constraint field is formed from the remaining candidate power supply paths.

Images