CN104348927A - Address field assignment method and apparatus - Google Patents

Abstract

Embodiments of the present invention provide a method and device for allocating address segments, the method comprising: the first BRAS determines the first sub-address segment to be applied for from the available address segments of the machine; the first BRAS sends the second sub-address segment to the second BRAS An address request message, the first address request message carries the first sub-address segment, and the address segment of the first BRAS overlaps with the address segment of the second BRAS; the first BRAS receives the first sub-address segment The address request response returned by the second BRAS, the address request response is used to indicate that the second BRAS allows the first BRAS to apply for the first sub-address segment; when it is determined that the second BRAS allows the first BRAS to apply After the first sub-address segment, the first BRAS allocates an address for the user equipment from the first sub-address segment. The method and device for allocating address segments provided by the embodiments of the present invention can improve the utilization efficiency of address segments.

Description

Address segment allocation method and device

technical field

Embodiments of the present invention relate to communication technologies, and in particular to a method and device for allocating address segments.

Background technique

The broadband MAN service control layer is a unique layer where the service access network connects to the core switching network, and the equipment that plays an important role is the Broadband Remote Access Server (BRAS for short). BRAS provides basic access means and manages the broadband access network.

In the prior art, a Dynamic Host Configuration Protocol (DHCP for short) server is deployed centrally on the entire network. When the user equipment is connected to the BRAS through the Point-to-Point Protocol over Ethernet (PPPOE), the BRAS applies for an IP address from the DHCP server through the DHCP agent or DHCP relay, and assigns the IP address to the user equipment.

When the local users of the BRAS have not used up the address segments configured on the BRAS, the remaining address segments will be generated. However, other BRASs cannot use the remaining address segment, which will lead to low utilization efficiency of the address segment.

Contents of the invention

Embodiments of the present invention provide a method and device for allocating address segments to improve the use efficiency of address segments.

In a first aspect, an embodiment of the present invention provides a method for allocating address segments, including:

The first broadband access server BRAS determines the first sub-address segment that needs to be applied for from the available address segment of the machine;

The first BRAS sends a first address request message to the second BRAS, the first address request message carries the first sub-address segment, and the address segment of the first BRAS and the address segment of the second BRAS exist intersection;

The first BRAS receives an address request response returned by the second BRAS, where the address request response is used to indicate that the second BRAS allows the first BRAS to apply for the first sub-address segment;

After determining that the second BRAS allows the first BRAS to apply for the first sub-address segment, the first BRAS allocates an address for the user equipment from the first sub-address segment.

With reference to the first aspect, in a first possible implementation manner of the first aspect, the method further includes:

The first BRAS receives a second address request message sent by the second BRAS, where the second address request message carries a second sub-address segment to be applied for;

After the first BRAS determines that it is necessary to apply for the first sub-address segment, when the first sub-address segment is consistent with the second sub-address segment, the first BRAS compares the priority and the priority of said second BRAS;

When the priority of the first BRAS is higher than the priority of the second BRAS, the first BRAS refuses the second BRAS to apply for the second sub-address segment.

With reference to the first possible implementation of the first aspect, in a second possible implementation of the first aspect, the method further includes:

When the priority of the first BRAS is equal to the priority of the second BRAS, comparing the IP address of the first BRAS with the IP address of the second BRAS;

When the comparison result does not satisfy the condition for allowing the second BRAS to apply for the second sub-address segment, the first BRAS refuses the second BRAS to apply for the second sub-address segment.

With reference to the first possible implementation of the first aspect, in a third possible implementation of the first aspect, the method further includes:

After the first BRAS determines that it is necessary to apply for the first sub-address segment, when the first sub-address segment does not overlap with the second sub-address segment and the second sub-address segment belongs to the first BRAS When there is an available address segment, the first BRAS allows the second BRAS to apply for the second sub-address segment, and removes the second sub-address segment from the available address segment of the first BRAS.

In a second aspect, an embodiment of the present invention provides a method for allocating address segments, including:

The second broadband access server BRAS receives the first address request message sent by the first BRAS, the first address request message carries the first sub-address segment that the first BRAS needs to apply for, the address segment of the first BRAS and There is an intersection between the address segments of the second BRAS;

The second BRAS determines whether the first sub-address segment is an available address segment in the address segment of the second BRAS;

After determining that the first sub-address segment is an available sub-address segment in the address segment of the second BRAS, return an address request response to the first BRAS, where the address request response is used to indicate the second BRAS Allowing the first BRAS to apply for the first sub-address segment.

With reference to the second aspect, in the first possible implementation manner of the second aspect, after determining that the first sub-address segment is an available sub-address segment in the address segment of the second BRAS, send the The BRAS return address request response specifically includes:

The second BRAS determines whether the first sub-address segment is consistent with the second sub-address segment that the second BRAS needs to apply for;

If not, the second BRAS returns an address request response to the first BRAS.

With reference to the second aspect, in a second possible implementation manner of the second aspect, after determining that the first sub-address segment is an available sub-address segment in the address segment of the second BRAS, send the The BRAS return address request response specifically includes:

The second BRAS determines whether the first sub-address segment is consistent with the second sub-address segment that the second BRAS needs to apply for;

If so, the second BRAS compares the priority of the first BRAS with the priority of the second BRAS;

When the priority of the first BRAS is higher than the priority of the second BRAS, the second BRAS returns an address request response to the first BRAS.

With reference to the second possible implementation manner of the second aspect, in a third possible implementation manner of the second aspect, the method further includes:

When the comparison result is that the priority of the first BRAS is the same as that of the second BRAS, the second BRAS compares the IP address of the first BRAS with the IP address of the second BRAS;

