CN110636146B - User address allocation method and device - Google Patents
User address allocation method and device Download PDFInfo
- Publication number
- CN110636146B CN110636146B CN201810661106.4A CN201810661106A CN110636146B CN 110636146 B CN110636146 B CN 110636146B CN 201810661106 A CN201810661106 A CN 201810661106A CN 110636146 B CN110636146 B CN 110636146B
- Authority
- CN
- China
- Prior art keywords
- field
- message
- address
- relay device
- user
- 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
- H04L61/5007—Internet protocol [IP] addresses
- H04L61/5014—Internet protocol [IP] addresses using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The embodiment of the invention provides a user address allocation method and equipment, wherein the method comprises the following steps: receiving a first message sent by a user gateway; adding a first field, a second field and a third field in the first message to obtain a second message; sending the second message to a server; receiving a third message which is sent by the server and used for responding to the second message, and forwarding the third message to the user gateway; wherein the first field indicates an address of the user gateway, the second field indicates whether the relay device and the user gateway are separated, and the third field indicates an address of the relay device. In this way, when the user gateway and the relay device are separated in the network and the addresses of the user gateway and the relay device are different, the server can send the response message and the IP address to the corresponding target address.
Description
Technical Field
The embodiment of the invention relates to the technical field of communication, in particular to a user address allocation method and device.
Background
Referring to fig. 1, in order to assign an IP (Internet Protocol) address to a user, a DHCP (Dynamic Host Configuration Protocol) is required to be used in a conventional BRAS (Broadband Remote Access Server) system. In a conventional BRAS system, a subscriber gateway and a DHCP relay device are the same device, i.e., a BRAS device. In this way, the DHCP client sends a DHCP discover (Dynamic Host Configuration Protocol Discovery) message through broadcasting, and after receiving the DHCP discover message, the BRAS device adds an address of the BRAS device in a giaddr (gateway IP address) field in the DHCP discover message, and sends a DHCP discover unicast message to which the address of the BRAS device is added to the DHCP server. And the DHCP server determines the address of the BRAS equipment according to the giaddr field and sends a DHCP offer message (provided by a Dynamic Host Configuration Protocol) to the BRAS equipment.
Referring to fig. 2, in the virtual BRAS system, in order to implement the diversion separation, the subscriber gateway and the DHCP relay device are different devices, i.e., BRAS-UP (BRAS User Plane) and BRAS-CP (BRAS Control Plane), where BRAS-UP corresponds to the subscriber gateway and BRAS-CP corresponds to the DHCP relay device. If the IP address is allocated to the user by using the DHCP according to the existing method, the BRAS-CP adds the address of the user gateway in the giaddr field in the DHCP Discovery message, and the address of the user gateway indicates the address of the BRAS-UP. After receiving the DHCP Discovery message added with the address of the BRAS-UP, the DHCP server sends the DHCP offer message to the BRAS-UP according to the giaddr field, so that the BRAS-CP cannot receive the DHCP offer message, DHCP processing faults are caused, and an IP address cannot be allocated to a user.
Disclosure of Invention
The embodiment of the invention provides a user address allocation method and device, which solve the problem that the IP address cannot be allocated to a user by using DHCP in a virtual BRAS system.
According to a first aspect of the embodiments of the present invention, there is provided a user address allocation method, applied to a relay device, the method including: receiving a first message sent by a user gateway; adding a first field, a second field and a third field in the first message to obtain a second message; sending the second message to a server; receiving a third message which is sent by the server and used for responding to the second message, and forwarding the third message to the user gateway; wherein the first field indicates an address of the user gateway, the second field indicates whether the relay device and the user gateway are separated, and the third field indicates an address of the relay device.
Optionally, the first message is a first DHCP Discovery message, the second message is a second DHCP Discovery message including the first field, the second field, and the third message is a DHCP offer message; adding a first field, a second field and a third field in the first message, including: adding the first field in a giaddr field of the first message, wherein the first field is the address of the user gateway; extending the second field in a Flags (identification) field of the first packet, wherein the field is one bit; when the bit is 1, indicating that the relay device is separated from the user gateway; when the bit is 0, indicating that the relay device and the user gateway are not separated; and expanding the third field in an option field of the first message, wherein the third field is the address of the relay equipment.
According to a second aspect of the embodiments of the present invention, there is provided a user address allocation method, applied to a server, the method including: receiving a second message sent by a relay device, wherein the second message is obtained by adding a first field, a second field and a third field to a first message, the first field represents an address of a user gateway, the second field represents whether the relay device and the user gateway are separated, and the third field represents the address of the relay device; and when the relay equipment is separated from the user gateway, sending an IP address to the user gateway according to the first field, and sending a third message for responding to the second message to the relay equipment according to the third field.
Optionally, the first message is a first DHCP Discovery message, the second message is a second DHCP Discovery message including the first field, the second field, and the third message is a DHCP offer message;
the first field is added in a giaddr field of the first message, and the first field is the address of the user gateway; the second field is a bit extended from a Flags field of the first message; when the bit is 1, indicating that the relay device is separated from the user gateway; when the bit is 0, indicating that the relay device and the user gateway are not separated; the third field is an extended field in an option field of the first packet, and the third field is an address of the relay device.
According to a third aspect of the embodiments of the present invention, there is provided a relay apparatus, including: a first transceiver and a first processor;
the first transceiver is used for receiving a first message sent by a user gateway; the first processor is configured to add a first field, a second field, and a third field to the first packet to obtain a second packet; the first transceiver is further configured to send the second packet to a server; the first transceiver is further configured to receive a third packet sent by the server and used for responding to the second packet, and forward the third packet to the user gateway; wherein the first field indicates an address of the user gateway, the second field indicates whether the relay device and the user gateway are separated, and the third field indicates an address of the relay device.
Optionally, the first message is a first DHCP Discovery message, the second message is a second DHCP Discovery message including the first field, the second field, and the third message is a DHCP offer message; the first processor is further configured to add the first field to a giaddr field of the first packet, where the first field is an address of the user gateway; the first processor is further configured to extend the second field in a Flags field of the first packet, where the field is a bit; when the bit is 1, indicating that the relay device is separated from the user gateway; when the bit is 0, indicating that the relay device and the user gateway are not separated; the first processor is further configured to extend the third field in an option field of the first packet, where the third field is an address of the relay device.
According to a fourth aspect of the embodiments of the present invention, there is provided a server, including: a second transceiver and a second processor;
the second transceiver is configured to receive a second message sent by a relay device, where the second message is obtained by adding a first field, a second field, and a third field to a first message, where the first field indicates an address of a user gateway, the second field indicates whether the relay device and the user gateway are separated, and the third field indicates the address of the relay device; and the second processor is configured to send an IP address to the user gateway according to the first field and send a third packet for responding to the second packet to the relay device according to the third field when the relay device and the user gateway are separated.
Optionally, the first message is a first DHCP Discovery message, the second message is a second DHCP Discovery message including the first field, the second field, and the third message is a DHCP offer message; the first field is added in a giaddr field of the first message, and the first field is the address of the user gateway; the second field is a bit extended from a Flags field of the first message; when the bit is 1, indicating that the relay device is separated from the user gateway; when the bit is 0, indicating that the relay device and the user gateway are not separated; the third field is an extended field in an option field of the first packet, and the third field is an address of the relay device.
According to a fifth aspect provided by an embodiment of the present invention, there is provided a network side device, including: a processor, a memory and a program of a user address allocation method stored on the memory and executable on the processor, which program, when executed by the processor, performs the steps of the user address allocation method according to the first aspect or the steps of the user address allocation method according to the second aspect.
According to a sixth aspect of embodiments of the present invention, there is provided a computer-readable storage medium having stored thereon a program of a user address allocation method, the program of the user address allocation method, when executed by a processor, implementing the steps of the user address allocation method according to the first aspect or the steps of the user address allocation method according to the second aspect.
In the embodiment of the invention, after receiving a first message sent by a user gateway, the relay equipment adds a first field, a second field and a third field in the first message to obtain a second message, and sends the second message to the server. The server can judge the relay equipment and the user gateway according to the first field, the second field and the third field, and sends the IP address and the response message to the corresponding target address. In this way, when the user gateway and the relay device are separated in the network and the addresses of the user gateway and the relay device are different, the server can send the response message and the IP address to the corresponding target address.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the embodiments of the present invention will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained based on these drawings without creative efforts.
Fig. 1 is a schematic flow chart of a subscriber address allocation method in a conventional BRAS system;
fig. 2 is a schematic flow chart of a subscriber address allocation method in a conventional virtual BRAS system;
fig. 3 is a schematic flow chart of a user address allocation method according to an embodiment of the present invention:
fig. 4 is a second flowchart illustrating a user address allocation method according to an embodiment of the present invention;
fig. 5 is a third schematic flowchart of a user address allocation method according to an embodiment of the present invention;
fig. 6 shows a format of a conventional DHCP message;
FIG. 7 is a diagram illustrating the format of the Flags field in the conventional DHCP message;
fig. 8 is a schematic structural diagram of a relay device according to an embodiment of the present invention;
fig. 9 is a schematic structural diagram of a server according to an embodiment of the present invention;
fig. 10 is a schematic structural diagram of a network-side device according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Referring to fig. 3, an embodiment of the present invention provides a user address allocation method, where an execution main body of the method is a relay device, and the method includes the following specific steps:
step 301: receiving a first message sent by a user gateway;
in the embodiment of the invention, the user gateway forwards the first message sent by the client to the relay equipment, wherein the first message represents that the user of the client requests to allocate the IP address. Based on different network protocols, the first packet has different types, for example: when the DHCP is used, the first message is a DHCP Discovery message, and the embodiment of the present invention does not specifically limit the type of the first message.
Step 302: adding a first field, a second field and a third field in the first message to obtain a second message;
in the embodiment of the present invention, a first field indicates an address of a user gateway, a second field indicates whether a relay device and the user gateway are separated, and a third field indicates the address of the relay device.
The first field, the second field and the third field may be added at the same position in the first message, or the first field, the second field and the third field may be added at different positions in the first message; the first field, the second field, and the third field may be a segment of character, and the first field, the second field, and the third field may also be one or more bits.
Step 303: sending the second message to a server;
step 304: receiving a third message which is sent by the server and used for responding to the second message, and forwarding the third message to the user gateway;
in the embodiment of the present invention, the third packet indicates that the server can provide an IP address for the user. The third packet is of a different type based on a different network protocol, for example: when the DHCP is used, the third message is a DHCP offer message, and the embodiment of the present invention does not specifically limit the type of the third message.
In the embodiment of the invention, when the user gateway and the relay equipment in the network are separated, so that the addresses of the user gateway and the relay equipment are different, the server can send the response message and the IP address to the corresponding target address, thereby avoiding the network protocol processing fault caused by the error of the target address and being incapable of distributing the IP address for the user.
Referring to fig. 4, an embodiment of the present invention provides a method for allocating a user address, where an execution subject of the method is a server, and the method includes the following specific steps:
step 401: receiving a second message sent by the relay equipment;
in the embodiment of the invention, the second message is obtained by adding a first field, a second field and a third field to the first message. Wherein, the first field represents the address of the user gateway, the second field represents whether the relay device and the user gateway are separated, and the third field represents the address of the relay device. The first message represents that a user of the client requests to allocate an IP address, and the first message has different types based on different network protocols, for example: when the DHCP is used, the first message is a DHCP Discovery message, and the embodiment of the present invention does not specifically limit the type of the first message.
Step 402: when the relay equipment is separated from the user gateway, the IP address is sent to the user gateway according to the first field, and a third message used for responding to the second message is sent to the relay equipment according to the third field;
in the embodiment of the invention, when the second field indicates that the relay equipment is separated from the user gateway, the server sends the IP address to the user gateway according to the indication of the first field and the third field, and sends the third message for responding to the second message to the relay equipment. The third message indicates that the server can provide the IP address for the user, and the third message has different types based on different network protocols, for example: when the DHCP is used, the third message is a DHCP offer message, and the embodiment of the present invention does not specifically limit the type of the third message.
It should be noted that, when the second field indicates that the relay device and the user gateway are not separated, that is, the relay device and the user gateway are the same device, at this time, the server sends the IP address and the third packet to the user gateway according to the indication of the first field by using the existing method.
In the embodiment of the invention, when the user gateway and the relay equipment in the network are separated, so that the addresses of the user gateway and the relay equipment are different, the server can send the response message and the IP address to the corresponding target address, thereby avoiding the network protocol processing fault caused by the error of the target address and being incapable of distributing the IP address for the user.
Referring to fig. 5, an embodiment of the present invention provides a method for allocating a user address, where a network protocol used in the method is DHCP, and the method includes the following specific steps:
step 501: the client sends a first DHCP Discovery message to the user gateway;
step 502: the user gateway sends the first DHCP Discovery message to the relay equipment;
in the embodiment of the present invention, for the case where the subscriber gateway and the relay device are separated, a tunnel may be established between the subscriber gateway and the relay device by using the existing method, and the subscriber gateway sends the DHCP Discovery message to the relay device through the tunnel.
It should be noted that, for the case that the subscriber gateway and the relay device are not separated, since the subscriber gateway and the relay device are the same device, when the client sends the first DHCP Discovery message, it can be understood that the subscriber gateway and the relay device receive the first DHCP Discovery message at the same time.
Step 503: the relay equipment adds a first field, a second field and a third field in the first DHCP Discovery message to obtain a second DHCP Discovery message;
referring to fig. 6, a format of an existing DHCP message is shown, where a relay device adds a first field, a second field, and a third field to corresponding fields in a first DHCP Discovery message;
specifically, a first field is added in a giaddr field, and the first field is an address of a user gateway;
referring to fig. 7, a second field, which is one bit 72, is extended in the Flags field 71;
the existing Flags field 71 is a field with 15 bits, and a bit 72 is extended on the basis of the existing Flags field, where the bit 72 may be referred to as a "S (separate) bit, and when the bit 72 is 1, it indicates that the relay device and the user gateway are separated; when the bit 72 is 0, it indicates that the relay device and the user gateway are not separated. The server determines the IP address and the target address of the DHCP offer message according to the value of the bit 72;
a third field is extended in the options field, where the third field is an address of the relay device, and optionally, the third field is an option 254 readdr (relay IP address).
Step 504: the relay equipment sends the second DHCP Discovery message to the server;
step 505: when the relay equipment is separated from the user gateway, an IP address is sent to the user gateway according to the first field, and a DHCP offer message is sent to the relay equipment according to the third field;
in the embodiment of the invention, when the relay equipment is separated from the user gateway, the server sends the IP address allocated to the user gateway according to the indication of the first field in the giaddr field; and the server sends the DHCP offer message to the relay equipment according to the indication of a third field in the options field.
It should be noted that, when the relay device and the user gateway are not separated, that is, the relay device and the user gateway are the same device, the server uses the existing method to send the IP address and the DHCP offer message to the same destination address according to the indication of the first field in the giaddr, so that the user gateway can receive the IP address, and the relay device can receive the DHCP offer message.
Step 506: the relay equipment forwards the DHCP offer message to a user gateway;
in the embodiment of the present invention, for the case where the subscriber gateway and the relay device are separated, a tunnel may be established between the subscriber gateway and the relay device by using an existing method, and the subscriber gateway sends the DHCP offer message to the relay device through the tunnel.
Step 507: and the user gateway sends the DHCP offer message to the client.
In the embodiment of the present invention, the user gateway sends the DHCP offer message to the client, and the client can continue to execute the subsequent network access process according to the DHCP offer message, which is not described again.
In the embodiment of the invention, a first field for expressing the address of a user gateway is added in a giaddr field of a DHCP message; expanding a second field which indicates whether the relay equipment and the user gateway are separated or not in a Flags field of the DHCP message; and extending a third field for representing the address of the relay equipment in the options automation of the DHCP message. When the user gateway and the relay device are separated in the network, the server can correctly send the DHCP offer message to the relay device and send the IP address to the user gateway, thereby avoiding the network protocol processing fault and enabling the user to be allocated with the IP address.
Referring to fig. 8, an embodiment of the present invention provides a relay apparatus 800, including: a first transceiver 801 and a first processor 802;
the first transceiver 801 is configured to receive a first message sent by a user gateway;
the first processor 802 is configured to add a first field, a second field, and a third field in the first packet to obtain a second packet;
the first transceiver 801 is further configured to send the second packet to a server;
the first transceiver 801 is further configured to receive a third packet sent by the server and used for responding to the second packet, and forward the third packet to the user gateway;
wherein the first field indicates an address of the user gateway, the second field indicates whether the relay device and the user gateway are separated, and the third field indicates an address of the relay device.
Referring to fig. 9, an embodiment of the present invention further provides a server 900, including: a second transceiver 901 and a second processor 902;
the second transceiver 901 is configured to receive a second message sent by a relay device, where the second message is obtained by adding a first field, a second field, and a third field to a first message, where the first field indicates an address of a user gateway, the second field indicates whether the relay device and the user gateway are separated, and the third field indicates an address of the relay device;
the second processor 902 is configured to send, when the relay device is separated from the user gateway, an IP address to the user gateway according to the first field, and send, to the relay device, a third packet configured to respond to the second packet according to the third field.
In the embodiment of the invention, after receiving a first message sent by a user gateway, the relay equipment adds a first field, a second field and a third field in the first message to obtain a second message, and sends the second message to the server. The server can judge the relay equipment and the user gateway according to the first field, the second field and the third field, and sends the IP address and the response message to the corresponding target address. Therefore, when the user gateway and the relay equipment in the network are separated and the addresses of the user gateway and the relay equipment are different, the server can send the response message and the IP address to the corresponding target address, so that the problem that the network protocol processing fails and the IP address cannot be allocated to the user due to the wrong target address is avoided.
Referring to fig. 10, an embodiment of the present invention provides a network-side device 1000, including: a processor 1001, a transceiver 1002, a memory 1003, a user interface 1004, and a bus interface.
Among other things, the processor 1001 may be responsible for managing the bus architecture and general processing. The memory 1003 may store data used by the processor 1001 in performing operations.
In this embodiment of the present invention, the network side device 1000 may further include: a computer program stored on the memory 1003 and executable on the processor 1001, which when executed by the processor 1001, performs the steps of the method provided by an embodiment of the present invention.
In fig. 10, the bus architecture may include any number of interconnected buses and bridges, with one or more processors represented by processor 1001 and various circuits of memory represented by memory 1003 being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further in connection with embodiments of the present invention. The bus interface provides an interface. The transceiver 1002 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium.
The embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a processor, the computer program implements each process of the foregoing network access method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
While the present invention has been described with reference to the embodiments shown in the drawings, the present invention is not limited to the embodiments, which are illustrative and not restrictive, and it will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the invention as defined in the appended claims.
Claims (10)
1. A user address allocation method is applied to relay equipment, and is characterized in that the method comprises the following steps:
receiving a first message sent by a user gateway;
adding a first field, a second field and a third field in the first message to obtain a second message;
sending the second message to a server;
receiving a third message which is sent by the server and used for responding to the second message, and forwarding the third message to the user gateway;
wherein the first field indicates an address of the user gateway, the second field indicates whether the relay device and the user gateway are separated, and the third field indicates an address of the relay device.
2. The method of claim 1, wherein the first message is a first dynamic host configuration protocol Discovery (DHCP) Discovery message, wherein the second message is a second DHCP Discovery message including the first field, the second field, and the third field, and wherein the third message provides a DHCP offer message for a dynamic host configuration protocol;
adding a first field, a second field and a third field in the first message, including:
adding the first field in a gateway IP address giaddr field of the first message, wherein the first field is the address of the user gateway;
expanding the second field in an identification Flags field of the first message, wherein the field is a bit;
when the bit is 1, indicating that the relay device is separated from the user gateway;
when the bit is 0, indicating that the relay device and the user gateway are not separated;
and expanding the third field in an option field of the first message, wherein the third field is the address of the relay equipment.
3. A user address allocation method is applied to a server, and is characterized in that the method comprises the following steps:
receiving a second message sent by a relay device, wherein the second message is obtained by adding a first field, a second field and a third field to a first message, the first field represents an address of a user gateway, the second field represents whether the relay device and the user gateway are separated, and the third field represents the address of the relay device;
and when the relay equipment is separated from the user gateway, sending an IP address to the user gateway according to the first field, and sending a third message for responding to the second message to the relay equipment according to the third field.
4. The method of claim 3, wherein the first message is a first DHCP Discovery message, the second message is a second DHCP Discovery message comprising the first field, the second field, and the third message is a DHCP offer message;
the first field is added in a giaddr field of the first message, and the first field is the address of the user gateway;
the second field is a bit extended from a Flags field of the first message;
when the bit is 1, indicating that the relay device is separated from the user gateway;
when the bit is 0, indicating that the relay device and the user gateway are not separated;
the third field is an extended field in an option field of the first packet, and the third field is an address of the relay device.
5. A relay device, comprising: a first transceiver and a first processor, wherein,
the first transceiver is used for receiving a first message sent by a user gateway;
the first processor is configured to add a first field, a second field, and a third field to the first packet to obtain a second packet;
the first transceiver is further configured to send the second packet to a server;
the first transceiver is further configured to receive a third packet sent by the server and used for responding to the second packet, and forward the third packet to the user gateway;
wherein the first field indicates an address of the user gateway, the second field indicates whether the relay device and the user gateway are separated, and the third field indicates an address of the relay device.
6. The relay device according to claim 5, wherein the first packet is a first DHCP Discovery packet, the second packet is a second DHCP Discovery packet including the first field, the second field, and the third packet is a DHCP offer packet;
the first processor is further configured to add the first field to a giaddr field of the first packet, where the first field is an address of the user gateway;
the first processor is further configured to extend the second field in a Flags field of the first packet, where the field is a bit;
when the bit is 1, indicating that the relay device is separated from the user gateway;
when the bit is 0, indicating that the relay device and the user gateway are not separated;
the first processor is further configured to extend the third field in an option field of the first packet, where the third field is an address of the relay device.
7. A server, comprising: a second transceiver and a second processor, wherein,
the second transceiver is configured to receive a second message sent by a relay device, where the second message is obtained by adding a first field, a second field, and a third field to a first message, where the first field indicates an address of a user gateway, the second field indicates whether the relay device and the user gateway are separated, and the third field indicates the address of the relay device;
and the second processor is configured to send an IP address to the user gateway according to the first field and send a third packet for responding to the second packet to the relay device according to the third field when the relay device and the user gateway are separated.
8. The server according to claim 7, wherein the first packet is a first DHCP Discovery packet, the second packet is a second DHCP Discovery packet including the first field, the second field, and the third packet is a DHCP offer packet;
the first field is added in a giaddr field of the first message, and the first field is the address of the user gateway;
the second field is a bit extended from a Flags field of the first message;
when the bit is 1, indicating that the relay device is separated from the user gateway;
when the bit is 0, indicating that the relay device and the user gateway are not separated;
the third field is an extended field in an option field of the first packet, and the third field is an address of the relay device.
9. A network-side device, comprising: processor, memory and program of a user address assignment method stored on the memory and executable on the processor, which program of the user address assignment method, when executed by the processor, carries out the steps of the user address assignment method as claimed in one of claims 1 or 2 or the steps of the user address assignment method as claimed in one of claims 3 or 4.
10. A computer-readable storage medium, characterized in that a program of a user address allocation method is stored on the computer-readable storage medium, which program, when being executed by a processor, carries out the steps of the user address allocation method according to one of claims 1 or 2, or the steps of the user address allocation method according to one of claims 3 or 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810661106.4A CN110636146B (en) | 2018-06-25 | 2018-06-25 | User address allocation method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810661106.4A CN110636146B (en) | 2018-06-25 | 2018-06-25 | User address allocation method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110636146A CN110636146A (en) | 2019-12-31 |
| CN110636146B true CN110636146B (en) | 2022-05-06 |
Family
ID=68967759
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810661106.4A Active CN110636146B (en) | 2018-06-25 | 2018-06-25 | User address allocation method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110636146B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113542905B (en) * | 2020-04-22 | 2024-05-03 | 中国移动通信集团有限公司 | Address allocation method, gateway, set top box, equipment and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107547597A (en) * | 2016-06-27 | 2018-01-05 | 中兴通讯股份有限公司 | Method for processing business and device |
| CN107659516A (en) * | 2017-10-25 | 2018-02-02 | 新华三技术有限公司 | A kind of Broadband Remote Access Server BRAS function control method and device |
| CN107786613A (en) * | 2016-08-30 | 2018-03-09 | 新华三技术有限公司 | Broadband Remote Access Server BRAS forwards implementation method and device |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7624181B2 (en) * | 2006-02-24 | 2009-11-24 | Cisco Technology, Inc. | Techniques for authenticating a subscriber for an access network using DHCP |
-
2018
- 2018-06-25 CN CN201810661106.4A patent/CN110636146B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107547597A (en) * | 2016-06-27 | 2018-01-05 | 中兴通讯股份有限公司 | Method for processing business and device |
| CN107786613A (en) * | 2016-08-30 | 2018-03-09 | 新华三技术有限公司 | Broadband Remote Access Server BRAS forwards implementation method and device |
| CN107659516A (en) * | 2017-10-25 | 2018-02-02 | 新华三技术有限公司 | A kind of Broadband Remote Access Server BRAS function control method and device |
Non-Patent Citations (1)
| Title |
|---|
| 《基于转发和控制分离的vBRAS应用研究》;祁钰;《电信技术》;20180228(第2期);第35-37页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110636146A (en) | 2019-12-31 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108307002B (en) | DHCP message processing method and device | |
| EP3264731B1 (en) | Method, relay agent, and system for acquiring internet protocol address in network | |
| CN108777722B (en) | Multi-system networking communication method and device, mobile terminal and storage medium | |
| US11405314B2 (en) | Packet processing method and apparatus | |
| US20120324063A1 (en) | Method, network device, and system for automatically configuring network device in ipv6 network | |
| CN107547665B (en) | Method, equipment and system for allocating DHCP (dynamic host configuration protocol) address | |
| JP7207827B2 (en) | Resource Acquisition Method and Device | |
| CN112654049B (en) | Method, system, node and medium for configuring a wireless communication coverage extension system | |
| US10432579B2 (en) | Internet protocol address allocation method and router | |
| CN107809386B (en) | IP address translation method, routing device and communication system | |
| CN106713130B (en) | A kind of routing table update method, EVPN control equipment and EVPN system | |
| CN112449752A (en) | IPv6 address configuration method and routing equipment | |
| CN111031129B (en) | Access request processing method, processing device, electronic equipment and storage medium | |
| US11929851B2 (en) | Gateway selection method, device, and system | |
| CN104426816B (en) | A kind of virtual machine communication method and device | |
| CN110636146B (en) | User address allocation method and device | |
| CN112272244B (en) | Router WAN end IPv6 internet mode configuration method and device | |
| EP3503484A1 (en) | Message transmission method, device and network system | |
| CN109842692B (en) | VxLAN switch, system and method for obtaining host information in physical network | |
| CN103634844A (en) | Method and system for realizing distributed multi-port DHCP relay | |
| CN111654390B (en) | Data transmission method, device, terminal equipment and storage medium | |
| CN108076025B (en) | Registration method and device of network equipment | |
| WO2023125807A1 (en) | Identifier allocation method and apparatus, and communication device and readable storage medium | |
| WO2022057477A1 (en) | Network configuration method, terminal, system, and storage medium | |
| JP2012010169A (en) | Radio communication network connection system, and radio communication network connection method |
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 |