An automatic topology identification method of a modular distribution box

Abstract

The present application relates to the technical field of intelligent power distribution equipment and power distribution automation, and particularly relates to an automatic topology identification method of a modular power distribution box; the process comprises: collecting connection behaviors of module interface insertion, mechanical locking and main circuit conduction state to form a connection behavior sequence; generating a structure-derived connection behavior sequence based on the power supply path of the module in the box and the correlation module relationship; checking the time sequence correspondence relationship and state closure relationship between the interface level and the structure-derived level sequence through cross-level consistency rules to form a topology relationship determination result; performing local topology update according to the determination result to update the topology structure mapping of the modular power distribution box; the present application overcomes the recognition dead zone and electromagnetic coupling interference caused by low impedance and high collinear branch, can accurately determine the real physical connection relationship between the modules, supports plug-and-play of the modules and dynamic adjustment of the local topology, and improves the system topology identification precision and operation and maintenance management efficiency.

Description

Technical Field

[0001] This invention relates to the field of intelligent power distribution equipment and power distribution automation technology, and more specifically to an automatic topology identification method for modular distribution boxes. Background Technology

[0002] Currently, the physical locations and electrical connections of various branch modules within modular distribution boxes frequently change dynamically due to capacity expansion, maintenance, or three-phase load adjustments. To achieve precise control of end-user loads and rapid fault location, real-time topology sensing capabilities, similar to those of distribution networks, are required. This means accurately identifying the physical correspondence between functional modules and busbar slots. However, existing topology identification methods primarily focus on link analysis at the wide-area power grid level, mainly relying on macroscopic inferences using time-series electrical data collected by intelligent monitoring terminals. These methods typically clean and structure the collected voltage, current, and power data, using algorithms to mine correlation features between data to determine connection paths. For example, patent CN116089849B discloses an automatic distribution network topology identification method based on big data. This method uses voltage correlation to verify the topological relationships between substations, lines, and transformers, and combines principal component analysis and K-Means clustering algorithms to process the dimensionality-reduced data. By identifying the consistency of voltage fluctuations, it verifies and corrects static topology errors or dynamic changes in the distribution network, achieving, to a certain extent, automated sensing of the wide-area topology relationships between substations and user meters.

[0003] However, directly transplanting existing wide-area scene recognition technologies to the micro-topology recognition inside modular distribution boxes results in failures. This is because, unlike wide-area power distribution lines, the electrical circuits inside modular distribution boxes are extremely close together and densely packed, leading to near-zero line impedance and strong electromagnetic coupling between circuits. In this low-impedance micro-environment, the voltage timing characteristics at the ends of different branches exhibit high mathematical collinearity due to the lack of line voltage drop. This extreme similarity in electrical characteristics causes recognition models based on correlation analysis or clustering algorithms to fall into a feature matrix singularity problem, making it impossible for algorithms to effectively distinguish the logical affiliation of parallel branches in almost identical waveform data. Furthermore, in high-density layouts, if signal injection is used, significant near-field electromagnetic crosstalk will inevitably occur between adjacent parallel conductors, causing non-target branches to induce pseudo-signals with amplitudes similar to the target branch. The system struggles to accurately identify the true physical connection path based solely on signal amplitude logic under dynamic load impedance fluctuations, leading to severe topology aliasing and recognition errors, failing to meet the precise control requirements of plug-and-play modular equipment. Summary of the Invention

[0004] To address the challenges of topology identification and electromagnetic coupling interference caused by low impedance and high-density branches in existing modular distribution boxes, this invention discloses an automatic topology identification method for modular distribution boxes. The method aims to accurately determine the physical connection relationships between modules through a two-level constraint of interface-level connection behavior sequences and structurally derived connection behavior sequences, thereby achieving reliable identification and local dynamic update management of parallel branch topology relationships.

[0005] To achieve the above-mentioned technical effects, the present invention adopts the following technical solution: An automatic topology identification method for a modular distribution box includes the following steps: Step 1: Define each functional module in the modular distribution box as a topology node, and define the physical plug-in interface between modules as a connection unit; and configure connection behavior acquisition parameters in each connection unit. Step 2: When an insertion, removal, or replacement operation occurs at any topology node, the corresponding connection unit records the target time information corresponding to the insertion completion state, locking completion state, and conduction confirmation state according to the preset interface state acquisition order, and constructs the first connection behavior sequence of the connection unit. Step 3: Based on the power supply path structure inside the modular distribution box, model the power supply hierarchy position, power supply path association, and resource sharing relationship of the topology nodes in the system to form a structural hierarchy relationship model; Step 4: Based on the structural hierarchy relationship model, collect the changes in power supply path reachability status, power supply resource occupancy status, or connection permission status caused by changes in the access status of topology nodes, and construct a second connection behavior sequence associated with the corresponding topology node. Step 5: For topology node pairs with connection relationship descriptions, determine the temporal correspondence and state closure relationship of the corresponding first connection behavior sequence and second connection behavior sequence through preset cross-level consistency conditions; if the determination result is yes, maintain the connection relationship description of the current topology node pair; if the determination result is no, mark the corresponding connection unit as a state to be reconstructed. Step 6: Re-execute steps 2 to 5 for the connection units in the state of being to be reconfigured, and update the connection relationship description of the corresponding topology node pairs to form a modular distribution box topology.

[0006] Preferably, the working process of step 1 includes: For each connection unit, the interface state variables corresponding to module insertion, mechanical locking, and main circuit conduction under different topology node operations are discretely sampled. For any two adjacent sampling times and Compare the state values ​​of the corresponding interface state variables one by one; When a certain interface state variable is and When the state values ​​are inconsistent, a state transition record is generated, and the interface identifier and sampling time interval corresponding to the state transition record are recorded. When a certain interface state variable is and When the state values ​​are consistent, no state transition record is generated; The state transition records generated within the same continuous operation interval are combined in the order of sampling time to form an interface state transition unit; The set of several interface state transition units is represented as connection behavior acquisition parameters.

[0007] Preferably, in step 2, for any module insertion, removal, or replacement operation event of a topology node, the connection behavior acquisition parameters are logically grouped according to their trigger time to form a first connection behavior sequence; the logical grouping process includes: Assign an operation source identifier and an event trigger index to the interface state transition unit; Arrange the interface state transition units that belong to the same operation event between adjacent sampling times in chronological order, and assign a sequence item index to each unit; Multiple sequence items are combined to form a first sequence of connection behaviors that are mapped one-to-one with the operation events of the corresponding topology nodes. When there are multiple parallel topology node operation events, each sequence is constructed according to the trigger time and operation source identifier.

[0008] Preferably, in step 2, each first connection behavior sequence is triggered by a single topology node operation event, and the start and end boundaries of the sequence are determined by the moment when the first interface state transition unit of the operation event changes and the moment when all interface state transition units complete the operation confirmation; the sequence items are arranged in chronological order, and each sequence item includes: interface identifier, corresponding interface state transition unit index, sequence item start and end sampling time, and operation event trigger source identifier; when there are multiple parallel topology node operation events, step 2 constructs its own first connection behavior sequence, and maintains the uniqueness of the sequence and its correspondence with the topology node through the operation event trigger source identifier.

[0009] Preferably, in step 3, when analyzing the power supply path structure inside the modular distribution box, the positional relationship of each topology node in the power supply path is transformed into a set of structural constraint parameters. The set of structural constraint parameters includes at least the upstream power supply node identifier, the downstream reachable node identifier, and the power supply path occupancy constraint parameters associated with the topology node. The power supply path occupancy constraint parameters are used to represent the reachability constraint relationship of other topology nodes sharing the power supply path with the topology node at the structural level under the condition of a change in the access status of the topology node. The set of structural constraint parameters is associated one-to-one with the corresponding topology node.