When the comparison result satisfies the condition of allowing the first BRAS to apply for the first sub-address segment, the second BRAS returns an address request response to the first BRAS.

In combination with the second aspect and any one of the first to third possible implementations of the second aspect, in a fourth possible implementation of the second aspect, the method further includes:

When the second BRAS allows the first BRAS to apply for the first sub-address segment, the second BRAS removes the first sub-address segment from available address segments of the second BRAS.

In a third aspect, an embodiment of the present invention provides a first broadband access server BRAS, including:

An application module, configured to determine the first sub-address segment to be applied for from the available address segments of the machine;

A sending module, configured to send a first address request message to a second BRAS, where the first address request message carries the first sub-address segment, and the address segment of the first BRAS and the address segment of the second BRAS exist intersection;

A first receiving module, configured to receive an address request response returned by the second BRAS, where the address request response is used to indicate that the second BRAS allows the first BRAS to apply for the first sub-address segment;

An allocating module, configured to allocate an address for the user equipment from the first sub-address segment after determining that the second BRAS allows the first BRAS to apply for the first sub-address segment.

In combination with the third aspect, the first possible implementation of the third aspect further includes:

A second receiving module, configured to receive a second address request message sent by the second BRAS, where the second address request message carries a second sub-address segment to be applied for;

The first comparison module is configured to compare the first BRAS when the first sub-address segment is consistent with the second sub-address segment after the first BRAS determines that it needs to apply for the first sub-address segment and the priority of the second BRAS;

The first responding module is configured to reject the second BRAS to apply for the second sub-address segment when the priority of the first BRAS is higher than the priority of the second BRAS.

In combination with the first possible implementation of the third aspect, the second possible implementation of the third aspect further includes:

A second comparison module, configured to compare the IP address of the first BRAS with the IP address of the second BRAS when the priority of the first BRAS is equal to the priority of the second BRAS;

The second response module is configured to reject the second BRAS from applying for the second sub-address segment when the comparison result does not satisfy the condition for allowing the second BRAS to apply for the second sub-address segment.

In combination with the first possible implementation of the third aspect, the third possible implementation of the third aspect also includes:

A removal module, configured to, after the first BRAS determines that it is necessary to apply for the first sub-address segment, when the first sub-address segment does not overlap with the second sub-address segment and the second sub-address segment belongs to When the available address segment of the first BRAS is available, the second BRAS is allowed to apply for the second sub-address segment, and the second sub-address segment is removed from the available address segment of the first BRAS.

In a fourth aspect, the embodiment of the present invention provides a second broadband access server BRAS, including:

A receiving module, configured to receive a first address request message sent by a first BRAS, where the first address request message carries a first sub-address segment that the first BRAS needs to apply for, the address segment of the first BRAS and the There is an intersection between the address segments of the second BRAS;

A determining module, configured to determine whether the first sub-address segment is an available address segment in the address segment of the second BRAS;

A response module, configured to return an address request response to the first BRAS after determining that the first sub-address segment is an available sub-address segment in the address segment of the second BRAS, where the address request response is used to indicate The second BRAS allows the first BRAS to apply for the first sub-address segment.

With reference to the fourth aspect, in a first possible implementation manner of the fourth aspect, the response module is specifically configured to:

Determine whether the first sub-address segment is consistent with the second sub-address segment that the second BRAS needs to apply for;

If not, return an address request response to the first BRAS.

With reference to the fourth aspect, in a second possible implementation manner of the fourth aspect, the response module is specifically configured to:

Determine whether the first sub-address segment is consistent with the second sub-address segment that the second BRAS needs to apply for;

If so, comparing the priority of the first BRAS with the priority of the second BRAS;

When the priority of the first BRAS is higher than the priority of the second BRAS, return an address request response to the first BRAS.

In conjunction with the second possible implementation of the fourth aspect, in the third possible implementation of the fourth aspect, the response module is further specifically configured to:

When the comparison result is that the priority of the first BRAS is the same as the priority of the second BRAS, comparing the IP address of the first BRAS with the IP address of the second BRAS;

When the comparison result satisfies the condition of allowing the first BRAS to apply for the first sub-address segment, return an address request response to the first BRAS.

In combination with the fourth aspect and any of the first to third possible implementations of the fourth aspect, the fourth possible implementation of the fourth aspect further includes:

A removing module, configured to remove the first sub-address segment from available address segments of the second BRAS when the second BRAS allows the first BRAS to apply for the first sub-address segment.

In the address segment allocation method and device provided in the embodiments of the present invention, the first BRAS determines the first sub-address segment to be applied for from the available address segments of the local machine; the first BRAS sends a first address request message to the second BRAS, The first address request message carries the first sub-address segment, and the address segment of the first BRAS overlaps with the address segment of the second BRAS; the first BRAS receives the address returned by the second BRAS A request response, the address request response is used to indicate that the second BRAS allows the first BRAS to apply for the first sub-address segment; after determining that the second BRAS allows the first BRAS to apply for the first sub-address segment After the address segment, the first BRAS allocates an address for the user equipment from the first sub-address segment. Each BRAS realizes the sharing of the address segment of each BRAS through negotiation, which improves the utilization rate of the address segment, and does not need to allocate the address segment through a unified network element, which solves the problem of allocation bottleneck.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description These are some embodiments of the present invention. For those skilled in the art, other drawings can also be obtained according to these drawings without any creative effort.

Fig. 1 is the flow chart of Embodiment 1 of the method for allocating address segments of the present invention;

Fig. 2 is the flow chart of Embodiment 2 of the address segment allocation method of the present invention;

