WO2009117891A1

WO2009117891A1 - A register method and equipment of packet data network connection

Info

Publication number: WO2009117891A1
Application number: PCT/CN2008/073464
Authority: WO
Inventors: 吴问付; 胡伟华
Original assignee: 华为技术有限公司
Priority date: 2008-03-26
Filing date: 2008-12-11
Publication date: 2009-10-01
Also published as: CN101547142B; CN101547142A

Abstract

A register method of packet data network PDN connection, includes: distributing PDN connection identifier for the PDN connection request initiated by the user equipment; transmitting a PDN connection register information including the PDN connection identifier, access point name APN and packet data network gateway PGW identifier to a home user server HSS. So, the information, which is used for the different PDN connections and is composed of APN, PGW identifier and PDN identifier, is unique, even if the same APN, the same PGW identifier corresponds to many of PDN connections, the records memorized in HSS are many, so as to avoid the problem that only one PDN connection is established, but the other PDN connection is lost existed in the prior art. An establishing method and all kinds of equipments of PDN connection are also provided.

Description

Method and device for registering packet data network connection This application claims to be submitted to the Chinese Patent Office on March 26, 2008, the application number is 200810086366.X, and the invention name is "Registration Method and Device of Packet Data Network Connection" and in 2008 6 The priority of the Chinese Patent Application No. 200810110181.8, entitled "Registering Method and Apparatus for Packet Data Network Connections", is incorporated herein by reference. Technical field

The embodiments of the present invention relate to the field of network technologies, and in particular, to a method and a device for registering a packet data network (PDN) connection. Background technique

The 3rd Generation Partner Project (3GPP) network refers to some networks defined by the 3GPP organization, including the traditional General Packet Radio Service (GPRS) network and Universal Mobile Communication System (Universal Mobile) Telecommunications System (UMTS) network, also includes 3GPP Long Time Evolution (LTE) network; non-3GPP network (non-3GPP) refers to some access networks defined by non-3GPP organizations, such as wireless local area network (Wireless Local Area Network, WLAN), Worldwide Interoperability for Microwave Access (Wimax), Code Division Multiple Access (CDMA) and other networks.

In order to have an understanding of the 3GPP LTE network, the E-UTRAN network architecture is first introduced in conjunction with FIG. In Figure 1, E-UTRAN is used to implement all functions related to the evolved network; Mobility Management Entity (ΜΜΕ) is mainly responsible for mobility management and session management, including user context and mobile state management, and assigning user identity. Temporary identification, etc.; Serving Gateway (SGW) is a user plane entity that UE (User Equipment, UE) accesses the core network, terminates the interface of E-UTRAN; Packet Data Network-Gateway (PGW) It is a user plane anchor network element between the 3GPP network and the non-3GPP network, and terminates the interface with the external packet data network (PDN); the interface between the SGW and the PGW can use the GPRS tunneling protocol (GPRS Tunneling Protocol) , GTP ) or Proxy Mobile Internet Protocol ( PMIP ); User Subscriber Server ( HSS ) is used to store user subscription information; Policy and Charging Rule Function ( PCRF) ) for policy control decisions and flow accounting control functions; authentication, authorization and accounting servers

(Authentication, Authorization and Accounting Server, AAA Server) is used to perform access authentication, authorization, and accounting functions for the UE; service GPRS support node

(Serving GPRS switching support node, SGSN) is used to implement functions such as routing and forwarding, mobility management and user information storage in GPRS networks; UMTS Terrestrial Radio Access Network (UTRAN), GSM/EDGE radio access GSM/EDGE Radio Access Network (GERAN) is used to implement all wireless related functions in existing GPRS/UMTS networks. It should be noted that the current 3GPP Long Time Evolution (LTE) is in the research stage. FIG. 1 only shows a possible LTE network diagram.

Those skilled in the art understand that a PDN connection to this PDN needs to be established before the UE accesses a particular PDN (some protocol documents are also referred to as data connections). For example, a data channel is established between the UE and the PGW, and data between the UE and the PDN is transmitted on the data channel.

In order to achieve uninterrupted service when the UE switches between the 3GPP network and the non-3GPP network, the target network needs to know the PDN connection information established by the UE in the source network. When the UE establishes a PDN connection in the source network, the access point name (APN) and the PGW address information required for the PDN connection are sent to the HSS for storage. The target network obtains these registration information from the HSS, initiates a PDN establishment procedure based on the registration information, and completes the PDN connection establishment between the UE and the PDN in the target network.

The inventors found in the process of implementing the present invention that: the existing mechanisms are all handled for one APN-PDN connection, and for an APN, there is only one record kept in the HSS. When switching between a 3GPP network and a non-3GPP network, only one PDN connection can be established in one APN of the target network. But if you can create multiple under one APN PDN connections, processing of PDN connection establishment, and existing mechanisms for handling at handover have not been addressed. Summary of the invention

In view of this, the embodiment of the present invention provides a method for registering a PDN connection, so as to solve the problem that the next APN has only one record in the HSS, and the same APN and the same PGW are used in multiple PDN connections, in 3GPP. When switching between a network and a non-3GPP network, only one PDN connection can be established in the target network, causing other PDN connections to be lost.

The method for registering a PDN connection provided by the embodiment of the present invention is implemented by: allocating a PDN connection identifier for a PDN connection request initiated by a user equipment UE; and transmitting, by the home subscriber server HSS, the PDN connection identifier and an access point name APN and a packet The PDN connection registration information identified by the data network gateway PGW; or, the PDN connection registration information including the PDN connection identifier and the packet data network gateway PGW identifier is sent to the home subscriber server HSS.

At the same time, the embodiments of the present invention also provide various devices in the PDN connection registration:

A communication terminal, comprising: an identifier configuration unit, configured to allocate a PDN connection identifier for a PDN connection, where the PDN connection identifier is used to identify the PDN connection; and a PDN request unit, configured to send an attach message that includes the PDN connection identifier Or a PDN connection request message.

A mobility management network element of a 3GPP network, including a message receiving unit for receiving an attach request message or a PDN connection request message from a UE, further comprising: an identifier configuration unit, configured to allocate a PDN connection identifier for the PDN connection; and a PDN request unit And configured to send a create default bearer request message that includes the PDN connection identifier.

A non-3GPP network element, including a message receiving unit for receiving a PDN connection request message from a UE, further comprising: an identifier configuration unit, configured to allocate a PDN connection identifier for the PDN connection, where the PDN connection identifier is used to identify the PDN a PDN request unit, configured to send a proxy binding update message that includes the PDN connection identifier.

A packet data network gateway (PGW) includes a message receiving unit for receiving a request for a PDN connection, and further includes: an identifier configuration unit, configured to allocate a PDN connection identifier for the PDN connection, where the PDN connection identifier is used to identify the PDN connection; PDN request reply unit, And is configured to send a reply message that includes the PDN connection identifier.

A home subscriber server HSS, including:

a message receiving unit, configured to receive a message that includes PDN connection identifier information, and a storage unit, configured to store the PDN connection identifier information.

Thus, for different PDN connections, the information of the APN, PGW identity and PDN connection identity used is unique, that is, the APN, PGW identity and PDN connection identity can uniquely identify a PDN connection, even for the same The APN and the same PGW ID correspond to multiple PDN connections. The records stored in the HSS are also multiple, so that the existing solution can be saved and only one record can be saved in the HSS, resulting in only the target network can be established. A PDN connection and other PDN connections will be lost.

In addition, the embodiment of the present invention further provides a method for allocating an IP address of a PDN connection, so as to solve the problem that the PGW processing abnormality occurs when performing network switching in the prior art. That is, in the scenario of a single APN multi-PDN connection, the existing scheme PGW locates a wrong PDN connection when performing network handover, thereby assigning a wrong IP address to the requested PDN connection, resulting in all services on the requested PDN connection. An interruption will occur, affecting the user's experience.

A method for allocating an IP address of a PDN connection, comprising: after receiving a message requesting to establish a PDN connection, the PGW locates a PDN connection established according to the PDN connection identifier information carried in the message; the PGW is a PDN connection established by the request Allocating an IP address in the established PDN connection.

In addition, the embodiment of the present invention further provides an IP address device for allocating a PDN connection, which is located on the PGW side, and includes:

a message receiving unit, configured to receive a message that includes a PDN connection identifier and an APN request to establish a PDN connection, or to receive a message that includes a PDN connection identifier to establish a PDN connection;

a query unit, configured to establish, according to the PDN connection identifier and the APN, a PDN connection established according to the PDN connection identifier;

The IP address control unit is configured to allocate an IP address in the established PDN connection for the PDN connection that is requested to be established.

Use the IP address method and PGW device to maintain the PDN connection, when the PGW passes the PDN The connection identifier and the APN or PGW can be found through the PDN connection, and the existing PDN connection IP address can be found. The UE will not be switched to the wrong destination IP address to ensure that the PGW processing is normal.

In addition, the embodiment of the present invention further provides a method for establishing a PDN connection, where the target network establishes a PDN connection in the source network of the UE to solve the problem that the existing solution uses the same APN and the same PGW when multiple PDN connections are used. In the target network, only one PDN connection can be established, resulting in the loss of other PDN connections.

A method for establishing a PDN connection, comprising: acquiring a PDN connection identifier, an APN, and a PGW identification information used by a UE, or acquiring a PDN connection identifier and PGW identification information used by the UE; and determining, according to the PDN connection identifier, the APN, and the PGW identification information. Or establishing a PDN connection according to the PDN connection identifier and the PGW identification information.

In addition, the embodiment of the present invention further provides a device for establishing a PDN connection, including: a device for establishing a PDN connection, located at a target 3GPP mobility management network element side, where: an information acquiring unit, configured to acquire a PDN connection identifier used by the UE, The APN and the PGW identify the information, or obtain the PDN connection identifier and the PGW identification information used by the UE. The PDN request unit is configured to send a create default bearer request message that includes the PDN connection identifier.

A device for establishing a PDN connection, located at a target non-3GPP network element side, includes: an information acquiring unit, configured to acquire, from an HSS, a PDN connection identifier, an APN, and a PGW identification information used by the UE, or obtain a PDN connection identifier used by the UE, and PGW identification information; a PDN requesting unit, configured to send a proxy binding update message that includes the PDN connection identifier.

