A method and system for allocating subnet addresses based on SDN

Abstract

The present application relates to a method and system for allocating subnet addresses based on SDN. The method includes obtaining initial network configuration requirements; collecting network information in real time; based on the network information and the initial network configuration requirements, dynamically dividing address segments using an adaptive subnet division algorithm to generate corresponding subnet configurations and dynamic address pools; when receiving a DHCP request, selecting available IP addresses from the dynamic address pool according to a pre-established IP address allocation policy, generating a corresponding DHCP response message, and sending the DHCP response message to the requesting device to complete address allocation; monitoring the real-time data after address allocation in real time, where the real-time data includes IP address usage, device load data, and topology changes, and dynamically adjusting the subnet configuration and the dynamic address pool according to the real-time data. The present application has the effect of improving the utilization efficiency of address resources.

Description

Technical Field

[0001] This application relates to the technical field of network communication, and in particular, to a method and system for allocating subnet addresses based on SDN. Background Art

[0002] Currently, with the continuous expansion of the network scale, especially in enterprise networks, cloud computing, and big data centers, the network topology structure is becoming increasingly complex, the number of devices and traffic loads are constantly increasing, and traditional IP address allocation methods face many challenges. Existing IP address allocation usually relies on static configuration or DHCP-based dynamic allocation methods. Although DHCP can achieve a certain degree of automation, its working scope is generally limited to address allocation within a single subnet, and it is difficult to achieve global planning and resource optimization across subnets. Traditional solutions usually adopt a fixed subnet division strategy, that is, manually set the address range of each subnet during the initial network configuration. However, this method lacks flexibility and cannot be dynamically adjusted according to changes in the network state. When the address resources of some subnets are exhausted while there are still a large number of idle addresses in other subnets, it is impossible to effectively schedule resources between subnets, resulting in uneven address allocation. In addition, existing technical solutions mostly rely on a centralized DHCP server for IP address allocation, lacking the ability to perceive the global network state, device load, and dynamic topology changes in real time, and it is difficult to ensure the optimality and efficiency of IP address allocation in a complex network environment.

[0003] The above existing technical solutions have the following defects: When the network topology changes or the device load fluctuates, it is difficult for the existing technical solutions to timely adjust the subnet division and address pool configuration, resulting in low resource utilization or local shortage, so there is room for improvement. Summary of the Invention

[0004] In order to improve the utilization efficiency of address resources, this application provides a method and system for allocating subnet addresses based on SDN.

[0005] The first invention object of this application is achieved through the following technical solutions:

[0006] A method for allocating subnet addresses based on SDN, the method for allocating subnet addresses based on SDN includes:

[0007] Obtain the initial network configuration requirements, where the initial network configuration requirements include the global IP address segment, subnet division strategy, lease duration, and network isolation requirements;

[0008] Collect network information in real time, where the network information includes network topology information, device status, and traffic load data;

[0009] Based on the network information and the initial network configuration requirements, an adaptive subnet division algorithm is used to dynamically divide the address segments, generating corresponding subnet configurations and dynamic address pools;

[0010] When a DHCP request is received, according to the pre-established IP address allocation policy, an available IP address is selected from the dynamic address pool, a corresponding DHCP response message is generated, and the DHCP response message is sent to the requesting device to complete the address allocation;

[0011] The real-time data after address allocation is monitored in real time. The real-time data includes IP address usage, device load data, and topology changes, and the subnet configuration and dynamic address pool are dynamically adjusted according to the real-time data.

[0012] By adopting the above technical solutions, by obtaining the initial network configuration requirements, including the global IP address segment, subnet division strategy, lease duration, and network isolation requirements, the rationality of network resource planning can be ensured, the allocation of IP addresses can meet the business requirements, thereby improving the flexibility and manageability of the network and reducing the complexity of manual intervention; by collecting network information in real time, including network topology information, device status, and traffic load data, the real-time status of the network environment can be obtained, ensuring that subnet division and address allocation can be optimized based on the latest network conditions, thereby improving the dynamic adaptability of IP address allocation and reducing address conflicts caused by topology changes; by using an adaptive subnet division algorithm to dynamically divide the address segments, generating corresponding subnet configurations and dynamic address pools, the subnet scale can be automatically adjusted based on the real-time collected network information, optimizing subnet division, improving IP address utilization rate, thereby reducing address waste within the subnet and improving the overall network performance; by when a DHCP request is received, according to the pre-established IP address allocation policy, an available IP address is selected from the dynamic address pool, a corresponding DHCP response message is generated, and the DHCP response message is sent to the requesting device to complete the address allocation, it can ensure that the address allocation conforms to the established policy, prevent IP address allocation conflicts, and reduce the manual intervention of network administrators, thereby enhancing the automation level of network management; by monitoring the real-time data after address allocation in real time and dynamically adjusting the subnet configuration and dynamic address pool according to the real-time data, network load changes can be detected in a timely manner, dynamically optimizing subnet division and address pool management, thereby ensuring the reasonable allocation of network resources and improving the stability and scalability of the network.

[0013] In one example of this application, it can be further configured that: the obtaining of the initial network configuration requirements includes:

[0014] The initial network configuration requirements further include preset service priorities and tenant isolation requirements;

[0015] Receive the network configuration requirement data submitted by the user, parse the network configuration requirement data submitted by the user, and extract the global IP address segment, subnet division strategy, lease duration, network isolation requirement, preset service priority, and tenant isolation requirement;

[0016] Statistically integrate the global IP address segment, subnet division strategy, lease duration, network isolation requirement, preset service priority, and tenant isolation requirement to obtain the initial network configuration requirement.

[0017] By adopting the above technical solution, further including the preset service priority and tenant isolation requirement when obtaining the initial network configuration requirement can ensure that the resource allocation between different service scenarios and tenants meets the differentiated requirements, thereby improving the fairness and security of network resources; by receiving the network configuration requirement data submitted by the user and parsing and extracting the global IP address segment, subnet division strategy, lease duration, network isolation requirement, service priority, and tenant isolation requirement, the standardized processing of network configuration requirements can be realized, ensuring that all parameters are accurately parsed, thereby reducing human configuration errors and improving the accuracy of network management; by statistically integrating the extracted data to obtain the initial network configuration requirement, a unified configuration data can be formed, providing a standardized input for subsequent subnet division and address allocation, thereby improving the automation degree and consistency of the entire network management.

[0018] In one example of the present application, it can be further configured that: the real-time collection of network information includes:

[0019] Collect the network topology information within a preset time period, where the network topology information includes the connection status between devices, port information, and link quality data;

[0020] Real-time monitor the status data of each network device, where the status data includes device running status, CPU and memory load, fault alarm, and key indicators;

[0021] Determine the real-time data traffic situation of each network area through traffic statistics to obtain the traffic load data of each node;

[0022] Integrate and analyze the network topology information, device status data, and traffic load data, and statistically obtain the network information.

[0023] By adopting the above technical solution, by collecting network topology information within a preset time period, including device connection status, port information, and link quality data, it is possible to continuously obtain the changes in the network structure, ensure that subnet division and IP address management always adapt to the current network environment, thereby reducing resource waste and conflicts caused by topology changes; by real-time monitoring the status data of each network device, including operating status, CPU and memory load, fault alarms, and key indicators, it is possible to ensure that the network management system promptly discovers abnormal devices and reasonably adjusts the IP address pool and subnet configuration, thereby reducing network instability problems caused by device failures; by traffic statistics to determine the real-time data traffic conditions of each network area and obtain the traffic load data of each node, it is possible to effectively evaluate the load conditions of different subnets, provide an optimization basis for subnet division, thereby reducing the load imbalance situation and improving the overall network performance; by integrating and analyzing the collected network information, it is possible to form a comprehensive network status view, provide accurate data support for subsequent subnet division, address pool management, and traffic optimization, thereby improving the intelligent level of network management.

