Intelligent configuration management method and system for distributed network topology

Abstract

The invention discloses an intelligent configuration management method and system for distributed network topology, and relates to the technical field of distributed network configuration management. The method comprises the following steps: dynamically calculating a configuration backup weight Q of each device according to a current configuration management requirement, an operation state parameter of each device and a congestion state from each device to an uplink network link; the device with the high configuration backup weight Q serves as a backup device, configuration backup operation of the management system is executed, and then the management system is started; when the slave device executes the management task, if a task initiator has configuration backup, local task processing is carried out; if the target executor does not have the configuration backup, selecting a proper device as an agent to execute the task according to the communication cost between the task initiator and the target executor and the running state of the target executor; and when the main gateway fails, selecting the equipment with the maximum configuration backup weight Q as the main gateway of the proxy. According to the invention, the efficiency and accuracy of network configuration are obviously improved.

Description

Technical Field

[0001] This invention relates to the field of distributed network configuration management technology, and in particular to an intelligent configuration management method and system for distributed network topology. Background Technology

[0002] With the continuous development of Internet technology, network application demands are becoming increasingly diversified, especially in enterprise-level networks and high-performance computing environments, where the requirements for network bandwidth and transmission quality are constantly increasing. To meet the needs of high-speed, high-capacity data transmission, new network architectures have emerged, among which FTTR (Fiber to the Room) technology, as an innovative fiber-to-the-room solution, has gradually attracted widespread attention.

[0003] FTTR technology deploys fiber optic cables within a building, directly connecting each room to the fiber, replacing traditional copper cabling and achieving higher transmission rates and lower signal loss. Compared to traditional FTTH (Fiber to the Home) technology, FTTR offers significant advantages in indoor network deployment, enabling each room in the building to enjoy independent high-speed fiber optic network service, thereby improving overall network performance.

[0004] However, despite the enormous potential of FTTR technology in providing high-speed network connectivity, current implementations still face several challenges, particularly in network topology and configuration information management. Existing FTTR systems primarily focus on fiber optic cabling and signal transmission, while the needs for equipment management, network topology configuration, and configuration backup remain largely unresolved.

[0005] Inter-device resource scheduling and load balancing: In an FTTR network environment, device load and bandwidth utilization fluctuate significantly across different time periods and rooms. How to dynamically adjust device tasks and resource allocation to ensure efficient network operation has become a pressing challenge for FTTR technology.

[0006] Network configuration management complexity: With the deployment of FTTR systems, the number and types of network devices are rapidly increasing, making efficient management and configuration of these devices a major challenge. Traditional configuration management methods often rely on manual operation or tedious manual configuration, which is prone to errors and leads to increased management costs.

[0007] Real-time performance and consistency of fiber optic network configuration: In FTTR networks, the stability of fiber optic connections and the quality of data transmission are highly dependent on the precise configuration of the network topology. However, existing distributed configuration management systems often struggle to ensure the real-time synchronization and consistency of network configuration data, especially when devices join or leave the network, or when failures occur. Configuration updates and backups may be delayed or inconsistent, affecting the overall reliability of the system.

[0008] Insufficient fault tolerance mechanisms: Although FTTR technology provides high-performance network connectivity, failures of the primary gateway or core nodes in the network topology can trigger large-scale network outages. Current FTTR systems generally lack intelligent fault tolerance mechanisms, failing to quickly switch to backup equipment or perform repair operations in the event of equipment failure, thus leading to network service interruptions or quality degradation.

[0009] Therefore, how to achieve more efficient distributed configuration management, optimize resource scheduling, ensure configuration consistency and real-time performance, and enhance fault tolerance mechanisms in FTTR technology to improve network stability and reliability has become a key issue in the development of FTTR systems. Summary of the Invention

[0010] The technical problem to be solved by the present invention is to provide an intelligent configuration management method and system for distributed network topology, which can automatically adjust the task allocation and configuration backup of devices according to the operating status of devices, network environment and bandwidth requirements, thereby significantly improving the efficiency and accuracy of network configuration.

[0011] In a first aspect, the present invention provides an intelligent configuration management method for distributed network topology, comprising: The configuration backup weight Q of each device is dynamically calculated based on the current configuration management requirements, the operating status parameters of each device, and the congestion status of the uplink network link of each device; the configuration backup weight Q of the main gateway is always the maximum value. Devices with a backup weight Q higher than the first preset value are designated as backupable devices. After performing the configuration backup operation of the management system, the management system is started. When executing management tasks from a device, if the task initiator has a configuration backup, the task is processed locally; if it does not have a configuration backup, a suitable device is selected as a proxy to execute the task based on the communication cost between the task initiator and the target executor and the target executor's own operating status. When the main gateway fails, the device with the highest backup weight Q is selected as the proxy's main gateway.

[0012] Furthermore, when the configured backup weight Q is higher than the first preset value... x If the proportion of devices with a value of 0 approaches 0, then at least the second preset value must be guaranteed. y One number of slave devices have configuration backups; when the proportion of devices with a configuration backup weight Q higher than the first preset value approaches 1, at most the third preset value is selected. y Two devices have configuration backups.

[0013] Furthermore, the first preset value x 0. Second preset value y 1. Third preset value y2. Based on the regression equation, the expected value is predicted. The initial dataset for establishing the regression equation is established by the supply and demand relationship in the current actual deployment environment. The supply and demand relationship includes: the total number of devices in the actual deployment environment β1, the overall failure rate of devices β2, the proportion of devices used for network management β3, the proportion of devices under high load for a long time β4, and the time period when the network environment is under high load β5.

