CN118055096A

CN118055096A - IP address configuration method and related equipment

Info

Publication number: CN118055096A
Application number: CN202211435268.9A
Authority: CN
Inventors: 杨学伟
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2022-11-16
Filing date: 2022-11-16
Publication date: 2024-05-17
Also published as: WO2024103738A1

Abstract

The application discloses a configuration method of an IP address and related equipment, wherein in a network comprising an ACS, a gateway and CPE, the management of the ACS on the CPE can be realized without configuring additional equipment, the implementation mode is simplified, and the operation and maintenance cost is reduced. Specifically, a bridge WAN link is established between the gateway and the CPE, and the CPE can obtain its own public network IP address from the ACS through the bridge WAN link. That is, the CPE no longer has only the private network IP address assigned by the gateway, and the CPE and gateway are comparable in public network for ACS. In addition, a routing WAN link can be established between the gateway and the CPE, and the CPE can adopt own public network IP address and communicate with the ACS through the routing WAN link.

Description

IP address configuration method and related equipment

Technical Field

The present application relates to the field of communications, and in particular, to a method for configuring an IP address and related devices.

Background

Network address translation (Network Address Translation, NAT) is a technique for translating private internet protocol (Internet Protocol, IP) addresses into public network IP addresses, where when an IP message communicated by a private network host and a public network host passes through a NAT device, the NAT device translates a source IP address or a destination IP address in the IP message between the private network IP address and the public network IP address of the NAT device.

In order to traverse NAT devices, to implement management of customer premise equipment (Customer Premises Equipment, CPE) by an auto-configuration server (Auto Configuration Server, ACS), the international standard organization DSL Forum proposes a technical solution in the WT-111 protocol. In this scheme, the CPE is required to install a NAT session traversal application (Session Traversal Utilities for NAT, STUN) client, configuring a STUN server for the ACS. The STUN client and STUN server are used to probe the public network IP address and port number of the NAT device. And then, the STUN server sends the public network IP address and the port number to the ACS, and when the ACS needs to actively connect with the CPE, the ACS sends a connection request to the CPE through the public network IP address and the port number. However, this solution requires additional STUN servers to implement management of the CPE by the ACS, which is complex to implement and increases the operation and maintenance costs.

Disclosure of Invention

The embodiment of the application provides a configuration method of an IP address and related equipment, wherein in a network comprising an ACS, a gateway and CPE, the ACS can manage the CPE without configuring additional equipment, the implementation mode is simplified, and the operation and maintenance cost is reduced.

In a first aspect, an embodiment of the present application provides a method for configuring an IP address, where the method includes the following steps. First, the gateway receives a request message sent by the CPE over a bridged wide area network (Wide Area Network, WAN) link and sends the request message to the ACS. The request message is used for requesting the ACS to allocate a public network IP address to the CPE. Next, the gateway receives a configuration message sent by the ACS, wherein the configuration message includes the public network IP address of the CPE. Further, the gateway sends the configuration message to the CPE over the bridged WAN link.

In this embodiment, the CPE may obtain its own public network IP address from the ACS across the gateway by bridging the WAN link. That is, the CPE no longer has only the private network IP address assigned by the gateway, and the CPE and gateway are comparable in public network for ACS. The CPE may then communicate with the ACS using its own public IP address. By the method, in the network comprising the ACS, the gateway and the CPE, the ACS can manage the CPE without configuring additional equipment, so that the implementation mode is simplified, and the operation and maintenance cost is reduced.

In some possible implementations, bridging the WAN link establishes between the first port of the gateway and the second port of the CPE. And, the bridged WAN link is bound to a designated virtual local area network (Virtual Local Area Network, VLAN). The VLAN has a corresponding VLAN label, and the message interacted between the gateway and the CPE through the bridging WAN link carries the VLAN label so that the gateway can identify the message transmitted through the bridging WAN link and output the message from the appointed port.

In some possible embodiments, a routing WAN link is further established between the second port of the CPE and the first port of the gateway, the routing WAN link being configured to transmit interaction information that the CPE uses the public network IP address to communicate with the ACS. That is, the CPE may employ its own public IP address and communicate with the ACS via a routing WAN link, thereby implementing management of the CPE by the ACS.

In some possible embodiments, the WAN link is configured to transmit an event message sent by the CPE to the ACS and a connection request sent by the ACS to the CPE, where an address of the connection request carried by the event message is a public network IP address of the CPE, and a destination address carried by the connection request is a public network IP address of the CPE. The embodiment provides a specific implementation mode for establishing communication between the CPE and the ACS, and improves the practicability of the scheme.

In some possible embodiments, the event message further includes a logical serial number of the CPE, the logical serial number of the CPE being associated with the logical serial number of the gateway, the logical serial number of the CPE being used to identify that the event message came from the CPE.

In this embodiment, since the CPE communicates with the ACS using its own public network IP address, the public network IP address of the CPE is in the same network segment as the public network IP address of the gateway. It is difficult for ACS to distinguish whether the device communicating with the ACS is a gateway or a CPE by using an IP address, so that an event message sent by the CPE to the ACS carries a logic serial number of the CPE, and the logic serial number of the CPE and the logic serial number of the gateway are managed, so that the CPE can be indicated to be a downstream device of the gateway, and the ACS can identify the CPE by using the event message, thereby realizing topology management.

In some possible embodiments, the method further comprises: the gateway associates the routed WAN link with a third port of the gateway so that the gateway outputs a message or message sent by the CPE over the routed WAN link from the designated third port to the ACS. For example, the event message may be transmitted to the ACS via a third port.

In a second aspect, an embodiment of the present application provides a method for configuring an IP address, where the method includes the following steps. The CPE sends a request message to the gateway through a bridge WAN link established by the gateway, and the gateway sends the request message to the ACS, wherein the request message is used for requesting the ACS to allocate a public network IP address for the CPE. And then, the gateway receives the configuration message sent by the ACS and sends the configuration message carrying the public network IP address of the CPE to the CPE through bridging the WAN link.

In some possible implementations, the bridged WAN link is established between a first port of the gateway and a second port of the CPE. And, the bridged WAN link is bound to the designated VLAN. The VLAN has a corresponding VLAN label, and the message interacted between the gateway and the CPE through the bridging WAN link carries the VLAN label so that the gateway can identify the message transmitted through the bridging WAN link and output the message from the appointed port.

In some possible implementations, a routing WAN link is also established between the second port of the CPE and the first port of the gateway. The routing WAN link is used for transmitting interaction information that CPE adopts public network IP address to communicate with ACS.

In some possible embodiments, after the CPE receives the configuration message sent by the gateway through the bridged WAN link, the method further includes: the CPE sends an event message carrying a connection request address to the gateway through the routing WAN link, so that the gateway sends the event message to the ACS, wherein the connection request address is a public network IP address of the CPE. The CPE receives a connection request sent by the gateway through a routing WAN link, wherein the connection request is sent to the gateway by the ACS, and a destination address carried by the connection request is a public network IP address of the CPE.

In a third aspect, an embodiment of the present application provides a gateway. The gateway comprises: a receiving unit and a transmitting unit. The receiving unit is used for: and receiving the request message sent by the CPE through the bridge WAN link. The transmitting unit is used for: and sending a request message to the ACS, wherein the request message is used for requesting the ACS to allocate a public network IP address for the CPE. Thereafter, the receiving unit is configured to: and receiving a configuration message sent by the ACS, wherein the configuration message comprises the public network IP address of the CPE. Further, the transmitting unit is configured to: the configuration message is sent to the CPE over the bridged WAN link.

In some possible implementations, bridging the WAN link establishes between the first port of the gateway and the second port of the CPE.

In some possible embodiments, a routing WAN link is further established between the second port of the CPE and the first port of the gateway, the routing WAN link being configured to transmit interaction information that the CPE uses the public network IP address to communicate with the ACS.

In some possible embodiments, the WAN link is configured to transmit an event message sent by the CPE to the ACS and a connection request sent by the ACS to the CPE, where an address of the connection request carried by the event message is a public network IP address of the CPE, and a destination address carried by the connection request is a public network IP address of the CPE.

In some possible embodiments, the gateway further comprises a processing unit for: the routed WAN link is associated with a third port of the gateway, and the event message is for transmission to the ACS via the third port.

In a fourth aspect, embodiments of the present application provide a CPE. The CPE comprises: a receiving unit and a transmitting unit. The transmitting unit is used for: and sending a request message to the gateway through bridging the WAN link of the wide area network, wherein the request message is sent to the ACS by the gateway and is used for requesting the ACS to allocate a public network IP address for the CPE. Thereafter, the receiving unit is configured to: and receiving a configuration message sent by the gateway through bridging the WAN link, wherein the configuration message is sent to the gateway by the ACS, and the configuration message comprises the public network IP address of the CPE.

In some possible implementations, the bridged WAN link is established between a first port of the gateway and a second port of the CPE.

In some possible embodiments, after the receiving unit receives the configuration message sent by the gateway through the bridged WAN link, the sending unit is further configured to: and sending an event message carrying a connection request address to the gateway through the routing WAN link, so that the gateway sends the event message to the ACS, wherein the connection request address is a public network IP address of the CPE. Thereafter, the receiving unit is configured to: and receiving a connection request sent by the gateway through a routing WAN link, wherein the connection request is sent to the gateway by the ACS, and the destination address carried by the connection request is the public network IP address of the CPE.

In the embodiment of the application, a bridging WAN link is established between the gateway and the CPE, and the CPE can pass through the gateway to acquire the own public network IP address from the ACS through the bridging WAN link. That is, the CPE no longer has only the private network IP address assigned by the gateway, and the CPE and gateway are comparable in public network for ACS. The CPE may then communicate with the ACS using its own public IP address. By the method, in the network comprising the ACS, the gateway and the CPE, the ACS can manage the CPE without configuring additional equipment, so that the implementation mode is simplified, and the operation and maintenance cost is reduced.

Drawings

FIG. 1 is a schematic diagram of a network architecture to which embodiments of the present application are applied;

fig. 2 is a first flowchart of a method for configuring an IP address according to an embodiment of the present application;

fig. 3 is a second flowchart of a method for configuring an IP address according to an embodiment of the present application;

Fig. 4 is a schematic structural diagram of a possible gateway according to an embodiment of the present application;

fig. 5 is a schematic structural diagram of another possible gateway according to an embodiment of the present application;

FIG. 6 is a schematic diagram of a possible CPE according to an embodiment of the present application;

Fig. 7 is a schematic diagram of another possible CPE according to an embodiment of the present application.

Detailed Description

It should be noted that the terms "first," "second," and the like in the description and claims of the application and in the foregoing figures, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the application described herein may be implemented, for example, in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

Fig. 1 is a schematic diagram of a network architecture to which an embodiment of the present application is applied. As shown in fig. 1, the network architecture includes an auto-configuration server (Auto Configuration Server, ACS) 10, a gateway 20, and at least one customer premise equipment (Customer Premises Equipment, CPE) 30. The network is divided into a public network and a private network, the gateway 20 is arranged at a routing exit position from the private network to the public network, and bidirectional traffic between the ACS 10 and the CPE 30 passes through the gateway 20. That is, the ACS 10 is in the public network, the CPE 30 is in the private network, the upstream port of the gateway 20 is connected to the downstream port of the ACS 10, and the downstream port of the gateway 20 is connected to the upstream port of the CPE 30. It should be understood that the application scenario of the present application may also be extended to a network architecture comprising a server, a network device and an intranet device, where ACS may be considered as a specific device type subordinate to the server, a gateway may be considered as a specific device type subordinate to the network device, and CPE may be considered as a specific device type subordinate to the intranet device. For ease of description, the following description will be given by taking as an example a network architecture comprising ACS, gateway and CPE.

It should be noted that, in order to facilitate the operation and maintenance of the network, the operator generally centrally manages the gateway through the ACS, and the CPE is a downstream device of the gateway, and cannot directly manage the CPE through the ACS due to the existence of the network address translation (Network Address Translation, NAT). However, the operator also wants to centrally manage the CPEs through the ACS, so that the present application provides a configuration method for IP addresses, and a bridged wide area network (Wide Area Network, WAN) link is established between the gateway and the CPEs, and the CPEs can obtain their own public network IP addresses from the ACS through the bridged WAN link. That is, the CPE no longer has only the private network IP address assigned by the gateway, and the CPE and gateway are comparable in public network for ACS. Afterwards, the CPE can communicate with the ACS through the routing WAN link, so that the ACS can perform centralized management on the CPE.

The following describes the configuration method of the IP address provided in the embodiment of the present application in detail. It should be understood that the ports of the gateway, CPE and ACS mentioned in the following embodiments may be physical ports or virtual ports, and the present application is not limited specifically.

Fig. 2 is a first flowchart of a method for configuring an IP address according to an embodiment of the present application. In this example, the configuration method of the IP address includes the following steps.

201. A bridged WAN link between the gateway and the CPE is established.

In this embodiment, the bridged WAN link is established by the gateway and the CPE in cooperation, specifically, the bridged WAN link is established between the downstream port of the gateway and the upstream port of the CPE. In one possible implementation, the establishment of the bridged WAN link is actively initiated by the gateway, and the CPE establishes the bridged WAN link in cooperation with the gateway according to the indication of the gateway. It should be appreciated that the bridged WAN link is bound to a designated virtual local area network (Virtual Local Area Network, VLAN). The VLAN has a corresponding VLAN label, and the message interacted between the gateway and the CPE through the bridging WAN link carries the VLAN label so that the gateway can identify the message transmitted through the bridging WAN link and output the message from the appointed port. The manner in which the gateway sets up the VLAN includes, but is not limited to, a static VLAN manner and a dynamic VLAN manner, and is not limited herein in particular. It should be appreciated that the bridged WAN link described above is primarily used to transmit configuration information, rather than traffic data, for interaction between ACS and CPE, that is, the bridged WAN link may be considered a management channel that is distinct from the traffic channel.

It should be noted that the gateway will also associate the bridged WAN link with the uplink port designated by the gateway. Thus, the gateway may output an upstream message sent by the CPE over the bridged WAN link from the designated upstream port to the ACS and send a downstream message received from the upstream port from the ACS to the CPE over the bridged WAN link. In one possible implementation, the gateway and ACS communicate over an already established first link between the two, e.g., the first link between the gateway and ACS is bound to the upstream port 1 of the gateway, which may be associated with the upstream port 1 of the gateway. In another possible embodiment, a second link different from the first link may be further established between the gateway and the ACS, for example, the second link between the gateway and the ACS is bound to the upstream port 2 of the gateway, and the bridged WAN link may also be associated with the upstream port 2 of the gateway. That is, the gateway may associate the bridged WAN link with an uplink port that has been configured by itself, or may newly configure an uplink port to associate with the bridged WAN link.

In some possible scenarios, multiple CPEs are suspended under the gateway, and different CPEs may correspond to different VLANs. Therefore, the gateway can bind the bridged WAN link with the designated VLAN according to the actual requirement, so that the designated CPE can obtain the configuration information from the ACS through the bridged WAN link. For example, with CPE1 and CPE2 suspended under the gateway, CPE1 is in VLAN1, CPE2 is in VLAN2, and if the bridged WAN link is bound to VLAN1, CPE1 can obtain configuration information from the ACS through the bridged WAN link. Similarly, if the bridged WAN link is bound to VLAN2, CPE2 may obtain configuration information from the ACS through the bridged WAN link.

202. The gateway receives the request message sent by the CPE over the bridged WAN link and sends the request message to the ACS.

The request message sent by the CPE is transmitted to the gateway through the bridge WAN link, and the gateway sends the request message to the ACS through the uplink port associated with the bridge WAN link. The request message is used for requesting the ACS to allocate a public network IP address to the CPE.

203. The gateway receives the configuration message sent by the ACS and sends the configuration message to the CPE through the bridged WAN link.

After the ACS receives the request message, it allocates a public network IP address to the CPE, and the configuration message issued by the gateway carries the public network IP address of the CPE. After the gateway receives the configuration message sent by the ACS, the configuration message can be transparently transmitted to the CPE through the bridged WAN link. The public network IP address of the CPE and the public network IP address of the gateway may be located in the same network segment, for example, the public network IP address of the gateway is 10.123.12.3, and the public network IP address of the CPE is 10.123.12.4. In this way, the CPE can communicate with the ACS using its own public IP address, and the communication process between the CPE and the ACS is described below with another embodiment.

Fig. 3 is a second flowchart of a method for configuring an IP address according to an embodiment of the present application. In this example, the configuration method of the IP address includes the following steps. It should be understood that the embodiment shown in fig. 3 is a further description of the embodiment shown in fig. 2, i.e. the process of communicating with the ACS after the CPE obtains its own public network IP address.

301. A routed WAN link between the CPE and the gateway is established.

In this embodiment, the routing WAN link is established between the upstream port of the CPE and the downstream port of the gateway. It should be appreciated that the routed WAN link is distinct from the bridged WAN links described above, and is primarily used to transport messages that interact between the CPE and ACS. In one possible implementation, the CPE may actively initiate the establishment of the routing WAN link upon indication of the gateway. The indication message sent by the gateway to the CPE may be any message type used for managing the CPE, for example, may be an indication message based on a smartlink protocol, or may be an indication message based on a DHCP protocol, which is not limited herein.

It should be appreciated that since the CPE obtains its own public network IP address from the ACS by bridging the WAN link, the CPE can employ its own public network IP address and communicate with the ACS by routing the WAN link. It should be noted that, the routing WAN link may bind the same VLAN as the bridging WAN link, that is, the packet interacted between the gateway and the CPE through the routing WAN link may also carry the VLAN tag, so that the gateway may identify the packet transmitted through the routing WAN link and make the packet output from the designated port.

It should also be noted that the gateway will also associate the routing WAN link with the uplink port designated by the gateway. Thus, the gateway may output an upstream message sent by the CPE over the routing WAN link from the designated upstream port to the ACS and send a downstream message received from the upstream port from the ACS to the CPE over the routing WAN link. Wherein the routing WAN link and the bridging WAN link may be associated with the same uplink port of the gateway.

302. The gateway receives the event message sent by the CPE through the routing WAN link and sends the event message to the ACS.

In this embodiment, the event message sent by the CPE carries a connection request address, where the connection request address is the public network IP address of the CPE. It should be understood that the event message may be a registration message, where the CPE will send the event message to the ACS when the CPE is first powered on to register, so as to indicate that the CPE registers with the ACS for the first time. The source address of the event message is the public network IP address of the CPE, and the destination address is the IP address of the ACS. In a possible implementation, in step 301, the indication message sent by the gateway to the CPE includes the IP address of the ACS.

It should be noted that, because the CPE uses its own public network IP address to communicate with the ACS, and the public network IP address of the CPE and the public network IP address of the gateway are in the same network segment. It is difficult for the ACS to distinguish whether the device communicating with the ACS is a gateway or a CPE through an IP address, so that an event message sent by the CPE to the ACS may indicate that the CPE is a downstream device of the gateway, so that the ACS can identify the CPE through the event message, thereby implementing topology management. It should be understood that the present application is not limited to a specific manner in which the event message indicates that the CPE is a downstream device of the gateway, and a possible implementation is described below.

Specifically, the gateway assigns a logical serial number to the CPE, wherein the logical serial number of the CPE is associated with the logical serial number of the gateway. For example, the gateway has a logical sequence number of 123456789012, the CPE has a logical sequence number of 123456789012-01, or the last two bits of the CPE's logical sequence number may be replaced with the CPE's MAC address. Furthermore, the indication message sent by the gateway to the CPE may carry the logic serial number of the CPE, and then the event message sent by the CPE to the ACS may also carry the logic serial number of the CPE. Thus, the ACS can identify the CPE based on the CPE's logical serial number.

It should be noted that, the indication message sent by the gateway to the CPE may perform other configurations on the CPE besides the several functions described above, which is not limited herein. In the following, as an example of extending the smartlink protocol, the configuration instruction of the indication message to the CPE can be shown in table 1 below.

TABLE 1

303. The gateway receives the connection request sent by the ACS and sends the connection request to the CPE through the routing WAN link.

The destination address carried by the connection request sent by the ACS is the public network IP address of the CPE. It should be appreciated that in practical applications, the ACS may also actively send a connection request to the CPE if the CPE has completed registration.

As can be seen from the description of the above embodiments, a bridge WAN link is established between the gateway and the CPE, and the CPE can obtain its own public network IP address from the ACS through the bridge WAN link. That is, the CPE no longer has only the private network IP address assigned by the gateway, and the CPE and gateway are comparable in public network for ACS. The CPE may then communicate with the ACS using its own public IP address. By the method, in the network comprising the ACS, the gateway and the CPE, the ACS can manage the CPE without configuring additional equipment, so that the implementation mode is simplified, and the operation and maintenance cost is reduced.

The gateway and CPE provided by the embodiments of the present application are described below.

Fig. 4 is a schematic structural diagram of a possible gateway according to an embodiment of the present application. The gateway comprises a sending unit 401 and a receiving unit 402. Specifically, the sending unit 401 is configured to perform the operation of sending a message by the gateway in the embodiments shown in fig. 2 and 3, and the receiving unit 402 is configured to perform the operation of receiving a message by the gateway in the embodiments shown in fig. 2 and 3.

Fig. 5 is a schematic structural diagram of another possible gateway according to an embodiment of the present application. The gateway comprises a processor 501 and a transceiver 502, the processor 501 and the transceiver 502 being interconnected by a wire. It should be noted that the transceiver 502 is configured to perform the operations of messaging by the gateway in the embodiments shown in fig. 2 and 3. The processor 501 is configured to perform other operations of the gateway, in addition to messaging, in the embodiments illustrated in fig. 2 and 3 described above. In some possible embodiments, the transceiver 502 includes the transmitting unit 401 and the receiving unit 402 described above. Optionally, the gateway may further comprise a memory 503, wherein the memory 503 is used for storing program instructions and data.

Fig. 6 is a schematic diagram of a possible CPE according to an embodiment of the present application. The CPE includes a transmitting unit 601 and a receiving unit 602. Specifically, the transmitting unit 601 is configured to perform the operation of transmitting a message by the CPE in the embodiments shown in fig. 2 and 3, and the receiving unit 602 is configured to perform the operation of receiving a message by the CPE in the embodiments shown in fig. 2 and 3.

Fig. 7 is a schematic diagram of another possible CPE according to an embodiment of the present application. The CPE includes a processor 701 and a transceiver 702, the processor 701 and the transceiver 702 being interconnected by a line. It should be noted that the transceiver 702 is configured to perform the operations of messaging by the CPE in the embodiments shown in fig. 2 and 3. The processor 701 is configured to perform other operations of the CPE in addition to messaging in the embodiments illustrated in fig. 2 and 3 described above. In some possible embodiments, the transceiver 702 includes the transmitting unit 601 and the receiving unit 602 described above. Optionally, the CPE may further comprise a memory 703, wherein the memory 703 is used for storing program instructions and data.

It should be noted that the processors shown in fig. 5 and fig. 7 may be general-purpose central processing units (Central Processing Unit, CPU), microprocessors, application specific integrated circuits ASICs, or at least one integrated circuit for executing related programs, so as to implement the technical solutions provided by the embodiments of the present application. The memory shown in fig. 5 and 7 described above may store an operating system and other application programs. When the technical scheme provided by the embodiment of the application is implemented by software or firmware, program codes for implementing the technical scheme provided by the embodiment of the application are stored in a memory and executed by a processor. In one embodiment, the processor may include memory within. In another embodiment, the processor and the memory are two separate structures.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, which are not repeated herein.

Those of ordinary skill in the art will appreciate that all or a portion of the steps implementing the above embodiments may be implemented by hardware, or may be implemented by a program for instructing the relevant hardware, where the program may be stored in a computer readable storage medium, where the storage medium may be a read-only memory, a random access memory, etc. Specifically, for example: the processing unit or processor may be a central processing unit, a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

When implemented in software, the method steps described in the above embodiments may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present application, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another, for example, by wired (e.g., coaxial cable, optical fiber, digital Subscriber Line (DSL)), or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state disk Solid STATE DISK (SSD)), etc.

Claims

1. A method for configuring an IP address, comprising:

After receiving a request message sent by a Customer Premise Equipment (CPE) through a bridge Wide Area Network (WAN) link, a gateway sends the request message to an Automatic Configuration Server (ACS), wherein the request message is used for requesting the ACS to allocate a public network IP address for the CPE;

The gateway receives a configuration message sent by the ACS, wherein the configuration message comprises a public network IP address of the CPE;

the gateway sends the configuration message to the CPE over the bridged WAN link.

2. The method of claim 1, wherein the bridged WAN link is established between a first port of the gateway and a second port of the CPE.

3. A method according to claim 1 or 2, wherein a routing WAN link is further established between the second port of the CPE and the first port of the gateway, the routing WAN link being configured to transmit interaction information that the CPE uses the public network IP address to communicate with the ACS.

4. A method according to claim 3, wherein the routing WAN link is configured to transmit an event message sent by the CPE to the ACS and a connection request sent by the ACS to the CPE, where an address of the connection request carried by the event message is a public network IP address of the CPE, and a destination address carried by the connection request is the public network IP address of the CPE.

5. The method of claim 4, wherein the event message further comprises a logical serial number of the CPE, the logical serial number of the CPE being associated with a logical serial number of the gateway, the logical serial number of the CPE being used to identify the event message from the CPE.

6. The method according to claim 4 or 5, characterized in that the method further comprises:

The gateway associates the routed WAN link with a third port of the gateway, the event message for transmission to the ACS via the third port.

7. A method for configuring an IP address, comprising:

The method comprises the steps that user equipment (CPE) sends a request message to a gateway through bridging a Wide Area Network (WAN) link, the request message is sent to an Automatic Configuration Server (ACS) by the gateway, and the request message is used for requesting the ACS to distribute a public network IP address for the CPE;

The CPE receives a configuration message sent by the gateway through the bridge WAN link, wherein the configuration message is sent to the gateway by the ACS, and the configuration message comprises a public network IP address of the CPE.

8. The method of claim 7, wherein the bridged WAN link is established between a first port of the gateway and a second port of the CPE.

9. A method according to claim 7 or 8, wherein a routing WAN link is further established between the second port of the CPE and the first port of the gateway, the routing WAN link being configured to transmit interaction information that the CPE uses the public network IP address to communicate with the ACS.