[0010] Preferably, in step 3, a structural hierarchy relationship model is constructed based on a set of structural constraint parameters. This model describes the structural hierarchy relationship through a set of structural hierarchy determination parameters for each topological node. The set of structural hierarchy determination parameters includes a power supply level candidate set, path constraint weight parameters, and resource sharing conflict determination parameters. The power supply level candidate set describes the multiple power supply level positions corresponding to the topological node under different combinations of power supply path occupancy states. The path constraint weight parameters represent the priority of the topological node in path occupancy constraints within each power supply path association. The resource sharing conflict determination parameters describe the structural conflict relationship between the topological node and other topological nodes under shared power supply path conditions. The construction relationship of the structural hierarchy determination parameter group is as follows: in: Indicates the first A candidate set of power supply levels for each topology node; This represents a predefined power supply level index; Indicates the first A topological node at the hierarchy The criteria for determining whether the set of structural constraint parameters is satisfied; Indicates the first Each topology node in the power supply path The path constraint weight parameters are as follows; Parameters indicating the relationship between topology nodes and power supply paths; This indicates the resource usage parameters of the topology node on the power supply path; Represents topology nodes With topology nodes Parameters for determining resource sharing conflicts between them; Representing topology nodes respectively , A collection of related resources.

[0011] Preferably, the second connection behavior sequence is constructed by determining and discretizing the structural constraint changes caused by changes in the access state of topology nodes. The construction process includes: The status of the structural hierarchy determination parameter group associated with the topology node is compared to identify changes in power supply path reachability parameters, power supply resource occupancy parameters, or connection permission parameters caused by changes in the access status of the topology node. Define each structural hierarchy decision parameter that undergoes a deterministic change as a structural constraint change item; Assign a change source topology node identifier, associated power supply path identifier, and change occurrence time identifier to each structural constraint change item; Multiple structural constraint change items are arranged in chronological order according to the time of change occurrence, generating a second connection behavior sequence associated with the topology node.

[0012] Preferably, during the construction of the second connection behavior sequence, the identified structural constraint change items are subjected to validity determination and conflict resolution during the state comparison process of the structural hierarchy judgment parameter group; The validity determination includes: Based on a preset structural determination period, the stability of the structural hierarchy determination parameters of the same topological node in a continuous sampling interval is compared. A parameter change is considered a valid structural constraint change only if the corresponding parameter maintains a consistent change trend within a sampling period of no less than a preset number of judgments. The conflict resolution process includes: When multiple structural constraint change items correspond to the same power supply path identifier under the same change occurrence time identifier, priority sorting is performed based on the path constraint weight parameter. Retain the structural constraint change items with the highest priority and mark the remaining structural constraint change items as suppression items; Only structural constraint change terms that pass the validity determination and are not marked as suppression terms are included in the second connection behavior sequence.

[0013] Preferably, the cross-level consistency determination process in step 5 includes: Within the cross-level decision window, using the sequence item index in the first connection behavior sequence as the base index, structural constraint triggering units in the second connection behavior sequence with the same operation event triggering source identifier are extracted. Based on the trigger source topology node identifier and power supply path identifier, a cross-level corresponding mapping unit is established between the sequence item of the first connection behavior sequence and the structural constraint trigger unit of the second connection behavior sequence; The timing correspondence determination of the cross-level corresponding mapping unit is performed as follows: determine whether the trigger timing identifier in the second connection behavior sequence is located within the start and end sampling time interval of the corresponding first connection behavior sequence item; if yes, retain the cross-level corresponding mapping unit; if no, delete the cross-level corresponding mapping unit and mark the corresponding first connection behavior sequence item or second connection behavior sequence structure constraint trigger unit as an unmatched item. After completing the timing correspondence determination, set difference operation is performed on the unmatched items to generate a set of unmatched sequence items and a set of unmatched trigger units; When both the set of unmatched sequence items and the set of unmatched triggering units are empty, it is determined that the topology node pair satisfies the cross-level consistency rule; When any set is a non-empty set, the corresponding connection unit is marked as a state to be reconstructed.

[0014] Preferably, after the cross-level consistency determination, the topology result is generated, including: Based on the cross-level correspondence mapping unit and the structural level determination parameter group, the topological connection matrix at the current moment is constructed; The topology connection matrix uses topology nodes as row and column indices and power supply path identifiers as matrix element values ​​to indicate whether there is a power supply path connection relationship between any two topology nodes. After the topology connection matrix is ​​constructed, a corresponding power supply level identifier is assigned to each topology node, and a node level mapping table is established. Based on the resource occupancy status flags in the second connection behavior sequence, a resource occupancy mapping table is generated. The resource occupancy mapping table is used to record the set of occupancy nodes of each power supply path under the current topology. When the cross-level consistency determination result meets the preset cross-level consistency condition, the topology connection matrix, node level mapping table and resource occupation mapping table are updated to the current valid topology identification result; When the cross-level consistency determination result does not meet the preset cross-level consistency conditions, the structural hierarchy relationship is remodeled based on the first connection behavior sequence and the second connection behavior sequence, and the reconstructed topology connection matrix is ​​generated as the current topology identification result.

[0015] Based on the above technical solution, the positive and beneficial effects of the present invention are as follows: 1. This invention constructs a two-level constraint mechanism in a modular distribution box, consisting of an interface-level connection behavior sequence and a structurally derived connection behavior sequence. It records the plug-in, mechanical locking, and main circuit conduction states of each module at the interface level. Simultaneously, it generates a structurally derived connection behavior sequence based on the power supply path, power supply level, and associated module states of the modules within the box. During the topology determination process, it verifies the consistency of the temporal correspondence and state closure relationship between the two-level sequences, thereby achieving accurate identification of the low-impedance, highly collinear topological relationships of parallel branches within the modular distribution box.

[0016] 2. This invention shifts the topology determination logic from a single electrical amplitude observation to cross-level consistency verification of interface behavior and structural derived state sequences, avoiding the impact of electromagnetic coupling interference on the identification results in high-density layout environments. It can suppress the interference of non-target branch pseudo signals on topology determination and achieve reliable determination of the real physical connection relationship between modules.

[0017] 3. This invention triggers local topology updates when modules are inserted, removed, or replaced by relying on a two-level sequence. Combined with cross-level consistency rules, it dynamically verifies the topology relationship, enabling plug-and-play modules and local topology adjustments without requiring a global recalculation of the entire distribution box topology. This improves system operating efficiency and the level of precision in operation and maintenance management. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort, wherein: Figure 1 This is a schematic diagram of the steps of the present invention; Figure 2 This is a schematic diagram of the hierarchical relationship model of the modular distribution box structure of the present invention; Figure 3 This is a logical framework diagram for generating the second connection behavior sequence of the modular distribution box of the present invention; Figure 4 This is a schematic diagram of the overall framework for cross-level consistency determination and topology generation of the present invention; Figure 5 This is a diagram showing the validity constraints and matrix writing relationship of the cross-level corresponding mapping unit in this invention. Detailed Implementation

[0019] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this invention, and not all embodiments. Based on the embodiments of this invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this invention.

[0020] In a possible implementation, a prototype will be used for illustration. This prototype is an integrated modular low-voltage distribution box with a rated current of 630A. Internally, it employs a plug-in copper busbar structure, with functional units arranged vertically in layers. The entire box is 600mm wide, 1000mm high, and 250mm deep. The main busbar is located at the rear of the box, using a three-phase four-wire copper busbar, 8mm thick, and less than 500mm long. Each functional module directly contacts the busbar via plug-in spring-loaded terminals, resulting in an extremely short contact path.

[0021] In this structure, from a traditional electrical perspective, the equivalent impedance of all branches is almost identical, and the distance between them is so short that the differences in distributed parameters can be ignored. We have actually measured this on a prototype: injecting a 10kHz test signal into different branch ports, the response amplitude difference between adjacent ports does not exceed 0.8%, and the phase difference is within 0.5 degrees. In this situation, if we still insist on "identifying the topology through differences in electrical quantities," we are essentially classifying it in a nearly completely collinear signal space, which is not separable.

[0022] The industry has long relied on electrical quantity identification methods because, in traditional power distribution network scenarios, long lines, large impedance differences, and dispersed nodes naturally provide distinguishable electrical characteristics. This has led to a default understanding: topology identification is equivalent to electrical parameter identification. This understanding is effective in open power grid environments, but it no longer holds true when the environment shrinks to a high-density, low-impedance, strongly coupled metal enclosure. This is because the input information itself lacks distinguishing dimensions. The starting point of this invention is precisely to acknowledge this. The biggest difference between modular distribution boxes and traditional lines is that their connections are not naturally generated but triggered by "plug-in behavior." In other words, topology changes are inevitably accompanied by explicit physical connection actions. By capturing this connection behavior and verifying it in conjunction with structural logic, identification can be completed without relying on differences in electrical amplitude.

