IP address allocation methods, devices, equipment, media and products

By obtaining the server's allocation demand information, the system automatically selects unused IP addresses from preset network segments, solving the problems of high cost and human error associated with manually allocating IP addresses and achieving efficient and accurate IP address allocation.

CN123123315APending Publication Date: 2026-11-17INDUSTRIAL AND COMMERCIAL BANK OF CHINA
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611505800.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-09-24
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

The existing method of manually assigning IP addresses consumes a lot of manpower, increases the workload of operation and maintenance personnel, and is difficult to avoid human error.

Method used

By obtaining server allocation requirements information, including application, number of IP addresses, pre-production status, load balancing type, etc., the system automatically selects unused IP addresses from preset network segments for allocation.

Benefits of technology

It automates IP address allocation, significantly improving the accuracy and efficiency of allocation, reducing labor costs, and minimizing the risk of human error.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123123315A_ABST
    Figure CN123123315A_ABST
Patent Text Reader

Abstract

This application provides an IP address allocation method, apparatus, device, medium, and product, relating to the fields of fintech or artificial intelligence. First, it acquires allocation request information from servers whose IP addresses are to be allocated. This information includes the application to which the server belongs, the number of IP addresses required, whether it is in pre-production mode, whether load balancing is being performed and the type of load balancing, and whether the new IP address is based on a region or references a specific server's IP address. Then, based on this request information, a target network segment is intelligently determined from multiple preset network segments, and unused IP addresses are further selected from this target network segment for allocation. This method effectively solves the problems of existing manual IP address allocation methods, which not only consume a lot of manpower and increase the workload of users, but also are difficult to avoid human error. It thus achieves automated IP address allocation, significantly improving the accuracy of IP address allocation.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the fields of financial technology or artificial intelligence, and in particular to an IP address allocation method, apparatus, device, medium and product. Background Technology

[0002] In the information age, servers play a crucial role as core devices for data processing and storage. A server's IP address is not only its unique identifier on the network but also key to enabling data transmission and resource sharing. Through proper IP address planning, servers can communicate efficiently with other devices, ensuring accurate data transmission and stable system operation.

[0003] In existing technologies, server IP address allocation is usually done manually. This means that maintenance personnel need to manually assign a suitable IP address to each server based on its physical location, region, and other relevant information, as well as by referring to the ledger information table and relying on their own experience and historical records.

[0004] However, with the development of large-scale distributed systems and the continuous expansion of network scale, the existing method of manually allocating IP addresses not only consumes a lot of manpower and increases the workload of operation and maintenance personnel, but also faces the problem of unavoidable human operation errors. Summary of the Invention

[0005] This application provides an IP address allocation method, apparatus, device, medium, and product to solve the problems that existing manual IP address allocation methods consume a lot of manpower, increase the workload of operation and maintenance personnel, and face the technical problem of unavoidable human operation errors.

[0006] Firstly, this application provides an IP address allocation method, including:

[0007] Obtain the allocation requirement information of the server to be assigned an IP address. The allocation requirement information includes one or more of the following: the application to which the server belongs, the number of IP addresses to be assigned, whether the IP addresses to be assigned are pre-production, whether the IP addresses to be assigned are load-balanced and the type of load balancing, and whether the new type of the IP address to be assigned is a region or reference server IP address.

[0008] Based on the allocation requirement information, a target network segment is determined from a set of preset network segments, and an unused IP address is selected from the target network segment as the IP address to be allocated this time.

[0009] Secondly, this application provides an IP address allocation device, comprising:

[0010] The acquisition module is used to acquire the allocation requirement information of the server to be allocated IP address. The allocation requirement information includes one or more of the following: the application to which the server belongs, the number of IP addresses to be allocated, whether the IP addresses to be allocated are pre-production, whether the IP addresses to be allocated are load balanced and the type of load balancing, and the type of new IP address to be allocated is a region or reference server IP address.

[0011] The determination module is used to determine the target network segment from a set of preset network segments based on the allocation requirement information, and select an unused IP address from the target network segment as the IP address to be allocated this time.

[0012] Thirdly, embodiments of this application provide an IP address allocation device, including: a memory and a processor;

[0013] The memory stores computer-executed instructions;

[0014] The processor executes computer execution instructions stored in the memory, causing the processor to perform the first aspect and / or various possible implementations of the first aspect as described above.

[0015] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the first aspect and / or various possible implementations of the first aspect.

[0016] Fifthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the first aspect and / or various possible implementations of the first aspect.

[0017] The IP address allocation method, apparatus, device, medium, and product provided in this application first obtain the allocation requirement information of the server whose IP addresses are to be allocated. This information includes the application to which the server belongs, the number of IP addresses to be allocated, whether it is pre-production deployed, whether load balancing is performed and the type of load balancing, and whether the type of new IP address is based on a region or references a specific server's IP address. Then, based on this requirement information, a target network segment is intelligently determined from multiple preset network segments, and unused IP addresses are further selected from this target network segment for allocation. This method effectively solves the problems of existing manual IP address allocation methods, which not only consume a lot of manpower and increase the workload of users, but also are difficult to avoid human error. It thus achieves automated IP address allocation, significantly improving the accuracy of IP address allocation. Attached Figure Description

[0018] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0019] Figure 1 Flowchart of the IP address allocation method provided in this application Figure 1 ;

[0020] Figure 2 Flowchart of the IP address allocation method provided in this application Figure 2 ;

[0021] Figure 3 Flowchart of the IP address allocation method provided in this application Figure 3 ;

[0022] Figure 4 Flowchart of the IP address allocation method provided in this application Figure 4 ;

[0023] Figure 5 Flowchart of the IP address allocation method provided in this application Figure 5 ;

[0024] Figure 6 Flowchart of the IP address allocation method provided in this application Figure 6 ;

[0025] Figure 7 A schematic diagram of the IP address allocation device provided in this application;

[0026] Figure 8 A schematic diagram of the IP address allocation device provided in this application.

[0027] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0028] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0029] It should be noted that the IP address allocation method, apparatus, device, medium and product provided in this application can be used in the fields of fintech or artificial intelligence, or in any field other than fintech or artificial intelligence. This application does not limit the application fields of the IP address allocation method, apparatus, device, medium and product.

[0030] With the continuous advancement of information technology and the booming development of Internet applications, servers, as core devices for data storage, processing, and transmission, are seeing a continuous expansion in number and network scale. Servers need to be assigned addresses to ensure that each device has a unique identity in the network, thereby achieving efficient data communication and resource sharing.

[0031] The existing method for allocating IP addresses to servers is manual. This means that maintenance personnel manually identify the physical location, region, and other relevant information of the servers, and, based on their experience and historical records, assign a suitable IP address to each server one by one.

[0032] However, with the development of large-scale distributed systems and the continuous expansion of network scale, the existing method of manually allocating IP addresses not only consumes a lot of manpower and increases the workload of operation and maintenance personnel, but also faces the problem of unavoidable human operation errors.

[0033] To address the aforementioned issues, this application provides an IP address allocation method. First, it obtains the allocation request information of the server whose IP addresses are to be allocated. This information includes the application to which the server belongs, the number of IP addresses required, whether it is in pre-production mode, whether load balancing is implemented and the type of load balancing, and whether the new IP address is based on a region or references a specific server's IP address. Then, based on this request information, it intelligently determines the target network segment from multiple preset network segments, and further selects unused IP addresses from this target network segment for allocation. This method effectively solves the problems of existing manual IP address allocation methods, which not only consume a lot of manpower and increase the user's workload but also are difficult to avoid human error. It thus achieves automated IP address allocation, significantly improving the accuracy of IP address allocation.

[0034] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0035] Figure 1 Flowchart of the IP address allocation method provided in this application Figure 1 .like Figure 1 As shown, the method includes:

[0036] S101. Obtain the allocation requirement information of the server to be assigned an IP address. The allocation requirement information includes one or more of the following: the application to which the server belongs, the number of IP addresses to be assigned, whether the IP addresses to be assigned are pre-production, whether the IP addresses to be assigned are load-balanced and the type of load balancing, and whether the new type of the IP addresses to be assigned is a region or reference server IP address.

[0037] The application to which a server belongs indicates the specific business that the server needs to support or run. Different servers support different businesses, and different businesses have different IP address requirements. For example, a data management platform may need a large number of IP addresses to support high-concurrency access, while an internal management system may need fewer IP addresses.

[0038] The number of IP addresses to be allocated indicates how many IP addresses need to be allocated. For example, suppose the server currently needs to support the operation of 100 virtual machines, then it may be necessary to allocate a separate IP address to each virtual machine. Therefore, the number of IP addresses to be allocated would be 100.