[0024] In one example, the present application can be further configured as follows: The dynamic division of the address segment by using the adaptive subnet division algorithm based on the network information and the initial network configuration requirements to generate the corresponding subnet configuration and dynamic address pool includes:

[0025] According to the global IP address segment in the initial network configuration requirements and the network topology information in the network information, initially divide multiple candidate subnets and determine the candidate subnet scheme;

[0026] Using the constraint optimization model, combined with the device status, traffic load data, and network isolation requirements, screen and optimize the candidate subnet scheme, determine the subnet scale and division boundary, and generate the subnet configuration;

[0027] According to the subnet configuration, construct a dynamic address pool for each subnet;

[0028] Based on the dynamic address pool and the lease duration, preset service priority, and isolation requirements in the initial network configuration requirements, formulate the corresponding IP address allocation policy to obtain the pre-formulated IP address allocation policy, and the pre-formulated IP address allocation policy is used to guide the subsequent DHCP address allocation process.

[0029] By adopting the above technical solutions, by initially dividing multiple candidate subnets according to the global IP address segment and network topology information and determining the candidate subnet solutions, a basic subnet plan can be formed in the overall network architecture, providing a structural framework for subsequent optimization, thus ensuring the rationality of subnet division and improving the flexibility of subnet planning; by using the constraint optimization model, combining device status, traffic load data and network isolation requirements, screening and optimizing the candidate subnet solutions, and determining the subnet scale and division boundaries, the subnet division can be dynamically optimized under different service requirements and network states, enabling the subnet boundaries to dynamically adapt to load changes, thereby improving the utilization rate of IP address resources and reducing the address fragmentation problem between subnets; by constructing a dynamic address pool for each subnet, it can ensure that the IP resources of different subnets can be flexibly expanded and adjusted, thereby improving the utilization efficiency of IP addresses and avoiding waste of subnet resources; by formulating corresponding IP address allocation policies based on the dynamic address pool and lease duration, service priority and isolation requirements in the initial network configuration requirements and using them to guide the subsequent DHCP address allocation process, it can ensure that the allocation of IP addresses meets service requirements and network security policies, thereby enhancing the manageability and resource allocation efficiency of the entire network.

[0030] In one example, this application can be further configured as follows: Before using the constraint optimization model to screen and optimize the candidate subnet solutions in combination with the device status, traffic load data, and network isolation requirements, the method for allocating subnet addresses based on SDN further includes:

[0031] Collect historical network operation data, where the historical network operation data includes historical IP address usage, device load conditions, network topology changes, and traffic load data;

[0032] According to the historical network operation data, analyze the subnet resource utilization rate, load balancing situation, and network isolation effect, evaluate the applicability of the existing subnet division strategy, and generate an analysis result;

[0033] Based on the analysis result, dynamically adjust the parameters of the constraint optimization model, where the parameters of the constraint optimization model include subnet division rules, load balancing weights, address pool allocation ratios, and tenant isolation strategies.

[0034] By adopting the above technical solutions, by collecting historical network operation data, including IP address usage, device load conditions, network topology changes, and traffic load data, it is possible to provide long-term network operation trend analysis, provide accurate data support for subnet optimization, and thus improve the predictability and rationality of subnet planning; by analyzing the subnet resource utilization rate, load balancing conditions, and network isolation effects based on historical data, evaluating the applicability of the existing subnet division strategy, and generating analysis results, it is possible to identify the deficiencies of the existing subnet division scheme, dynamically adjust the planning strategy, and thus reduce the problems of low address utilization rate and network congestion caused by unreasonable subnet division; by dynamically adjusting the parameters of the constraint optimization model based on the analysis results, including subnet division rules, load balancing weights, address pool allocation ratios, and tenant isolation strategies, it is possible to ensure that the optimization model can be continuously adjusted according to historical data, thereby enhancing its adaptability and making network management more intelligent and dynamically adjustable.

[0035] In one example, the present application can be further configured as follows: when receiving a DHCP request, selecting an available IP address from the dynamic address pool and generating a corresponding DHCP response message includes:

[0036] Parsing the DHCP request to determine the subnet where the requesting device is located;

[0037] Selecting an available IP address from the dynamic address pool according to the dynamic address pool of the subnet where the requesting device is located and the pre-established IP address allocation policy;

[0038] Determining network configuration information corresponding to the available IP address according to the lease duration defined in the initial network configuration requirements, the preset service priority, and the network isolation requirements;

[0039] Generating the corresponding DHCP response message according to the available IP address and the network configuration information.

[0040] By adopting the above technical solution, by parsing the DHCP request to determine the subnet where the requesting device is located, the accuracy of IP address allocation can be ensured, preventing network anomalies caused by incorrect subnet allocation, thereby improving the accuracy of allocation; by selecting an available IP address from the dynamic address pool according to the dynamic address pool of the subnet where the requesting device is located and the pre-established IP address allocation policy, the allocation of IP addresses can be ensured to conform to the current resource situation and service requirements, thereby improving the utilization efficiency of IP address resources; by determining the network configuration information corresponding to the available IP address according to the lease duration, service priority, and network isolation requirements in the initial network configuration requirements, the IP allocation can be ensured to conform to the overall network management policy, thereby improving the security and flexibility of the network; by generating a corresponding DHCP response message according to the available IP address and network configuration information, the standardized allocation of IP addresses can be realized, ensuring that the terminal device can be normally connected to the network, thereby improving the stability of the entire network management system.

[0041] In one example, the present application can be further configured as: the method for allocating a subnet address based on SDN further includes:

[0042] When the lease of the allocated IP address is about to expire, a lease renewal notice is sent to the corresponding requesting device. If the requesting device does not send a lease renewal request and the online status of the requesting device is not detected after the lease expires, the allocated IP address is released and returned to the dynamic address pool;

[0043] When a long-unused IP address or the offline status of the requesting device is detected, the corresponding IP address is recycled and reallocated according to a preset recycling strategy;

[0044] When a change in service requirements is obtained, the subnet division is dynamically adjusted and the subnet configuration is adjusted.

[0045] By adopting the above technical solution, when the lease of the allocated IP address is about to expire, a lease renewal notice is sent to the terminal device. If the terminal device does not send a renewal request and the online status of the requesting device is not detected after the lease expires, the IP address is released and returned to the dynamic address pool, which can ensure the rationality of IP address recycling, avoid the occupation of invalid addresses, and thereby improve the utilization efficiency of IP address resources; when a long-unused IP address or the offline status of the requesting device is detected, the corresponding IP address is recycled and reallocated according to a preset recycling strategy, which can further optimize the resource allocation of IP addresses, reduce the problem of invalid address occupation, and thereby improve the IP address management efficiency of the entire network; when a change in service requirements is obtained, the subnet division is dynamically adjusted and the subnet configuration is adjusted, which can ensure that the subnet division can adapt to new service requirements at any time, thereby improving the flexibility and expansion ability of the network.

[0046] The second inventive object of the present application is achieved by the following technical solutions:

[0047] A subnet address allocation system based on SDN, the subnet address allocation system based on SDN includes:

[0048] A requirement acquisition module, configured to acquire an initial network configuration requirement, where the initial network configuration requirement includes a global IP address segment, a subnet division policy, a lease duration, and a network isolation requirement;

[0049] A network information collection module, configured to collect network information in real time, where the network information includes network topology information, device status, and traffic load data;

[0050] A division module, configured to dynamically divide an address segment based on the network information and the initial network configuration requirement, using an adaptive subnet division algorithm, to generate a corresponding subnet configuration and a dynamic address pool;

[0051] An address allocation module, configured to, when receiving a DHCP request, select an available IP address from the dynamic address pool according to a pre-established IP address allocation policy, generate a corresponding DHCP response message, and send the DHCP response message to the requesting device to complete address allocation;

[0052] An adjustment module, configured to monitor in real time the real-time data after address allocation, where the real-time data includes IP address usage, device load data, and topology changes, and dynamically adjust the subnet configuration and the dynamic address pool according to the real-time data.

[0053] By adopting the above technical solutions, by obtaining the initial network configuration requirements, including the global IP address segment, subnet division strategy, lease duration, and network isolation requirements, it is possible to ensure the rationality of network resource planning, make the allocation of IP addresses meet business requirements, thereby improving the flexibility and manageability of the network and reducing the complexity of manual intervention; by collecting network information in real time, including network topology information, device status, and traffic load data, it is possible to obtain the real-time status of the network environment, ensure that subnet division and address allocation can be optimized based on the latest network conditions, thereby improving the dynamic adaptability of IP address allocation and reducing address conflicts caused by topology changes; by adopting an adaptive subnet division algorithm to dynamically divide the address segment, generate the corresponding subnet configuration and dynamic address pool, it is possible to automatically adjust the subnet scale based on the network information collected in real time, optimize subnet division, and improve the utilization rate of IP addresses, thereby reducing address waste within the subnet and improving the overall network performance; by, when receiving a DHCP request, selecting an available IP address from the dynamic address pool according to the pre-established IP address allocation strategy, generating the corresponding DHCP response message, and sending the DHCP response message to the requesting device to complete address allocation, it is possible to ensure that address allocation conforms to the established strategy, prevent IP address allocation conflicts, and reduce the manual intervention of network administrators, thereby enhancing the automation level of network management; by monitoring the real-time data after address allocation in real time and dynamically adjusting the subnet configuration and dynamic address pool according to the real-time data, it is possible to promptly detect network load changes, dynamically optimize subnet division and address pool management, thereby ensuring the reasonable allocation of network resources and improving the stability and scalability of the network.

[0054] In summary, the present application includes the following beneficial technical effects:

[0055] 1. By obtaining the initial network configuration requirements, it is possible to ensure the rationality of network resource planning, make the allocation of IP addresses meet business requirements, thereby improving the flexibility and manageability of the network and reducing the complexity of manual intervention; by collecting network information in real time, it is possible to obtain the real-time status of the network environment, ensure that subnet division and address allocation can be optimized based on the latest network conditions, thereby improving the dynamic adaptability of IP address allocation and reducing address conflicts caused by topology changes; s

[0056] 2. By adopting an adaptive subnet division algorithm to dynamically divide the address segment, generating corresponding subnet configurations and dynamic address pools, it is possible to automatically adjust the subnet scale based on real-time collected network information, optimize subnet division, improve IP address utilization rate, thereby reducing address waste within the subnet and enhancing the overall network performance. When receiving a DHCP request, according to a pre-established IP address allocation policy, select an available IP address from the dynamic address pool, generate a corresponding DHCP response message, and send the DHCP response message to the requesting device to complete address allocation, which can ensure that the address allocation conforms to the established policy, prevent IP address allocation conflicts, and reduce manual intervention by network administrators, thus enhancing the automation level of network management. Brief Description of the Drawings

[0057] Figure 1 is a flowchart of a method for allocating subnet addresses based on SDN in an embodiment of the present application;

[0058] Figure 2 is an implementation flowchart of step S10 in a method for allocating subnet addresses based on SDN in an embodiment of the present application;

[0059] Figure 3 is an implementation flowchart of step S20 in a method for allocating subnet addresses based on SDN in an embodiment of the present application;

[0060] Figure 4 is an implementation flowchart of step S30 in a method for allocating subnet addresses based on SDN in an embodiment of the present application;

[0061] Figure 5 is an implementation flowchart of step S32 in a method for allocating subnet addresses based on SDN in an embodiment of the present application;

[0062] Figure 6 is an implementation flowchart of step S40 in a method for allocating subnet addresses based on SDN in an embodiment of the present application;

[0063] Figure 7 is an implementation flowchart of a method for allocating subnet addresses based on SDN in an embodiment of the present application;

[0064] Figure 8 is a principle block diagram of a system for allocating subnet addresses based on SDN in an embodiment of the present application. Detailed Description of the Embodiment

[0065] The following further elaborates on the present application with reference to the accompanying drawings.

[0066] In an embodiment, as Figure 1As shown, the present application discloses a method for allocating subnet addresses based on SDN, which specifically includes the following steps:

[0067] S10: Obtain initial network configuration requirements, which include global IP address segments, subnet division strategies, lease duration, and network isolation requirements.

[0068] Specifically, it parses the network configuration data input by the user, extracts the global IP address segment information, identifies the starting address, ending address and subnet range of the IP address, determines the granularity of address allocation based on the subnet division strategy, such as whether to divide it according to a fixed size or dynamically adjust the subnet size according to business needs, calculates the number of available addresses in each subnet, extracts the lease duration parameters, determines the effective time of the IP address allocation, and generates corresponding isolation strategies based on network isolation requirements, such as whether the traffic between tenants is interoperable, the priority setting of different business flows, and the constraints of security policies. All parsed configuration data is stored as structured data to provide basic information for subsequent address allocation and management.

[0069] S20: Collect network information in real time, including network topology information, device status and traffic load data.

[0070] Specifically, it regularly accesses the network control plane to obtain the current network topology information, including the connection relationship between switches, routers and terminal devices, queries the port status of network devices, records whether the port is enabled, the current rate and bandwidth usage, accesses the device management interface, collects the CPU usage, memory usage and operating status of each device, counts the load of each device, calls the traffic monitoring module to analyze the traffic interaction between different subnets, calculates the traffic load of each link, identifies traffic peak areas and possible congestion points, and stores all acquired network information according to timestamps for subsequent subnet division and dynamic adjustment.

[0071] S30: Based on the network information and the initial network configuration requirements, an adaptive subnetting algorithm is used to dynamically divide the address segments, and a corresponding subnet configuration and a dynamic address pool are generated.

[0072] Specifically, parse the stored network information, calculate the currently available global IP address range, determine the subnet division strategy according to the current device load situation. If the device load is low, perform subnet division according to fixed rules. If the device load is high, adopt a dynamic adjustment strategy, predict future load changes by combining historical traffic data, and divide subnets of different scales based on the lease duration and service isolation requirements. During the process of generating subnets, calculate the subnet mask, gateway address, and broadcast address of each subnet, avoiding the generation of overly small subnets that lead to a decrease in address utilization, and at the same time avoiding overly large subnet scales that affect network stability. Dynamically generate corresponding address pools based on the divided subnets, record the available IP ranges, the current number of allocated IPs, and the lease management rules of each address pool, and store all the generated data in the address allocation database to provide a basis for subsequent DHCP request processing.