[0023] In this embodiment, each functional module is designed with three types of state sensing structures. The first type is a plug-in detection structure. Specifically, a pair of alignment metal contacts are embedded in the plug-in track at the front end of the module. The contacts form a closed loop when the module is fully pushed in. This loop does not participate in the main current transmission and is only used to detect whether the plug-in is in place. The loop voltage is DC 5V, provided by the central control board, and the signal lines are arranged with shielded twisted-pair cables to avoid inductive coupling with the main current.

[0024] The second type is a locking detection structure; after the module is pushed in, a mechanical locking latch needs to be rotated to secure it. A miniature magnetic encoder is connected to the end of the latch shaft. When the latch rotates through a specified angle, the encoder outputs a level-to-level inversion signal. This signal is also connected to the digital input port of the control board. This allows for the distinction between the states of "inserted but not locked" and "truly mechanically secured".

[0025] The third type is the main circuit continuity confirmation structure. Instead of measuring the current magnitude, a separate auxiliary contact is placed next to the main contacts. This auxiliary contact only closes after the main contacts are pressed down, and there is a mechanical linkage between the two. The closure of the auxiliary contact indicates that the pressure of the main contacts has reached the design value, mechanically ensuring reliable electrical contact. The auxiliary contact is also connected to the low-voltage detection circuit.

[0026] The three detection signals are designated S1, S2, and S3. The control board scans the input ports at 1ms intervals, recording a timestamp for any state change. For each interface unit, the system generates a time series, for example: t1: S1 changes from 0 to 1; t2: S2 changes from 0 to 1; t3: S3 changes from 0 to 1. This ternary time series is the specific implementation of the first connection behavior sequence; the system does not care whether current has flowed, but only whether the physical connection process is complete and the order is reasonable. If t2 occurs before t1, or t3 does not occur, the interface is marked as an abnormal state.

[0027] Up to this point, only the physical layer has been recorded. However, a physical connection is not necessarily equivalent to a valid structural connection. For example, if a branch module is plugged into the wrong location, although it may be physically connected, it may not be allowed to supply power according to structural logic.

[0028] Therefore, this embodiment establishes a fixed structural logic model in the control board software. The model exists in the form of a graph structure, and each module type is assigned a structural role parameter at the factory, including constraints such as allowed upstream types, allowed downstream types, and maximum number of parallel connections. For example, the main incoming line module can only exist as a root node, and branch modules must be attached to the main incoming line or a superior allocation node.

[0029] Once the first sequence of connection actions is formed, the software performs structural deduction. The core logic of the deduction is: if an interface completes event t3, an edge from the upstream node to that node is attempted to be established in the graph model. However, this edge is not written directly; instead, it undergoes validity verification first. Verification includes three types of rules: power supply level rules, capacity rules, and resource usage rules.

[0030] The power supply hierarchy rule requires that the hierarchy number of the new node must be one level higher than that of the upstream node; the capacity rule requires that the remaining capacity of the upstream node be greater than the rated capacity of the node; the resource occupancy rule requires that the physical slot is not occupied by other legitimate nodes.

[0031] When all the above rules are met, the system generates a second sequence of connection behaviors. This sequence is not a physical signal, but rather a record of structural state changes at the software level. Specifically, it includes: t4: The node is marked as "reachable"; t5: Upstream capacity decreases; t6: Downstream node permission status is refreshed; the times of t4, t5, and t6 are all later than t3, and the interval does not exceed 20ms. This constitutes the derived behavior of the structural hierarchy.

[0032] The actual topology confirmation occurs during the cross-level consistency check phase. The system checks for a complete logical loop: physical layer connection and conduction are completed, structural layer generates a legally reachable state, and the time sequence of both conforms to a preset window. For example, t4 must occur within 50ms after t3; otherwise, it is considered a logical anomaly. Only when the loop is established are the formal connection relationships written into the topology mapping table.

[0033] The key to this design is that it transforms the criterion for determining whether a connection exists from a single dimension to a dual dimension. Electromagnetic coupling can affect electrical waveforms, but it cannot trigger changes in the physical states of S1, S2, and S3; software misjudgments may generate structural deductions, but without physical sequence support, the verification will fail. Both levels must be satisfied simultaneously to confirm a connection.

[0034] In prototype testing, we intentionally injected simulated signals into a slot without the module installed, attempting to interfere with the system's judgment. The results showed that because S1 was never triggered, the first connection behavior sequence was invalid, and the system did not generate any structural deductions. Conversely, we also simulated software anomalies forcibly generating reachable structural states, but due to the lack of corresponding physical time sequences, the system automatically rolled back structural changes during the consistency verification phase.

[0035] From an engineering perspective, this system is not complex. It does not use high-precision voltage sampling chips or complex signal processing algorithms; instead, it utilizes the inherent pluggable behavior of modular systems as its information source. However, in 200 consecutive random pluggable tests, the system exhibited zero misjudgments. Even with the main busbar carrying its rated current, the identification logic remained stable and unaffected by electromagnetic interference. Implementation demonstrates that, even in low-impedance, high-coupling environments, shifting the identification dimension from "electrical quantities" to "connection behavior and structural consistency," topology identification can still be stably achieved, saving additional computational resources and facilitating layout design, thus demonstrating high application potential.

[0036] To further illustrate the necessity and inventiveness of the technical solution of this invention, this embodiment provides a comparative implementation. This comparative implementation only sets up physical plug-in detection and continuity detection structures at the module interface. When the module is detected to be inserted and connected, the corresponding connection relationship is directly established in the system topology diagram, without establishing a structure derivation behavior sequence or performing cross-level consistency verification.

[0037] Specifically, in the comparative scheme, each interface is also equipped with an S1 insertion signal and an S3 conduction signal. When both S1 and S3 are in a valid state, it is considered that the module has established a connection with the upstream node, and the system immediately writes an edge into the topology adjacency list and updates the topology graph display. This scheme no longer verifies the legality of the module hierarchy, does not perform capacity checks, and does not generate a structural derivation state sequence.

[0038] In the experimental environment, the comparative scheme works correctly in simple single-module insertion scenarios. When users insert branch modules in the correct order, the system can correctly display their connection relationships. However, when the actual scenario is slightly more complex, this scheme reveals obvious problems.

[0039] First, when there are incorrect slot insertions, such as inserting a module that is only allowed as a secondary node into a slot dedicated to a primary node, the system will incorrectly identify it as a valid connection because the scale scheme establishes connections solely based on physical conductivity. This will generate an incorrect hierarchical relationship in the topology graph. Due to the lack of structural rule constraints, the system cannot recognize that the connection is logically invalid.

[0040] Secondly, in capacity-constrained scenarios, such as when the main incoming line module is designed to connect a maximum of 12 branch modules, if a 13th module is forcibly inserted, the proportional scheme will still establish a connection. This can lead to inconsistencies between the topology and the design capacity limit, and may even create overload risks in subsequent control logic.

[0041] More critically, mechanical vibrations or contact transients exist inside high-density distribution boxes. During testing, when the contacts briefly close and then open again during module insertion, the S3 signal becomes briefly effective. If the proportional scheme does not have strict debouncing and timing logic, it can easily misjudge a connection as established within milliseconds and write it into the topology table. Once an incorrect topology is written, subsequent correction becomes extremely difficult.

[0042] We simulated this situation on the prototype: the module was inserted to a half-insertion state, causing the auxiliary contact to close momentarily for 50ms before opening. In the comparative scheme, because a connection was established as soon as S3 was detected as 1, the system incorrectly generated a topology. Subsequently, when the contact opened, the system deleted the connection. This repeated operation caused the topology diagram to flicker frequently, and even resulted in display desynchronization under communication delays.

[0043] In contrast, the solution of this invention requires the formation of a complete first connection behavior sequence (S1→S2→S3) that meets the requirements of time order and duration, and also requires the generation of a second connection behavior sequence that passes consistency verification before it is formally written into the topology table. Therefore, in the aforementioned half-insertion or jitter scenarios, the first connection behavior sequence cannot be closed, the system will not generate structural deductions, and naturally will not make misjudgments.