[0014] Furthermore, selecting a suitable device as the proxy to execute the task specifically includes: calculating the selection bias P, and then selecting the device with the largest P value as the proxy to execute the task; the formula for calculating the selection bias P is as follows: ; Where Q represents the configuration backup weight, and F... NetTrans F represents the latency of information exchange between the task initiating device and the task executing device, as well as the number of hops in the network topology. DevStatus This indicates the remaining CPU and memory usage of the task executor's device when the task is selected. .

[0015] Furthermore, each device with a configuration backup maintained by the management system maintains a management table, including key-value pairs of configuration copy content (value) and copy version number (N). The version number (N) of each backup device is periodically synchronized to ensure that all devices with configuration backups have the same and up-to-date configuration version as the main gateway. When a task is initiated on a device and the target executor device is determined through the above calculations, the device sends a configuration version information request to the main gateway before executing the task, selecting the newest configuration information to execute the task. After the task is completed, the configuration backup version number is updated and the latest configuration information is sent to the main gateway.

[0016] Secondly, the present invention provides an intelligent configuration management system for distributed network topology, comprising: The configuration weight determination module is used to dynamically calculate the configuration backup weight Q of each device based on the current configuration management requirements, the operating status parameters of each device, and the congestion status of the uplink network link of each device; the configuration backup weight Q of the main gateway is always the maximum value; The configuration backup module is used to designate devices with a configuration backup weight Q higher than the first preset value as backupable devices, perform configuration backup operations on the management system, and then start the management system. The task execution module is used to perform local task processing when a slave device executes a management task. If the task initiator has a configuration backup, it will perform the task locally. If it does not have a configuration backup, it will select a suitable device as a proxy to execute the task based on the communication cost between the task initiator and the target executor and the target executor's own operating status. The main gateway switching module is used to select the device with the highest configured backup weight Q as the proxy's main gateway when the main gateway fails.

[0017] Furthermore, the configuration backup module is also used to handle situations where the configuration backup weight Q is higher than a first preset value. x If the proportion of devices with a value of 0 approaches 0, then at least the second preset value must be guaranteed. y One number of slave devices have configuration backups; when the proportion of devices with a configuration backup weight Q higher than the first preset value approaches 1, at most the third preset value is selected. y Two devices have configuration backups.

[0018] Furthermore, the first preset value x 0. Second preset value y 1. Third preset value y 2. Based on the regression equation, the expected value is predicted. The initial dataset for establishing the regression equation is established by the supply and demand relationship in the current actual deployment environment. The supply and demand relationship includes: the total number of devices in the actual deployment environment β1, the overall failure rate of devices β2, the proportion of devices used for network management β3, the proportion of devices under high load for a long time β4, and the time period when the network environment is under high load β5.

[0019] Furthermore, selecting a suitable device as the proxy to execute the task specifically includes: calculating the selection bias P, and then selecting the device with the largest P value as the proxy to execute the task; the formula for calculating the selection bias P is as follows: ; Where Q represents the configuration backup weight, and F... NetTrans F represents the latency of information exchange between the task initiating device and the task executing device, as well as the number of hops in the network topology. DevStatus This indicates the remaining CPU and memory usage of the task executor's device when the task is selected. .

[0020] Furthermore, the configuration weight determination module is also used to maintain a management table for each device with configuration backups managed by the system, including key-value pairs of configuration copy content value and copy version number N, and periodically synchronize the version number N of each backup device copy to keep the configuration version of all devices with configuration backups consistent with and up-to-date with the main gateway; when a task is initiated on a device and the target executor device is determined through the above calculations, the device sends a configuration version information request to the main gateway before executing the task, and selects the newest configuration information to execute the task; after the task is completed, the configuration backup version number is updated and the latest configuration information is sent to the main gateway.

[0021] The technical solutions provided in the embodiments of the present invention have at least the following technical effects: 1. Optimize network configuration management to improve work efficiency: This invention, by introducing a resilient network regression model and a dynamic task scheduling mechanism, can automatically adjust device task allocation and configuration backup based on device operating status, network environment, and bandwidth requirements. This automated and intelligent management approach reduces manual operation and errors, significantly improving the efficiency and accuracy of network configuration.

[0022] 2. Ensure the real-time nature and consistency of configuration data: This invention employs the Paxos algorithm to synchronize and manage device configuration versions, ensuring that network configuration information is updated promptly when devices join, leave, or fail, thus avoiding the risks of data inconsistency and obsolescence. This consistency guarantee mechanism improves system stability during dynamic changes, ensuring more reliable configuration updates and backup operations.

[0023] 3. Enhance the intelligence and flexibility of network resource scheduling.

[0024] This invention intelligently assesses device load, network status, and task execution capabilities, automatically selecting the most suitable device to perform management tasks and optimizing resource scheduling. This avoids performance bottlenecks and resource waste caused by uneven device load or unreasonable task allocation in traditional network management systems, thus improving the overall network operating efficiency.

[0025] 4. Improve system fault tolerance and ensure high availability.

[0026] This invention incorporates an intelligent fault-tolerance mechanism. When the primary gateway or backup node fails, it automatically selects a device with higher weight to perform tasks or restore services, thereby ensuring continuous network operation and high availability. Even in the event of device failure, the system can quickly switch over and maintain network stability, reducing service interruption time caused by device failure.

[0027] 5. Supports rapid deployment and efficient operation of FTTR technology.

[0028] This invention is specifically optimized for FTTR (Fiber to the Room) network architecture, enabling rapid deployment, dynamic adjustment, and efficient management of fiber optic connections in high-density equipment environments. By applying the distributed configuration management scheme of this invention, users can enjoy stable and high-speed network services in each room, significantly improving network performance and user experience.