FIG. 3 is a signaling diagram of Embodiment 3 of the address segment allocation method of the present invention;

FIG. 4 is a signaling diagram of Embodiment 4 of the address segment allocation method of the present invention;

FIG. 5 is a schematic structural diagram of Embodiment 1 of the first BRAS of the present invention;

FIG. 6 is a schematic structural diagram of Embodiment 2 of the first BRAS of the present invention;

FIG. 7 is a schematic structural diagram of Embodiment 1 of the second BRAS of the present invention;

FIG. 8 is a schematic structural diagram of Embodiment 2 of the second BRAS of the present invention.

Detailed ways

In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments It is a part of embodiments of the present invention, but not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without creative efforts fall within the protection scope of the present invention.

FIG. 1 is a flow chart of Embodiment 1 of the method for allocating address segments in the present invention. This embodiment provides a method for allocating address segments, which can be executed by an address segment allocating device, and the device can be implemented by software and/or hardware. Specifically, the device can be a broadband access server (Broadband Remote Access Server, referred to as BRAS), in which there are generally multiple BRASs, which are located on the edge of the backbone network, and can allocate access addresses for users, so that users can realize the interconnection between networks with high bandwidth. Data access to the Internet Protocol (IP) network. The BRASs communicate with each other to realize the sharing of the address segments of the BRASs and improve the utilization rate of the address segments. Those skilled in the art can understand that, in a specific implementation process, each BRAS may be either the first BRAS or the second BRAS. That is, each BRAS includes the functions of the first BRAS and the functions of the second BRAS. In this embodiment, firstly, the first BRAS is used as an execution subject, and the method for allocating address segments is described in detail. As shown in Figure 1, the method of this embodiment may include:

Step 101: the first BRAS determines the first sub-address segment to be applied for from the available address segments of the local computer.

In the specific implementation process, firstly, address segments can be configured in each BRAS. Among them, the address segments configured on each BRAS must overlap with the address segments configured on other BRASs. A maximum of 32 address segments can be configured on each BRAS. The range is 0-31. In particular, the BRASs whose address segments overlap form an address sharing group.

When the user equipment accesses one of the BRASs through PPPOE or DHCP, for the convenience of description, this embodiment is referred to as the first BRAS here, that is, when the user equipment accesses the first BRAS, the first BRAS selects the first BRAS from the local available address range Determine the first sub-address segment that needs to be applied for. Among them, the available address segment of the machine is the address segment not allocated to the user. When the sub-address segment in the address segment is assigned to the user of the first BRAS, or the sub-address segment is allocated to the user by other BRAS, the assigned sub-address segment is a used sub-address segment, and the sub-address segment needs to be removed from Remove from the available address segment of the local machine to obtain a new available address segment of the local machine. In the specific implementation process, the first BRAS can record the used sub-address section to obtain a record table, and when applying for a sub-address section again, exclude the sub-address section recorded in the record table, and use the available address section from the local machine. Apply for a sub-address segment.

Step 102: the first BRAS sends a first address request message to the second BRAS, the first address request message carries a first sub-address segment, and the address segment of the first BRAS overlaps with the address segment of the second BRAS.

Because there is an intersection between the address segment of the first BRAS and the address segment of the second BRAS, after the first BRAS determines the first sub-address segment that needs to be applied for from the available address segment of this machine, the first BRAS needs to report to the second BRAS (that is, other BRASs) send a first address request message, wherein the first address request message carries the first sub-address segment, so that all second BRASs determine whether the first BRAS can use the first sub-address segment. In particular, the address sharing group may include a maximum of 65535 BRASs, and each BRAS has its own identifier, and the first BRAS may send an address request message to each second BRAS according to the identifiers of each second BRAS.

Step 103: the first BRAS receives the address request response returned by the second BRAS, where the address request response is used to instruct the second BRAS to allow the first BRAS to apply for the first sub-address segment.

When the second BRAS allows the first BRAS to apply for the first sub-address segment, it returns an address request response to the first BRAS, which is used to instruct the second BRAS to allow the first BRAS to apply for the first sub-address segment. The first BRAS receives the address request response returned by the second BRAS.

Step 104: After determining that the second BRAS allows the first BRAS to apply for the first sub-address segment, the first BRAS allocates an address for the user equipment from the first sub-address segment.

After receiving the address request response returned by the second BRAS, the first BRAS determines that the second BRAS allows the first BRAS to apply for the first sub-address segment, and the first BRAS allocates an address for the user equipment from the first sub-address segment. At the same time, the first BRAS removes the first sub-address segment from the remaining available address segment to form a new available address segment, and when the first BRAS applies for a sub-address again, it determines the first sub-address that needs to be applied for in the new available address segment. Sub address segment.

In the address segment allocation method provided by the embodiment of the present invention, the first BRAS determines the first sub-address segment to be applied for from the available address segments of the local machine; the first BRAS sends a first address request message to the second BRAS, and the first address request The message carries the first sub-address segment, and the address segment of the first BRAS overlaps with the address segment of the second BRAS; the first BRAS receives the address request response returned by the second BRAS, and the address request response is used to instruct the second BRAS to allow the first BRAS Apply for the first sub-address segment; after confirming that the second BRAS allows the first BRAS to apply for the first sub-address segment, the first BRAS allocates an address for the user equipment from the first sub-address segment, and each BRAS realizes that each BRAS The address segment sharing improves the utilization rate of the address segment, and it is not necessary to allocate the address segment through a unified network element, which solves the problem of allocation bottleneck.