[0044] Consider a more subtle scenario. In industrial settings, internal module faults may exist, such as welding failure of auxiliary contacts, causing the S3 signal to be normally closed. In the comparative scheme, this anomaly would be identified as a continuous conducting state, and the system would consider the module to be constantly connected, even when it is not inserted, it might incorrectly display a connection. However, in the solution of this invention, because cross-level consistency verification requires that the structural derived state must correspond to the physical sequence time, when S1 and S2 are not triggered but S3 exists alone, the first connection behavior sequence cannot be established, and the system will mark it as an abnormal interface, rather than a legitimate connection.

[0045] More importantly, from an information theory perspective, the comparative scheme uses only a single-layer physical signal as the basis for judgment, and its judgment condition dimension is one-dimensional. Any noise or anomaly that meets this single condition will lead to misjudgment. The present invention constructs a two-dimensional judgment space by combining physical connection behavior and structural logic derived behavior. Connection is confirmed only when constraints are satisfied in both dimensions simultaneously. This multi-dimensional constraint mechanism has a fundamental difference in anti-interference capability. This mechanism binds physical layer behavior with structural layer logic, making topology confirmation a process that must satisfy multiple constraints. This mechanism remains effective even in environments where electrical quantities are completely inseparable and strong electromagnetic coupling exists.

[0046] To facilitate a deeper understanding of the technology in this invention, a detailed description of an automatic topology identification method for a modular distribution box disclosed in the embodiments of this application is provided below. Please refer to [link to relevant documentation]. Figure 1 The schematic diagram shown illustrates the steps of the invention, which include: Step 1: Define each functional module in the modular distribution box as a topology node, and define the physical plug-in interface between modules as a connection unit; and configure connection behavior acquisition parameters in each connection unit. Each functional module within the modular distribution box is physically connected to adjacent modules or busbar units via standardized plug-in interfaces. Each physical plug-in interface is abstracted as a connection unit in this invention. This connection unit corresponds to at least three observable interface state variables: a module insertion status variable, a mechanical locking completion status variable, and a main circuit conduction confirmation status variable. All of these state variables are discrete, and their values ​​include at least two possible values: "not triggered" and "triggered."

[0047] During system operation, for each connection unit, the control unit continuously monitors the interface state variables using discrete sampling. This discrete sampling can employ a fixed-period sampling method or a state-change-triggered sampling method; the core principle is to form a series of ordered sampling time sets. At any two adjacent sampling times and Between them, the system compares the state values ​​of the corresponding interface state variables one by one.

[0048] When a certain interface state variable is and When the state value changes between different time intervals, a valid state transition is considered to have occurred within that sampling time interval. The system generates a state transition record. This state transition record includes at least: connection unit identifier, state variable identifier, state value before transition, state value after transition, and corresponding sampling time interval information. The sampling time interval information is used to represent the time range in which the state transition occurred, rather than a single point in time, thereby preserving the process attributes of the state change.

[0049] When a certain interface state variable is and When the state values ​​remain consistent, no state transition record is generated. In this way, the system only records state change behavior and compresses stable states, thereby avoiding meaningless duplicate data occupying storage space and allowing subsequent behavior analysis to focus on the actual connection actions that occurred.

[0050] In actual operation, a module typically undergoes a series of physical actions from initial insertion to full conduction, including advancement, positioning, locking, and contact clamping. These physical actions are sequential in time. Therefore, the concept of a "continuous operation interval" is introduced into the system. A continuous operation interval refers to a set of continuous state transition records generated by the same connection unit within a preset time window. When the time interval between two adjacent state transition records is less than a preset threshold, the system classifies them into the same continuous operation interval; when the time interval exceeds the threshold, it is considered the start of a new operation interval. This preset threshold can be set based on the statistical results of actual module insertion operation times, for example, set to within 2 seconds.

[0051] For each state transition record generated within a continuous operation interval, the system sorts and combines them according to the order of sampling time to form an interface state transition unit. This interface state transition unit is not an isolated single state change record, but a structured data object representing a complete or partial connection behavior process. This data object reflects the time-dimensional changes of state variables such as module insertion, locking, and conduction.

[0052] If, within a certain continuous operating interval, only some state variable transition records are generated, such as only a plug-in state change without a conduction confirmation state change, then this interface state transition unit is marked as an unclosed unit. It is only retained as a behavioral process record and does not participate in subsequent connection relationship confirmation. When all predetermined interface state variables complete the expected state transition within the same continuous operating interval, the interface state transition unit is marked as a closed unit.

[0053] In this invention, a set of several interface state transition units is defined as connection behavior acquisition parameters. These connection behavior acquisition parameters not only represent the state changes of a certain interface within a certain time period, but also serve as the basic input data for subsequently generating the first connection behavior sequence and performing cross-level consistency verification. In other words, the connection behavior acquisition parameters play a role in behavior modeling within the system, rather than simply storing states.

[0054] In this way, the continuous physical actions during module insertion are abstracted into an ordered state transition structure, thereby transforming the actual connection behavior into a calculable and verifiable data form. This processing method, which constructs behavioral units from state transition records and then uses these behavioral units to form connection behavior acquisition parameters, enables the system to perform subsequent topology deduction based on the behavioral process, without relying on electrical amplitude differences.

[0055] Step 2: When an insertion, removal, or replacement operation occurs at any topology node, the corresponding connection unit records the target time information corresponding to the insertion completion state, locking completion state, and conduction confirmation state according to a preset interface state acquisition sequence, thus constructing the first connection behavior sequence of the connection unit. The construction of the first connection behavior sequence is triggered by the actual operation behavior of the topology node. A topology node operation event refers to the operation process corresponding to the physical insertion, removal, or replacement action performed on a specific functional module. This operation process is not an abstract concept at the system level but is objectively reflected through the interface state transition unit formed in Step 1. When the interface state variable of a connection unit changes for the first time, the system can determine that an operation behavior targeting the corresponding topology node has been initiated.

[0056] As one possible implementation, when the system detects the generation of the first interface state transition record of a certain connection unit, it creates an operation event instance and assigns a unique operation event trigger source identifier. This identifier can be generated using an auto-incrementing number or a combination of "topology node number + timestamp". Its purpose is to distinguish the operation behaviors of different topology nodes, so as to maintain the independence of their respective sequences even if there is overlap in time.

[0057] The starting boundary of the first connection behavior sequence is determined by the sampling time when the first interface state transition unit of the corresponding operation event changes. In other words, when an interface state variable generates a state transition record for the first time within the continuous operation interval described in step 1, this sampling time is recorded as the sequence start time. The sequence termination boundary is determined by the time when all relevant interface state transition units under the operation event complete operation confirmation. The completion of operation confirmation means that within the same continuous operation interval, all interface state variables in a preset order have completed the target state transition, such as completing plugging, locking, and conduction confirmation.

[0058] It should be noted that "operation confirmation" in this application differs from the triggering of a single state variable. It emphasizes the logical closure relationship between multiple interface state variables. The triggering of a single state variable only indicates that a certain physical action has occurred, while operation confirmation indicates that the topology node has reached the expected connection state under the current operation intention, thus allowing it to enter the subsequent structural layer processing stage.

[0059] When constructing the first connection behavior sequence, the system arranges the interface state transition unit indices belonging to the same operation event sequentially according to time order. Each sequence item includes: the interface identifier corresponding to the connection unit, the state transition unit index number associated with that interface, the start and end sampling times of the sequence item, and the operation event trigger source identifier. By recording the state transition unit index, rather than simply copying the state variable information, data redundancy can be avoided, and the consistency between the sequence items and the data structure formed in step 1 can be ensured.

[0060] As one possible implementation, if only a portion of the interface state variables are transferred during an operation event, and a complete operation confirmation is not formed within a preset time window, the system marks the first connection behavior sequence as an unclosed sequence. Unclosed sequences do not participate in subsequent topology confirmations, but retain their trigger source identifier so that the original sequence can continue when a supplementary state transition occurs, rather than generating a new operation event.

[0061] In situations involving multiple parallel topology node operation events, such as the insertion of modules in two different slots almost simultaneously, the system creates an independent first connection behavior sequence for each trigger source. The distinction is not based solely on the order of events, but rather on the physical identifier of the connection unit and the identifier of the trigger source for each generated operation event. Even if the sampling times of two operation events overlap, as long as their interface identifiers differ, the system will classify them into different sequences to avoid sequence item mixing.