[0039] Whether the IP addresses to be allocated are for pre-production or for testing purposes refers to whether these IP addresses are intended for the full production environment or a test production environment. Pre-production environments are typically used to test server performance and stability before going live. For example, if the server is intended for development and testing, the allocated IP addresses are pre-production, used for performance testing before official deployment.

[0040] Whether the IP addresses to be assigned should be load balanced refers to whether these IP addresses need to be configured on a load balancer. For example, if the server is used to handle a large number of concurrent requests, then these IP addresses may need to be configured on a load balancer to distribute the request processing.

[0041] Load balancing types include, but are not limited to: existing load balancing and new load balancing. New load balancing can be further categorized into: load balancing pools and regional load balancing.

[0042] The new type of IP address to be assigned refers to the method of determining the new IP address. One method is to determine it based on a specific region, and the other method is to determine it based on the IP addresses of existing servers.

[0043] The purpose of obtaining the allocation requirements for the IP addresses to be assigned in this step is to ensure that the allocation of IP addresses can meet the specific needs of the server and the network architecture.

[0044] Understandably, by determining the application to which the server belongs, the number of IP addresses to be allocated, whether it is for pre-production deployment, whether load balancing is being implemented, and the type of load balancing, IP addresses can be allocated more accurately, avoiding resource waste and conflicts. Furthermore, determining the allocation method based on the type of new IP addresses also helps ensure the stability and scalability of the network architecture.

[0045] The method for obtaining the server's IP address to be assigned in this step can be as follows: The user first operates through the visual interface of the dynamic server IP allocation tool. On this interface, the user needs to input relevant allocation requirements, including but not limited to the application type of the server, the number of IP addresses to be allocated, whether it is in the pre-production stage, whether load balancing is required and its specific type, and whether the new IP addresses are determined based on a specific region or by referencing existing server IP addresses. Once the user completes and submits this information, the dynamic server IP allocation tool will immediately obtain this allocation requirement information and perform the subsequent IP address allocation work accordingly.

[0046] S102. Based on the allocation requirement information, determine the target network segment from multiple preset network segments, and select an unused IP address from the target network segment as the IP address to be allocated this time.

[0047] Different allocation requirements correspond to different target network segments. For example, if the allocation requirement includes the application to which the server belongs, the number of IP addresses to be allocated, and the IP addresses to be allocated are for pre-production use, the target network segment could be network segment A; if the allocation requirement includes the application to which the server belongs, the number of IP addresses to be allocated, and the IP addresses to be allocated are not load-balanced, the target network segment could be network segment B; if the allocation requirement includes the application to which the server belongs, the number of IP addresses to be allocated, and the IP addresses to be allocated are load-balanced and are existing load balancers, the target network segment could be network segment C; and if the allocation requirement includes the application to which the server belongs, the number of IP addresses to be allocated, and the IP addresses to be allocated are load-balanced and are part of a load balancing pool, the target network segment could be network segment D.

[0048] The purpose of this step, determining the target network segment from a set of preset network segments based on allocation requirements, is to filter out network segments that meet the allocation requirements and use them as the target network segment. Furthermore, selecting unused IP addresses from the target network segment as the IP addresses for this allocation is to avoid IP address conflicts and waste.

[0049] Understandably, in the process of IP address allocation, the first step is to select network segments that meet the allocation requirements from a set of pre-defined network segments and establish them as target network segments. Next, to ensure that the allocated IP addresses do not cause network conflicts or communication failures, IP addresses that are not currently in use by other devices must be selected from the target network segments for allocation.

[0050] The IP address allocation method provided in this application first obtains various allocation requirement information of the server whose IP address needs to be allocated. This information includes, but is not limited to, the application type of the server, the number of IP addresses required, whether it is in the pre-production stage, whether load balancing is required and its specific type, and whether the new IP address is determined based on a specific region or by referring to the IP addresses of existing servers. Subsequently, based on this detailed requirement information, the method intelligently filters the most suitable target network segment from multiple pre-defined network segments, and further selects unoccupied IP addresses in the target network segment for allocation. This method effectively solves the problems of traditional manual IP address allocation, which not only consumes a lot of manpower and increases the workload of users, but also makes it difficult to completely avoid human error. Therefore, it significantly improves allocation efficiency and accuracy, effectively reduces manpower costs, and greatly reduces potential risks caused by human error.

[0051] Figure 2 Flowchart of the IP address allocation method provided in this application Figure 2 ,like Figure 2 As shown, in this embodiment... Figure 1 Based on the embodiments, the IP address allocation method is described in detail, which includes:

[0052] S201. Obtain the allocation requirement information of the server to be assigned an IP address. The allocation requirement information includes one or more of the following: the application to which the server belongs, the number of IP addresses to be assigned, whether the IP addresses to be assigned are pre-production, whether the IP addresses to be assigned are load-balanced and the type of load balancing, and whether the new type of the IP addresses to be assigned is a region or reference server IP address.

[0053] The explanation of step S201 is similar to that of step S201 above, and will not be repeated here.

[0054] S202. If the IP address to be allocated is in pre-production mode, and the new type of the IP address to be allocated is a region, then the first pre-production network segment corresponding to the first region input by the user is determined from multiple preset network segments, and the first pre-production network segment is determined as the target network segment.

[0055] The first pre-production network segment is a network segment pre-configured within the first region, specifically designed for allocating IP addresses in the pre-production environment. For example, assuming the first region is numbered 001, the system can determine the first pre-production network segment within that region as 192.168.1.0 / 24 based on region number 001.

[0056] When it is determined that the IP addresses to be allocated are for pre-production use and the new type of the IP addresses to be allocated is a region, it means that when allocating IP addresses this time, not only must the specific needs of the pre-production environment be fully met, but the allocation must also follow the region range specified by the user.

[0057] Understandably, in the IP address allocation scenario, if the IP addresses to be allocated are in the pre-production stage and the new type of these IP addresses is tagged as a region, then the system will first search for the first pre-production network segment corresponding to the region selected by the user from multiple preset network segments, and then determine this found network segment as the target network segment for subsequent IP address allocation.

[0058] S203. If the new type of the IP address to be allocated is a reference server IP address, then determine the second region to which the first reference server IP address entered by the user belongs, and determine the second pre-production network segment corresponding to the second region from multiple preset network segments, and determine the second pre-production network segment as the target network segment.

[0059] The second pre-production network segment is a network segment pre-configured within the second area and specifically used for allocating IP addresses in the pre-production environment. For example, assuming the second area is numbered 002, the system can determine the second pre-production network segment within that area as 192.168.2.0 / 24 based on the area numbered 002.

[0060] When it is determined that the IP address to be allocated is for pre-production and the new type of the IP address to be allocated is a reference server IP address, it means that when allocating IP addresses, the system needs to consider two key factors at the same time: first, it must fully meet the specific needs of the pre-production environment to ensure the stable operation of the production environment; second, it must allocate IP addresses according to the region corresponding to the reference server IP address specified by the user to ensure the reasonable layout and effective management of IP addresses.

[0061] As is understandable, a reference server IP address is the IP address used by a specific server, and it usually corresponds to a specific region. Therefore, when the system receives the first reference server IP address entered by the user, it will first determine the corresponding region based on this IP address, which is called the second region. Next, the system will find a range of IP addresses specifically reserved for the pre-production environment within this second region to ensure that there are enough suitable IP addresses available for allocation in this environment.

[0062] S204. Determine at least one first candidate network segment from multiple preset network segments based on the allocation demand information.

[0063] The first candidate network segment differs depending on the allocation demand information. The first candidate network segment can include several scenarios:

[0064] (1) When the allocation requirement information is that the IP address to be allocated is not load balanced, and the new type of the IP address to be allocated is a region, the first candidate network segment is at least one network segment obtained after removing the network segments labeled as virtual server and real server in the region.

[0065] (2) When the allocation requirement information is that the IP address to be allocated is not load balanced, and the new type of the IP address to be allocated is a reference server IP address, the first candidate network segment is at least one network segment obtained after removing all other network segments labeled as virtual servers or real servers within the area to which the IP address belongs, where there are no unused IP addresses in the network segment corresponding to the IP address. The first candidate network segment also includes the network segment corresponding to the IP address when there are used IP addresses within the network segment corresponding to the IP address.

[0066] (3) When the allocation requirement information is to load balance the IP address to be allocated, the load balancing type is existing load balancing, and the new type of the IP address to be allocated is a region, when the first candidate network segment matches the region entered by the user and the region to which the virtual server address entered by the user belongs, at least one network segment labeled as a real server is found from the region entered by the user.