On the basis of the embodiment in Fig. 1, the address segment allocation method provided by the embodiment of the present invention further includes: the first BRAS receives the second address request message sent by the second BRAS, and the second address request message carries the second sub-address to be applied for segment; the first BRAS determines whether the second BRAS can apply for the second sub-address segment according to whether the first sub-address segment is consistent with the second sub-address segment

In a specific implementation process, the first BRAS determines whether the second BRAS can apply for the second sub-address segment according to whether the first sub-address segment is consistent with the second sub-address segment. Specifically, it can be divided into the following possible implementation methods:

A possible implementation is that after the first BRAS determines that it is necessary to apply for the first sub-address segment, when the first sub-address segment is consistent with the second sub-address segment, the first BRAS compares the priority of the first BRAS with the priority of the first BRAS. Two BRAS priorities.

In the specific implementation process, each BRAS in the address sharing group has its own priority, and the value range of the priority is 0-65535, and the smaller the value of the priority, the higher the priority. Meanwhile, the second address request message sent by the second BRAS may further include the priority of the second BRAS. When the first sub-address segment is consistent with the second sub-address segment, the BRAS with a higher priority obtains the corresponding sub-address segment, and the BRAS with a lower priority applies for a sub-address segment again. Those skilled in the art can understand that, in a specific implementation process, it may happen that the priorities configured by the first BRAS and the second BRAS are the same.

The first BRAS compares the priority of the first BRAS and the second BRAS, and determines whether to allow the second BRAS to apply for the second sub-address segment according to the priority comparison result, specifically there may be three possible situations:

In a possible situation, when the priority of the first BRAS is higher than that of the second BRAS, the first BRAS refuses the second BRAS to apply for the second sub-address segment. In a specific implementation process, the first BRAS may send an address rejection response to the second BRAS to reject the application of the second BRAS, and the first BRAS may not make any response.

In another possible situation, when the priority of the first BRAS is lower than that of the second BRAS, the first BRAS allows the second BRAS to apply for the second sub-address segment. In a specific implementation process, the first BRAS sends an address request response to the second BRAS to allow the second BRAS to apply for the second sub-address segment.

In another possible situation, when the priority of the first BRAS is equal to the priority of the second BRAS, compare the IP address of the first BRAS and the IP address of the second BRAS; When the condition of the second sub-address segment is met, the first BRAS rejects the application of the second sub-address segment by the second BRAS. In the specific implementation process, if the IP address value of the first BRAS is less than the IP address value of the second BRAS, then the first BRAS determines that the second BRAS is not allowed to apply for the second sub-address segment, if the IP address value of the first BRAS is greater than the second sub-address segment The IP address value of the second BRAS, then the first BRAS determines to allow the second BRAS to apply for the second sub-address segment.

Another possible implementation is that after the first BRAS determines that it needs to apply for the first sub-address segment, when there is no intersection between the first sub-address segment and the second sub-address segment and the second sub-address segment belongs to the available address of the first BRAS When the segment is available, the first BRAS allows the second BRAS to apply for the second sub-address segment, and removes the second sub-address segment from the available address segments of the first BRAS.

In the specific implementation process, the first BRAS sends an address request response to the second BRAS to allow the second BRAS to apply for the second sub-address segment, and remove the second sub-address segment from the remaining available address segments to form a new available address segment , when the first BRAS applies for the first sub-address segment again, it determines the first sub-address segment to be applied for in the new available address segment.

In the address segment allocation method provided in the embodiment of the present invention, the first BRAS receives the second address request message sent by the second BRAS, and the first BRAS determines the first sub-address segment that the first BRAS needs to apply for and the second address segment that the second BRAS needs to apply for. Whether the two sub-address segments are consistent, when the first BRAS determines that the first sub-address segment that needs to be applied for is consistent with the second sub-address segment that the second BRAS needs to apply for, then the first BRAS determines whether to allow the second BRAS application according to the priority The second sub-address section not only realizes the sharing of the address sections of the BRASs, but also ensures that the same address section is only used by one BRAS at the same time, so that the BRAS can allocate addresses to the user equipment from the sub-address section in an orderly manner.

FIG. 2 is a flow chart of Embodiment 2 of the address segment allocation method of the present invention. This embodiment provides a method for allocating address segments, which can be executed by an address segment allocating device, and the device can be implemented by software and/or hardware. Specifically, the device can be a broadband access server (Broadband Remote Access Server, referred to as BRAS), in which there are generally multiple BRASs, which are located on the edge of the backbone network, and can allocate access addresses for users, so that users can realize the interconnection between networks with high bandwidth. Data access to the Internet Protocol (IP) network. The BRASs communicate with each other to realize the sharing of the address segments of the BRASs and improve the utilization rate of the address segments. Those skilled in the art can understand that, in a specific implementation process, each BRAS may be either the first BRAS or the second BRAS. In this embodiment, the second BRAS is used as the execution subject, and the method for allocating address segments is described in detail. As shown in Figure 2, the method of this embodiment may include:

Step 201, the second BRAS receives the first address request message sent by the first BRAS, the first address request message carries the first sub-address segment that the first BRAS needs to apply for, the address segment of the first BRAS and the address segment of the second BRAS exist intersection;

Those skilled in the art can understand that, in the specific implementation process, the second BRAS receives the first address request message sent by one or more first BRASs, wherein the first address request message carries the first sub-address segment applied by the first BRAS , an intersection exists between the address segment of the first BRAS and the address segment of the second BRAS. At the same time, the first sub-address segments may be discontinuous. When the first sub-address segments are multi-segments, the number of the first sub-address segments is also indicated in the first address request message.

Step 202, the second BRAS determines whether the first sub-address segment is an available address segment in the address segment of the second BRAS;