[0062] It should be noted that the "replacement operation" in this application differs from the simple mechanical combination of "removal + insertion". A replacement operation refers to the removal of an existing module at the same topology node location, followed by the insertion of a new module within a preset time window. By comparing the operation event trigger source identifier and the physical slot identifier, the system can associate consecutive removal and insertion actions as the same replacement event, rather than two completely independent operation sequences. This approach helps maintain structural continuity during subsequent topology update phases.

[0063] Step 3: Based on the power supply path structure inside the modular distribution box, model the power supply hierarchy position, power supply path association, and resource sharing relationship of the topology nodes in the system to form a structural hierarchy relationship model; Please see Figure 2 The schematic diagram of the hierarchical relationship model of the modular distribution box structure is shown. In an actual modular distribution box, the power supply path typically consists of the main busbar, distribution busbar, and conductors within each module. Each functional module physically occupies a specific slot and is connected to a power supply path via a plug-in structure. Step 3 first numbers all definable power supply paths within the distribution box and establishes a mapping relationship between the paths and physical slots. This mapping relationship does not rely on real-time electrical measurements but is generated based on structural design drawings or predefined structural templates.

[0064] When analyzing the power supply path structure, the positional relationship of each topology node in the power supply path is transformed into a set of structural constraint parameters. This set of structural constraint parameters is associated one-to-one with the corresponding topology node and is pre-generated during system initialization. The set of structural constraint parameters includes at least the following three categories.

[0065] The first is the upstream power supply node identifier. This identifier is used to limit the set of upstream nodes that the current topology node is structurally allowed to connect to. As one possible implementation, the upstream power supply node identifier can be stored as an array of node numbers. For example, if a branch module is only allowed to connect to the main incoming node or a certain level of distribution node, then its upstream node identifier set only contains the corresponding numbers. This parameter can be used to exclude structurally disallowed connection attempts in subsequent determinations.

[0066] The second parameter is the downstream reachable node identifier. This parameter represents the set of downstream nodes that can theoretically be reached through their power supply path when the current topology node is in a valid access state. This set is not an actual connection relationship, but rather the reachable range allowed by the structure. It should be noted that in this application, "reachable" is different from "connected." The former indicates that there is a possibility of connection at the structural level, while the latter indicates that the connection has been confirmed through behavioral verification. By distinguishing between these two concepts, confusion between the structural model and the real-time topology can be avoided.

[0067] Thirdly, there is the power supply path occupancy constraint parameter. This parameter describes the structural impact on other topology nodes sharing a power supply path when a current topology node is added or removed. For example, when a node occupies a certain allocation bus path, its occupancy behavior may affect the legality of the power supply hierarchy of other nodes on the same path. As one possible implementation, the power supply path occupancy constraint parameter can be expressed in the form of a Boolean vector or a set of resource identifiers, where each resource identifier corresponds to a power supply path segment.

[0068] Based on the aforementioned set of structural constraint parameters, a structural hierarchy model is constructed. This model is not a simple graph structure, but rather described through a set of structural hierarchy determination parameters for each topological node. The set of structural hierarchy determination parameters includes a candidate set of power supply levels. Path constraint weight parameters And resource sharing conflict determination parameters .

[0069] For the power supply level candidate set Construct the relation as follows .in, This indicates a predefined power supply level index, such as primary level, distribution level, terminal level, etc. This indicates a criterion for determining whether the i-th topological node satisfies its set of structural constraint parameters at level l. As one possible implementation, The calculation can be based on the following logic: if there is a valid match between the set of upstream node identifiers of node i at level l and the currently confirmed node set, and there is no conflict in the power supply path occupancy constraint, then Otherwise, it is 0. This is the result. It is not a single level value, but may contain multiple candidate levels, which are used to dynamically determine the actual level under different path occupancy states.

[0070] Path constraint weight parameters pass Confirmed. (Among them) The parameter representing the relationship between topology node i and power supply path p can be understood as the structural connection strength or dependence of node i on path p. This represents the resource usage parameters of node i on path p, such as the number of path segments occupied or the priority of occupation. The function f maps the path association degree and resource usage to a weight value. This weight value is used to prioritize multiple possible power supply paths when they compete for power. It should be noted that the "weight" here is different from the electrical load weight; it is only used for structural decision-making.

[0071] Resource sharing conflict determination parameters Through relational formulas Confirmed, among which and Let i and j represent the resource sets associated with topological node i and node j, respectively. When two nodes have an intersection in their resource sets, i.e. ∩ ≠∅, the function g is used to determine whether the intersection constitutes a structural conflict. For example, when two nodes share the same power supply path segment, and that path segment is designed to only allow a single node to occupy it, It is marked as a conflict state. As one possible implementation, the g function can classify and determine the conflict based on resource type and occupancy pattern, rather than simply determining whether there is an intersection.

[0072] It should be noted that the term "resources" in this application differs from traditional electrical resources. It is not limited to physical quantities such as current, voltage, or power, but rather refers to power supply path segments or connection locations that can be occupied at the structural level. By abstracting resources into set elements, sharing relationships can be uniformly handled at the logical level.

[0073] By establishing the aforementioned structural hierarchy parameter set, the structural hierarchy relationship model becomes a dynamically computable constraint system. Once the first connection behavior sequence is generated, the system can calculate the corresponding node's [connection status] based on the current power supply path occupancy status. , and The parameters are used to determine the legal hierarchical position of the resource in the current structure and whether there are resource conflicts.

[0074] Step 4: Based on the structural hierarchy model, collect changes in power supply path reachability, power supply resource occupancy, or connection permission status caused by changes in the access status of topology nodes, and construct a second connection behavior sequence associated with the corresponding topology node. When the access status of a topology node changes, for example from not connected to connected, or from connected to removed, the system first calls the structural hierarchy model to compare the status of the structural hierarchy judgment parameter group associated with that topology node. This status comparison is not simply reading the current parameter values, but rather comparing the snapshot of the structural parameters before the change with the calculated results of the structural parameters after the change, thereby identifying the structural constraint differences caused by the change in the node's access status.

[0075] It should be noted that the "power supply path reachability state" in this application is different from whether the actual voltage reaches a node. The reachability state is a logical state derived from the structural model, used to indicate whether a node has the structural path conditions to be powered under the current topology, without involving whether actual electrical energy has been transmitted. By using logical reachability rather than electrical quantity judgment, the problem of inseparable electrical signals in low impedance environments can be avoided.

[0076] For a detailed implementation, please refer to Figure 3 The diagram shown illustrates the logic framework for generating the second connection behavior sequence of the modular distribution box. The system compares various parameters in the structural hierarchy parameter group item by item. For example, regarding the power supply path reachability parameter, the system compares whether a node appears in the downstream reachable node set of its upstream node before and after the change; regarding the power supply resource occupancy parameter, the system compares whether a resource identifier has been added or released in the path occupancy set; regarding the connection permission parameter, the system compares whether a node has changed from "access prohibited" to "access permitted" under the current path occupancy status.

[0077] A structural constraint change is defined as occurring when a parameter exhibits a deterministic difference before and after a change. It should be noted that in this application, "deterministic change" differs from instantaneous fluctuations or temporary states; it requires that the parameter change satisfies the structural model constraint rules and remains consistent within a preset stable time window. As a possible implementation, the system can be configured with a short-delay confirmation mechanism, such as continuously monitoring for several calculation cycles after a parameter change, and only recognizing a valid change if the change persists.

[0078] Each structural hierarchy parameter undergoing a deterministic change is defined as a structural constraint change item. This change item must contain at least the following information: the source topology node identifier, the associated power supply path identifier, and the change occurrence time identifier. The source topology node identifier indicates which node's access status change triggered the structural change. The associated power supply path identifier indicates the specific power supply path segment or resource set involved in the change. The change occurrence time identifier records the point in time when the structural model calculations confirmed the change's validity.

[0079] As one possible implementation, structural constraint change items can also include pre-change and post-change state values ​​for subsequent consistency checks or anomaly backtracking. For example, when the reachability state of a downstream node changes from 0 to 1, the change item can record the node's identifier and its state transition direction.

[0080] After identifying multiple structural constraint changes, the system sorts them chronologically according to the occurrence time of each change and generates a second connection behavior sequence associated with the topology node. This sequence essentially reflects the trajectory of the structural constraint evolution from one stable state to another. Unlike the first connection behavior sequence, which records the physical action process, the second connection behavior sequence records the structural logical response process.