[0029] 6. Reduce system maintenance costs and lower operational risks.

[0030] This invention simplifies the complexities of traditional distributed network management, making the management of network devices and configurations more automated and visualized, and reducing the need for manual intervention and maintenance. Intelligent configuration backup and fault recovery mechanisms can efficiently handle emergencies, reducing operational costs and risks caused by human error or equipment failure.

[0031] In summary, this invention, through its innovative distributed network topology configuration information management method, not only effectively solves the problems of insufficient configuration synchronization, resource scheduling, and fault tolerance in existing technologies, but also significantly improves the application effect of FTTR technology in high-performance network environments, greatly enhancing the stability, reliability, and scalability of network systems.

[0032] The above description is merely an overview of the technical solution of the present invention. In order to better understand the technical means of the present invention and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of the present invention more apparent and understandable, specific embodiments of the present invention are described below. Attached Figure Description

[0033] The present invention will be further described below with reference to the accompanying drawings and embodiments.

[0034] Figure 1 This is a flowchart illustrating the overall process of the method in Embodiment 1 of the present invention. Figure 2 This is a schematic diagram of the main table entries maintained by the system in Embodiment 1 of the present invention; Figure 3 This is a schematic diagram of the transaction execution process in Embodiment 1 of the present invention; Figure 4 This is a schematic diagram of the consistency logic in Embodiment 1 of the present invention; Figure 5 This is a schematic diagram of the execution framework in Embodiment 1 of the present invention; Figure 6 This is a schematic diagram of the system structure in Embodiment 2 of the present invention. Detailed Implementation

[0035] This invention provides an intelligent configuration management method and system for distributed network topology, which can automatically adjust device task allocation and configuration backup according to device operating status, network environment and bandwidth requirements, significantly improving the efficiency and accuracy of network configuration.

[0036] The overall concept of the technical solutions in the embodiments of the present invention is as follows: Intelligent task scheduling mechanism This invention proposes a configuration management system based on distributed network topology, specifically optimized for FTTR (Fiber to the Room) network environments. This system enables efficient management of network devices, ensures real-time synchronization and consistency of configuration data, and achieves intelligent resource scheduling, improving network performance and stability while avoiding resource waste and performance bottlenecks.

[0037] Real-time configuration synchronization and consistency guarantee By introducing a resilient network regression model and a dynamic task scheduling mechanism, it is possible to monitor device operating status, bandwidth requirements, and network environment in real time, and automatically optimize device task allocation and resource scheduling. This intelligent mechanism improves network configuration efficiency and reduces human error.

[0038] Fault tolerance mechanisms and high availability design An intelligent fault-tolerance mechanism is designed so that when the main gateway or core node fails, the system can automatically select a backup device to perform the task, ensuring the continuity and high availability of network services and minimizing the service interruption time caused by the failure.

[0039] Highly efficient support for rapid deployment of FTTR environments The FTTR technology has been specifically optimized to enable rapid deployment and efficient management of fiber optic connections in high-density equipment environments. Through an optimized distributed configuration management approach, network performance and user experience are significantly improved.

[0040] Automated and visualized network maintenance management The automated and visual management interface simplifies the complexity of traditional network management, reduces the need for manual intervention, and lowers operation and maintenance costs and risks. Meanwhile, intelligent configuration backup and fault recovery mechanisms further improve system maintenance efficiency and fault handling capabilities.

[0041] Example 1 This embodiment provides an intelligent configuration management method for distributed network topology, such as... Figure 1 As shown, it includes: S1. Dynamically calculate the configuration backup weight Q of each device based on the current configuration management requirements, the operating status parameters of each device, and the congestion status of the uplink network link of each device.

[0042] The backup weight Q can be calculated using the following formula, and then normalized: Q=a0F TotalReq +a1F DevStatus +a2F NetCongestion a0 + a1 + a2 = 100; Among them, equipment configuration management requirement F TotalReqThis indicates the device's tendency to be included in the management system, i.e., whether the device needs to be included and the expected value for inclusion; device operating status parameter F DevStatus This parameter represents a multi-factor influence on the proportion of current device resources used to execute business functions; in other words, it reflects how much available resource the device has left to run the system. It also represents the congestion status F of the link between the device and the uplink edge OLT network. NetCongestion This represents the cost of network communication between the entire system and the outside world, assuming the device is managed and used as a backup controller. The proportions of a0, a1, and a2 can be adjusted according to the overall environmental conditions; a suggested proportion is 20%, 50%, and 30%.

[0043] It should be noted that since the entire invention logic is used to back up the entire network environment topology configuration information stored by the main gateway, the main gateway weight is always the maximum value of 1.

[0044] All devices and their weights Q are stored as key-value pairs in a maintainable data table for planning and management. This table entry is independent of backup configurations, such as... Figure 2 As shown.

[0045] S2. Select devices with a backup weight Q higher than the first preset value as backupable devices, perform the configuration backup operation of the management system, and then start the management system.

[0046] When the device weight is higher than the first preset value x If the device weight is 0, it is considered to meet the conditions for configuration backup and expected management operations, and the backup operation and system startup will be performed; when the device weight is lower than the first preset value... x If the value is 0, it is considered that the system no longer has the ability to maintain configuration backup and management. The system will then perform configuration backup cleanup and temporarily shut down to prioritize business performance requirements.