Since there is an intersection between the address segment of the first BRAS and the address segment of the second BRAS, the second BRAS needs to determine whether the first address segment is an available address segment in the address segment of the second BRAS. When the second BRAS determines that the first sub-address segment is not an available address segment in the address segment of the second BRAS, the second BRAS allows the first BRAS to apply for the first sub-address segment. When the second BRAS determines that the first sub-address segment is an available address segment in the address segments of the second BRAS, go to step 203 .

Step 203, after determining that the first sub-address segment is an available address segment in the address segment of the second BRAS, return an address request response to the first BRAS, and the address request response is used to indicate that the second BRAS allows the first BRAS to apply for the first sub-address segment. address segment.

Specifically, after determining that the first sub-address segment is an available address segment in the address segment of the second BRAS, the second BRAS returns an address response to the first BRAS, specifically including the following process:

The second BRAS determines whether the first sub-address segment is consistent with the second sub-address segment that the second BRAS needs to apply for;

If not, the second BRAS returns an address request response to the first BRAS, specifically, when the first sub-address segment is inconsistent with the second sub-address segment, it means that the second BRAS does not currently use the first sub-address segment, and the current If there is no application for using the first sub-address segment, the second BRAS returns an address request response to the first BRAS.

If so, the second BRAS compares the priority of the first BRAS with the priority of the second BRAS. Each BRAS has its own priority. The value range of the priority is 0-65535. The smaller the value of the priority, the higher the priority. higher.

When the priority of the first BRAS is higher than that of the second BRAS, the second BRAS returns an address request response to the first BRAS.

When the priority of the first BRAS is lower than that of the second BRAS, the second BRAS ignores the first address request message sent by the first BRAS, that is, does not make any reply, or returns an address rejection response to the first BRAS.

When the comparison result is that the priority of the first BRAS is the same as that of the second BRAS, the second BRAS compares the IP address of the first BRAS with the IP address of the second BRAS; when the result of the comparison is satisfied, the first BRAS is allowed to apply for the first When the conditions of the sub-address segment are met, the second BRAS returns an address request response to the first BRAS. Specifically, the IP address is the IP address for the BRAS to send the address request message. If the IP address value of the first BRAS is less than the IP address value of the second BRAS, then the second BRAS allows the first BRAS to apply, if the IP address value of the first BRAS is greater than the IP address value of the second BRAS, then the second BRAS determines not to First BRAS applications are permitted.

Optionally, when the second BRAS allows the first BRAS to apply for the first sub-address segment, the second BRAS removes the first sub-address segment from the available address segments of the second BRAS. In this way, it is guaranteed that the management of the second BRAS to the available address segment will not cause the address conflict between the first BRAS and the second BRAS, and when the second BRAS applies for the second sub-address segment again, it will not apply for the first BRAS being The address segment to use.

In the method for allocating address segments provided by the embodiments of the present invention, the second BRAS receives the first address request message sent by the first BRAS, the first address request message carries the first sub-address segment that the first BRAS needs to apply for, and the address of the first BRAS segment and the address segment of the second BRAS have an intersection; the second BRAS determines whether the first sub-address segment is an available address segment in the address segment of the second BRAS; After the sub-address section is available, an address request response is returned to the first BRAS, and the address request response is used to indicate that the second BRAS allows the first BRAS to apply for the first sub-address section, which not only realizes the sharing of the address sections of each BRAS, but also ensures The same address segment is only used by one BRAS at the same time, so that the BRAS can allocate addresses to the user equipment from the sub-address segment in an orderly manner.

FIG. 3 is a signaling diagram of Embodiment 3 of the address segment allocation method of the present invention. The address segment allocation method provided by the embodiment of the present invention will be described in detail below with reference to FIG. 3 . In FIG. 3 , BRAS-A can be understood as a first BRAS, and BRAS-B and BRAS-C can be understood as a second BRAS. The BRAS-A, BRAS-B, and BRAS-C are briefly described below.

BRAS-A, the priority value is 100, the configured address segment is 10.0.1-10.0.255.255, and the length of the first sub-address segment is 255; BRAS-B, the priority value is 200, and the configured address segment is 10.0.1-10.0. 255.255, the length of the second sub-address segment is 255; BRAS-C, the priority value is 250, the configured address segment is 10.0.1-10.0.255.255, the length of the second sub-address segment is 255;

In a specific implementation process, BRAS-A may send address request messages to BRAS-B and BRAS-C according to the identities of BRAS-B and BRAS-C. The specific process is as follows:

Step 301, BRAS-A sends a first address request message to BRAS-B, and the first address request message carries the first sub-address segment 10.0.0.1-10.0.0.255;

Step 302, BRAS-A sends a first address request message to BRAS-C, and the first address request message carries the first sub-address segment 10.0.0.1-10.0.0.255;

Those skilled in the art can understand that there is no strict timing relationship between step 301 and step 302. In a specific implementation process, BRAS-A may send the first address request message to BRAS-B and BRAS-C at the same time.

Step 303, BRAS-B determines that the first sub-address segment that BRAS-A needs to apply for is inconsistent with the second sub-address segment that BRAS-B needs to apply for;

Step 304, BRAS-C determines that the first sub-address segment that BRAS-A needs to apply for is inconsistent with the second sub-address segment that BRAS-B needs to apply for;

In the actual application process, after receiving the first address request message sent by BRAS-A, BRAS-B and BRAS-C will check whether the first sub-address segment of BRAS-A and the second sub-address segment that the machine needs to apply for are unanimous. Among them, the first sub-address segment that BRAS-A needs to apply for is inconsistent with the second sub-address segment that BRAS-B and BRAS-C need to apply for. Specifically, it can include two situations, one is that BRAS-A and BRAS-B and BRAS-C The second sub-address segments that C needs to apply for are inconsistent, and the other is that BRAS-B and BRAS-C have not applied for sub-addresses at this time.

