A method for dynamic coordination and control of NID and bandwidth in low-voltage multi-mode networks
By constructing historical situation tables to predict conflicts and prioritizing bandwidth parameter adjustments, the problem of untimely network coordination in existing technologies is solved, achieving efficient and low-cost network coordination and service continuity.
Patent Information
- Application Number
- CN202611596264.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-10-15
- Publication Date
- 2026-11-10
AI Technical Summary
Existing technologies suffer from long network coordination detection windows and late negotiation triggers in complex multi-zone environments, and fail to effectively balance the costs of NID changes and bandwidth adjustments, resulting in untimely network conflict responses.
By building historical situation tables, we can predict conflict risks and proactively trigger coordination processes, prioritize adjusting bandwidth parameters, make NID changes only when necessary, and use proxy coordinators to ensure critical business continuity.
It significantly reduces the probability of high-cost network identifier changes, improves the efficiency and reliability of network coordination, and ensures the continuity of critical services during network reconfiguration.
Smart Images

Figure CN123075690A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of dual-mode communication technology, specifically to a method for dynamic coordination and control of NID and bandwidth in low-voltage multi-dual-mode networks. Background Technology
[0002] Dual-mode communication, consisting of high-speed carrier (HPLC) and high-speed wireless (HRF), has become the preferred communication method for low-voltage power line acquisition systems and distribution transformer detection systems. In low-voltage power line dual-mode communication systems, when multiple power lines are deployed adjacent to each other, the networks built by different CCOs overlap in physical space, requiring inter-network coordination.
[0003] Currently, multi-network coordination mainly relies on the following mechanisms: NID Coordination: After power-on, the CCO first performs network monitoring for a period of time (up to 10 seconds) to determine if other high-speed carrier communication networks exist nearby. If so, it periodically sends inter-network coordination frames. These frames carry parameters such as duration (a 16-bit field indicating the length of time slot this network needs to request, in 1 milliseconds), bandwidth start offset (a 16-bit field indicating the time offset of the next bandwidth time slot start, in 1 milliseconds), and the received neighbor network number. When the NID displayed in the inter-network coordination frame of another network monitored by the CCO matches the NID selected by this network, it indicates a NID conflict, requiring negotiation. During negotiation, the CCO first sets a random negotiation buffer period within the range of 10ms to 10s, continuing to monitor within this buffer period. If the conflict persists, a new idle NID is used as the identifier for this network, and network reconfiguration is initiated. When multiple network conflicts are detected through conflict reporting messages, the MAC addresses of the CCO can be compared. The party with the larger MAC address can keep its existing NID unchanged, while the party with the smaller MAC address can change its NID in a timely manner. In a multi-mode converged network, it can also be adjusted so that the network with the smaller currently assigned TEI (Terminal Equipment Identifier) can complete the network reorganization.
[0004] Bandwidth Coordination: In existing technologies, bandwidth conflict coordination is based on the one-way backoff principle, the first-to-end priority principle, and the small NID priority principle to determine the backoff target. Among them, the one-way backoff principle means that: assuming two CCOAs and B, when A can receive B's inter-network coordination frame, but B cannot receive A's inter-network coordination frame, if A finds that B also declares that it wants to occupy the bandwidth it wants to occupy, then A needs to back off B, B's bandwidth occupation takes effect, and A needs to avoid occupying B's bandwidth in other time slots.
[0005] Wireless channel coordination: In dual-mode communication, in addition to NID and bandwidth coordination mentioned above, there is also a need for wireless channel conflict coordination.
[0006] However, existing technologies require NID coordination to wait until the NIDs in the inter-network coordination frames are consistent before starting; bandwidth coordination requires waiting until the bandwidth duration and offset actually overlap before starting. This post-conflict response mode has inherent problems such as long detection windows and late negotiation triggering in complex multi-site environments. Furthermore, existing technologies determine which party changes the NID based on the priority of the smaller NID or MAC address comparison, placing NID changes (triggering re-networking, causing a network-wide interruption of several to tens of seconds) on an equal footing with bandwidth adjustments (only adjusting the start offset or duration of the TDMA time slot, with minimal cost), without making any cost trade-offs. Summary of the Invention
[0007] To address the shortcomings of existing technologies, this invention provides a method for dynamic coordination and control of NID and bandwidth in low-voltage multi-mode networks, which solves the problems mentioned in the background.
[0008] To achieve the above objectives, the present invention provides the following technical solution: a low-voltage multi-mode network NID and bandwidth dynamic coordination control method, applied to a multi-network coexistence scenario in a low-voltage power line high-speed carrier and high-speed wireless dual-mode communication system, comprising multiple central coordinators (CCOs), each CCO establishing an independent dual-mode communication network, each network having a unique network identifier (NID), and further comprising the following steps: Step S1, Historical Situation Construction: Each CCO maintains a multi-network historical coordination situation table locally, recording the NID Hamming distance and its convergence rate, bandwidth tension, signal coupling strength change gradient, coordination history, and service carrying urgency between its own network and each neighboring network. Step S2, Conflict Prediction: Each CCO calculates conflict early warning indicators based on the historical coordination situation table. : ; in, The Hamming distance convergence rate of NID represents the rate at which the Hamming distance between the NID in this network and the NID in neighboring networks decreases over time. This represents the bandwidth strain level, reflecting the combined effect of historical bandwidth request frequency and actual bandwidth utilization. The gradient represents the change in signal coupling strength between this network and its neighboring networks over time. The urgency of service delivery is calculated by weighting the number of queued frames and the queuing time of each LID priority queue. These are the weighting coefficients for four indicators: NID Hamming distance convergence rate, bandwidth stress, signal coupling strength change gradient, and service carrying urgency. LID, or Link Identifier, is used to identify service priority queues. Values from 0 to 3 represent message priorities, with higher values indicating higher priorities. LID=3 indicates critical services. Step S3, Predictive Trigger: When the conflict warning indicator When the preset warning threshold is exceeded, the coordination process is actively triggered before the NID is completely consistent or the bandwidth time slots are completely overlapping. Step S4, Bandwidth Priority Decision: The CCO constructs a bandwidth priority decision matrix, prioritizing the elimination of conflict impacts by adjusting the bandwidth start offset, bandwidth duration, or TDMA time slot ratio of the network; only when bandwidth dimension adjustment fails to eliminate conflicts will it proceed to NID change decision. Step S5, NID Restricted Change: When an NID change is necessary, it is based on a comparison of the service urgency between this network and neighboring networks. The party deciding which party will change the NID; the party changing the NID executes a restricted reconfiguration mechanism: the designated proxy coordinator (PCO) takes over critical service relay forwarding during the reconfiguration period, sites are re-entering the network in batches according to LID priority, the new NID network inherits the original bandwidth allocation scheme, and the entire reconfiguration process is limited to the reconfiguration time. Completed within the time limit, of which The beacon period is the time interval at which the CCO sends beacon frames. The proxy coordinator (PCO) is the site that relays data between the CCO and the STA or between STAs.
[0009] Furthermore, the NID Hamming distance convergence rate The calculation method is as follows: within multiple consecutive inter-network coordination frame listening periods, calculate the ratio of the difference in Hamming distance between the local network NID and the neighboring network NID to the time difference; when the ratio is negative and the absolute value exceeds the preset convergence threshold, the NID conflict risk is determined to be high.
[0010] Furthermore, the bandwidth stress The calculation method is as follows: the historical bandwidth request frequency, actual bandwidth utilization rate, and historical bandwidth conflict occurrence number of this network and neighboring networks; when the actual bandwidth utilization rate exceeds 80% or the number of bandwidth conflicts exceeds 3 times in a statistical period, the bandwidth tension is judged to be high.
[0011] Furthermore, the urgency of the aforementioned service load The calculation method is as follows: ; in, LID= Priority business queue length The business weight for this priority, satisfying ,and That is, the key business with LID=3 has the highest weight; This represents the average queuing time for this priority level.
[0012] Furthermore, the urgency comparison of the aforementioned services. The calculation and judgment methods are as follows: ; in, The service urgency of this network as defined in step S2 ; Urgency of service carrying capacity for neighboring networks The urgency of this network service carrying capacity Service urgency of neighboring networks All are based on the urgency of network service carrying capacity. The same formula is used to calculate the weighted calculation results of the queued frame count, queued time and service weight of each LID priority queue in this network and the neighboring network, respectively. When comparing the urgency of business operations When the urgency of service carrying in this network is higher than that in the neighboring network, this network keeps its NID unchanged, while the neighboring network changes its NID; when At that time, the neighboring network's service load is more urgent, and this network proactively changes its NID; when When the signal coupling strength is weaker between the network and its neighboring networks, the NID is changed.
[0013] Furthermore, in the restricted reorganization network mechanism, the proxy coordinator (PCO) is designated as follows: the site with the lightest service load and the best signal quality in the network is selected as the PCO; during the reorganization network, the PCO takes over the relay forwarding of critical services with LID=3 to ensure the continuity of critical services during the reorganization network process; sites are re-entered into the network in batches according to LID priority, of which critical service sites with LID=3 complete the network entry within the first beacon period, and ordinary service sites with LID=0~2 gradually enter the network in subsequent beacon periods.
[0014] Furthermore, in step S3, based on the conflict early warning indicators... Compared with the preset warning threshold The multiple relationship is addressed using a graded response: Level 1: When At that time, only adjust the bandwidth start offset or duration; Level Two: When At the same time, while adjusting the bandwidth, a backup NID is pre-selected and notified to all site sites, but the switch is not made immediately; Level 3: When Immediately execute bandwidth priority decisions and NID-restricted changes.
[0015] Furthermore, it also includes: The historical situation construction module is used to maintain a multi-network historical coordinated situation table locally, recording the NID Hamming distance convergence rate. Bandwidth tension Gradient of signal coupling strength change Coordinate historical records and the urgency of business operations. ; The conflict prediction module is used to calculate conflict early warning indicators based on historical coordination status tables. And proactively trigger the coordination process before the actual occurrence of a conflict when the conflict warning indicators exceed the warning threshold; The bandwidth priority decision module is used to construct and execute the bandwidth priority decision matrix, prioritizing the elimination of conflict effects by adjusting bandwidth parameters, and only entering the NID change decision when the bandwidth dimension cannot resolve the issue. The NID restricted change module is used to compare based on the urgency of service load. Determine the party responsible for NID changes and implement the restricted reorganization network mechanism.
[0016] Furthermore, the restricted network reconfiguration mechanism executed by the NID restricted change module includes: designating the Proximity Coordinator (PCO) to take over critical service relay forwarding, re-entering the network in batches according to LID priority, the new NID network inheriting the original bandwidth allocation scheme, and restricting the network reconfiguration process within the network reconfiguration time. Completed within a specified time; the conflict prediction module calculates the conflict early warning indicators. The results are fed back to the historical situation construction module, forming a cyclical feedback mechanism of historical situation collection, conflict prediction, bandwidth priority decision-making, NID limitation change, and situation update; that is, the updated results of conflict early warning indicators are fed back to the historical situation construction module, so that the NID Hamming distance convergence rate, bandwidth tension, signal coupling strength change gradient, and service carrying urgency in the multi-network historical coordination situation table are dynamically updated with the coordination process.
[0017] This invention provides a method for dynamic coordination and control of NID and bandwidth in low-voltage multi-mode networks, which has the following beneficial effects: 1. This low-voltage multi-mode network NID and bandwidth dynamic coordination control method continuously monitors the signal evolution trend and service load changes between networks. It identifies potential risks and proactively triggers the coordination process before conflicts actually occur. This not only eliminates the inherent blind spots in conflict detection but also provides valuable lead time for subsequent coordination decisions. This allows bandwidth priority adjustment to play a full role before conflicts escalate, thereby significantly reducing the probability of triggering high-cost network identifier changes. In other words, predictive triggering provides the necessary time redundancy for the implementation of hierarchical coordination strategies and is the logical starting point for the efficient operation of the entire methodology.
[0018] 2. This low-voltage multi-mode network NID and bandwidth dynamic coordination control method establishes a hierarchical coordination principle that prioritizes bandwidth adjustment and restricts network identifier changes. It resolves resource contention by prioritizing low-cost bandwidth parameter adjustments, and only cautiously initiates network identifier changes when bandwidth measures are truly ineffective. The responsible party for the change is determined based on a comparison of service load pressure, while a restricted reconfiguration mechanism ensures the continuity of critical services during the change process. The effectiveness of this mechanism highly depends on the early warning provided by the preceding prediction stage. It is precisely because of pre-conflict prediction that bandwidth adjustments can be completed calmly within a sufficient time window, avoiding the chain risks brought about by hasty decisions. When network identifier changes are unavoidable, the situational information accumulated by the prediction mechanism provides a reliable basis for accurate comparison of service load, ensuring that change decisions always prioritize the protection of the interests of high-load networks. Attached Figure Description
[0019] Figure 1 This is a schematic diagram of the steps in Embodiment 1 of the present invention. Detailed Implementation
[0020] The embodiments of the present invention will be described in further detail below with reference to the accompanying drawings and examples. The following examples are for illustrative purposes only and should not be construed as limiting the scope of the invention.
[0021] This invention provides a technical solution: a method for dynamic coordination and control of NID and bandwidth in low-voltage multi-mode networks, which is applied to a low-voltage power line high-speed carrier and high-speed wireless dual-mode communication system; Example 1: Detailed implementation of a scenario where two adjacent transformer substations approximate each other's NIDs: The system contains multiple Control Operations (CCOs), each building an independent dual-mode communication network, with each network having a unique NID. When multiple transformer substations are deployed adjacent to each other, the networks built by different CCOs overlap in physical space, and the power line channel and wireless channel are coupled together, requiring inter-network coordination. The initial state is as follows: The physical distance between transformer area A (CCO_A) and transformer area B (CCO_B) is approximately 15 meters. Their initial NIDs are 1001 and 1002, respectively, and their Hamming distance is 1. The network service urgency for transformer area A is... The urgency of B network service carrying capacity Implement according to the following steps (e.g.) Figure 1 (as shown) Step S1, detailed execution of historical situation construction: After CCO_A is powered on, it first receives inter-network coordination frames sent by neighboring networks through the HPLC channel within a neighboring network listening period of less than 10 seconds. The inter-network coordination frames carry key parameters such as duration (a 16-bit field indicating the length of the time slot that this network needs to request, in 1 milliseconds), bandwidth start offset (a 16-bit field indicating the time offset of the start of the next bandwidth time slot, in 1 milliseconds), and the received neighboring network number. Over five consecutive listening cycles, CCO_A parses the received CCO_B inter-network coordination frames and obtains the following situational data: NID Hamming distance convergence rate The Hamming distance was observed to continue converging from its initial value of 1. (The negative sign indicates that the Hamming distance decreases over time; the larger the absolute value, the faster the two NIDs approach each other, and the higher the risk of conflict.) Bandwidth stress (Actual bandwidth utilization exceeds 80%) Signal coupling strength change gradient (Enhanced coupling strength); Business urgency According to the formula Calculation, where The LID value can be 0~3. LID= Priority business queue length The business weight for this priority, satisfying ,and That is, the key business with LID=3 has the highest weight; This represents the average queuing time for this priority level. CCO_A organizes the above information into a local multi-network historical coordination status table; Step S2, detailed execution of conflict prediction: CCO_A calculates conflict early warning indicators. (Weight coefficients are taken as follows) The sum of the four is 1): ; Warning threshold Set it to 10, calculate This falls under Level 3 (Red Alert), requiring immediate implementation of bandwidth priority decisions and NID restriction changes; Step S3, detailed execution of predictive triggering and bandwidth priority decision: CCO_A proactively triggers a red alert response before NIDs are completely identical: First, the first priority scheme of the bandwidth priority decision matrix is executed: the bandwidth of this network is adjusted to start offset by 2ms, and at the same time, a backup NID=5000 is pre-selected and notified to all network sites through beacon frames, but the switch is not performed immediately. After three listening cycles, the Hamming distance converges to 0 (NID collision actually occurs); at this time, CCO_A has completed bandwidth adjustment during the early warning phase, and alternative NIDs have been pre-issued; Step S4, detailed execution of NID restricted changes: Comparison of CCO_A computing service urgency : ; Determined to be more urgent for network service load, the NID remains unchanged, and the neighboring network B changes the NID; CCO_B executes the restricted reconfiguration mechanism: CCO_B selects the site with the lightest service load and best signal quality in the network as PCO; during the network reorganization, the PCO takes over the relay forwarding of critical services with LID=3 (i.e., services with the highest message priority) to ensure the continuity of critical services during the network reorganization process; sites are re-entered into the network in batches according to LID priority, with critical service sites with LID=3 completing the network entry within the first beacon cycle, and ordinary service sites with LID=0~2 gradually entering the network in subsequent beacon cycles; the new NID network directly inherits the original bandwidth allocation scheme to avoid renegotiating bandwidth; The entire reorganization process is limited to The time frame for re-entry (coefficient 3 is selected based on the following: LID=3 critical business sites must complete re-entry within one beacon cycle; LID=0~2 ordinary business sites must complete re-entry in batches within the subsequent two beacon cycles, totaling three beacon cycles; assuming a beacon cycle of 200ms, then...) 600ms); Since CCO_A had completed bandwidth adjustment during the early warning phase and CCO_B implemented the restricted reconfiguration mechanism, critical services on network A remained continuous throughout the coordination process without interruption; critical services on network B remained continuous through PCO takeover. Example 2: Detailed implementation of a bandwidth contention scenario involving three servers: The three stations (A, B, and C) are deployed adjacently, with an initial bandwidth allocation of 8ms for each. Their service urgency levels are respectively... Network A is a high-density residential area, carrying high-frequency data collection services; networks B and C are low-density areas, and the coordination process is as follows: Network A is located in a high-density residential area and carries high-frequency data collection services; Networks B and C are located in low-density areas. Warning threshold =10, calculate It belongs to the third level (red alert), and the bandwidth priority decision should be implemented immediately. According to the bandwidth priority decision matrix evaluation, the conflict can be eliminated by adjusting the bandwidth start offset, so the NID change was not triggered. CCO_A executes the bandwidth priority decision matrix: First, it expands the bandwidth of this network from 8ms to 16ms. Inspired by the "first to end first" principle in existing technology, CCO_A notifies networks B and C through inter-network coordination frames that the bandwidth of network A will be expanded, and requests that the bandwidth of networks B and C begin to be offset and extended accordingly. Because the service urgency of network A is much higher than that of networks B and C (comparison of service urgency). When the bandwidth of networks B and C begins to be offset, networks B and C respond according to the existing single-pass backoff principle: if B can receive the inter-network coordination frame from A but A cannot receive B's, then B backs off from A; after negotiation, the bandwidth offset adjustment of network B is set to 16ms and the bandwidth offset adjustment of network C is set to 24ms. In actual testing, the latency of critical services on network A was reduced from 95ms to 56ms, a reduction of 41%; bandwidth utilization increased from 68% to 92%; no NID changes or network reorganization were triggered throughout the process, and services on networks B and C were not significantly affected; this fully demonstrates the advantages of the bandwidth-first decision-making principle; by flexibly adjusting the bandwidth dimension, conflicts were eliminated, and costly NID changes were avoided.
[0022] Example 3, detailed execution flow of the module: Historical situation construction module: After power-on, within a neighbor network monitoring period of less than 10 seconds, it receives inter-network coordination frames from neighbor networks through the HPLC physical layer, and parses fields such as duration, bandwidth start offset, and neighbor network number; it receives wireless beacons from neighbor networks through the HRF physical layer; it calculates signal coupling strength by measuring RSSI and SNR through the physical layer; it extracts the queued frame number of each LID priority queue from the communication success rate reporting messages collected within the routing period; and it writes the above information into the local multi-network historical coordination situation table, updating the corresponding entries each time a new inter-network coordination frame is received. Conflict prediction module: periodically triggered by a timer (e.g., once per beacon cycle), it calculates conflict early warning indicators based on historical coordination status tables. The calculation formula is: ; Bandwidth Priority Decision Module: Upon receiving the trigger signal from the conflict prediction module, it constructs a bandwidth priority decision matrix. First, it checks whether the conflict can be eliminated by adjusting the bandwidth start offset, bandwidth duration, or TDMA time slot ratio (first priority). If the conflict cannot be eliminated by adjusting the bandwidth dimension, it calculates the service carrying urgency comparison. Based on the urgency of business operations The value determines whether the NID is changed by the local network or by requesting a neighboring network, and the decision result is notified to the NID restricted change module. NID Restricted Change Module: When the decision result is to change the NID of this network, a restricted reconfiguration mechanism is executed, performing the following operations in sequence: First, a proxy coordinator (PCO) is designated; then, the PCO takes over the relay forwarding of critical services during the reconfiguration period; next, sites are re-entered into the network in batches according to LID priority; subsequently, the new NID network inherits the original bandwidth allocation scheme; finally, the entire reconfiguration process is restricted to... Completed within the specified timeframe, after the network reorganization is finished, the results, including the new NID, new bandwidth allocation scheme, and new channel quality, will be fed back to the historical situation construction module to update the local multi-network historical coordination situation table, forming a cyclical feedback mechanism (i.e., conflict early warning indicators). The updated results are fed back to the historical situation construction module, so that the NID Hamming distance convergence rate, bandwidth tension, signal coupling strength change gradient, and service carrying urgency in the multi-network historical coordination situation table are dynamically updated as the coordination process progresses.
[0023] In high-coupling scenarios, i.e., when the signal coupling strength > 0.8 (i.e., the two networks are physically very close and interference is severe), the warning threshold is further tightened to 5; the conflict prediction module assigns a higher actual weight to the gradient term of signal coupling change in the joint cost function calculation (through...). (Dynamic upscaling implementation), prioritizing the elimination of channel conflicts; When the number of neighboring networks in the situation table exceeds 5, the neighboring networks are first sorted by signal coupling strength, and strict early warning calculations are only performed for strongly interfering neighbors; for weakly interfering neighbors, it is only necessary to ensure that their NID Hamming distance is ≥4 and their bandwidths do not overlap, in order to reduce computational complexity. During the restricted reconfiguration process, if the CCO receives a new inter-network coordination frame, indicating the presence of an unexpected neighbor network, the CCO will pause the current reconfiguration process and re-execute situational awareness and conflict prediction. If the new decision does not conflict with the ongoing reconfiguration process, the reconfiguration will be merged in a new transition window. If there is a conflict, the current reconfiguration will be canceled and restarted according to the new decision.
[0024] In summary, this method for dynamic coordination and control of NID and bandwidth in low-voltage multi-mode networks proposes to proactively predict conflict risks and trigger coordination in advance by analyzing historical coordination trends and service urgency before NIDs become completely consistent and bandwidths completely overlap. Specifically: Each CCO maintains a multi-network historical coordination status table locally, recording not only real-time parameters such as the NID, bandwidth, and channel of the current neighboring networks, but also: NID conflict proximity (the Hamming distance between the NID of this network and the NID of each neighboring network, and the trend of this distance changing over time), bandwidth tension (historical bandwidth request frequency, actual bandwidth utilization, and number of bandwidth conflicts of this network and neighboring networks), signal coupling evolution (historical RSSI / SNR curves between this network and neighboring networks, determining whether the coupling strength is increasing or decreasing), coordination history (timestamps and triggering reasons for each NID change, bandwidth adjustment, and channel switching of this network), and service carrying urgency (queuing frame count, queuing time, and proportion of critical services in each LID priority queue of this network). LID stands for Link Identifier, with values ranging from 0 to 3 indicating message priority. Higher values indicate higher priority, and LID=3 corresponds to critical services. Critical services refer to the highest priority service categories in dual-mode communication networks, typically including critical service messages such as electricity information collection and power distribution automation. The CCO calculates conflict warning indicators based on historical coordination situation tables. When these indicators exceed a preset warning threshold, the CCO proactively triggers the coordination process before the actual conflict occurs. Different levels of predictive response are adopted based on the multiple relationship between the conflict warning indicators and the warning threshold: Yellow Warning (…) When an orange alert is triggered, only the bandwidth shift or duration is adjusted. When a red alert is triggered, a backup NID is pre-selected and all sites are notified, but the switch is not performed immediately; The coordination decision should be executed immediately when the above multiplier (1.5 times, 3 times) is set. The multiplier can be adjusted adaptively according to the network scale, channel quality and service level requirements on site, but once set, it will remain stable during system operation.
[0025] This invention also proposes bandwidth-first and NID-limited bandwidth-first and NID-limited methods, specifically: When a conflict is predicted or actually occurs, the CCO first constructs a bandwidth priority decision matrix: it prioritizes eliminating the impact of the conflict by adjusting the bandwidth start offset, bandwidth duration, or TDMA time slot ratio of the network; only when bandwidth dimension adjustment cannot eliminate the conflict will it proceed to NID change decision. When an NID change is necessary, the decision of which network should change the NID is based on a comparison of the service urgency between the local network and the neighboring network. The service urgency of the local network and the neighboring network are calculated using the same formula, and are respectively weighted calculation results of the queued frames, queued time and service weight of each LID priority queue of the local network and the neighboring network. When comparing the urgency of business operations When the threshold is >1, the network service load urgency is higher, and the NID is changed by the neighboring network; when When the value is less than 1, the NID is changed proactively by this network; when the value is approximately 1, the NID is changed by the party with weaker signal coupling strength. When the signal coupling strength is approximately 1, the NID is changed by the party with weaker signal coupling. The designated proxy coordinator PCO (the site that relays data between the CCO and STA or between STAs) takes over the relay forwarding of critical services during the network reorganization period. Sites re-enter the network in batches according to LID priority. The new NID network inherits the original bandwidth allocation scheme. The entire network reorganization process is limited to the network reorganization time. Complete within the specified time.
[0026] By continuously monitoring the evolution trends of signals and changes in service load between networks, potential risks can be identified and coordination processes can be proactively triggered before conflicts actually occur. This not only eliminates the inherent blind spots in conflict detection but also provides valuable lead time for subsequent coordination decisions. This allows bandwidth priority adjustments to play a full role before conflicts escalate, thereby significantly reducing the probability of triggering high-cost network identifier changes. In other words, predictive triggering provides the necessary time redundancy for the implementation of hierarchical coordination strategies and is the logical starting point for the efficient operation of the entire methodology.
[0027] A hierarchical coordination principle was established, prioritizing bandwidth adjustments and restricting network identifier changes. This approach resolves resource contention by prioritizing low-cost bandwidth parameter adjustments, and only cautiously initiates network identifier changes when bandwidth measures prove ineffective. The responsible party for the change is determined based on a comparison of service load pressure, while a restricted network reconfiguration mechanism ensures the continuity of critical services during the change process. The effectiveness of this mechanism heavily relies on early warnings provided by the preceding forecasting phase. It is precisely because of pre-conflict forecasting that bandwidth adjustments can be completed calmly within a sufficient time window, avoiding the chain of risks brought about by hasty decisions. When network identifier changes are unavoidable, the situational information accumulated by the forecasting mechanism provides a reliable basis for accurate comparison of service load, ensuring that change decisions always prioritize the protection of the interests of high-load networks, achieving a shift from passive response to proactive governance.
[0028] The embodiments of the present invention are given for illustrative and descriptive purposes only, and are not intended to be exhaustive or to limit the invention to the forms disclosed. Many modifications and variations will be apparent to those skilled in the art. The embodiments were chosen and described in order to better illustrate the principles and practical application of the invention, and to enable those skilled in the art to understand the invention and to design various embodiments with various modifications suitable for a particular purpose.
Claims
1. A method for dynamic coordination and control of NID and bandwidth in low-voltage multi-mode networks, applied to multi-network coexistence scenarios in low-voltage power line high-speed carrier and high-speed wireless dual-mode communication systems, comprising multiple central coordinators (CCOs), each CCO establishing an independent dual-mode communication network, each network having a unique network identifier (NID), characterized in that: It also includes the following steps: Step S1, Historical Situation Construction: Each CCO maintains a multi-network historical coordination situation table locally, recording the NID Hamming distance and its convergence rate, bandwidth tension, signal coupling strength change gradient, coordination history, and service carrying urgency between its own network and each neighboring network. Step S2, Conflict Prediction: Each CCO calculates conflict early warning indicators based on the historical coordination situation table. : ; in, The Hamming distance convergence rate of NID represents the rate at which the Hamming distance between the NID in this network and the NID in neighboring networks decreases over time. This represents the bandwidth strain level, reflecting the combined effect of historical bandwidth request frequency and actual bandwidth utilization. The gradient represents the change in signal coupling strength between this network and its neighboring networks over time. The urgency of service delivery is calculated by weighting the number of queued frames and the queuing time of each LID priority queue. These are the weighting coefficients for four indicators: NID Hamming distance convergence rate, bandwidth stress, signal coupling strength change gradient, and service carrying urgency. LID, or Link Identifier, is used to identify service priority queues. Values from 0 to 3 represent message priorities, with higher values indicating higher priorities. LID=3 indicates critical services. Step S3, Predictive Trigger: When the conflict warning indicator When the preset warning threshold is exceeded, the coordination process is actively triggered before the NID is completely consistent or the bandwidth time slots are completely overlapping. Step S4, Bandwidth Priority Decision: The CCO constructs a bandwidth priority decision matrix, prioritizing the elimination of conflict impacts by adjusting the bandwidth start offset, bandwidth duration, or TDMA time slot ratio of the network; only when bandwidth dimension adjustment fails to eliminate conflicts will it proceed to NID change decision. Step S5, NID Restricted Change: When an NID change is necessary, it is based on a comparison of the service urgency between this network and neighboring networks. The party deciding which party will change the NID; the party changing the NID executes a restricted reconfiguration mechanism: the designated proxy coordinator (PCO) takes over critical service relay forwarding during the reconfiguration period, sites are re-entering the network in batches according to LID priority, the new NID network inherits the original bandwidth allocation scheme, and the entire reconfiguration process is limited to the reconfiguration time. Completed within the time limit, of which The beacon period is the time interval at which the CCO sends beacon frames. The proxy coordinator (PCO) is the site that relays data between the CCO and the STA or between STAs.
2. The method for dynamic coordination and control of NID and bandwidth in a low-voltage multi-mode network according to claim 1, characterized in that: The NID Hamming distance convergence rate The calculation method is as follows: within multiple consecutive inter-network coordination frame listening periods, calculate the ratio of the difference in Hamming distance between the local network NID and the neighboring network NID to the time difference; when the ratio is negative and the absolute value exceeds the preset convergence threshold, the NID conflict risk is determined to be high.
3. The method for dynamic coordination and control of NID and bandwidth in a low-voltage multi-mode network according to claim 1, characterized in that: The bandwidth tension The calculation method is as follows: the historical bandwidth request frequency, actual bandwidth utilization rate, and historical bandwidth conflict occurrence number of this network and neighboring networks; when the actual bandwidth utilization rate exceeds 80% or the number of bandwidth conflicts exceeds 3 times in a statistical period, the bandwidth tension is judged to be high.
4. The method for dynamic coordination and control of NID and bandwidth in a low-voltage multi-mode network according to claim 1, characterized in that: The urgency of the service The calculation method is as follows: ; in, LID= Priority business queue length The business weight for this priority, satisfying ,and That is, the key business with LID=3 has the highest weight; This represents the average queuing time for this priority level.
5. The method for dynamic coordination and control of NID and bandwidth in a low-voltage multi-mode network according to claim 1, characterized in that: Comparison of the urgency of the aforementioned services The calculation and judgment methods are as follows: ; in, The service urgency of this network as defined in step S2 ; Urgency of service carrying capacity for neighboring networks The urgency of this network service carrying capacity Service urgency of neighboring networks All are based on the urgency of network service carrying capacity. The same formula is used to calculate the weighted calculation results of the queued frame count, queued time and service weight of each LID priority queue in this network and the neighboring network, respectively. When comparing the urgency of business operations When the urgency of service carrying in this network is higher than that in the neighboring network, this network keeps its NID unchanged, while the neighboring network changes its NID; when At that time, the neighboring network's service load is more urgent, and this network proactively changes its NID; when When the signal coupling strength between the local network and its neighboring networks is weaker, the NID is changed by the latter.
6. The method for dynamic coordination and control of NID and bandwidth in a low-voltage multi-mode network according to claim 1, characterized in that: In the restricted reorganization network mechanism, the proxy coordinator (PCO) is designated as follows: the site with the lightest service load and the best signal quality in the network is selected as the PCO; during the reorganization network, the PCO takes over the relay forwarding of critical services with LID=3 to ensure the continuity of critical services during the reorganization network process; sites are re-entered into the network in batches according to LID priority, of which critical service sites with LID=3 complete the network entry within the first beacon period, and ordinary service sites with LID=0~2 gradually enter the network in subsequent beacon periods.
7. The method for dynamic coordination and control of NID and bandwidth in a low-voltage multi-mode network according to claim 1, characterized in that: In step S3, based on the conflict early warning indicators Compared with the preset warning threshold The multiple relationship is addressed using a graded response: Level 1: When At that time, only adjust the bandwidth start offset or duration; Level Two: When At the same time, while adjusting the bandwidth, a backup NID is pre-selected and notified to all site sites, but the switch is not made immediately; Level 3: When Immediately execute bandwidth priority decisions and NID-restricted changes.
8. The method for dynamic coordination and control of NID and bandwidth in a low-voltage multi-mode network according to claim 1, characterized in that: Also includes: The historical situation construction module is used to maintain a multi-network historical coordinated situation table locally, recording the NID Hamming distance convergence rate. Bandwidth tension Gradient of signal coupling strength change Coordinate historical records and the urgency of business operations. ; The conflict prediction module is used to calculate conflict early warning indicators based on historical coordination status tables. And proactively trigger the coordination process before the actual occurrence of a conflict when the conflict warning indicators exceed the warning threshold; The bandwidth priority decision module is used to construct and execute the bandwidth priority decision matrix, prioritizing the elimination of conflict effects by adjusting bandwidth parameters, and only entering the NID change decision when the bandwidth dimension cannot resolve the issue. The NID restricted change module is used to compare based on the urgency of service load. Determine the party responsible for NID changes and implement the restricted reorganization network mechanism.
9. The method for dynamic coordination and control of NID and bandwidth in a low-voltage multi-mode network according to claim 8, characterized in that: The restricted network reconfiguration mechanism executed by the NID restricted change module includes: designated agent coordinator (PCO) taking over critical service relay forwarding, sites re-entering the network in batches according to LID priority, the new NID network inheriting the original bandwidth allocation scheme, and the network reconfiguration process being limited to the network reconfiguration time. Completed within a specified time; the conflict prediction module calculates the conflict early warning indicators. The results are fed back to the historical situation construction module, forming a cyclical feedback mechanism of historical situation collection, conflict prediction, bandwidth priority decision-making, NID limitation change, and situation update; that is, the updated results of conflict early warning indicators are fed back to the historical situation construction module, so that the NID Hamming distance convergence rate, bandwidth tension, signal coupling strength change gradient, and service carrying urgency in the multi-network historical coordination situation table are dynamically updated with the coordination process.