A device for establishing a PDN connection, located at the UE side, includes: an information storage unit, configured to store PDN connection identifiers, APNs, and PGW identification information used by the UE, or obtain PDN connection identifiers and PGW identification information used by the UE; And a unit, configured to send a message that includes the PDN connection identifier to establish a PDN connection.

It can be seen that the PDN connection establishment method and the PGW and the UE device can directly establish a PDN connection by acquiring the PDN connection information used by the UE, and uniquely indicate a PDN connection through the PDN connection identifier, thereby solving the existing scheme and using multiple PDN connections. When the same APN and the same PGW, only one PDN connection can be established in the target network, causing other PDN connections to be lost, thus ensuring complete and continuous services. In addition, the embodiment of the present invention further provides a method for processing a PDN connection, so as to solve the problem that the PDN connection cannot be located when multiple PDN connections use the same APN and the same PGW in the prior art.

A packet data network PDN connection processing method, including:

Receiving a PDN connection request initiated by the UE of the user equipment;

A PDN connection identifier is assigned to the PDN connection request, and the PDN connection identifier is used to identify the PDN connection.

Therefore, for different PDN connections, a PDN connection identifier can be used to locate a PDN connection, so that when the UE switches from the source network to the target network, the PDN connection in the source network can be located according to the PDN connection identifier, so that The target network establishes multiple PDN connections and uses the IP address used in the PDN connection in the source network to ensure complete and continuous services. DRAWINGS

1 is a schematic diagram of a prior art E-UTRAN architecture;

2 is a flow chart of a first method of the present invention;

3 is a flow chart 1 of Embodiment 1 of the first method of the present invention;

Figure 4 is a flow chart 2 of the first embodiment of the first method of the present invention;

Figure 5 is a flow chart 1 of the second embodiment of the first method of the present invention;

Figure 6 is a flow chart 2 of the second embodiment of the first method of the present invention;

Figure 7 is a flow chart 3 of the second embodiment of the first method of the present invention;

Figure 8 is a flow chart of a second method of the present invention;

Figure 9 is a flow chart 1 of a second embodiment of the second method of the present invention;

Figure 10 is a flow chart 2 of a second embodiment of the second method of the present invention;

Figure 11 is a flow chart 3 of a second embodiment of the second method of the present invention;

Figure 12 is a flow chart 1 of the second embodiment of the second method of the present invention;

Figure 13 is a second embodiment of the second method of the second embodiment of the present invention 2;

Figure 14 is a flow chart 3 of the second embodiment of the second method of the present invention;

FIG. 15 is a flowchart 4 of Embodiment 2 of the second method of the present invention. detailed description

The first method provided by the embodiment of the present invention is a registration method of a PDN connection. Referring to FIG. 2, the following steps are included:

S201: assign a PDN connection identifier to the PDN connection request initiated by the UE.

S202: Send PDN connection registration information including a PDN connection identifier, an APN, and a PGW address to the HSS, or send PDN connection registration information including the PDN connection identifier and a PGW address to the HSS, where the PDN connection identifier is used to identify a PDN connection.

Therefore, for different PDN connections, the information of the APN, the PGW address, and the PDN connection identifier used by the PDN connection or the PDN connection identifier and the PGW address information used by the PDN connection are unique, that is, the APN, the PGW address, and the PDN connection identifier or The PDN connection identifier and the PGW address information can uniquely identify a PDN connection. Even if the same APN and the same PGW address correspond to multiple PDN connections, the records stored in the HSS are multiple, thereby avoiding the existing solution. Only one record can be saved in the HSS, resulting in the problem that only one PDN connection can be established in the target network and other PDN connections will be lost.

The first method will be described in detail below with reference to the accompanying drawings.

First, the first method embodiment 1 is introduced: a registration method of a PDN connection in a 3GPP network.

The UE may request to establish a PDN connection by requesting access to the 3GPP network's attach request message or after accessing the 3GPP network through a non-default PDN connection request message. The following two cases are introduced separately.

Referring to FIG. 3, it is a flow chart 1 of the first method embodiment.

In the flowchart 1 of the first method embodiment, when the UE accesses the 3GPP network, the mobility management network element obtains the PDN connection identifier used by the PDN connection in the establishment procedure of the PDN connection, and the mobility management network element uses the PDN. The APN, PGW address, and PDN connection identifier used by the connection are registered to the HSS or the mobility management network element registers the PDN GW address and the PDN connection identifier used by this PDN connection to the HSS.

Figure 3 includes:

S301: The UE sends an attach request (Attach Request) message to the mobility management network element.

For the GERAN/UTRAN network, the mobility management network element refers to the SGSN, E-UTRAN network, mobility management network element refers to MME.

S302: Perform an authentication process between the UE, the mobility management network element, and the HSS.

S303: Performing a location update and insertion contract data flow between the mobility management network element and the HSS, registering the address of the mobility management network element into the HSS, and the HSS inserts the subscription data of the UE into the mobility management network element.

S304: The mobility management network element selects a PGW according to the default APN used by the UE, and sends a default bearer request message to the SGW to create a default PDN connection, where the message carries the selected PGW address and APN information.

Wherein, if the PDN connection identifier is allocated by the mobility management network element, the mobility management network element assigns a PDN Connectivity ID (PDN Connectivity ID) to the default PDN connection in this step to identify the PDN connection, and then creates the missing The provincial bearer request message is carried to the SGW. The PDN connection identifier may be unique within a UE range or may be unique within the APN range used by the UE.

S305: The SGW sends a create default bearer request message or a proxy binding update message to the selected PGW, where the message carries the APN information.

If the interface protocol between the SGW and the PGW uses the GTP protocol, the Create Default Bearer Request message is used; if the interface protocol between the SGW and the PGW uses the PMIP protocol, the proxy binding update message is used. If the mobility management network element carries the PDN connection identifier to the SGW, the SGW carries this information to the PGW.

S306: The PGW returns a default bearer response or a proxy binding acknowledgement message to the SGW. If the PGW allocates an IP address for the PDN connection, the message carries the IP address used by the PDN connection. If the PDN connection ID is assigned by the PGW, the PGW assigns a PDN connection identifier to this PDN connection. If the PGW assigns a PDN connection identifier to the PDN connection, the PGW carries the assigned PDN connection identifier in the Create Default Bearer Response or Proxy Binding Acknowledgement message. The PDN connection identifier may be unique within a UE range or may be unique within the APN range used by the UE.

S307: The SGW returns a default bearer response message to the mobility management network element. If the PGW carries the PDN connection identifier information to the SGW, the SGW carries the PDN connection identifier.

S308: The mobility management network element attaches an attach message to the UE, and the message carries the message. PDN connection identifier used by the PDN connection;

S309: The mobility management network element sends an update location request message to the HSS, where the message carries the APN, the PGW address, the PDN connection identifier information of the default PDN connection used by the UE, or the PGW address of the default PDN connection used by the UE in the message. PDN connection identification information;

S310: The HSS saves the APN, the PGW address, and the PDN connection identifier information used by the UE, or the HSS saves the PGW address and the PDN connection identifier information used by the UE, and returns a location update response message to the mobility management network element.

It can be seen that in the flowchart 1 of the first method embodiment, the PDN connection identifier can be allocated to the PDN connection by the mobility management network element or the PGW.

If the SGW allocates a PDN connection identifier to the PDN connection, the SGW allocates a PDN connection identifier to the PDN connection when the default management bearer request message is sent by the mobility management network element, and then creates a default bearer request message or a proxy tie. The PDN connection identifier is carried in the update message to the PGW, and the PDN connection identifier is carried in the default bearer response message to the mobility management network element.

Referring to FIG. 4, it is a flow chart 2 of the first method embodiment.

In the flow chart 2 of the first method embodiment, when the UE requests the PDN connection, the mobility management network element obtains the PDN connection identifier used by the PDN connection in the establishment procedure of the PDN connection, and the mobility management network element uses the PDN. The APN, PGW address, PDN connection identifier, or mobility management network element used by the connection registers the PDN GW address and PDN connection identifier used by this PDN connection to the HSS.

Figure 4 includes:

S401: The UE sends a PDN connection request message to the mobility management network element to request to establish a PDN connection, where the message carries the APN used by the PDN;

If the PDN connection identifier is assigned by the UE, the UE assigns a PDN connection identifier to the PDN connection in this step, and then carries the PDN connection request message to the mobility management network element. The PDN connection identifier may be unique within a UE range or may be unique within the APN range used by the UE.

For the GERAN/UTRAN network, the mobility management network element is the SGSN; for the E-UTRAN network, the mobility management network element is the MME. S402: The mobility management network element selects a PGW according to the APN carried by the UE, and sends and sends a default bearer request message to the SGW to create a PDN connection, where the message carries the selected PGW address and APN information. If the UE carries the PDN connection identifier in the PDN connection request message, the mobility management network element carries the PDN connection identifier in the Create Default Bearer Request message. If the UE does not carry the PDN connection identifier in the PDN connection request message and the PDN connection identifier is allocated by the mobility management network element, the mobility management network element assigns a PDN connection identifier to the PDN connection, and the mobility management network element creates a default. The bearer request message carries the PDN connection identifier. The PDN connection identifier may be unique within a UE range or may be unique within the APN range used by the UE.

S403: The SGW sends a create default bearer request message or a proxy binding update message to the selected PGW, where the message carries the APN information.

If the mobility management network element carries the PDN connection identifier to the SGW, the SGW carries the information to the PGW.

If the interface protocol between the SGW and the PGW uses the GTP protocol, the Create Default Bearer Request message is used; if the interface protocol between the SGW and the PGW uses the PMIP protocol, the proxy binding update message is used.

S404: The PGW returns a default bearer response or a proxy binding acknowledgement message to the SGW. If the PGW allocates an IP address for the PDN connection, the message carries the IP address used by the PDN connection.

If the PDN connection identifier is assigned by the PGW, the PGW assigns a PDN connection identifier to this PDN connection. The PDN connection identifier may be unique within a UE range or may be unique within the APN range used by the UE.