Step 305, BRAS-B sends to BRAS-A the address request response that allows BRAS-A to apply for the first sub-address segment;

Step 306, BRAS-C sends to BRAS-A the address request response that allows BRAS-A to apply for the first sub-address segment;

Those skilled in the art can understand that step 305 and step 306 do not have a strict timing relationship. In the specific implementation process, BRAS-B and BRAS-C can simultaneously send to BRAS-A an address request response allowing BRAS-A to apply, or There is a sequence.

Step 307, BRAS-C removes the first sub-address segment from the remaining available address segments;

Step 308, BRAS-B removes the first sub-address segment from the remaining available address segments;

Step 309, BRAS-A removes the first sub-address segment from the remaining available address segments.

Those skilled in the art can understand that in the specific implementation process, there is no strict timing relationship between step 307 and step 309. As long as the first sub-address segment is successfully applied by any BRAS, all BRASs will remove this sub-address segment from the remaining available address segments. The first sub-address segment.

As can be seen from Fig. 3, in the specific implementation process, only when BRAS-B and BRAS-C all send to BRAS-A the address request response that allows BRAS-A to apply for the first subaddress section, BRAS-A just can use this first subaddress section. Sub address segment.

FIG. 4 is a signaling diagram of Embodiment 4 of the address segment allocation method of the present invention. The address segment allocation method provided by the embodiment of the present invention will be described in detail below with reference to FIG. 4 . Wherein, the priority value of the first BRAS is 100, and the priority value of the second BRAS is 200.

Step 401, the first BRAS sends a first address request message to the second BRAS, and the first address request message carries the first sub-address segment 10.0.0.1-10.0.0.255;

Step 402, the second BRAS sends a second address request message to the first BRAS, and the second address request message carries the second sub-address segment 10.0.0.1-10.0.0.255;

Those skilled in the art can understand that there is no strict timing relationship between step 401 and step 402, and the first BRAS and the second BRAS can send address request messages to each other at the same time.

Step 403, the first BRAS determines that the priority of the first BRAS is higher than the priority of the second BRAS;

When the first BRAS determines that the first sub-address segment is consistent with the second sub-address segment that the second BRAS needs to apply for, the first BRAS determines that the priority of the first BRAS is higher than that of the second BRAS. The first BRAS may not perform any processing.

Step 404, the second BRAS determines that the priority of the second BRAS is lower than the priority of the first BRAS;

When the second BRAS determines that the second sub-address segment is consistent with the first sub-address segment that the first BRAS needs to apply for, the second BRAS determines that the priority of the second BRAS is lower than that of the first BRAS.

Step 405, the second BRAS sends an address request response allowing the first BRAS to apply for the first sub-address segment to the first BRAS;

When the second BRAS determined that the priority of the second BRAS was lower than the priority of the first BRAS, the second BRAS determined that this machine could not apply for the second sub-address segment, and sent to the first BRAS to allow the first BRAS to apply for the first sub-address segment The address request response.

Step 406, the first BRAS removes the first sub-address segment from the remaining available address segments;

Step 407, the second BRAS removes the first sub-address segment from the remaining available address segments;

Those skilled in the art can understand that step 406 and step 407 do not have a strict time sequence relationship.

Step 408, the second BRAS sends a second address request message to the first BRAS, and the second address request message carries the sub-address segment 10.0.1.1-10.0.1.255.

When the second BRAS cannot obtain the sub-address segment, the second BRAS resends the address request message to the first BRAS. For possible implementations after step 408, refer to FIG. 3 and FIG. 4 .

FIG. 5 is a schematic structural diagram of Embodiment 1 of the first BRAS of the present invention. As shown in FIG. 5 , the first BRAS 50 provided by the present invention includes an application module 501 , a sending module 502 , a first receiving module 503 and an allocation module 504 .

An application module 501, configured to determine the first sub-address segment that needs to be applied for from the available address segments of the machine;

A sending module 502, configured to send a first address request message to a second BRAS, where the first address request message carries the first sub-address segment, the address segment of the first BRAS and the address segment of the second BRAS There is an intersection;

The first receiving module 503 is configured to receive an address request response returned by the second BRAS, where the address request response is used to indicate that the second BRAS allows the first BRAS to apply for the first sub-address segment;

The allocating module 504 is configured to allocate an address for the user equipment from the first sub-address segment after determining that the second BRAS allows the first BRAS to apply for the first sub-address segment.

The first BRAS in this embodiment can be used to implement the technical solution in the embodiment in FIG. 1 , and its implementation principle and technical effect are similar, and will not be repeated here.

FIG. 6 is a schematic structural diagram of Embodiment 2 of the first BRAS of the present invention. As shown in Figure 6, on the basis of the embodiment shown in Figure 5, this embodiment also includes:

The second receiving module 505 is configured to receive a second address request message sent by the second BRAS, where the second address request message carries a second sub-address segment to be applied for;

The first comparison module 506 is configured to compare the first sub-address segment when the first sub-address segment is consistent with the second sub-address segment after the first BRAS determines that the first sub-address segment needs to be applied for. the priority of the BRAS and the priority of the second BRAS;

The first responding module 507 is configured to refuse the second BRAS to apply for the second sub-address segment when the priority of the first BRAS is higher than the priority of the second BRAS.

Optionally, also include:

A second comparison module 508, configured to compare the IP address of the first BRAS with the IP address of the second BRAS when the priority of the first BRAS is equal to the priority of the second BRAS;