[0047] In extreme cases, when the configured backup weight Q is higher than the first preset value... x If the proportion of devices with a value of 0 approaches 0, then at least the second preset value must be guaranteed. y One number of slave devices have configuration backups, and the selection of devices follows a selection rule that is directly proportional to the device weight Q. Conversely, if the proportion of devices with a configuration backup weight Q higher than the first preset value approaches 1, indicating that the overall environment is in a state of relatively low business demand, then at most the third preset value will be selected. y Two devices have configuration backups, and the selection of devices follows a selection rule that is proportional to the device weight Q.

[0048] The aforementioned first preset value x 0. Second preset value y 1. Third preset value y2. Based on the regression equation, predict the expected value to make reasonable judgments about the future network environment. The initial dataset for establishing the regression equation is built using the supply and demand relationship in the current actual deployment environment, so that the established regression equation is as realistic as possible. The supply and demand relationship includes, but is not limited to: the total number of devices in the actual deployment environment β1, the overall failure rate of devices β2, the proportion of devices used for network management β3, the proportion of devices under high load for a long period of time β4, and the time period of high load in the network environment β5.

[0049] As can be seen from the above, the first, second, and third preset values ​​are influenced by several factors with high dimensionality. These factors are highly correlated and exhibit multicollinearity. Furthermore, due to the presence of redundant features in actual deployments, the ElasticNet Regression model is used to calculate the expected values ​​of these preset values, specifically using the following formula: ; in, For the first Each feature corresponds to a regression coefficient that minimizes the elasticity regression loss function, calculated in a specific way; For the test data The sample at the th Values ​​on each feature; The number of features refers to the number of influencing factors.

[0050] The elastic regression loss function is: ; In the elastic regression model, for the specific approach described above, this embodiment uses cross-validation to determine the optimal set of regression coefficients β0, β1, ..., β... p The optimal set of parameters λ and α is determined, and the selection is aided by a learning curve.

[0051] This concludes the device node selection process for data backup and configuration management.

[0052] S3. When executing management tasks from a device, if the task initiator has a configuration backup, the task is processed locally; otherwise, a suitable device is selected as the proxy to execute the task based on the communication cost between the task initiator and the target executor and the target executor's own operating status. This allows the system to determine the appropriate device to execute a management task. Figure 3 As shown.

[0053] Preferably, selecting a suitable device as the proxy for task execution specifically includes: calculating the selection bias P, and then selecting the device with the largest P value as the proxy for task execution; the formula for calculating the selection bias P is as follows: ; Where Q represents the configured backup weight, and F represents the communication cost. NetTrans This represents the latency of information exchange between the task initiating device and the task executing device, as well as the number of hops in the network topology, and the target executor's own running state F. DevStatus This indicates the remaining CPU and memory usage of the task executor's device when the task is selected. .

[0054] Calculation results Normalization was performed. The proportions can be adjusted according to the overall state of the environment. One reference proportion is 20, 40, 40.

[0055] For the selection preference P, the device corresponding to the maximum value is selected first as the target executor chosen by the task initiator to perform the configuration management task.

[0056] S4. When the main gateway fails, select the device with the highest backup weight Q as the proxy's main gateway.

[0057] System Consistency: To ensure configuration consistency across all backup devices, this embodiment employs a local logic based on the Paxos algorithm, such as... Figure 4 As shown, each device with a configuration backup maintains a management table containing key-value pairs: configuration copy content (value) and copy version number (N). Based on the Paxos algorithm, the version number (N) of each backup device's copy is periodically synchronized to ensure that all devices have the same and up-to-date configuration version as the main gateway (the version number increments, so a larger number indicates a newer configuration).

[0058] Unlike the Paxos algorithm, when a network administrator initiates a task on a device and determines the target executor device through the above calculations, the device will proactively initiate a configuration backup check before executing the task: the device will send a configuration version information request to the main gateway, and after receiving the configuration version information, it will compare the size relationship between the local configuration information version number and the obtained configuration information version number and select the larger configuration information to execute the task.

[0059] After the task is completed, the configuration backup version number of the executor device is updated to N+1=N. It then proactively sends the latest configuration information to the main gateway, which then synchronously updates its configuration. Unlike the Paxos algorithm, which initiates synchronization across all backup devices in the entire environment, this process waits for periodic processing logic to synchronize all backup devices, further reducing performance overhead.

[0060] Please note that the synchronization of network topology configuration information is performed between devices selected as backup nodes to improve the security of configuration information storage. In contrast, the management entries related to the management system maintenance involved in this invention are performed between all devices to improve the portability of configuration management. All synchronization operations involve both of these information types.

[0061] When the main gateway in the environment malfunctions and becomes unusable, the backup device with the highest weight will be selected as the proxy main gateway to perform the aforementioned main gateway role operations.

[0062] The following examples from practical use provide a simple explanation of the entire system. Please refer to them. Figure 5 .

[0063] 1. How to determine whether backup is needed and how to synchronize backups when a new device is connected? Prerequisites: There are already devices running in the network environment, and the system contains backup configuration information for these devices.

[0064] The new device has successfully connected to the FTTR network and is able to communicate with the system.

[0065] Use case steps: Preliminary verification during device connection: The system received information about a new device accessing the system.

[0066] The system verifies the hardware and software environment of the new device to ensure that it can support backup functions (e.g., memory and computing power meet the requirements).

[0067] Calculate the weight (Q-value) of the device: The system calculates the weight Q value of the new device, considering the following factors: Operating status of new equipment Congestion status of the uplink edge OLT network link The new device's memory and computing resources When the weight Q value is higher than the preset threshold, the device is considered suitable for configuration backup.

[0068] Determine whether to perform a backup: The weight Q value exceeds the first preset value: The system marks the new device as a "backupable device" and starts the configuration backup program.