[0067] (4) When the allocation requirement information is to load balance the IP address to be allocated, the load balancing type is existing load balancing, and the new type of the IP address to be allocated is a reference server IP address, if the user enters a virtual server IP address, the first candidate network segment is at least one network segment labeled as a real server found within the region to which the reference server IP address belongs, when the region to which the user-entered reference server IP address belongs matches the region to which the user-entered virtual server address belongs. Conversely, if the user does not enter a virtual server IP address, at least one network segment labeled as a virtual server is found within the region to which the user-entered reference server IP address belongs, and if the virtual server IP address to be allocated is found from at least one network segment of the virtual server, at least one network segment labeled as a real server associated with the virtual server IP address to be allocated is found.

[0068] (5) When the allocation requirement information is to load balance the IP address to be allocated, the load balancing type is new load balancing, and the new type of the IP address to be allocated is a region, the first candidate network segment is to find at least one network segment labeled as a real server from the region input by the user, and when the real server IP address to be allocated is found from at least one network segment corresponding to the real server, the first candidate network segment is to find at least one network segment labeled as a virtual server associated with the real server IP address to be allocated.

[0069] (6) When the allocation requirement information is to load balance the IP address to be allocated, the load balancing type is new load balancing, and it is a regional load balancing, and the new type of the IP address to be allocated is a reference server IP address, if there is no unused IP address in the network segment corresponding to the IP address, then the first candidate network segment is at least one network segment labeled as a real server found in other network segments besides the network segment corresponding to the IP address within the region to which the IP address belongs, and if the real server IP address to be allocated is found in at least one real server network segment, then at least one network segment labeled as a virtual server found in the region associated with the real server IP address to be allocated. Conversely, if there is an unused IP address in the network segment corresponding to the IP address, then the first candidate network segment is the network segment labeled as a real server in the network segment corresponding to the IP address, and if the real server IP address to be allocated is found in the network segment labeled as a real server, then at least one network segment labeled as a virtual server found in the region associated with the real server IP address to be allocated.

[0070] (7) When load balancing is performed on the IP address to be allocated, and the load balancing type is new load balancing and is a load balancing pool, the first candidate network segment is the network segment labeled as virtual server found from the application level to which the server belongs, and the network segment labeled as real server found when the virtual server IP address to be allocated is found in the network segment of the virtual server.

[0071] S205. Based on the network segment identifier of the application to which the server belongs, determine at least one first deployment network segment that matches the network segment identifier from at least one first candidate network segment.

[0072] The network segment identifier is used to distinguish the network segment area to which different network devices or servers belong. For example, network segment identifier 1 and network segment identifier 2 both represent the network segment area to which the server belongs, while network segment identifier 3 and network segment identifier 4 both represent the network segment area to which network devices (such as switches, routers, etc.) belong.

[0073] The purpose of this step is to select deployment network segments that match the network segment identifiers of the application to which the server belongs from a pre-determined first candidate network segments.

[0074] Understandably, the first candidate network segment includes both the network segment area to which the server belongs and the network segment area to which the network device belongs. However, when allocating IP addresses for the server, it is not necessary to consider the entire first candidate network segment. Therefore, it is necessary to determine at least one first deployment network segment that matches the network segment identifier of the application to which the server belongs from at least one first candidate network segment based on the network segment identifier of the application to which the server belongs.

[0075] S206. If at least one first network segment exists in at least one first deployment network segment, and at least one IP address in the first network segment has been assigned to the application to which the server belongs, then the network segment with the highest usage rate in at least one first network segment shall be determined as the target network segment.

[0076] The purpose of determining whether at least one first deployment network segment exists is to determine whether any first deployment network segment has pre-assigned IP addresses to the application to which the server belongs.

[0077] If at least one first deployment network segment exists, it indicates that a first deployment network segment has pre-assigned IP addresses to the application to which the server belongs. Therefore, it is necessary to find the deployment network segment with the highest usage rate from all deployment network segments that have assigned IP addresses to the application to which the server belongs, and determine it as the target network segment.

[0078] Understandably, when assessing network configuration, it's necessary to first confirm whether at least one primary deployment network segment has been pre-assigned IP addresses to the server's application. If such a primary deployment network segment exists, it means that some IP address resources have already been pre-allocated to the server application. In this case, to effectively utilize resources and avoid conflicts, the segment with the highest usage rate among these allocated primary deployment network segments needs to be selected as the target network segment for subsequent server deployment or IP address management.

[0079] In this step, for example, it can be first determined whether a first network segment exists in at least one first deployment network segment. Then, if it is determined that at least one first network segment exists, the utilization rate of at least one network segment is determined. Finally, from at least one network segment, the network segment with the highest utilization rate is determined as the target network segment.

[0080] The utilization rate is determined based on the total number of IP addresses in the first network segment and the number of IP addresses allocated to it. For example, if the total number of IP addresses in the first network segment is 100 and the number of IP addresses allocated to it is 40, then the utilization rate of the first network segment can be determined to be 40%.

[0081] S207. If at least one of the first deployment network segments does not exist, then the network segment with the highest utilization rate of at least one first deployment network segment shall be determined as the target network segment.

[0082] If at least one of the first deployment network segments does not exist, it indicates that no first deployment network segment has been pre-assigned an IP address to the application to which the server belongs. Therefore, it is necessary to find the deployment network segment with the highest usage rate from the first deployment network segments and determine it as the target network segment.

[0083] Understandably, during network configuration, it's necessary to first confirm whether a primary deployment network segment has been pre-assigned IP addresses to the server's application. If such a primary deployment network segment doesn't exist, it means no primary deployment network segment has been pre-assigned to the server's application. In this case, to ensure the server can successfully access the network and obtain an IP address, the most frequently used primary deployment network segment needs to be selected as the target network segment for subsequent IP address allocation and server deployment.

[0084] In this step, for example, it can be first determined whether a first network segment exists in at least one first deployment network segment. Then, if it is determined that at least one first network segment does not exist, the utilization rate of at least one deployment network segment is determined. Finally, from at least one deployment network segment, the network segment with the highest utilization rate is determined as the target network segment.

[0085] The utilization rate is determined based on the total number of IP addresses in the first deployment segment and the number of IP addresses allocated to it. For example, if the total number of IP addresses in the first deployment segment is 254 and the number of IP addresses allocated to it is 120, then the utilization rate of the first segment can be determined to be approximately 47%.

[0086] S208. Divide the target network segment into multiple IP addresses. For each IP address, determine whether the IP address is in use. If the IP address is not in use, then determine the IP address to be allocated this time, until the number of IP addresses to be allocated and the number of IP addresses to be allocated this time are determined.

[0087] This step of splitting the target network segment into multiple IP addresses is for more granular management and allocation of network resources. A large target network segment contains many IP addresses; by splitting it, IP addresses can be allocated more flexibly according to actual needs, avoiding resource waste and conflicts, and also facilitating subsequent maintenance and management.

[0088] For each IP address, the purpose of determining whether the IP address is in use is to ensure that the IP address to be assigned is valid and not occupied by other servers.

[0089] Understandably, in a network environment, an IP address is a unique identifier for device communication. If an assigned IP address is already in use by another server, it will cause an IP conflict, affecting the normal operation of the network. Therefore, before assigning an IP address, it is necessary to determine whether it has already been used to ensure that the assigned IP address is available and unique.

[0090] If an IP address is already in use, it means that the IP address is not valid and has been occupied by another server. Therefore, the IP address cannot be used as the IP address for this allocation.

[0091] If an IP address is not in use, it means that the IP address is valid and not occupied by other servers. Therefore, the IP address can be used as the IP address for this allocation.

[0092] For example, suppose there is a target network segment 192.168.1.0 / 24, from which 5 IP addresses need to be allocated to the server. First, this network segment is split into 256 individual IP addresses (from 192.168.1.0 to 192.168.1.255). Then, by scanning or querying devices in the network, each of these IP addresses is checked to see if it is already in use, thus determining that the five IP addresses 192.168.1.1, 192.168.1.2, 192.168.1.3, 192.168.1.5, and 192.168.1.10 are unused.

[0093] Optionally, after determining the number of IP addresses to be allocated and the IP addresses to be allocated in this round, in order to ensure more accurate management and identification of IP addresses, the system also needs to update the label of each allocated IP address so as to avoid re-allocating these already allocated IP addresses in subsequent IP allocation processes.

[0094] Optionally, this application provides a method for detecting used IP addresses, including: first, verifying whether the used IP address is in a normal operating state; second, if it is determined that a used IP address is not in a normal operating state, determining the abnormal runtime of the used IP address; then, determining whether the abnormal runtime of the used IP address is greater than a preset abnormal runtime; and finally, if it is determined that the abnormal runtime of the used IP address is greater than the preset abnormal runtime, updating the used IP address to an unused state.