The second response module 509 is configured to deny the second BRAS to apply for the second sub-address segment when the comparison result does not satisfy the condition for allowing the second BRAS to apply for the second sub-address segment.

Optionally, also include:

The removal module 510 is configured to, after the first BRAS determines that it is necessary to apply for the first sub-address segment, when the first sub-address segment does not overlap with the second sub-address segment and the second sub-address segment When it belongs to the available address segment of the first BRAS, the second BRAS is allowed to apply for the second sub-address segment, and the second sub-address segment is removed from the available address segment of the first BRAS.

The first BRAS in this embodiment may be used to implement the technical solutions of the foregoing method embodiments, and its implementation principles and technical effects are similar, and details are not repeated here.

FIG. 7 is a schematic structural diagram of Embodiment 1 of the second BRAS of the present invention. As shown in FIG. 7 , the second BRAS 70 provided by the embodiment of the present invention includes: a receiving module 701 , a determining module 702 and a responding module 703 .

Wherein, the receiving module 701 is configured to receive the first address request message sent by the first BRAS, the first address request message carries the first sub-address segment that the first BRAS needs to apply for, and the address segment of the first BRAS There is an intersection with the address segment of the second BRAS;

A determination module 702, configured to determine whether the first sub-address segment is an available address segment in the address segment of the second BRAS;

The response module 703 is configured to return an address request response to the first BRAS after determining that the first sub-address segment is an available sub-address segment in the address segment of the second BRAS, and the address request response is used for Instructing the second BRAS to allow the first BRAS to apply for the first sub-address segment.

The second BRAS in this embodiment can be used to execute the technical solution of the method embodiment shown in FIG. 2 , and its implementation principle and technical effect are similar, and details are not repeated here.

FIG. 8 is a schematic structural diagram of Embodiment 2 of the second BRAS of the present invention. As shown in FIG. 8, this embodiment is based on the embodiment shown in FIG. 7, and the response module 703 is specifically used for:

Determine whether the first sub-address segment is consistent with the second sub-address segment that the second BRAS needs to apply for;

If not, return an address request response to the first BRAS.

Optionally, the response module 703 is specifically configured to:

Determine whether the first sub-address segment is consistent with the second sub-address segment that the second BRAS needs to apply for;

If so, comparing the priority of the first BRAS with the priority of the second BRAS;

When the priority of the first BRAS is higher than the priority of the second BRAS, return an address request response to the first BRAS.

Optionally, the response module 703 is further specifically configured to:

When the comparison result is that the priority of the first BRAS is the same as the priority of the second BRAS, comparing the IP address of the first BRAS with the IP address of the second BRAS;

When the comparison result satisfies the condition of allowing the first BRAS to apply for the first sub-address segment, return an address request response to the first BRAS.

Optionally, also include:

The removal module 704 is configured to remove the first sub-address segment from available address segments of the second BRAS when the second BRAS allows the first BRAS to apply for the first sub-address segment.

The second BRAS in this embodiment may be used to implement the technical solutions of the foregoing method embodiments, and its implementation principles and technical effects are similar, and details are not repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed devices and methods may be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units or modules is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or modules can be Incorporation may either be integrated into another system, or some features may be omitted, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or modules may be in electrical, mechanical or other forms.

The modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in one place, or may also be distributed to multiple network units. Part or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

Those of ordinary skill in the art can understand that all or part of the steps for implementing the above method embodiments can be completed by program instructions and related hardware. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it executes the steps including the above-mentioned method embodiments; and the aforementioned storage medium includes: ROM, RAM, magnetic disk or optical disk and other various media that can store program codes.

Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present invention, rather than limiting them; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: It is still possible to modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements for some or all of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the technical solutions of the various embodiments of the present invention. scope.

Claims (18)