If the PGW assigns a PDN connection identifier to the PDN connection, the PGW carries the assigned PDN connection identifier in the Create Default Bearer Response or Proxy Binding Acknowledgement message.

S405: The SGW returns a default bearer response message to the mobility management network element. If the PGW carries the PDN connection identifier information to the SGW, the SGW carries the PDN connection identifier.

S406: The mobility management network element returns a PDN connection accept message to the UE.

If the PDN connection identifier is assigned by the mobility management network element or the PGW, the mobility management network element carries the PDN connection identification information to the UE. S407: The mobility management network element sends an update location request message to the HSS, where the message carries the APN, the PGW address, the PDN connection identifier information of the default PDN connection used by the UE, or the PGW address of the default PDN connection used by the UE in the message, PDN connection identification information;

S408: The HSS saves the APN, the PGW address, and the PDN connection identifier information used by the UE, or the HSS saves the PGW address and the PDN connection identifier information used by the UE, and returns a location update response message to the mobility management network element.

It can be seen that in the flow chart 2 of the first method embodiment, the PDN connection identifier can be allocated by the UE, the mobility management network element or the PGW for the PDN connection.

The first method embodiment 2 is described below: The registration method of the PDN connection in the non-3GPP network.

The UE may request to establish a PDN connection by requesting to access an attach request message of the non-3GPP network, or after accessing the 3GPP network, and then establishing a PDN connection by using a PDN connection request message, where The non-3GPP network element sends a proxy binding update message to the PGW and the UE directly sends a binding update message to the PGW to implement a PDN connection request. The following three cases are introduced separately.

Referring to FIG. 5, it is a flow chart 1 of the first method embodiment.

In the flowchart 1 of the first method embodiment, when the UE accesses the non-3GPP network, the PGW connects the PDN used by the PDN connection in the PDN connection establishment procedure, the APN, the PGW address, the PDN connection identifier, or the PGW. The PDN GW address and PDN connection identifier used are registered to the HSS.

Figure 5 includes:

S501: performing authentication and authentication between the UE, the non-3 GPP GW, the AAA server, and the HSS;