[0073] S40: When receiving a DHCP request, select an available IP address from the dynamic address pool according to the pre-established IP address allocation strategy, generate a corresponding DHCP response message, and send the DHCP response message to the requesting device to complete the address allocation.

[0074] Specifically, parse the DHCP request message, extract the MAC address of the requesting device, the requested IP address, and the lease duration requirement, and determine whether the requesting device belongs to a registered device. If the device is registered and within the lease validity period, return the original IP address and lease information. If the device is a newly connected device or the lease has expired, query the dynamic address pool, select the optimal available IP address according to the preset IP allocation strategy, and preferentially allocate the available IP in the subnet with a lower load. If the loads of multiple subnets are the same, select the earliest available IP according to the address allocation order, generate a DHCP Offer message containing the IP address, subnet mask, gateway address, and lease duration. If the requesting device accepts the IP address, return a DHCP Ack message to confirm the allocation result, record the allocation status of the IP address, and at the same time update the available IP quantity in the dynamic address pool to ensure that the allocated IP address will not be reused.

[0075] S50: Monitor the real-time data after address allocation in real time. The real-time data includes IP address usage, device load data, and topology changes, and dynamically adjust the subnet configuration and dynamic address pool according to the real-time data.

[0076] Specifically, continuously track the usage of the assigned IP addresses, count the occupancy rate of IP addresses in each subnet. If the subnet address usage rate exceeds the preset threshold, trigger the subnet expansion mechanism, adjust the subnet boundary according to the current network load situation, and add new IP address segments to the dynamic address pool of the high-load subnet. If the subnet address utilization rate is lower than the preset threshold for a long time, recycle some unused addresses to the global address pool to optimize resource utilization. At the same time, monitor the load changes of network devices. If the traffic load of a certain subnet continues to increase, which may lead to a decline in the performance of the subnet, predict the future trend based on the traffic model, and adjust the IP address pool of the subnet in advance or migrate some terminal devices to the subnet with lower load. In addition, monitor the changes in the network topology in real time. If new devices are detected to be connected or devices are offline, update the network topology structure to ensure that the subnet division and address pool configuration always match the latest network environment. All the adjusted data is stored in the database for subsequent optimization analysis.

[0077] By adopting the above technical solutions, by obtaining the initial network configuration requirements, the rationality of network resource planning can be ensured, the allocation of IP addresses can meet the business requirements, thereby improving the flexibility and manageability of the network and reducing the complexity of manual intervention; by collecting network information in real time, the real-time state of the network environment can be obtained, ensuring that subnet division and address allocation can be optimized based on the latest network conditions, thereby improving the dynamic adaptability of IP address allocation and reducing address conflicts caused by topology changes; by using an adaptive subnet division algorithm to dynamically divide address segments and generate corresponding subnet configurations and dynamic address pools, the subnet scale can be automatically adjusted based on the network information collected in real time, optimizing subnet division and improving IP address utilization, thereby reducing address waste within the subnet and improving the overall network performance; by selecting an available IP address from the dynamic address pool according to the pre-established IP address allocation policy when receiving a DHCP request, generating a corresponding DHCP response message, and sending the DHCP response message to the requesting device to complete address allocation, it can ensure that address allocation conforms to the established policy, prevent IP address allocation conflicts, and reduce the manual intervention of network administrators, thereby enhancing the automation level of network management; by monitoring the real-time data after address allocation in real time and dynamically adjusting the subnet configuration and dynamic address pool according to the real-time data, it can timely detect network load changes, dynamically optimize subnet division and address pool management, thereby ensuring the reasonable allocation of network resources and improving the stability and scalability of the network.

[0078] In one embodiment, as Figure 2 shown, in step S10, that is, obtaining the initial network configuration requirements, specifically includes:

[0079] S11: Receive the network configuration requirement data submitted by the user, parse the network configuration requirement data submitted by the user, and extract the global IP address segment, subnet division strategy, lease duration, network isolation requirement, preset service priority, and tenant isolation requirement.

[0080] Specifically, receive the network configuration parameters submitted by the user through the interface, parse the data format, identify the range of the global IP address segment, extract the subnet division strategy information, determine whether to adopt the fixed subnet division rule or dynamic adaptive division, parse the lease duration parameter, determine the lease period of the IP address, extract the network isolation requirement, analyze whether it is necessary to impose an access control policy on a specific IP address range, and at the same time parse the service priority information to determine the priority of different types of devices or service applications in address allocation, extract the tenant isolation requirement, and judge whether forced isolation is required between tenants or whether some network resources can be shared. All the parsed data is stored in the cache and consistency verification is performed to ensure that the data is complete and conforms to the predefined rules.

[0081] Furthermore, the initial network configuration requirement further includes the preset service priority and tenant isolation requirement. Through the service priority information, determine the priority order of different types of services in IP address allocation. For example, allocate a subnet with lower load to services with low latency requirements, and allocate a subnet with more sufficient bandwidth resources to services with higher bandwidth requirements. Identify the network isolation level between tenants according to the tenant isolation requirement, and determine whether different tenants are allowed to share subnet resources. If complete isolation is required between tenants, allocate independent IP address pools in different subnets. If partial sharing is allowed, configure access control rules according to the preset policy to ensure that the traffic isolation between tenants meets the security requirements. All the extracted data is stored in the configuration database to provide a basis for subsequent address allocation.

[0082] S12: Statistically integrate the global IP address segment, subnet division strategy, lease duration, network isolation requirement, preset service priority, and tenant isolation requirement to obtain the initial network configuration requirement.

[0083] Specifically, read the parsed configuration data, verify the global IP address segment to ensure that the address range does not conflict with the existing subnets, calculate the number of subnets that can be divided according to the subnet division strategy, determine the address range of each subnet, calculate the allocation time limit of the IP address in combination with the lease duration information to ensure that it can be recycled and reallocated after the lease expires, determine the IP address allocation rules for different service types according to the service priority information, and give priority to ensuring the address allocation requirements of key services. Adjust the subnet plan according to the tenant isolation requirement to ensure that the IP address allocation for different tenants conforms to the security policy. Store all the statistically integrated configuration data in the database and generate a standardized initial network configuration file for subsequent subnet division and IP address management.

[0084] In one embodiment, as Figure 3 shown, in step S20, that is, real-time collecting network information, specifically including:

[0085] S21: Collect network topology information within a preset time period. The network topology information includes the connection status between devices, port information, and link quality data.

[0086] Specifically, regularly access the network device management interface, obtain the current network topology structure, record the connection relationships between switches, routers, and terminal devices, query the enabled status, bandwidth configuration, and actual traffic load of each port, collect link quality data, including link latency, packet loss rate, and bandwidth utilization, analyze whether there are abnormal fluctuations in the link status. If an anomaly is found, mark it as a potential fault point and trigger an alarm mechanism. Store all the collected network topology information in a database and record the topology changes in chronological order for subsequent subnet division optimization.

[0087] S22: Real-time monitor the status data of each network device. The status data includes device operating status, CPU and memory load, fault alarms, and key metrics.