[0095] Understandably, verifying the operational status of IP addresses first allows for the timely detection and resolution of potential issues, ensuring network stability and reliability. When an IP address is detected as not operating normally, determining its abnormal runtime and comparing it to a preset abnormal runtime helps accurately identify IP addresses that have been unable to function properly for extended periods. Finally, once the abnormal runtime is determined to exceed a preset range, these IP addresses are updated to an unused state. This not only avoids resource waste but also facilitates subsequent IP address reallocation and troubleshooting, thereby optimizing network resource allocation and utilization efficiency.

[0096] The IP address allocation method provided in this application first obtains the allocation requirement information of the server whose IP address is to be allocated. This information includes the application to which the server belongs, the number of IP addresses to be allocated, whether it is pre-deployed, whether it is load-balanced and its type, and the new type (based on region or reference server IP address). Then, based on different allocation requirement information, different processing strategies are determined: on the one hand, if it is determined that the IP address to be allocated is to be pre-deployed, the system will determine the target network segment corresponding to the new type of the IP address to be allocated; on the other hand, based on the allocation requirement information, at least one first candidate network segment is filtered from multiple network segments, and further filtered according to the network segment identifier of the application to which the server belongs to, a matching first deployment network segment is selected. If the existing deployment network segment contains a network segment already allocated to the same application (i.e., the first network segment), the network segment with the highest usage rate is selected as the target; if there is no such network segment, the deployment network segment with the highest usage rate is selected as the target. Finally, the system splits the target network segment into multiple IP addresses and checks their usage one by one to ensure that unused IP addresses are allocated until the number of IP addresses to be allocated is met. This method not only significantly reduces labor costs and alleviates the workload of maintenance personnel, but also effectively avoids human error and improves the accuracy and efficiency of IP address allocation.

[0097] Figure 3 Flowchart of the IP address allocation method provided in this application Figure 3 ,like Figure 3 As shown, in this embodiment... Figure 2 Based on the embodiments, and without load balancing of the IP addresses to be allocated, the implementation process of determining at least one first candidate network segment from a preset number of network segments according to allocation requirement information is described in detail. The method includes:

[0098] S301. If the new type of the IP address to be allocated is a region, then determine the first region network segment corresponding to the third region input by the user from multiple preset network segments, and remove the network segments labeled as virtual server and real server in the first region network segment to obtain at least one first candidate network segment.

[0099] The new types of IP addresses to be assigned include: Zone and Reference Server IP Address. A Zone is a geographical or logical region selected by the user through the interface of the tool for dynamically assigning server IP addresses. A Reference Server IP Address is a specific server IP address manually entered by the user in the tool; the system uses this IP address to determine the zone to which the IP address to be assigned belongs.

[0100] Different third regions correspond to different first region network segments. For example, if the third region is numbered 003, the first region network segment is 192.1.3.0 / 24; if the third region is numbered 004, the first region network segment is 192.1.4.0 / 24.

[0101] Virtual Server (VS): Responsible for receiving requests from clients and distributing them to a set of backend physical servers according to a pre-defined scheduling algorithm. The VS plays a crucial role in the overall load balancing architecture because it not only schedules and manages requests but also ensures load balancing and high availability of the backend servers. A VS is typically configured with one or more Virtual IP addresses (VIPs), which are the target addresses of client requests.

[0102] Real Servers (RS): RSs are the machines that actually execute client requests, providing specific services such as web services, email services, and file transfer services. RSs receive requests from Visual Studios (VS), process these requests, and return the processing results to the VS, which then sends the results to the client. The performance and number of RSs directly affect the processing capacity and scalability of the entire load balancing system. In a load balancing architecture, RSs are typically configured with private IP addresses (RIPs), which are visible within the internal network but hidden from the outside world.

[0103] When it is determined that the IP addresses to be allocated will not be load balanced, and the new type of the IP addresses to be allocated is a region, it means that when allocating IP addresses this time, not only should these addresses be avoided from being associated with the load balancer, but the allocation should also follow the region range specified by the user.

[0104] Understandably, during the IP address allocation process, if the addresses to be allocated are explicitly not intended for load balancing, and the new type of these IP addresses is specified as a region, then the system will first follow the user-specified region range when allocating IP addresses. At the same time, these IP addresses will not be configured to the load balancer.

[0105] S302. If the new type of the IP address to be assigned is a reference server IP address, then determine the fourth region to which the second reference server IP address entered by the user belongs, and determine the second region network segment corresponding to the fourth region from multiple preset network segments.

[0106] The second area network segment corresponds to different fourth areas. For example, if the fourth area is numbered 005, the second area network segment is 192.1.5.0 / 24; if the fourth area is numbered 006, the second area network segment is 192.1.6.0 / 24.

[0107] When it is determined that the IP addresses to be allocated will not be load balanced, and the new type of the IP addresses to be allocated is a reference server IP address, it means that when allocating IP addresses this time, not only should these addresses be avoided from being associated with the load balancer, but the allocation should also follow the zone corresponding to the reference server IP address specified by the user.

[0108] Understandably, during the IP address allocation process, if the system has determined that the addresses to be allocated do not require load balancing, and the new types of these IP addresses are based on the reference server IP address, this means that two key measures must be taken when allocating IP addresses. First, the system must ensure that these IP addresses to be allocated are not incorrectly associated with the load balancer. Second, the allocation must also follow the region corresponding to the reference server IP address specified by the user to ensure reasonable resource distribution and meet the user's actual needs.

[0109] S303. Determine whether there are any unused IP addresses in the second area network segment; if yes, proceed to step S304; if no, proceed to step S305.

[0110] The purpose of determining whether there are no unused IP addresses in the second area network segment is to determine whether there are any IP addresses that can be assigned in the second area network segment.

[0111] Understandably, if all IP addresses in the second subnet have already been assigned, continuing to search for available IP addresses within that subnet will be futile, leading to allocation failures or IP conflicts. Therefore, determining in advance whether there are any unused IP addresses in the subnet can effectively avoid these problems and ensure a smooth allocation process.

[0112] S304. From the preset multiple network segments, except for the second area network segment, remove the network segments labeled as virtual server and real server to obtain at least one first candidate network segment.

[0113] If there are no unused IP addresses in the second area network segment, it means that there are no IP addresses that can be assigned in the second area network segment. Therefore, from the multiple preset network segments other than the second area network segment, network segments labeled as virtual server and real server can be removed to obtain at least one first candidate network segment.

[0114] Understandably, when all IP address resources in the second network segment are occupied, meaning there are no unused IP addresses, it means that IP addresses cannot be allocated for new services within that segment. Therefore, to solve this problem, it is necessary to exclude network segments already labeled as being used by virtual servers and real servers from a set of pre-defined network segments, thereby obtaining at least one unlabeled first candidate network segment that may contain available IP addresses.

[0115] S305. Determine the second regional network segment as the target network segment.

[0116] If there are unused IP addresses in the second area network segment, it indicates that there are IP addresses that can be assigned in the second area network segment. Therefore, the second area network segment can be identified as the target network segment.

[0117] Understandably, when it is determined that there are unused IP addresses in the second network segment, it means that there are still available IP resources within that segment that can be used to meet new configuration requirements. Therefore, in order to efficiently and accurately complete the IP address allocation task, the second network segment can be directly identified as the target network segment for subsequent IP address allocation work.

[0118] The IP address allocation method provided in this application first performs different processing based on the type of new IP address to be allocated. If the new type is a region, the first region network segment corresponding to the third region specified by the user is determined from a set of preset network segments, and network segments marked as virtual servers and real servers are removed, thus obtaining at least one first candidate network segment. If the new type is a reference server IP address, the second region to which the second reference server IP address entered by the user belongs is first determined, and then the second region network segment corresponding to the fourth region is found from the preset network segments. Next, it is checked whether there are any unused IP addresses in the second region network segment. If not, the marked network segments are removed from other preset network segments (excluding the second region network segment), again obtaining at least one first candidate network segment. If there are unused IP addresses in the second region network segment, the second region network segment is directly determined as the target network segment. This method, through an automated processing flow, not only significantly reduces labor costs and alleviates the workload of operation and maintenance personnel, but also avoids the problem of human error. Thus, it provides strong support for the stable operation of large-scale distributed systems.

[0119] Figure 4 Flowchart of the IP address allocation method provided in this application Figure 4 ,like Figure 4 As shown, in this embodiment... Figure 2Based on the embodiments, and in the case of load balancing on the addresses to be allocated, where the load balancing type is existing load balancing, the implementation process of determining at least one first candidate network segment from a preset number of network segments according to allocation requirement information is described in detail. The method includes:

[0120] S401. If the new type of the IP address to be assigned is a region, then determine whether the fifth region entered by the user matches the region to which the first virtual server address entered by the user belongs. If they match, then determine at least one first candidate network segment from the multiple preset network segments, which corresponds to the fifth region and is labeled as a real server.

[0121] Zone 5 includes multiple network segments labeled as "real server" segments, with each segment containing different real server IP addresses. For example, assuming Zone 5 is numbered 201, there might be two different network segments labeled as real servers within this zone: 192.168.8.0 / 24 and 192.168.9.0 / 24. These two segments represent two different IP address ranges used to assign to different real servers within this zone.

[0122] Existing load balancing refers to load balancing solutions that are already deployed and running in the current network architecture. They are responsible for allocating network traffic, optimizing resource utilization, and ensuring high service availability.

[0123] When the addresses to be allocated for load balancing are determined, the load balancing type is existing load balancing, and the new type of the IP addresses to be allocated is a region, it means that during this IP address allocation, it is necessary to ensure that these addresses are not only configured on the load balancer, but also connected to the specified existing load balancer. Furthermore, the IP address allocation must adhere to the region range specified by the user.

[0124] Understandably, when determining that the addresses to be allocated require a load balancing strategy, and the specific type of load balancing is existing load balancing, while the IP addresses to be allocated have a clear regional attribute, the system's IP address allocation work needs to follow the following principles: First, it must be ensured that these IP addresses to be allocated can be accurately configured on the load balancer; second, these addresses need to be connected to the designated, existing load balancing system to ensure effective distribution of network traffic; finally, the entire allocation process must strictly adhere to the regional scope specified by the user to meet the needs of network planning and resource management.

[0125] In this step, when determining whether the region entered by the user (the fifth region) matches the region of the first virtual server address entered by the user, the system needs to check the following: location, whether it is a traditional region, and whether it is a business region. For example, the content corresponding to the fifth region entered by the user is Beijing, a traditional region, and business region 1. The content corresponding to the region of the first virtual server address entered by the user is Beijing, a traditional region, and business region 3. Based on the above information, the system can determine that the fifth region entered by the user and the region of the first virtual server address entered by the user do not match.

[0126] Optionally, if the region entered by the user does not match the region of the first virtual server address entered by the user, this application needs to provide feedback to the user to indicate that the input is incorrect.

[0127] S402. If the new type of the IP address to be assigned is a reference server IP address, determine whether the user has not entered a virtual server address; if yes, proceed to step S403; if no, proceed to step S404.

[0128] Specifically, when it's determined that the addresses to be allocated for load balancing are existing load balancers, and the IP addresses to be allocated are reference server IP addresses, it means that during this IP address allocation process, it's necessary to ensure that not only are these addresses configured on the load balancer, but they are also connected to the specified existing load balancer. Furthermore, the allocation must adhere to the region corresponding to the reference server IP address specified by the user.

[0129] Understandably, when determining that the addresses to be allocated require a load balancing strategy, and the specific type of load balancing is existing load balancing, and the IP addresses to be allocated have a clearly defined regional attribute, the system's IP address allocation process must adhere to the following principles: First, ensure that these IP addresses to be allocated can be correctly configured on the load balancer, and that they need to be connected to the designated, existing load balancing system to achieve effective management and distribution of network traffic. Second, the allocation process must also follow the regional classification corresponding to the reference server IP address specified by the user to ensure reasonable resource allocation and efficient utilization, while meeting the needs of network architecture and operation and maintenance management.

[0130] The purpose of determining whether a user has not entered a virtual server IP address is to ascertain whether the user has specified a target virtual server.

[0131] As is understandable, a virtual server IP address is used to identify the network identity and location of a specific virtual server, and it is necessary to access that server. Therefore, by determining whether a user has provided a virtual server IP address, it is possible to determine whether the user has explicitly specified the target virtual server they wish to access or operate on.

[0132] S403. From a set of multiple network segments, determine at least one first candidate virtual server network segment whose region corresponds to the IP address of the fourth reference server and whose label is virtual server.

[0133] If the user does not enter a virtual server IP address, it means that the user has not specified a target virtual server. Therefore, it is necessary to determine at least one first candidate virtual server network segment from multiple preset network segments that corresponds to the network segment labeled as virtual server in this area.

[0134] Understandably, if the user does not provide a virtual server IP address, it means the user has not explicitly specified a target virtual server. In this case, the system needs to take further steps to determine a suitable virtual server IP address. Therefore, in this situation, the system will first identify the third-party reference server IP address entered by the user and determine the region to which that address belongs. Then, from a set of preset network segments, the system will filter out network segments located within that region and labeled as virtual servers. These network segments will be considered as at least one first-candidate virtual server network segment, so that the virtual server IP address can be subsequently determined from these first-candidate virtual server network segments.

[0135] S404. The network segment associated with the virtual server IP address allocated this time and labeled as a real server is identified as at least one first candidate real server network segment.

[0136] Specifically, after determining the most used first candidate virtual server network segment from at least one first candidate virtual server network segment, and taking the most used first candidate virtual server network segment as the target network segment, and determining the virtual server IP address to be allocated this time from the target network segment, it is necessary to find at least one first candidate real server network segment associated with the virtual server IP address to be allocated this time and labeled as a real server.

[0137] Understandably, firstly, virtual servers serve as access points for network services or applications, while real servers handle the actual processing of these requests. Secondly, by associating virtual server IP addresses with real server network segments, the system establishes a connection, allowing the virtual server to accurately forward requests to the corresponding real server for processing when it receives them.

[0138] Therefore, once the virtual server IP address is determined, it is necessary to find the associated real server network segment so that a connection can be established between the virtual server and the real server when needed.

[0139] S405. Determine whether the region to which the user-inputted third reference server IP address belongs matches the region to which the user-inputted second virtual server address belongs. If they match, determine at least one first candidate network segment from among multiple preset network segments whose network segment corresponds to the region to which the third reference server IP address belongs and is labeled as a real server.

[0140] If the user enters a virtual server IP address, it indicates that the user has specified a target virtual server. Therefore, it is necessary to determine whether the region of the third reference server IP address entered by the user matches the region of the second virtual server address entered by the user.

[0141] Understandably, when a user enters a virtual server IP address, it explicitly indicates that the user has specified a target virtual server. In this case, the system needs to determine whether the region of the user-entered third-party reference server IP address matches the region of the user-entered virtual server address. If they match, the system needs to find the network segments labeled as real servers within the region corresponding to the user-entered third-party reference server IP address and use these network segments as at least one first-choice real server network segment.

[0142] In this step, when determining whether the region of the user-input third reference server IP address matches the region of the user-input second virtual server address, the system needs to check the following: location, whether it is a traditional zone, and whether it is a service zone. For example, the region of the user-input third reference server IP address corresponds to Shanghai, a traditional zone, and service zone 1. The region of the user-input second virtual server address also corresponds to Shanghai, a traditional zone, and service zone 1. Based on this information, the system can determine that the regions of the user-input third reference server IP address and the user-input second virtual server address match.

[0143] The IP address allocation method provided in this application performs different processing based on the new type of the IP address to be allocated during the IP address allocation process. If the new type is a region, it first verifies whether the fifth region entered by the user matches the region to which the first virtual server address belongs. If the match is successful, it filters out the network segment corresponding to the fifth region and labeled as a real server from a preset set of network segments as at least one first candidate network segment. If the new type is a reference server IP address, it checks whether the user has not entered a virtual server address. If the user has not entered one, it determines the network segment corresponding to the region to which the third reference server IP address belongs and labeled as a virtual server from the preset network segments as at least one first candidate virtual server network segment. If the user has entered a virtual server address, it determines the network segment associated with the virtual server IP address allocated this time and labeled as a real server as at least one first candidate real server network segment. In addition, it also verifies whether the region to which the third reference server IP address belongs matches the region to which the second virtual server address belongs. If they match, it similarly determines the corresponding real server network segment from the preset network segments as a candidate. This method effectively solves the problems caused by the existing manual IP address allocation method with the development of large-scale distributed systems and the continuous expansion of network scale, thereby reducing the workload of operation and maintenance personnel and significantly reducing the risk of human error.

[0144] Figure 5 Flowchart of the IP address allocation method provided in this application Figure 5 ,like Figure 5 As shown, in this embodiment... Figure 2 Based on the embodiments, and in the case of load balancing of the IP addresses to be allocated, where the load balancing type is new load balancing and regional load balancing, the implementation process of determining at least one first candidate network segment from a preset number of network segments according to allocation requirement information is described in detail. The method includes:

[0145] S501. If the new type of the IP address to be assigned is a region, then determine at least one first candidate real server network segment from the multiple preset network segments corresponding to the sixth region entered by the user and labeled as a real server.

[0146] Among them, new load balancing refers to new load balancing systems planned for deployment to meet growing business demands or improve network performance.

[0147] The new load balancing features include regional load balancing and load balancing pools. Regional load balancing intelligently distributes user requests to servers in different geographical regions based on factors such as geographic location, network latency, and server load. Load balancing pools dynamically distribute user requests to virtual servers within the pool.

[0148] Zone 6 includes multiple network segments labeled as real server segments, and the real server IP addresses contained in different network segments are different. For example, if Zone 6 is numbered 101, then the network segments labeled as real servers include 192.168.4.0 / 24 and 192.168.5.0 / 24.

[0149] When it's determined that the IP addresses to be allocated for load balancing are of the new load balancing type and are designated as regional load balancing, and the new type of the IP addresses to be allocated is also designated as regional, it means that during this IP address allocation process, not only must these IP addresses be explicitly configured onto the new load balancing device, but it must also be ensured that they are connected to the regional load balancer. Furthermore, the IP address allocation must adhere to the regional range specified by the user.

[0150] Understandably, when allocating IP addresses, if a set of IP addresses to be allocated for new regional load balancing has been determined, and the new type of these IP addresses is explicitly specified as regional, then this means that during the allocation of these IP addresses, the system needs to ensure that they are not only correctly configured and connected to the new load balancing device to achieve effective distribution of network traffic and improved quality of service, but also strictly adhere to the regional scope specified by the user to ensure that resource allocation conforms to the expected geographical and logical boundaries.

[0151] S502. The network segment associated with the real server IP address allocated this time and labeled as virtual server is identified as at least one first candidate virtual server network segment.

[0152] Specifically, after determining the most used first candidate real server network segment from at least one first candidate real server network segment, and taking the most used candidate real server network segment as the target network segment, and determining the real server IP address to be allocated this time from the target network segment, it is necessary to find at least one first candidate virtual server network segment associated with the real server IP address to be allocated this time and labeled as virtual server.

[0153] Understandably, when the allocation requirement is clearly defined as load balancing using IP addresses to be allocated, the load balancing type is new load balancing and it's a regional load balancing, and the new type of the IP addresses to be allocated is also regional, the system will first determine suitable real server IP addresses because the user has specified the new load balancing requirement. After successfully determining these real server IP addresses, the system will then look for virtual server IP addresses associated with these real servers. This process not only provides real server IP addresses but also establishes the relationship between real server IP addresses and associated virtual servers, thereby meeting the regional load balancing requirements during operation.

[0154] S503. If the new type of the IP address to be assigned is a reference server IP address, then determine the seventh zone to which the fifth reference server IP address entered by the user belongs, and determine the network segment with the label of real server corresponding to the seventh zone from multiple preset network segments.

[0155] The different seventh zones correspond to different network segments labeled as real servers, and these network segments contain different real server IP addresses. For example, if the seventh zone is numbered 101, the network segment labeled as a real server is 192.168.1.0 / 24; if the seventh zone is numbered 102, the network segment labeled as a real server is 192.168.2.0 / 24.

[0156] When it's determined that the IP addresses to be allocated for load balancing are of the "new load balancing" type and are zone load balancing, and the "new" type of the IP addresses to be allocated is a reference server IP address, it means that during this IP address allocation process, these addresses must not only be configured on the load balancer but also connected to the new load balancer. Furthermore, the allocation must adhere to the zone corresponding to the reference server IP address specified by the user.

[0157] Understandably, when new regional load balancers are assigned IP addresses, and these IP addresses are added based on reference server IP addresses, the entire allocation process must not only ensure that these IP addresses are correctly configured on the new load balancer system, but also require corresponding connection settings on the newly created load balancer. Furthermore, the allocation process must strictly adhere to the user-specified regional division principles corresponding to the reference server IP addresses to ensure that IP addresses are allocated reasonably according to the expected regional distribution.

[0158] S504. Determine whether there are any unused IP addresses in the network segment corresponding to the seventh area and labeled as the real server; if yes, proceed to step S505; if no, proceed to step S507.

[0159] The purpose of determining whether there are no unused IP addresses in the network segment labeled as a real server corresponding to the seventh region is to determine whether there are any assignable IP addresses in the network segment labeled as a real server within the seventh region.

[0160] Understandably, IP address conflicts can disrupt network stability and reliability, preventing normal access to network resources, impacting business continuity, and affecting user experience. Therefore, before allocating IP addresses, it is essential to determine whether the IP addresses in the real server network segment of Zone 7 are already in use. This ensures that the allocated IP addresses are unique and unused, effectively preventing IP address conflicts and maintaining normal network operation and smooth service provision.

[0161] S505. From the multiple preset network segments, except for the network segment corresponding to the seventh area, determine the network segment labeled as the real server as at least one first candidate network segment.

[0162] If there are no unused IP addresses in the network segment labeled as a real server corresponding to the seventh region, it means that there are no assignable IP addresses in the network segment labeled as a real server within the seventh region. In this case, it is necessary to determine the network segment labeled as a real server from the network segments other than the network segment corresponding to the seventh region from the preset multiple network segments as at least one first candidate network segment.

[0163] Understandably, if there are no available free IP addresses to allocate within the network segment labeled "real server" corresponding to Zone 7, it means that the network segment labeled "real server" within that zone cannot meet the new IP address allocation requirements. In this case, the system needs to exclude the network segment corresponding to Zone 7 from a pre-defined pool of network segments and select the network segment labeled "real server" from the remaining network segments as at least one first-line candidate network segment for subsequent IP address allocation.

[0164] S506. The network segment labeled as virtual server associated with the real server IP address allocated this time shall be identified as at least one first candidate virtual server network segment.

[0165] Specifically, after determining the most used first candidate real server network segment from at least one first candidate real server network segment, and taking the most used first candidate real server network segment as the target network segment, and determining the real server IP address to be allocated this time from the target network segment, it is necessary to find at least one first candidate virtual server network segment associated with the real server IP address to be allocated this time and labeled as virtual server.

[0166] Understandably, in the process of allocating real server IP addresses, selecting the most frequently used first-choice real server network segment as the target network segment and determining the specific real server IP address from that target network segment is to optimize resource utilization and ensure efficient service operation. However, simply allocating real server IP addresses is insufficient to build a complete network service architecture. To achieve service virtualization, flexible scheduling, and ensure that requests can be correctly routed from the client to the real server, it is also necessary to find at least one first-choice virtual server network segment labeled as a virtual server associated with the real server IP address allocated this time. This establishes a mapping relationship between real servers and virtual servers, allowing client requests to be received through the virtual server's IP address and subsequently forwarded to the corresponding real server for processing.

[0167] S507. Determine the network segment corresponding to the seventh region and labeled as the real server as the target network segment of the real server.

[0168] If there are unused IP addresses in the network segment labeled as a real server corresponding to the seventh region, it indicates that there are assignable IP addresses in the network segment labeled as a real server within the seventh region. In this case, the network segment labeled as a real server corresponding to the seventh region needs to be identified as the target network segment for the real server.

[0169] Understandably, if there are unused IP addresses in the network segment labeled "real server" corresponding to Zone 7, then this means that the network segment labeled "real server" within Zone 7 still has the capability to allocate new IP addresses. In this case, the system needs to identify the network segment labeled "real server" corresponding to Zone 7 as the target network segment for real servers, for subsequent IP address allocation.

[0170] S508. The network segment associated with the real server IP address allocated this time and labeled as virtual server is determined as the target network segment of the virtual server.

[0171] Specifically, after determining the real server IP address assigned in this instance within the seventh region corresponding to the reference server IP address and from the network segments labeled as real servers within that region, it is necessary to continue to find at least one virtual server network segment labeled as virtual server that is associated with the real server IP address.

[0172] Understandably, in a real network environment, a real server typically hosts multiple virtual servers, which communicate with the real server through specific network configurations. Therefore, after finding the real server's IP address, it's also necessary to find the virtual server network segment associated with that IP address to ensure that the virtual servers can correctly access resources on the real server, thus enabling communication between the real server and the virtual servers.