For WLAN systems, non-3GPP GW (also known as MAG (mobile) The access gateway (Mobile Access Gateway) is an Evolved Packet Data Gateway (EPDG); for the Wimax system, the non-3 GPP GW is an Access Service Network Gateway (ASN GW); For CDMA systems, the non-3 GPP GW is an Access Gateway (AGW).

S502: The UE sends a layer 3 attach request message to the non-3GPP GW.

S503: If the PMIP protocol is used in the non-3GPP network, the non-3GPP GW selects the PGW according to the default APN used by the UE, and then sends a proxy binding update message to the selected PGW to establish a default PDN connection, where the message carries the APN information; If the PDN connection identifier is assigned by the non-3GPP GW, the non-3GPP GW assigns a PDN connection identifier to the PDN connection in this step, and then carries the PDN in the proxy binding update message; the PDN connection identifier may be in a UE range. It is unique within the scope of the APN used by the UE.

S504: If the non-3GPP GW does not assign a PDN connection identifier to the PDN connection, the PGW allocates a PDN connection identifier for the PDN connection. The PDN connection identifier can be unique within a UE range or within the APN range used by the UE.

The PGW sends an update PGW address message to the AAA server, and the AAA Server sends an update PGW address message to the HSS to register the information of the PDN connection to the HSS. The message carries the APN, the PGW address, the PDN connection identifier, or the message used by the PDN connection. Carrying the PDN GW address and PDN connection identifier used by this PDN connection;

S505: The PGW returns a proxy binding acknowledgement message to the non-3GPP GW.

If the PGW assigns a PDN connection identifier to the PDN connection, the PGW carries the PDN connection identifier in the proxy binding acknowledgement message.

S506: The non-3GPP GW sends a layer 3 attach accept message to the UE, where the message carries the PDN connection identifier.

It can be seen that, in the flowchart 1 of the first method embodiment, the PDN connection identifier can be allocated by the non-3GPP network element or the PGW for the PDN connection.

Referring to FIG. 6, it is a flow chart 2 of the first method embodiment.

In the second method and flowchart 2 of the second method, when the UE accesses the non-3GPP network, the PGW connects the APN and the PGW used by the PDN in the establishment procedure of the PDN connection. The address, PDN connection identifier or PGW registers the PDN GW address and PDN connection identifier used by this PDN connection to the HSS. And the first method embodiment 2 in the flow chart 1

The non-3GPP network element sends a proxy binding update message to the PGW. In FIG. 6, the UE directly sends a binding update message to the PGW.

Figure 6 includes:

S601: performing authentication and authentication between the UE, the non-3 GPP GW, the AAA server, and the HSS;

S602: The UE sends a layer 3 attach request message to the non-3GPP GW.

S603: If the CMIP protocol is used in the non-3GPP network, the non-3GPP GW returns to the layer 3 to accept the message to the UE;

S604: If the CMIP protocol is used in the non-3GPP network, the UE sends a binding update message to the PGW to establish a default PDN connection, where the message carries the APN information. If the PDN connection identifier is allocated by the UE, the UE is the PDN in this step. The connection allocates a PDN connection identifier and then carries it to the PGW in the binding update message; the PDN connection identifier may be unique within one UE range, or may be unique within the APN range used by the UE.

S605: If the PDN connection identifier is allocated by the PGW, the PGW allocates a PDN connection identifier for the PDN connection. The PDN connection identifier may be unique within a UE range or may be unique within the APN range used by the UE.

The PGW sends an update PGW address message to the AAA server, and the AAA Server sends an update PGW address message to the HSS to register the information of the PDN connection to the HSS, where the message carries the APN, PGW address, PDN connection identifier or message used by the PDN connection. The PDN GW address and PDN connection identifier used for carrying this PDN connection.

S606: The PGW sends a binding acknowledgement message to the UE.

If the PGW assigns a PDN connection identifier to the PDN connection, the PGW carries the PDN connection identifier in the binding acknowledgement message.

It can be seen that in the flowchart 2 of the second method embodiment, the PDN connection identifier can be allocated by the UE or the PGW for the PDN connection.

Referring to FIG. 7, it is a flow chart 3 of the first method embodiment.

In the flowchart 3 of the first method embodiment, when the UE requests the PDN connection in the non-3GPP network, the PGW uses the APN, the PGW address, and the PDN connection identifier used by the PDN connection. Or the PGW registers the PDN GW address and PDN connection identifier used by this PDN connection to the HSS.

Figure 7 includes:

S701: If the PMIP protocol is used in the non-3GPP network, the UE sends a PDN connection request message to the non-3GPP GW, where the message carries the APN information used by the PDN connection; if the PDN connection identifier is allocated by the UE, the UE is in this step. A PDN connection identifier is allocated to the PDN connection, and then carried in the PDN connection request message to the non-3GPP GW; the PDN connection identifier may be unique within one UE range, or may be unique within the APN range used by the UE.

S702: The non-3GPP GW selects the PGW according to the APN, and then sends a proxy binding update message to the selected PGW to establish a PDN connection.

If the UE carries the PDN connection identifier in the PDN connection request message, the non-3GPP GW carries the PDN connection identifier in the proxy binding update message.

If the UE does not carry the PDN connection identifier in the PDN connection request message and the PDN connection identifier is allocated by the non-3GPP GW, the non-3GPP GW allocates a PDN connection identifier for the PDN connection, and the non-3GPP GW in the proxy binding update message Carry the PDN connection identifier. The PDN connection identifier may be unique within a UE range or may be unique within the APN range used by the UE.

S703: If the PDN connection identifier is allocated by the PGW, the PGW allocates a PDN connection identifier for the PDN connection. The PDN connection identifier may be unique within a UE range or may be unique within the APN range used by the UE.

The PGW sends an update PGW address message to the AAA server, and the AAA Server sends an update PGW address message to the HSS to register the information of the PDN connection to the HSS, where the message carries the APN, PGW address, PDN connection identifier or message used by the PDN connection. Carrying the PDN GW address and PDN connection identifier used by this PDN connection;

S704: The PGW returns a proxy binding acknowledgement message to the non-3GPP GW.

If the PGW assigns a PDN connection identifier to the PDN connection, the PGW carries the PDN connection identifier in the proxy binding update message.

S705: The non-3GPP GW sends a PDN connection accept message to the UE.

Non-3GPP if the PDN connection identifier is assigned by a non-3GPP GW or PGW The GW carries the PDN connection identifier in the PDN connection accept message.

It can be seen that in the flowchart 3 of the second embodiment, the PDN connection identifier can be allocated by the UE, the non-3GPP network element or the PGW for the PDN connection.

The second method provided by the embodiment of the present invention is to allocate an IP address of a PDN connection and a method for establishing a PDN connection in the target network.

Referring to Figure 8, assigning an IP address for a PDN connection includes the following steps:

S801: After receiving the message requesting to establish a PDN connection, the PGW searches for the IP address of the pre-established PDN connection according to the APN and PDN connection identifier information carried in the message or according to the PDN connection identifier information carried in the message;

S802: The PGW allocates the IP address of the queried PDN connection.

In order to ensure the continuity of the service when the UE switches between the 3GPP network and the non-3GPP network, the IP address in the PDN connection used by the UE after the UE switches to the target network needs to remain unchanged. That is, when the UE switches between the 3GPP network and the non-3GPP network, after the mobility management network element or the non-3GPP GW network element or the UE initiated PDN connection request message to the PGW, the PGW needs to use the PDN connection. The IP address assigned when the source network. For different PDN connections, the PGW assigns different IP addresses to the UE. Therefore, if multiple PDN connections of the UE use the same APN, the APN used by the UE on the PGW has multiple IP addresses. Therefore, when the PGW connects to the APN through the PDN, it can find the existing PDN connection IP address, and will not switch the UE to the wrong destination IP address, ensuring that the PGW processing is normal.

In the meantime, the embodiment of the present invention further provides a method for establishing a PDN connection, including the following steps:

1. Obtain the PDN connection identifier, APN, and PGW address information established by the UE on the source network, or obtain the PDN connection identifier and PGW address information established by the UE on the source network.

2. Establishing a PDN connection in the target network according to the PDN connection identifier, the APN and PGW address information, or according to the PDN connection identifier and the PGW address information.

The PDN connection establishment method and the PGW and the UE device can establish a PDN connection in the target network by using the PDN connection information of the source network, and solve the existing solution when the same APN and the same PGW are used in multiple PDN connections, only in the target network. The problem of establishing a PDN connection and causing other PDN connections to be lost will ensure that the service is complete and continuous.

The second method will be described in detail below with reference to the accompanying drawings. First, the second method embodiment 1 is introduced: a PDN connection establishment method in the process of handover from a non-3GPP network to a 3GPP network.

Referring to FIG. 9, it is a flowchart 1 of the second method embodiment.

In the flowchart 1 of the second method embodiment, when the UE switches from the non-3GPP network to the 3GPP network or the UE needs to handover from the non-3GPP network to the 3GPP network, the MME acquires the PDN connection record used by the UE in the non-3GPP network. For each PDN connection record, the MME initiates a PDN connection establishment procedure, notifies the PDN of the PDN-connected APN, PDN connection identifier, or notifies the PDN GW of the PDN connection identifier of the PDN connection. The PGW locates the PDN connection used by the UE according to the APN and the PDN connection identifier or the PDN GW according to the PDN connection identifier, and keeps the IP address of the PDN connection unchanged.

Figure 9 includes:

S901: The UE accesses in the non-3GPP, and initiates a handover between the non-3GPP network and the 3GPP network.

S902: The UE switches to the 3GPP network, and the UE sends an attach request message to the mobility management network element by using the access network element of the 3GPP network; or the UE needs to switch to the 3GPP network, but the UE also resides in the non-3GPP network, and the UE passes the non- The network element of the 3GPP network sends an attach request message to the mobility management network element;

The UE carries an identifier in the attach request message indicating that the attach request is an attach request caused by the handover. For example, the UE sets the Attach Type cell in the message to Handover Attach.

S903: Perform an authentication process between the UE, the mobility management network element, and the HSS.

S904: Perform a location update and insertion subscription data flow between the mobility management network element and the HSS, register the address of the mobility management network element into the HSS, and the HSS inserts the subscription data of the UE into the mobility management network element.

In this step, the HS S sends the PDN connection information used by the UE in the non-3 GPP network to the mobility management network element, that is, the mobility management network element obtains the APN, PGW address used by the UE in the non-3GPP network, The PDN connection identification information or the mobility management network element obtains the PDN GW address and PDN connection identification information used by the UE in the non-3GPP network.

S905: The mobility management network element identifies that the attach request message of the UE is an attach request caused by the handover, and the mobility management network element obtains, for each acquired APN, PGW address, The PDN connection identifier record or the mobility management network element initiates a PDN connection establishment procedure for each obtained PDN GW address and PDN connection identity record. For each PDN connection establishment procedure, the mobility management network element sends a Create Default Bearer Request message to The SGW, the message carries the PGW address, the APN, the PDN connection identifier in the record, or the PDN GW address and the PDN connection identifier in the record carried in the message;

S906: After receiving the foregoing message, the SGW sends a default bearer request message or a proxy binding update message to the PGW, where the message carries the APN, the PDN connection identifier, or the message carries the PDN connection identifier.

S907: For each PDN connection establishment procedure, the PGW returns a default bearer response or a proxy binding acknowledgement message to the SGW;

After receiving the above message, the PGW locates the PDN connection used by the UE according to the PDN connection identifier according to the APN, the PDN connection identifier, or the PGW, and the PGW keeps the IP address of the PDN connection unchanged, that is, the PGW connects to the PDN. The IP address assigned by the UE in the non-3GPP network is continued to be used without assigning an IP address to this PDN connection.

If the PGW receives the Create Default Bearer Request message or the Proxy Binding Update message carries the APN information without the PDN connection identifier or a new PDN connection identifier (ie, the PDN connection identifier cannot be queried on the PGW), the PGW considers This is a new PDN connection setup request message, and the PGW assigns an IP address to this PDN connection (as described in Figure 3).

S908: For each PDN connection establishment procedure, the SGW returns to create a default bearer response message to the mobility management network element.

S909: The mobility management network element attaches an attach message to the UE.

If the PDN connection initiated by the mobility management network element is established by the UE in the non-3GPP network (ie, the mobility management network element initiates the PDN connection establishment according to the queried record), the mobility management network element does not need to register the PDN connection. Information to the HSS; if the PDN connection initiated by the mobility management network element is that the UE is not built in the non-3GPP network Then, the mobility management network element registers the information of the PDN connection (ie, the APN, the PGW address, and the PDN connection identifier, or the PDN GW address and the PDN connection identifier) to the HSS.

Referring to FIG. 10, it is a flow chart 2 of Embodiment 1 of the second method.

In the flow chart 2 of the second method embodiment, when the UE switches from the non-3GPP network to the 3GPP network or the UE needs to switch from the non-3GPP network to the 3GPP network, the UE obtains the PDN connection record used by the UE in the non-3GPP network. . The UE initiates a PDN connection establishment procedure, and notifies the mobility management network element of the PDN connection APN, the PDN connection identifier, or the PDN connection PDN connection identifier. After receiving the PDN connection setup request message of the UE, the mobility management network element obtains the PGW address information used by the PDN connection according to the APN and PDN connection identifier carried in the message or according to the PDN connection identifier query record carried in the message. The mobility management network element initiates a PDN connection establishment procedure to the queried PGW, and the message carries the APN and PDN connection identification information used by the PDN connection or the PDN connection identification information used by the PDN connection in the message. The PGW locates the PDN connection used by the UE according to the APN and the PDN connection identifier or the PDN GW according to the PDN connection identifier, and keeps the IP address of the PDN connection unchanged.

Figure 10 includes:

S1001: The UE accesses in the non-3GPP, and initiates a handover between the non-3GPP network and the 3GPP network;

S1002: The UE switches to the 3GPP network, and the UE sends an attach request message to the mobility management network element through the access network element of the 3GPP network; or the UE needs to switch to the 3GPP network, but the UE also resides in the non-3GPP network, and the UE passes the non- The network element of the 3GPP network sends an attach request message to the mobility management network element;

The UE carries an identifier in the attach request message indicating that the attach request is an attach request caused by the handover (eg, the UE sets the Attach Type cell in the message to Handover Attach).

S1003: Perform an authentication process between the UE, the mobility management network element, and the HSS.

S1004: Performing a location update and insertion subscription data flow between the mobility management network element and the HSS, registering the address of the mobility management network element into the HSS, and the HSS inserts the subscription data of the UE into the mobility management network element; In this step, the HSS sends the PDN connection information used by the UE in the non-3GPP network to the mobility management network element, that is, the mobility management network element obtains the APN, PGW address, and PDN connection used by the UE in the non-3GPP network. The identification information, or the mobility management network element obtains the PDN GW address and PDN connection identifier information used by the UE in the non-3GPP network.

S1005: The mobility management network element returns an attach message to the UE.

S1006: For each PDN connection, the UE sends a PDN connection request message to the mobility management network element to request establishment of a PDN connection. The message carries the APN, the PDN connection identifier used by the PDN connection, or the PDN connection identifier used by the PDN connection in the message;

S1007: After receiving the foregoing message, the mobility management network element obtains the PPN address corresponding to the APN and the PDN connection identifier or obtains the PDN according to the APN and the PDN connection identifier carried in the message or according to the PDN connection identifier carried in the message. The PDN GW address corresponding to the connection identifier;

The mobility management NE sends a Create Default Bearer Request message to the SGW to request the PDN connection to be created. The Create Default Bearer Request message carries the APN, PDN connection identifier, PGW address information, or carries the PDN connection identifier and PDN GW address information. .

S1008: After receiving the foregoing message, the SGW sends a default bearer request message or a proxy binding update message to the PGW, where the message carries the APN, the PDN connection identifier information, or carries the PDN connection identifier information.

S1009: For each PDN connection establishment procedure, the PGW returns to create a default bearer response or proxy binding acknowledgement message to the SGW;

The PGW keeps the PDN connection used by the UE according to the APN, the PDN connection identifier, or the PDN connection identifier according to the PDN. The PGW keeps the IP address of the PDN connection unchanged, that is, the PGW continues to use the UE for the PDN connection. The IP address assigned when the non-3GPP network is not required to assign an IP address to this PDN connection. If the PGW receives the Create Default Bearer Request message or the Proxy Binding Update message carries the APN information without the PDN connection identifier or a new PDN connection identifier, the PGW considers this to be a new PDN connection setup request message, and the PGW is the PDN. The connection assigns an IP address (as described in Figure 4).

S1010: For each PDN connection establishment procedure, the SGW returns a default bearer response message to the mobility management network element.

S1011: The mobility management network element returns a PDN connection accept message to the UE;

If the PDN connection initiated by the UE is that the UE has been established in the non-3GPP network, the mobility management network element does not need to register the information of the PDN connection to the HSS; if the PDN connection initiated by the UE is not established by the UE in the non-3GPP network Then, the mobility management network element registers the information of the PDN connection (that is, the APN, the PGW address, the PDN connection identifier, or the PDN GW address, the PDN connection identifier) to the HSS.

Referring to FIG. 11, it is a flow chart 3 of Embodiment 1 of the second method.

In the flow chart 3 of the first method embodiment, when the UE accesses the 3GPP network or the non-3GPP network access, the mobility management network element or the PDN GW may also register only the APN and PDN GW address information used by the UE to the HSS. When the UE switches from the non-3GPP network to the 3GPP network or the UE needs to handover from the non-3 GPP network to the 3GPP network, the MME acquires the APN and PDN GW address information used by the UE in the non-3GPP network. For the PDN connection established by the UE in the non-3GPP network, the UE initiates a PDN connection establishment procedure in the 3GPP network, and notifies the mobility management network element of the APN and PDN connection identifier of the PDN connection. After receiving the PDN connection establishment request message of the UE, the mobility management network element obtains the PGW address information used by the PDN connection according to the APN query record carried in the message. The mobility management network element initiates a PDN connection establishment procedure to the queried PGW, and the message carries the APN and PDN connection identification information used by the PDN connection.

The PGW locates the PDN connection used by the UE according to the APN and the PDN connection identifier, and keeps the IP address of the PDN connection unchanged.

Figure 11 includes:

S 1101: the UE accesses in the non-3GPP, and initiates a handover between the non-3GPP network and the 3GPP network; S1102: The UE switches to the 3GPP network, and the UE sends an attach request message to the mobility management network element through the access network element of the 3GPP network; or the UE needs to switch to the 3GPP network, but the UE also resides in the non-3GPP network, and the UE passes the non- The network element of the 3GPP network sends an attach request message to the mobility management network element;

S1103: Perform an authentication process between the UE, the mobility management network element, and the HSS.

S1104: Perform a location update and insertion subscription data flow between the mobility management network element and the HSS, register the address of the mobility management network element into the HSS, and the HSS inserts the subscription data of the UE into the mobility management network element;

In this step, the HSS sends the PDN address information used by the UE in the non-3GPP network to the mobility management network element, that is, the mobility management network element obtains the APN and PGW address information used by the UE in the non-3GPP network.

S1105: The mobility management network element returns an attach message to the UE.

S 1106: For each PDN connection, the UE sends a PDN connection request message to the mobility management network element to request establishment of a PDN connection. The message carries the APN and PDN connection identifiers used by the PDN connection.

S1107: After receiving the foregoing message, the mobility management network element obtains the PGW address corresponding to the APN according to the APN query record carried in the message;

The mobility management NE sends a Create Default Bearer Request message to the SGW to request the PDN connection to be created. The Create Default Bearer Request message carries the APN, PDN connection identifier, and PGW address information.

S1108: After receiving the foregoing message, the SGW sends a create default bearer request message or a proxy binding update message to the PGW, where the message carries the APN and PDN connection identifier information. If the interface protocol between the SGW and the PGW uses the GTP protocol, the use is created. Default bearer request message; if the interface protocol between the SGW and the PGW uses the PMIP protocol, the proxy binding update message is used.

S1109: For each PDN connection establishment procedure, the PGW returns a default bearer response or a proxy binding acknowledgement message to the SGW; After receiving the foregoing message, the PGW locates the PDN connection used by the UE according to the APN and the PDN connection identifier, and the PGW keeps the IP address of the PDN connection unchanged, that is, the PGW continues to use the UE in the non-3GPP network for the PDN connection. The assigned IP address does not need to be assigned an IP address for this PDN connection.

If the PGW receives the Create Default Bearer Request message or the Proxy Binding Update message carries the APN information without the PDN connection identifier or a new PDN connection identifier, the PGW considers this to be a new PDN connection setup request message, and the PGW is the PDN. The connection assigns an IP address.

S1110: For each PDN connection establishment procedure, the SGW returns a default bearer response message to the mobility management network element.

S1111: The mobility management network element returns a PDN connection accept message to the UE;

If the PDN connection initiated by the UE is that the UE has been established in the non-3GPP network, the mobility management network element does not need to register the information of the PDN connection to the HSS; if the PDN connection initiated by the UE is not established by the UE in the non-3GPP network Then, the mobility management network element registers the information of the PDN address (that is, the APN, PGW address) to the HSS. The second method embodiment 2 is described below: The PDN connection establishment method in the process of switching from the 3GPP network to the non-3GPP network or from the 3GPP network to the non-3GPP network.

Referring to FIG. 12, it is a flow chart 1 of the second method embodiment.

In the flow chart 1 of the second method embodiment, when the UE switches from the 3GPP network to the non-3GPP network or when the 3GPP network needs to switch to the non-3GPP network, the non-3GPP GW acquires the PDN connection record used by the UE in the 3GPP network. For each PDN connection record, the non-3GPP GW initiates a PDN connection establishment procedure, notifies the PDN of the PDN-connected APN, PDN connection identifier, or the PDN connection identifier of the PDN connection. The PGW locates the PDN connection used by the UE according to the APN and PDN connection identifier or according to the PDN connection identifier, and keeps the IP address of the PDN connection unchanged.

Figure 12 includes:

S1201: The UE accesses in a 3GPP network, and initiates a handover between the 3GPP network and the non-3GPP network; S1202: Perform authentication and authentication between the UE, the non-3GPP GW, the AAA server, and the HSS;

The non-3GPP GW obtains the PDN connection information used by the UE in the 3GPP network in this step, that is, the non-3GPP GW obtains the APN, PGW address, PDN connection identifier information used by the UE in the 3GPP network, or non-3GPP 0\^ Obtain the PDN GW address and PDN connection identification information used in the 1? 30 network.

S1203: If the PMIP protocol is used in the non-3GPP network, the UE sends a layer 3 attach request message to the non-3GPP GW, where the message may carry the indication bit information to indicate that the layer 3 attach request message is caused by the handover;

S1204: The non-3GPP GW initiates a PDN connection establishment procedure for each obtained APN, PGW address, PDN connection identifier record, or each obtained PDN GW address, PDN connection identifier, and for each PDN connection establishment procedure, non-3GPP GW Sending a proxy binding update message to the PGW, where the message carries the APN in the record, the PDN connection identifier information, or the PDN connection identifier information in the carrying record;

S1205: For each PDN connection establishment procedure, the PGW returns a proxy binding acknowledgement message to the non-3GPP GW;

After receiving the above message, the PGW locates the PDN connection used by the UE according to the APN, the PDN connection identifier, or according to the PDN connection identifier, and the PGW keeps the IP address of the PDN connection unchanged, that is, the PGW continues to use the UE for the PDN connection on the 3GPP network. The IP address assigned at that time does not need to be assigned an IP address for this PDN connection.

If the proxy binding update message received by the PGW carries the APN information without the PDN connection identifier or the new PDN connection identifier, the PGW considers that this is a new PDN connection setup request message, and the PGW assigns an IP address to the PDN connection.

If the PDN connection initiated by the non-3GPP GW is that the UE has been established in the 3GPP network, the PGW does not need to register the information of the PDN connection to the HSS; if the PDN connection initiated by the non-3GPP GW is not established by the UE in the 3GPP network, Then, the PGW registers the information of the PDN connection (that is, the APN, the PGW address, the PDN connection identifier, or the PDN GW address, the PDN connection identifier) to the HSS.

S1206: The non-3GPP GW sends a layer 3 attach accept message to the UE.

Referring to FIG. 13, it is a flow chart 2 of the second method embodiment. When the UE switches from the 3GPP network to the non-3GPP network or when the 3GPP network needs to switch to the non-3GPP network, the non-3GPP GW acquires the PDN connection record used by the UE in the 3GPP network, and for each PDN connection record, the UE initiates the PDN connection. Establish a program to notify the PGW of the APN, PDN connection identifier of the PDN connection or the PDN connection identifier of the PDN connection. The PGW locates the PDN connection used by the UE according to the APN and the PDN connection identifier or according to the PDN connection identifier, and keeps the IP address of the PDN connection unchanged.

Figure 13 includes:

S1301: The UE accesses in the 3GPP network, and initiates a handover between the 3GPP network and the non-3GPP network;

S1302: Perform authentication and authentication between the UE, the non-3GPP GW, the AAA server, and the HSS;

The non-3GPP GW obtains the PDN connection information used by the UE in the 3GPP network in this step, that is, the non-3GPP GW obtains the APN, the PGW address, the PDN connection identifier information used by the UE in the 3GPP network, or the non-3GPP GW. Obtaining the PDN GW address and PDN connection identifier information used by the UE in the 3GPP network.

S1303: The UE sends a layer 3 attach request message to the non-3GPP GW.

S 1304: if the CMIP protocol is used in the non-3GPP network, the non-3GPP GW back layer 3 attach accept message to the UE;

S1305: For each PDN connection established by the UE in the 3GPP network, the UE sends a binding update message to the PGW to establish a PDN connection, where the message carries the APN, the PDN connection identifier information used by the PDN connection, or the PDN connection identifier information used by the PDN connection. ;

S1306: For each PDN connection establishment procedure, the PGW returns a binding confirmation message to

UE.

In step S1306, after receiving the foregoing message, the PGW locates the PDN connection used by the UE according to the APN, the PDN connection identifier, or according to the PDN connection identifier, and the PGW keeps the IP address of the PDN connection unchanged, that is, the PGW continues for the PDN connection. The IP address assigned by the UE when it is in the 3GPP network is used without assigning an IP address to this PDN connection. If the binding update message received by the PGW carries the APN information without the PDN connection identifier or the new PDN connection identifier, the PGW considers that this is a new PDN connection setup request message, and the PGW allocates an IP address for the PDN connection. If the UE initiates a PDN connection, the UE is If the PDM connection is established in the 3GPP network, the PGW does not need to register the information of the PDN connection to the HSS. If the PDN connection initiated by the UE is not established in the 3GPP network, the PGW registers the PDN connection information (ie, the APN, the PGW address, and the PDN connection). Identifies, or, PDN GW address and PDN connection identifier) to the HSS.