[0081] It should be noted that the second connection behavior sequence in this application records the temporal order of state changes and their causal sources, which can reflect the process of structural evolution. By recording the identifier of the change source topology node, it can be ensured that the structural change sequences triggered by each of the multiple topology nodes operating in parallel are not confused.

[0082] For example, when a branch module is inserted, the resource occupancy parameter of its upstream master node increases, and at the same time, the reachability parameter of several downstream measurement and control nodes changes from unreachable to reachable. Then, the system will generate multiple structural constraint change items and form the second connection behavior sequence corresponding to the branch module in chronological order.

[0083] In constructing the second connection behavior sequence, in addition to recording structural constraint changes, each change needs to undergo stability verification and conflict resolution to ensure that the sequence reflects truly usable structural evolution information. Specifically, when determining the validity of structural constraint changes, the system observes the parameter states of the same topology node over multiple consecutive determination periods to confirm that the change direction is consistent and there are no repeated jumps. This approach avoids misjudgments caused by instantaneous fluctuations or computational uncertainties and ensures the continuity of the structural model's response to changes in node access states. As a possible implementation, parameter changes can be included in the sequence only after maintaining the same change trend for three to five consecutive periods; changes that are not yet stable are not added temporarily for reconfirmation in subsequent periods.

[0084] For multiple changes involving the same power supply path, the system prioritizes them using path constraint weight parameters. Changes with higher weight values ​​are included in the sequence first, while other changes are marked as suppressed in the current period. This approach considers not only the path occupancy importance of the node itself but also shared resource conflict parameters to determine whether priority sorting needs to be triggered. It should be noted that in this application, "suppressed state" is different from deletion; it means that the change is temporarily ineffective but can be reactivated when conditions permit, thus avoiding the loss of structural evolution information due to a single decision.

[0085] As an implementation reference, multi-level weighting rules can be designed for different types of path resources. For example, the priority of the main busbar can be higher than that of the distribution busbar, and the priority of the terminal module can be lower than that of the core node. In this way, even if multiple nodes connect at the same time, the system can automatically determine which change is confirmed as valid first based on priority. For conflicts in reachability parameters, the reachability of low-priority nodes can be temporarily frozen after weighting, and recalculated after the upstream path resources are released. This approach is particularly important in high-density modular distribution boxes because multiple nodes operating simultaneously can easily cause cross-influences. Without adjudication, the sequence may exhibit contradictory state changes.

[0086] In practice, to ensure the feasibility of the judgment, the system can be dynamically adjusted by combining time windows and weight parameters. For example, after an operational event occurs, the system can set a short time delay window to collect the continuous changing trends of structural parameters, and then generate stable sequence items all at once, labeling their trigger source, time, and involved paths. This process avoids the large amount of intermediate data generated by continuous calculations, while maintaining sequence integrity and traceability.

[0087] It should be noted that stability determination differs from physical quantity filtering, focusing on trend consistency at the logical level; while "conflict resolution" differs from electrical protection mechanisms, only adjudicating structural occupancy priorities and shared path logic. Through this clear distinction, the system can generate a reliable second connection behavior sequence without relying on electrical amplitude, providing accurate input for cross-level consistency verification.

[0088] Furthermore, to ensure sequence uniqueness in a multi-node operation environment, each change item retains its source topology node identifier and associated power supply path identifier. This way, even with multiple parallel operations at the same time, sequence items from different source nodes can be distinguished based on the identifiers, ensuring that sequences are not confused. As one possible implementation, a combination of "node number + timestamp" can be used as the identifier, or operation event trigger source information can be added for subsequent matching with the first connection behavior sequence.

[0089] Step 5: For topology node pairs with connection relationship descriptions, determine the temporal correspondence and state closure relationship of the corresponding first connection behavior sequence and second connection behavior sequence through preset cross-level consistency conditions; if the determination result is yes, maintain the connection relationship description of the current topology node pair; if the determination result is no, mark the corresponding connection unit as a state to be reconstructed; First, it needs to be clarified that "cross-level" refers to the logical correspondence between the interface behavior layer and the structural response layer, not different voltage levels or different physical space regions. The interface behavior layer originates from the physical insertion process of the connection unit, and the structural response layer originates from the state changes in the power supply path model. The two are at different abstraction levels, hence the term "cross-level".

[0090] The "connection relationship description" refers to the power supply path association record between a pair of nodes in a specific topology that has been recorded within the system. It typically includes the node identifier, power supply path identifier, and current connection status identifier. This description may originate from a previous decision or be the default connection relationship during initialization.

[0091] Regarding the "cross-level decision window," this window is a time interval used to limit the scope of behavior involved in this decision. As one possible implementation, the cross-level decision window can be determined jointly by the start sampling time of the first sequence item and the end sampling time of the last sequence item in the first connection behavior sequence; it can also be extended according to the maximum insertion duration set by the system to cover possible structural response delays.

[0092] For specific judgment procedures, please refer to Figure 4 The diagram illustrates the overall framework for cross-level consistency determination and topology generation. Matching is performed using the sequence item index in the first connection behavior sequence as the base index, meaning that each physical plugging behavior unit needs to find a corresponding structural trigger unit at the structural level. The "structural constraint trigger unit" typically includes status indicators such as changes in power path reachability, resource occupancy status, or connection permission status, as well as corresponding trigger time indicators. As one possible implementation, the structural constraint trigger unit can be generated by the state machine output signal within the control module.

[0093] Please see Figure 5 The cross-level mapping unit validity constraints and matrix writing relationship diagram shown indicate that when establishing a "cross-level mapping unit," three elements must be consistent simultaneously: consistent operation event trigger source identifier, consistent topology node identifier, and consistent power supply path identifier. It should be noted that the "trigger source identifier" in this application differs from a general timestamp identifier; it not only represents a point in time but also distinguishes different sources of parallel operation events to avoid cross-matching errors when multiple modules operate simultaneously.

[0094] Regarding the timing correspondence determination, the core logic is not simply to determine the order of events, but rather to determine whether the trigger timing identifier of the structural triggering unit falls within the start and end sampling time interval of the corresponding sequence item. As a possible implementation method, a certain time tolerance can be allowed, for example, by setting... Tolerance range, when the trigger time is within the range Even if the time is within the specified range, it is still considered a match. This tolerance parameter can be preset according to the fluctuation range of the module's mechanical locking time.

[0095] When the determination is negative, the corresponding cross-level mapping unit is deleted, and the unmatched object is marked as "unmatched item". It should be noted that "unmatched item" is different from "pending reconstruction state". The former only indicates sequence items or triggering units for which no mapping relationship has been established in the current matching process, and belongs to the intermediate data set; the latter is the final determination result state.

[0096] During the set difference operation phase, the set of unmatched sequence items represents the situation where the interface behavior exists but the structure layer does not generate a corresponding response; the set of unmatched trigger units represents the situation where the structure layer generates a response but the interface layer does not detect the corresponding physical behavior. Both situations can lead to topology misjudgment, so they need to be statistically analyzed separately.

[0097] When both sets are empty, it indicates that the interface behavior and structural response form a complete closed structure within the decision window, and the topology node pair is deemed to satisfy the cross-level consistency rule. If either set is not empty, it indicates the existence of an unclosed link or redundant responses, and the connection unit is marked as a state to be refactored. As one possible implementation, the state to be refactored can be accompanied by an unmatched type identifier for subsequent refactoring strategy selection.

[0098] It should be noted that the "state closure relationship" in this application is different from simple time consistency. It emphasizes the integrity of behavior triggering and structural response in the logical causal chain, that is, each physical connection behavior should generate a unique and corresponding state response in the structural layer, and there are no isolated response units.

[0099] Based on the above explanation, those skilled in the art will understand that step 5 is not based on statistical correlation or probabilistic inference, but rather on the deterministic correspondence between the interface layer and the structural layer. Its technical foundation is structured data mapping and set operation logic, rather than electrical quantity analysis logic. This determination process can be implemented by a software module within the controller or by an embedded logic unit.

[0100] After cross-level consistency determination is completed, the system enters the structural result organization stage. The core task of this stage is not simply to output the determination result, but to transform the cross-level corresponding mapping units into a computable, storable, and updatable structural expression.

