CN112995349A - Address management method, server, and computer-readable storage medium - Google Patents
Address management method, server, and computer-readable storage medium Download PDFInfo
- Publication number
- CN112995349A CN112995349A CN201911271217.5A CN201911271217A CN112995349A CN 112995349 A CN112995349 A CN 112995349A CN 201911271217 A CN201911271217 A CN 201911271217A CN 112995349 A CN112995349 A CN 112995349A
- Authority
- CN
- China
- Prior art keywords
- address
- segment
- network segment
- group
- management method
- 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.)
- Granted
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/50—Address allocation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/12—Avoiding congestion; Recovering from congestion
- H04L47/122—Avoiding congestion; Recovering from congestion by diverting traffic away from congested entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/12—Avoiding congestion; Recovering from congestion
- H04L47/125—Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering
-
- 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
-
- 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/50—Address allocation
- H04L61/5061—Pools of addresses
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The present disclosure provides an address management method, including: receiving a user access protocol message; determining a first target address field group according to a pre-configured load balancing strategy; judging whether a first allocated exclusive address network segment corresponding to the access transponder identification exists in the first target address segment group; and when the first target address segment group is judged to have a first allocated exclusive address network segment corresponding to the access repeater identification, acquiring the first allocated exclusive address network segment. The present disclosure also provides a server and a computer readable medium.
Description
Technical Field
The present disclosure relates to the field of communications technologies, and in particular, to an address management method, a server, and a computer-readable storage medium.
Background
A conventional Broadband Access Server (BRAS) has been widely used for home Broadband Access service, and as global networking is continuously promoted, more and more users are added to the service. The existing broadband access server device cannot meet the trend of rapid development of the market due to the characteristics of the broadband access server device, such as limited hardware processing capacity, slow adaptive change capacity and the like. A Virtual Broadband Access Server (vbars) arises, which solves the above problems to some extent, reduces all service processing undertaken by a single device, separates upper layer service control from bottom layer forwarding, and reduces the degree of dependence on device hardware.
In the existing address management method, a centralized management mode is mostly adopted, for example, when a user accesses, an address pool module performs address allocation by unified centralized management, and the management mode has the advantages of serial execution of tasks, low operation efficiency, inflexible layout and easy address waste; or the address pool database is independent to the upper application module and applies for the idle address in real time, and the stored idle address is used for address allocation when the user accesses, thus improving the user access efficiency, but the load sharing can not be realized, the address allocation is easy to be uneven,
resulting in wasted addresses.
Disclosure of Invention
The present disclosure is directed to at least one of the technical problems of the prior art, and provides an address management method.
To achieve the above object, in a first aspect, an embodiment of the present disclosure provides an address management method, including:
receiving a user access protocol message, wherein the user access protocol message carries an access transponder identifier;
determining a first target address field group according to a pre-configured load balancing strategy;
judging whether a first allocated exclusive address network segment corresponding to the access repeater identification exists in the first target address segment group;
and when the first target address segment group is judged to have a first allocated exclusive address network segment corresponding to the access repeater identification, acquiring the first allocated exclusive address network segment.
In a second aspect, an embodiment of the present disclosure provides a server, including:
one or more processors;
storage means for storing one or more programs;
when executed by the one or more processors, cause the one or more processors to implement the address management method as in any one of the above embodiments.
In a third aspect, the disclosed embodiments provide a computer-readable storage medium, on which a computer program is stored, which when executed by a processor implements the steps in the address management method as described in any of the above embodiments.
The present disclosure has the following beneficial effects:
the embodiment of the disclosure provides an address management method, a server and a computer readable storage medium, which can realize address management in an address pool distributed management mode, determine a corresponding address segment group according to a corresponding load balancing strategy, execute a user address allocation task in real time and in parallel, improve the address management efficiency, avoid uneven address allocation and reduce the waste of address resources.
Drawings
FIG. 1 is a block diagram of a system architecture in which an address management method provided by an embodiment of the present disclosure may be deployed;
fig. 2 is a flowchart of an address management method according to an embodiment of the present disclosure;
FIG. 3 is a flow chart of another address management method provided by the embodiments of the present disclosure;
fig. 4 is a flowchart of another address management method provided in the embodiment of the present disclosure.
Detailed Description
In order to make those skilled in the art better understand the technical solution of the present disclosure, the address management method provided in the present disclosure is described in detail below with reference to the accompanying drawings.
Example embodiments will be described more fully hereinafter with reference to the accompanying drawings, but which may be embodied in different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It will be understood that, although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. Thus, a first element, component, or module discussed below could be termed a second element, component, or module without departing from the teachings of the present disclosure.
Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and the present disclosure, and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
The address management method provided by the disclosure can be used for a distributed deployment mode based on the address pool, a plurality of resource pool components receive the address application distributed by the load balancing component, and when multiple users access, the user address distribution task is executed in parallel.
Fig. 1 is a block diagram of a system architecture in which an address management method provided in an embodiment of the present disclosure may be deployed. As shown in fig. 1, the system architecture includes: a control plane and a forwarding plane.
The control plane includes upper layer applications and address management virtual machines (in particular, virtual broadband access servers); the address management virtual machine comprises an address pool data management component, a plurality of resource pool components and a load balancing component; the upper layer application and the address management virtual machine are connected through an address pool issuing configuration interface, address pool configuration is carried out through the upper layer application, and corresponding address pool information and configuration information, such as an address pool, address segments, network segment routing, address masks and the like, are issued to the address pool data management component, wherein a plurality of address segments are stored in the address pool in advance; the virtual network port of the load balancing component and the physical network port of the host machine can communicate through the creation of the network bridge.
The forwarding plane comprises a switch and a plurality of repeaters; the receiving port and the output port of the switch are isolated through a configured virtual local area network, data communication is established between the switch and a physical network port corresponding to the virtual machine, and data communication between the resource pool component and the load balancing component and the outside is realized; and the switch hangs a plurality of repeaters down, and establishes connection with the network side equipment and the user through the repeaters.
Fig. 2 is a flowchart of an address management method provided in an embodiment of the present disclosure, where as shown in fig. 2, the method is applied to an address management virtual machine side, and the method includes:
and step S1, receiving the user access protocol message.
Wherein, the user access protocol message carries the access transponder identification. Generally, the user access protocol packet also carries a user terminal identifier.
In some embodiments, in combination with the system architecture shown in fig. 1, the load balancing component obtains a user access protocol packet provided by a user terminal from an access repeater, where after receiving the user access protocol packet sent by a user side, the access repeater encapsulates the packet according to its own repeater identifier, so as to identify an access repeater corresponding to the user terminal.
It should be noted that, in the embodiment of the present disclosure, the expression "access repeater" only indicates that the repeater plays a corresponding role in the user access process, and does not indicate that the repeater only works in the user access process, or only has a function of forwarding a user access protocol message.
Step S2, determining a first target address field group according to a pre-configured load balancing strategy;
in some embodiments, in conjunction with the system architecture shown in fig. 1, the first target address segment group is determined according to a preconfigured load balancing policy, that is, the load balancing component specifies a corresponding resource pool component according to the preconfigured load balancing policy, and the resource pool component is substantially used for managing each address segment group. When a user accesses, the load balancing component receives a user access protocol message sent by the access repeater, and determines a corresponding resource pool component according to a pre-configured load balancing strategy so as to realize load sharing of address allocation. In some embodiments, the load balancing component may also perform resource pool component determination based on other resource pool component determination policies, depending on the particular scenario. Generally, the load balancing component should also verify the type of the received message, and perform the subsequent steps when the message is a user access protocol message.
In some embodiments, after step S2, and before step S3, further comprising:
and performing user authentication according to the user access protocol message.
Wherein, when the user authentication passes, step S3 is executed.
Step S3, determine whether there is a first allocated exclusive address network segment corresponding to the access forwarder identifier in the first target address segment group.
In some embodiments, in combination with the system architecture shown in fig. 1, the address pool data management component configures and issues address fields and corresponding address network segment masks to the resource pool component, and the resource pool component divides the address fields into address network segments with smaller granularity according to the corresponding address network segment masks. After that, at least one address network segment can be allocated to a corresponding transponder as a dedicated address network segment, specifically, a corresponding relationship between the at least one address network segment and the corresponding transponder is established according to a corresponding transponder identifier. A single repeater may correspond to multiple different proprietary address segments of multiple resource pool element configurations. Therefore, whether a first allocated exclusive address network segment corresponding to the access repeater identifier exists in the first target address segment group or not is judged, namely whether the resource pool component allocates the exclusive address network segment to the access repeater or not is judged and the exclusive address network segment is not recycled.
In step S3, when it is determined that the first target address segment group has the first allocated dedicated address segment corresponding to the access repeater identifier, then step S4 is executed; and when judging that the first target address segment group does not have the first allocated exclusive address network segment corresponding to the access transponder identification, allocating the corresponding address network segment according to a preset strategy.
Step S4, obtain a first allocated exclusive address network segment.
The disclosed embodiment provides an address management method, which can be used for determining a corresponding address segment group when a user accesses according to a corresponding load balancing strategy, determining a corresponding address network segment according to an access repeater identifier, and performing address management, so as to realize load sharing, avoid uneven address distribution and reduce address resource waste.
Fig. 3 is a flowchart of another address management method according to an embodiment of the disclosure. As shown in fig. 3, the method is an embodiment of the method shown in fig. 2, and specifically, after step S4, the method further includes:
step S5, determine whether there is an idle address in the first assigned dedicated address network segment.
In step S5, when it is determined that there is a free address in the first assigned dedicated address segment, step S6 is performed.
Step S6, allocating an idle address in the first allocated exclusive address network segment to a corresponding ue.
In some embodiments, in step S3, when it is determined that the first assigned dedicated address segment corresponding to the access repeater identifier does not exist in the first target address segment group, step S7 is performed.
Step S7, further determine whether there is an unallocated free address segment in the first destination address segment group.
In some embodiments, in step S5, when it is determined that there is no free address in the first assigned dedicated address segment, step S7 is performed.
In some embodiments, in conjunction with the system architecture shown in fig. 1, it is determined whether an unallocated free address segment exists in the first destination address segment group, that is, whether the resource pool component has an unallocated or incompletely allocated address segment.
In step S7, when it is determined that there is an unallocated free address segment in the first destination address segment group, step S8 is performed.
Step S8, using at least one idle address network segment as the first newly allocated exclusive address network segment, and establishing the corresponding relation between the access transponder identification and the first newly allocated exclusive address network segment.
In some embodiments, in conjunction with the system architecture shown in fig. 1, the resource pool component divides at least one address segment from the first set of destination address segments for allocation to the access forwarder as a first newly allocated dedicated address segment.
Step S9, allocating an idle address in the first newly allocated dedicated address network segment to the corresponding ue.
In some embodiments, in step S7, when it is determined that there is no unallocated free address segment in the first target address segment group, step S10 is performed.
Step S10, apply for a new address field for the first target address field group as the first address field.
In some embodiments, in conjunction with the system architecture shown in FIG. 1, the resource pool component applies for a new address segment as the first address segment from the address pool data management component. Generally speaking, the resource pool component can also be planned according to the requirement, detect the address utilization rate of the resource pool component, and send alarm information to the address pool data management component when the address utilization rate is higher than a preset threshold value, and the address pool data management component can issue a new address field according to the alarm information.
In addition, in some embodiments, in combination with the system architecture shown in fig. 1, when the resource pool component is instantiated, the method further includes: an address field is applied to an address pool data management component.
In some embodiments, the address pool data management component can also actively issue corresponding address pool configuration data, including address fields and address network segment masks.
In some embodiments, in combination with the system architecture shown in fig. 1, when applying for a new address segment, the resource pool component sends the identity of the resource pool component and the new address segment to the load balancing component, so that the load balancing component establishes a correspondence between each resource pool component and each address segment. The condition that the resource pool component applies for the new address segment comprises the condition that the address pool data management component actively issues the address segment and the condition that the resource pool component actively applies for the address segment successfully when the resource pool component is instantiated.
Step S11, at least one address network segment is divided from the first address segment to be used as a second newly allocated exclusive address network segment, and the corresponding relation between the access transponder identification and the second newly allocated exclusive address network segment is established.
In some embodiments, in conjunction with the system architecture shown in fig. 1, the resource pool component divides at least one address network segment from the first address segment for allocation to the access forwarder as a second newly allocated dedicated address network segment.
In some embodiments, after the step S8 and the step S11 are performed, the method further includes the following steps:
and issuing a network segment route corresponding to the network segment of the newly allocated exclusive address according to the access transponder identifier.
In some embodiments, in conjunction with the system architecture shown in fig. 1, the access repeater publishes the network segment route to the outside. Then, when the user terminal accesses the external network, the data message is sent from the network side to the user side, and after the network side equipment directly connected with the repeater finds the network segment route, the corresponding flow message is delivered to the repeater; the repeater receives the flow message and then delivers the flow message to the control plane continuously, and the control plane corresponding module counts the user flow and charges.
And step S12, allocating an idle address in the second newly allocated exclusive address network segment to the corresponding user terminal.
The embodiment of the disclosure provides an address management method, which can be used for allocating an address network segment to an access repeater according to the address use condition and allocating an address to a user terminal.
Fig. 4 is a flowchart of another address management method provided in the embodiment of the present disclosure. As shown in fig. 4, the method is an embodiment based on the method shown in fig. 2, and specifically, the method includes steps S13 to S19 in addition to steps S1 to S4. Only step S13 to step S19 will be described in detail below.
And step S13, receiving an address recovery request.
The address recovery request comprises an address to be recovered.
In some embodiments, with reference to the system architecture shown in fig. 1, when a user goes offline, a repeater receives an offline message sent by the user side, and sends the offline message to a load balancing component and an address recovery request, where the load balancing component obtains a current address of the offline user and uses the address as an address to be recovered. Generally, the load balancing component should also verify the type of the received message, and execute the subsequent steps when the message is a user offline message.
In the embodiment of the present disclosure, the expression "retrieve" indicates an action of actively canceling an address field, an address network segment, or an address configured for a lower layer object, for example, retrieving an address in an address field group, retrieving an address network segment in an address field, or the like. In conjunction with the system architecture shown in fig. 1, for example, the resource pool component reclaims the dedicated address network segment allocated to the repeater, the resource pool component reclaims the address allocated to the user, and so on.
And step S14, determining a second target address field group to which the address to be recovered belongs.
And step S15, recycling the address to be recycled in the second target address field group.
Specifically, the address to be recovered is recovered in the second target address field group, that is, the address to be recovered in the second target address field group is marked as a free address.
In some embodiments, after step S15, the method further includes:
step S16, determine whether all the second allocated exclusive address network segments where the addresses to be recovered are located are idle addresses.
In step S16, when all of the second assigned dedicated address segments are determined to be idle addresses, then step S17 is executed; and when judging that all the second allocated exclusive address network segments are not idle addresses, performing no other processing.
Step S17, recycling the second allocated exclusive address segment in the second target address segment group.
Specifically, the second allocated exclusive address segment is recovered in the second target address segment group, i.e. the corresponding relationship between the second exclusive address segment and the corresponding transponder identifier is cancelled.
In some embodiments, in combination with the system architecture shown in fig. 1, after recovering the dedicated address network segment, the forwarder corresponding to the dedicated address network segment should be notified to withdraw the network segment route corresponding to the recovered dedicated address network segment.
In some embodiments, after step S17, the method further includes:
step S18, judging whether all the second address segments where the recovered second allocated exclusive address network segment is located are idle addresses;
when all the second address fields are judged to be idle addresses, executing step S19; and when judging that all the second address fields are not idle addresses, not performing other processing.
Step S19, freeing the second address field in the second set of target address fields.
In particular, the second address field is released in the second set of target address fields, i.e., the second address field is deleted from the second set of target address fields.
In some embodiments, in conjunction with the system architecture shown in FIG. 1, the resource pool component releases the address segment, after which the persisted configuration information may be deleted by sending an address segment release message to the address pool data management component. In some embodiments, the resource pool component may also send an address segment reclamation message to the address pool data management component, with reclamation for the address segment being performed proactively by the address pool data management component.
It should be noted that, in the embodiment of the present disclosure, the expression "release" indicates an action of actively canceling an address segment, an address network segment, or an address configured by an upper layer object, for example, releasing an address segment, releasing an address network segment, and the like in an address segment group. In conjunction with the system architecture shown in FIG. 1, for example, the resource pool component releases the address fields configured by the address pool data management component, and so on.
It should be noted that, the present disclosure does not limit the execution sequence of steps S1 to S4 and S13 to S19, that is, steps S1 to S4 may be executed before steps S13 to S19, steps S1 to S4 may be executed after steps S13 to S19, or steps S1 to S4 may be executed in synchronization with steps S13 to S19, and all of them fall within the protection scope of the present disclosure.
The embodiment of the disclosure provides an address management method, which can be used for recovering a user address when a user is offline, recovering an address network segment when the user is idle, and releasing the address segment so as to reduce waste of address resources.
In the present disclosure, different steps in the above embodiments may be combined with each other to obtain a new technical solution, and the combined new technical solution also belongs to the protection scope of the present disclosure.
An embodiment of the present disclosure provides a server, including: one or more processors; storage means for storing one or more programs; when the one or more programs are executed by the one or more processors, the one or more processors are caused to implement any of the address management methods as in the above embodiments.
The disclosed embodiments provide a computer-readable storage medium, on which a computer program is stored, which when executed by a processor implements the steps in any of the address management methods in the embodiments described above.
It will be understood by those of ordinary skill in the art that all or some of the steps of the methods disclosed above, functional modules/units in the apparatus, may be implemented as software, firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed by several physical components in cooperation. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). The term computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, as is well known to those of ordinary skill in the art. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by a computer. In addition, communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media as known to those skilled in the art.
Example embodiments have been disclosed herein, and although specific terms are employed, they are used and should be interpreted in a generic and descriptive sense only and not for purposes of limitation. In some instances, features, characteristics and/or elements described in connection with a particular embodiment may be used alone or in combination with features, characteristics and/or elements described in connection with other embodiments, unless expressly stated otherwise, as would be apparent to one skilled in the art. Accordingly, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the scope of the disclosure as set forth in the appended claims.
Claims (12)
1. An address management method, comprising:
receiving a user access protocol message, wherein the user access protocol message carries an access transponder identifier;
determining a first target address field group according to a pre-configured load balancing strategy;
judging whether a first allocated exclusive address network segment corresponding to the access repeater identification exists in the first target address segment group;
and when the first target address segment group is judged to have a first allocated exclusive address network segment corresponding to the access repeater identification, acquiring the first allocated exclusive address network segment.
2. The address management method of claim 1, comprising: after the step of obtaining the first assigned private address network segment, the method further includes:
judging whether an idle address exists in the first allocated exclusive address network segment;
and when judging that the idle address exists in the first allocated exclusive address network segment, allocating one idle address in the first allocated exclusive address network segment to a corresponding user terminal.
3. The address management method according to claim 2,
when the first allocated exclusive address network segment corresponding to the access transponder identification does not exist in the first target address segment group, further judging whether an unallocated idle address network segment exists in the first target address segment group or not;
when judging that an unallocated idle address network segment exists in the first target address segment group, taking at least one idle address network segment as a first newly allocated exclusive address network segment, and establishing a corresponding relation between the access transponder identifier and the first newly allocated exclusive address network segment;
and allocating an idle address in the first newly allocated exclusive address network segment to a corresponding user terminal.
4. The address management method according to claim 3,
when judging that no unallocated idle address network segment exists in the first target address segment group, applying for a new address segment for the first target address segment group to serve as a first address segment;
dividing at least one address network segment from the first address segment to serve as a second newly allocated exclusive address network segment, and establishing a corresponding relation between the access transponder identifier and the second newly allocated exclusive address network segment;
and allocating an idle address in the second newly allocated exclusive address network segment to a corresponding user terminal.
5. The address management method according to claim 3 or 4,
and when judging that no idle address exists in the first allocated exclusive address segment group, executing the step of further judging whether an unallocated idle address segment group exists in the first target address segment group.
6. The address management method according to claim 3 or 4, wherein after establishing the correspondence between the access repeater identifier and the newly allocated dedicated address network segment, further comprising:
and issuing a network segment route corresponding to the newly allocated exclusive address network segment according to the access transponder identifier.
7. The address management method according to claim 1, wherein after the step of determining a first target address segment group according to a preconfigured load balancing policy and before the step of determining whether there is a first allocated dedicated address segment corresponding to the access forwarder identifier in the first target address segment group, further comprising:
performing user authentication according to the user access protocol message;
and when the user passes the authentication, executing the step of judging whether a first allocated exclusive address network segment corresponding to the access repeater identifier exists in the first target address segment group.
8. The address management method according to claim 1, further comprising:
receiving an address reclamation request, the address reclamation request comprising: the address to be recovered;
determining a second target address field group to which the address to be recovered belongs;
and recovering the address to be recovered in the second target address field group.
9. The address management method of claim 8, wherein, after the step of reclaiming the to-be-reclaimed address in the second target address field group, further comprising:
judging whether all the second allocated exclusive address network segments where the addresses to be recovered are idle addresses;
and when all the second allocated exclusive address network segments are judged to be idle addresses, recovering the second allocated exclusive address network segments in the second target address segment group.
10. The address management method of claim 9, wherein, after the step of reclaiming the second assigned private address segment in the second group of destination address segments, further comprising:
judging whether all the second address segments where the recovered second allocated exclusive address network segments are located are idle addresses;
and when all the second address fields are judged to be idle addresses, releasing the second address fields in the second target address field group.
11. A server, comprising:
one or more processors;
storage means for storing one or more programs;
when executed by the one or more processors, cause the one or more processors to implement the address management method of any one of claims 1-10.
12. A computer-readable storage medium, on which a computer program is stored, which program, when being executed by a processor, carries out the steps of the address management method according to any one of claims 1 to 10.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911271217.5A CN112995349B (en) | 2019-12-12 | 2019-12-12 | Address management method, server, and computer-readable storage medium |
| PCT/CN2020/133419 WO2021115183A1 (en) | 2019-12-12 | 2020-12-02 | Address management method, server and computer-readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911271217.5A CN112995349B (en) | 2019-12-12 | 2019-12-12 | Address management method, server, and computer-readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112995349A true CN112995349A (en) | 2021-06-18 |
| CN112995349B CN112995349B (en) | 2023-07-04 |
Family
ID=76329518
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911271217.5A Active CN112995349B (en) | 2019-12-12 | 2019-12-12 | Address management method, server, and computer-readable storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN112995349B (en) |
| WO (1) | WO2021115183A1 (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116896543A (en) * | 2023-09-11 | 2023-10-17 | 中移(苏州)软件技术有限公司 | IP address allocation method and device, electronic equipment and storage medium |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115150169B (en) * | 2022-06-30 | 2024-02-09 | 北京天融信网络安全技术有限公司 | Policy convergence method, device, system and medium |
Citations (21)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050025179A1 (en) * | 2003-07-31 | 2005-02-03 | Cisco Technology, Inc. | Distributing and balancing traffic flow in a virtual gateway |
| CN102265568A (en) * | 2011-06-13 | 2011-11-30 | 华为技术有限公司 | Communication method and load equalizer |
| US20120198096A1 (en) * | 2009-09-23 | 2012-08-02 | Zte Corporation | Method, Apparatus, System for Address Management |
| WO2013159641A1 (en) * | 2012-04-28 | 2013-10-31 | 华为技术有限公司 | Address allocation method, device, and system |
| US20140143428A1 (en) * | 2011-07-14 | 2014-05-22 | Huawei Technologies Co., Ltd. | Method, Apparatus, and Edge Node Controller for Allocating Edge Node |
| CN103873497A (en) * | 2012-12-11 | 2014-06-18 | 中国电信股份有限公司 | Method, device and system for scheduling information |
| CN104320353A (en) * | 2014-11-19 | 2015-01-28 | 中国联合网络通信集团有限公司 | User address managing method and device |
| US9043463B1 (en) * | 2009-03-30 | 2015-05-26 | Amazon Technologies, Inc. | Providing extendible network capabilities for managed computer networks |
| CN105991460A (en) * | 2015-03-02 | 2016-10-05 | 杭州迪普科技有限公司 | Traffic load forwarding method, main control board, service board and network equipment |
| JP2016178494A (en) * | 2015-03-20 | 2016-10-06 | 株式会社Ｎｔｔドコモ | Gateway device and communication method |
| CN106331192A (en) * | 2015-06-23 | 2017-01-11 | 中兴通讯股份有限公司 | Network protocol IP address allocation method and device |
| US20170171149A1 (en) * | 2014-07-15 | 2017-06-15 | ZET Corporation | Method for Acquiring Identifier of Terminal in Network, Management Network Element and Storage Medium |
| CN107070983A (en) * | 2017-01-23 | 2017-08-18 | 天地融科技股份有限公司 | A kind of load-balancing method, equipment and system forwarded based on address |
| CN107294845A (en) * | 2017-07-31 | 2017-10-24 | 杭州迪普科技股份有限公司 | VRRP load-balancing methods and device |
| CN108063837A (en) * | 2017-12-25 | 2018-05-22 | 锐捷网络股份有限公司 | Dynamic IP addressing distribution method and device |
| CN108449282A (en) * | 2018-05-29 | 2018-08-24 | 华为技术有限公司 | A kind of load-balancing method and its device |
| CN109413224A (en) * | 2018-11-12 | 2019-03-01 | 杭州数梦工场科技有限公司 | Message forwarding method and device |
| CN109495593A (en) * | 2017-09-11 | 2019-03-19 | 中兴通讯股份有限公司 | Address distribution method and system |
| CN109525684A (en) * | 2018-12-11 | 2019-03-26 | 杭州数梦工场科技有限公司 | Message forwarding method and device |
| CN109672758A (en) * | 2017-10-13 | 2019-04-23 | 中兴通讯股份有限公司 | Address distribution method, access server and computer storage medium |
| CN110445884A (en) * | 2018-05-04 | 2019-11-12 | 中国移动通信集团浙江有限公司 | A kind of container IP address management method and device |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102333027B (en) * | 2011-06-17 | 2014-05-07 | 杭州华三通信技术有限公司 | Traffic load sharing realization method based on virtual router redundancy protocol extend (VRRPE) backup group and realization apparatus thereof |
| CN102447638A (en) * | 2012-01-12 | 2012-05-09 | 中兴通讯股份有限公司 | Load balancing method and forwarding apparatus |
| CN102833161B (en) * | 2012-08-21 | 2018-01-30 | 中兴通讯股份有限公司 | Tunnel load share method and device |
| CN108959127B (en) * | 2018-05-31 | 2021-02-09 | 华为技术有限公司 | Address translation method, device and system |
-
2019
- 2019-12-12 CN CN201911271217.5A patent/CN112995349B/en active Active
-
2020
- 2020-12-02 WO PCT/CN2020/133419 patent/WO2021115183A1/en active Application Filing
Patent Citations (21)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050025179A1 (en) * | 2003-07-31 | 2005-02-03 | Cisco Technology, Inc. | Distributing and balancing traffic flow in a virtual gateway |
| US9043463B1 (en) * | 2009-03-30 | 2015-05-26 | Amazon Technologies, Inc. | Providing extendible network capabilities for managed computer networks |
| US20120198096A1 (en) * | 2009-09-23 | 2012-08-02 | Zte Corporation | Method, Apparatus, System for Address Management |
| CN102265568A (en) * | 2011-06-13 | 2011-11-30 | 华为技术有限公司 | Communication method and load equalizer |
| US20140143428A1 (en) * | 2011-07-14 | 2014-05-22 | Huawei Technologies Co., Ltd. | Method, Apparatus, and Edge Node Controller for Allocating Edge Node |
| WO2013159641A1 (en) * | 2012-04-28 | 2013-10-31 | 华为技术有限公司 | Address allocation method, device, and system |
| CN103873497A (en) * | 2012-12-11 | 2014-06-18 | 中国电信股份有限公司 | Method, device and system for scheduling information |
| US20170171149A1 (en) * | 2014-07-15 | 2017-06-15 | ZET Corporation | Method for Acquiring Identifier of Terminal in Network, Management Network Element and Storage Medium |
| CN104320353A (en) * | 2014-11-19 | 2015-01-28 | 中国联合网络通信集团有限公司 | User address managing method and device |
| CN105991460A (en) * | 2015-03-02 | 2016-10-05 | 杭州迪普科技有限公司 | Traffic load forwarding method, main control board, service board and network equipment |
| JP2016178494A (en) * | 2015-03-20 | 2016-10-06 | 株式会社Ｎｔｔドコモ | Gateway device and communication method |
| CN106331192A (en) * | 2015-06-23 | 2017-01-11 | 中兴通讯股份有限公司 | Network protocol IP address allocation method and device |
| CN107070983A (en) * | 2017-01-23 | 2017-08-18 | 天地融科技股份有限公司 | A kind of load-balancing method, equipment and system forwarded based on address |
| CN107294845A (en) * | 2017-07-31 | 2017-10-24 | 杭州迪普科技股份有限公司 | VRRP load-balancing methods and device |
| CN109495593A (en) * | 2017-09-11 | 2019-03-19 | 中兴通讯股份有限公司 | Address distribution method and system |
| CN109672758A (en) * | 2017-10-13 | 2019-04-23 | 中兴通讯股份有限公司 | Address distribution method, access server and computer storage medium |
| CN108063837A (en) * | 2017-12-25 | 2018-05-22 | 锐捷网络股份有限公司 | Dynamic IP addressing distribution method and device |
| CN110445884A (en) * | 2018-05-04 | 2019-11-12 | 中国移动通信集团浙江有限公司 | A kind of container IP address management method and device |
| CN108449282A (en) * | 2018-05-29 | 2018-08-24 | 华为技术有限公司 | A kind of load-balancing method and its device |
| CN109413224A (en) * | 2018-11-12 | 2019-03-01 | 杭州数梦工场科技有限公司 | Message forwarding method and device |
| CN109525684A (en) * | 2018-12-11 | 2019-03-26 | 杭州数梦工场科技有限公司 | Message forwarding method and device |
Non-Patent Citations (1)
| Title |
|---|
| 何朔;: "SDN在金融数据中心网络中的应用", 计算机应用与软件, no. 10, pages 198 - 204 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116896543A (en) * | 2023-09-11 | 2023-10-17 | 中移(苏州)软件技术有限公司 | IP address allocation method and device, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112995349B (en) | 2023-07-04 |
| WO2021115183A1 (en) | 2021-06-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11895154B2 (en) | Method and system for virtual machine aware policy management | |
| CN105323136B (en) | Information processing method and device | |
| EP3528466A1 (en) | Information sending method, unit and system | |
| EP3664372A1 (en) | Network management method and related device | |
| RU2683630C2 (en) | Method for update of nsd network service descriptor and device | |
| EP3664420B1 (en) | Managing address spaces across network elements | |
| CN104584484A (en) | System and method providing policy based data center network automation | |
| WO2020001045A1 (en) | Address management method and device | |
| CN110661894A (en) | User IP address allocation method, network device and storage medium | |
| CN112492063A (en) | IP address pool allocation and application method, device, equipment and medium | |
| CN108390956A (en) | A kind of method and system for virtual machine configuration internet protocol address | |
| CN112995349B (en) | Address management method, server, and computer-readable storage medium | |
| CN105704042A (en) | Message processing method, BNG and BNG cluster system | |
| CN107547675B (en) | User equipment migration method and device | |
| US11811879B2 (en) | Networking connection management based on container identification | |
| CN108933844B (en) | Method and equipment for providing DHCP service | |
| CN113452806A (en) | Container adaptation SDN network management method and system based on Kubernetes system | |
| CN110933192A (en) | Local area network IP address allocation method, device, system and computer equipment | |
| CN108540408B (en) | Openstack-based distributed virtual switch management method and system | |
| CN112804276B (en) | Virtual broadband remote access server, control method thereof and communication system | |
| CN109933959B (en) | License control method and related equipment | |
| CN113904871B (en) | Access method of network slice, PCF entity, terminal and communication system | |
| CN110545336A (en) | IP address replacing method, device, computer equipment and storage medium | |
| CN108259345B (en) | Port generation method and device | |
| CN112468458B (en) | Scheduling method based on neutron layering mechanism |
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 |