[0069] The system checks the current configuration status of the device. If there is no backup copy, it triggers a synchronization operation to synchronize the current configuration from the primary device to the new device.

[0070] The weighted Q value is lower than the first preset value but higher than the second preset value: The system marks the new device as a "conditional backup device" and decides whether to perform a backup operation based on network load.

[0071] If the current network load is low, the system will still choose to perform backup synchronization.

[0072] If the network load is high, the system will delay backup operations until the load decreases.

[0073] The weighted Q value is lower than the second preset value: The system has determined that the new device cannot be backed up and will not synchronize it for the time being. Adjustments will be made as needed based on the device's operating status.

[0074] Backup and synchronization: Start Backup Synchronization: Once a new device is determined to require backup, the system will initiate the backup synchronization process to synchronize the configuration data of the main gateway device to the new device.

[0075] Version consistency check: Before backup, the system checks the configuration versions of the current primary device and the backup device to ensure that the versions are consistent.

[0076] If the configuration versions are inconsistent, update the version first, and then synchronize.

[0077] Synchronization Complete Confirmation: After the backup synchronization is complete, the system confirms that the new device configuration has been successfully synchronized and updates the device status to "Backup Complete".

[0078] Troubleshooting: If a failure occurs during backup synchronization, the system will perform the following actions: If the backup synchronization is not complete, the system will attempt to resynchronize.

[0079] If a device malfunctions or becomes unavailable, the system will clear its backup information and mark the device as an "unavailable backup device" for subsequent maintenance or replacement.

[0080] Log recording and notifications: The system will record detailed logs of all operation steps, device status changes, and backup synchronization.

[0081] If an anomaly or malfunction occurs, the system will send a notification to the administrator, providing detailed fault information and suggested solutions.

[0082] Postconditions: The new device has completed backup and synchronization, and the system has updated the device configuration status to "normal operation".

[0083] If the device is unable to be backed up or synchronized, the system will log the failure and take further action.

[0084] Expected results: The new device successfully determined whether a backup was needed, and the backup synchronization operation was performed according to the predetermined procedure.

[0085] If the backup synchronization is successful, the device configuration will be consistent with the main gateway device, ensuring stable network operation.

[0086] 2. How to select the target executor and perform backup synchronization when initiating a device transaction. Prerequisites: The system already has multiple devices, some of which have been configured and backed up.

[0087] The system can calculate the weight (Q value) of the devices and record the backup status of each device.

[0088] The device's operating status and weight (Q value) are updated in real time.

[0089] Use case steps: Device transaction initiation: A device initiates a management transaction request, such as a configuration update or backup synchronization.

[0090] When a device initiates a transaction, the system verifies the device's status.

[0091] Determine if a backup is available: The system checks whether the device that initiated the transaction has a backup.

[0092] If the device is not backed up, the system will first calculate whether it can be backed up and take on the task based on the device's weight.

[0093] If the device has been backed up, the system will skip the backup process and proceed directly to select the transaction target executor.

[0094] Select the target executor: The system selects the executor based on the device's weight (Q value) and communication cost: High-weight devices are prioritized: The system prioritizes devices with higher weights for transaction execution. High-weight devices mean that the devices have sufficient resources and can handle a greater transaction load.

[0095] Load balancing: If multiple devices have similar weights, the system will select the appropriate executor based on the current device load. Devices with lower loads will be selected first.

[0096] Communication cost considerations: The system also takes into account the communication costs (latency, bandwidth consumption, etc.) between the device and the target executor, avoiding the selection of devices with excessively high communication costs.

[0097] Task allocation after the executor is selected: Once an executor is selected, the system will verify whether the target device is capable of handling the transaction.

[0098] If the target executor device has sufficient computing power, memory, and network bandwidth, the system will send a transaction instruction to the device to initiate transaction processing.

[0099] If the target executor device is unable to handle the transaction load, the system will reselect an executor until a suitable device is found.

[0100] Backup and synchronization operations: Initiate backup synchronization: If a device transaction involves backup or configuration updates, the system will initiate backup synchronization before the target executor device completes the transaction.

[0101] Check configuration version consistency: The system checks the configuration version of the target executor device and compares it with that of the master device. If the versions differ, the device configuration is updated first, and then backup and synchronization are performed.

[0102] If the target device and the master device have the same configuration, the system will skip the configuration update step and directly perform backup and synchronization.

[0103] Backup synchronization complete: Once the system confirms that the backup synchronization is complete, the device transactions will continue.

[0104] Transaction execution: The executor device performs operations according to the transaction requirements, which may include configuration changes, system updates, data processing, etc.

[0105] During execution, the system will monitor the device status and execution progress in real time to ensure the smooth progress of the transaction.

[0106] Confirmation and update after transaction completion: After the executor device completes the transaction, the system will confirm the successful execution of the transaction.

[0107] The system will update the device status, including transaction completion flags, backup synchronization status, etc.

[0108] The system will record transaction logs, including the selection process of the target executor, the backup synchronization status, and the transaction execution results.

[0109] Failure handling and retries: If the target executor device malfunctions during the execution of a transaction, the system will automatically perform fault recovery operations: The system will reselect an executor and assign the transaction to a new device.

[0110] If the backup synchronization is not complete, the system will restart the backup synchronization process until all devices are configured in the same way.

[0111] If the equipment malfunction cannot be resolved, the system will notify the administrator and take appropriate follow-up measures (such as equipment replacement, troubleshooting, etc.).

[0112] Log recording and notifications: The system will record all operation steps, transaction execution status, and detailed logs of backup synchronization.

[0113] If an anomaly or malfunction occurs, the system will send a notification to the administrator, providing detailed fault information and suggested solutions.

[0114] Postconditions: Once the transaction is completed, the status of the target executor device is updated, and the configuration backups of all devices are successfully synchronized, ensuring system consistency.

[0115] If the transaction fails, the system has already selected a new target device and completed the remedial operation.

[0116] Expected results: The device transaction selects the most suitable target executor for execution based on weight and load.

[0117] Backup and synchronization operations work closely with transaction execution to ensure configuration consistency and successful transaction execution.

[0118] The system can handle failures during transaction execution and automatically select a new executor for retry.

[0119] 3. Handling main gateway or backup node anomalies Prerequisites: The system has been configured with multiple devices, including the main gateway device and backup nodes.

[0120] The system can monitor the status of the main gateway and backup nodes in real time.

[0121] The system records the backup status of devices and can automatically identify abnormal devices.

[0122] Use case steps: Abnormal detection: The system periodically monitors the health status of the main gateway and backup nodes.

[0123] If the main gateway or backup node fails (such as network outage, hardware failure, etc.), the system will mark it as an "abnormal state" and trigger the processing flow.

[0124] The monitoring system detects anomalies in the following ways: The network is disconnected or unreachable.

[0125] Hardware failure, such as memory or CPU overload.

[0126] The configuration versions are out of sync or the data is inconsistent.

[0127] Main gateway exception handling: Handling steps when the main gateway is abnormal: The system first checks if the main gateway is completely unavailable. If it is unavailable, the system will mark it as "main gateway abnormal".

[0128] The system initiates a takeover operation with the backup gateway or standby master device to ensure the continuous operation of the network and configuration.

[0129] Backup gateway switching: The system will select an available backup node or standby primary gateway as the new primary gateway and automatically take over the responsibilities of the primary gateway.

[0130] If a backup node exists, the system will ensure that the configuration of the backup node is consistent with that of the main gateway through backup synchronization.

[0131] The system will notify the backup node of the successful takeover through log records and administrator notifications, and mark the device status as "normal".

[0132] Backup node anomaly handling: Steps for handling backup node failures: The system first determines the status of the backup node. If the backup node cannot be taken over or is no longer available, the system will mark it as "backup node abnormal".

[0133] The system will attempt to enable other devices as new backup nodes: If other devices meet the hardware and network requirements for a backup node, the system will select this device as the new backup node.

[0134] The system will synchronize the configuration of the main gateway to the new backup node through backup synchronization to ensure configuration consistency.

[0135] If a suitable backup node cannot be found, the system will issue an alert and notify the administrator, providing detailed fault information.

[0136] Data consistency check: Version consistency check: During the switchover process, the system checks whether the data versions of the primary gateway and the backup node are consistent.

[0137] If there are inconsistencies in configuration versions, the system will initiate a version synchronization operation to ensure that the configurations of the primary gateway and backup nodes are consistent.

[0138] During the configuration synchronization process, the system will confirm that the backup node has successfully received and applied the latest master gateway configuration.

[0139] Equipment recovery operation: Main gateway restored: If the original primary gateway device returns to normal after repair, the system will put it back into use and synchronize the configuration of the backup node back to the primary gateway to ensure consistency.

[0140] After the main gateway recovers, the system will verify whether it has the conditions to take over the main gateway's responsibilities and re-enable it as the main device.

[0141] Backup node recovery: If the backup node recovers normally, the system will re-mark it as a backup node based on the device status and start the configuration synchronization operation.

[0142] The restored backup node will synchronize data to ensure data consistency between the main gateway and the backup node.

[0143] Fault logging and notification: All anomaly detection, device switching, and backup synchronization operations will be logged in detail.

[0144] The system will automatically send a notification to the administrator when an anomaly occurs, including the cause of the fault, the affected devices, the corrective measures taken, and suggestions for recovery.

[0145] Transaction retry and fault recovery: When a device malfunctions, the system will attempt to re-execute transactions that were interrupted during the malfunction (such as backup synchronization, configuration updates, etc.).

[0146] If the system is unable to restore the device during the recovery process, the administrator will be notified for further manual intervention and processing.

[0147] Postconditions: If the primary gateway or backup node fails, the system can ensure continuous network operation and restore configuration consistency through measures such as backup node switching and version synchronization.

[0148] All fault information, switchover and recovery operations have been recorded and the administrator has been notified for follow-up.

[0149] Expected results: The system can effectively identify and handle anomalies in the main gateway or backup nodes, ensuring the normal operation of devices and the stability of the network.

[0150] After a faulty device is restored, the system can automatically synchronize its configuration to ensure that the device status is consistent and avoid system crashes or configuration conflicts.

[0151] All operations, fault information, and recovery processes can be recorded in detail and effectively managed through notifications.

[0152] Transparent and reliable: All devices within the FTTR network environment have a unified visual management interface, displaying the same content to the outside world. This reduces learning costs, simplifies operation processes, and meets users' needs for operation anytime, anywhere. Decentralization also ensures that configuration information within the entire FTTR internal network environment is difficult to lose and easy to recover, reducing maintenance costs and improving work efficiency.

[0153] Based on the same inventive concept, this application also provides a system corresponding to the method in Embodiment 1, as detailed in Embodiment 2.