Referring to FIG. 14, it is a flow chart 3 of the second method embodiment.

In the flow chart 3 of the second method embodiment, when the UE switches from the 3GPP network to the non-3GPP network or when the 3GPP network needs to switch to the non-3GPP network, the non-3GPP GW acquires the PDN connection record used by the UE in the 3GPP network. For each PDN connection record, the UE initiates a PDN connection establishment procedure, notifies the non-3GPP GW of the APN, PDN connection identity of the PDN connection or the PDN connection identity of the PDN connection. The non-3GPP GW obtains the PGW address information used by the PDN connection according to the APN, PDN connection identifier information or the PDN connection identifier information query record. The non-3GPP GW sends a proxy binding update message to the obtained PGW, and the message carries the APN, the PDN connection identifier used by the PDN connection, or the PDN connection identifier information used by the PDN connection. The PGW locates the PDN connection used by the UE according to the APN and the PDN connection identifier or according to the PDN connection identifier, and keeps the IP address of the PDN connection unchanged.

Figure 14 includes: (Original Figure 12)

S1401: The UE accesses in the 3GPP network, and initiates a handover between the 3GPP network and the non-3GPP network;

S1402: Perform authentication and authentication between the UE, the non-3GPP GW, the AAA server, and the HSS;

S1403: The UE sends a layer 3 attach request message to the non-3GPP GW.

S1404: The non-3GPP GW returns Layer 3 attach accept message to the UE;

S 1405: For each PDN connection established by the UE in the 3GPP network, the UE sends a PDN connection request message to the non-3GPP GW to establish a PDN connection, where the message carries the APN, PDN connection identifier information used by the PDN connection, or carries the PDN connection. PDN connection identifier Information

S1406: After receiving the foregoing message, the non-3 GPP GW obtains the PGW address used by the PDN connection according to the APN and PDN connection identifier information in the message or according to the PDN connection identifier information in the message; The update message is sent to the obtained PGW, and the message carries the APN, the PDN connection identifier information in the record or the PDN connection identifier information in the record;

S1407: For each PDN connection establishment procedure, the PGW returns a proxy binding acknowledgement message to the non-3GPP GW;

After receiving the above message, the PGW locates the PDN connection used by the UE according to the APN, the PDN connection identifier, or according to the PDN connection identifier, and the PGW keeps the IP address of the PDN connection unchanged, that is, the PGW continues to use the UE for the PDN connection on the 3GPP network. The IP address assigned at that time does not need to be assigned an IP address for this PDN connection. If the proxy binding update message received by the PGW carries the APN information without the PDN connection identifier or the new PDN connection identifier, the PGW considers that this is a new PDN connection setup request message, and the PGW allocates an IP address for the PDN connection.

S1408: The non-3 GPP GW sends a PDN connection accept message to the UE.

Referring to FIG. 15, it is a flow chart 4 of the second method embodiment.

In the flow chart 4 of the second method embodiment, when the UE accesses the 3GPP network or the non-3GPP network, the mobility management network element or the PDN GW may register only the APN and PDN GW address information used by the UE to the HSS. When the UE switches from the 3GPP network to the non-3GPP network or from the 3GPP network needs to switch to the non-3GPP network, the non-3GPP GW acquires the PDN address record used by the UE in the 3GPP network, and for each PDN connection record, the UE initiates the PDN connection. Establish a procedure to notify the non-3GPP GW of the APN and PDN connection identifier of the PDN connection. The non-3GPP GW obtains the PGW address information used by the PDN connection according to the APN information query record. The non-3GPP GW sends The proxy binds the update message to the obtained PGW, and the message carries the APN and PDN connection identifier information used by the PDN connection. The PGW locates the PDN connection used by the UE according to the APN and the PDN connection identifier, and keeps the IP address of the PDN connection unchanged.

Figure 15 includes:

S1501: The UE accesses in the 3GPP network, and initiates a handover between the 3GPP network and the non-3GPP network;

S1502: Perform authentication and authentication between the UE, the non-3GPP GW, the AAA server, and the HSS;

The non-3GPP GW obtains the PDN address information used by the UE in the 3GPP network in this step, that is, the non-3GPP GW obtains the APN and PGW address information used by the UE in the 3GPP network.

S1503: The UE sends a layer 3 attach request message to the non-3GPP GW.

S1504: The non-3GPP GW returns Layer 3 attach accept message to the UE;

S1505: For each PDN connection established by the UE in the 3GPP network, the UE sends a PDN connection request message to the non-3GPP GW to establish a PDN connection, where the message carries the APN and PDN connection identifier information used by the PDN connection.

S1506: After receiving the foregoing message, the non-3GPP GW queries the record according to the APN information in the message, and obtains the PGW address used by the PDN connection; the non-3GPP GW sends a proxy binding update message to the obtained PGW, where the message carries the record. APN, PDN connection identification information;

S1507: For each PDN connection establishment procedure, the PGW returns a proxy binding acknowledgement message to the non-3GPP GW;

After receiving the above message, the PGW locates the PDN connection used by the UE according to the APN and PDN connection identifiers, and the PGW keeps the IP address of the PDN connection unchanged, that is, the PGW continues to use the IP address allocated by the UE in the 3GPP network for the PDN connection. There is no need to assign an IP address to this PDN connection. If the proxy binding update message received by the PGW carries the APN information without the PDN connection identifier or the new PDN connection identifier, the PGW considers that this is a new PDN connection setup request message, and the PGW allocates an IP address for the PDN connection.

If the non-3GPP GW initiates a PDN connection that the UE has established in the 3GPP network, the PGW does not need to register the information of this PDN connection to the HSS; if non-3GPP The GW-initiated PDN connection is that the UE is not established in the 3GPP network, and the PGW registers the PDN address information (ie, the APN, PGW address) to the HSS.

S 1508: The non-3 GPP GW sends a PDN Connection Accept message to the UE.

The processing of the second method in the present invention may also be applied to the processing in other scenarios. For example, to ensure the validity of the PDN connection, the UE initiates a PDN connection establishment process after a period of time to re-establish the established PDN connection. Sending a PDN connection request message to the mobility management network element or the non-3GPP GW, where the message carries the PDN connection identifier and the APN information or the PDN connection identifier information; the mobility management network element or the non-3GPP GW according to the PDN connection identifier and the APN information Or, according to the PDN connection identifier information, the PGW used by the requested PDN connection, the mobility management network element or the non-3GPP GW notifies the PDN connection of the PGW reestablishment request, where the notification carries the PDN connection identifier and the APN information or the PDN connection identifier. The PGW establishes a PDN connection according to the obtained PDN connection identifier and the APN information or the PDN connection identifier information. It should be noted that, in various embodiments provided by the present invention, the PDN connection is uniquely identified by the PDN connection identifier, the APN, the PGW address, or the PDN connection identifier and the PGW address. In actual implementation, the method may also be implemented in other manners. Uniquely identifies a PDN connection, such as the IP address, APN, PGW address used by the PDN connection to uniquely identify the PDN connection, or the IP address type (IPv4 or IPv6 or IPv4/IPv6 type), APN, PGW address used by the PDN connection. The PDN connection is uniquely identified, and the processing method is the same as the processing in the embodiment of the present invention, except that the PDN connection identifier in the embodiment is replaced with the IP address used by the PDN connection or the IP address type used for the PDN connection. There is no limit to this. It should be noted that, in various embodiments provided by the present invention, the PDN connection identifier may be an independent cell. In an actual implementation, the PDN connection identifier may also be appended to the APN cell, such as an APN+ serial number (eg, The format is APN: serial number) to identify (the serial number here is the PDN connection identifier described in the embodiment of the present invention), which is not limited by the embodiment of the present invention. It should be noted that, in various embodiments provided by the present invention, the PGW address is registered in the HSS, and in actual implementation, the FQDN of the PGW (fully qualified domain name, The Fully Qualified Domain Name information is registered to the HSS, and the subsequent mobility management network element or the non-3GPP gateway network element obtains the FQDN information of the PGW, and the PGW address used by the UE can be obtained according to the FQDN. The PGW ID information of the PGW used by the PGW is used to identify the PGW used by the UE.

Corresponding to the foregoing first method, the embodiments of the present invention provide various devices, including devices located on the UE side, the mobility management network element side in the 3GPP network, the non-3GPP network element side, the PGW side, and the HSS side, which are respectively introduced below.

The PDN connection registration device on the UE side provided by the embodiment of the present invention may be the UE itself or a functional entity located inside the UE, and may be implemented by software, hardware or a combination of software and hardware. Specifically, the device includes: an identifier configuration unit, configured to allocate a PDN connection identifier for the PDN connection; and a PDN request unit, configured to send an attach message or a PDN connection request message that includes the PDN connection identifier.

The mobility management network element side of the 3GPP network provided by the embodiment of the present invention

The PDN connection registration device may be a mobility management network element itself or a functional entity located inside the mobility management network element, and may be implemented by software, hardware, or a combination of software and hardware. Specifically, the apparatus includes: a message receiving unit, configured to receive an attach request message or a PDN connection request message from a UE, further comprising: an identifier configuration unit, configured to allocate a PDN connection identifier for the PDN connection; and a PDN request unit, configured to send the The default bearer request message is created by the PDN connection identifier. The mobility management network element includes an MME or an SGSN.

The PDN connection registration device of the non-3GPP network element provided by the embodiment of the present invention may be a non-3GPP network element itself, or may be a functional entity located in a non-3GPP network element, and may be combined by software, hardware, or combination of software and hardware. achieve. Specifically, the apparatus includes: a message receiving unit, configured to receive a PDN connection request message from the UE, further comprising: an identifier configuration unit, configured to allocate a PDN connection identifier for the PDN connection; and a PDN request unit, configured to send the PDN connection The identified proxy binding update message. The non-3GPP network element refers to an EPDG, an ASN GW, or an AGW. The PDN connection registration device on the PGW side provided by the embodiment of the present invention may be the PGW itself or a functional entity located inside the PGW, and may be implemented by software, hardware or a combination of software and hardware. Specifically, the apparatus includes: a message receiving unit, configured to receive a PDN connection request, and further includes: an identifier configuration unit, configured to allocate a PDN connection identifier for the PDN connection; and a PDN request reply unit, configured to send the PDN connection identifier Reply message. The PDN request replying unit replies to the SGW to create a default bearer response message, a binding acknowledgement message, or a proxy binding acknowledgement message.

The PDN connection registration device on the HSS side provided by the embodiment of the present invention may be the HSS itself or a functional entity located inside the HSS, and may be implemented by software, hardware or a combination of software and hardware. Specifically, the device includes: a message receiving unit, configured to receive a message including a PDN connection identifier, an APN, and PGW address information, or a message that includes a PDN connection identifier and a PGW address information; and a storage unit, configured to store the PDN connection identifier The APN and PGW address information are either used to store the PDN connection identifier and PGW address information. The message receiving unit receives a message including the PDN connection identifier, the APN, and the PGW address information from the mobility management network element or the AAA server, or the message receiving unit receives the content from the mobility management network element or the AAA server. The PDN connects the message with the identifier and the PGW address information.

Corresponding to the second method described above, the embodiment of the present invention also provides a device on the PGW side. The PDN connection establishing device on the PGW side may be the PGW itself or a functional entity located inside the PGW, and may be implemented by software, hardware or a combination of software and hardware. Specifically, the device includes: a message receiving unit, configured to receive a message including a PDN connection identifier and an APN, or to receive a message including a PDN connection identifier; a query unit, configured to use the PDN connection identifier and the APN according to the The PDN connection identifier is used to query the PDN connection that has been established for the UE; the IP address control unit is configured to keep the IP address of the PDN connection unchanged. In the 3GPP network, the message receiving unit of the device is configured to receive a create default bearer request message or a proxy binding update message that includes a PDN connection identifier and an APN from the SGW, or the message receiving unit of the device is received from the SGW. The PDN connection identifier creates a default bearer request message or a proxy binding update message. In a non-3GPP network, the message receiving unit of the device receives a proxy binding update message including a PDN connection identifier and an APN from a non-3GPP network element, Or the message receiving unit of the device receives the proxy binding update message that includes the PDN connection identifier from the non-3GPP network element, or receives the binding update message that includes the PDN connection identifier and the APN from the UE, or receives the binding update message from the UE. A binding update message containing the PDN connection ID.

Corresponding to the foregoing second method, the embodiments of the present invention provide various devices, including the UE side, the mobility management network element side in the 3GPP network, and the non-3GPP network element side, which are respectively introduced below.

The PDN connection establishing apparatus on the UE side provided by the embodiment of the present invention may be the UE itself or a functional entity located inside the UE, and may be implemented by software, hardware or a combination of software and hardware. Specifically, the device includes: an information storage unit, configured to store PDN connection identifiers, APNs, and PGW address information established by the UE in the source network, or obtain PDN connection identifiers and PGW address information established by the UE in the source network; And a message for sending a request for establishing a PDN connection that includes the PDN connection identifier.

The device for establishing a PDN connection on the mobility management network element side of the 3GPP network according to the embodiment of the present invention may be a mobility management network element itself, or may be a functional entity located inside the mobility management network element, and may be implemented by software, hardware or The combination of software and hardware is implemented. Specifically, the device includes: an information acquiring unit, configured to acquire, from the HSS, the PEN connection identifier, the APN, and the PGW address information established by the UE in the source network, or obtain the PDN connection identifier and the PGW address information established by the UE in the source network; And a requesting unit, configured to send a create default bearer request message that includes the PDN connection identifier.

The PDN connection establishing apparatus of the non-3GPP network element provided by the embodiment of the present invention may be a non-3GPP network element itself, or may be a functional entity located inside the non-3GPP network element, and may be combined by software, hardware or combination of software and hardware. achieve. Specifically, the device includes: an information acquiring unit, configured to acquire, from the HSS, the PEN connection identifier, the APN, and the PGW address information established by the UE in the source network, or obtain the PDN connection identifier and the PGW address information established by the UE in the source network; And a requesting unit, configured to send a create default bearer request message that includes the PDN connection identifier. The above description is only a preferred embodiment of the present invention, and it should be noted that those skilled in the art will not deviate from the present disclosure. On the premise of the inventive concept, several modifications and refinements can also be made, and such improvements and refinements should also be considered as protection scope of the present invention.

Through the description of the above embodiments, those skilled in the art can clearly understand that the present invention can be implemented by hardware, or can be implemented by means of software plus necessary general hardware platform, and the technical solution of the present invention. It can be embodied in the form of a software product that can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.), including a number of instructions for making a computer device (may It is a personal computer, a server, or a network device, etc.) that performs the methods described in various embodiments of the present invention.