[0088] Specifically, periodically query the operating status of network devices, obtain the CPU usage rate, memory occupancy, and port activity status, analyze the device load situation. If a device's CPU or memory is in a high-load state for a long time, mark it as a high-load node and record the historical load change trend of the device. Listen to the device's fault alarm information, analyze whether there are port failures, connection interruptions, or hardware anomalies, extract key performance metrics, including device temperature, power status, and fan speed, and determine whether the device is in a normal operating state. Store all the monitoring data in a database and generate a device health status report for subsequent network optimization and resource scheduling.

[0089] S23: Determine the real-time data traffic situation of each network area through traffic statistics to obtain the traffic load data of each node.

[0090] Specifically, listen to the traffic statistics data of switches and routers, analyze the traffic exchange situation between different subnets, calculate the inbound and outbound traffic of each network node, count the data load situation during peak traffic periods, identify whether there are abnormal traffic surges, calculate the link utilization rate, determine whether there is a congestion risk, extract the traffic proportion of key business flows to ensure that the traffic occupancy of high-priority services meets expectations, perform aggregation processing on the traffic data of each node, calculate the overall traffic load of each subnet, and store the data in a database for subsequent subnet adjustment and traffic balance optimization.

[0091] S24: Integrate and analyze the network topology information, device status data, and traffic load data to statistically obtain network information.

[0092] Specifically, summarize the collected network topology information, analyze the changes in device connection relationships, evaluate the health status of each node in combination with the device status data, calculate the resource utilization rate of different subnets based on the traffic load data, identify the load balancing situation, determine whether it is necessary to optimize the subnet configuration or adjust the traffic path, analyze historical data, predict future traffic trends, calculate the overall network load balancing situation. If it is found that some subnets are in a high-load state for a long time, record them as potential optimization targets, store all the analyzed network information in the database, and generate a statistical report for subsequent network management and subnet division decision-making.

[0093] In one embodiment, as Figure 4 shown, in step S30, that is, based on the network information and the initial network configuration requirements, use an adaptive subnet division algorithm to dynamically divide the address segment to generate the corresponding subnet configuration and dynamic address pool, specifically including:

[0094] S31: According to the global IP address segment in the initial network configuration requirements and the network topology information in the network information, initially divide multiple candidate subnets and determine the candidate subnet scheme.

[0095] Specifically, parse the global IP address segment information to obtain the available IP address range, identify the physical and logical structures of different network regions according to the network topology information, judge the connection relationships between regions and the device deployment situation, calculate a reasonable subnet scale according to the subnet division strategy to ensure that the subnet size meets the requirements of the current network environment. If the fixed subnet division method is used, divide the subnet equally according to the preset address range. If the adaptive subnet division method is used, dynamically adjust the subnet boundary in combination with the network load situation, consider the device location, service flow direction, and link quality during the division process to ensure that the divided subnets can efficiently utilize network resources and avoid address conflicts between different subnets at the same time. Store all the division results as the candidate subnet scheme and record the preliminary configuration information of each subnet, including the address range, gateway, subnet mask, and broadcast address.

[0096] S32: Use the constraint optimization model, combine the device status, traffic load data, and network isolation requirements to screen and optimize the candidate subnet scheme, determine the subnet scale and division boundary, and generate the subnet configuration.

[0097] Specifically, load the candidate subnet solutions, calculate the optimal subnet division solution based on the constraint optimization model, analyze the device status data, filter out the areas with low load to accommodate more terminal devices, and at the same time prevent the subnet scale from continuing to expand in high-load areas. Evaluate the network traffic conditions in different areas in combination with the traffic load data to avoid congestion caused by an overly large subnet scale in high-traffic areas. Determine the isolation level between different subnets based on the network isolation requirements. If some subnets require strong isolation, adjust the subnet boundaries to ensure that direct communication between different address segments is not possible. Apply the constraint optimization algorithm during the optimization process, use heuristic methods to evaluate different division solutions, calculate the resource utilization rate, load balance, and address utilization rate of each solution, filter out the optimal solution that meets the business requirements, finally determine the subnet scale and division boundaries, and store the final subnet configuration data, including the IP address range, gateway, subnet mask, and security policy of each subnet. The objective function of this constraint optimization model maximizes the IP address resource utilization rate and minimizes the subnet load imbalance and tenant isolation violations. The constraint conditions ensure the rationality of subnet division, including restrictions such as IP address continuity, load balance, and tenant isolation. The solution method combines heuristic clustering, particle swarm optimization, or genetic algorithms to search for the optimal solution, and adjusts the solutions that do not meet the constraints through the penalty function method, finally generating an optimized subnet configuration solution.

[0098] S33: According to the subnet configuration, construct a dynamic address pool for each subnet.

[0099] Specifically, parse the finally determined subnet configuration, obtain the address range of each subnet, and calculate the number of available IP addresses. Eliminate special-purpose addresses according to the address allocation policy, including gateway addresses, broadcast addresses, and reserved IP addresses, construct a dynamic address pool, record the list of available IP addresses for each subnet, initialize the address allocation status to ensure that unoccupied IP addresses are in an allocable state, and at the same time configure lease management rules for each dynamic address pool, define the allocation duration of IP addresses and the lease renewal policy. If the utilization rate of the address pool of a certain subnet is relatively high, mark this address pool as a high-load area so that IP addresses in low-load areas can be preferentially allocated during the subsequent DHCP address allocation process. Finally, store all dynamic address pools in the address management database for subsequent DHCP allocation process calls.

[0100] S34: Based on the dynamic address pool, the lease duration in the initial network configuration requirements, the preset service priority, and the isolation requirements, formulate the corresponding IP address allocation policy to obtain the pre-formulated IP address allocation policy, and the pre-formulated IP address allocation policy is used to guide the subsequent DHCP address allocation process.

[0101] Specifically, determine the lease time limits for different types of devices according to the lease duration parameters of the initial network configuration requirements. For example, allocate a longer lease time for fixed terminal devices and a shorter lease time for mobile devices or temporarily connected devices. Define the address allocation priority in combination with the preset service priority information to ensure that critical services are preferentially allocated stable IP addresses. At the same time, adopt a dynamic adjustment mechanism for low-priority services to avoid low-priority services occupying high-value IP resources for a long time. Analyze the network isolation requirements to ensure that the address allocation for different tenants does not cross. If isolation is required between tenants, allocate IP addresses in different address pools respectively and configure corresponding network policies to avoid network conflicts between different tenants. Finally, generate a pre-determined IP address allocation policy and store it in the database for subsequent DHCP address allocation process calls to ensure that the allocation of all IP addresses meets the established business requirements and security policies.

[0102] In one embodiment, as Figure 5 shown, before step S32, that is, before screening and optimizing the candidate subnet solutions by using the constraint optimization model in combination with device status, traffic load data, and network isolation requirements, the method for allocating subnet addresses based on SDN further includes:

[0103] S3201: Collect historical network operation data, where the historical network operation data includes historical IP address usage, device load conditions, network topology change conditions, and traffic load data.

[0104] Specifically, regularly extract IP address usage records from the historical data repository, analyze the change in the usage rate of IP addresses in different time periods, and identify address segments that have not been used for a long time to optimize the configuration of the address pool. Statistically analyze the device load conditions, extract the CPU usage rate, memory occupancy, and historical load trends of each device, and identify high-load areas and long-term low-load areas to provide a reference for subnet optimization. Analyze the historical network topology change conditions, record the device connection change conditions in different time periods, and determine which areas have a higher device access frequency to optimize the subnet division strategy. Extract the historical traffic load data, calculate the traffic occupancy of different subnets during peak periods and low-load periods, identify areas with long-term load imbalance, and store all historical data for subsequent analysis and optimization of the subnet division model.