[0173] The IP address allocation method provided in this application embodiment, if the new type of the IP address to be allocated is a region, then based on the sixth region input by the user, a network segment labeled "real server" is selected from a preset set of network segments as at least one first candidate real server network segment; simultaneously, a network segment labeled "virtual server" associated with the real server IP address allocated this time is determined as at least one first candidate virtual server network segment. If the new type of the IP address to be allocated is a reference server IP address, then firstly, the seventh region to which the fifth reference server IP address input by the user belongs is determined, and a network segment labeled "real server" corresponding to the seventh region is found from a preset set of network segments. Next, it is determined whether there is an unused IP address in this network segment. If not, a network segment labeled "real server" is determined from other network segments besides the network segment corresponding to the seventh region from the preset set of network segments as at least one first candidate network segment; if it exists, the network segment corresponding to the seventh region is directly determined as the real server target network segment. At the same time, a network segment labeled "virtual server" associated with the real server IP address allocated this time is determined as at least one first candidate virtual server network segment. This method replaces the traditional manual allocation of IP addresses with an automated process, effectively solving the problems brought about by the development of large-scale distributed systems and the continuous expansion of network scale, thereby reducing labor costs and the risks caused by human error.

[0174] Figure 6 Flowchart of the IP address allocation method provided in this application Figure 6 ,like Figure 6 As shown, in this embodiment... Figure 2 Based on the embodiments, and in the case where load balancing is performed on the IP addresses to be allocated, the load balancing type is new load balancing, and it is a load balancing pool, the implementation process of determining at least one first candidate network segment from multiple preset network segments according to allocation requirement information is described in detail. The method includes:

[0175] S601. Determine the application level to which the server belongs, and determine the first group and the target plane in the first group from multiple groups corresponding to the application level. From multiple preset network segments, determine at least one network segment with the label "virtual server" corresponding to the target plane, and determine the network segment with the highest usage rate among the at least one network segment with the label "virtual server" corresponding to the target plane as the virtual server target network segment.

[0176] The application level of a server refers to a classification based on the importance of the applications it hosts. For example, suppose there are three application levels for a server, represented by the numbers 1, 2, and 3, where a smaller number indicates a higher level and greater importance. Therefore, if the current server's application level is 1, it can be determined that the applications hosted on that server are of high importance.

[0177] Different levels contain different grouping information. For example, if the level is 1, the grouping information includes groups numbered 01, 02, and 03; if the level is 2, the grouping information includes groups numbered 04, 05, and 06.

[0178] At the same application level, each group corresponds to multiple planes, and each plane contains multiple different virtual server network segments. For example, at level 1, group 01 contains planes A and B, group 02 contains planes C and D, and group 03 contains planes E and F.

[0179] Understandably, once the IP addresses to be allocated for load balancing are determined, and the load balancing type is new load balancing and a load balancing pool, it means that when allocating IP addresses, not only must these IP addresses be reasonably allocated to new load balancing devices to ensure that the devices can efficiently handle the traffic of these IP addresses, but it is also necessary to ensure that these IP addresses can successfully access the load balancing pool so that they can participate in traffic distribution and scheduling as part of the load balancing process.

[0180] This step can be implemented as follows: The user first operates through the visual interface of a tool for dynamically allocating server IPs. On this interface, the user needs to enter the application to which the server belongs and select load balancing. Next, the user selects "Add Regional Load Balancer" from the load balancing options and clicks "Submit" if a load balancing pool is selected. The system then determines the application's level based on the server's application and displays multiple groups related to that level on the interface. The user needs to select the first group from these groups, and the interface further displays multiple planes corresponding to that group. After the user selects a target plane, the system determines the target network segment with the highest usage and labeled as a virtual server.

[0181] S602. The network segment with the highest usage rate among the network segments associated with the virtual server IP address allocated this time and labeled as real servers is determined as the target network segment for the real server.

[0182] After determining the virtual server IP address to be allocated from the network segment with the highest usage rate among at least one network segment labeled as virtual server, it is also necessary to find the network segment with the highest usage rate among the network segments labeled as real servers associated with the virtual server IP address to be allocated.

[0183] Understandably, usage rate is used to characterize the load and resource utilization of a network segment. Therefore, selecting the network segment with the highest usage rate for IP address allocation can, to a certain extent, ensure efficient resource utilization and load balancing.

[0184] Furthermore, since the physical server is the actual device that processes the data, while the virtual server primarily acts as an intermediary or proxy, identifying the physical server network segment associated with the virtual server's IP address ensures smooth data flow between the virtual and physical servers, thereby enabling the entire system to operate normally.

[0185] The IP address allocation method provided in this application first determines the application level to which the server belongs, and then selects a first group and its target plane from multiple corresponding groups. Subsequently, from multiple preset network segments, at least one network segment labeled as a virtual server corresponding to the target plane is identified, and the network segment with the highest usage rate is selected as the virtual server target network segment. Simultaneously, this scheme also considers the real server network segments associated with the virtual server IP addresses allocated this time, and determines the network segment with the highest usage rate as the real server target network segment. This method, through automated allocation, not only significantly reduces labor costs and alleviates operational pressure, but also effectively avoids the possibility of human error, achieving high efficiency, accuracy, and intelligence in IP address allocation.

[0186] Figure 7 A schematic diagram of the structure of the IP address allocation device provided in this application is shown below. Figure 7 As shown, the IP address allocation device 700 provided in this embodiment includes:

[0187] The acquisition module 701 is used to acquire the allocation requirement information of the server to be allocated IP address. The allocation requirement information includes one or more of the following: the application to which the server belongs, the number of IP addresses to be allocated, whether the IP addresses to be allocated are pre-production, whether the IP addresses to be allocated are load balanced and the type of load balancing, and whether the new type of the IP address to be allocated is a region or reference server IP address.

[0188] The determination module 702 is used to determine the target network segment from multiple preset network segments based on the allocation requirement information, and select an unused IP address from the target network segment as the IP address for this allocation.

[0189] The IP address allocation device provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and will not be described in detail here.

[0190] Figure 8 A schematic diagram of the IP address allocation device provided in this application. Figure 8 As shown, the electronic device 800 provided in this embodiment includes at least one processor 801 and a memory 802. Optionally, the device 800 further includes a communication component 803. The processor 801, memory 802, and communication component 803 are connected via a bus 804.

[0191] In a specific implementation, at least one processor 801 executes computer execution instructions stored in memory 802, causing at least one processor 801 to perform the above-described method.

[0192] The specific implementation process of processor 801 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0193] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0194] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.

[0195] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0196] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method.

[0197] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the above-described method.

[0198] The aforementioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0199] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in the device.

[0200] The division of units is merely a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.

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

[0202] In addition, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

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

[0204] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0205] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily essential to this application.

[0206] It should be further noted that although the steps in the flowchart are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowchart may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0207] It should be understood that the above-described device embodiments are merely illustrative, and the device of this application can also be implemented in other ways. For example, the division of units / modules in the above embodiments is only a logical functional division, and there may be other division methods in actual implementation. For example, multiple units, modules, or components may be combined, or integrated into another system, or some features may be ignored or not executed.

[0208] Furthermore, unless otherwise specified, the functional units / modules in the various embodiments of this application can be integrated into one unit / module, or each unit / module can exist physically separately, or two or more units / modules can be integrated together. The integrated units / modules described above can be implemented in hardware or as software program modules.

[0209] When integrated units / modules are implemented in hardware, the hardware can be digital circuits, analog circuits, etc. The physical implementation of the hardware structure includes, but is not limited to, transistors, memristors, etc. Unless otherwise specified, the processor can be any suitable hardware processor, such as a CPU, GPU, FPGA, DSP, and ASIC, etc. Unless otherwise specified, the storage unit can be any suitable magnetic or magneto-optical storage medium, such as Resistive Random Access Memory (RRAM), Dynamic Random Access Memory (DRAM), Static Random Access Memory (SRAM), Enhanced Dynamic Random Access Memory (EDRAM), High-Bandwidth Memory (HBM), Hybrid Memory Cube (HMC), etc.

[0210] If the integrated unit / module is implemented as a software program module and sold or used as an independent product, it can be stored in a computer-readable storage device (CMD). Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a memory and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned memory includes various media capable of storing program code, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk.

[0211] In the above embodiments, the descriptions of each embodiment have their own emphasis. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments. The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as the combination of these technical features does not contradict each other, it should be considered within the scope of this specification.

[0212] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0213] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A method for allocating IP addresses, characterized in that, include: Obtain the allocation requirement information of the server to be assigned an IP address. The allocation requirement information includes one or more of the following: the application to which the server belongs, the number of IP addresses to be assigned, whether the IP addresses to be assigned are pre-production, whether the IP addresses to be assigned are load-balanced and the type of load balancing, and whether the new type of the IP address to be assigned is a region or reference server IP address. Based on the allocation requirement information, a target network segment is determined from a set of preset network segments, and an unused IP address is selected from the target network segment as the IP address to be allocated this time.