[0154] Example 2 This embodiment provides an intelligent configuration management system for distributed network topology, such as Figure 6 As shown, it includes: The configuration weight determination module is used to dynamically calculate the configuration backup weight Q of each device based on the current configuration management requirements, the operating status parameters of each device, and the congestion status of the uplink network link of each device; the configuration backup weight Q of the main gateway is always the maximum value; The configuration backup module is used to designate devices with a configuration backup weight Q higher than the first preset value as backupable devices, perform configuration backup operations on the management system, and then start the management system. The task execution module is used to perform local task processing when a slave device executes a management task. If the task initiator has a configuration backup, it will perform the task locally. If it does not have a configuration backup, it will select a suitable device as a proxy to execute the task based on the communication cost between the task initiator and the target executor and the target executor's own operating status. The main gateway switching module is used to select the device with the highest configured backup weight Q as the proxy's main gateway when the main gateway fails.

[0155] Preferably, the configuration backup module is further configured to, when the configuration backup weight Q is higher than a first preset value x If the proportion of devices with a value of 0 approaches 0, then at least the second preset value must be guaranteed. y One number of slave devices have configuration backups; when the proportion of devices with a configuration backup weight Q higher than the first preset value approaches 1, at most the third preset value is selected. y Two devices have configuration backups.

[0156] Preferably, the first preset value x 0. Second preset value y 1. Third preset value y2. Based on the regression equation, the expected value is predicted. The initial dataset for establishing the regression equation is established by the supply and demand relationship in the current actual deployment environment. The supply and demand relationship includes: the total number of devices in the actual deployment environment β1, the overall failure rate of devices β2, the proportion of devices used for network management β3, the proportion of devices under high load for a long time β4, and the time period when the network environment is under high load β5.

[0157] Furthermore, selecting a suitable device as the proxy to execute the task specifically includes: calculating the selection bias P, and then selecting the device with the largest P value as the proxy to execute the task; the formula for calculating the selection bias P is as follows: ; Where Q represents the configuration backup weight, and F... NetTrans F represents the latency of information exchange between the task initiating device and the task executing device, as well as the number of hops in the network topology. DevStatus This indicates the remaining CPU and memory usage of the task executor's device when the task is selected. .

[0158] Preferably, the configuration weight determination module is further configured to maintain a management table for each device with configuration backups managed by the system, including key-value pairs of configuration copy content value and copy version number N, and periodically synchronize the version number N of each backup device copy to keep the configuration version of all devices with configuration backups consistent with and up-to-date with the main gateway; when a task is initiated on a device and the target executor device is determined through the above calculations, the device initiates a configuration version information request to the main gateway before executing the task, and selects the newest configuration information to execute the task; after the task is completed, the configuration backup version number is updated and the latest configuration information is sent to the main gateway.

[0159] Since the system described in Embodiment 2 of the present invention is used to implement the method of Embodiment 1 of the present invention, those skilled in the art can understand the specific structure and variations of the system based on the method described in Embodiment 1 of the present invention, and therefore will not be described again here. All systems used in the method of Embodiment 1 of the present invention fall within the scope of protection of the present invention.

[0160] The technical solutions provided in the embodiments of the present invention have at least the following technical effects: 1. Optimize network configuration management to improve work efficiency: This invention, by introducing a resilient network regression model and a dynamic task scheduling mechanism, can automatically adjust device task allocation and configuration backup based on device operating status, network environment, and bandwidth requirements. This automated and intelligent management approach reduces manual operation and errors, significantly improving the efficiency and accuracy of network configuration.

[0161] 2. Ensure the real-time nature and consistency of configuration data: This invention employs the Paxos algorithm to synchronize and manage device configuration versions, ensuring that network configuration information is updated promptly when devices join, leave, or fail, thus avoiding the risks of data inconsistency and obsolescence. This consistency guarantee mechanism improves system stability during dynamic changes, ensuring more reliable configuration updates and backup operations.

[0162] 3. Enhance the intelligence and flexibility of network resource scheduling.

[0163] This invention intelligently assesses device load, network status, and task execution capabilities, automatically selecting the most suitable device to perform management tasks and optimizing resource scheduling. This avoids performance bottlenecks and resource waste caused by uneven device load or unreasonable task allocation in traditional network management systems, thus improving the overall network operating efficiency.

[0164] 4. Improve system fault tolerance and ensure high availability.

[0165] This invention incorporates an intelligent fault-tolerance mechanism. When the primary gateway or backup node fails, it automatically selects a device with higher weight to perform tasks or restore services, thereby ensuring continuous network operation and high availability. Even in the event of device failure, the system can quickly switch over and maintain network stability, reducing service interruption time caused by device failure.

[0166] 5. Supports rapid deployment and efficient operation of FTTR technology.

[0167] This invention is specifically optimized for FTTR (Fiber to the Room) network architecture, enabling rapid deployment, dynamic adjustment, and efficient management of fiber optic connections in high-density equipment environments. By applying the distributed configuration management scheme of this invention, users can enjoy stable and high-speed network services in each room, significantly improving network performance and user experience.

[0168] 6. Reduce system maintenance costs and lower operational risks.

[0169] This invention simplifies the complexities of traditional distributed network management, making the management of network devices and configurations more automated and visualized, and reducing the need for manual intervention and maintenance. Intelligent configuration backup and fault recovery mechanisms can efficiently handle emergencies, reducing operational costs and risks caused by human error or equipment failure.

[0170] In summary, this invention, through its innovative distributed network topology configuration information management method, not only effectively solves the problems of insufficient configuration synchronization, resource scheduling, and fault tolerance in existing technologies, but also significantly improves the application effect of FTTR technology in high-performance network environments, greatly enhancing the stability, reliability, and scalability of network systems.