1. A method for address segment allocation, characterized in that, comprising: The first broadband access server BRAS determines the first sub-address segment that needs to be applied for from the available address segment of the machine; The first BRAS sends a first address request message to the second BRAS, the first address request message carries the first sub-address segment, and the address segment of the first BRAS and the address segment of the second BRAS exist intersection; The first BRAS receives an address request response returned by the second BRAS, where the address request response is used to indicate that the second BRAS allows the first BRAS to apply for the first sub-address segment; After determining that the second BRAS allows the first BRAS to apply for the first sub-address segment, the first BRAS allocates an address for the user equipment from the first sub-address segment. 2. The method according to claim 1, characterized in that the method further comprises: The first BRAS receives a second address request message sent by the second BRAS, where the second address request message carries a second sub-address segment to be applied for; After the first BRAS determines that it is necessary to apply for the first sub-address segment, when the first sub-address segment is consistent with the second sub-address segment, the first BRAS compares the priority and the priority of said second BRAS; When the priority of the first BRAS is higher than the priority of the second BRAS, the first BRAS refuses the second BRAS to apply for the second sub-address segment. 3. The method according to claim 2, wherein the method further comprises: When the priority of the first BRAS is equal to the priority of the second BRAS, comparing the IP address of the first BRAS with the IP address of the second BRAS; When the comparison result does not satisfy the condition for allowing the second BRAS to apply for the second sub-address segment, the first BRAS refuses the second BRAS to apply for the second sub-address segment. 4. The method according to claim 2, characterized in that the method further comprises: After the first BRAS determines that it is necessary to apply for the first sub-address segment, when the first sub-address segment does not overlap with the second sub-address segment and the second sub-address segment belongs to the first BRAS When there is an available address segment, the first BRAS allows the second BRAS to apply for the second sub-address segment, and removes the second sub-address segment from the available address segment of the first BRAS. 5. A method for allocating address segments, comprising: The second broadband access server BRAS receives the first address request message sent by the first BRAS, the first address request message carries the first sub-address segment that the first BRAS needs to apply for, the address segment of the first BRAS and There is an intersection between the address segments of the second BRAS; The second BRAS determines whether the first sub-address segment is an available address segment in the address segment of the second BRAS; After determining that the first sub-address segment is an available sub-address segment in the address segment of the second BRAS, return an address request response to the first BRAS, where the address request response is used to indicate the second BRAS Allowing the first BRAS to apply for the first sub-address segment. 6. The method according to claim 5, wherein after determining that the first sub-address segment is an available sub-address segment in the address segment of the second BRAS, return an address request to the first BRAS Specifically, the response includes: The second BRAS determines whether the first sub-address segment is consistent with the second sub-address segment that the second BRAS needs to apply for; If not, the second BRAS returns an address request response to the first BRAS. 7. The method according to claim 5, wherein after determining that the first sub-address segment is an available sub-address segment in the address segment of the second BRAS, return an address request to the first BRAS Specifically, the response includes: The second BRAS determines whether the first sub-address segment is consistent with the second sub-address segment that the second BRAS needs to apply for; If so, the second BRAS compares the priority of the first BRAS with the priority of the second BRAS; When the priority of the first BRAS is higher than the priority of the second BRAS, the second BRAS returns an address request response to the first BRAS. 8. The method according to claim 7, further comprising: When the comparison result is that the priority of the first BRAS is the same as that of the second BRAS, the second BRAS compares the IP address of the first BRAS with the IP address of the second BRAS; When the comparison result satisfies the condition of allowing the first BRAS to apply for the first sub-address segment, the second BRAS returns an address request response to the first BRAS. 9. The method according to any one of claims 5 to 8, wherein the method further comprises: When the second BRAS allows the first BRAS to apply for the first sub-address segment, the second BRAS removes the first sub-address segment from available address segments of the second BRAS. 10. A first broadband access server BRAS, characterized in that, comprising: An application module, configured to determine the first sub-address segment to be applied for from the available address segments of the machine; A sending module, configured to send a first address request message to a second BRAS, where the first address request message carries the first sub-address segment, and the address segment of the first BRAS and the address segment of the second BRAS exist intersection; A first receiving module, configured to receive an address request response returned by the second BRAS, where the address request response is used to indicate that the second BRAS allows the first BRAS to apply for the first sub-address segment; An allocating module, configured to allocate an address for the user equipment from the first sub-address segment after determining that the second BRAS allows the first BRAS to apply for the first sub-address segment. 11. The first BRAS according to claim 10, further comprising: A second receiving module, configured to receive a second address request message sent by the second BRAS, where the second address request message carries a second sub-address segment to be applied for; The first comparison module is configured to compare the first BRAS when the first sub-address segment is consistent with the second sub-address segment after the first BRAS determines that it needs to apply for the first sub-address segment and the priority of the second BRAS; The first responding module is configured to reject the second BRAS to apply for the second sub-address segment when the priority of the first BRAS is higher than the priority of the second BRAS. 12. The first BRAS according to claim 11, further comprising: A second comparison module, configured to compare the IP address of the first BRAS with the IP address of the second BRAS when the priority of the first BRAS is equal to the priority of the second BRAS; The second response module is configured to reject the second BRAS from applying for the second sub-address segment when the comparison result does not satisfy the condition for allowing the second BRAS to apply for the second sub-address segment. 13. The first BRAS according to claim 11, further comprising: A removal module, configured to, after the first BRAS determines that it is necessary to apply for the first sub-address segment, when the first sub-address segment does not overlap with the second sub-address segment and the second sub-address segment belongs to When the available address segment of the first BRAS is available, the second BRAS is allowed to apply for the second sub-address segment, and the second sub-address segment is removed from the available address segment of the first BRAS. 14. A second broadband access server BRAS, characterized in that it comprises: A receiving module, configured to receive a first address request message sent by a first BRAS, where the first address request message carries a first sub-address segment that the first BRAS needs to apply for, the address segment of the first BRAS and the There is an intersection between the address segments of the second BRAS; A determining module, configured to determine whether the first sub-address segment is an available address segment in the address segment of the second BRAS; A response module, configured to return an address request response to the first BRAS after determining that the first sub-address segment is an available sub-address segment in the address segment of the second BRAS, where the address request response is used to indicate The second BRAS allows the first BRAS to apply for the first sub-address segment. 15. The second BRAS according to claim 14, wherein the response module is specifically used for: Determine whether the first sub-address segment is consistent with the second sub-address segment that the second BRAS needs to apply for; If not, return an address request response to the first BRAS. 16. The second BRAS according to claim 14, wherein the response module is specifically used for: Determine whether the first sub-address segment is consistent with the second sub-address segment that the second BRAS needs to apply for; If so, comparing the priority of the first BRAS with the priority of the second BRAS; When the priority of the first BRAS is higher than the priority of the second BRAS, return an address request response to the first BRAS. 17. The second BRAS according to claim 16, wherein the response module is further specifically configured to: When the comparison result is that the priority of the first BRAS is the same as the priority of the second BRAS, comparing the IP address of the first BRAS with the IP address of the second BRAS; When the comparison result satisfies the condition of allowing the first BRAS to apply for the first sub-address segment, return an address request response to the first BRAS. 18. The second BRAS according to any one of claims 13 to 17, further comprising: A removing module, configured to remove the first sub-address segment from available address segments of the second BRAS when the second BRAS allows the first BRAS to apply for the first sub-address segment.