CN112995349B - Address management method, server, and computer-readable storage medium - Google Patents
Address management method, server, and computer-readable storage medium Download PDFInfo
- Publication number
- CN112995349B CN112995349B CN201911271217.5A CN201911271217A CN112995349B CN 112995349 B CN112995349 B CN 112995349B CN 201911271217 A CN201911271217 A CN 201911271217A CN 112995349 B CN112995349 B CN 112995349B
- Authority
- CN
- China
- Prior art keywords
- address
- segment
- network segment
- allocated
- 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.)
- 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/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
Abstract
The present disclosure provides an address management method, including: receiving a user access protocol message; determining a first target address segment group according to a pre-configured load balancing strategy; judging whether a first allocated exclusive address network segment corresponding to the access transponder identifier exists in the first target address segment group; and when judging that the first allocated exclusive address network segment corresponding to the access transponder identifier exists in the first target address segment group, 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
The broadband access server (Broadband Remote Access Server, BRAS for short) of the conventional device has been widely used for home broadband access service, and with the continuous advancement of global networking, more and more users are added to the service. The current 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 capability, slow capability of adapting to changes and the like. The appearance of a virtual broadband access server (Virtual Broadband Remote Access Server, vbas for short) has resulted in a solution to the above-mentioned problems to a certain extent, reducing all service processing undertaken by a single device, separating upper layer service control from lower layer forwarding, and enabling the system to reduce the degree of dependence on device hardware.
The current address management method mostly adopts a centralized management mode, for example, when a user accesses, the address pool module performs unified centralized management to perform address allocation, the task of the management mode is executed in series, the operation efficiency is low, the layout is not flexible enough, and the situation of address waste is easy to occur; or the address pool database is independently connected to the upper layer application module and carries out idle address application in real time, and when a user accesses, the stored idle address is used for carrying out address allocation, so that although the user access efficiency is improved, the load sharing can not be realized, the uneven address allocation is easy to be caused,
resulting in address wastage.
Disclosure of Invention
The present disclosure aims to solve at least one of the technical problems existing in the prior art, and proposes 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 segment group according to a pre-configured load balancing strategy;
judging whether a first allocated exclusive address network segment corresponding to the access transponder identifier exists in the first target address segment group;
and when judging that the first allocated exclusive address network segment corresponding to the access transponder identifier exists in the first target address segment group, acquiring the first allocated exclusive address network segment.
In a second aspect, embodiments of the present disclosure provide a server, including:
one or more processors;
a storage means for storing one or more programs;
the 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 described in any of the embodiments above.
In a third aspect, the disclosed embodiments provide a computer readable storage medium having stored thereon a computer program which when executed by a processor implements the steps of 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, wherein the method can realize address management in an address pool distributed management mode, determine corresponding address segment groups according to corresponding load balancing strategies, execute user address allocation tasks in real time and in parallel, improve address management efficiency, avoid uneven address allocation and reduce address resource waste.
Drawings
FIG. 1 is a block diagram of a system architecture in which an address management method provided by embodiments 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 flowchart of another address management method according to an embodiment of the present disclosure;
fig. 4 is a flowchart of yet another address management method according to an embodiment of the present disclosure.
Detailed Description
In order to better understand the technical solutions 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 may be embodied in various 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 element. Accordingly, 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 an address pool, a plurality of resource pool components receive address applications distributed by a load balancing component, and user address distribution tasks are executed in parallel when multiple users access.
Fig. 1 is a block diagram of a system architecture in which an address management method according to an embodiment of the present disclosure may be deployed. As shown in fig. 1, the system architecture includes: control plane and 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 address pools, address segments, network segment routes, address masks and the like, are issued to an address pool data management component, wherein a plurality of address segments are prestored in the address pools; the virtual network port of the load balancing component and the physical network port of the host can communicate through the creation of a 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, and data communication is established between the switch and a physical network port corresponding to the virtual machine, so that the data communication between the resource pool component and the load balancing component and the outside is realized; the switch hangs down a plurality of forwarders, establishes the connection with network side equipment and user through the forwarder.
Fig. 2 is a flowchart of an address management method according to 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:
step S1, receiving a user access protocol message.
The user access protocol message carries an access transponder identifier. In general, 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 the access repeater receives the user access protocol packet sent by the user side, the access repeater encapsulates the packet according to its own repeater identifier, so as to identify the 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 procedure, and does not represent that the repeater only works in the user access procedure, or only has a function of forwarding the user access protocol message.
S2, determining a first target address segment group according to a pre-configured load balancing strategy;
in some embodiments, in connection with the system architecture shown in fig. 1, the first set of target address segments is determined according to a pre-configured load balancing policy, i.e. the load balancing component specifies a corresponding resource pool component according to the pre-configured load balancing policy, the resource pool component being substantially used for managing the respective set of address segments. And when the 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, depending on the particular scenario, the load balancing component may also make the determination of the resource pool component based on other resource pool component determination policies. In general, the load balancing component should also verify the type of the received message, and execute 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 carrying out user authentication according to the user access protocol message.
Wherein, when the user authentication is passed, step S3 is performed.
And S3, judging whether a first allocated exclusive address network segment corresponding to the access transponder identifier exists in the first target address segment group.
In some embodiments, in conjunction with the system architecture shown in FIG. 1, address segments and corresponding address segment masks are configured by an address pool data management component and issued to a resource pool component, which divides the address segments into smaller-granularity address segments according to the corresponding address segment masks. Thereafter, at least one address network segment may be assigned as a dedicated address network segment to the respective transponder, in particular, a correspondence between the at least one address network segment and the respective transponder is established in accordance with the respective transponder identification. A single forwarder may correspond to a plurality of different proprietary address segments of a plurality of resource pool component configurations. Therefore, whether a first allocated dedicated address network segment corresponding to the access transponder identifier exists in the first target address segment group is judged, namely whether the resource pool component allocates the dedicated address network segment to the access transponder and is not recovered is judged.
In step S3, when it is determined that the first allocated dedicated address segment corresponding to the access transponder identifier exists in the first target address segment group, step S4 is executed; and when judging that the first allocated exclusive address network segment corresponding to the access transponder identifier does not exist in the first target address segment group, allocating the corresponding address network segment according to a preset strategy.
And S4, acquiring a first allocated exclusive address network segment.
The embodiment of the disclosure provides an address management method, which can be used for determining a corresponding address segment group according to a corresponding load balancing strategy when a user accesses, determining a corresponding address network segment according to an access transponder identifier, and performing address management so as to realize load sharing, avoid uneven address allocation and reduce address resource waste.
Fig. 3 is a flowchart of another address management method according to an embodiment of the present disclosure. As shown in fig. 3, the method is an alternative embodiment of the method shown in fig. 2, specifically, after step S4, further including:
and S5, judging whether a free address exists in the first allocated exclusive address network segment.
In step S5, when it is determined that there is a free address in the first allocated private address network segment, step S6 is performed.
And S6, allocating a free address in the first allocated exclusive address network segment to the corresponding user terminal.
In some embodiments, in step S3, when it is determined that the first allocated dedicated address segment corresponding to the access transponder identifier does not exist in the first target address segment group, step S7 is performed.
And S7, further judging whether an unallocated free address network segment exists in the first target address segment group.
In some embodiments, in step S5, when it is determined that there is no free address in the first allocated dedicated address segment, step S7 is performed.
In some embodiments, in conjunction with the system architecture shown in fig. 1, it is determined whether there is an unallocated free address field in the first set of target address fields, i.e., whether the resource pool component has an unallocated or unallocated address field.
In step S7, when it is determined that there is an unassigned free address segment in the first target address segment group, step S8 is performed.
And S8, taking at least one idle address network segment as a first new allocation exclusive address network segment, and establishing a corresponding relation between the access transponder identifier and the first new allocation exclusive address network segment.
In some embodiments, in connection with the system architecture shown in fig. 1, the resource pool component divides at least one address segment from the first set of target address segments for allocation to the access repeater as a first newly allocated dedicated address segment.
Step S9, a free address in the first newly allocated dedicated address network segment is allocated to the corresponding user terminal.
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, applying a new address segment for the first target address segment group to serve as a first address segment.
In some embodiments, in connection with the system architecture shown in FIG. 1, the resource pool component applies for a new address segment as the first address segment to the address pool data management component. In general, the resource pool component can also plan 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 segment according to the alarm information.
In addition, in some embodiments, in conjunction with the system architecture shown in fig. 1, when the resource pool component is instantiated, the method further includes: address segments are applied to the address pool data management component.
When the address pool is configured, the instance numbers of the corresponding resource pool components are bound under the address pool, and in some embodiments, the address pool data management component can also actively issue corresponding address pool configuration data, including address segments, address network segment masks and the like.
In some embodiments, in conjunction with the system architecture shown in fig. 1, when applying for a new address field, the resource pool component sends its own identity and the new address field to the load balancing component, so that the load balancing component establishes a correspondence between each resource pool component and each address field. The resource pool component applies for the new address field, which comprises the situation that the address field is actively issued by the address pool data management component and the situation that the address field is successfully applied by the resource pool component 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 a corresponding relation between the access transponder identification and the second newly allocated exclusive address network segment is established.
In some embodiments, in connection with the system architecture shown in fig. 1, the resource pool component divides at least one address segment from the first address segment for allocation to the access repeater as a second newly allocated dedicated address segment.
In some embodiments, after establishing the correspondence between the access repeater identifier and the newly allocated dedicated address network segment in step S8 and step S11, the method further includes:
and issuing a network segment route corresponding to the newly allocated dedicated address network segment according to the access transponder identifier.
In some embodiments, the access forwarder issues the segment route externally in connection with the system architecture shown in fig. 1. 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 out the network segment route, the corresponding flow message is delivered to the repeater; and the repeater continuously delivers the flow message to the control surface after receiving the flow message, and the control surface corresponding module counts the user flow and charges.
And step S12, allocating a free address in the second newly allocated dedicated address network segment to the corresponding user terminal.
The embodiment of the disclosure provides an address management method which can be used for distributing address network segments to access transponders according to address use conditions and distributing addresses to user terminals.
Fig. 4 is a flowchart of yet another address management method according to an embodiment of the present disclosure. As shown in fig. 4, the method is an alternative embodiment of the method shown in fig. 2, specifically, the method includes not only steps S1 to S4, but also steps S13 to S19. Only steps S13 to S19 will be described in detail below.
Step S13, receiving an address recycling request.
The address recycling request comprises an address to be recycled.
In some embodiments, in conjunction with the system architecture shown in fig. 1, when a user goes offline, the repeater receives an offline message sent by the user side, and sends the offline message to the load balancing component and the address recycling request, so that the load balancing component obtains the current address of the offline user, and takes the address as the address to be recycled. In general, the load balancing component should also verify the type of message received, and execute the subsequent steps when the message is a user offline message.
In the embodiment of the present disclosure, the expression "reclamation" means an action of actively canceling an address field, or an address configured for an underlying object, for example, reclaiming an address in an address field group, reclaiming an address field in an address field, or the like. In connection with the system architecture shown in fig. 1, for example, the resource pool component recovers the dedicated address segments configured to the forwarder, the resource pool component recovers the addresses allocated to the users, and so on.
Step S14, determining a second target address segment group to which the address to be recovered belongs.
And S15, recycling the address to be recycled in the second target address segment group.
Specifically, the addresses to be reclaimed are reclaimed in the second target address segment group, namely the addresses to be reclaimed in the second target address segment group are marked as free addresses.
In some embodiments, after step S15, further comprising:
and S16, judging whether all the second allocated exclusive address network segments where the addresses to be recovered are located are free addresses.
In step S16, when it is determined that all the second allocated dedicated address segments are free addresses, step S17 is executed; when it is determined that not all the second allocated dedicated address segments are free addresses, no other processing is performed.
Step S17, recycling the second allocated exclusive address network segment in the second target address segment group.
Specifically, the second allocated private address segment is recovered in the second destination address segment group, that is, the correspondence between the second private address segment and the corresponding transponder identifier is canceled.
In some embodiments, in conjunction with the system architecture shown in fig. 1, after the private address segment is recovered, the repeater corresponding to the private address segment should be notified to withdraw the network segment route corresponding to the recovered private address segment.
In some embodiments, after step S17, further comprising:
step S18, judging whether all the second address segments where the recovered second allocated exclusive address network segments are located are free addresses or not;
when judging that all the second address segments are idle addresses, executing step S19; when it is determined that not all the second address segments are free addresses, no other processing is performed.
Step S19, releasing the second address segment in the second target address segment group.
Specifically, the second address segment is released in the second set of target address segments, i.e. deleted from the second set of target address segments.
In some embodiments, in connection with the system architecture shown in FIG. 1, the resource pool component releases the address segment, after which the persisted configuration information can 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, which proactively performs reclamation for the address segment.
In this embodiment of the present disclosure, the expression "release" means an action of actively canceling an address segment, an address network segment, or an address configured by an upper object, for example, releasing an address segment in an address segment group, releasing an address network segment, or the like. In connection with the system architecture shown in FIG. 1, for example, the resource pool component releases address segments of the address pool data management component configuration, and so forth.
It should be noted that, the execution sequence of steps S1 to S4 and steps S13 to S19 is not limited in the technical solution of the present disclosure, that is, steps S1 to S4 may be executed before steps S13 to S19, or steps S1 to S4 may be executed after steps S13 to S19, or steps S1 to S4 and S13 to S19 may be executed synchronously, which is all 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 goes offline, recovering an address network segment when the user goes idle, and releasing the address segment so as to reduce address resource waste.
In the present disclosure, the different steps in the foregoing embodiments may be combined with each other to obtain a new technical solution, and the combined new technical solution should also belong to the protection scope of the present disclosure.
The embodiment of the disclosure provides a server, comprising: one or more processors; a storage means for storing one or more programs; the 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 of the embodiments described above.
The presently disclosed embodiments provide a computer readable storage medium having stored thereon a computer program which, when executed by a processor, performs steps in any of the address management methods of the embodiments described above.
Those of ordinary skill in the art will appreciate that all or some of the steps of the methods, functional modules/units in the apparatus disclosed above may be implemented as software, firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between the 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 cooperatively by several physical components. 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 both 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 known to those skilled 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 be accessed by a computer. Furthermore, as is well known to those of ordinary skill in the art, 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.
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 purpose of limitation. In some instances, it will be apparent to one skilled in the art that features, characteristics, and/or elements described in connection with a particular embodiment may be used alone or in combination with other embodiments unless explicitly stated otherwise. 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 segment group according to a pre-configured load balancing strategy;
judging whether a first allocated exclusive address network segment corresponding to the access transponder identifier exists in the first target address segment group;
when judging that a first allocated exclusive address network segment corresponding to the access transponder identifier exists in the first target address segment group, acquiring the first allocated exclusive address network segment;
the first allocated exclusive address network segment corresponding to the access transponder identifier is a network segment which is allocated exclusive address network segment to the access transponder and is not recovered.
2. The address management method of claim 1, comprising: after the step of obtaining the first allocated 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 free address exists in the first allocated exclusive address network segment, allocating one free address in the first allocated exclusive address network segment to a corresponding user terminal.
3. The address management method of claim 2, wherein,
when judging that the first allocated exclusive address network segment corresponding to the access transponder identifier does not exist in the first target address segment group, further judging whether an unallocated free address network segment exists in the first target address segment group;
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 new allocation exclusive address network segment, and establishing a corresponding relation between the access transponder identifier and the first new allocation exclusive address network segment;
and allocating one free address in the first newly allocated dedicated address network segment to a corresponding user terminal.
4. The address management method of claim 3, wherein,
when judging that the first target address segment group does not have unallocated free address segments, applying for a new address segment for the first target address segment group to serve as a first address segment;
at least one address network segment is divided from the first address segment to serve as a second newly allocated exclusive address network segment, and a corresponding relation between the access transponder identifier and the second newly allocated exclusive address network segment is established;
and allocating a free address in the second newly allocated dedicated address network segment to a corresponding user terminal.
5. The address management method as claimed in claim 3 or 4, wherein,
and when judging that the first allocated exclusive address network segment does not have the free address, executing the step of further judging whether the first target address segment group has the unallocated free address network segment.
6. The address management method according to claim 3 or 4, wherein after establishing the correspondence between the access repeater identification and the newly allocated dedicated address network segment, further comprising:
and issuing a network segment route corresponding to the newly allocated dedicated address network segment according to the access repeater 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 pre-configured load balancing policy and before the step of determining whether there is a first allocated dedicated address segment corresponding to the access repeater identification in the first target address segment group, further comprising:
user authentication is carried out according to the user access protocol message;
and when the user authentication is passed, executing the step of judging whether the first allocated exclusive address network segment corresponding to the access transponder identifier exists in the first target address segment group.
8. The address management method of claim 1, further comprising:
receiving an address reclamation request, the address reclamation request comprising: an address to be recovered;
determining a second target address segment group to which the address to be recovered belongs;
and recycling the address to be recycled in the second target address segment group.
9. The address management method of claim 8, wherein after the step of reclaiming the address to be reclaimed in the second target address segment group, further comprising:
judging whether all the second allocated exclusive address network segments where the addresses to be recovered are located are idle addresses or not;
and when judging that all the second allocated exclusive address network segments are free addresses, recycling 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 recovering the second allocated private address segment in the second set of destination address segments, further comprising:
judging whether all the recovered second address segments where the second allocated exclusive address network segments are located are free addresses or not;
and when judging that all the second address segments are free addresses, releasing the second address segments in the second target address segment group.
11. A server, comprising:
one or more processors;
a storage means for storing one or more programs;
when executed by the one or more processors, causes the one or more processors to implement the address management method of any of claims 1-10.
12. A computer readable storage medium having stored thereon a computer program, wherein the program when executed by a processor implements the steps of the address management method according to any of claims 1-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 CN112995349A (en) | 2021-06-18 |
| CN112995349B true 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) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115150169B (en) * | 2022-06-30 | 2024-02-09 | 北京天融信网络安全技术有限公司 | Policy convergence method, device, system and medium |
| CN116896543A (en) * | 2023-09-11 | 2023-10-17 | 中移(苏州)软件技术有限公司 | IP address allocation method and device, electronic equipment and storage medium |
Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
| 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 |
| JP2016178494A (en) * | 2015-03-20 | 2016-10-06 | 株式会社Ｎｔｔドコモ | Gateway device and communication method |
| 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 |
| 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 (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7593346B2 (en) * | 2003-07-31 | 2009-09-22 | Cisco Technology, Inc. | Distributing and balancing traffic flow in a virtual gateway |
| CN102025528B (en) * | 2009-09-23 | 2013-12-18 | 中兴通讯股份有限公司 | Address management method, device and system |
| WO2012171169A1 (en) * | 2011-06-13 | 2012-12-20 | 华为技术有限公司 | Communications method and load balancer |
| 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 |
| CN102882699B (en) * | 2011-07-14 | 2015-07-29 | 华为技术有限公司 | The distribution method of fringe node and device and fringe node controller |
| 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 |
| CN105306612A (en) * | 2014-07-15 | 2016-02-03 | 中兴通讯股份有限公司 | Method for acquiring identifier of terminal in network and management network element |
| CN105991460B (en) * | 2015-03-02 | 2019-09-06 | 杭州迪普科技股份有限公司 | Flow load retransmission method, master control borad, business board and the network equipment |
| CN106331192B (en) * | 2015-06-23 | 2020-12-04 | 中兴通讯股份有限公司 | Network protocol IP address allocation method and device |
| CN108959127B (en) * | 2018-05-31 | 2021-02-09 | 华为技术有限公司 | Address translation method, device and system |
| CN109525684B (en) * | 2018-12-11 | 2022-09-30 | 杭州数梦工场科技有限公司 | Message forwarding method and device |
-
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 (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9043463B1 (en) * | 2009-03-30 | 2015-05-26 | Amazon Technologies, Inc. | Providing extendible network capabilities for managed computer networks |
| 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 |
| CN104320353A (en) * | 2014-11-19 | 2015-01-28 | 中国联合网络通信集团有限公司 | User address managing method and device |
| JP2016178494A (en) * | 2015-03-20 | 2016-10-06 | 株式会社Ｎｔｔドコモ | Gateway device and communication method |
| 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 |
Non-Patent Citations (1)
| Title |
|---|
| SDN在金融数据中心网络中的应用;何朔;;计算机应用与软件(10);198-204 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112995349A (en) | 2021-06-18 |
| WO2021115183A1 (en) | 2021-06-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105323136B (en) | Information processing method and device | |
| US11646973B2 (en) | Method for managing hardware resource, method for querying location of hardware resource, and related apparatus | |
| US20170373931A1 (en) | Method for updating network service descriptor nsd and apparatus | |
| EP3664420B1 (en) | Managing address spaces across network elements | |
| CN112995349B (en) | Address management method, server, and computer-readable storage medium | |
| WO2020001045A1 (en) | Address management method and device | |
| CN108390956A (en) | A kind of method and system for virtual machine configuration internet protocol address | |
| CN110661894A (en) | User IP address allocation method, network device and storage medium | |
| CN113452806B (en) | Container adaptation SDN network management method and system based on Kubernets system | |
| CN105979202B (en) | Data transmission method and device | |
| CN105704042A (en) | Message processing method, BNG and BNG cluster system | |
| CN106453690A (en) | IP address allocation method and apparatus | |
| CN108933844B (en) | Method and equipment for providing DHCP service | |
| CN115843429A (en) | Method and apparatus for isolation support in network slicing | |
| CN108540408B (en) | Openstack-based distributed virtual switch management method and system | |
| CN110391961B (en) | Tunnel binding method, device and system | |
| CN110933192A (en) | Local area network IP address allocation method, device, system and computer equipment | |
| CN111131529B (en) | Method, device and storage medium for centralized management of address pools | |
| US11811879B2 (en) | Networking connection management based on container identification | |
| CN108259345B (en) | Port generation method and device | |
| CN113904871B (en) | Access method of network slice, PCF entity, terminal and communication system | |
| CN110460683B (en) | Method and switching equipment for processing data message through gateway | |
| CN112152899B (en) | Data processing method and device based on network slice | |
| WO2021057150A1 (en) | Port sharing method and apparatus, storage medium and electronic apparatus | |
| CN109933959B (en) | License control method and related equipment |
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 |