In conclusion, the above description is only a preferred embodiment of the present invention and is not intended to limit the scope of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Claims

Rights request

A method for registering a PDN connection of a packet data network, comprising: assigning a PDN connection identifier to a PDN connection request initiated by a user equipment UE; and transmitting, by the home subscriber server HSS, the PDN connection identifier and an access point name APN and PDN connection registration information identified by the packet data network gateway PGW; or

The PDN connection registration information including the PDN connection identifier and the packet data network gateway PGW identifier is sent to the home subscriber server HSS.

The method according to claim 1, wherein the UE-initiated PDN connection request comprises: an attach request message sent by the UE, configured to request access to a 3GPP network or a non-3GPP network, or a PDN connection sent by the UE. A request message, configured to request to establish a PDN connection in a 3GPP or non-3GPP network.

The method according to claim 2, wherein the assigning the PDN connection identifier to the PDN connection request initiated by the user equipment UE comprises:

When the UE sends an attach request message requesting access to the 3GPP network or the UE sends a PDN connection request message requesting to establish a PDN connection in the 3GPP network, the PDN connection is allocated by the mobility management network element receiving the attach request message or the PDN connection request message. After the mobility management network element receives the attach request message or the PDN connection request message, the serving gateway SWG sends a default bearer request or a proxy binding update to the PGW, and the PGW allocates the PDN connection identifier. .

When the UE sends an attach request message requesting access to the non-3GPP network or the UE sends a PDN connection request message requesting to establish a PDN connection in the non-3GPP network, the PDN is allocated by the non-3GPP network element receiving the attach request message or the PDN connection request message After the connection identifier is received, the non-3GPP network element initiates a proxy binding update to the PGW after receiving the attach request message or the PDN connection request message, and the PGW allocates the PDN connection identifier.

When the UE sends an attach request or a PDN connection request message, the UE allocates a PDN connection identifier;

Or,

After the UE sends the attach request, the UE sends a binding update message to the PGW; after receiving the binding update message, the PGW allocates the PDN connection identifier.

A method for allocating an IP address of a PDN connection, comprising: after receiving a message requesting to establish a PDN connection, the PGW locates the established PDN connection according to the PDN connection identifier information carried in the message;

The PGW allocates an IP address in the established PDN connection for the PDN connection requested to be established.

The method according to claim 6, wherein the requesting to establish a PDN connection message comprises creating a default bearer request message or a proxy binding update message or a binding update message.

The method according to claim 7, wherein the method further comprises: acquiring, by the mobility management network element in the 3GPP network, the PDN connection identifier, the APN, and the PGW identification information used by the UE from the HSS, and sending the information to the PGW through the SGW. Creating a default bearer request message or a proxy binding update message, and carrying the PDN connection identifier in the create default bearer request message or the proxy binding update message;

Or,

The mobility management network element in the 3GPP network obtains the PDN connection identifier and the PGW identification information used by the UE from the HSS, and sends a default bearer request message or a proxy binding update message to the PGW through the SGW, and creates a default bearer request message or The proxy binding update message carries the PDN connection identifier;

Or,

The mobility management network element in the 3GPP network receives the PDN connection request message that is sent by the UE and includes the APN and the PDN connection identifier. The mobility management network element queries the PGW identifier corresponding to the APN according to the APN, and sends a default bearer request message to the PGW through the SGW. Or The proxy binding update message carries the PDN connection identifier in the create default bearer request message or the proxy binding update message.

9. The method according to claim 8, wherein in the 3GPP network

PGW identification information, including:

The mobility management network element in the 3GPP network acquires, from the HSS, the PDN connection identifier, APN, and PGW identification information used by the UE in the source non-3GPP network;

The mobility management network element in the 3GPP network obtains the PDN connection identifier and the PGW identifier information used by the UE from the HSS, including:

The mobility management network element in the 3GPP network acquires the PDN connection identifier and the PGW identification information used by the UE in the source non-3GPP network from the HSS.

The method according to claim 7, wherein the method further comprises: obtaining, by the non-3GPP network element, the PDN connection identifier, the APN and the PGW identification information used by the UE from the HSS, and binding the update message to the PGW sender proxy, Carrying the PDN connection identifier in the proxy binding update message;

Or,

The non-3GPP network element obtains the PDN connection identifier and the PGW identification information used by the UE from the HSS, and sends a proxy binding update message to the PGW, where the PDN connection identifier is carried in the proxy binding update message;

Or

The non-3GPP network element receives the PDN connection request message that is sent by the UE and includes the APN and the PDN connection identifier, and the non-3GPP network element sends the proxy binding update message to the PGW according to the APN query PGW identifier corresponding to the APN, and carries the proxy binding update message in the proxy binding update message. The PDN connection identifier.

The method according to claim 10, wherein the non-3GPP network element obtains, from the HSS, the PDN connection identifier, the APN, and the PGW identification information used by the UE, including:

The non-3GPP network element obtains the PDN connection identifier, APN, and PGW identification information used by the UE in the source 3GPP network from the HSS; The non-3GPP network element obtains the PDN connection identifier and the PGW identification information used by the UE from the HSS, including:

The non-3GPP network element obtains the PDN connection identifier and the PGW identification information used by the UE in the source 3GPP network from the HSS.

The method according to claim 6, wherein the method further comprises: sending, by the UE, a binding update message including the PDN connection identifier and the APN to the PGW;

Or,

The UE sends a binding update message including the PDN connection identifier to the PGW.

13. A method for establishing a PDN connection, comprising:

Obtaining the PDN connection identifier, the APN, and the PGW identifier information used by the UE, or obtaining the PDN connection identifier and the PGW identifier information used by the UE;

And establishing a PDN connection according to the PDN connection identifier, the APN and PGW identification information, or according to the PDN connection identifier and the PGW identification information.

The method according to claim 13, wherein the acquiring the PDN connection identifier, the APN, and the PGW identification information used by the UE, or acquiring the PDN connection identifier and the PGW identification information used by the UE, includes:

Obtaining the PDN connection identifier, the APN, and the PGW identification information used by the UE in the source network, or acquiring the PDN connection identifier and the PGW identification information used by the UE in the source network, where the information is based on the PDN connection identifier, the APN, and the PGW identification information. The PDN connection identifier and the PGW identification information establish a PDN connection, including:

And establishing a PDN connection in the target network according to the PDN connection identifier, the APN and PGW identification information, or according to the PDN connection identifier and the PGW identification information.

The method according to claim 13, wherein the acquiring the PDN connection identifier, the APN, and the PGW identification information used by the UE, or acquiring the PDN connection identifier and the PGW identifier information used by the UE includes:

The mobility management network element obtains the PDN connection identifier, the APN, and the PGW identification information used by the UE from the HSS, or The mobility management network element obtains the PDN connection identifier and the PGW identification information used by the UE from the HSS, or

The mobility management network element receives the PDN connection request message that is sent by the UE and includes the APN and the PDN connection identifier, and the mobility management network element queries the PGW identifier corresponding to the APN or the mobility management network element according to the APN and the The PGW identifier corresponding to the PDN connection identifier is queried, or

The mobility management network element receives the PDN connection request message that is sent by the UE and includes the PDN connection identifier, and the mobility management network element queries the corresponding PGW identifier according to the PDN connection identifier.

The method according to claim 15, wherein the mobility management network element obtains, from the HSS, the PDN connection identifier, the APN, and the PGW identifier information used by the UE, including:

The mobility management network element acquires, from the HSS, the PDN connection identifier, the APN, and the PGW identity information used by the UE in the source non-3GPP network;

The mobility management network element obtains the PDN connection identifier and the PGW identifier information used by the UE from the HSS, including:

The mobility management network element obtains, from the HSS, the PDN connection identifier and PGW identification information used by the UE in the source non-3GPP network.

The method according to claim 15, wherein the establishing a PDN connection according to the PDN connection identifier, the APN and PGW identification information, or the PDN connection identifier and the PGW identification information comprises:

The mobility management network element sends a default bearer request message to the SGW for the obtained APN, the PGW identifier, the PDN connection identifier, or the obtained PGW identifier and the PDN connection identifier, where the message carries the PGW identifier, the APN, the PDN connection identifier, or the message. Carry the PGW identifier and the PDN connection identifier;

After receiving the Create Default Bearer Request message, the SGW sends a Create Default Bearer Request message or a Proxy Binding Update message to the PGW. The message carries the APN, the PDN connection identifier, or the message carries the PDN connection identifier.

The non-3GPP network element obtains the PDN connection identifier, the APN, and the PGW identification information used by the UE from the HSS.

Or,

The non-3GPP network element obtains the PDN connection identifier and the PGW identification information used by the UE from the HSS.

Or

The non-3GPP network element receives the PDN connection request message that is sent by the UE and includes the APN and the PDN connection identifier, and the non-3GPP network element queries the PGW identifier corresponding to the APN according to the APN or the non-3GPP network element is connected according to the APN and the PDN. Identify the PGW ID corresponding to the query.

Or,

The non-3GPP network element receives the PDN connection request message that is sent by the UE and includes the PDN connection identifier, and the non-3GPP network element queries the corresponding PGW identifier according to the PDN connection identifier.

The method according to claim 18, wherein the non-3GPP network element obtains the PDN connection identifier, the APN, and the PGW identification information used by the UE from the HSS, including:

The non-3GPP network element obtains, from the HSS, the PDN connection identifier, APN, and PGW identification information used by the UE in the source 3GPP network;

The non-3GPP network element obtains the PDN connection identifier and the PGW identifier information used by the UE from the HSS, including:

The method according to claim 18, wherein the establishing a PDN connection according to the PDN connection identifier, the APN and PGW identification information, or the PDN connection identifier and the PGW identification information comprises:

The non-3GPP network element sends a proxy binding update message to the PGW for the obtained APN, PGW identity, PDN connection identifier, or for the obtained PGW identity and PDN connection identity, The message carries the APN, PDN connection identifier information or carries the PDN connection identifier information.

The method according to claim 13, wherein the method specifically includes: the UE acquiring the PDN connection identifier, the APN, and the PGW identifier information used by the UE, or the UE acquiring the PDN connection identifier and the PGW identifier information used by the UE;

The UE sends a binding update message to the PGW, and the message carries the APN, the PDN connection identifier, or the message carries the PDN connection identifier, for the obtained PDN connection identifier, the APN and the PGW identifier information, or the PGW identifier and the PDN connection identifier.

The method according to claim 21, wherein the acquiring, by the UE, the PDN connection identifier, the APN, and the PGW identification information used by the UE, includes:

The UE acquires the PDN connection identifier, the APN, and the PGW identifier information used by the UE in the source 3GPP network; or

The UE acquires the PDN connection identifier, the APN, and the PGW identifier information used by the UE in the source non-3GPP network;

And obtaining, by the UE, the PDN connection identifier and the PGW identifier information used by the UE, where: the UE acquires the PDN connection identifier and the PGW identifier information used by the UE in the source 3GPP network; or

The UE acquires the PDN connection identifier and PGW identification information used by the UE in the source non-3GPP network.

A packet data network PDN connection processing method, characterized in that:

Receiving a PDN connection request initiated by the UE of the user equipment;

And assigning a PDN connection identifier to the PDN connection request, where the PDN connection identifier is used to identify the PDN connection.

The method according to claim 23, wherein the UE-initiated PDN connection request comprises: an attach request message sent by the UE, configured to request access to a 3GPP network or a non-3GPP network, or a PDN connection sent by the UE. A request message, configured to request to establish a PDN connection in a 3GPP or non-3GPP network.

The method according to claim 24, wherein the allocating the PDN connection identifier for the PDN connection request comprises: When the UE sends an attach request message requesting access to the 3GPP network or the UE sends a PDN connection request message requesting to establish a PDN connection in the 3GPP network, the PDN connection is allocated by the mobility management network element receiving the attach request message or the PDN connection request message. After the mobility management network element receives the attach request message or the PDN connection request message, the serving gateway SWG initiates a default bearer request or a proxy binding update to the PGW, and the PGW allocates the PDN connection identifier. .

The method according to claim 24, wherein the assigning the PDN connection identifier to the PDN connection request initiated by the user equipment UE comprises:

27. A communication terminal, comprising:

An identifier configuration unit, configured to allocate a PDN connection identifier for the PDN connection, where the PDN connection identifier is used to identify the PDN connection;

And a PDN requesting unit, configured to send an attach message or a PDN connection request message that includes the PDN connection identifier.

28. A mobility management network element of a 3GPP network, comprising: a message receiving unit, configured to receive an attach request message or a PDN connection request message from the UE, further comprising:

An identification configuration unit, configured to allocate a PDN connection identifier for the PDN connection;

The PDN request unit is configured to send a create default bearer request message that includes the PDN connection identifier.

The mobility management network element according to claim 28, wherein the mobility management network element comprises a mobility management entity MME or a serving GPRS node SGSN.

30. A non-3GPP network element, comprising: a message receiving unit, configured to receive a PDN connection request message from a UE, where the method further includes: An identifier configuration unit, configured to allocate a PDN connection identifier for the PDN connection, where the PDN connection identifier is used to identify the PDN connection;

A PDN request unit, configured to send a proxy binding update message including the PDN connection identifier.

The non-3GPP network element according to claim 30, wherein the non-3GPP network element comprises an evolved packet data gateway EPDG, an access service network gateway ASN GW or an access gateway AGW.

32. A packet data network gateway PGW, comprising: a message receiving unit, configured to receive a request PDN connection, further comprising:

The PDN request reply unit is configured to send a reply message including the PDN connection identifier.

33. The PGW according to claim 32, wherein the PDN request replying unit replies to the SGW to create a default bearer response message, a binding acknowledgement message or a proxy binding acknowledgement message.

34. A home subscriber server HSS, comprising:

35. The HSS according to claim 34, wherein the message receiving unit receives a message including the PDN connection identifier information from a mobility management network element or an AAA server.

36. An IP address device for allocating a PDN connection, located on the PGW side, and including:

a query unit, configured to establish, according to the PDN connection identifier and the APN, a PDN connection established according to the PDN connection identifier; An IP address control unit, configured to allocate the established PDN connection for requesting

The IP address in the PDN connection.

The device according to claim 36, wherein, in the 3GPP network, the message receiving unit of the device receives a create default bearer request message or a proxy binding update message that includes a PDN connection identifier and an APN from the SGW, Alternatively, the message receiving unit of the device receives a create default bearer request message or a proxy binding update message that includes a PDN connection identifier from the SGW.

The device according to claim 36, wherein, in the non-3GPP network, the message receiving unit of the device receives the proxy binding update message including the PDN connection identifier and the APN from the non-3GPP network element, or The non-3GPP network element receives the proxy binding update message that includes the PDN connection identifier, or receives the binding update message that includes the PDN connection identifier and the APN from the UE, or receives the binding update message that includes the PDN connection identifier from the UE.

39. A device for establishing a PDN connection, located on a target 3GPP mobility management network side, and including:

The information obtaining unit is configured to obtain the PDN connection identifier, the APN, and the PGW identifier information used by the UE, or obtain the PDN connection identifier and the PGW identifier information used by the UE.

The device according to claim 39, wherein the information acquiring unit is configured to acquire the PDN connection identifier, the APN and the PGW identification information established by the UE in the source network, or obtain the PDN established by the UE in the source network. Connection identifier and PGW identification information.

41. A device for establishing a PDN connection, located on a target non-3GPP network element side, and the method includes:

An information acquiring unit, configured to acquire, from the HSS, a PDN connection identifier, an APN, and a PGW identifier information used by the UE, or obtain a PDN connection identifier and a PGW identifier information used by the UE;

And a PDN requesting unit, configured to send a proxy binding update message that includes the PDN connection identifier.

The device according to claim 41, wherein the information acquiring unit is configured to acquire a PDN connection identifier, an APN, and a PGW identifier information established by the UE on the source network, or obtain a PDN established by the UE in the source network. Connection identifier and PGW identification information.

43. A device for establishing a PDN connection, located on a UE side, and the method includes:

An information storage unit, configured to store a PDN connection identifier, an APN, and a PGW identifier information used by the UE, or obtain a PDN connection identifier and PGW identifier information used by the UE;

And a PDN requesting unit, configured to send a message that includes the PDN connection identifier to establish a PDN connection.

The device according to claim 43, wherein the information acquiring unit is configured to acquire the PDN connection identifier, the APN, and the PGW identification information that the UE establishes on the source network, or obtain the PDN established by the UE in the source network. Connection identifier and PGW identification information.