[0105] S3202: According to the historical network operation data, analyze the subnet resource utilization rate, load balancing situation, and network isolation effect, evaluate the applicability of the existing subnet division strategy, and generate an analysis result.

[0106] Specifically, calculate the resource utilization rate of each subnet based on the historical IP address usage, determine whether there are problems of long-term IP address shortage or address waste in some subnets, analyze the load balancing situation, calculate the load changes of each device at different time periods, evaluate whether the current subnet division strategy can balance network traffic, identify high-load subnets and low-load subnets, and record optimization adjustment suggestions. Combine the network isolation effect to evaluate the traffic interaction between subnets, and judge whether the current network isolation strategy meets the expectations. If unexpected traffic interaction is found between different tenants, record the abnormal situation for subsequent adjustment of the isolation strategy. Finally, generate a subnet optimization report based on all analysis data and store it in the database for subsequent use in optimizing the subnet division strategy.

[0107] S3203: Based on the analysis results, dynamically adjust the parameters of the constraint optimization model. The parameters of the constraint optimization model include subnet division rules, load balancing weights, address pool allocation ratios, and tenant isolation strategies.

[0108] Specifically, parse the subnet optimization report, extract the analysis results of subnet resource utilization rate, load balancing situation, and network isolation effect. Adjust the subnet division rules according to the IP address usage. If some subnets are short of IP addresses for a long time, appropriately increase the IP address range of this subnet. If some subnets waste IP addresses for a long time, reduce the scale of this subnet. Adjust the load balancing weights to ensure that high-load areas can obtain more resources during subnet division and reduce network congestion problems. Optimize the address pool allocation ratio based on historical data to ensure a more balanced distribution of IP address resources between different subnets. If loopholes are found in the tenant isolation strategy, adjust the tenant isolation rules of the constraint optimization model to ensure that the network isolation of different tenants meets business requirements. Finally, store the optimized parameters of the constraint optimization model in the database for subsequent calls during subnet division to improve the dynamic adaptability and resource utilization rate of subnet division.

[0109] In one embodiment, as Figure 6 shown, in step S40, that is, when receiving a DHCP request, select an available IP address from the dynamic address pool and generate a corresponding DHCP response message, specifically including:

[0110] S41: Parse the DHCP request to determine the subnet where the requesting device is located.

[0111] Specifically, receive and parse the DHCP request message, extract the device's MAC address, client identifier, requested IP address, and other relevant fields, query the currently allocated IP address records. If the requesting device has been allocated an IP address before and the lease has not expired, directly confirm its affiliated subnet. If the requesting device has not obtained an IP address or the lease has expired, based on the Option field information in the DHCP request, such as subnet identifier, gateway address, etc., combined with the current network topology information, match the switch, access port, and VLAN information where the device is located, determine the subnet range where the device is located, and store the parsing result in a temporary database for subsequent IP address allocation steps to call.

[0112] S42: Select an available IP address from the dynamic address pool according to the dynamic address pool of the subnet where the requesting device is located and the pre-established IP address allocation policy.

[0113] Specifically, according to the parsed device subnet information, query the dynamic address pool of the corresponding subnet, read the current list of available IP addresses, and according to the pre-established IP address allocation policy, preferentially select the idle addresses of the low-load subnet. If the current subnet has a high load, determine whether cross-subnet allocation is allowed. If it is allowed, search for available addresses in the adjacent subnet. If the MAC address or client identifier of the device matches the historical record, preferentially allocate the IP address that the device has used before to reduce the impact of address changes on the business. If the device belongs to a high-priority service, select the IP address in the low-latency or high-bandwidth subnet according to the service priority information. If the requesting device belongs to a special tenant and the tenant isolation policy requires allocating a specific range of IP addresses, select an available IP address from the reserved address pool of the tenant and mark the allocation status of the address to ensure that it will not be occupied by other devices.

[0114] S43: Determine the network configuration information corresponding to the available IP address according to the lease duration defined in the initial network configuration requirements, the preset service priority, and the network isolation requirements.

[0115] Specifically, according to the lease duration parameter in the initial network configuration requirements, determine the lease validity period of the device. If the device is a fixed terminal or server, allocate a long-term lease; if the device is a temporary access terminal or guest device, allocate a short-term lease. According to the service priority information, determine whether additional network resource guarantee is required. If the device belongs to a high-priority service, such as a video conferencing terminal or a critical service server, enable the QoS policy in the configuration and preferentially allocate network resources with low latency and high bandwidth. According to the network isolation requirements, check whether the IP address belongs to the isolation address pool. If the device belongs to an independent tenant, add access control rules to the allocated configuration to ensure that devices of different tenants cannot communicate directly. Finally, generate complete network configuration information including the IP address, subnet mask, gateway address, DNS server, and lease duration, and store the allocation record of the device for subsequent lease management and renewal processing.

[0116] S44: Generate a corresponding DHCP response message according to the available IP address and network configuration information.

[0117] Specifically, according to the selected available IP address and the determined network configuration information, construct a DHCP Offer message, fill in parameters such as the allocated IP address, subnet mask, default gateway, DNS server address, and lease duration. If the device has confirmed the IP address allocation, include the same configuration information in the DHCP Ack message and set the lease effective time. If the IP address pool is insufficient or the device does not meet the allocation conditions, return a DHCP NAK message to reject the address allocation request. All generated DHCP response messages are subject to integrity verification before being sent to ensure that all fields comply with the DHCP protocol specification, and are broadcast or unicast to the DHCP client of the requesting device through the UDP protocol to complete the address allocation process. At the same time, record the allocation log for subsequent query and management.

[0118] In one embodiment, as Figure 7 shown, the method for allocating a subnet address based on SDN further includes:

[0119] S60: When the lease of the allocated IP address is about to expire, send a lease renewal notice to the corresponding requesting device. If the requesting device does not send a lease renewal request and the online status of the requesting device is not detected after the lease expires, release the allocated IP address and return it to the dynamic address pool.

[0120] Specifically, within a preset time period before the lease is about to expire, a DHCP_Renewal request is sent to the device. If the device responds and requests a renewal, the lease time is updated and the usage status of the device is re-recorded. If the device does not respond, it enters the lease grace period and continues to detect the online status of the device. If no renewal request is received after the grace period ends, the online status of the device is probed through ARP or ICMP_Ping. If the device is still active, it is automatically renewed and the current IP address is retained. If the device does not respond and no traffic activity is detected within multiple detection cycles, the device is determined to be offline, the IP address is released, re-marked as assignable, and the address is returned to the dynamic address pool for new device allocation and use.

[0121] S70: When an IP address that has not been used for a long time is detected or the requested device goes offline, the corresponding IP address is recycled and reallocated according to the preset recycling policy.

[0122] Specifically, the list of assigned IP addresses is scanned periodically to count the usage of each IP address. If a certain IP address does not generate data traffic for a long time and the device does not send a renewal request, it is marked as "recyclable". If the IP address belongs to a device that has been offline for a long time, it is processed according to the recycling policy. If the recycling policy allows immediate recycling, the IP address is directly released and returned to the dynamic address pool. If the recycling policy requires gradual release, it enters the observation period, during which the activity status of the device continues to be detected. If the device is not detected to be back online after the observation period ends, the IP address is forcibly released and the IP binding relationship of the device is removed from the allocation record so that subsequent devices can use this IP address. At the same time, the recycling log is stored for the administrator to review or adjust the recycling policy.

[0123] S80: When a change in business requirements is obtained, the subnet division is dynamically adjusted according to the change in business requirements, and the subnet configuration is adjusted.

[0124] Specifically, listen for change events of business requirements, regularly analyze business traffic data. If it is detected that the traffic of a specific business increases or decreases, then determine whether it is necessary to adjust the subnet range used by this business. If the business traffic continues to grow and the available IP addresses of the current subnet are about to be exhausted, then trigger a subnet expansion operation, adjust the subnet boundary, and add new address blocks to meet the business growth requirements. If the business requirements decline and the utilization rate of the current subnet addresses continues to be lower than the preset threshold, then trigger a subnet contraction operation, recycle some unused IP addresses, and return them to the global address pool to ensure the reasonable allocation of IP address resources. If it is detected that a new business goes online and requires an independent subnet environment, then according to the preset subnet division strategy, automatically generate a new subnet configuration and create a corresponding dynamic address pool to meet the network requirements of the new business. Finally, synchronize the adjusted subnet configuration to network devices and the DHCP server to ensure that all network devices and terminal devices can communicate according to the latest address plan, and store the adjustment log for subsequent analysis and optimization.

[0125] It should be understood that the magnitudes of the sequence numbers of the steps in the above embodiments do not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

[0126] In one embodiment, a system for allocating subnet addresses based on SDN is provided. This system for allocating subnet addresses based on SDN corresponds one-to-one with the method for allocating subnet addresses based on SDN in the above embodiment. As Figure 8 shown, this system for allocating subnet addresses based on SDN includes a requirement acquisition module, a network information collection module, a division module, an address allocation module, and an adjustment module. The detailed description of each functional module is as follows:

[0127] The requirement acquisition module is used to acquire the initial network configuration requirements, and the initial network configuration requirements include the global IP address segment, the subnet division strategy, the lease duration, and the network isolation requirements;

[0128] The network information collection module is used to collect network information in real time, and the network information includes network topology information, device status, and traffic load data;

[0129] The division module is used to dynamically divide the address segment based on the network information and the initial network configuration requirements, and adopt an adaptive subnet division algorithm to generate the corresponding subnet configuration and dynamic address pool;

[0130] The address allocation module is used to, when receiving a DHCP request, select available IP addresses from the dynamic address pool according to the pre-established IP address allocation strategy, generate the corresponding DHCP response message, and send the DHCP response message to the requesting device to complete the address allocation;

[0131] An adjustment module for real-time monitoring of real-time data after address allocation. The real-time data includes IP address usage, device load data, and topology changes, and dynamically adjusts the subnet configuration and dynamic address pool according to the real-time data.

[0132] Optionally, the requirement acquisition module includes:

[0133] A requirement analysis sub-module for receiving network configuration requirement data submitted by a user, analyzing the network configuration requirement data submitted by the user, and extracting a global IP address segment, a subnet division strategy, a lease duration, a network isolation requirement, a preset service priority, and a tenant isolation requirement.

[0134] An integration sub-module for statistically integrating the global IP address segment, the subnet division strategy, the lease duration, the network isolation requirement, the preset service priority, and the tenant isolation requirement to obtain an initial network configuration requirement.

[0135] Optionally, the network information collection module includes:

[0136] A network topology collection sub-module for collecting network topology information within a preset time period. The network topology information includes connection statuses between devices, port information, and link quality data.

[0137] A real-time monitoring status sub-module for real-time monitoring of status data of each network device. The status data includes device running status, CPU and memory load, fault alarms, and key metrics.

[0138] A traffic statistics sub-module for determining the real-time data traffic conditions of each network area through traffic statistics to obtain traffic load data of each node.

[0139] A network integration sub-module for integrating and analyzing the network topology information, device status data, and traffic load data, and statistically obtaining network information.

[0140] Optionally, the division module includes:

[0141] A candidate determination sub-module for preliminarily dividing multiple candidate subnets according to the global IP address segment in the initial network configuration requirement and the network topology information in the network information, and determining a candidate subnet scheme.

[0142] A screening sub-module for screening and optimizing the candidate subnet scheme by using a constraint optimization model, combining device status, traffic load data, and network isolation requirements, determining the subnet scale and division boundary, and generating a subnet configuration.

[0143] An address pool construction sub-module for constructing a dynamic address pool for each subnet according to the subnet configuration.

[0144] A determining allocation policy sub-module, which is used to formulate a corresponding IP address allocation policy based on the lease duration, preset service priority, and isolation requirements in the dynamic address pool and the initial network configuration requirements, to obtain a pre-formulated IP address allocation policy, and the pre-formulated IP address allocation policy is used to guide the subsequent DHCP address allocation process.

[0145] Optionally, this SDN-based subnet address allocation system further includes:

[0146] A historical data collection module, which is used to collect historical network operation data, and the historical network operation data includes historical IP address usage, device load conditions, network topology change conditions, and traffic load data;

[0147] An operation analysis module, which is used to analyze the subnet resource utilization rate, load balancing situation, and network isolation effect according to the historical network operation data, evaluate the applicability of the existing subnet division strategy, and generate an analysis result;

[0148] An optimization model parameter module, which is used to dynamically adjust the parameters of the constraint optimization model based on the analysis result, and the parameters of the constraint optimization model include subnet division rules, load balancing weights, address pool allocation ratios, and tenant isolation strategies

[0149] Optionally, the address allocation module includes:

[0150] A determining subnet sub-module, which is used to parse the DHCP request and determine the subnet where the requesting device is located;

[0151] An address selection sub-module, which is used to select an available IP address in the dynamic address pool according to the dynamic address pool of the subnet where the requesting device is located and the pre-formulated IP address allocation policy;

[0152] A determining network configuration sub-module, which is used to determine the network configuration information corresponding to the available IP address according to the lease duration defined in the initial network configuration requirements, the preset service priority, and the network isolation requirements;

[0153] A message generation sub-module, which is used to generate a corresponding DHCP response message according to the available IP address and the network configuration information.

[0154] Optionally, this SDN-based subnet address allocation system further includes:

[0155] A lease renewal module, which is used to send a lease renewal notice to the corresponding requesting device when the lease of the allocated IP address is about to expire. If the requesting device does not send a lease renewal request and the online status of the requesting device is not detected after the lease expires, the allocated IP address is released and returned to the dynamic address pool;

[0156] A recycling module, which is used to recycle the corresponding IP address according to a preset recycling policy and reallocate it when a long-unused IP address is detected or the requesting device goes offline;

[0157] A partitioning adjustment module, which is used to obtain a change in business requirements and dynamically adjust the subnet partitioning according to the change in business requirements to adjust the subnet configuration.

[0158] For the specific limitations of a subnet address allocation system based on SDN, reference can be made to the limitations of a subnet address allocation method based on SDN in the above text, which will not be elaborated here. Each module in the above-mentioned subnet address allocation system based on SDN can be implemented in whole or in part by software, hardware, and their combination. The above-mentioned modules can be embedded in the processor of the computer device in hardware form or be independent of it, or be stored in the memory of the computer device in software form, so that the processor can call and execute the operations corresponding to the above-mentioned modules.