[0101] First, regarding the construction of the "topology connection matrix," it should be noted that the "topology connection matrix" in this application differs from the admittance matrix or impedance matrix in traditional power grid analysis. The matrix in this application does not contain electrical parameters and is only used to express the structural connection relationships between nodes. Both the row and column indices of the matrix are topology node identifiers. The values ​​of matrix elements can be power supply path identifiers or null values. When a cross-level corresponding mapping unit passes the consistency determination, the system writes the path identifier at the corresponding position in the matrix based on the trigger source topology node identifier and the power supply path identifier in the mapping unit; if no mapping unit exists, the position is empty.

[0102] As one possible implementation, the matrix can be stored using a sparse matrix structure to reduce storage overhead when the number of nodes is large; it can also be implemented internally using an adjacency list, but logically it is still regarded as a matrix representation.

[0103] The structural hierarchy determination parameter group is used to define the relative position of nodes within the power supply structure. This parameter group may include: hierarchy depth parameters. (Indicates the number of path levels from the node to the power node), path uniqueness parameter (Indicates whether a node has the potential for multipath power supply), and priority parameters. (This indicates the order of nodes in resource contention). The above parameters can be pre-calculated and stored during the structural hierarchy modeling phase. After the matrix is ​​constructed, the system... The parameters are used to sort the nodes hierarchically and generate a node hierarchy mapping table. This mapping table uses the node identifier as an index and the hierarchy number as the value to describe the current structural state.

[0104] It should be noted that the "hierarchical identifier" in this application is different from the physical installation location identifier. It refers to the power supply logic hierarchy, rather than the spatial location.

[0105] The "Resource Occupancy Mapping Table" is generated based on data from the resource occupancy status flags in the second connection behavior sequence. If each structural constraint triggering unit contains a resource occupancy status change flag, it records the corresponding power supply path flag and trigger source node flag. After the topology connection matrix is ​​determined, the system traverses all valid triggering units, merging the node sets belonging to the same path flag to form the resource occupancy mapping table. This mapping table expresses which nodes currently occupy a given power supply path. As one possible implementation, this mapping table can be stored using a key-value pair structure, where the key is the power supply path flag and the value is the node set.

[0106] When the consistency determination result meets the conditions, the currently constructed topology connection matrix, node hierarchy mapping table, and resource usage mapping table are written to the system's valid topology storage area, replacing the original structure data. This writing process can employ a double buffering mechanism to avoid instantaneous structural gaps during the update process.

[0107] When the consistency determination result does not meet the conditions, the original matrix is ​​not directly used. Instead, the structural hierarchy relationship modeling is re-executed based on the first and second connection behavior sequences. It should be noted that this "re-modeling" differs from complete initialization modeling; it involves recalculating local paths involving unmatched items while preserving the structure of unaffected nodes. As a possible implementation, the reconstruction operation can be performed only on the power supply path subgraph containing unmatched trigger units, thereby improving reconstruction efficiency.

[0108] After reconstruction, a new topology connectivity matrix is ​​generated and output as the current topology identification result. At this point, the system retains a log of unmatched items for subsequent diagnostic analysis.

[0109] It should be further clarified that the "topology identification result" in this application is not a single state flag, but is composed of the three types of data structures mentioned above: a connection matrix describes the logical connectivity between nodes, a hierarchy mapping table describes the relative hierarchical position of nodes in the power supply system, and a resource occupancy mapping table describes the path resource allocation status. The combination of these three constitutes a complete modular distribution box structure expression model.

[0110] Step 6: Re-execute steps 2 to 5 for the connection units in the pending reconstruction state, and update the connection relationship description of the corresponding topology node pairs to form a modular distribution box topology. It should be noted that the pending reconstruction state indicates that the connection unit has not formed a complete correspondence between interface behavior and structural response within the current judgment window. Its physical connection state may actually exist, or it may be in the process of insertion or in an abnormal intermediate state. Therefore, the purpose of step 6 is to reconfirm its structural affiliation, rather than directly determining its failure. Re-execution of steps 2 to 5 does not involve a global re-identification of the entire modular distribution box. As one possible implementation, the system first extracts a subset of topology nodes related to the connection unit to be reconstructed and constructs a local judgment sub-window. The time range of this sub-window can be extended forward or backward by a preset time from the original cross-level judgment window. This is used to cover any potential delays in response. Subsequently, only for this subset, interface state change information is re-collected to reconstruct the first connection behavior sequence, while simultaneously generating a new second connection behavior sequence by combining it with the current effective structural hierarchy model.

[0111] During the reconstruction process, the connection relationship descriptions of topology node pairs that are not directly related to the connection unit should be retained to avoid unnecessary global structural jitter. In other words, step 6 is a selective reconstruction, not a complete reset. As a possible implementation, a topology subgraph separation algorithm can be used to extract the power supply path branch where the connection unit to be reconstructed is located as an independent structural unit, and steps 2 to 5 are performed within the subgraph.

[0112] When updating the connection relationship description, the system writes the newly approved cross-level corresponding mapping units into the topology connection matrix, while deleting the old mapping records corresponding to the original connection units to be reconstructed. If the consistency condition is still not met after reconstruction, the reconstruction count parameter can be recorded. ,when When the preset threshold is exceeded, the connection unit is marked as a structurally abnormal unit and its disconnected state in the topology connection matrix is ​​maintained, but it does not affect the structure of other nodes.

[0113] It should be noted that "forming a modular distribution box topology" in this application does not refer to generating a static result all at once, but rather to continuously maintaining a structural data model consistent with the actual physical connection state during system operation. Step 6 ensures that the structural model has self-recovery capability under conditions such as module insertion, replacement, loosening, or transient jitter.

[0114] From the perspective of the overall solution, steps 6 and 5 together constitute a self-verifying and self-updating closed-loop system. Step 5 is responsible for determining whether the correspondence between interface behavior and structural response is valid; step 6 is responsible for initiating local structural reconstruction and updating the topology representation when the correspondence is invalid. Together, they ensure that the topology identification result always remains consistent with the actual physical connection, preventing permanent erroneous structural records due to momentary anomalies or concurrent operation conflicts.

[0115] Through the above mechanism, the topology identification method of the present invention possesses continuous operational capability. Regardless of whether the modular distribution box is in the initial assembly stage or the long-term operation stage, as long as a change in the state of the connection unit occurs, the system can trigger a reconstruction process and update the topology data within a local range, thereby maintaining the stability and consistency of the overall structural representation. Those skilled in the art can implement this process based on conventional embedded controllers and data storage units without introducing additional detection hardware or complex algorithm modules.

[0116] While specific embodiments of the present invention have been described above, those skilled in the art should understand that these specific embodiments are merely illustrative. Those skilled in the art can omit, substitute, and modify the details of the above methods and systems in various ways without departing from the principles and essence of the present invention. For example, combining the above method steps to perform substantially the same function and achieve substantially the same result according to substantially the same method falls within the scope of the present invention. Therefore, the scope of the present invention is defined only by the appended claims.

Claims

1. An automatic topology identification method for a modular distribution box, characterized in that: The method includes the following steps: Step 1: Define each functional module in the modular distribution box as a topology node, and define the physical plug-in interface between modules as a connection unit; and configure connection behavior acquisition parameters in each connection unit. Step 2: When an insertion, removal, or replacement operation occurs at any topology node, the corresponding connection unit records the target time information corresponding to the insertion completion state, locking completion state, and conduction confirmation state according to the preset interface state acquisition order, and constructs the first connection behavior sequence of the connection unit. Step 3: Based on the power supply path structure inside the modular distribution box, model the power supply hierarchy position, power supply path association, and resource sharing relationship of the topology nodes in the system to form a structural hierarchy relationship model; Step 4: Based on the structural hierarchy relationship model, collect the changes in power supply path reachability status, power supply resource occupancy status, or connection permission status caused by changes in the access status of topology nodes, and construct a second connection behavior sequence associated with the corresponding topology node. Step 5: For topology node pairs with connection relationship descriptions, determine the temporal correspondence and state closure relationship of the corresponding first connection behavior sequence and second connection behavior sequence through preset cross-level consistency conditions; if the determination result is yes, maintain the connection relationship description of the current topology node pair; if the determination result is no, mark the corresponding connection unit as a state to be reconstructed. Step 6: Re-execute steps 2 to 5 for the connection units in the state of being to be reconfigured, and update the connection relationship description of the corresponding topology node pairs to form a modular distribution box topology.

