CN107786680B - Method and device for managing IP address resources - Google Patents
Method and device for managing IP address resources Download PDFInfo
- Publication number
- CN107786680B CN107786680B CN201610786697.9A CN201610786697A CN107786680B CN 107786680 B CN107786680 B CN 107786680B CN 201610786697 A CN201610786697 A CN 201610786697A CN 107786680 B CN107786680 B CN 107786680B
- Authority
- CN
- China
- Prior art keywords
- address
- edge device
- idle
- priority
- block
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/30—Managing network names, e.g. use of aliases or nicknames
Abstract
The invention discloses a method and a device for managing IP address resources, and relates to the field of network technical communication. The method comprises the following steps: determining the use state of the IP address resources of each edge device; judging whether new IP address resources need to be issued to the edge equipment or allocated IP address resources need to be recycled according to the use state of the IP address resources; and managing the IP address resources according to the judgment result. The resource manager can judge according to the use state of the address resources reported by the edge device at regular time, and automatically issue and recover the IP address resources according to the needs, so that the resource waste problems of excessive application of the address resources, untimely recovery and the like possibly caused by the active application mode of the edge device can be avoided.
Description
Technical Field
The present invention relates to the field of network technology communication, and in particular, to a method and an apparatus for managing IP address resources.
Background
With the continuous development of internet technology, the demand of internet users and terminal devices for IP address resources shows a significantly increasing trend, the existing IPv4 address resources are consumed up, and the shortage of address resources becomes a problem to be solved urgently in an operator network. In a conventional IP network, edge devices such as a BRAS (Broadband Remote Access Server) device are responsible for allocating service IP addresses to terminal users, and in the current network, each edge device needs to manually allocate fixed IP address blocks and address pool resources to meet internet Access requirements of a large number of internet users, which causes the problems of uneven IP address resource allocation and resource waste.
At present, IP address resources of IP network edge devices such as BRAS devices, firewalls, CGN (Carrier-grade NAT) devices and the like are implemented by adopting a manual configuration mode of an address block associated address pool and an address pool associated domain (domain), each device needs to monopolize fixed IP address resources, and a user accesses the internet to authenticate and acquire a service IP address by associating a designated domain. The intelligent mode is triggered by the equipment, the dynamic interaction is carried out with the IP address resource management system, the address resource is dynamically applied to issue and recover, and the resource management system is only responsible for responding to the equipment requirement and allocating the available address to the equipment for use.
Fig. 1 is a work flow diagram of an edge device trigger mode, where an IP network edge device (taking a vbrs as an example) is connected to an IP address resource manager, a fixed IP address resource configuration is provided on the vbrs, and a certain idle allocable IP address resource is reserved on the IP address resource manager. For the situations of insufficient address resources and idle address resources, the main workflow is described as follows:
when the vBRAS equipment detects that the local address resource reaches an alarm threshold value, triggering an address resource issuing request message and sending the address resource issuing request message to an address resource manager; the address resource manager checks whether idle IP address resources are available for allocation locally, and if the addresses are available, the address resource manager judges to issue and responds to an address request issuing message of the equipment side to issue new IP address resources. If no idle address is available locally, responding to the failure of equipment side allocation; when the vBRAS device detects that local address resources are free, the vBRAS device initiates an address resource recovery request message to a resource manager, the resource manager checks the address resources to be recovered after receiving the message, judges recovery after the check is passed, responds to the address recovery request of the device side, records the address into a local address resource library, and finishes the recovery operation.
The automatic IP address resource allocation system can not meet the requirement of global intelligent address resource management by adopting an equipment request mode, and the equipment is not treated in a differentiation manner in the automatic allocation process, so that the resource guarantee requirement of the existing network key equipment and edge equipment can not be met.
Disclosure of Invention
The invention aims to solve the technical problem of providing a scheme for managing IP address resources, which can meet the global intelligent management requirement of the address resources.
According to an aspect of the present invention, a method for managing IP address resources is provided, including: determining the use state of the IP address resources of each edge device; judging whether new IP address resources need to be issued to the edge equipment or allocated IP address resources need to be recycled according to the use state of the IP address resources; and managing the IP address resources according to the judgment result.
Further, the method further comprises: acquiring the priority of the edge device; and judging whether to issue new IP address resources to the edge equipment or recover the allocated IP address resources according to the priority of the edge equipment and the use state of the IP address resources.
Further, determining the IP address resource usage status of each edge device includes: receiving an address block usage parameter of an edge device; determining the address utilization rate of an address pool to which an address block belongs according to the address block utilization rate parameter of the edge device; and determining the address utilization rate of the domain to which the address pool belongs according to the address utilization rate of the address pool to which the address block belongs.
Further, judging whether a new IP address resource needs to be issued to the edge device according to the usage state of the IP address resource includes: and if the address utilization rate of the domain to which the address pool of the edge device belongs exceeds a threshold value, determining to issue idle address resources to the edge device.
Further, if the address utilization rate of the domain to which the address pool of the edge device belongs exceeds a threshold value, the method also comprises the steps of inquiring the priority of the edge device and judging whether to preferentially issue idle address resources to the edge device; if the idle address resource needs to be issued preferentially, the IP address resource type corresponding to the priority of the edge device is selected, and the idle address block in the IP address resource type is issued to the edge device.
Further, the method further comprises: and if no idle address resource exists in the IP address resource type corresponding to the priority of the edge device, selecting an idle address block from the IP address resource type corresponding to the priority lower than the priority of the edge device and sending the idle address block to the edge device.
Further, the determining whether the allocated IP address resources need to be recycled to the edge device according to the usage status of the IP address resources includes: and if the address block utilization rate parameter of the edge device is less than or equal to the address block idle threshold, determining to recycle the allocated address block to the edge device.
Further, if the address block usage parameter of the edge device is less than or equal to the address block idle threshold, determining to reclaim the allocated address block to the edge device includes: inquiring the priority of the edge device, and judging whether the address block utilization rate parameter of the edge device is less than or equal to the address block idle threshold corresponding to the priority of the edge device; and if the address block utilization rate parameter of the edge device is less than or equal to the address block idle threshold corresponding to the priority of the edge device, and the idle time length of the address block of the edge device exceeds the idle waiting time corresponding to the priority of the edge device, determining to recycle the allocated address block to the edge device.
Further, the method further comprises: if the address block utilization rate parameter of the edge device is less than or equal to the address block idle threshold corresponding to the priority of the edge device, and the address block idle duration of the edge device does not exceed the idle waiting time corresponding to the priority of the edge device, judging whether the allocated address block of the edge device needs to be recovered urgently; if the allocated address blocks of the edge device need to be recovered urgently, determining to recover the allocated address blocks to the edge device.
According to another aspect of the present invention, there is also provided an apparatus for managing IP address resources, including: the address block state data management unit is used for determining the IP address resource use state of each edge device; the address block scheduling policy decision unit is used for judging whether new IP address resources need to be issued to the edge device or allocated IP address resources need to be recycled according to the use state of the IP address resources; and the address block scheduling decision execution unit is used for managing the IP address resources according to the judgment result.
Further, a device priority management unit is included; the device priority management unit is used for acquiring the priority of the edge device; the address block scheduling policy decision unit is used for determining whether new IP address resources need to be issued to the edge device or allocated IP address resources need to be recycled according to the priority of the edge device and the use state of the IP address resources.
Further, the address block state data management unit is configured to receive an address block utilization rate parameter of the edge device, determine an address utilization rate of an address pool to which the address block belongs according to the address block utilization rate parameter of the edge device, and determine an address utilization rate of a domain to which the address pool belongs according to the address utilization rate of the address pool to which the address block belongs.
Further, the address block scheduling policy decision unit is configured to determine to issue the idle address resource to the edge device if the address utilization of the domain to which the address pool of the edge device belongs exceeds a threshold.
Further, the address block scheduling policy decision unit is further configured to query a priority of the edge device, determine whether to preferentially issue the idle address resource to the edge device, select an IP address resource type corresponding to the priority of the edge device if the idle address resource needs to be preferentially issued, and issue the idle address block in the IP address resource type to the edge device.
Further, the address block scheduling policy decision unit is further configured to select a free address block from the IP address resource types corresponding to the priority levels lower than the priority level of the edge device and send the free address block to the edge device if there is no free address resource in the IP address resource types corresponding to the priority levels of the edge device.
Further, the address block scheduling policy decision unit is configured to determine to recycle the allocated address block to the edge device if the address block usage parameter of the edge device is less than or equal to the address block idle threshold.
Further, the address block scheduling policy decision unit is further configured to query the priority of the edge device, determine whether the address block usage rate parameter of the edge device is less than or equal to an address block idle threshold corresponding to the priority of the edge device, and determine to recycle the allocated address block to the edge device if the address block usage rate parameter of the edge device is less than or equal to the address block idle threshold corresponding to the priority of the edge device and the address block idle duration of the edge device exceeds the idle waiting time corresponding to the priority of the edge device.
Further, the address block scheduling policy decision unit is further configured to determine whether to need to urgently recycle the allocated address block of the edge device if the address block usage parameter of the edge device is less than or equal to the address block idle threshold corresponding to the priority of the edge device and the address block idle duration of the edge device does not exceed the idle waiting time corresponding to the priority of the edge device, and determine to recycle the allocated address block to the edge device if the allocated address block of the edge device needs to urgently recycle.
Compared with the prior art, the method and the device for determining the IP address block use state judge whether to issue new IP address resources to the edge device or recover the allocated IP address resources according to the device address block use state information, and can avoid the problem of resource waste such as excessive application of the address resources and untimely recovery possibly caused by an active application mode of the edge device.
Other features of the present invention and advantages thereof will become apparent from the following detailed description of exemplary embodiments thereof, which proceeds with reference to the accompanying drawings.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description, serve to explain the principles of the invention.
The invention will be more clearly understood from the following detailed description, taken with reference to the accompanying drawings, in which:
fig. 1 is a flowchart illustrating a device-triggered address resource allocation in the prior art.
Fig. 2 is a flowchart illustrating an embodiment of a method for managing IP address resources according to the present invention.
Fig. 3 is a flowchart illustrating another embodiment of the method for managing IP address resources according to the present invention.
Fig. 4 is a flowchart illustrating an embodiment of a method for issuing IP address resources according to the present invention.
Fig. 5 is a flowchart illustrating an embodiment of a method for IP address resource recovery according to the present invention.
Fig. 6 is a schematic structural diagram of an embodiment of an apparatus for managing IP address resources according to the present invention.
Fig. 7 is a schematic structural diagram of another embodiment of the apparatus for managing IP address resources according to the present invention.
Fig. 8 is a schematic structural diagram of an embodiment of a device application for managing IP address resources according to the present invention.
Fig. 9 is a schematic diagram of an embodiment of a specific application of the present invention.
Detailed Description
Various exemplary embodiments of the present invention will now be described in detail with reference to the accompanying drawings. It should be noted that: the relative arrangement of the components and steps, the numerical expressions and numerical values set forth in these embodiments do not limit the scope of the present invention unless specifically stated otherwise.
Meanwhile, it should be understood that the sizes of the respective portions shown in the drawings are not drawn in an actual proportional relationship for the convenience of description.
The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the invention, its application, or uses.
Techniques, methods, and apparatus known to those of ordinary skill in the relevant art may not be discussed in detail but are intended to be part of the specification where appropriate.
In all examples shown and discussed herein, any particular value should be construed as merely illustrative, and not limiting. Thus, other examples of the exemplary embodiments may have different values.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, further discussion thereof is not required in subsequent figures.
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to specific embodiments and the accompanying drawings.
Fig. 2 is a flowchart illustrating an embodiment of a method for managing IP address resources according to the present invention. The method is executed by a resource manager and comprises the following steps:
at step 210, the IP address resource usage status of each edge device is determined. For example, the BRAS device reports the usage rate parameter of its own address block at regular time, and the resource manager calculates the address usage rate of its affiliated address pool, and determines the address usage rate of the domain (domain) to which the address pool belongs according to the address usage rate of the address pool. Wherein, the utilization rate of the address block is the ratio of the number of the addresses allocated to the terminal user to the number of all the addresses of the address block (except the available addresses of the host address, the broadcast address and the gateway address); the address utilization rate of the address pool is the ratio of the number of all the addresses which are allocated to the end user in the address pool to the total number of the addresses of all the address blocks contained in the address pool (each address block needs to remove the host address, the broadcast address and the gateway address); the address usage rate of a domain is the ratio of the number of addresses that have been assigned to end users under the domain to the total number of addresses of the block of addresses contained in the various address pools within the domain (each block of addresses needs to be freed up of host, broadcast and gateway addresses).
In step 220, it is determined whether it is necessary to issue a new IP address resource to the edge device or to recycle the allocated IP address resource according to the usage status of the IP address resource. When the resource manager calculates that the address utilization rate of a certain domain exceeds an alarm threshold, a free address block can be selected to be issued to a certain existing address pool, and the new address block can be matched with a gateway and a DNS (domain name system) of the address pool, so that the availability of the allocated address is ensured; an address pool can also be newly issued to the domain, wherein the address pool comprises a new address block and parameters such as a corresponding gateway and DNS, and the availability of the allocated address is guaranteed. In addition, if the address block usage parameter of the edge device is less than or equal to the address block idle threshold, then it is determined to reclaim the allocated address blocks to the edge device.
In step 230, the IP address resources are managed according to the judgment result, that is, the resource manager issues new IP address resources to the edge device or recovers the allocated IP address resources as required.
In the embodiment, the resource manager can make a decision according to the address resource use state reported by the edge device at regular time, and automatically issue and recover the IP address resource as required, so that the resource waste problems of excessive address resource application, untimely recovery and the like possibly caused by the active application mode of the edge device can be avoided.
Fig. 3 is a flowchart illustrating another embodiment of the method for managing IP address resources according to the present invention. The method comprises the following steps:
at step 310, the resource manager determines the IP address resource usage status of each edge device.
At step 320, the resource manager obtains the priority of the edge device. For example, different priority parameters are configured for different edge devices, and the edge devices with different priorities adopt different address allocation strategies, so that the address requirements of devices with high priorities are guaranteed preferentially, address resource differentiation services are provided, and the resource use priority of key devices is guaranteed.
In step 330, the resource manager determines whether it is necessary to issue a new IP address resource to the edge device or to recycle the allocated IP address resource according to the priority of the edge device and the usage status of the IP address resource. For example, edge devices with different priorities correspond to address block resources with different magnitudes, idle thresholds and waiting time, and when a plurality of edge devices simultaneously apply for limited address resources, address allocation of the devices with high priorities is preferentially guaranteed; when address resources are in short supply, the idle address blocks of the equipment with low priority are recovered firstly, and the resource allocation of important equipment is guaranteed.
In step 340, the resource manager issues a new IP address resource to the edge device or recycles the allocated IP address resource according to the determination result.
In this embodiment, the resource manager adopts different address allocation policies for devices of different priorities, and when resources of the resource manager are in short supply, the address resource allocation of important devices can be guaranteed first by the priorities of the devices, and an emergency recovery flow of an idle address of a low-priority device can be started to be used by a high-priority device, so as to provide differentiated services for devices of different levels.
Fig. 4 is a flowchart illustrating an embodiment of a method for issuing IP address resources according to the present invention. The method comprises the following steps:
in step 410, each edge device reports its address block usage parameter to the resource manager.
In step 420, the resource manager determines the address utilization rate of the address pool to which the address block belongs according to the address block utilization rate parameter of the edge device, and determines the address utilization rate of the domain to which the address pool belongs according to the address utilization rate of the address pool to which the address block belongs.
In step 430, it is determined whether the address utilization of the domain to which the address pool of the edge device belongs exceeds a threshold, if so, step 440 is executed, otherwise, step 410 is continuously executed.
At step 440, the priority of the edge device is queried.
In step 450, it is determined whether to preferentially issue idle address resources to the edge device, if so, step 460 is performed, otherwise, the queue is queued for issuance. When a plurality of edge devices simultaneously apply for the prior address resources, the address allocation of the devices with high priority is preferentially ensured.
In step 460, the IP address resource type corresponding to the edge device priority is selected, whether there is a corresponding idle address resource is determined, if there is an idle address resource, step 470 is executed, and if there is no idle address resource in the IP address resource type corresponding to the edge device priority, step 480 is executed.
In step 470, the idle address resource in the IP address resource type is sent to the edge device.
In step 480, a free address resource is selected from the lower level IP address resource types and sent to the edge device.
For example, the correspondence between the device priority and the address field from high to low is as follows:
0: the block of the a0 address is preferentially allocated (e.g. 500-1024 addresses), and if no address of this type can be divided, the allocation is selected downwards in a descending manner.
1: the A1 address block (e.g. 255-512 addresses) is preferentially allocated, and if no address of the type can be divided, the allocation is selected downwards in a descending manner.
2: the block of address a2 (e.g., 50-255 addresses) is preferentially allocated and the allocation is decremented downward if no address of that type is available.
3: preferentially allocate a3 address blocks (e.g., <50 addresses) if no addresses of this type are available, reply to a device allocation failure.
At step 490, the status of the address resource is updated and written to a DB (Database) storage log.
In this embodiment, the resource manager determines whether the current address usage exceeds a threshold according to the address usage status reported by the edge device, and if not, the normal response device continues to report the flow at regular time. If the priority is preferentially issued, the resource manager preferentially selects the address resource type corresponding to the priority of the equipment and preferentially selects a section of idle address from the address resource type to be issued to the equipment, and if the address resource corresponding to the priority is not idle and can be allocated, the idle address resource is preferentially selected from the resources of the lower level to be issued. And updating the state of the address resource after successful issuing and writing the state into a DB storage log. Therefore, the embodiment can perform calculation and decision globally by the resource manager, and when the resource of the resource manager is in short supply, the address resource allocation of important equipment can be firstly ensured, namely finer-grained allocation is realized, the requirement of the network on the differentiation of the equipment is met, and the use efficiency of the address resource is improved.
Fig. 5 is a flowchart illustrating an embodiment of a method for IP address resource recovery according to the present invention. The method comprises the following steps:
in step 510, each edge device reports its address block usage parameter to the resource manager.
At step 520, the priority of the edge device is queried and the corresponding idle threshold and idle latency are selected. For example, the correspondence between the device priority and the address block recycling policy is as follows:
0: the idle threshold is N0, and the idle waiting time is T0 (within T0, if the address block usage rates are all equal to N0, it can be determined to be recycled).
1: the idle threshold is N1, and the idle latency is T1(N1> -N0, T1< -T0).
2: the idle threshold is N2, and the idle latency is T2(N2> -N1, T2< -T1).
3: the idle threshold is N3, and the idle latency is T3(N3> -N2, T3< -T2).
In step 530, it is determined whether the address block utilization parameter of the edge device is less than or equal to the address block idle threshold corresponding to the priority of the edge device, if so, step 540 is executed, otherwise, step 510 is executed continuously.
In step 540, it is determined whether the address block idle duration of the edge device exceeds the idle waiting time corresponding to the priority of the edge device, if so, step 550 is executed, otherwise, step 560 is executed.
At step 550, the allocated address block is reclaimed to the edge device. And the equipment side deletes the corresponding service configuration and address resource configuration and then successfully replies the recovery instruction.
At step 551, the status of the address resource is updated and written to the DB store log.
In step 560, it is determined whether there is a need to reclaim the allocated address blocks of the edge devices urgently, if so, step 550 is performed, otherwise, step 561 is performed.
And if the current resources of the resource manager are in shortage and urgent recovery of the resources is needed to be carried out on the equipment with low priority, immediately starting a recovery flow.
In step 561, the idle duration is recorded, the allocated address block is not recycled for the time being, and the DB storage log is written.
In the embodiment, the resource manager queries the priority of the device according to the address use state reported by the edge device, selects a corresponding idle threshold and idle waiting time as judgment criteria, judges whether the address use of all address blocks of the device meets the idle recovery condition, starts a recovery flow when the address use of all address blocks of the device continuously meets the idle threshold condition in a set idle period, immediately recovers the address, sends a recovery instruction to the device, successfully replies the recovery instruction after the device side deletes corresponding service configuration and address resource configuration, updates the address resource state and writes a DB storage log. If the idle waiting time is not exceeded, the resource manager checks whether the current resource shortage period needs to carry out emergency recovery on the resources of the equipment with low priority, if the resource shortage period needs to be recovered, the resource manager carries out the recovery according to the flow of immediate recovery, and if the resource manager does not need to carry out emergency recovery, the resource manager records the idle time length and temporarily does not carry out the recovery. Therefore, the device priorities and the recovery strategies in this embodiment are different, the higher the priority is, the higher the recovery threshold of the device address resource is, the frequent recovery of the high-priority device address resource is avoided, and when the resource of the resource manager is in short supply, the emergency recovery process of the idle address of the low-priority device can be started, so that the high-priority device can use the idle address, and differentiated services are provided for different levels of devices.
Fig. 6 is a schematic structural diagram of an embodiment of an apparatus for managing IP address resources according to the present invention. The device is a resource manager, and comprises an address block state data management unit 610, an address block scheduling policy decision unit 620 and an address block scheduling decision execution unit 630, wherein:
the address block status data management unit 610 is configured to determine an IP address resource usage status of each edge device. For example, the BRAS device reports the usage rate parameter of its own address block at regular time, and the resource manager calculates the address usage rate of its address pool, and determines the address usage rate of the domain to which the address pool belongs according to the address usage rate of the address pool. Wherein, the utilization rate of the address block is the ratio of the number of the addresses allocated to the terminal user to the number of all the addresses of the address block (except the available addresses of the host address, the broadcast address and the gateway address); the address utilization rate of the address pool is the ratio of the number of all the addresses which are allocated to the end user in the address pool to the total number of the addresses of all the address blocks contained in the address pool (each address block needs to remove the host address, the broadcast address and the gateway address); the address usage rate of a domain is the ratio of the number of addresses that have been assigned to end users under the domain to the total number of addresses of the block of addresses contained in the various address pools within the domain (each block of addresses needs to be freed up of host, broadcast and gateway addresses).
The address block scheduling policy decision unit 620 is configured to determine whether to issue a new IP address resource to the edge device or to recycle an allocated IP address resource according to the usage status of the IP address resource. When the resource manager calculates that the address utilization rate of a certain domain exceeds an alarm threshold, a free address block can be selected to be issued to a certain existing address pool, and the new address block can be matched with a gateway and a DNS (domain name system) of the address pool, so that the availability of the allocated address is ensured; an address pool can also be newly issued to the domain, wherein the address pool comprises a new address block and parameters such as a corresponding gateway and DNS, and the availability of the allocated address is guaranteed. In addition, if the address block usage parameter of the edge device is less than or equal to the address block idle threshold, then it is determined to reclaim the allocated address blocks to the edge device.
The address block scheduling decision execution unit 630 is configured to manage IP address resources according to the determination result. I.e. issuing new IP address resources to the edge device or recycling the allocated IP address resources as required.
In the embodiment, the resource manager can make a decision according to the address resource use state reported by the edge device at regular time, and automatically issue and recover the IP address resource as required, so that the resource waste problems of excessive address resource application, untimely recovery and the like possibly caused by the active application mode of the edge device can be avoided.
Fig. 7 is a schematic structural diagram of another embodiment of the apparatus for managing IP address resources according to the present invention. The device comprises an address block state data management unit 710, a device priority management unit 720, an address block scheduling policy decision unit 730 and an address block scheduling decision execution unit 740, wherein:
the address block status data management unit 710 is configured to determine the IP address resource usage status of each edge device.
The device priority management unit 720 is configured to obtain the priority of the edge device. For example, different priority parameters are configured for different edge devices, and the edge devices with different priorities adopt different address allocation strategies, so that the address requirements of devices with high priorities are guaranteed preferentially, address resource differentiation services are provided, and the resource use priority of key devices is guaranteed.
The address block scheduling policy decision unit 730 is configured to determine whether to issue a new IP address resource to the edge device or to recycle an allocated IP address resource according to the priority of the edge device and the usage state of the IP address resource. For example, edge devices with different priorities correspond to address block resources with different magnitudes, idle thresholds and waiting time, and when a plurality of edge devices simultaneously apply for limited address resources, address allocation of the devices with high priorities is preferentially guaranteed; when address resources are in short supply, the idle address blocks of the equipment with low priority are recovered firstly, and the resource allocation of important equipment is guaranteed.
The address block scheduling decision execution unit 740 is configured to issue a new IP address resource to the edge device or recover an allocated IP address resource according to the determination result.
In the embodiment, the device priority corresponds to different IP address resource classifications, address resources are divided in a finer granularity, the design that different devices allocate different types of address resources is met, when resources of a resource manager are in short supply, the address resource allocation of important devices can be guaranteed firstly according to the priority of the devices, and an emergency recovery process of idle addresses of low-priority devices can be started for the high-priority devices to use, so that differentiated services are provided for the different-level devices.
In another embodiment of the present invention, the address block status data management unit 710 is configured to receive respective address block utilization rate parameters reported by each edge device, determine an address utilization rate of an address pool to which an address block belongs according to the address block utilization rate parameters, and determine an address utilization rate of a domain to which the address pool belongs according to the address utilization rate of the address pool to which the address block belongs. The device priority management unit 720 is configured to obtain the priority of the edge device. The address block scheduling policy decision unit 730 is configured to query the priority of the edge device, determine whether to preferentially issue idle address resources to the edge device, select an IP address resource type corresponding to the priority of the edge device if the idle address resources need to be preferentially issued, and issue an idle address block in the IP address resource type to the edge device; and if no idle address resource exists in the IP address resource types corresponding to the priority of the edge equipment, selecting an idle address block from the IP address resource types of the lower level and issuing the idle address block to the edge equipment. The address block scheduling decision execution unit 740 is configured to issue a new IP address resource to the edge device according to the determination result.
In this embodiment, the resource manager determines whether the current address usage exceeds a threshold according to the address usage status reported by the edge device, and if not, the normal response device continues to report the flow at regular time. If the priority is preferentially issued, the resource manager preferentially selects the address resource type corresponding to the priority of the equipment and preferentially selects a section of idle address from the address resource type to be issued to the equipment, and if the address resource corresponding to the priority is not idle and can be allocated, the idle address resource is preferentially selected from the resources of the lower level to be issued. Therefore, the embodiment can perform calculation and decision globally by the resource manager, and when the resource of the resource manager is in short supply, the address resource allocation of important equipment can be firstly ensured, namely finer-grained allocation is realized, the requirement of the network on the differentiation of the equipment is met, and the use efficiency of the address resource is improved.
In another embodiment of the present invention, the address block status data management unit 710 is configured to receive respective address block usage rate parameters reported by each edge device. The device priority management unit 720 acquires the priority of the edge device. The address block scheduling policy decision unit 730 is configured to query the priority of the edge device, select a corresponding idle threshold and idle waiting time, determine whether an address block usage rate parameter of the edge device is less than or equal to the address block idle threshold corresponding to the priority of the edge device, and determine to recycle an allocated address block to the edge device if the address block usage rate parameter of the edge device is less than or equal to the address block idle threshold corresponding to the priority of the edge device and the idle time of the address block of the edge device exceeds the idle waiting time corresponding to the priority of the edge device; if the address block utilization rate parameter of the edge device is less than or equal to the address block idle threshold corresponding to the edge device priority, but the address block idle duration of the edge device does not exceed the idle waiting time corresponding to the edge device priority, judging whether the allocated address block of the edge device needs to be recovered urgently, and if the allocated address block of the edge device needs to be recovered urgently, determining to recover the allocated address block to the edge device. The address block scheduling decision execution unit 740 is configured to issue a new IP address resource to the edge device according to the determination result.
In the embodiment, the resource manager queries the priority of the device according to the address use state reported by the edge device, selects a corresponding idle threshold and idle waiting time as judgment criteria, judges whether the address use of all address blocks of the device meets the idle recovery condition, starts a recovery process when the address use of all address blocks of the device continuously meets the idle threshold condition in a set idle period, and sends a recovery instruction to the device when the address use of all address blocks of the device is immediately recovered. If the idle waiting time is not exceeded, the resource manager checks whether the current resource shortage period needs to carry out urgent recovery on the equipment with low priority, and if the resource shortage period needs to be recovered, the resource manager carries out the recovery according to the flow of immediate recovery. Therefore, the device priorities and the recovery strategies in this embodiment are different, the higher the priority is, the higher the recovery threshold of the device address resource is, the frequent recovery of the high-priority device address resource is avoided, and when the resource of the resource manager is in short supply, the emergency recovery process of the idle address of the low-priority device can be started, so that the high-priority device can use the idle address, and differentiated services are provided for different levels of devices.
Fig. 8 is a schematic structural diagram of an embodiment of the device application for managing IP address resources according to the present invention, where the device for issuing and recovering IP address resources is a resource manager, where:
the resource manager UI 810 is responsible for opening up the administrator to perform the IP address resource import and device configuration. All configuration information and state reporting information are stored in the DB 820, and messages and parameters related to the unit call are read from the DB 820.
Each edge device 830 reports the respective Address block usage rate parameter to an Address block status data Management unit 860 of the resource manager through an AMA (Address Management Agent) node 840 through a message reporting interface 850, and the Address block status data Management unit 860 reports the received message to the DB 820. The AMA node 840 mainly completes the docking of the device and the address resource manager, and completes the functions of issuing and recovering the IP address related configuration, reporting the address use state at regular time, reporting the heartbeat message of the device, and the like. In particular, the communication protocol between the AMA node 840 and the resource manager may select the netconf or radius protocol for different device types.
The device priority management unit 861 may store priority information of devices in the DB 820. The address block scheduling policy decision unit 862 acquires the device address block usage status information and the priority information from the DB 820, and determines whether to issue a new IP address resource to the edge device or to recover an allocated IP address resource according to the device address block usage status information and the priority information, and sends the determination result to the address block scheduling decision execution unit 863, and the address block scheduling decision execution unit 863 sends a corresponding command to the AMA node 840 of each edge device 830 through the message issue interface 851 according to the determination result. In addition, the AMA node 840 of each edge device 830 may further send device heartbeat information to the heartbeat and configuration management unit 864 through the heartbeat interface 852, and the heartbeat and configuration management unit 864 may further perform corresponding configuration on each edge device 830, for example, configure device priority, a usage alarm threshold, an idle threshold, a waiting time, and the like.
In the embodiment, the resource manager can perform global calculation and decision, and automatically issue and recover the IP address resources as required based on the address use state and the equipment priority, so that the problem of resource waste such as excessive application of the address resources and untimely recovery possibly caused by an edge equipment active application mode can be solved. In addition, the embodiment has small change to the current network architecture, and only needs the address management agent node of the equipment to interact with the address resource manager, thereby reducing the workload of manual configuration and reducing the maintenance cost.
Fig. 9 is a schematic diagram of an embodiment of a specific application of the present invention. Taking a vbrs device and an entity BRAS device as an example, the vbrs device and the entity BRAS device are respectively connected with a resource manager through a Netconf interface and a Radius interface.
Firstly, information related to address resources to be managed needs to be imported or configured in a resource manager, and the information includes: the name, id, prefix and prefix length of the IPv4 and IPv6 address block (IPv4 refers to network address and mask, IPv6 refers to network prefix and prefix length), and corresponding gateway, DNS and other parameters. Then, global policy parameters need to be configured, including: the device timing reporting period, the alarm threshold, the device heartbeat time, the device sampling period, etc. The administrative IP address and port of the connected device, the type of device (vbras, bras, cgn, etc.), and some basic information description of the device are then added on the resource manager.
And then, configuring priorities for the equipment, defaulting that the priorities of all the equipment are the same, and allocating different priorities to the equipment by an administrator according to the user quantity and the importance of the equipment. After the equipment is added, domains are configured for the equipment according to the service plan, each domain can be configured with the address block type which is preferentially allocated, and if not, the system randomly issues the address blocks according to the equipment priority. According to different priorities of the devices, an administrator can configure an address block idle threshold and an idle waiting time parameter, and the difference of idle recovery of the devices with different priorities is ensured. If not, the address block recycling judgment is carried out on the devices with different priorities according to default parameters of the system.
When the device is on-line for the first time, the resource manager connects the device according to the configuration, and the resource manager issues the global parameter and the device id and domain configuration to the device, for example:
the vbras device is configured as follows:
(1) priority 0 (high priority)
(2) Domain with pppoe configuration
(3) The domain address allocation corresponds to the A0 type address block (the domain A0 type address block is preferentially allocated, the A0 address block has 500-1024 address numbers)
(4) Configuring an idle threshold value to be 0, namely the address block utilization rate is 0, and judging that the address block is idle for one time; the idle waiting time is 5 reporting periods T, namely when the utilization rate of the address block is 0 in 5 continuous reporting periods, the idle waiting time is judged to be an idle starting recovery flow
The bras device is configured as follows:
(1) priority 2 (lower priority than vbras)
(2) Ipoe-configured domain
(3) domain address assignment corresponds to a class A2 address block (domain A2 address block is assigned first, A2 address block is 50-255 address numbers)
(4) Configuring an idle threshold value to be 0, namely the address block utilization rate is 0, and judging that the address block is idle for one time; the idle waiting time is 3 reporting periods T, that is, when the usage rates of the address blocks in 3 consecutive reporting periods are all 0, it is determined that the address blocks are idle to start the recovery process.
When the resource manager is successfully connected with the equipment and issues the configuration parameters, default address resources are allocated to different domains of the equipment. In this example, the resource manager may send an address pool ippool1 for pppoe domain of the vbras device and associate the address pool ippool1 with a segment of address block ipblock1 (the number of addresses of the address block ipblock1 is 1024, which meets the address number requirement of the address block of a0 class configured for the device); and an address pool ippool2 of the ipoe domain sent to the online bras device is associated with another segment of address block ipblock2 (the number of the address blocks of the ipblock2 is 255, which meets the requirement of the address number of the A2 type address block configured by the device). And the issued address blocks are matched with the corresponding gateways and DNS. After the initial distribution, the two devices can distribute service IP address parameters for the users.
The two devices report the utilization rates of ipblock1 and ipblock2 to the resource manager at regular time according to the issued regular reporting cycle time, the resource manager calculates the average utilization rates of the addresses of ippool1 and ippool2 and the average utilization rates of the addresses of a pppoe domain and an ipoe domain according to the utilization rates of the ipblock1 and the ipblock2 address blocks, compares the average utilization rate of the addresses of the domains with an address shortage alarm threshold value, normally, the average utilization rate of the address resources of a certain domain is lower than the threshold value, and the resource manager records the utilization rate information of the devices and replies a response message.
Assuming that the set alarm threshold is 80%, when a large number of users suddenly come on line to apply for service addresses, the resource manager calculates the average address utilization rate of the pppoe domain of the vbras device to be 81% at a certain time, and the resource manager compares the average address utilization rate with the alarm threshold to find that the average address utilization rate exceeds the alarm threshold and triggers a new address block allocation process. The resource manager correspondingly manages the address blocks according to the priority of the device configuration, firstly, whether allocable A0-class idle address blocks (the number of the addresses is 500-1024) exist is searched, if yes, an ipblock3 address block in the A0-class address is selected, the address block can be associated and matched with existing gateway and dns of ippool1, namely, the ipblock1 and the ipblock3 can use a set of gateway and dns, and therefore the user can be guaranteed to normally access after being allocated with the IP address. If the resource manager can not find the address block which is matched with gateway and dns which are already provided by ippool1, the selected ipblock3 is newly associated with one ippool3 and is issued to the pppoe domain of the vbras device, and the availability of the ipblock3 is realized by newly establishing one ippool. When the address resources on the resource manager are in short supply and no free address blocks of A0 types are available for allocation after local query, the resource manager selects from the free address blocks of A1 types (the number of the addresses is 255-512), the selection principle is consistent, if the free address blocks are still unavailable, the resource manager selects from the address blocks of a lower type, and in an extreme case, no free address blocks are available for all types of addresses, the feedback equipment fails to allocate and sends an address resource total shortage alarm to the manager. The resource manager can mark the state of the allocated address block, and avoid repeated issuing of the address block.
When the bras equipment reports the utilization rate of the address block regularly, a tide effect applied by a user service address occurs in a certain time period, the address block applied on the bras equipment is ipblock2 and ipblock4, the resource manager monitors the address block in 3 reporting periods, finds that the utilization rate of the ipblock4 address block on the bras equipment is not higher than an idle threshold value, starts an idle address block recovery flow at the moment, when the resource manager judges that the idle address is recovered immediately, sends an address block recovery instruction of the ipblock4 to the bras equipment according to the recovery judgment flow, the bras equipment deletes service configuration such as routing issue and the like related to the address block after receiving the instruction, deletes configuration of the ipblock4, feeds back a recovery success message to the resource manager after the recovery succeeds, and the resource manager sets the state of the address block to be idle after receiving the message, and can continue to distribute other equipment. When the extreme condition of insufficient resources occurs, the device with high priority may have insufficient address application, but when the available idle address is insufficient, the resource manager will start an emergency resource recovery process for the device with lower priority, for example, when the bras device has an address idle report and just reaches 2 reporting cycles, the resource manager will not start the address recovery process but continue to wait for one reporting cycle to judge whether to recover according to the normal process. But if the resource manager ensures the address of the higher priority device to be used, the resource manager starts the idle address urgent recovery of ipblock4 of the bras device at this time, recovers and sets the address block as 'idle' to be allocated to the higher priority device.
When the free address resource on the resource manager is extremely insufficient, the address allocation of the device with high priority is preferentially ensured, for example, when only 1 free address block is available, the vbras device and the bras device simultaneously have an excessive alarm threshold of the address resource, and under normal conditions, the address resource manager needs to allocate the free address block to the two devices simultaneously so as to ensure that the address manager allocates the service address to the user. But when only 1 free address block exists, the resource manager can judge the priority of 2 devices, when the higher priority of the vbras is found, the automatic allocation process of the address block with insufficient address is started for the vbras device, the bsa device is added into the free address allocation queue, and the release of the free address block of other devices is waited or the resource manager has new address resources to be introduced, and then the bras device is issued according to the priority of the device to be allocated in the queue. The Bras equipment can only continue to use the locally allocated address resources to allocate service addresses to the users at the moment, and reports the use states of the address blocks at regular time.
In the embodiment, the allocated device reports the use state information of each address block to the resource manager at regular time, the resource manager dynamically calculates and judges whether a domain needs to issue a new address block or a new address pool according to the use state of each device address block, and selects the optimal IP address resource to issue according to the requirement by combining the priority of the device; when judging that a certain address block is idle, starting an address recovery process, finishing the state updating of the IP address block, and selecting the required address block to be preferentially issued according to the priority of the equipment. The embodiment can provide differentiated services for different levels of equipment, and can avoid the problem of resource waste such as excessive application of address resources and untimely recovery possibly caused by an active application mode of the edge equipment.
Thus far, the present invention has been described in detail. Some details well known in the art have not been described in order to avoid obscuring the concepts of the present invention. It will be fully apparent to those skilled in the art from the foregoing description how to practice the presently disclosed embodiments.
The method and apparatus of the present invention may be implemented in a number of ways. For example, the methods and apparatus of the present invention may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above-described order for the steps of the method is for illustrative purposes only, and the steps of the method of the present invention are not limited to the order specifically described above unless specifically indicated otherwise. Furthermore, in some embodiments, the present invention may also be embodied as a program recorded in a recording medium, the program including machine-readable instructions for implementing a method according to the present invention. Thus, the present invention also covers a recording medium storing a program for executing the method according to the present invention.
Although some specific embodiments of the present invention have been described in detail by way of illustration, it should be understood by those skilled in the art that the above illustration is only for the purpose of illustration and is not intended to limit the scope of the invention. It will be appreciated by those skilled in the art that modifications may be made to the above embodiments without departing from the scope and spirit of the invention. The scope of the invention is defined by the appended claims.
Claims (8)
1. A method for managing IP address resources, comprising:
determining the use state of IP address resources of each edge device, wherein address block use rate parameters of the edge devices are received, the address use rate of an address pool to which the address blocks belong is determined according to the address block use rate parameters of the edge devices, and the address use rate of a domain to which the address pool belongs is determined according to the address use rate of the address pool to which the address blocks belong;
judging whether to issue new IP address resources to the edge device or to recycle the allocated IP address resources according to the use state of the IP address resources, wherein the judging whether to issue the new IP address resources comprises the following steps: if the address utilization rate of the domain to which the address pool of the edge device belongs exceeds a threshold value, determining to issue idle address resources to the edge device; judging whether to recycle the allocated IP address resources comprises: inquiring the priority of the edge device, selecting a corresponding address block idle threshold and idle waiting time, and judging whether the address block utilization rate parameter of the edge device is less than or equal to the address block idle threshold corresponding to the priority of the edge device; if the address block utilization rate parameter of the edge device is less than or equal to the address block idle threshold corresponding to the priority of the edge device, and the address block idle duration of the edge device exceeds the idle waiting time corresponding to the priority of the edge device, determining to recycle the allocated address block to the edge device; if the address block utilization rate parameter of the edge device is less than or equal to the address block idle threshold corresponding to the priority of the edge device and the address block idle duration of the edge device does not exceed the idle waiting time corresponding to the priority of the edge device, judging whether the allocated address block of the edge device needs to be recovered urgently; if the allocated address blocks of the edge equipment need to be recovered urgently, determining to recover the allocated address blocks to the edge equipment, otherwise, recording idle time and writing a storage log;
and managing the IP address resources according to the judgment result.
2. The method of claim 1, further comprising:
acquiring the priority of the edge device;
and judging whether to issue new IP address resources to the edge equipment or recover the allocated IP address resources according to the priority of the edge equipment and the use state of the IP address resources.
3. The method of claim 1, wherein if the address usage of the domain to which the address pool of the edge device belongs exceeds a threshold, further comprising:
inquiring the priority of the edge device, and judging whether to preferentially issue the idle address resource to the edge device;
if the idle address resource needs to be issued preferentially, selecting the IP address resource type corresponding to the priority of the edge device, and issuing the idle address block in the IP address resource type to the edge device.
4. The method of claim 3, further comprising:
and if no idle address resource exists in the IP address resource type corresponding to the priority of the edge device, selecting an idle address block from the IP address resource type corresponding to the priority lower than the priority of the edge device and sending the idle address block to the edge device.
5. An apparatus for managing IP address resources, comprising:
the system comprises an address block state data management unit, a domain management unit and a domain management unit, wherein the address block state data management unit is used for determining the use state of IP address resources of each edge device, receiving address block use rate parameters of the edge devices, determining the address use rate of an address pool to which an address block belongs according to the address block use rate parameters of the edge devices, and determining the address use rate of a domain to which the address pool belongs according to the address use rate of the address pool to which the address block belongs;
an address block scheduling policy decision unit, configured to determine whether to issue a new IP address resource to the edge device or to recover an allocated IP address resource according to the usage state of the IP address resource, where determining whether to issue the new IP address resource includes: if the address utilization rate of the domain to which the address pool of the edge device belongs exceeds a threshold value, determining to issue idle address resources to the edge device; judging whether to recycle the allocated IP address resources comprises: inquiring the priority of the edge device, selecting a corresponding address block idle threshold and idle waiting time, and judging whether the address block utilization rate parameter of the edge device is less than or equal to the address block idle threshold corresponding to the priority of the edge device; if the address block utilization rate parameter of the edge device is less than or equal to the address block idle threshold corresponding to the priority of the edge device, and the address block idle duration of the edge device exceeds the idle waiting time corresponding to the priority of the edge device, determining to recycle the allocated address block to the edge device; if the address block utilization rate parameter of the edge device is less than or equal to the address block idle threshold corresponding to the priority of the edge device and the address block idle duration of the edge device does not exceed the idle waiting time corresponding to the priority of the edge device, judging whether the allocated address block of the edge device needs to be recovered urgently; if the allocated address blocks of the edge equipment need to be recovered urgently, determining to recover the allocated address blocks to the edge equipment, otherwise, recording idle time and writing a storage log;
and the address block scheduling decision execution unit is used for managing the IP address resources according to the judgment result.
6. The apparatus of claim 5, comprising a device priority management unit;
the device priority management unit is used for acquiring the priority of the edge device;
the address block scheduling policy decision unit is used for determining whether to issue new IP address resources to the edge device or to recycle allocated IP address resources according to the priority of the edge device and the use state of the IP address resources.
7. The apparatus of claim 5, wherein the address block scheduling policy determining unit is further configured to query a priority of the edge device, determine whether to preferentially issue the idle address resource to the edge device, select an IP address resource type corresponding to the priority of the edge device if the idle address resource needs to be preferentially issued, and issue an idle address block in the IP address resource type to the edge device.
8. The apparatus of claim 7, wherein the address block scheduling policy determining unit is further configured to select a free address block from the IP address resource types corresponding to the priority of the edge device and send the free address block to the edge device if there is no free address resource in the IP address resource types corresponding to the priority of the edge device.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610786697.9A CN107786680B (en) | 2016-08-31 | 2016-08-31 | Method and device for managing IP address resources |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610786697.9A CN107786680B (en) | 2016-08-31 | 2016-08-31 | Method and device for managing IP address resources |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107786680A CN107786680A (en) | 2018-03-09 |
| CN107786680B true CN107786680B (en) | 2020-11-13 |
Family
ID=61451480
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610786697.9A Active CN107786680B (en) | 2016-08-31 | 2016-08-31 | Method and device for managing IP address resources |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107786680B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110113445B (en) * | 2019-05-10 | 2022-02-15 | 广东电网有限责任公司 | IP resource on-line management method, device and equipment for enterprise network |
| CN111193944B (en) * | 2019-12-17 | 2023-06-06 | 视联动力信息技术股份有限公司 | Sub-equipment number configuration method, device and storage medium |
| CN111371921B (en) * | 2020-03-24 | 2022-07-29 | 河南信大网御科技有限公司 | IP address recovery method, address pool management method and address pool management server |
| US11757833B2 (en) * | 2021-09-29 | 2023-09-12 | Juniper Networks, Inc. | Network device interface for supporting centralized address pool management |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102231764A (en) * | 2011-06-22 | 2011-11-02 | 华为技术有限公司 | Method and device for distributing network addresses |
| CN103685586A (en) * | 2012-09-07 | 2014-03-26 | 中兴通讯股份有限公司 | Method, device and system for realizing address sharing |
| CN104348927A (en) * | 2013-07-31 | 2015-02-11 | 北京华为数字技术有限公司 | Address field assignment method and apparatus |
| CN104754072A (en) * | 2015-03-04 | 2015-07-01 | 杭州华三通信技术有限公司 | Address allocation method and equipment |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103685008B (en) * | 2012-08-31 | 2017-02-15 | 中国电信股份有限公司 | Bidirectional message priority marking method and system |
| CN102932501B (en) * | 2012-11-08 | 2015-06-10 | 杭州迪普科技有限公司 | Address pool resource protecting method and device thereof |
-
2016
- 2016-08-31 CN CN201610786697.9A patent/CN107786680B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102231764A (en) * | 2011-06-22 | 2011-11-02 | 华为技术有限公司 | Method and device for distributing network addresses |
| CN103685586A (en) * | 2012-09-07 | 2014-03-26 | 中兴通讯股份有限公司 | Method, device and system for realizing address sharing |
| CN104348927A (en) * | 2013-07-31 | 2015-02-11 | 北京华为数字技术有限公司 | Address field assignment method and apparatus |
| CN104754072A (en) * | 2015-03-04 | 2015-07-01 | 杭州华三通信技术有限公司 | Address allocation method and equipment |
Non-Patent Citations (3)
| Title |
|---|
| NFV对于运营级IP网络的影响及挑战;解冲锋，胡晓娟，李晨，谷欣;《电信技术》;20150725;全文 * |
| 新IP网络的地址资源池化及智能调度技术;解冲锋 李晨 谷欣 孙琼;《电信技术》;20160725;第18-21页 * |
| 解冲锋 李晨 谷欣 孙琼.新IP网络的地址资源池化及智能调度技术.《电信技术》.2016, * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107786680A (en) | 2018-03-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107786680B (en) | Method and device for managing IP address resources | |
| CN107786681B (en) | Method, device and system for scheduling IP address resources | |
| US11265258B2 (en) | Network device, controller, queue management method, and traffic management chip | |
| US20170195282A1 (en) | Address Processing Method, Related Device, and System | |
| JP2005309644A (en) | Resource control method and its system | |
| RU2518948C1 (en) | Method, apparatus and system for quality of service control based on charging system | |
| CN109766174B (en) | Resource scheduling method, resource scheduling apparatus, and computer-readable storage medium | |
| WO2007041899A1 (en) | A system and method of managing the dynamic adaptive distributed resource | |
| CN110661894A (en) | User IP address allocation method, network device and storage medium | |
| CN108429824B (en) | Address allocation method and device | |
| CN107665143B (en) | Resource management method, device and system | |
| CN113452806B (en) | Container adaptation SDN network management method and system based on Kubernets system | |
| WO2019170011A1 (en) | Task allocation method and device, and distributed storage system | |
| CN110647392A (en) | Intelligent elastic expansion method based on container cluster | |
| US7961620B2 (en) | Network scheduler for selectively supporting work conserving mode and network scheduling method thereof | |
| CN109428950B (en) | Automatic scheduling method and system for IP address pool | |
| WO2015014195A1 (en) | Address resource allocation method, management device, request device, and system | |
| WO2008074236A1 (en) | A method, device and system for allocating a media resource | |
| KR20050076522A (en) | Method for label management of distributed muti protocol label switching router and the router thereof | |
| CN113420029A (en) | Global ID generation method, device, equipment and medium for distributed system | |
| CN112995349B (en) | Address management method, server, and computer-readable storage medium | |
| CN108234681B (en) | Address resource automatic recovery method, address resource management device and network system | |
| CN110399216B (en) | Method, system and device for distributing power consumption of whole machine box and readable storage medium | |
| CN106161068B (en) | Recovery prompting and distributing method for network resources and controller | |
| Cisco | Automating IP Address Management |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |