WO2011094956A1

WO2011094956A1 - Method, apparatus and system for address distribution

Info

Publication number: WO2011094956A1
Application number: PCT/CN2010/070568
Authority: WO
Inventors: 戚彩霞; 王姗姗; 胡颖
Original assignee: 华为技术有限公司
Priority date: 2010-02-08
Filing date: 2010-02-08
Publication date: 2011-08-11
Also published as: CN102870395A; CN102870395B

Abstract

Provided are a method, apparatus and system, which relate to wireless communication field and are used to solve the problem that binding can not be established or updated between a service gateway or access point and an inter working proxy element. A method for address distribution includes: the inter working proxy element transmits a request message to the packet data network gateway to request the IPv4 address of a terminal (201), receives the response message transmitted by the packet data network gateway (202), and transmits to the serving gateway or the access point the proxy binding acknowledgement message (203) which carries the IPv4 address, wherein the IPv4 address is the IPv4 address of the user terminal carried in the response message by the packet data network gateway or is distributed by the inter working proxy temporarily.

Description

Address allocation method, device and system

The present invention relates to the field of wireless communication technologies, and in particular, to an address allocation method, apparatus, and system.

Background technique

Figure 1 shows the logical architecture of the next generation mobile communication network. The user terminal accesses the mobile communication network through the local wireless access network, and the access node is the convergence point of the access network, and is responsible for location management, connection management, security authentication, gateway selection, and the like of the mobile user terminal; The gateway is a local access gateway of the user terminal, and is responsible for access technology related connection management and data forwarding. The data gateway is a gateway for the user terminal to access the external data network, and is responsible for data connection management and data forwarding of the user terminal accessing the packet data network. It is also the fault of providing mobile services for mobile users.

The interface protocol between the service gateway and the data gateway may be a GPRS (General Packet Radio Service) tunneling protocol (GPRS Tunneling Protocol, GTP for short), or a proxy mobile IPv6 protocol (Proxy Mobile IPv6, abbreviated as PMIP).

When the user terminal performs roaming, it returns to the local data gateway through the access node and the serving gateway of the visited place. If the interface protocol supported by the service gateway in the Public Land Mobile-Communication Network (PLMN) of the visited place is different from the interface protocol supported by the data gateway in the PLMN of the home location, for example, the service gateway of the visited place The data gateway supporting the GTP protocol and supporting the location supports the PMIP protocol, or the service gateway of the visited place supports the PMIP protocol and the data gateway of the home location supports the GTP protocol. At this time, the user terminal cannot return to the terrestrial location through the visited service gateway in the roaming place. The data gateway cannot access the communication network.

In order to solve the above problem, an Interworking Proxy (IWP) is introduced between the service gateway and the data gateway supporting different protocols, and the interworking proxy network element is responsible for mutual conversion between the PMIP protocol and the GTP protocol. To ensure that the user terminal is able to roam properly. Access to the communication network for telecommunications services.

For the case where there is no service gateway in some networks, the interworking proxy gateway can also implement the conversion of different protocols between the access node and the data gateway.

In the process of implementing the above-mentioned network access through the interworking proxy network element, the inventors found that at least the following problems exist in the prior art:

In a network with an interworking proxy network element, if the home PLMN only supports the GTP protocol, and the visited PLMN only supports the PMIP protocol, then the Attach, PDP (Packet Data Protocol) context activation, PDN (Packet Data Network) , packet data network) connection establishment, or PDN connection IPv4 (Internet Protocol version 4, Internet Protocol version 4) address allocation process, the interworking proxy network element will not be able to obtain DHCP (Dynamic Host Configuration Protocol) The case where the server or the data gateway is assigned to the IPv4 address of the user terminal; thus, the interworking proxy network element cannot send the IPv4 address of the user terminal to the serving gateway or the access node, thereby causing the serving gateway or the access node and the interworking proxy network element to The binding cannot be established or updated, and the user terminal cannot attach to the roaming network, activate the PDP context, or establish a PDN connection for service.

Summary of the invention

An embodiment of the present invention provides an address allocation method, apparatus, and system for solving the problem that a service gateway or an access node and an interworking proxy network element cannot be normally established or updated.

In order to achieve the above object, the embodiment of the present invention adopts the following technical solutions:

An address allocation method includes:

The interworking proxy network element sends a request message to the data gateway to request an IPv4 address of the user terminal; and receives a response message sent by the data gateway;

Sending a proxy binding acknowledgement message to the serving gateway or the access node, where the proxy binding acknowledgement message carries an IPv4 address, where the IPv4 address is an IPv4 address of the user terminal carried in the response message by the data gateway Or the IPv4 address is temporarily allocated by the interworking proxy network element.

An address allocation device includes: a requesting unit, configured to send a request message to the data gateway to request an IPv4 address of the user terminal, and a receiving unit, configured to receive a response message sent by the data gateway;

a sending unit, configured to send a proxy binding acknowledgement message to the serving gateway or the access node, where the proxy binding acknowledgement message carries an IPv4 address, where the IPv4 address is carried by the data gateway in the response message The IPv4 address of the user terminal or the IPv4 address is temporarily allocated by the address distribution device.

An address allocation system, comprising: an interworking proxy network element, an access node, and a data gateway; wherein the interworking proxy network element is configured to send a request message to the data gateway to request an IPv4 address of the user terminal;

The data gateway is configured to provide an IPv4 address to the interworking proxy network element according to the request message, where the IPv4 address is an IPv4 address of the user terminal or an IPv4 address of all 0s, and the IPv4 address is passed the response message. Sending to the interworking proxy network element;

The interworking proxy network element is further configured to send a proxy binding acknowledgement message to the access node, where the proxy binding acknowledgement message carries an IPv4 address, and the IPv4 address is provided by the data gateway to be carried in the response The IPv4 address of the user terminal in the message, or the IPv4 address is an IPv4 address temporarily allocated by the interworking proxy network element.

The address allocation method, device and system provided by the embodiment of the present invention firstly initiate a request for acquiring an IPv4 address of a user terminal to the data gateway by using the interworking proxy network element, or autonomously temporarily assigning a non-zero IPv4 by the interworking proxy network element. The address is then sent to the serving gateway or the access node from the IPv4 address of the user terminal or the temporarily assigned IPv4 address obtained from the data gateway, so that the service gateway or the access node and the interworking proxy network element are normally established. The binding enables the user terminal to complete the attach, establish a PDN connection or activate the PDP context at the roaming/visiting location to perform the corresponding service.

DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings to be used in the description of the embodiments will be briefly described below, and obviously, the attached in the following description The drawings are only some of the embodiments of the present invention, and those skilled in the art can obtain other drawings based on these drawings without any inventive labor.

1 is a logical architecture diagram of a next-generation mobile communication network in the prior art;

2 is a flowchart of an address allocation method in Embodiment 1 of the present invention;

3 is a schematic structural diagram of an address allocation apparatus according to Embodiment 1 of the present invention;

4 is a signaling flowchart of an address allocation method in Embodiment 2 of the present invention;

FIG. 5 is a signaling flowchart of an address allocation method in Embodiment 3 of the present invention;

6 is a signaling flowchart of an address allocation method in Embodiment 4 of the present invention;

Figure Ί is a signaling flowchart of an address allocation method in Embodiment 5 of the present invention;

8 is a signaling flowchart of an address allocation method in Embodiment 6 of the present invention;

9 is a signaling flowchart of an address allocation method in Embodiment 7 of the present invention;

FIG. 10 is a schematic structural diagram of an address allocation apparatus according to Embodiment 8 of the present invention; FIG.

FIG. 11 is a schematic structural diagram of an address allocation system in Embodiment 9 of the present invention.

detailed description

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

The address allocation method, apparatus, and system provided by the embodiments of the present invention are described in detail below with reference to the accompanying drawings.

Embodiment 1:

As shown in FIG. 2, the address allocation method provided in this embodiment includes:

201. The interworking proxy network element sends a request message to the data gateway to request an IPv4 address of the user terminal.

In this embodiment, the request message may be an attach procedure, a PDP context activation process, or a setup session request message in a PDN connection establishment process, or may be a DHCPv4 mode IP address. DHCPv4 discovery message in the address allocation process.

202. Receive a response message sent by the data gateway.

Corresponding to the different request message types in step 201, the response message in this step may be a session establishment response message or a DHCPv4 provision message.

203. Send a proxy binding acknowledgement message to the serving gateway or the access node.

The proxy binding acknowledgement message carries an IPv4 address, where the IPv4 address is an IPv4 address of the user terminal carried in the response message by the data gateway, or the IPv4 address is temporarily used by the interworking proxy network element. distribution.

Generally, the interworking proxy network element sends a proxy binding acknowledgement report to the serving gateway. In some non-3GPP access scenarios, there may be no serving gateway in the network, then the interworking proxy network element directly goes to the access node. Send a proxy binding confirmation report.

The execution body of the above steps may be an interworking proxy network element for mutual conversion of different protocols. In this example, an address allocation apparatus is further provided, and the foregoing steps may be implemented. As shown in FIG. 3, the address allocation apparatus includes:

The requesting unit 31 is configured to send a request message to the data gateway to request an IPv4 address of the user terminal;

The receiving unit 32 is configured to receive a response message sent by the data gateway.

The sending unit 33 is configured to send a proxy binding acknowledgement message to the serving gateway or the access node, where the proxy binding acknowledgement message carries an IPv4 address, where the IPv4 address is carried by the data gateway in the response message. The IPv4 address of the user terminal or the IPv4 address is temporarily allocated by the address distribution device.

The address allocating device in this embodiment may be an interworking proxy network element for being responsible for mutual conversion of different protocols.

The method and device for address allocation provided in this embodiment first initiates a request for acquiring an IPv4 address of a user terminal to the data gateway by using the interworking proxy network element, or autonomously temporarily assigns a non-zero IPv4 address by the interworking proxy network element. And then the user terminal obtained from the data gateway The IPv4 address or the temporarily assigned IPv4 address is sent to the serving gateway or the access node, so that the binding between the serving gateway or the access node and the interworking proxy network element is normally established, so that the user terminal can roam or visit the place. Complete the process of attaching, establishing a PDN connection, or activating a PDP context to perform the corresponding service.

Embodiment 2:

In this embodiment, the following scenario is first set up: The access network of the visited place where the mobile terminal is currently located is accessed through 3GPP (3rd Generation Partnership Project), which may be UTRAN (Universal Terrestrial) Radio Access Network, E-UTRAN (Evolved-Universal Terrestrial Radio Access Network) or GERAN (GSM EDGE Radio Access Network, GSM/EDGE Radio Access Network) In this embodiment, the access node may be a mobility management network element, and may be an MME (Mobility Management Entity) or an SGSN (Service GPRS Support Node); The SGW can be an SGW (Serving Gateway). The interworking proxy network element can be an IWP (Interworking Proxy). The data gateway can be a PGW (Packet Data Network Gateway).

Specifically, as shown in FIG. 4, the address allocation method provided in this embodiment includes the following steps: 401. A user terminal initiates an attach procedure, and sends an attach request (Attach Request) message to the mobility management network element.

The message may include a protocol configuration option (PCO), which is used to indicate to the data gateway that the user terminal requests to obtain the IPv4 address of the user terminal by using DHCPv4; or, of course, the PCO is not carried, then the data gateway is not required. Select the address allocation method according to its own configuration:

For example, the configuration on the data gateway is as follows: The address assignment corresponding to the Access Point Name (APN) can only be in the DHCPv4 mode, and the data gateway allocates the IPv4 address in the DHCPv4 manner. In this embodiment, the attaching process is taken as an example; of course, the scope of application of the solution is not limited thereto, and may also be a PDP context activation process or a PDN connection establishment process.

The mobile management network element sends a Create Session Request message to the serving gateway, where the setup session request message carries a PDN type to request the data gateway to allocate the IP address type to the user terminal; May carry a PCO.

403. The serving gateway sends a proxy binding update (Proxy Binding Update) message to the interworking proxy network element, where the message carries a request for assigning an IP address; the request message may carry a PCO.

The serving gateway carries the IPv6 (Internet Protocol version 6, Internet Protocol version 6) home network prefix option and/or the IPv4 home address request option in the proxy binding update message according to the PDN type carried in the session establishment request message by the mobility management network element. Transmitting to the interworking proxy network element to indicate the corresponding IP address request; specifically,

If the proxy binding update message carries only the IPv4 home address request option and does not carry the IPv6 home network prefix option, the PDN type is IPv4.

If the proxy binding update message carries the IPv4 home address request option and the IPv6 home network prefix option, the PDN type is IPv4 and IPv6.

If the proxy binding update message carries only the IPv6 home network prefix option and does not carry the IPv4 home address request option, the PDN type is IPv6.

404. The interworking proxy network element sends a setup session request to the data gateway, where the PDN type is carried, and the message may carry the PCO cell.

405. The data gateway replies with a Create Session Response message to the interworking proxy network element, where the response message carries a PDN type and a PDN address selected by the data gateway.

Specifically, the data gateway selects a PDN type according to factors such as a PDN type and a carrier policy carried in the received session establishment request message;

For example, if the PDN type carried in the setup session request message is IPv4 and IPv6, and the policy configured by the operator allows the APN to establish an IPv4 and IPv6 connection, the PDN type selected by the data gateway is IPv4 and IPv6. If the user terminal indicates in the PCO cell that the IPv4 address is obtained by means of DHCPv4 and the data gateway agrees, or the operator configures the PDN address associated with the request APN to be allocated only by DHCPv4, then the PDN type selected by the data gateway is IPv4. The IPv4 address in the PDN address in the setup session response message sent by the data gateway to the interworking proxy network element is all 0s. When the PDN type selected by the data gateway is IPv4 and IPv6, the PDN address carries the IPv6 prefix of the local network. Interface ID and all 0 IPv4 addresses.

406. After the interworking proxy network element receives the setup response message sent by the data gateway, if the IPv4 address in the PDN address carried in the PDN address is all 0, and the PDN type is IPv4, or IPv4 and IPv6, the interworking proxy network element can It is known that the data gateway allocates an IPv4 address to the user terminal in the manner of DHCPv4. At this time, the interworking proxy network element acts as a DHCP client, and sends a DHCPv4 Discover (DHCPv4 Discover) message to the data gateway to request the IPv4 address of the user terminal.

407. The data gateway acts as a DHCP server, and sends a DHCPv4 Offer (DHCPv4 Offer) message to the interworking proxy network element, where the message carries an IPv4 address and other settings allocated for the user terminal.

In the embodiment of the present invention, the IPv4 address of the user terminal is allocated by the data gateway, but is not limited thereto; of course, it may also be allocated by a DHCP server other than the data gateway. When an IPv4 address is assigned by a DHCP server other than the data gateway, the data gateway acts as a DHCP for the interworking proxy network element.

408. The interworking proxy network element sends a proxy binding acknowledgement (Proxy Binding Acknowledgement) message to the serving gateway.

If the PDN type in the setup session response returned by the data gateway is IPv4, the proxy binding acknowledgement message carries the IPv4 address obtained by the interworking proxy network element in step 407, and the DHCPv4 address allocation flow indication; After obtaining the IPv4 address of the user terminal, the service gateway can establish a binding between the service gateway and the interworking proxy network element.

If the PDN type is IPv4 and IPv6, the IPv6 prefix obtained in step 405 and the DHCPv4 address allocation process indication are carried in the proxy binding acknowledgement message. 409. The serving gateway sends a setup response message to the mobility management network element, where the setup session response message carries the PDN address.

If the PDN type selected by the data gateway is IPv4, and the proxy binding acknowledgement message in step 408 carries the DHCPv4 address allocation procedure indication, the PDN address carried in the setup session response message is an all-zero IPv4 address;

If the PDN type is IPv4 and IPv6, and the proxy binding acknowledgement message in step 408 carries the DHCPv4 address allocation procedure indication, the PDN address carried in the setup session response message includes an all-zero IPv4 address, and the step of passing 408 Obtained IPv6 prefix.

410. The mobility management network element sends an attach accept message to the user terminal, where the attach accept message carries the PDN address.

Similarly, if the user terminal sends a PDP Context Activation Request (PDP Context Activation Request) message or a PDN Connectivity Request (PDN Connectivity Request) message to the mobility management network element in step 401, then correspondingly moves in this step. The management network element may feed back a PDP context activation accept message or a PDN connection establishment accept message to the user terminal, and the PDP context activation accept message or the PDN connection setup accept message carries the PDN address.

411. The user terminal broadcasts a DHCPv4 discovery message.

If the PDN type selected by the data gateway is IPv4, the binding between the serving gateway and the interworking proxy network element is established after the step 408; at this time, after step 411 is completed, step 414 can be directly performed. Its subsequent steps;

If the PDN type selected by the data gateway is IPv4 and IPv6, steps 412, 413 and subsequent steps are required to update the binding between the serving gateway and the data gateway.

412. After receiving the DHCPv4 discovery message, the serving gateway sends a proxy binding update message to the interworking proxy network element, where the proxy binding update message carries an all-zero IPv4 address.

413. The interworking proxy network element replies to the proxy binding acknowledgement message to the serving gateway, where the message carries the IPv4 address allocated for the user terminal obtained in step 407, and the binding between the service gateway update and the interworking proxy network element. 414. The serving gateway acts as a DHCP relay, and forwards the DHCPv4 discovery message sent by the user terminal to the interworking proxy network element.

415. The interworking proxy network element is used as the DHCP server of the user terminal, and sends a DHCPv4 providing message to the serving gateway. The DHCPv4 providing message carries the IPv4 address allocated to the user terminal obtained through step 407, and other settings. The serving gateway forwards the message to the user terminal, whereby the user terminal obtains the IPv4 address.

After that, the user terminal initiates a DHCPv4 request procedure, and confirms the received IPv4 address to the DHCP server.

In the subsequent process, the interworking proxy network element acts as the DHCP server of the user terminal, and also processes the DHCP-related process as the DHCP client of the data gateway.

In this embodiment, if the PDN type selected by the data gateway is IPv4 and IPv6, the execution order of steps 406 and 407 may be scheduled after step 412; that is, the original steps 406 and 407 are ignored, and in step 412 And add between step 413:

412-1. After receiving the proxy binding update message sent by the serving gateway, the interworking proxy network element acts as a DHCP client of the data gateway, and sends a DHCPv4 discovery message to the data gateway to request an IPv4 address of the user terminal.

412-2. The data gateway replies to the interworking proxy network element with a DHCPv4 providing message, where the message carries an IPv4 address and other settings allocated for the user terminal. The IPv4 address can be assigned by the data gateway or by a DHCP server other than the data gateway.

Then, the IPv4 address involved in step 413 and step 415 may also be obtained in step 412-2.

The address allocation method provided in this embodiment firstly sends a DHCPv4 discovery message to the data gateway of the user terminal by the interworking proxy network element to request to obtain the IPv4 address of the user terminal, and then sends the IPv4 address of the user terminal acquired from the data gateway to the IPv4 address of the user terminal. Serving the gateway, so that the binding between the serving gateway and the interworking proxy network element is normally established, so that the user terminal can attach, establish a PDN connection or activate a PDP context to perform corresponding services at the roaming/visiting location. Embodiment 3:

The solution described in the second embodiment is based on the access network where the mobile terminal is located.

3GPP accesses such a scenario to implement; however, the implementation of the solution provided by the present invention is not limited thereto, and the same applies to a scenario in which a visited access network passes non-3GPP access.

Specifically, in this embodiment, the non-3GPP access network may be WiMax (Worldwide Interoperability for Microwave Access) or CDMA (Code Division Multiple Access) or WLAN (Wireless Local) A wireless access network such as an Area Network (WLAN); an access node may be an access gateway/evolved packet data gateway, ie, an A-GW (Access Gateway) or an ePDG (Evolved Packet Data Gateway). The data gateway can be a SGW, the interworking proxy network element can be an IWP, and the data gateway can be a PGW.

For the address allocation method provided in this embodiment, reference may be made to FIG. 5; wherein, steps 501 to 510 are substantially the same as steps 401 to 410 in the second embodiment, and are not described in detail herein; Introduced as follows:

The access node in the second embodiment is a mobility management network element, and in this embodiment is an access gateway or an evolved packet data gateway (hereinafter abbreviated as: access gateway/evolved packet data gateway). The function of the ingress node and the corresponding service;

In step 501, the user terminal initiates an attach procedure or a PDN connection setup procedure. In step 502, the access gateway/evolved packet data gateway sends a proxy binding update message to the serving gateway, where the request for assigning an IP address is carried;

In step 509, the serving gateway forwards the received proxy binding response message to the access gateway/evolved packet data gateway;

In step 510, the attach process or the PDN connection establishment process ends.

The process after step 510 is roughly as follows:

511. The user terminal broadcasts a DHCPv4 discovery message.

If the PDN type selected by the data gateway is IPv4, then after step 508 Binding between the access gateway/evolved packet data gateway and the serving gateway, and between the serving gateway and the interworking proxy network element has been established. At this time, after step 511 is completed, step 514 and subsequent steps can be directly performed;

If the PDN type selected by the data gateway is IPv4 and IPv6, steps 512, 513 and subsequent steps are required to update between the access gateway/evolved packet data gateway and the serving gateway, between the serving gateway and the interworking proxy network element. Binding.

512. After receiving the DHCPv4 discovery message, the access gateway/evolved packet data gateway sends a proxy binding update message to the serving gateway, where the proxy binding update message carries an all-zero IPv4 address. The serving gateway forwards the proxy binding update message to the interworking proxy network element.

513. The interworking proxy network element returns a proxy binding acknowledgement message to the serving gateway, where the message carries an IPv4 address allocated for the user terminal, and the IPv4 address is obtained in step 507 to update the binding between the serving gateway and the interworking proxy network element. . The serving gateway forwards the proxy binding acknowledgement message to the access gateway/evolved packet data gateway.

514. The access gateway/evolved packet data gateway acts as a DHCP relay and forwards the DHCPv4 discovery message to the serving gateway. The serving gateway forwards the DHCPv4 discovery message to the interworking proxy network element.

515. The interworking proxy network element sends a DHCPv4 providing message to the serving gateway, where the DHCPv4 providing message carries the IPv4 address allocated to the user terminal obtained through step 507, and other settings. The serving gateway forwards the message to the access gateway/evolved packet data gateway, and the access gateway/evolved packet data gateway forwards the DHCPv4 providing message to the user terminal, whereby the user terminal acquires the IPv4 address.

Since the access gateway/evolved packet data gateway can serve as the DHCP server on the user terminal side in some cases, when the access gateway/evolved packet data gateway is used as the DHCP server, the above step 514 can be omitted, and at step 515 Replaced by step 515-1:

515-1. The access gateway/evolved packet data gateway sends a DHCPv4 providing message to the user terminal, where the DHCPv4 providing message carries the IPv4 address allocated to the user terminal acquired in step 509 or step 513, and other settings. After that, the user terminal initiates a DHCPv4 request procedure, and confirms the received IPv4 address to the DHCP server.

As in the second embodiment, in this embodiment, if the PDN type selected by the data gateway is IPv4 and IPv6, the execution order of steps 506 and 507 may be scheduled after step 512; that is, the original step 506 and 507 ignores, and adds between step 512 and step 513:

512-1. After receiving the proxy binding update message sent by the serving gateway, the interworking proxy network element acts as a DHCP client of the data gateway, and sends a DHCPv4 discovery message to the data gateway to request an IPv4 address of the user terminal.

512-2. The data gateway replies to the interworking proxy network element with a DHCPv4 providing message, where the message carries an IPv4 address and other settings allocated for the user terminal. The IPv4 address can be assigned by the data gateway or by a DHCP server other than the data gateway.

Then, the IPv4 address involved in step 513 and step 515 may also be obtained in step 512-2.

In addition, since there may be no serving gateway in the network in the case of non-3GPP access, signaling transmission between the interworking proxy network element and the access gateway/evolved packet data gateway in this embodiment does not need to be performed. The serving gateway performs forwarding; for example, step 502 and step 503 can be merged into the same process, and steps 508 and 509 can be combined into the same process, thereby between the interworking proxy network element and the access gateway/evolved packet data gateway. Establish bindings directly.

The address allocation method provided in this embodiment firstly sends a DHCPv4 discovery message to the data gateway through the interworking proxy network element to request to obtain the IPv4 address of the terminal, and then sends the IPv4 address obtained from the data gateway to the access node, thereby establishing normally. The binding between the access node and the interworking proxy network element enables the user terminal to attach, establish a PDN connection or activate a PDP context to perform corresponding services at the roaming/visiting location.

Embodiment 4:

In this embodiment, the following scenario is first set up: The access network where the mobile terminal is currently located is accessed through 3GPP, which may be UTRAN/E-UTRAN/GERAN; For example, the access node may be a mobile management network element, and may be an MME or an SGSN. In addition, the serving gateway may be an SGW, the interworking proxy network element may be an IWP, and the data gateway may be a PGW.

Specifically, as shown in FIG. 6, the address allocation method provided in this embodiment includes the following steps:

601. The user terminal initiates an attach procedure, and sends an attach request message to the mobility management network element.

The message carries a protocol configuration option PCO cell, and is used to indicate to the data gateway that the user terminal requests to obtain the IPv4 address of the user terminal by using DHCPv4.

In this embodiment, the attaching process is taken as an example; of course, the scope of application of the solution is not limited thereto, and may also be a PDP context activation process or a PDN connection establishment process.

602. The mobility management network element sends a setup session request message to the serving gateway, where the setup session request message carries a PDN type to request an IP address type assigned to the user terminal, and the message carries the PCO cell.

603. The service gateway sends a proxy binding update message to the interworking proxy network element, where the message carries a request for allocating an IP address; the request message carries a PCO.

After the serving gateway obtains the PDN type in the session establishment request message, the mobility management network element carries the IPv6 home network prefix option and/or the IPv4 home address request option in the proxy binding update message according to the PDN type, and sends the information to the interworking device. Proxy network element, to indicate the corresponding IP address request; specifically,

604. If the IP address request type carried in the binding update message received by the interworking proxy network element is IPv4, or IPv4 and IPv6, and the PCO information indicates that the user terminal requests to obtain an IPv4 address by using DHCPv4, the interworking proxy The network element changes the content of the PCO cell to indicate the user terminal. The IP address is assigned by the NAS (Non-Access-Stratified) signaling, and the modified PCO cell is carried in the setup session request message and sent to the data gateway, where the setup session request message is also carried. PDN type.

605. The data gateway returns a setup response message to the interworking proxy network element, where the response message carries a PDN type and a PDN address selected by the data gateway.

If the PDN type carried in the session response message is IPv4, and the PCO cell indicates that the request is to allocate an IP address through the NAS signaling, the PDN address carries the allocated IPv4 address;

If the PDN type carried in the session response message is IPv4 and IPv6, and the PCO cell indicates that the request is to allocate an IP address through the NAS signaling, the PDN address carries the assigned IPv4 address, and the assigned IPv6 prefix and the interface identifier.

In an embodiment of the present invention, the IPv4 address of the user terminal is allocated by the data gateway, but is not limited thereto; of course, it may also be allocated by a network element other than the data gateway.

606. The interworking proxy network element sends a proxy binding acknowledgement message to the serving gateway.

If the PDN type selected by the data gateway is IPv4, the proxy binding acknowledgement message carries the IPv4 address allocated to the user terminal obtained in step 605, and the message may carry the DHCPv4 address allocation process indication, or may not carry The DHCPv4 address allocation process indicates that the service gateway can establish a binding between the service gateway and the interworking proxy network element after obtaining the IPv4 address of the user terminal;

If the PDN type selected by the data gateway is IPv4 and IPv6, the proxy binding acknowledgement message carries the IPv6 prefix and the DHCPv4 address allocation process indication in the case that the DHCPv4 address allocation process is required. The DHCPv4 address is not required. In the case of the allocation process, the proxy binding acknowledgement message carries the IPv4 address and the IPv6 prefix assigned to the user terminal obtained in step 605.

The IPv4 address and the IPv6 prefix of the user terminal are all established through the setup session in step 605. Respond to the message to get it.

607. The serving gateway sends a setup response message to the mobility management network element, where the setup session response message carries the PDN address.

If the PDN type is IPv4, and the proxy binding acknowledgement message received by the serving gateway carries the DHCPv4 address allocation procedure indication, the IPv4 address in the PDN address is all 0; if the proxy binding acknowledgement message received by the serving gateway is not carried The DHCPv4 address allocation process indicates that the PDN address is the IPv4 address of the user terminal obtained through step 605.

If the PDN type is IPv4 and IPv6, and the proxy binding acknowledgement message received by the serving gateway carries the DHCPv4 address allocation process indication, the PDN address includes an IPv6 prefix and an interface identifier, and an all-zero IPv4 address; The acknowledgment message does not carry the DHCPv4 allocation process indication, and the PDN address includes the IPv4 address, the IPv6 prefix, and the interface identifier of the user terminal obtained in step 605.

608. The mobility management network element sends an attach accept message to the user terminal, where the attach accept message carries the PDN address obtained in step 607.

Similarly, if the user terminal sends a PDP context activation request message or a PDN connection establishment request message to the mobility management network element in step 601, the mobile management network element correspondingly feeds back the PDP context activation to the user terminal in this step. The accept message, or the PDN connection establishment accept message, and the PDP context activation accept message or the PDN connection setup accept message carries the PDN address.

The following steps 609 and subsequent processes only occur when the IPv4 address of the PDN address received by the user terminal is all 0s.

609. The user terminal broadcasts a DHCPv4 discovery message.

If the PDN type selected by the data gateway is IPv4, the binding between the serving gateway and the interworking proxy network element is established after the step 606. At this time, after step 609 is completed, step 612 can be directly performed. Its subsequent steps;

If the PDN type selected by the data gateway is IPv4 and IPv6, step 610 is required. 611 and subsequent steps are used to update the binding between the serving gateway and the interworking proxy network element.

610. After receiving the DHCPv4 discovery message, the serving gateway sends a proxy binding update message to the interworking proxy network element, where the proxy binding update message carries an all-zero IPv4 address.

611. The interworking proxy network element returns a proxy binding acknowledgement message to the serving gateway, where the proxy binding acknowledgement message carries an IPv4 address allocated for the user terminal, and the IPv4 address is obtained in step 605 to update the serving gateway and the interworking proxy network. Binding between meta.

612. The serving gateway acts as a DHCP relay, and forwards the DHCPv4 discovery message sent by the user terminal to the interworking proxy network element.

613. The interworking proxy network element is used as a DHCP server of the user terminal, and sends a DHCPv4 providing message to the serving gateway. The DHCPv4 providing message carries the IPv4 address and other settings allocated by the step 605 for the user terminal. The serving gateway forwards the message to the user terminal, whereby the user terminal obtains the IPv4 address.

In the subsequent process, the interworking proxy network element will process the DHCP-related process as the DHCP server of the user terminal.

The address allocation method provided in this embodiment firstly initiates a session establishment request message to the data gateway to request the IPv4 address of the user terminal by using the interworking proxy network element, and then sends the IPv4 address obtained from the data gateway to the service gateway, thereby establishing normally. Binding between the serving gateway and the interworking proxy network element enables the user terminal to complete the attach, establish a PDN connection, or activate the PDP context to perform the corresponding service at the roaming/visiting location.

Embodiment 5:

The solution described in Embodiment 4 is implemented based on the scenario where the access network where the mobile terminal is located is accessed through 3GPP access; however, the implementation of the solution provided by the present invention is not limited thereto, and is The scenario of accessing the network through non-3GPP access is also applicable.

Specifically, in this embodiment, the non-3GPP access network may be WiMax/CDMA/WLAN. The access node may be an access gateway/evolved packet data gateway, and may be A-GW/ePDG when implemented; the service gateway may be an SGW, the interworking proxy network element may be an IWP, and the data gateway may be PGW.

For the address allocation method provided in this embodiment, reference may be made to FIG. 7: Steps 701 to 708 are substantially the same as steps 601 to 608 in Embodiment 4, and are not described in detail herein; Introduced as follows:

The access node in the fourth embodiment is a mobility management network element, and in this embodiment, the access gateway/evolved packet data gateway bears the function of the access node and the corresponding service;

In step 701, the user terminal initiates an attach procedure or a PDN connection establishment procedure. In step 702, the access gateway/evolved packet data gateway sends a proxy binding update message to the serving gateway, where the request for assigning an IP address is carried;

In step 707, the serving gateway forwards the received proxy binding response message to the access gateway/evolved packet data gateway;

In step 708, the attach or PDN connection establishment process ends.

As in the fourth embodiment, the process in step 709 and subsequent steps occurs only when the IPv4 address of the PDN address received by the user terminal is all 0s; the specific process is as follows:

709. The user terminal broadcasts a DHCPv4 discovery message.

If the PDN type selected by the data gateway is IPv4, the binding between the access gateway/evolved packet data gateway and the serving gateway, the serving gateway, and the interworking proxy network element is established after step 706; After completing step 709, step 712 and subsequent steps may be directly performed;

If the PDN type selected by the data gateway is IPv4 and IPv6, steps 710, 711 and subsequent steps are required to update the binding between the access gateway/evolved packet data gateway and the serving gateway, the serving gateway, and the interworking proxy network element. set.

710. After receiving the DHCPv4 discovery message, the access gateway/evolved packet data gateway sends a proxy binding update message to the serving gateway, and carries the all-zero IPv4 in the proxy binding update message. address. The serving gateway forwards the proxy binding update message to the interworking proxy network element.

711. The interworking proxy network element returns a proxy binding acknowledgement message to the serving gateway, and the serving gateway forwards the proxy binding acknowledgement message to the access gateway/evolved packet data gateway. The proxy binding acknowledgement message is carried as a user terminal. The assigned IPv4 address, which is obtained in step 705, to update the binding between the access gateway/evolved packet data gateway and the serving gateway, the serving gateway, and the interworking proxy network element.

712. The access gateway/evolved packet data gateway acts as a DHCP relay, and forwards the DHCPv4 discovery message sent by the user terminal to the serving gateway. The serving gateway forwards the DHCPv4 discovery message to the interworking proxy network element.

713. The interworking proxy network element is configured as a DHCP server on the user terminal side, and sends a DHCPv4 providing message to the serving gateway, where the DHCPv4 providing message carries the IPv4 address allocated for the user terminal obtained in step 705, and other settings. The serving gateway forwards the message to the access gateway/evolved packet data gateway, and the access gateway/evolved packet data gateway forwards the DHCPv4 providing message to the user terminal, whereby the user terminal acquires the IPv4 address.

Since in some cases, the access gateway/evolved packet data gateway can serve as a DHCP server on the user terminal side; and when the access gateway/evolved packet data gateway is used as the DHCP server, the above step 712 can be omitted, and at the same time, step 713 Replaced by step 713-1:

713-1. The access gateway/evolved packet data gateway sends a DHCPv4 providing message to the user terminal, where the DHCPv4 providing message carries the IPv4 address assigned to the user terminal carried in step 705, and other settings.

In the subsequent process, if the access gateway/evolved packet data gateway functions as a DHCP relay, the interworking proxy network element will process the DHCP-related process as the DHCP server on the user terminal side.

In addition, since there may be no serving gateway in the network in the case of non-3GPP access, signal transmission between the interworking proxy network element and the access gateway/evolved packet data gateway in this embodiment The process does not need to be forwarded by the service gateway; for example, step 702 and step 703 in the figure can be merged into the same process, and step 706 and step 707 can be merged into the same process, thereby directly establishing the interworking proxy network element and the Binding between access gateways/evolved packet data gateways.

The address allocation method provided in this embodiment firstly initiates a session establishment request message to the data gateway through the interworking proxy network element to request to obtain the IPv4 address of the user terminal, and then sends the IPv4 address obtained from the data gateway to the access gateway/evolution. a packet data gateway, so that the binding between the access gateway/evolved packet data gateway and the interworking proxy network element is normally established, so that the user terminal can attach, establish a PDN connection or activate a PDP context at a roaming/visiting location. Carry out the corresponding business.

Example 6:

In this embodiment, the following scenario is first set up: The access network where the mobile terminal is currently located is accessed through 3GPP, which may be UTRAN/E-UTRAN/GERAN; in this embodiment, the access node It may be a mobility management network element, and may be an MME or an SGSN. In addition, the service gateway may be an SGW, the interworking proxy network element may be an IWP, and the data gateway may be a PGW.

Specifically, as shown in FIG. 8, the address allocation method provided in this embodiment includes the following steps:

801. The user terminal initiates an attach procedure, and sends an attach request message to the mobility management network element.

The message configuration option PCO cell may be carried in the message, and is used to indicate to the data gateway that the user terminal requests to obtain the IPv4 address of the user terminal by using DHCPv4.

802. The mobility management network element sends a setup session request message to the serving gateway, where the setup session request message carries a PDN type to request an IP address type assigned to the user terminal; and the message may carry a PCO cell.

803. The serving gateway sends a proxy binding update message to the interworking proxy network element, where the message carries a request for allocating an IP address; the request message carries a PCO cell.

The serving gateway carries the IPv6 home network prefix option and/or the IPv4 home address request option in the proxy binding update according to the PDN type carried in the session establishment request message by the mobility management network element. The information is sent to the interworking proxy network element to indicate the corresponding IP address request. Specifically, if the proxy binding update message carries only the IPv4 home address request option and does not carry the IPv6 home network prefix option, the PDN type is IPv4.

804. The interworking proxy network element sends a session establishment request to the data gateway, where the PDN type is carried, and the message may carry the PCO cell.

805. The data gateway returns a setup response message to the interworking proxy network element, where the setup session response message carries a PDN type and a PDN address selected by the data gateway.

For example, if the received PDN type in the setup session request message is IPv4 and IPv6, the policy configured by the operator allows the APN to establish an IPv4 and IPv6 connection, and the PDN type selected by the data gateway is IPv4 and IPv6.

If the user terminal indicates in the PCO cell that the IPv4 address is obtained by means of DHCPv4 and the data gateway agrees, or the operator configures the PDN address associated with the request APN to be allocated only by DHCPv4, then the PDN type selected by the data gateway is IPv4. The IPv4 address in the PDN address in the setup session response message sent by the data gateway to the interworking proxy network element is all 0s. When the PDN type selected by the data gateway is IPv4 and IPv6, the PDN address carries the IPv6 prefix of the local network. Interface ID and all 0 IPv4 addresses.

806. The interworking proxy network element sends a proxy binding acknowledgement message to the serving gateway.

If the PDN type selected by the data gateway is IPv4, the proxy binding acknowledgement message carries a non-zero IPv4 address and a DHCPv4 address allocation process indication, where the IPv4 address is temporarily allocated by the interworking proxy network element, and Is generated randomly, or it can be generated according to a specific algorithm; In this way, after obtaining the non-zero IPv4 address, the serving gateway can establish a binding between the serving gateway and the interworking proxy network element.

If the PDN type selected by the data gateway is IPv4 and IPv6, the message carries an IPv6 prefix and a DHCPv4 address allocation process indication, where the IPv6 prefix is obtained through the establishment session response message in step 805.

807. The serving gateway sends a setup response message to the mobility management network element, where the setup session response message carries the PDN address.

If the PDN type is IPv4, and the proxy binding acknowledgement message received by the serving gateway carries the DHCPv4 address allocation process indication, the IPv4 address in the PDN address is all 0s;

If the PDN type is IPv4 and IPv6, and the proxy binding confirmation message received by the serving gateway carries the DHCPv4 address allocation process indication, the PDN address includes an IPv6 prefix and an interface identifier, and an all-zero IPv4 address.

808. The mobility management network element sends an attach accept message to the user terminal, where the attach accept message carries the PDN address.

Similarly, if the user terminal sends a PDP context activation request message or a PDN connection establishment request message to the mobility management network element in step 801, then correspondingly the mobility management network element feeds back the PDP context activation to the user terminal in this step. The accept message, or the PDN connection establishment accept message, and the PDP context activation accept message or the PDN connection setup accept message carries the PDN address.

809. The user terminal broadcasts a DHCPv4 discovery message.

If the PDN type selected by the data gateway is IPv4, then the binding between the serving gateway and the interworking proxy network element is established after the step 806; at this time, after step 809 is completed, step 812 can be directly performed. Its subsequent steps;

If the PDN type selected by the data gateway is IPv4 and IPv6, steps 810, 811 and subsequent steps are required to update the binding between the serving gateway and the interworking proxy network element.

810. After receiving the DHCPv4 discovery message, the serving gateway sends a proxy binding update message to the The interworking proxy network element carries an all-zero IPv4 address in the proxy binding update message.

811. The interworking proxy network element returns a proxy binding acknowledgement message to the serving gateway, where the proxy binding acknowledgement message carries a non-zero IPv4 address to update the binding between the serving gateway and the interworking proxy network element. The non-zero IPv4 address is temporarily allocated by the interworking proxy network element, which may be randomly generated or generated according to a specific algorithm.

812. The serving gateway acts as a DHCP relay, and forwards the DHCPv4 discovery message sent by the user terminal to the interworking proxy network element.

813. The interworking proxy network element acts as a DHCP relay, and forwards the DHCPv4 discovery message sent by the interworking proxy network element to the data gateway, where the DHCPv4 message carries an all-zero address request option.

814. The data gateway acts as a DHCP server, and sends a DHCPv4 providing message to the interworking proxy network element. The DHCPv4 providing message carries an IPv4 address and other settings allocated for the user terminal. The interworking proxy network element forwards the DHCPv4 providing message to the serving gateway; after receiving the message, the serving gateway finds that the IPv4 address carried in the DHCPv4 providing message is carried in the message sent by the interworking proxy network element in step 806 or step 811. The IPv4 address is different, and the serving gateway stores the IPv4 address carried in the DHCPv4 providing message, and updates the binding. The serving gateway forwards the DHCPv4 providing message to the user terminal, whereby the user terminal obtains an IPv4 address.

In the embodiment of the present invention, the IPv4 address of the user terminal is allocated by the data gateway, but is not limited thereto; of course, it may also be allocated by a DHCP server other than the data gateway. When an IPv4 address is assigned by a DHCP server other than the data gateway, the data gateway acts as a DHCP server for the user terminal and also serves as a DHCP client for the DHCP server that allocates the IPv4 address.

In the subsequent process, the interworking proxy network element will act as a DHCP relay to handle DHCP-related processes. The address allocation method provided in this embodiment is to send a non-zero IPv4 address temporarily assigned by the interworking proxy network element to the serving gateway, thereby establishing a binding between the serving gateway and the interworking proxy network element, so that the user terminal Can attach, establish a PDN connection or activate a PDP at a roaming/visiting location The context is used to perform the corresponding service; after that, the IPv4 address assigned to the user terminal is obtained through the normal process.

Example 7:

The solution described in Embodiment 6 is implemented based on the scenario where the access network where the mobile terminal is located is accessed through 3GPP access; however, the implementation of the solution provided by the present invention is not limited thereto, and is The scenario of accessing the network through non-3GPP access is also applicable.

Specifically, in this embodiment, the non-3GPP access network may be a wireless access network such as WiMax/CDMA/WLAN; the access node may be an access gateway/evolved packet data gateway, and may be A when implemented. -GW/ePDG; The service gateway can be an SGW, the interworking proxy network element can be an IWP, and the data gateway can be a PGW.

For the address allocation method provided in this embodiment, reference may be made to FIG. 9: Steps 901 to 908 are substantially the same as steps 801 to 808 in Embodiment 6, and are not described in detail herein; Introduced as follows:

The access node in the sixth embodiment is a mobility management network element, and in this embodiment, the access gateway/evolved packet data gateway bears the function of the access node and the corresponding service;

In step 901, the user terminal initiates an attach procedure or a PDN connection setup procedure. In step 902, the access gateway/evolved packet data gateway sends a proxy binding update message to the serving gateway, where the request for assigning an IP address is carried;

In step 907, the serving gateway forwards the received proxy binding response message to the access gateway/evolved packet data gateway;

In step 908, the attach or PDN connection establishment process ends.

The flow after step 908 is roughly as follows:

909. The user terminal broadcasts a DHCPv4 discovery message.

If the PDN type selected by the data gateway is IPv4, the binding between the access gateway/evolved packet data gateway and the serving gateway, the serving gateway, and the interworking proxy network element is established after step 906; After completing step 909, step 912 can be directly performed Next steps;

If the PDN type selected by the data gateway is IPv4 and IPv6, steps 910, 911, and subsequent steps are required to update the binding between the access gateway/evolved packet data gateway and the serving gateway, the serving gateway, and the interworking proxy network element. set.

910. After receiving the DHCPv4 discovery message, the access gateway/evolved packet data gateway sends a proxy binding update message to the serving gateway, where the proxy binding update message carries an all-zero IPv4 address. The serving gateway forwards the DHCPv4 discovery message to the interworking proxy network element.

911. The interworking proxy network element replies to the proxy binding acknowledgement message to the serving gateway, and the proxy gateway forwards the proxy binding acknowledgement message to the access gateway/evolved packet data gateway, where the proxy binding acknowledgement message carries a non-zero An IPv4 address to update the binding between the access gateway/evolved packet data gateway and the serving gateway, the serving gateway, and the interworking proxy network element; wherein the non-zero IPv4 address is temporarily configured by the interworking proxy network element Assigned, it can be generated randomly or it can be generated according to a specific algorithm.

912. The access gateway/evolved packet data gateway acts as a DHCP relay, and forwards the DHCPv4 discovery message sent by the user terminal to the serving gateway. The serving gateway forwards the DHCPv4 discovery message to the interworking proxy network element.

913. The interworking proxy network element acts as a DHCP relay, and forwards a DHCPv4 discovery message sent by the serving gateway to the data gateway, where the DHCPv4 message carries an all-zero address request option.

914. The data gateway functions as a DHCP server, and sends a DHCPv4 providing message to the interworking proxy network element, where the DHCPv4 providing message carries an IPv4 address and other settings allocated for the user terminal. The interworking proxy network element forwards the DHCPv4 providing message to the serving gateway; the serving gateway forwards the message to the access gateway/evolved packet data gateway; after receiving the DHCPv4 providing message, the serving gateway/access gateway/evolved packet data gateway If the IPv4 address carried in the DHCPv4 providing message is different from the IPv4 address carried in the message sent by the interworking proxy network element in step 906, step 907 or step 911, the serving gateway/access gateway/evolved packet data gateway is stored. The DHCPv4 provides an IPv4 address carried in the message, and updates the binding. Access gateway/evolved packet data gateway forwarding said DHCPv4 provides a message to the user terminal, whereby the user terminal obtains an IPv4 address.

In the subsequent process, the interworking proxy network element will act as a DHCP relay to handle DHCP-related processes. In addition, since there may be no serving gateway in the network in the case of non-3GPP access, signaling transmission between the interworking proxy network element and the access gateway/evolved packet data gateway in this embodiment does not need to be performed. The serving gateway performs forwarding; for example, step 902 and step 903 in FIG. 9 may be merged into the same process, and step 906 and step 907 may be merged into the same process, thereby directly establishing the interworking proxy network element and the access gateway/evolving Binding between packet data gateways.

The address allocation method provided in this embodiment is to establish the access gateway/evolved packet data gateway by transmitting the non-zero IPv4 address temporarily allocated by the interworking proxy network element to the access gateway/evolved packet data gateway. Binding with the interworking proxy network element, so that the user terminal can attach, establish a PDN connection or activate a PDP context to perform a corresponding service at a roaming/visiting location; and then obtain an IPv4 address assigned to the user terminal through a normal process. .

Example 8:

Corresponding to the above Embodiment 2 to Embodiment 7, this embodiment provides an address allocation apparatus. As shown in FIG. 10, the address allocation apparatus includes:

The requesting unit 101 is configured to send a request message to the data gateway to request an IPv4 address of the user terminal;

The receiving unit 102 is configured to receive a response message sent by the data gateway.

The sending unit 103 is configured to send a proxy binding acknowledgement message to the serving gateway or the access node, where the proxy binding acknowledgement message carries an IPv4 address, where the IPv4 address is carried by the data gateway in the response message. The IPv4 address of the user terminal or the IPv4 address is temporarily allocated by the address distribution device.

For the above address allocation device, the following three implementation manners are provided in this embodiment: Method 1: In the address allocation device, the requesting unit 101 is specifically configured to send a DHCPv4 discovery message to the data gateway;

The receiving unit 102 is specifically configured to receive a DHCPv4 providing message sent by the data gateway, where the IPv4 address of the user terminal is carried;

The proxy binding acknowledgement message sent by the sending unit 103 carries the IPv4 address of the user terminal.

Method 2:

In the address allocation device, the requesting unit 101 is specifically configured to send a setup session request message to the data gateway, where the setup session request message carries a protocol configuration option, to indicate that the IP address is allocated by means other than DHCPv4;

The receiving unit 102 is specifically configured to receive a setup session response message sent by the data gateway, where the IPv4 address of the user terminal is carried;

Method three:

In the address allocation device, the requesting unit 101 is specifically configured to send a setup session request message to the data gateway;

The receiving unit 102 is specifically configured to receive a setup session response message sent by the data gateway, where the IPv4 address of all 0s is carried;

The proxy binding acknowledgement message sent by the sending unit 103 carries a non-zero IPv4 address that is temporarily allocated by the address allocating device.

The address allocation device provided in this embodiment may be the interworking proxy network element mentioned in the foregoing method embodiment.

In this embodiment, the request for acquiring the IPv4 address of the user terminal is initiated to the data gateway by the interworking proxy network element, or the non-zero IPv4 address is temporarily and autonomously allocated by the interworking proxy network element, and then the data gateway is obtained from the data gateway. The IPv4 address of the user terminal or the temporarily assigned IPv4 The address is sent to the serving gateway or the access node, so that the binding between the serving gateway or the access node and the interworking proxy network element is normally established, so that the user terminal can complete the attaching and establishing at the roaming/visiting location.

The PDN connects or activates the PDP context for the corresponding service.

Example 9:

An address allocation system is provided in this embodiment. As shown in FIG. 11, the address allocation system includes an access node 111, an interworking proxy network element 112, and a data gateway 113. The interworking proxy network element 112 is responsible for accessing. Protocol conversion between node 111 and data gateway 113. specifically,

The interworking proxy network element 112 is configured to send a request message to the data gateway 113 to request an IPv4 address of the user terminal.

The data gateway 113 is configured to provide an IPv4 address to the interworking proxy network element 112 according to the request message, where the IPv4 address may be an IPv4 address allocated to the user terminal or an all-zero IPv4 address, and the The IPv4 address is sent to the interworking proxy network element 112 by using a response message. The interworking proxy network element 112 is further configured to send a proxy binding acknowledgement message to the access node 111, where the proxy binding acknowledgement message carries IPv4. Address, the IPv4 address is an IPv4 address of the user terminal carried in the response message by the data gateway 113, or the IPv4 address is an IPv4 address temporarily allocated by the interworking proxy network element 112; specifically, if the interworking The IPv4 address received by the proxy network element 112 is an IPv4 address assigned to the user terminal, and the interworking proxy network element 112 carries the IPv4 address assigned to the user terminal in the proxy binding acknowledgement message and sends the access to the access. The node 111; if the IPv4 address received by the interworking proxy network element 112 is all 0s, the interworking proxy network element 112 temporarily allocates a non-zero IPv4 address carried in the proxy binding acknowledgment message sent to the access node 111.

In addition, in some scenarios of the 3GPP access network or non-3GPP access, the interworking proxy network element and the access node may further include a service gateway 114;

The serving gateway 114 is configured to receive the proxy binding acknowledgement message sent by the interworking proxy network element 112, and then forward the proxy binding acknowledgement message to the access node 111, or to the access node. 111 sends a setup session response message. The access node 111 may be a mobility management network element in a network that is accessed by the 3GPP, and the access node 111 may be an access gateway or an evolved packet data in a network that is not accessed by the 3GPP. Gateway.

The address allocation system provided in this embodiment first initiates a request for acquiring an IPv4 address of the terminal to the data gateway through the interworking proxy network element, or autonomously temporarily allocates a non-zero IPv4 address by the interworking proxy network element, and then The IPv4 address obtained by the data gateway or the temporarily assigned IPv4 address is sent to the serving gateway or the access node, so that the binding between the serving gateway or the access node and the interworking proxy network element is normally established, so that the user terminal can roam. Complete/attach the attachment, establish a PDN connection, or activate the PDP context for the corresponding service.

Through the description of the above embodiments, those skilled in the art can clearly understand that the present invention can be implemented by means of software plus a necessary hardware platform, and of course, can also be implemented entirely by hardware. Based on such understanding, all or part of the technical solution of the present invention contributing to the background art may be embodied in the form of a software product, which may be stored in a storage medium such as a ROM/RAM, a magnetic disk, an optical disk, or the like. A number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform the methods described in various embodiments of the present invention or portions of the embodiments.

The above is only the specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any change or replacement that can be easily conceived by those skilled in the art within the technical scope of the present invention is All should be covered by the scope of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

Claim

An address allocation method, comprising:

The address allocation method according to claim 1, wherein the request message is a dynamic host configuration protocol DHCPv4 discovery message;

The response message is a DHCPv4 message, where the IPv4 address of the user terminal is carried, and the proxy binding acknowledgement message carries the IPv4 address of the user terminal.

The address allocation method according to claim 1, wherein the request message is a setup session request message, where the setup session request message carries a protocol configuration option, to indicate that the IPv4 is allocated by means other than DHCPv4. Address

The response message is a setup session response message, where the IPv4 address of the user terminal is carried, and the proxy binding acknowledgement message carries an IPv4 address of the user terminal.

The address allocation method according to claim 1, wherein the request message is a session establishment request message;

The response message is a setup session response message, which carries an all-zero IPv4 address. The proxy binding acknowledgement message carries a non-zero IPv4 address temporarily allocated by the interworking proxy network element.

The address allocation method according to claim 1, further comprising: after the serving gateway or the access node receives the proxy binding acknowledgement message, establishing or updating the IPv4 address according to the IPv4 address; Binding between the serving gateway or access node and the interworking proxy network element.

6. An address allocation apparatus, comprising:

a requesting unit, configured to send a request message to the data gateway to request an IPv4 address of the user terminal, and a receiving unit, configured to receive a response message sent by the data gateway; a sending unit, configured to send a proxy binding acknowledgement message to the serving gateway or the access node, where the proxy binding acknowledgement message carries an IPv4 address, where the IPv4 address is carried by the data gateway in the response message The IPv4 address of the user terminal or the IPv4 address is temporarily allocated by the address distribution device.

7. The address distribution device according to claim 6, wherein:

The requesting unit is specifically configured to send a DHCPv4 discovery message to the data gateway;

The receiving unit is specifically configured to receive a DHCPv4 providing message sent by the data gateway, where the IPv4 address of the user terminal is carried;

The proxy binding acknowledgement message sent by the sending unit carries the IPv4 address of the user terminal.

8. The address distribution device according to claim 6, wherein:

The requesting unit is specifically configured to send a setup session request message to the data gateway, where the setup session request message carries a protocol configuration option, to indicate that the IPv4 address is allocated by means other than DHCPv4;

The receiving unit is specifically configured to receive a setup session response message sent by the data gateway, where the IPv4 address of the user terminal is carried;

9. The address distribution device according to claim 6, wherein:

The requesting unit is specifically configured to send a setup session request message to the data gateway;

The receiving unit is specifically configured to receive a setup session response message sent by the data gateway, where the IPv4 address of all 0s is carried;

The proxy binding acknowledgement message sent by the sending unit carries a non-zero IPv4 address temporarily allocated by the address allocating device.

An address allocation system, comprising: an interworking proxy network element, an access node, and a data gateway; wherein

The interworking proxy network element is configured to send a request message to the data gateway to request an IPv4 address of the user terminal; The data gateway is configured to provide an IPv4 address to the interworking proxy network element according to the request message, where the IPv4 address is an IPv4 address of the user terminal or an IPv4 address of all 0s, and the IPv4 address is passed the response message. Sending to the interworking proxy network element;

The interworking proxy network element is further configured to send a proxy binding acknowledgement message to the access node, where the proxy binding acknowledgement message carries an IPv4 address, and the IPv4 address is carried by the data gateway in the response message. The IPv4 address of the user terminal or the IPv4 address is an IPv4 address temporarily allocated by the interworking proxy network element.

11. The address allocation system according to claim 10, further comprising: a service gateway between the interworking proxy network element and the access node; and then forwarding the proxy binding acknowledgement message to the Accessing the node, or sending a setup session response message to the access node.

The address allocation system according to claim 10 or 11, wherein the access node is an access gateway, or an evolved packet data gateway, or a mobility management network element.