2. The automatic topology identification method for a modular distribution box according to claim 1, characterized in that: The working process of step 1 includes: For each connection unit, the interface state variables corresponding to module insertion, mechanical locking, and main circuit conduction under different topology node operations are discretely sampled. For any two adjacent sampling times and Compare the state values ​​of the corresponding interface state variables one by one; When a certain interface state variable is and When the state values ​​are inconsistent, a state transition record is generated, and the interface identifier and sampling time interval corresponding to the state transition record are recorded. When a certain interface state variable is and When the state values ​​are consistent, no state transition record is generated; The state transition records generated within the same continuous operation interval are combined in the order of sampling time to form an interface state transition unit; The set of several interface state transition units is represented as connection behavior acquisition parameters.

3. The automatic topology identification method for a modular distribution box according to claim 1, characterized in that: Step 2, for any module insertion, removal or replacement operation event of any topology node, logically groups the connection behavior acquisition parameters according to their trigger time to form a first connection behavior sequence; The logical grouping process includes: Assign an operation source identifier and an event trigger index to the interface state transition unit; Arrange the interface state transition units that belong to the same operation event between adjacent sampling times in chronological order, and assign a sequence item index to each unit; Multiple sequence items are combined to form a first sequence of connection behaviors that are mapped one-to-one with the operation events of the corresponding topology nodes. When there are multiple parallel topology node operation events, each sequence is constructed according to the trigger time and operation source identifier.

4. The automatic topology identification method for a modular distribution box according to claim 3, characterized in that: In step 2, each first connection behavior sequence is formed by a single topology node operation event, and the start and end boundaries of the sequence are determined by the moment when the first interface state transition unit of the operation event changes and the moment when all interface state transition units complete the operation confirmation. The sequence items are arranged in chronological order. Each sequence item includes: interface identifier, corresponding interface state transition unit index, start and end sampling times of the sequence item, and operation event trigger source identifier. In step 2, when there are multiple parallel topology node operation events, each first connection behavior sequence is constructed, and the uniqueness of the sequence and its correspondence with the topology node are maintained by the operation event trigger source identifier.

5. The automatic topology identification method for a modular distribution box according to claim 1, characterized in that: In step 3, when analyzing the power supply path structure inside the modular distribution box, the positional relationship of each topology node in the power supply path is transformed into a set of structural constraint parameters. The set of structural constraint parameters includes at least the upstream power supply node identifier, the downstream reachable node identifier, and the power supply path occupancy constraint parameters associated with the topology node. The power supply path occupancy constraint parameters are used to represent the reachability constraint relationship of other topology nodes sharing the power supply path with the topology node at the structural level under the condition of a change in the access status of the topology node. The set of structural constraint parameters is associated one-to-one with the corresponding topology node.

6. The automatic topology identification method for a modular distribution box according to claim 5, characterized in that: In step 3, a structural hierarchy relationship model is constructed based on the set of structural constraint parameters. The structural hierarchy relationship model describes the structural hierarchy relationship through the structural hierarchy determination parameter set of each topology node. The structural hierarchy determination parameter set includes a power supply hierarchy candidate set, path constraint weight parameters, and resource sharing conflict determination parameters. The power supply level candidate set is used to describe the multiple power supply level positions corresponding to the topology node under different combinations of power supply path occupancy states; the path constraint weight parameter is used to represent the priority of the topology node in the path occupancy constraint in each power supply path association; the resource sharing conflict determination parameter is used to describe the structural conflict relationship between the topology node and other topology nodes under the condition of sharing a power supply path. The construction relationship of the structural hierarchy determination parameter group is as follows: in: Indicates the first A candidate set of power supply levels for each topology node; This represents a predefined power supply level index; Indicates the first A topological node at the hierarchy The criteria for determining whether the set of structural constraint parameters is satisfied; Indicates the first Each topology node in the power supply path The path constraint weight parameters are as follows; Parameters indicating the relationship between topology nodes and power supply paths; This indicates the resource usage parameters of the topology node on the power supply path; Represents topology nodes With topology nodes Parameters for determining resource sharing conflicts between them; Representing topology nodes respectively , A collection of related resources.

7. The automatic topology identification method for a modular distribution box according to claim 1, characterized in that: The second connection behavior sequence is constructed by determining and discretizing the structural constraint changes caused by changes in the access state of topology nodes. The construction process includes: The status of the structural hierarchy determination parameter group associated with the topology node is compared to identify changes in power supply path reachability parameters, power supply resource occupancy parameters, or connection permission parameters caused by changes in the access status of the topology node. Define each structural hierarchy decision parameter that undergoes a deterministic change as a structural constraint change item; Assign a change source topology node identifier, associated power supply path identifier, and change occurrence time identifier to each structural constraint change item; Multiple structural constraint change items are arranged in chronological order according to the time of change occurrence, generating a second connection behavior sequence associated with the topology node.

8. The automatic topology identification method for a modular distribution box according to claim 7, characterized in that: When constructing the second connection behavior sequence, during the state comparison of the structural hierarchy judgment parameter group, the identified structural constraint change items are subjected to validity judgment and conflict resolution. The validity determination includes: Based on the preset structure determination period, the stability of the structure hierarchy determination parameters of the same topological node in the continuous sampling interval is compared. A parameter change is considered a valid structural constraint change only if the corresponding parameter maintains a consistent change trend within a sampling period of no less than a preset number of judgments. The conflict resolution process includes: When multiple structural constraint change items correspond to the same power supply path identifier under the same change occurrence time identifier, priority sorting is performed based on the path constraint weight parameter. Retain the structural constraint change items with the highest priority and mark the remaining structural constraint change items as suppression items; Only structural constraint change terms that pass the validity determination and are not marked as suppression terms are included in the second connection behavior sequence.

9. The automatic topology identification method for a modular distribution box according to claim 1, characterized in that: The cross-level consistency determination process in step 5 includes: Within the cross-level decision window, using the sequence item index in the first connection behavior sequence as the base index, structural constraint triggering units in the second connection behavior sequence with the same operation event triggering source identifier are extracted. Based on the trigger source topology node identifier and power supply path identifier, a cross-level corresponding mapping unit is established between the sequence item of the first connection behavior sequence and the structural constraint triggering unit of the second connection behavior sequence; The timing correspondence determination of the cross-level corresponding mapping unit is performed as follows: determine whether the trigger timing identifier in the second connection behavior sequence is located within the start and end sampling time interval of the corresponding first connection behavior sequence item; if yes, retain the cross-level corresponding mapping unit; if no, delete the cross-level corresponding mapping unit and mark the corresponding first connection behavior sequence item or second connection behavior sequence structure constraint trigger unit as an unmatched item. After completing the timing correspondence determination, set difference operation is performed on the unmatched items to generate a set of unmatched sequence items and a set of unmatched trigger units; When both the set of unmatched sequence items and the set of unmatched triggering units are empty, it is determined that the topology node pair satisfies the cross-level consistency rule; When any set is a non-empty set, the corresponding connection unit is marked as a state to be reconstructed.

10. The automatic topology identification method for a modular distribution box according to claim 1, characterized in that: After the cross-level consistency determination, a topology result is generated, including: Based on the cross-level correspondence mapping unit and the structural level determination parameter group, the topological connection matrix at the current moment is constructed; The topology connection matrix uses topology nodes as row and column indices and power supply path identifiers as matrix element values ​​to indicate whether there is a power supply path connection relationship between any two topology nodes. After the topology connection matrix is ​​constructed, a corresponding power supply level identifier is assigned to each topology node, and a node level mapping table is established. Based on the resource occupancy status flags in the second connection behavior sequence, a resource occupancy mapping table is generated. The resource occupancy mapping table is used to record the set of occupancy nodes of each power supply path under the current topology. When the cross-level consistency determination result meets the preset cross-level consistency condition, the topology connection matrix, node level mapping table and resource occupation mapping table are updated to the current valid topology identification result; When the cross-level consistency determination result does not meet the preset cross-level consistency conditions, the structural hierarchy relationship is remodeled based on the first connection behavior sequence and the second connection behavior sequence, and the reconstructed topology connection matrix is ​​generated as the current topology identification result.

Images