[0159] Those skilled in the art can clearly understand that, for the convenience and brevity of description, only the above-mentioned division of each functional unit and module is used as an example. In actual applications, the above-mentioned functions can be allocated to different functional units and modules according to needs, that is, the internal structure of the system can be divided into different functional units or modules to complete all or part of the functions described above.

[0160] The above-mentioned embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions recorded in the foregoing embodiments, or perform equivalent replacements for some of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

Claims

1. A method for allocating subnet addresses based on SDN, characterized in that, The described method for allocating subnet addresses based on SDN includes: Obtain the initial network configuration requirements, where the initial network configuration requirements include the global IP address segment, subnet division strategy, lease duration, and network isolation requirements; The obtaining of the initial network configuration requirements includes: The initial network configuration requirements further include the preset service priority and tenant isolation requirements; Receive the network configuration requirement data submitted by the user, parse the network configuration requirement data submitted by the user, and extract the global IP address segment, subnet division strategy, lease duration, network isolation requirements, preset service priority, and tenant isolation requirements; Statistically integrate the global IP address segment, subnet division strategy, lease duration, network isolation requirements, preset service priority, and tenant isolation requirements to obtain the initial network configuration requirements; Collect network information in real time, where the network information includes network topology information, device status, and traffic load data; Based on the network information and the initial network configuration requirements, use an adaptive subnet division algorithm to dynamically divide the address segment and generate the corresponding subnet configuration and dynamic address pool; The using of the adaptive subnet division algorithm to dynamically divide the address segment based on the network information and the initial network configuration requirements to generate the corresponding subnet configuration and dynamic address pool includes: According to the global IP address segment in the initial network configuration requirements and the network topology information in the network information, initially divide multiple candidate subnets and determine the candidate subnet plan; Use a constraint optimization model, combine the device status, traffic load data, and network isolation requirements to screen and optimize the candidate subnet plan, determine the subnet scale and division boundary, and generate the subnet configuration; According to the subnet configuration, construct a dynamic address pool for each subnet; Based on the dynamic address pool and the lease duration, preset service priority, and isolation requirements in the initial network configuration requirements, formulate the corresponding IP address allocation policy to obtain the pre-formulated IP address allocation policy, and the pre-formulated IP address allocation policy is used to guide the subsequent DHCP address allocation process; When receiving a DHCP request, select an available IP address from the dynamic address pool according to the pre-formulated IP address allocation policy, generate the corresponding DHCP response message, and send the DHCP response message to the requesting device to complete the address allocation; Monitor the real-time data after address allocation in real time, where the real-time data includes the IP address usage, device load data, and topology changes, and dynamically adjust the subnet configuration and dynamic address pool according to the real-time data.

2. The allocation method of a subnet address based on SDN according to claim 1, characterized in that The real-time collection of network information includes: Collect the network topology information within a preset time period, where the network topology information includes the connection status between devices, port information, and link quality data; Monitor the status data of each network device in real time, where the status data includes the device running status, CPU and memory load, fault alarm, and key indicators; Determine the real-time data traffic conditions of each network area through traffic statistics to obtain the traffic load data of each node; Integrate and analyze the network topology information, device status data, and traffic load data to statistically obtain the network information.

3. The allocation method of a subnet address based on SDN according to claim 1, characterized in that, Before screening and optimizing the candidate subnet solutions using the constraint optimization model in combination with the device status, traffic load data, and network isolation requirements, the method for allocating subnet addresses based on SDN further includes: Collect historical network operation data, where the historical network operation data includes historical IP address usage, device load conditions, network topology changes, and traffic load data; Analyze the subnet resource utilization rate, load balancing situation, and network isolation effect based on the historical network operation data, evaluate the applicability of the existing subnet division strategy, and generate an analysis result; Dynamically adjust the parameters of the constraint optimization model based on the analysis result, where the parameters of the constraint optimization model include subnet division rules, load balancing weights, address pool allocation ratios, and tenant isolation strategies.

4. The allocation method of a subnet address based on SDN according to claim 1, characterized in that, When receiving a DHCP request, selecting an available IP address from the dynamic address pool and generating a corresponding DHCP response message includes: Parse the DHCP request to determine the subnet where the requesting device is located; Select an available IP address from the dynamic address pool according to the dynamic address pool of the subnet where the requesting device is located and the pre-defined IP address allocation strategy; Determine the network configuration information corresponding to the available IP address according to the lease duration defined in the initial network configuration requirements, the preset service priority, and the network isolation requirements; Generate the corresponding DHCP response message according to the available IP address and the network configuration information.

5. The allocation method of a subnet address based on SDN according to claim 1, characterized in that, The method for allocating subnet addresses based on SDN further includes: When the lease of the allocated IP address is about to expire, send a lease renewal notice to the corresponding requesting device. If the requesting device does not send a lease renewal request and the online status of the requesting device is not detected after the lease expires, release the allocated IP address and return it to the dynamic address pool; When detecting an IP address that has not been used for a long time or the requesting device is offline, recycle the corresponding IP address according to the preset recycling strategy and re-allocate it; Obtain a change in business requirements, and dynamically adjust the subnet division according to the change in business requirements to adjust the subnet configuration.

6. A subnet address allocation system based on SDN, characterized in that, The system for allocating subnet addresses based on SDN includes: A requirement acquisition module for acquiring initial network configuration requirements, where the initial network configuration requirements include a global IP address segment, a subnet division strategy, a lease duration, and network isolation requirements; A network information collection module for real-time collecting network information, where the network information includes network topology information, device status, and traffic load data; A division module for dynamically dividing the address segment using an adaptive subnet division algorithm based on the network information and the initial network configuration requirements, and generating corresponding subnet configurations and a dynamic address pool; An address allocation module, which is used to select an available IP address from the dynamic address pool according to a pre-established IP address allocation policy when receiving a DHCP request, generate a corresponding DHCP response message, and send the DHCP response message to the requesting device to complete address allocation; An adjustment module, which is used to monitor the real-time data after address allocation in real time. The real-time data includes IP address usage, device load data, and topology changes, and dynamically adjusts the subnet configuration and the dynamic address pool according to the real-time data; The requirement acquisition module includes: A requirement parsing sub-module, which is used to receive the network configuration requirement data submitted by the user, parse the network configuration requirement data submitted by the user, and extract the global IP address segment, subnet division strategy, lease duration, network isolation requirement, preset service priority, and tenant isolation requirement; An integration sub-module, which is used to statistically integrate the global IP address segment, subnet division strategy, lease duration, network isolation requirement, preset service priority, and tenant isolation requirement to obtain the initial network configuration requirement; The division module includes: A candidate determination sub-module, which is used to preliminarily divide multiple candidate subnets according to the global IP address segment in the initial network configuration requirement and the network topology information in the network information, and determine a candidate subnet scheme; A screening sub-module, which is used to use a constraint optimization model, combine the device status, traffic load data, and network isolation requirement, screen and optimize the candidate subnet scheme, determine the subnet scale and division boundary, and generate the subnet configuration; An address pool construction sub-module, which is used to construct a dynamic address pool for each subnet according to the subnet configuration; An allocation policy determination sub-module, which is used to formulate a corresponding IP address allocation policy based on the dynamic address pool, the lease duration, the preset service priority, and the isolation requirement in the initial network configuration requirement, and obtain the pre-established IP address allocation policy. The pre-established IP address allocation policy is used to guide the subsequent DHCP address allocation process.

Images