[0171] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0172] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0173] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0174] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0175] While specific embodiments of the present invention have been described above, those skilled in the art should understand that the specific embodiments described are merely illustrative and not intended to limit the scope of the present invention. Equivalent modifications and variations made by those skilled in the art in accordance with the spirit of the present invention should be covered within the scope of protection of the claims of the present invention.

Claims

1. A method for intelligent configuration management of distributed network topology, characterized in that, include: The configuration backup weight Q of each device is dynamically calculated based on the current configuration management requirements, the operating status parameters of each device, and the congestion status of the uplink network link of each device. The primary gateway's backup weight Q is always set to the maximum value. Devices with a backup weight Q higher than the first preset value are designated as backupable devices. After performing the configuration backup operation of the management system, the management system is started. When performing management tasks from the device, if the task initiator has a configuration backup, the task will be processed locally. If no configuration backup exists, a suitable device will be selected as the proxy to execute the task based on the communication cost between the task initiator and the target executor and the target executor's own operating status. When the main gateway fails, the device with the highest backup weight Q is selected as the proxy's main gateway.

2. The method according to claim 1, characterized in that: When the configured backup weight Q is higher than the first preset value x If the proportion of devices with a value of 0 approaches 0, then at least the second preset value must be guaranteed. y One number of slave devices have configuration backups; when the proportion of devices with a configuration backup weight Q higher than the first preset value approaches 1, at most the third preset value is selected. y Two devices have configuration backups.

3. The method according to claim 2, characterized in that: First preset value x 0. Second preset value y 1. Third preset value y 2. Based on the regression equation, the expected value is predicted. The initial dataset for establishing the regression equation is established by the supply and demand relationship in the current actual deployment environment. The supply and demand relationship includes: the total number of devices in the actual deployment environment β1, the overall failure rate of devices β2, the proportion of devices used for network management β3, the proportion of devices under high load for a long time β4, and the time period when the network environment is under high load β5.

4. The method according to claim 1, characterized in that: Selecting a suitable device as the proxy to execute the task specifically involves: calculating the selection bias P, and then selecting the device with the largest P value as the proxy to execute the task; the formula for calculating the selection bias P is as follows: ； Where Q represents the configuration backup weight, and F... NetTrans F represents the latency of information exchange between the task initiating device and the task executing device, as well as the number of hops in the network topology. DevStatus This indicates the remaining CPU and memory usage of the task executor's device when the task is selected. .

5. The method according to claim 1, characterized in that: Each device with a configuration backup maintained by the management system maintains a management table, including key-value pairs of configuration copy content value and copy version number N. The version number N of each backup device copy is periodically synchronized to ensure that all devices with configuration backups are consistent with and up-to-date with the main gateway configuration version. When a task is initiated on a device and the target executor device is determined, the device sends a configuration version information request to the main gateway before executing the task, and selects the newest configuration information to execute the task. After the task is completed, update the configuration backup version number and send the latest configuration information to the main gateway.

6. An intelligent configuration management system for distributed network topology, characterized in that, include: The configuration weight determination module is used to dynamically calculate the configuration backup weight Q of each device based on the current configuration management requirements, the operating status parameters of each device, and the congestion status of the link from each device to the uplink network. The primary gateway's backup weight Q is always set to the maximum value. The configuration backup module is used to designate devices with a configuration backup weight Q higher than the first preset value as backupable devices, perform configuration backup operations on the management system, and then start the management system. The task execution module is used to perform local task processing when the slave device executes management tasks, if the task initiator has a configuration backup. If no configuration backup exists, a suitable device will be selected as the proxy to execute the task based on the communication cost between the task initiator and the target executor and the target executor's own operating status. The main gateway switching module is used to select the device with the highest configured backup weight Q as the proxy's main gateway when the main gateway fails.

7. The system according to claim 6, characterized in that: The configuration backup module is further configured to, when the configuration backup weight Q is higher than a first preset value x If the proportion of devices with a value of 0 approaches 0, then at least the second preset value must be guaranteed. y One number of slave devices have configuration backups; when the proportion of devices with a configuration backup weight Q higher than the first preset value approaches 1, at most the third preset value is selected. y Two devices have configuration backups.

8. The system according to claim 7, characterized in that: First preset value x 0. Second preset value y 1. Third preset value y 2. Based on the regression equation, the expected value is predicted. The initial dataset for establishing the regression equation is established by the supply and demand relationship in the current actual deployment environment. The supply and demand relationship includes: the total number of devices in the actual deployment environment β1, the overall failure rate of devices β2, the proportion of devices used for network management β3, the proportion of devices under high load for a long time β4, and the time period when the network environment is under high load β5.

9. The system according to claim 6, characterized in that: Selecting a suitable device as the proxy to execute the task specifically involves: calculating the selection bias P, and then selecting the device with the largest P value as the proxy to execute the task; the formula for calculating the selection bias P is as follows: ； Where Q represents the configuration backup weight, and F... NetTrans F represents the latency of information exchange between the task initiating device and the task executing device, as well as the number of hops in the network topology. DevStatus This indicates the remaining CPU and memory usage of the task executor's device when the task is selected. .

10. The system according to claim 6, characterized in that: The configuration weight determination module is also used to maintain a management table for each device with configuration backup in the management system, including key-value pairs of configuration copy content value and copy version number N, and periodically synchronize the version number N of each backup device copy to keep the configuration version of all devices with configuration backup consistent with the main gateway and up-to-date; when a task is initiated on a device and the target executor device is determined, the device initiates a configuration version information request to the main gateway before executing the task, and selects the newest configuration information to execute the task; After the task is completed, update the configuration backup version number and send the latest configuration information to the main gateway.

Images