10. The method of claim 9, wherein after the CPE receives the configuration message sent by the gateway over the bridged WAN link, the method further comprises:

the CPE sends an event message carrying a connection request address to the gateway through the routing WAN link, so that the gateway sends the event message to the ACS, wherein the connection request address is a public network IP address of the CPE;

And the CPE receives a connection request sent by the gateway through the routing WAN link, wherein the connection request is sent to the gateway by the ACS, and a destination address carried by the connection request is a public network IP address of the CPE.

11. The method of claim 10, wherein the event message further comprises a logical serial number of the CPE, the logical serial number of the CPE being associated with a logical serial number of the gateway, the logical serial number of the CPE being used to identify the event message from the CPE.

12. A gateway, comprising: a receiving unit and a transmitting unit;

the receiving unit is used for: receiving a request message sent by Customer Premise Equipment (CPE) through a bridge Wide Area Network (WAN) link;

The transmitting unit is used for: sending the request message to an automatic configuration server ACS, wherein the request message is used for requesting the ACS to allocate a public network IP address for the CPE;

The receiving unit is used for: receiving a configuration message sent by the ACS, wherein the configuration message comprises a public network IP address of the CPE;

the transmitting unit is used for: and sending the configuration message to the CPE through the bridge WAN link.

13. The gateway of claim 12, wherein the bridged WAN link is established between a first port of the gateway and a second port of the CPE.

14. A gateway according to claim 12 or 13, wherein a routing WAN link is further established between the second port of the CPE and the first port of the gateway, the routing WAN link being configured to transmit interaction information that the CPE uses the public network IP address to communicate with the ACS.

15. The gateway of claim 14, wherein the routing WAN link is configured to transmit an event message sent by the CPE to the ACS and a connection request sent by the ACS to the CPE, where an address of the connection request carried by the event message is a public network IP address of the CPE, and a destination address carried by the connection request is the public network IP address of the CPE.

16. The gateway of claim 15, wherein the event message further comprises a logical serial number of the CPE, the logical serial number of the CPE being associated with the logical serial number of the gateway, the logical serial number of the CPE being used to identify the event message from the CPE.

17. Gateway according to claim 15 or 16, characterized in that it further comprises a processing unit for:

and associating the routing WAN link with a third port of the gateway, wherein the event message is used for being transmitted to the ACS through the third port.

18. A customer premise equipment CPE, comprising: a receiving unit and a transmitting unit;

The transmitting unit is used for: sending a request message to the gateway through bridging a WAN (wide area network) link, wherein the request message is sent to an ACS (auto configuration server) by the gateway and is used for requesting the ACS to allocate a public network IP (Internet protocol) address for the CPE;

The receiving unit is used for: and receiving a configuration message sent by the gateway through the bridge WAN link, wherein the configuration message is sent to the gateway by the ACS, and the configuration message comprises a public network IP address of the CPE.

19. The CPE of claim 18, wherein the bridged WAN link is established between a first port of the gateway and a second port of the CPE.

20. A CPE according to claim 18 or 19, characterized in that a routing WAN link is also established between the second port of the CPE and the first port of the gateway, said routing WAN link being used for transmitting interworking information that the CPE uses the public network IP address for communication with the ACS.

21. The CPE of claim 20, wherein after the receiving unit receives the configuration message sent by the gateway over the bridged WAN link, the sending unit is further configured to: sending an event message carrying a connection request address to the gateway through the routing WAN link, so that the gateway sends the event message to the ACS, wherein the connection request address is a public network IP address of the CPE;

The receiving unit is further configured to: and receiving a connection request sent by the gateway through the routing WAN link, wherein the connection request is sent to the gateway by the ACS, and a destination address carried by the connection request is a public network IP address of the CPE.

22. The CPE of claim 21, wherein the event message further comprises a logical serial number of the CPE associated with a logical serial number of the gateway, the logical serial number of the CPE being used to identify the event message from the CPE.