2. The method according to claim 1, characterized in that, The step of determining the target network segment from a preset set of network segments based on the allocation requirement information includes: If the IP address to be allocated is in pre-production mode, and the new type of the IP address to be allocated is a region, then the first pre-production network segment corresponding to the first region input by the user is determined from the preset multiple network segments, and the first pre-production network segment is determined as the target network segment. If the new type of the IP address to be allocated is a reference server IP address, then the second region to which the first reference server IP address entered by the user belongs is determined, and the second pre-production network segment corresponding to the second region is determined from the preset multiple network segments, and the second pre-production network segment is determined as the target network segment.

3. The method according to claim 1, characterized in that, The step of determining the target network segment from a preset set of network segments based on the allocation requirement information includes: Based on the allocation requirement information, at least one first candidate network segment is determined from the preset multiple network segments; Based on the network segment identifier of the application to which the server belongs, determine at least one first deployment network segment that matches the network segment identifier from the at least one first candidate network segment; If at least one first network segment exists in the at least one first deployment network segment, and at least one IP address in the first network segment has been assigned to the application to which the server belongs, then the network segment with the highest usage rate among the at least one first network segment is determined as the target network segment; If the first network segment is not present in the at least one first deployment network segment, then the network segment with the highest utilization rate among the at least one first deployment network segments is determined as the target network segment.

4. The method according to claim 3, characterized in that, The step of determining at least one first candidate network segment from the preset plurality of network segments based on the allocation demand information includes: If the IP address to be allocated is not load balanced, and the new type of the IP address to be allocated is a region, then the first region network segment corresponding to the third region input by the user is determined from the preset multiple network segments, and the network segments labeled as virtual server and real server in the first region network segment are removed to obtain at least one first candidate network segment.

5. The method according to claim 3, characterized in that, The step of determining at least one first candidate network segment from the preset plurality of network segments based on the allocation demand information includes: If the IP address to be allocated is not load balanced, and the new type of the IP address to be allocated is a reference server IP address, then the fourth region to which the second reference server IP address entered by the user belongs is determined, and the second region network segment corresponding to the fourth region is determined from the preset multiple network segments. If there are no unused IP addresses in the second region network segment, then the network segments labeled as virtual server and real server are removed from the other network segments in the preset multiple network segments other than the second region network segment, to obtain the at least one first candidate network segment.

6. The method according to claim 5, characterized in that, Also includes: If there are unused IP addresses in the second regional network segment, then the second regional network segment is determined as the target network segment.

7. The method according to claim 3, characterized in that, The step of determining at least one first candidate network segment from the preset plurality of network segments based on the allocation demand information includes: When load balancing is performed on the IP address to be assigned, and the load balancing type is existing load balancing, if the new type of the IP address to be assigned is a region, it is determined whether the fifth region entered by the user and the region to which the first virtual server address entered by the user belong match. If they match, the network segment corresponding to the fifth region and labeled as a real server is determined from the preset multiple network segments as the at least one first candidate network segment.

8. The method according to claim 3, characterized in that, The step of determining at least one first candidate network segment from the preset plurality of network segments based on the allocation demand information includes: When load balancing is performed on the IP address to be assigned, and the load balancing type is existing load balancing, if the new type of the IP address to be assigned is a reference server IP address, then it is determined whether the region to which the third reference server IP address entered by the user belongs matches the region to which the second virtual server address entered by the user belongs. If they match, then from the preset multiple network segments, the network segment corresponding to the region to which the third reference server IP address belongs and labeled as a real server is determined as the at least one first candidate network segment.

9. The method according to any one of claims 2-8, characterized in that, The step of selecting an unused IP address from the target network segment as the IP address for this allocation includes: The target network segment is divided into multiple IP addresses. For each IP address, it is determined whether the IP address is in use. If the IP address is not in use, it is determined as the IP address to be allocated this time, until the number of IP addresses to be allocated and the number of IP addresses to be allocated this time are determined.

10. The method according to claim 3, characterized in that, The first candidate network segment includes a first candidate virtual server network segment and a first candidate real server network segment. Correspondingly, the target network segment includes a virtual server target network segment determined based on the first candidate virtual server network segment and a real server target network segment determined based on the first candidate real server network segment. Correspondingly, the IP address to be allocated this time includes a virtual server IP address determined based on the virtual server target network segment and a number of real server IP addresses to be allocated determined based on the real server target network segment.

11. The method according to claim 10, characterized in that, The step of determining at least one first candidate network segment from the preset plurality of network segments based on the allocation demand information includes: When load balancing is performed on the IP address to be assigned, the load balancing type is existing load balancing, the new type of the IP address to be assigned is reference server IP address, and the user has not entered a virtual server address, from the preset multiple network segments, determine at least one of the first candidate virtual server network segments whose region belongs to the fourth reference server IP address and whose label is virtual server. The step of determining at least one first candidate network segment from the preset plurality of network segments based on the allocation demand information further includes: The network segment associated with the virtual server IP address allocated this time and labeled as a real server is identified as at least one of the first candidate real server network segments.

12. The method according to claim 10, characterized in that, The step of determining at least one first candidate network segment from the preset plurality of network segments based on the allocation demand information includes: When load balancing is performed on the IP address to be allocated, the load balancing type is new load balancing and regional load balancing, and the new type of the IP address to be allocated is regional, the network segment corresponding to the sixth region input by the user and labeled as real server is determined from the preset multiple network segments as at least one of the first candidate real server network segments. The step of determining at least one first candidate network segment from the preset plurality of network segments based on the allocation demand information further includes: The network segment labeled "virtual server" associated with the real server IP address allocated in this transaction is identified as at least one of the first candidate virtual server network segments.

13. The method according to claim 10, characterized in that, The step of determining at least one first candidate network segment from the preset plurality of network segments based on the allocation demand information includes: When load balancing is performed on the IP address to be allocated, the load balancing type is new load balancing and regional load balancing, and the new type of the IP address to be allocated is a reference server IP address, the seventh region to which the fifth reference server IP address entered by the user belongs is determined, and the network segment corresponding to the seventh region and labeled as a real server is determined from the preset multiple network segments. If there is no unused IP address in the network segment corresponding to the seventh region and labeled as a real server, then the network segment labeled as a real server is determined from the other network segments in the preset multiple network segments other than the network segment corresponding to the seventh region as the at least one first candidate network segment. The step of determining at least one first candidate network segment from the preset plurality of network segments based on the allocation demand information further includes: The network segment labeled "virtual server" associated with the real server IP address allocated in this transaction is identified as at least one of the first candidate virtual server network segments.

14. The method according to claim 13, characterized in that, The method further includes: If there are unused IP addresses in the network segment labeled as a real server corresponding to the seventh region, then the network segment labeled as a real server corresponding to the seventh region is determined as the target network segment of the real server. The network segment labeled "virtual server" that is associated with the real server IP address allocated in this transaction is determined as the target network segment of the virtual server.

15. The method according to claim 1, characterized in that, The target network segment includes a virtual server target network segment and a real server target network segment. Correspondingly, the IP address allocated this time includes the virtual server IP address and the number of real server IP addresses to be allocated. The step of determining the target network segment from a preset set of network segments based on the allocation requirement information includes: When load balancing is performed on the IP address to be assigned, and the load balancing type is new load balancing and is a load balancing pool, the application level to which the server belongs is determined, and the first group and the target plane in the first group are determined from multiple groups corresponding to the application level. From multiple preset network segments, at least one network segment with the label of virtual server corresponding to the target plane is determined, and the network segment with the highest usage rate among the at least one network segment with the label of virtual server corresponding to the target plane is determined as the target network segment of the virtual server. The step of determining the target network segment from a preset set of network segments based on the allocation requirement information further includes: The network segment with the highest usage rate among those associated with the virtual server IP address allocated this time and labeled as a real server is determined as the target network segment for the real server.

16. An IP address allocation device, characterized in that, include: The acquisition module is used to acquire the allocation requirement information of the server to be allocated IP address. The allocation requirement information includes one or more of the following: the application to which the server belongs, the number of IP addresses to be allocated, whether the IP addresses to be allocated are pre-production, whether the IP addresses to be allocated are load balanced and the type of load balancing, and the type of new IP address to be allocated is a region or reference server IP address. The determination module is used to determine the target network segment from a set of preset network segments based on the allocation requirement information, and select an unused IP address from the target network segment as the IP address to be allocated this time.

17. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1 to 15.

18. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1 to 15.

19. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method of any one of claims 1 to 15.