WO2013166817A1

WO2013166817A1 - Data message transmission method, pdn connection identification processing method, and device

Info

Publication number: WO2013166817A1
Application number: PCT/CN2012/084854
Authority: WO
Inventors: 刘国燕; 朱春晖; 涂杨巍; 周星月
Original assignee: 中兴通讯股份有限公司
Priority date: 2012-09-07
Filing date: 2012-11-19
Publication date: 2013-11-14
Also published as: CN103686846A; CN103686846B

Abstract

Disclosed are a data message transmission method, a PDN connection identification processing method, and a device. By sending a first IP address request message to a trusted non-3GPP access network, UE receives a first IP address which is allocated to the UE by the trusted non-3GPP access network, and then by sending a second IP address request message to the trusted non-3GPP access network, the UE acquires a second IP address which is allocated to the UE by a 3GPP core network to realize the discrimination of different PDNs of the UE through different IP addresses, which solves the problem in the related art that the reliability of data message transmission of UE through a trusted non-3GPP access network is relatively poor, improving the reliability of data message transmission, and solves the problem in the related art that the reliability of data message transmission of UE through a non-3GPP access network is relatively poor, achieving the effect of improving the reliability of data message transmission of the UE through the non-3GPP access network.

Description

Data message transmission method, PDN connection identifier processing method, and device

The present invention relates to the field of communications, and in particular, to a data packet transmission method, a packet data network (Packet Data Network, PDN for short) connection identifier processing method, and a device. The evolved packet system (Evolved Packet System, EPS for short) is composed of an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and a Mobility Management Entity (abbreviated as Mobility Management Entity). The MME, the Serving Gateway (S-GW), the Packet Data Network Gateway (PDN GW or P-GW), and the Home Subscriber Server (HSS).

1 is a network structure diagram of a related art 3GPP network and a non-3GPP network interworking, as shown in FIG. 1, the EPS supports interworking with a non-3GPP system, wherein interworking with a non-3GPP system is implemented through an S2a/b/c interface, The PDN GW acts as an anchor between 3GPP and non-3GPP systems. In the system architecture diagram of EPS, non-3GPP system access is divided into untrusted non-3GPP access and trusted non-3GPP access. The untrusted non-3GPP access needs to be connected to the PDN GW by an Evolved Packet Data Gateway (ePDG), and the interface between the ePDG and the PDN GW is S2b; the trusted non-3GPP access can directly pass through the S2a. The interface is connected to the PDN GW. The S2a interface uses the Proxy Mobile Internet Protocol (PMIP) protocol to exchange information. In addition, the S2c interface provides the user equipment (User Equipment, UE for short) and the PDN GW. User plane-related control and mobility support, supporting mobility management protocols for mobile IPv6 supporting dual stacks ( Double Supported Moblie IPv6 Support for Dual Stack Hosts and Routers (referred to as DSMIPv6), which can be used for untrusted non-3GPP and trusted non-3GPP access.

At present, many operators believe that a wireless local area network (WLAN) can be used as a trusted non-3GPP system. Therefore, the problem of interconnecting UEs accessing EPS through trusted WLANs has gradually been taken seriously and research has begun. And existing architectures have been created in the prior art. A logical network element of the WLAN communicates with the P-GW of the 3GPP through the S2a interface, and the S2a interface supports the Generic Tunneling Protocol (GTP)/PMIP protocol. In order to avoid upgrading the Access Controller (AC)/Broadband Network Gateway (BNG) device in the live network, a WLAN access gateway (for example, a trusted WLAN) is introduced. The Trusted WLAN Access Gateway (TWAG) is used to reduce the upgrade of the existing network equipment. The TWAG is introduced. The network structure is shown in Figure 2. In this case, TWAG needs to be supported and P. - S2a interface function between GW.

The 3GPP protocol stipulates that after the UE accesses through the WLAN, it may access different mobile service packet networks at the same time. At this time, multiple Packet Data Network (PDN) connections are established. In the related art, a UE may distinguish different PDN connections by using a service quintuple. However, different PDN connections of the same UE may be assigned the same IP address. Therefore, for this scenario, how to distinguish between different PDN connections needs to be further resolved.

For the problem that the reliability of data packet transmission by the UE through the trusted non-3GPP access network is relatively poor in the related art, an effective solution has not been proposed yet. Summary of the invention

The embodiment of the invention provides a data packet transmission method, a PDN connection identifier processing method, and a device, which can solve the problem that the UE has poor reliability of data packet transmission through the trusted non-3GPP access network.

According to an aspect of the embodiments of the present invention, a data packet transmission method is provided, including: Sending, by the UE, a first IP address request message to a trusted non-3rd generation partner 3GPP access network, and receiving a first IP address allocated by the trusted non-3GPP access network to the UE; The trusted non-3GPP access network sends a second IP address request message, and receives a second IP address allocated by the 3GPP core network to the UE; the UE transmits a data packet encapsulated by the tunnel, where the datagram The source IP address or the destination IP address of the text is the second IP address, and the source IP address or the destination IP address of the tunnel is the first IP address.

Preferably, the UE sends a first IP address request message to the trusted non-3GPP access network, and receiving the first IP address allocated by the trusted non-3GPP access network to the UE includes: The controller/broadband network gateway AC/BNG sends a first IP address request message, obtains a first IP address allocated by the AC/BNG to the UE, or the UE accesses a trusted wireless local area network WLAN access gateway TWAG, Sending a first IP address request message, and acquiring a first IP address allocated by the TWAG' to the UE.

Preferably, before the UE transmits the data packet encapsulated by the tunnel, the method further includes: receiving, by the UE, information about the tunnel allocated by the trusted non-3GPP access network to the UE, where The tunnel information is allocated to the UE after the trusted non-3GPP access network receives the first IP address request message sent by the UE.

Preferably, when the UE sends the first IP address request message to the AC/BNG, the AC/BNG sends a Radius request message to the trusted WLAN access gateway TWAG, and receives the tunnel allocated by the TWAG′ Information.

Preferably, the information of the tunnel includes: a key of the tunnel and/or a local IP address of the tunnel.

Preferably, the first IP address request message and the second IP address request message are all associated by a packet data network PDN connection identifier or are associated by the information of the tunnel.

Preferably, the first IP address request message includes: a dynamic host setup protocol (DHCP) message; and the second IP address request message includes: the DHCP message. Preferably, before the sending, by the UE, the first IP address request message to the trusted non-3GPP access network, or sending the first IP address to the trusted non-3GPP access network by the UE When requesting a message, the UE transmits access point name (APN) information through at least one of the following messages: Institute of Electrical and Electronics Engineers (IEEE) 802.11 message, Dynamic Host Setup Protocol (DHCP) message, Extended Authentication Protocol (EAP) message .

According to still another aspect of the embodiments of the present invention, a data message transmission method is provided, including: a trusted non-third generation partner 3GPP access network receives a first Internet Protocol IP address request message sent by a user equipment UE, Allocating a first IP address to the UE; the trusted non-3GPP access network receiving a second IP address request message sent by the UE, sending a session request message to the 3GPP core network, and receiving the 3GPP core network as a second IP address allocated by the UE; the trusted non-3GPP access network transmits a data packet encapsulated by the tunnel, where the source IP address or the destination IP address of the data packet is a second IP address. The source IP address or destination IP address of the tunnel is the first IP address.

Preferably, before the trusted non-3GPP access network transmits the data packet encapsulated by the tunnel, the method further includes: the trusted non-3GPP access network receiving the first IP address sent by the UE After the request message, the UE is assigned information of the tunnel.

Preferably, the first IP address request message includes: a dynamic host setup protocol DHCP message; and the second IP address request message includes: the DHCP message.

According to still another aspect of the present invention, a method for processing a PDN connection identifier is provided, including: a user equipment (UE) sends a message carrying an access point name APN information to an AC/BNG through an AP/RG; Receiving the trusted WLAN access gateway TWAG' forwarding a first PDN connection identifier corresponding to the APN information that is allocated by the AC/BNG; or the second PDN connection identifier corresponding to the APN information that is allocated by the TWAG', where the second PDN connection identifier is The TWAG is allocated after receiving the message that the AC/BNG sends the APN information.

Preferably, the UE sends the message carrying the access point name APN information to the AC/BNG through the AP/RG. The UE sends the GAS-ANQP initial request message carrying the APN information to the AP/RG. And triggering, by the AP/RG, to send a CAPWAP WTP event request or a Radius request message carrying the APN information to the AC/BNG.

Preferably, the receiving, by the UE, the first PDN connection identifier corresponding to the APN information that is forwarded by the AC/BNG that is forwarded by the TWAG of the UE includes: the UE receiving the AP/RG corresponding to the GAS-ANQP a GAS-ANQP initial response message of the initial request message, where the GAS-ANQP initial response message is that the AP/RG receives the CAPWAP WTP event response corresponding to the CAPWAP WTP event request sent by the AC/BNG or And corresponding to the Radius response message of the Radius request message, sent to the AP/RG, and the CAPWAP WTP event response and the Radius response message both carry the first PDN connection identifier; the CAPWAP WTP event response And the Radius response message is sent by the AC/BNG to the AC/BNG after receiving the TWAG and transmitting the Radius authentication response message carrying the first PDN connection identifier.

Preferably, the receiving, by the UE, the second PDN connection identifier corresponding to the APN information that is allocated by the TWAG' includes: receiving, by the UE, the GAS-ANQP initial corresponding to the GAS-ANQP initial request message sent by the AP/RG a response message, where the GAS-ANQP initial response message is that the AP/RG receives the CAPWAP WTP event response corresponding to the CAPWAP WTP event request sent by the AC/BNG or corresponds to the Radius request message. After the Radius response message is sent to the AP/RG, and the CAPWAP WTP event response and the Radius response message both carry the second PDN connection identifier; the CAPWAP The WTP event response and the Radius response message are sent by the AC/BNG to the AC/BNG after receiving the Radius authentication response message sent by the TWAG' carrying the second PDN connection identifier.

Preferably, the first PDN connection identifier and the second PDN connection identifier are one of the following: a default bearer identifier of the first GTP session or a session identifier of the PMIP session triggered by the PDN connection, and an Institute of Electrical and Electronics Engineers IEEE 802. llu message identifier, xid of DHCP message, client connection identifier client id, interface identifier interceptce id.

According to still another aspect of the present invention, a method for processing a PDN connection identifier is provided, including: an access controller/broadband network gateway (AC/BNG) receiving user equipment (UE) carrying the AP/RG forwarding a message having an access point name (APN) information; the AC/BNG assigns a corresponding first PDN connection identifier to the APN information; or the AC/BNG sends a message carrying the APN information to the trusted one. Wireless local area network access gateway TWAG', receiving a second PDN connection identifier corresponding to the APN information allocated by the TWAG'; the AC/BNG identifying the first PDN connection identifier or the second PDN connection identifier Sent to the UE.

Preferably, the AC/BNG receiving message that the user equipment UE forwards through the AP/RG and carrying the APN information includes: the AC/BNG receiving the CAPWAP WTP event request or the Radius that is sent by the AP/RG and carrying the APN information. a request message, wherein the CAPWAP WTP event request or the Radius request message is sent by the AP/RG to the AP/RG after receiving the GAS-ANQP initial request message that is sent by the UE and carrying the APN information. Sent.

Preferably, the AC/BNG sends a message carrying the APN information to the TWAG, including: the AC/BNG transmitting a Radius authentication request message carrying the APN information to the TWAG'; Receiving, by the BNG, the second PDN connection identifier corresponding to the APN information that is allocated by the TWAG' includes: the AC/BNG receiving a Radius authentication response message corresponding to the Radius authentication request message sent by the TWAG′, where , the Radius The authentication response message carries a second PDN connection identifier.

Preferably, the sending, by the AC/BNG, the first PDN connection identifier or the second PDN connection identifier to the UE includes: the AC/BNG corresponding to a CAPWAP WTP event response of the CAPWAP WTP event request or corresponding to the Transmitting, by the GAS-ANQP initial response message of the Radius response message of the Radius request message, the first PDN connection identifier or the second PDN connection identifier to the UE, where the CAPWAP WTP event response and the Radius The response message carries the first PDN connection identifier or the second PDN connection identifier.

According to another aspect of the present invention, a data message transmission apparatus is provided, which is applied to a UE, and includes: a first sending module, configured to send a first to a trusted non-3rd generation partner 3GPP access network An Internet Protocol IP address request message; a first receiving module, configured to receive a first IP address assigned by the trusted non-3GPP access network to the UE; a second sending module, configured to be to the trusted non The 3GPP access network sends a second IP address request message; the second receiving module is configured to receive a second IP address allocated by the 3GPP core network for the UE; the first transmission module is configured to transmit a data packet encapsulated by the tunnel, The source IP address or the destination IP address of the data is the second IP address, and the source IP address or the destination IP address of the tunnel is the first IP address.

Preferably, the first sending module is configured to send a first IP address request message to the AC/BNG; the first receiving module is configured to acquire the first IP address allocated by the AC/BNG to the UE; The first sending module is set to be a trusted wireless local area network access gateway TWAG' Sending the first IP address request message; the first receiving module is configured to acquire the first IP address allocated by the TWAG for the UE.

Preferably, the foregoing apparatus further includes: a third receiving module, configured to receive tunnel information allocated by the trusted non-3GPP access network to the UE, where the tunnel information is the trusted non-3GPP interface After receiving the first IP address request message sent by the UE, the network is allocated for the UE.

According to another aspect of the present invention, a data message transmission apparatus is provided, which is applied to a trusted non-3rd generation partner 3GPP access network, and includes: a fourth receiving module, configured to receive a user equipment, and send the UE a first Internet Protocol IP address request message; a first allocation module, configured to allocate a first IP address to the UE; a fifth receiving module, configured to receive a second IP address request message sent by the UE; a module, configured to send a session request message to the 3GPP core network; a sixth receiving module, configured to acquire a second IP address allocated by the 3GPP core network to the UE; and a second transmission module configured to transmit data encapsulated through the tunnel The packet, where the source IP address or the destination IP address of the data is the second IP address, and the source IP address or the destination IP address of the tunnel is the first IP address.

Preferably, the foregoing apparatus further includes: a second allocation module, configured to allocate the information of the tunnel to the UE after receiving the first IP address request message sent by the UE.

According to a further aspect of the present invention, a processing apparatus for a PDN connection identifier is further provided, which is applied to a UE, and includes: a fourth sending module, configured to send, by using an AP/RG, a message carrying an access point name APN information to AC/BNG;

a seventh receiving module, configured to receive a first PDN connection identifier corresponding to the APN information allocated by the AC/BNG forwarded by the trusted WLAN access gateway TWAG′, or an eighth receiving module, configured to receive the TWAG, The second PDN connection identifier corresponding to the allocated APN information, where the second PDN connection identifier is the TWAG, and is allocated after receiving the message that the AC/BNG sends the APN information. Preferably, the fourth sending module includes: a fifth sending module, configured to send a GAS-ANQP initial request message carrying the APN information to the AP/RG, triggering the AP/RG to carry A CAPWAP WTP event request or a Radius request message describing the APN information is sent to the AC/BNG.

Preferably, the seventh receiving module is configured to receive a GAS-ANQP initial response message corresponding to the GAS-ANQP initial request message sent by the AP/RG, where the GAS-ANQP initial response message is the AP/ Receiving, by the RG, the CAPWAP WTP event response corresponding to the CAPWAP WTP event request or the Radius response message corresponding to the Radius request message sent by the AC/BNG, and sending the CAPWAP to the AP/RG The WTP event response and the Radius response message both carry the first PDN connection identifier; the CAPWAP WTP event response and the Radius response message are that the AC/BNG receives the TWAG, and the sent carries the first PDN connection. After the identified Radius authentication response message is sent to the AC/BNG.

Preferably, the eighth receiving module is configured to receive a GAS-ANQP initial response message that is sent by the AP/RG and that is corresponding to the GAS-ANQP initial request message, where the GAS-ANQP initial response message is After receiving the CAPWAP WTP event response corresponding to the CAPWAP WTP event request or the Radius response message corresponding to the Radius request message sent by the AC/BNG, the AP/RG sends the message to the AP/RG. The CAPWAP WTP event response and the Radius response message both carry the second PDN connection identifier; the CAPWAP WTP event response and the Radius response message are that the AC/BNG receives the TWAG, and the sent carries the second After the PDN connection identifies the Radius authentication response message, it is sent to the AC/BNG.

According to still another aspect of the present invention, a processing apparatus for a PDN connection identifier is further provided, which is applied to an access controller/broadband network gateway (AC/BNG), and includes: a ninth receiving module, configured to receive a UE by A message carried by the AP/RG carrying the access point name APN information; a third allocation module, configured to allocate a corresponding first PDN connection identifier for the APN information; or a sixth sending module, configured to send a message carrying the APN information to a trusted wireless local area network access gateway TWAG', a tenth receiving module, configured to receive the TWAG, the allocated second PDN connection identifier corresponding to the APN information, and a seventh sending module, configured to set the first PDN connection identifier or the second PDN connection identifier Sent to the UE.

Preferably, the ninth receiving module is configured to receive a CAPWAP WTP event request or a Radius request message that is sent by the AP/RG and that carries the APN information, where the CAPWAP WTP event request or the Radius request message is the After receiving the GAS-ANQP initial request message that is sent by the UE and carrying the APN information, the AP/RG sends the message to the AP/RG.

Preferably, the sixth sending module is configured to send a Radius authentication request message carrying the APN information to the TWAG, and the tenth receiving module is configured to receive the corresponding TWAG' assigned to the The second PDN connection identifier of the APN information includes: the AC/BNG receives a Radius authentication response message that is sent by the TWAG and corresponds to the Radius authentication request message, where the Radius authentication response message carries a second PDN connection identifier.

Preferably, the seventh sending module is configured to connect the first PDN by using a CAPWAP WTP event response corresponding to the CAPWAP WTP event request or a GAS-ANQP initial response message corresponding to the Radius response message of the Radius request message. The identifier or the second PDN connection identifier is sent to the UE, where the CAPWAP WTP event response and the Radius response message both carry the first PDN connection identifier or the second PDN connection identifier.

The embodiment of the present invention uses the UE to send a first IP address request message to a trusted non-3GPP access network, and receives a first IP address assigned by the trusted non-3GPP access network to the UE, and then the UE passes the trusted non- The 3GPP access network sends a second IP address request message to obtain 3GPP The second IP address assigned by the core network to the UE is implemented, and the different PDNs of the UE are distinguished by different IP addresses, so that the reliability of the data packet transmission by the UE through the trusted non-3GPP access network is relatively poor. The problem is that the reliability of the data packet transmission is improved, and the problem that the reliability of the data packet transmission by the UE through the non-3GPP access network is relatively poor is solved, thereby improving the UE to transmit the datagram through the non-3GPP access network. The effect of the reliability of the text. DRAWINGS

1 is a network structure diagram of a related art 3GPP network interworking with a non-3GPP network; FIG. 2 is a schematic diagram of an architecture of a related art UE accessing an EPC through a trusted WLAN; FIG. 3 is a data packet according to an embodiment of the present invention; FIG. 4 is a second flowchart of a data message transmission method according to an embodiment of the present invention; FIG. 5 is a first structural block diagram of a data message transmission apparatus according to an embodiment of the present invention; A preferred first block diagram of a data message transmission apparatus according to an embodiment of the present invention; FIG. 7 is a second structural block diagram of a data message transmission apparatus according to an embodiment of the present invention; and FIG. 8 is data according to an embodiment of the present invention. A preferred second block diagram of a message transmission apparatus; FIG. 9 is a first flowchart of a PDN connection identifier processing method according to an embodiment of the present invention; FIG. 10 is a second flowchart of a connection identifier processing method according to an embodiment of the present invention; 11 is a first structural block diagram of a connection identification processing apparatus according to an embodiment of the present invention; FIG. 12 is an overview of a connection identification processing apparatus according to an embodiment of the present invention; A first frame structure of FIG;

13 is a second structural block diagram of a connection identification processing apparatus according to an embodiment of the present invention; FIG. 14 is a flowchart 1 of a flow of a UE accessing an EPC through a trusted WLAN according to an embodiment of the present invention;

15 is a flowchart 2 of a process for a UE to access an EPC through a trusted WLAN according to an embodiment of the present invention;

16 is a diagram of a UE accessing an EPC through a trusted WLAN according to an embodiment of the present invention. Flow chart 3 of the process;

17 is a flowchart 4 of a process for a UE to access an EPC through a trusted WLAN according to an embodiment of the present invention;

18 is a flowchart 5 of a process for a UE to access an EPC through a trusted WLAN according to an embodiment of the present invention;

FIG. 19 is a flowchart 6 of a process for a UE to access an EPC through a trusted WLAN according to an embodiment of the present invention; FIG.

20 is a flowchart 7 of a process for a UE to access an EPC through a trusted WLAN according to an embodiment of the present invention;

21 is a flowchart 8 of a process for a UE to access an EPC through a trusted WLAN according to an embodiment of the present invention;

22 is a flowchart IX of a process for a UE to access an EPC through a trusted WLAN according to an embodiment of the present invention;

23 is a flowchart 10 of a process for a UE to access an EPC through a trusted WLAN according to an embodiment of the present invention;

24 is a flowchart 10 of a process for a UE to access an EPC through a trusted WLAN according to an embodiment of the present invention;

25 is a flowchart 11 of a process for a UE to access an EPC through a trusted WLAN according to an embodiment of the present invention; and

26 is a flowchart 12 of a flow of a UE accessing an EPC through a trusted WLAN according to an embodiment of the present invention. detailed description

The invention will be described in detail below with reference to the drawings in conjunction with the embodiments. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict.

This embodiment provides a data packet transmission method, and FIG. 3 is a diagram according to an embodiment of the present invention. A first flowchart of the data message transmission method, as shown in FIG. 3, the method includes the following steps S302 to S306.

Step S302: The UE sends a first IP address request message to the trusted non-3GPP access network, and receives the first IP address allocated by the trusted non-3GPP access network to the UE.

Step S304: The UE sends a second IP address request message to the trusted non-3GPP access network, and receives a second IP address allocated by the 3GPP core network to the UE.

Step S306: The UE transmits the data packet encapsulated by the tunnel, where the source IP address or the destination IP address of the data packet is the second IP address, and the source IP address or the destination IP address of the tunnel is the first IP address.

Through the above steps, the UE sends a first IP address request message to the trusted non-3GPP access network, receives the first IP address allocated by the trusted non-3GPP access network for the UE, and then the UE passes the trusted non-3GPP. The access network sends a second IP address request message, and receives a second IP address assigned by the 3GPP core network to the UE, so that different PDNs of the UE are distinguished by different IP addresses, thereby solving the related technology in which the UE passes the trusted non-3GPP. The access network has a relatively poor reliability of data packet transmission, which improves the reliability of data packet transmission.

In order to achieve the flexibility of the UE to receive the first IP address, the first IP address request message may be sent to the trusted non-3GPP access network by receiving the first IP address:

Manner 1: The UE sends a first IP address request message to the AC/BNG, and obtains a first IP address allocated by the AC/BNG to the UE.

Manner 2: The UE sends a first IP address request message to the trusted WLAN access gateway TWAG' to obtain the first IP address allocated by the TWAG for the UE.

In order to achieve the reliability of the data packet transmission, before the step S306, the UE receives the information of the tunnel allocated by the trusted non-3GPP access network for the UE, where the tunnel information is the trusted non-3GPP interface. The network is allocated to the UE after receiving the first IP address request message sent by the UE. Preferably, when the UE sends the first IP address request message to the AC/BNG, the AC/BNG sends a Radius request message to the trusted WLAN access gateway TWAG, and receives the tunnel allocated by the TWAG′ Information.

Preferably, the first IP address request message and the second IP address request message are all associated by the packet data network PDN connection identifier or are associated by the information of the tunnel.

In implementation, a variety of messages may be employed as the first IP address request message, such as: Dynamic Host Setup Protocol (DHCP) messages.

In implementation, a variety of messages may be employed as the second IP address request message. For example: DHCP message.

As a preferred implementation manner, before the UE sends the first IP address request message to the trusted non-3GPP access network, or the UE sends the first IP address request to the trusted non-3GPP access network. In the message, the UE transmits the access point name APN information through at least one of the following messages: Institute of Electrical and Electronics Engineers (IEEE) 802.11 message, Dynamic Host Setup Protocol (DHCP) message, Extended Authentication Protocol EAP message.

The present embodiment provides a data packet transmission method. FIG. 4 is a second flowchart of a data packet transmission method according to an embodiment of the present invention. As shown in FIG. 4, the method includes the following steps S402 to S406.

Step S402: The trusted non-3GPP access network receives the first IP address request message sent by the user equipment UE, and allocates the first IP address to the UE.

Step S404: The trusted non-3GPP access network receives the second IP address request message sent by the UE, sends a session request message to the 3GPP core network, and receives a second IP address allocated by the 3GPP core network to the UE.

Step S406: The trusted non-3GPP access network transmits the data packet encapsulated by the tunnel. The source IP address or the destination IP address of the data is the second IP address, and the source IP address or the destination IP address of the tunnel is the first IP address.

Through the above steps, the different PDNs of the UE are distinguished by different IP addresses, thereby solving the problem that the reliability of the data transmission of the UE through the trusted non-3GPP access network is relatively poor in the related art, and the data packet transmission is improved. Reliability.

In order to achieve the reliability of the data packet transmission, the trusted non-3GPP access network receives the number sent by the UE before the trusted non-3GPP access network transmits the data packet encapsulated by the tunnel. After an IP address request message, the information of the tunnel is allocated to the UE.

Preferably, the information of the tunnel includes: a key of the tunnel and/or a local IP address of the tunnel. Preferably, the first IP address and the second IP address may be associated by a PDN connection identifier or associated by tunnel information.

It should be noted that the steps shown in the flowchart of the accompanying drawings may be performed in a computer system such as a set of computer executable instructions, and, although the logical order is shown in the flowchart, in some cases, The steps shown or described may be performed in an order different than that herein.

In another embodiment, a data message transmission software is provided for performing the technical solutions described in the above embodiments and preferred embodiments.

In another embodiment, a storage medium is provided, in which the data message transmission software is stored, including but not limited to: an optical disk, a floppy disk, a hard disk, a rewritable memory, and the like.

The embodiment of the invention further provides a data message transmission device, which can be applied to a UE, and the data message transmission device can be used to implement the data message transmission method and the preferred implementation. The method has been described, and will not be described again. The modules involved in the data message transmission device will be described below. As used below, the term "module" may implement a combination of software and/or hardware of a predetermined function. Although the systems and methods described in the following embodiments are preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.

FIG. 5 is a first structural block diagram of a data message transmission apparatus according to an embodiment of the present invention. As shown in FIG. 5, the apparatus includes: a first sending module 52, a first receiving module 54, a second sending module 56, and a second The receiving module 58, the first transmitting module 59, will be described in detail below.

The first sending module 52 is configured to send a first Internet Protocol IP address request message to the trusted non-3rd generation partner 3GPP access network; the first receiving module 54 is connected to the first sending module 52, and is configured to receive The first IP address assigned by the trusted non-3GPP access network to the UE; the second sending module 56 is configured to send a second IP address request message to the trusted non-3GPP access network; the second receiving module The second transmission module 56 is configured to receive the second IP address assigned by the 3GPP core network to the UE. The first transmission module 59 is connected to the first receiving module 54 and the second receiving module 58 and configured to transmit The data packet encapsulated by the tunnel, where the source IP address or the destination IP address of the data is the second IP address, and the source IP address or the destination IP address of the tunnel is the first IP address.

Preferably, the first sending module 52 is configured to send a first IP address request message to the AC/BNG; the first receiving module 54 is configured to obtain the first IP address allocated by the AC/BNG to the UE.

Preferably, the first sending module 52 is configured to send the first IP address request message to the trusted WLAN access gateway TWAG'; the first receiving module 54 is configured to acquire the TWAG, the first IP address allocated for the UE.

FIG. 6 is a first block diagram of a first structure of a data message transmission apparatus according to an embodiment of the present invention. As shown in FIG. 6, the apparatus further includes: a third receiving module 62 connected to the first transmission module 59, configured to receive The tunnel information allocated by the trusted non-3GPP access network to the UE, where The tunnel information is allocated to the UE after the trusted non-3GPP access network receives the first IP address request message sent by the UE.

The embodiment of the invention further provides a data message transmission device, which can be applied to a trusted non-3GPP access network, and the data message transmission device can be used to implement the data message transmission method and a preferred implementation manner. The description has been made and will not be described again. The modules involved in the data message transmission device will be described below. As used hereinafter, the term "module" can implement a combination of software and/or hardware for a predetermined function. Although the systems and methods described in the following embodiments are preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.

FIG. 7 is a second structural block diagram of a data message transmission apparatus according to an embodiment of the present invention. As shown in FIG. 7, the apparatus includes: a fourth receiving module 72, a first allocation module 74, a fifth receiving module 76, and a third The transmitting module 78, the sixth receiving module 79, and the second transmitting module 70, the above structure will be described in detail below.

The fourth receiving module 72 is configured to receive a first Internet Protocol IP address request message sent by the UE. The first allocating module 74 is connected to the second receiving module 72, and is configured to allocate a first IP address to the UE. 76. The third sending module 78 is configured to receive the second IP address request message sent by the UE, and the third sending module 78 is configured to send a session request message to the 3GPP core network. The sixth receiving module 79 is connected. The third sending module 76 is configured to obtain the second IP address allocated by the 3GPP core network to the UE. The second transmitting module 70 is connected to the first allocating module 74 and the sixth receiving and acquiring module 78, and is configured to transmit through the tunnel. Number of packages According to the packet, the source IP address or the destination IP address of the data packet is the second IP address, and the source IP address or the destination IP address of the tunnel is the first IP address.

FIG. 8 is a block diagram of a second preferred structure of a data message transmission apparatus according to an embodiment of the present invention. As shown in FIG. 8, the apparatus further includes: a second allocation module 82 connected to the second transmission module 79, configured to be After receiving the first IP address request message sent by the UE, the information about the tunnel is allocated to the UE.

The present embodiment provides a method for processing a PDN connection identifier. FIG. 9 is a first flowchart of a method for processing a PDN connection identifier according to an embodiment of the present invention. As shown in FIG. 9, the method includes the following steps S902 to S904. .

Step S902: The UE sends a message carrying the APN information to the AC/BNG through the Access Point/Residential Gateway (AP/RG).

Step S904: The UE receives the TWAG, and forwards the first PDN connection identifier corresponding to the APN information that is allocated by the AC/BNG; or the UE receives the second PDN connection identifier corresponding to the APN information that is allocated by the TWAG, where the second The PDN connection identifier is the TWAG, and is allocated after receiving the message that the AC/BNG sends the APN information.

Through the above steps, the UE sends a message carrying the access point name APN information to the AC/BNG through the AP/RG, and then receives the TWAG, and forwards the first PDN connection identifier or the corresponding corresponding to the APN information allocated by the AC/BNG. The second PDN connection identifier corresponding to the APN information allocated by the TWAG' solves the problem that the AC/BNG cannot obtain the APN in the related art and cannot allocate the PDN connection identifier.

In the implementation, the UE may send the message carrying the access point name APN information to the AC/BNG through the AP/RG. In the preferred embodiment, the UE performs the following information: The UE will carry the APN information. The GAS-ANQP initial request message is sent to the AP/RG, and the AP/RG is triggered to send a CAPWAP WTP event request or a Radius request message carrying the APN information to the AC/BNG. Corresponding to the above-mentioned preferred embodiment, in implementation, the UE may implement the first PDN connection identifier corresponding to the APN information that is received by the AC/BNG that is forwarded by the trusted TWAG': the UE receives the corresponding information sent by the AP/RG. The GAS-ANQP initial response message of the Access Network Query Protocol (ANQP) initial request message, where the GAS-ANQP initial response message is carried in the Generic Advertisement Service (GAS) There is the first PDN connection identifier, and the GAS-ANQP initial response message is that the AP/RG receives the control and provisioning corresponding to the wireless access point sent by the AC/BNG (Control And Provisioning of Wireless Access Points, referred to as CAPWAP) Wireless Termination Point (WTP) event request CAPWAP WTP event response or Radius response message corresponding to the Radius request message, sent to the AP/RG, and the CAPWAP WTP event response and remote The Remote Authentication Dial In User Service (Radius) response message carries the The first PDN connection identifier; the CAPWAP WTP event response and the Radius response message are sent by the AC/BNG to the AC/BNG after receiving the Radius authentication response message carrying the first PDN connection identifier.

As a preferred implementation manner, the UE may receive the second PDN connection identifier corresponding to the APN information allocated by the TWAG′ by: receiving, by the UE, the GAS-ANQP corresponding to the GAS-ANQP initial request message sent by the AP/RG. The initial response message, the GAS-ANQP initial response message carries a second PDN connection identifier, and the GAS-ANQP initial response message is that the AP/RG receives the CAPWAP WTP corresponding to the CAPWAP WTP event request sent by the AC/BNG. After the event response or the Radius response message corresponding to the Radius request message, sent to the AP/RG, and the CAPWAP WTP event response and the Radius response message both carry the second PDN connection identifier; the CAPWAP WTP event response and the Radius The response message is sent by the AC/BNG to the AC/BNG after receiving the Radius authentication response message sent by the TWAG' carrying the second PDN connection identifier. In implementation, a plurality of information that can identify the PDN connection may be used as the first PDN connection identifier and the second PDN connection identifier, for example, the default bearer identifier of the first GTP session established by the PDN connection or the session identifier of the PMIP session. , Institute of Electrical and Electronics Engineers (IEEE) 802.llu message identification, xid of DHCP message, client connection ID (client id), interface identifier (interferce id).

The preferred embodiment of the present invention provides a PDN connection identifier processing method. FIG. 10 is a second flowchart of a PDN connection identifier processing method according to an embodiment of the present invention. As shown in FIG. 10, the method includes the following steps S1002 to S1006.

Step S1002: The AC/BNG receives the message carrying the APN information forwarded by the UE through the AP/RG.

Step S1004: The AC/BNG allocates a corresponding first PDN connection identifier for the APN information; or the AC/BNG sends a message carrying the APN information to the TWAG, and receives the TWAG, and the allocated corresponding to the APN information. Two PDN connection identifiers.

Step S1006: The AC/BNG sends the first PDN connection identifier or the second PDN connection identifier to the UE.

Through the above steps, the AC/BNG receives the message carrying the APN information forwarded by the AP/RG, and then assigns the corresponding first PDN connection identifier or the TWAG to the APN information, and the allocated second PDN connection identifier corresponding to the APN information. The problem that the AC/BNG cannot obtain the APN and cannot allocate the PDN connection identifier in the related technology is solved.

In the implementation, the AC/BNG can receive the message carrying the APN information that is forwarded by the UE through the AP/RG in multiple manners. The preferred embodiment provides the following implementation manner: The AC/BNG receives the carried by the AP/RG. a CAPWAP WTP event request or a Radius request message of the APN information, where the CAPWAP WTP event request or the Radius request message is after the AP/RG receives the GAS-ANQP initial request message that is sent by the UE and carries the APN information, Sent to the AP/RG. As a preferred implementation manner, the AC/BNG may send the message carrying the APN information to the TWAG in the following manner: The AC/BNG may send a Radius authentication request message carrying the APN information to the TWAG. Corresponding to the preferred embodiment manner, the AC/BNG may receive the second PDN connection identifier corresponding to the APN information allocated by the TWAG' by: the AC/BNG receiving the Radius authentication request message sent by the TWAG′ The Radius authentication response message, wherein the Radius authentication response message carries a second PDN connection identifier.

In implementation, the AC/BNG may send the first PDN connection identifier or the second PDN connection identifier to the UE in multiple implementation manners. In the preferred embodiment, the AC/BNG will correspond to the CAPWAP WTP event request. The CAPWAP WTP event response or the Radius response message corresponding to the Radius request message is sent to the AP/RG, and the AP/RG is triggered to identify the first PDN connection by using the GAS-ANQP initial response message corresponding to the GAS-ANQP initial request message. Or the second PDN connection identifier is sent to the UE, where the CAPWAP WTP event response and the Radius response message both carry the first PDN connection identifier or the second PDN connection identifier.

In implementation, a plurality of information that can identify the PDN connection may be used as the first PDN connection identifier and the second PDN connection identifier, for example, the first general packet radio service tunneling protocol established by the PDN connection triggering (General Packet Radio Service Tunneling Protocol) , referred to as GTP for the default bearer identifier of the session or the session identifier of the PMIP session, the Institute of Electrical and Electronics Engineers (IEEE) 802. l lu message identifier, the xid of the DHCP message, the client connection identifier (client id), the interface identifier ( Interferce id ).

In another embodiment, a PDN connection identification processing software is also provided, which is used to implement the technical solutions described in the above embodiments and preferred embodiments.

In another embodiment, a storage medium is further provided, where the PDN connection identifier processing software is stored, including but not limited to: an optical disc, a floppy disk, and a hard disk. Disk, rewritable memory, etc.

The embodiment of the present invention further provides a PDN connection identifier processing device, which may be applied to a UE. The PDN connection identifier processing device may be used to implement the PDN connection identifier processing method and a preferred implementation manner. Further, the modules involved in the PDN connection identifier processing apparatus will be described below. As used hereinafter, the term "module" can implement a combination of software and/or hardware of a predetermined function. Although the systems and methods described in the following embodiments are preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.

FIG. 11 is a first structural block diagram of a PDN connection identifier processing apparatus according to an embodiment of the present invention. As shown in FIG. 11, the apparatus includes: a fourth sending module 112, a seventh receiving module 114, and an eighth receiving module 116. The above structure will be described in detail.

The fourth sending module 112 is configured to send, by the AP/RG, a message carrying the access point name APN information to the AC/BNG; the seventh receiving module 114 is connected to the fourth sending module 112, and is configured to receive the TWAG' forwarding. The first PDN connection identifier corresponding to the APN information allocated by the AC/BNG; or the eighth receiving module 116 is connected to the fourth sending module 112, and configured to receive the second PDN connection identifier corresponding to the APN information allocated by the TWAG′, The second PDN connection identifier is the TWAG, and is allocated after receiving the message that is sent by the AC/BNG and carrying the APN information.

FIG. 12 is a first block diagram of a first structure of a data packet transmission apparatus according to an embodiment of the present invention. As shown in FIG. 12, the fourth sending module 112 includes: a fifth sending module 1122, connected to the information for carrying the APN. The GAS-ANQP initial request message is sent to the AP/RG, and the AP/RG is triggered to send a CAPWAP WTP event request or a Radius request message carrying the APN information to the AC/BNG.

Preferably, the seventh receiving module 114 is configured to receive a GAS-ANQP initial response message corresponding to the GAS-ANQP initial request message sent by the AP/RG; The GAS-ANQP initial response message is sent by the AP/RG to the AP/RG after receiving the CAPWAP WTP event response corresponding to the CAPWAP WTP event request sent by the AC/BNG or the Radius response message corresponding to the Radius request message. And the CAPWAP WTP event response and the Radius response message both carry the first PDN connection identifier; the CAPWAP WTP event response and the Radius response message are that the AC/BNG receives the TWAG, and the sent carries the first PDN connection. After the identified Radius authentication response message is sent to the AC/BNG.

Preferably, the eighth receiving module 116 is configured to receive a GAS-ANQP initial response message corresponding to the GAS-ANQP initial request message sent by the AP/RG, where the GAS-ANQP initial response message is that the AP/RG receives the After the CAPWAP WTP event response corresponding to the CAPWAP WTP event request or the Radius response message corresponding to the Radius request message sent by the AC/BNG, sent to the AP/RG, and the CAPWAP WTP event response and the Radius response message are both Carrying the second PDN connection identifier; the CAPWAP WTP event response and the Radius response message are sent to the AC/BNG after the AC/BNG receives the TWAG and sends the Radius authentication response message carrying the second PDN connection identifier. Sent.

In another embodiment, a storage medium is provided, in which the PDN connection identification processing software is stored, including but not limited to: an optical disk, a floppy disk, a hard disk, a rewritable memory, and the like.

The embodiment of the present invention further provides a PDN connection identifier processing device, which can be applied to an AC/BNG, and the PDN connection identifier processing device can be used to implement the foregoing PDN connection identifier processing method and a preferred implementation manner. , and will not be described again. The following describes the modules involved in the PDN connection identifier processing device. As used below, the term "module" may implement a combination of software and/or hardware for a predetermined function. Although the systems and methods described in the following embodiments are preferably implemented in software, hardware, or a combination of software and hardware, is also implemented. It is possible and conceived.

FIG. 13 is a second structural block diagram of a data message transmission apparatus according to an embodiment of the present invention. As shown in FIG. 13, the apparatus includes: a ninth receiving module 131, a third allocating module 132, a sixth sending module 133, and a tenth The receiving module 134 and the seventh transmitting module 135, the above structure will be described in detail below.

The ninth receiving module 131 is configured to receive a message that the user equipment UE forwards through the AP/RG and carries the access point name APN information. The third allocation module 132 is connected to the ninth receiving module 131, and is configured to allocate the APN information. Corresponding first PDN connection identifier; or sixth sending module 133, connected to the ninth receiving module 131, configured to send the message carrying the APN information to the TWAG', and the tenth receiving module 134 is configured to receive the TWAG' The second PDN connection identifier corresponding to the APN information is allocated; the seventh sending module 135 is connected to the third allocating module 132 and the tenth sending module 134, and is configured to allocate the first PDN connection identifier by the third allocating module 132. Or the second PDN connection identifier received by the tenth receiving module 134 is sent to the UE.

Preferably, the ninth receiving module 131 is configured to receive a CAPWAP WTP event request or a Radius request message that is sent by the AP/RG and that carries the APN information, where the CAPWAP WTP event request or the Radius request message is that the AP/RG is receiving After the GAS-ANQP initial request message carrying the APN information sent by the UE is sent to the AP/RG.

Preferably, the sixth sending module 133 is configured to send the Radius authentication request message carrying the APN information to the TWAG, and the tenth receiving module 134 is configured to receive the TWAG, and the second corresponding to the APN information is allocated. The PDN connection identifier includes: the AC/BNG receives the Radius authentication response message sent by the TWAG' corresponding to the Radius authentication request message, where the Radius authentication response message carries the second PDN connection identifier.

Preferably, the seventh sending module 135 is configured to send a CAPWAP WTP event response corresponding to the CAPWAP WTP event request or a Radius response message corresponding to the Radius request message to the AP/RG, and trigger the AP/RG to pass the corresponding GAS- ANQP initial request message The GAS-ANQP initial response message sends the first PDN connection identifier or the second PDN connection identifier to the UE, where the CAPWAP WTP event response and the Radius response message both carry the first PDN connection identifier or the second PDN connection identifier.

The following description will be made in conjunction with the preferred embodiments, and the following preferred embodiments incorporate the above-described embodiments and preferred embodiments.

Preferred embodiment 1

The present invention provides a method for a UE to perform multiple PDN connections through a trusted non-3GPP access mobile network.

For the UE side, the method includes the following steps S1 to S5.

Step S1: The UE sends a first IP address request message to the network to request to allocate a local IP address.

Step S3: After obtaining the local IP address, the UE sends a second IP address request message to the network to obtain an IP address assigned by the 3GPP core network.

Step S5: The UE sends an uplink user data packet encapsulated by the tunnel.

For the network side: The method includes the following steps S2 to S6.

Step S2: The network receives the first IP address request message sent by the UE, and locally allocates an IP address to the UE.

Step S4: The network receives the second IP address request message allocated by the UE, and sends an S2a session request message to the 3GPP core network to obtain an IP address assigned by the 3GPP core network.

Step S6: The network sends a downlink user data packet encapsulated by the tunnel.

Preferred embodiment two

The preferred embodiment provides a UE accessing the mobile network through the non-3GPP access network. In this embodiment, the UE is configured to access the EPC through a trusted WLAN, where the dynamic host configuration protocol (Dynamic Host Configuration Protocol) , referred to as DHCP, the access point (Access Point Name, APN for short) and other information, TWAG, for the UE to allocate outside the tunnel Layer 2 (the two DHCP request messages are associated by the PDN connection identifier). FIG. 14 is a flowchart of a process for a UE to access an EPC through a trusted WLAN according to an embodiment of the present invention. As shown in FIG. 14, the method includes The following steps S1401 to S1416 are performed.

Step S1401: Performing a non-3GPP specific process between the UE and the trusted WLAN access network.

Step S1402: The AP/RG functions as an EAP authenticator, and performs an EAP authentication process, where AC/BNG and TWAG can act as AAA agents. In the EAP authentication response message, AC/BNG obtains the determined service type from the 3GPP AAA server. Specifically, it includes: a split service split, or access to the EPC, or both.

Step S1403: S1403a: The UE sends a Solicitation (DHCPv6)/DHCP Discovery (DHCPv4) message to the AC/BNG, which may carry APN information. After the AC/BNG receives the message, it will perform the following specific operations:

If the APN is not carried in the DHCP request message, it is further determined according to the service type of the decision. If the service is split, the IP address is directly allocated to the UE. If the access to the EPC is allowed, As a DHCP relay, forward the DHCP request message to TWAG'.

If the DHCP request message carries the APN, if it considers that it is allowed to access the EPC, it acts as a DHCP relay and forwards the DHCP request message to TWAG'.

Step S1404a - Step S1404: TWAG sends an advertisement (DHCPv6) / DHCP providing message (DHCPv4) to the UE through the AC/BNG, and the message may include the UE IP address 1.

Step S1405-Step S1405a: The UE sends a request (DHCPv6)/DHCP request (DHCPv4) to the TWAG through the AC/BNG, where the message includes the UE IP address 1 and the GRE key (key) on the UE side.

Step S1406a - Step S1406: The TWAG generates a PDN connection identifier locally according to the received APN information. The specific generation principle is as follows: If there is no PDN connection identifier associated with the APN in the TWAG, a new PDN connection identifier is generated;

If there is already a PDN connection identifier associated with the APN in TWAG, then TWAG' considers the additional PDN connection establishment request under the same APN, and a new PDN connection identifier is also generated.

The PDN connection identifier may be the default bearer identifier of the first GTP session established by the PDN connection or the session identifier of the PMIP session, or may be an extended authentication protocol EAP authentication authorization message, a dynamic host setting protocol DHCP message xid, a client The end connection identifies the client id, the interface label i only the interferce id, or the new label i only.

Then, TWAG, reply replies to the UE (DHCPv6) / DHCP acknowledgment (DHCPv4), the message includes UE IP address 1, TWAG, side GRE key, PDN connection identifier, TWAG' user plane address; TWAG, locally save GRE Association of keys, PDN connection identifiers, TWAGs, user plane addresses, and APNs.

Step S1407: The UE sends a request for request (DHCPv6)/DHCP discovery (DHCPv4) to the AC/BNG, where the message carries the PDN connection identifier information. After receiving the message, the AC/BNG forwards the DHCP request message to TWAG' according to the PDN connection identifier carried in the message as a DHCP relay.

Step S1408: After receiving the DHCP request message, the TWAG finds the associated APN and other information according to the PDN connection identifier, and then sends a create session request or a proxy binding update message to the PDN GW, where the message includes the APN.

Step S1409: Perform an IP-CAN session establishment operation between the PDN GW and the PCRF.

Step S1410: The PDN GW updates the PDN GW address to the HSS through the AAA Server. Step S1411: The PDN GW sends a create session response or a proxy binding acknowledgement message to the trusted non-3GPP access network, where the message carries the IP address 2 assigned by the PDN GW to the UE.

Steps S1412-S1413: TWAG, sending an announcement to the UE through the AC/BNG (DHCPv6) /DHCP provides a message (DHCPv4), which contains the UE IP address 2.

Step S1414: The UE sends a request (DHCPv6)/DHCP request (DHCPv4) to the TWAG through the AC/BNG, where the message includes the UE IP address 2.

Step S1415: TWAG, replying to the UE with a reply (DHCPv6)/DHCP acknowledgment (DHCPv4), the message including the UE IP address 2; TWAG' local will save the association between the APN and the UE IP address 2.

Step S1416: The UE and the TWAG perform the uplink and downlink data transmission through the GRE tunnel encapsulation. The UE is responsible for the encapsulation of the uplink data and the decapsulation of the downlink data, and the TWAG is responsible for the encapsulation of the downlink data and the decapsulation of the uplink data.

It should be noted that, in the foregoing embodiment, the GRE key and the TWAG, the user plane address are used for

Information about the GRE tunnel encapsulation.

The above DHCP message may be used only to allocate some parameters other than the IP address, and request the IP address by routing request/routing response message. Then, after step S1406 and S1415, the flow of the route request/routing response message needs to be added. To request an IP address, the other processes that follow will continue after the IP address is obtained.

When the 3GPP network is UMTS, the GGSN can replace the PDN GW in this embodiment, and the functions to be enhanced are the same.

Preferred embodiment three

The preferred embodiment provides a UE accessing the mobile network through the non-3GPP access network. In this embodiment, the UE accesses the EPC through a trusted WLAN, where the DHCP transmits APN and other information, AC. /BNG allocates the outer layer IP address of the tunnel to the UE, and the tunnel encapsulation of the data packet is implemented between the UE and the TWAG. The two DHCP request messages are associated by the PDN connection identifier. FIG. 15 is a trusted UE according to an embodiment of the present invention. Flowchart 2 of the WLAN, the process of accessing the EPC, as shown in FIG. 15, the method includes the following steps S1501 to S1518.

Step S1501: Performing a non-3GPP specific flow between the UE and the trusted WLAN access network Cheng.

In the EAP authentication process, the AC/BNG can act as an AAA proxy. In the EAP authentication response message, the AC/BNG obtains the service type of the decision from the 3GPP AAA server, specifically including the EAP authentication process. : Separated business diversion, or access to EPC, or both.

Step S1503: The UE sends an Solicitation (DHCPv6) / DHCP Discovery (DHCPv4) message to the AC/BNG, which may carry APN information. After receiving the message, the AC/BNG locally saves the APN carried by the UE, which may indicate that the APN is delivered by the UE through a flag, or the source of the APN carried by the UE and the source of the signed APN information are different. Differentiate, then the UE is assigned an IP address of 1 locally.

Step S1504: The AC/BNG sends an advertisement (DHCPv6)/DHCP providing message (DHCPv4) to the UE, and the message may include the UE IP address 1.

Step S1505: The UE sends a request (DHCPv6) / DHCP request (DHCPv4) to the AC/BNG, where the message includes the UE IP address 1 and the UE side GRE key. AC/BNG performs the following specific operations:

If the locally saved APN is from the AAA, it will further judge according to the service type of the decision. If there is a slotted service offload, step S1508 is directly performed; if it is allowed to access the EPC, step S1506 is performed.

If the locally saved APN is from the UE, step S1506 is performed.

Step S1506: The AC/BNG sends a Remote Authentication Dial In User Service (Radio Authentication) authentication request message to the TWAG, and the message carries the APN, the UE IP address 1 and the GRE key of the UE side.

Step S1507: TWAG' replies to the Radius authentication response message to the AC/BNG, and generates a PDN connection identifier locally. For the specific generation principle, refer to the related description of Embodiment 1. The message carries the TWAG' user plane address, the UE side GRE key, and the PDN connection. Logo. Step SI 508: The AC/BNG replies to the UE with a reply (DHCPv6)/DHCP acknowledgment (DHCPv4), and the message includes the UE IP address 1, the TWAG, the side GRE key, the PDN connection identifier, and the TWAG 'user plane address; TWAG, The association between the GRE key, the PDN connection identifier, the TWAG, the user plane address, and the APN is locally saved.

Step S1509-S1518: For details, refer to step S1407 - step S1416.

It should be noted that, in the foregoing embodiment, the GRE key and the TWAG, the user plane address are information used for GRE tunnel encapsulation.

The above DHCP message may only be used to allocate some parameters other than the IP address, and request the IP address by routing request/routing response message. Then, after step S1508 and steps S1517a, S1517b, the routing request/routing response message needs to be added. The process, to request the allocation of an IP address, the other processes that follow to obtain the IP address, continue to execute.

Preferred embodiment four

The preferred embodiment provides a UE accessing the mobile network through the non-3GPP access network. In this embodiment, the UE describes the information such as the trusted WLAN, the access to the EPC, and the DHCP delivery APN. The AC/BNG is the UE. Allocating the outer layer IP of the tunnel (the tunnel between the UE and the AC/BNG, the AC/BNG and the TWAG implements the tunnel encapsulation of the data packet, and the two DHCP request messages are associated by the PDN connection identifier). The preferred embodiment and the preferred implementation The difference between the third embodiment is that the user data is encapsulated in the GRE tunnel between the UE and the AC/BNG, the AC/BNG, and the TWAG. FIG. 16 is a flowchart of the UE accessing the EPC through the trusted WLAN according to the embodiment of the present invention. Flowchart 3, as shown in FIG. 16, the method includes the following steps S1601 to S1618.

Step S1601: A non-3GPP specific process is performed between the UE and the trusted WLAN access network.

Step S 1602: The AP/RG functions as an EAP authenticator, and performs an EAP authentication process, where The AC/BNG can act as an AAA proxy. In the EAP authentication response message, the AC/BNG obtains the service type of the decision from the 3GPP AAA server, including: a split service split, or an access EPC, or both.

Step S1603: The UE sends an Solicitation (DHCPv6)/DHCP Discovery (DHCPv4) message to the AC/BNG, where the APN information may be carried. After receiving the message, the AC/BNG locally saves the APN carried by the UE, which may indicate that the APN is delivered by the UE through a flag, or the source of the APN carried by the UE and the source of the signed APN information are different. Differentiate, then the UE is assigned an IP address of 1 locally.

Step S1604: The AC/BNG sends an advertisement (DHCPv6)/DHCP providing message (DHCPv4) to the UE, and the message may include the UE IP address 1.

Step S1605: The UE sends a request (DHCPv6) / DHCP request (DHCPv4) to the AC/BNG, where the message includes the UE IP address 1 and the UE side GRE key 1. AC/BNG performs the following specific operations:

1) If the locally saved APN is from the AAA, then it is further determined according to the service type of the decision. If there is a slotted service offload, step S1608 is directly performed; if the access to the EPC is allowed, step S1606 is performed. Or S1606a.

2) If the locally saved APN is from the UE, step S1608 is performed.

If the TWAG, locally assigns the PDN connection identifier, steps S1606 and S1607 are performed. Step S1606: The AC/BNG sends a Radius authentication request message to the TWAG, where the message carries the APN, the UE IP address 1 and the GRE key 2 on the AC/BNG side.

Step S1607: TWAG, replies to the Radius authentication response message to the AC/BNG, and generates the PDN connection identifier locally. The specific generation principle is the same as the preferred embodiment 2, and is not described here. The message carries the TWAG, the user plane address, the TWAG, and the side GRE. Key 2, PDN connection identifier.

If the AC/BNG locally allocates the PDN connection identifier, steps S1606a and S1607a are performed. Step S1606a: The AC/BNG generates the PDN connection identifier locally. For the specific generation principle, refer to the related description of Embodiment 1. Then, send a Radius authentication request message to the TWAG, where the message carries the APN, the PDN connection identifier, the UE IP address 1 and the AC. GRE key 2 on the /BNG side.

Step S 1607a: TWAG' replies to the AC/BNG with a Radius authentication response message carrying the TWAG, the user plane address, the TWAG, and the GRE key 2 on the side.

Step S1608: The AC/BNG replies with a reply (DHCPv6)/DHCP acknowledgment (DHCPv4) to the UE, where the message includes the UE IP address 1, the GRE key on the AC/BNG side, the PDN connection identifier, and the AC/BNG user plane address; The AC/BNG performs an association between the GRE key 1 and the GRE key 2.

Steps S1609-S1617: Same steps S1407-S1415.

Step S1618: When the UE sends the uplink data, the GRE tunnel containing the GRE key 1 is encapsulated. After receiving the AC/BNG, the GRE tunnel is decapsulated, and the associated GRE key 2 is found, and the GRE key 2 is encapsulated. The GRE tunnel is then sent to TWAG'; conversely, the downlink data is also true.

It should be noted that the GRE key 1 is used for tunnel encapsulation between the UE and the AC/BNG, and the GRE key 2 is used for tunnel encapsulation between AC/BNG and TWAG, and other tunnel encapsulation descriptions are the same as the preferred embodiment 2. .

Preferred embodiment five

The preferred embodiment provides a UE accessing the mobile network through the non-3GPP access network. In this embodiment, the UE accesses the EPC through a trusted WLAN, where the DHCP transmits the APN and the like, and the TWAG is The UE allocates the tunnel outer layer IP (the two DHCP request messages are associated by the tunnel key information). The difference between the preferred embodiment and the preferred embodiment 2 is that the two DHCP request messages are associated by the tunnel information, and FIG. 17 is according to the present invention. UE of the embodiment Flowchart 4 of the process of accessing the EPC through the trusted WLAN, as shown in FIG. 17, the method includes the following steps S1701 to S1715.

Steps S1701-S1706: Refer to steps S1401-S1406 of the preferred embodiment 2, except that the TWAG' does not locally generate the PDN connection identifier and does not pass the information.

Step S1707: The UE sends a request (DHCPv6)/DHCP discovery to the TWAG' again.

(DHCPv4) message, which is encapsulated by GRE tunneling through the GRE tunnel information in steps S1201-S1206.

Step S1708: After receiving the DHCP request message, the TWAG finds the associated APN information according to the GRE key, and then sends a create session request or a proxy binding update message to the PDN GW, where the message includes the APN.

Step S1709: Perform an IP-CAN session establishment operation between the PDN GW and the PCRF.

Step S1710: The PDN GW updates the PDN GW address to the HSS through the AAA Server. Step S1711: The PDN GW sends a create session response or a proxy binding acknowledgement message to the trusted non-3GPP access network, where the message carries the IP address 2 assigned by the PDN GW to the UE.

Step S1712: S1713: TWAG, sending an advertisement (DHCPv6)/DHCP providing message (DHCPv4) to the UE, where the message includes the UE IP address 2; the message is encapsulated by the GRE tunnel information in the GRE tunnel information in steps S1701-S1706.

Step S1714: TWAG, replying to the UE with a reply (DHCPv6)/DHCP acknowledgment (DHCPv4), the message including the UE IP address 2; TWAG, the local will save the association between the APN and the UE IP address 2. The message is encapsulated by GRE tunneling through the GRE tunnel information in steps S1701-S1706.

Step S1715: The UE and the TWAG perform the uplink and downlink data transmission through the GRE tunnel encapsulation. The UE is responsible for the encapsulation of the uplink data and the decapsulation of the downlink data, and the TWAG is responsible for the encapsulation of the downlink data and the decapsulation of the uplink data.

It should be noted that, in the foregoing embodiment, the GRE key and the TWAG, the user plane address are used for Information about the GRE tunnel encapsulation.

Preferred embodiment six

The preferred embodiment provides a UE accessing the mobile network through the non-3GPP access network. In this embodiment, the UE accesses the EPC through a trusted WLAN, where the DHCP transmits the APN, etc., AC/BNG. Assigning a tunnel outer IP to the UE (the tunnel encapsulation of the data packet between the UE and the TWAG is performed, and the two DHCP request messages are associated with the tunnel key information). The difference between this embodiment and the preferred embodiment 3 is that the DHCP is twice. The request message is associated with the tunnel information. FIG. 13 is a flowchart of a process for the UE to access the EPC through the trusted WLAN according to the embodiment of the present invention. As shown in FIG. 18, the method includes the following steps S1801 to S1815.

Steps S1801-S1808: Steps S1501-S1508 of the preferred embodiment 3, except that TWAG' does not locally generate a PDN connection identifier and does not pass the information.

Steps S1807-S1815: Same as steps S1707-S1715 of the preferred embodiment 5.

Preferred embodiment seven

The preferred embodiment provides a UE accessing the mobile network through the non-3GPP access network. In this embodiment, the UE accesses the EPC through a trusted WLAN, where the DHCP transmits the APN, etc., AC/BNG. The tunnel outer layer IP is allocated to the UE (the tunnel between the UE and the AC/BNG, the AC/BNG, and the TWAG implements the tunnel encapsulation of the data, and the two DHCP request messages are associated through the tunnel key information). The difference between the preferred embodiment and the fourth embodiment is that the two DHCP request messages are associated with each other through the tunnel information. FIG. 19 is a flowchart 6 of the process for the UE to access the EPC through the trusted WLAN according to the embodiment of the present invention, as shown in FIG. The method includes the following steps S1901 to S1918.

Steps S1901-S1908: See steps S1601-S1108 of the preferred embodiment four, with the difference that TWAG does not generate a PDN connection identifier locally and does not pass this information.

Step S1909: The UE sends a Solicitation (DHCPv6)/DHCP Discovery (DHCPv4) message to the AC/BNG, and the message is encapsulated between the UE and the AC/BNG through a GRE tunnel containing the GRE key 1.

Step S1910: After receiving the message, the AC/BNG decapsulates the GRE tunnel containing the GRE key 1, and then finds the associated GRE key 2, encapsulates it through the GRE tunnel containing the GRE key 2, and sends it to the TWAG.

Step S1911: After receiving the DHCP request message, the TWAG finds the associated APN and other information according to the GRE key 2, and then sends a create session request or a proxy binding update message to the PDN GW, where the message includes the APN.

Step S1912-S1914: Same steps S1612-S1614.

Step S1915: TWAG sends an advertisement (DHCPv6) to the AC/BNG/DHCP to provide a message (DHCPv4), and the message includes the UE IP address 2; the message is encapsulated by the GRE tunnel containing the GRE key 2 and sent to the TWAG'.

Step S1916: After receiving the notification (DHCPv6)/DHCP providing message (DHCPv4), the AC/BNG decapsulates the GRE tunnel containing the GRE key 2, and then finds the associated GRE key 1 through the GRE tunnel containing the GRE key 1. Encapsulation and sending to the UE.

Step S1917a: The UE completes the DHCP request/DHCP acknowledgement operation (DHCPv4). For tunnel encapsulation, see steps S1915-S1916.

Step S1917b: The UE completes the request/reply operation (DHCPv6). Tunnel encapsulation see steps

S1915-S1916.

Step S1918: When the UE sends the uplink data, the GRE tunnel containing the GRE key 1 is encapsulated. After receiving the AC/BNG, the GRE tunnel is decapsulated, and the associated GRE key 2 is found, and the GRE key 2 is encapsulated. The GRE tunnel is then sent to TWAG'; conversely, the downlink data is also true. It should be noted that, in the foregoing embodiment, the GRE key 1 is used for tunnel encapsulation between the UE and the AC/BNG, and the GRE key 2 is used for tunnel encapsulation between AC/BNG and TWAG. The description of other tunnel encapsulations is the same as the preferred embodiment 2, and details are not described herein again. .

The above DHCP message may only be used to allocate some parameters other than the IP address, and request the IP address through the route request/route response message. After the relevant step, the flow of the route request/route response message needs to be added to request After the IP address is assigned, the other processes that follow will continue after the IP address is obtained.

Preferred embodiment eight

The preferred embodiment provides a UE accessing the mobile network through the non-3GPP access network. In this embodiment, the UE accesses the EPC through the trusted WLAN, where the EAP message transmits the APN and other information, TWAG, The UE is assigned a tunnel outer IP address, and the two DHCP request messages are associated by the PDN connection identifier. FIG. 20 is a flowchart VII of the process for the UE to access the EPC through the trusted WLAN according to the embodiment of the present invention. The method includes the following steps S2001 to S2018.

Step S2001: A non-3GPP specific process is performed between the UE and the trusted WLAN access network.

Step S2002-S2008: The AP/RG functions as an EAP Authenticator and performs an EAP authentication process. The AC/BNG and TWAG can act as AAA agents.

In the EAP authentication request message, the UE may carry the APN;

In the EAP authentication response message, the AC/BNG obtains the service type of the decision from the 3GPP AAA server, including: a slotted service offload, or access to the EPC, or both. Moreover, the TWAG allocates a PDN connection identifier to the UE, and delivers the PDN connection identifier to the UE through the EAP response message.

If the S2a session is successfully triggered by the EAP authentication, the steps S2003-S2006 are performed. For details, refer to steps S1408-S1411. The PDN GW returns the IP address 2 and TWAG to the TWAG, and locally stores the association between the APN and the APN. .

Step S2009: The UE sends an Solicitation (DHCPv6)/DHCP Discovery (DHCPv4) message to the AC/BNG, where the message may carry an IP address request subtype and PDN connection identifier information. If the slotted service offload is defined as a special PDN connection, a new flag information is added to the PDN connection identifier at the location to distinguish the slotted service offload from other PDN connections to the EPC; If the slotted service offload is not defined as a special PDN connection, then the IP address request subtype and PDN connection identifier information may not be carried at this time.

The IP address request subtype represents the local assigned IP or the PDN GW allocates an IP. After the AC/BNG receives the solicitation (DHCPv6)/DHCP discovery (DHCPv4) message, if the slotted service offload is not defined as a special PDN connection, it is determined whether to forward to the TWAG according to whether the PDN connection identifier is carried. If the slotted service offload is defined as a special PDN connection, it is defined to be forwarded to the TWAG according to the flag bits used to distinguish between the slotted service offload and other PDN connections to the EPC.

If it is a PDN connection to the EPC, step S2009a is performed.

Step S2009a: AC/BNG to TWAG, Forward Solicitation (DHCPv6) / DHCP Discovery

(DHCPv4) message.

Step S2010a-S2010: TWAG, according to the IP address request subtype, confirming that the IP address is locally allocated, then assigning an IP address of 1, and transmitting an announcement (DHCPv6)/DHCP providing message (DHCPv4) to the UE through the AC/BNG, the message may be Contains the UE IP address 1.

Step S2011: The UE sends a request (DHCPv6)/DHCP request (DHCPv4) to the TWAG, The message includes the UE IP address 1 and the GRE key on the UE side.

Step S2012: TWAG sends a reply (DHCPv6)/DHCP acknowledgment (DHCPv4) operation to the UE, in order to further confirm the IP address 1.

Step S2013-S2013a: The UE sends a Solicitation (DHCPv6)/DHCP Discovery (DHCPv4) message to the AC/BNG, which carries the IP address request subtype and the PDN connection identifier information. After receiving the message, the AC/BNG, based on the PDN connection identifier carried in the message, confirms that it is accessing the EPC, and then acts as a DHCP relay to forward the DHCP request message to the TWAG'.

Step S2014: TWAG, according to the IP address request subtype, confirms that the PDN GW is requested to allocate an IP address.

If step S2003-S2006 is not executed, TWAG' will find the associated APN and other information according to the PDN connection identifier, and then send a Create Session Request or Proxy Binding Update message to the PDN GW, which contains the APN. See step S2003-S2006 for details.

Step S2015-S2016: TWAG sends an advertisement (DHCPv6)/DHCP providing message (DHCPv4) to the UE through AC/BNG, and the message includes the UE IP address 2;

Step S2017-S2017a: The UE sends a request to the TWAG via AC/BNG (DHCPv6)

/DHCP request (DHCPv4), the message contains the UE IP address 2;

TWAG, reply replies to the UE (DHCPv6) / DHCP acknowledgment (DHCPv4), the message contains the UE IP address 2; TWAG, the local will save the association between the APN and the UE IP address 2.

Step S2018: The UE and the TWAG perform the uplink and downlink data transmission through the GRE tunnel encapsulation, the UE is responsible for the encapsulation of the uplink data and the decapsulation of the downlink data, and the TWAG' is responsible for the encapsulation of the downlink data and the decapsulation of the uplink data.

The above DHCP message may only be used to allocate some parameters other than the IP address, and request the IP address by routing request/routing response message. After steps 306 and 315, it is required. The process of adding a route request/routing response message is requested to allocate an IP address, and other processes subsequent to it continue to execute after obtaining an IP address.

Preferred embodiment nine

The preferred embodiment provides a UE accessing the mobile network through the non-3GPP access network. In this embodiment, the UE accesses the EPC through the trusted WLAN, where the EAP message transmits the APN, etc., AC/ The BNG allocates the tunnel outer IP address to the UE, and the two DHCP request messages are associated by the PDN connection identifier. FIG. 21 is a flowchart 8 of the process of the UE accessing the EPC through the trusted WLAN according to the embodiment of the present invention, as shown in FIG. 21 . As shown, the method includes the following steps S2101 to S2120.

Step S2101: A non-3GPP specific process is performed between the UE and the trusted WLAN access network.

Step S2102-S2108: See step S2002-step S2008.

Step S2109: The UE sends an Solicitation (DHCPv6) / DHCP Discovery to the AC/BNG.

(DHCPv4) message, which may carry the IP address request subtype and PDN connection identifier information. If the slotted service offload is defined as a special PDN connection, a new flag information is added to the PDN connection identifier at the location to distinguish the slotted service offload from other PDN connections to the EPC; If the slotted service offload is not defined as a special PDN connection, then the IP address request subtype and PDN connection identifier information may not be carried at this time.

The IP address request subtype represents the local assigned IP or the PDN GW allocates an IP. After receiving the request (DHCPv6)/DHCP discovery (DHCPv4) message, if the slotted service offload is not defined as a special PDN connection, the AC/BNG determines whether the subsequent processing is forwarded to the TWAG according to whether the PDN connection identifier is carried. , if there is a sewn business diversion If it is defined as a special PDN connection, it defines whether to forward subsequent processing to TWAG according to the flag bits used to distinguish between the slotted service offload and other PDN connections to the EPC.

Step S2110: The AC/BNG sends an advertisement (DHCPv6)/DHCP providing message (DHCPv4) to the UE, and the message may include the UE IP address 1.

Step S2111: The UE sends a request (DHCPv6) / DHCP request to the AC/BNG.

(DHCPv4), the message includes the UE IP address 1 and the GRE key on the UE side.

If the AC/BNG determines that the PDN connection is to access the EPC, steps S2112-S2113 are performed. Step S2112: The AC/BNG sends a Radius authentication request message to the TWAG, where the message carries the PDN connection identifier, the UE IP address 1 and the GRE key on the AC/BNG side.

Step S2113: The TWAG' replies to the AC/BNG with a Radius authentication response message, where the message carries the TWAG, the user plane address, the TWAG, and the GRE key on the side.

Step S2114: The AC/BNG sends a reply (DHCPv6)/DHCP acknowledgment (DHCPv4) operation to the UE, in order to further confirm the IP address 1.

Step S2115-S2120: See steps S2013-S2018.

Information about the GRE tunnel encapsulation.

The above DHCP message may only be used to allocate some parameters other than the IP address, and request the IP address through the route request/route response message. After the relevant step, the flow of the route request/routing response message needs to be added to request After the IP address is assigned, the other processes that follow will continue after the IP address is obtained.

Preferred embodiment ten

The preferred embodiment provides a UE accessing the mobile network through the non-3GPP access network. In this embodiment, the UE is connected to the EPC through the trusted WLAN. This embodiment and the preferred embodiment The difference between the ninth embodiment is that the user data is segmented into GRE tunnel encapsulation between the UE and the AC/BNG, the AC/BNG, and the TWAG, and FIG. 22 is the UE accessing the EPC through the trusted WLAN according to the embodiment of the present invention. Flowchart 9 of the flow, as shown in FIG. 22, the method includes the following steps S2201 to S2220.

Steps S2201-S2210: Same steps S2101-S2110.

Step S2211: The UE sends a request (DHCPv6) / DHCP request (DHCPv4) to the AC/BNG, where the message includes the UE IP address 1 and the UE side GRE key 1.

If the AC/BNG determines that the PDN connection is to access the EPC, steps S2212-S2213 are performed. Step S2212: The AC/BNG sends a Radius authentication request message to the TWAG, where the message carries the AC/BNG user plane address, the PDN connection identifier, and the GRE key 2 on the AC/BNG side.

Step S2213: The TWAG' replies to the AC/BNG with a Radius authentication response message carrying the TWAG, the user plane address, the TWAG, and the GRE key 2 on the side.

Step S2214: The AC/BNG replies to the UE with a reply (DHCPv6)/DHCP acknowledgment (DHCPv4), and the message includes the UE IP address 1, the GRE key on the AC/BNG side, and the AC/BNG user plane address; AC/BNG will The association between the GRE key 1 and the GRE key 2 is performed.

Step S2215- S2219a: See step S2013-S2017.

Step S2220: When the UE sends the uplink data, the GRE tunnel containing the GRE key 1 is encapsulated. After receiving the AC/BNG, the GRE tunnel is decapsulated, and the associated GRE key 2 is found, and the GRE key 2 is encapsulated. The GRE tunnel is then sent to TWAG'; conversely, the downlink data is also true.

The above DHCP message may only be used to allocate some parameters other than the IP address, and request the IP address through the route request/route response message. After the relevant steps, the path needs to be added. The IP address is requested by the flow of the request/routing response message, and the other processes that follow are obtained after obtaining the IP address.

Preferred embodiment eleven

The preferred embodiment provides a UE accessing the mobile network through the non-3GPP access network. In this embodiment, the UE is connected to the EPC through the trusted WLAN. The difference between this embodiment and the preferred embodiment 8 lies in The two DHCP request messages are associated with each other through the tunnel information. FIG. 23 is a flowchart of a process for the UE to access the EPC through the trusted WLAN according to the embodiment of the present invention. As shown in FIG. 23, the method includes the following step S2301. Go to step S2318.

Steps S2301-S2308: See steps S2001-S2008 of the preferred embodiment eight.

Step S2309-S2309a: The UE sends a Solicitation (DHCPv6)/DHCP Discovery (DHCPv4) message to the AC/BNG, which may carry the PDN connection identifier information. If the slotted service offload is not defined as a special PDN connection, it is determined whether to forward to the TWAG according to whether to carry the PDN connection identifier; if the slotted service offload is defined as a special PDN connection, then according to The PDN connection identifies the type of service associated with the decision to decide whether to forward to TWAG. If the service type of the decision is to allow access to the EPC, then it is decided to forward the message to TWAG'.

Step S2310: The TWAG sends an advertisement (DHCPv6)/DHCP providing message (DHCPv4) to the UE through the AC/BNG, and the message may include the UE IP address 1.

Step S2311: The UE sends a request (DHCPv6)/DHCP request (DHCPv4) to the TWAG through the AC/BNG, where the message includes the UE IP address 1 and the GRE key of the UE side.

TWAG, reply replies to the UE (DHCPv6) / DHCP acknowledgment (DHCPv4), the message includes UE IP address 1, TWAG, side GRE key, TWAG, user plane address; TWAG, local save GRE key, PDN connection identifier , TWAG, user plane address and APN information Association.

Step S2312: The UE sends a Solicitation (DHCPv6)/DHCP Discovery (DHCPv4) message to the TWAG, and the message is encapsulated by the GRE tunnel through the GRE tunnel information.

Step S2313: After receiving the DHCP request message, the TWAG finds the associated APN information according to the GRE key, and then sends a create session request or a proxy binding update message to the PDN GW, where the message includes the APN. For other steps, see steps S2303-S2306.

Step S2314: The TWAG sends an advertisement (DHCPv6)/DHCP providing message (DHCPv4) to the UE, where the message includes the UE IP address 2; the message is encapsulated by the GRE tunnel through the GRE tunnel information.

Step S2315: The UE sends a request (DHCPv6)/DHCP request (DHCPv4) to the TWAG, where the message includes the UE IP address 2;

TWAG, reply replies to the UE (DHCPv6) / DHCP acknowledgment (DHCPv4), the message contains the UE IP address 2; TWAG, the local will save the association between the APN and the UE IP address 2. The message is encapsulated by the GRE tunnel through the GRE tunnel information.

Step S2316: The UE and the TWAG perform the uplink and downlink data transmission through the GRE tunnel encapsulation. The UE is responsible for the encapsulation of the uplink data and the decapsulation of the downlink data, and the TWAG is responsible for the encapsulation of the downlink data and the decapsulation of the uplink data.

Preferred embodiment twelve

The preferred embodiment provides a UE accessing the mobile network through the non-3GPP access network. In this embodiment, the UE is connected to the EPC through the trusted WLAN. The difference between this embodiment and the preferred embodiment 9 lies in The two DHCP request messages are associated with each other through the tunnel information. FIG. 24 is a flowchart 10 of a process for the UE to access the EPC through the trusted WLAN according to the embodiment of the present invention. As shown in FIG. 24, the method includes the following step S2401. Go to step S2420. Steps S2401-S2408: See steps S2301-S2308 of the preferred embodiment eight. Step S2409: The UE sends an Solicitation (DHCPv6)/DHCP Discovery (DHCPv4) message to the AC/BNG, where the message may carry the PDN connection identifier information. If the slotted service offload is not defined as a special PDN connection, it is determined whether the subsequent processing is forwarded to the TWAG according to whether the PDN connection identifier is carried, and if the slotted service offload is defined as a special PDN connection, Then, according to the service type of the decision associated with the PDN connection identifier, whether the subsequent processing is forwarded to the TWAG is determined. If the service type of the decision is to allow access to the EPC, then it is decided to forward the message to the TWAG.

Step S2410: The TWAG sends an advertisement (DHCPv6)/DHCP providing message (DHCPv4) to the UE through the AC/BNG, and the message may include the UE IP address 1.

Step S2411: The UE sends a request (DHCPv6)/DHCP request (DHCPv4) to the TWAG through the AC/BNG, where the message includes the UE IP address 1 and the GRE key of the UE side.

Step S2412: The AC/BNG sends a Radius authentication request message to the TWAG, where the message carries the PDN connection identifier, the UE IP address 1 and the GRE key on the AC/BNG side.

Step S2413: The TWAG' replies to the AC/BNG with a Radius authentication response message, where the message carries the TWAG, the user plane address, the TWAG, and the GRE key on the side.

Step S2414: The TWAG sends a reply (DHCPv6)/DHCP acknowledgment (DHCPv4) operation to the UE, in order to further confirm the IP address 1.

Steps S2415-S2420: See steps S2312-S2316.

NOTE: In the above embodiment, the GRE key and TWAG, the user plane address are information used for GRE tunnel encapsulation.

Preferred embodiment thirteen

The preferred embodiment provides a UE accessing the mobile network through the non-3GPP access network. In this embodiment, the UE is connected to the EPC through the trusted WLAN. The difference between this embodiment and the preferred embodiment is that , two DHCP request messages are associated through tunnel information, Figure 25 A flowchart of a process for a UE to access an EPC through a trusted WLAN according to an embodiment of the present invention. As shown in FIG. 25, the method includes the following steps S2501 to S2520.

Steps S2501-S2508: Steps S2001-S2008 of the preferred embodiment eight.

Step S2509: The UE sends an Solicitation (DHCPv6)/DHCP Discovery (DHCPv4) message to the AC/BNG, where the message may carry the PDN connection identifier information. If the slotted service offload is not defined as a special PDN connection, it is determined whether the subsequent processing is forwarded to the TWAG according to whether the PDN connection identifier is carried, and if the slotted service offload is defined as a special PDN connection, Then, according to the service type of the decision associated with the PDN connection identifier, whether the subsequent processing is forwarded to the TWAG is determined. If the service type of the decision is to allow access to the EPC, then it is decided to forward the message to the TWAG.

Step S2510: The TWAG sends an advertisement (DHCPv6)/DHCP providing message (DHCPv4) to the UE through the AC/BNG, and the message may include the UE IP address 1.

Step S2511: The UE sends a request (DHCPv6)/DHCP request (DHCPv4) to the TWAG through the AC/BNG, where the message includes the UE IP address 1 and the UE side GRE key 1.

Step S2512: The AC/BNG sends a Radius authentication request message to the TWAG, and the message carries the PDN connection identifier, the AC/BNG user plane address, and the GRE key 2 on the AC/BNG side.

Step S2513: TWAG' replies to the AC/BNG with a Radius authentication response message carrying the TWAG, the user plane address, the TWAG, and the GRE key 2 on the side.

Step S2514: The TWAG sends a reply (DHCPv6)/DHCP acknowledgment (DHCPv4) operation to the UE, where the message includes an AC/BNG user plane address, and a GRE key 1 on the AC/BNG side.

Steps S2515-S2520: For details, refer to the preferred embodiment seven steps S1909-S1918.

Embodiment 14

The preferred embodiment provides a UE accessing the mobile network through the non-3GPP access network. In this embodiment, the UE accesses the EPC through the trusted WLAN, where the 802.11u message transmits the APN, and the like. Other processes for EAP messaging such as APN are similar. Figure 26 is a flowchart of a process for a UE to access an EPC through a trusted WLAN according to an embodiment of the present invention. As shown in Figure 26, the method includes the following steps S2601 to S2610.

Step S2601: Perform process processing inside the WLAN between the UE and the trusted WLAN access network, for example, including: probe operation between the UE and the AP, establishment of a CAPWAP session between the AP and the AC, or between the UE and the RG Operation, etc.

Step S2602 - S2603: Perform a GAS-ANQP request/response operation between the UE and the AP/RG. Step S2604: The UE may perform some association operations and an authentication process inside the WLAN. Step S2605: The EAP authentication and authorization process is completed between the UE and the 3GPP AAA.

Step S2606: The UE sends a GAS-ANQP initial request message to the AP/RG, where the message carries the APN information.

Step S2607: After receiving the foregoing message, the AP/RG sends a CAPWAP WTP event request/Radius authentication request message to the AC/BNG, where the message carries the APN information.

After receiving the above message, the AC/BNG sends a Radius authentication request message to the TWAG. If the AC/BNG allocates the PDN connection identifier, step S2108a-S2109a is performed. If the TWAG allocates the PDN connection identifier, step S2608b is performed. S2609b.

Step S2608a-S2609a: The AC/BNG sends a Radius authentication request message to the TWAG, where the message includes the APN and PDN connection identification information. Step S2608b-S2609b: The AC/BNG sends a Radius authentication request message to the TWAG, and the message contains the information. In the Radius authentication response message, the TWAG returns the PDN connection identifier to the AC/BNG.

The principles for assigning PDN connection identifiers are as follows:

1) If there is no PDN connection identifier associated with the APN, a new PDN connection identifier is generated;

2) If the PDN connection identifier associated with the APN already exists, the TWAG, which is considered to be an additional PDN connection establishment request under the same APN, will also newly generate a PDN connection identifier.

3) The PDN connection identifier may be the default bearer identifier of the first GTP session established by the PDN connection or the session identifier of the PMIP session, or may be an 802.llu message, a dynamic host setting protocol, a xid of a DHCP message, or a client connection. Identifies the client id, the interface identifier, the intercept id, or the new ID.

Step S2608: After receiving the foregoing message, the AC/BNG sends a CAPWAP/Radius authentication response message to the AP/RG, where the message carries the PDN connection identifier.

Step S2609: The AP/RG sends a GAS-ANQP initial response message to the UE, where the message carries the PDN connection identifier.

Step S2610: Same as step S2009-S2018 or S2109-S2120 or S2209-S2220 or S2309-S2316 or S2409-S2419 or S2509-S2520.

When the 3GPP network is UMTS, the GGSN can replace the PDN GW in this embodiment. The features to be enhanced are the same.

Through the foregoing embodiment, a data packet transmission method, a PDN connection identifier processing method, and a device are provided, and a trusted non-3GPP access is received by a UE by sending a first IP address request message to a trusted non-3GPP access network. The first IP address assigned by the network to the UE, and then the UE obtains the second IP address assigned by the 3GPP core network to the UE by sending a second IP address request message to the trusted non-3GPP access network, and implements different PDNs of the UE. Differentiated by different IP addresses, the problem that the reliability of data transmission of the UE through the trusted non-3GPP access network is relatively poor in the related art is solved, and the reliability of data packet transmission is improved. These technical effects are not achieved by all of the above embodiments, and some of the technical effects are achieved by certain preferred embodiments.

Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device so that they may be stored in the storage device by the computing device, or they may be separately fabricated into individual integrated circuit modules, or Multiple modules or steps are made into a single integrated circuit module. Thus, the invention is not limited to any particular combination of hardware and software.

The above is only a preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to 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

Claim

A data message transmission method, wherein the method comprises:

The user equipment UE sends a first Internet Protocol IP address request message to the trusted non-3rd generation partner 3GPP access network, and receives the first IP address allocated by the trusted non-3GPP access network to the UE;

Sending, by the UE, a second IP address request message to the trusted non-3GPP access network, and receiving a second IP address allocated by the 3GPP core network to the UE;

The UE transmits a data packet encapsulated by the tunnel, where the source IP address or the destination IP address of the data packet is a second IP address, and the source IP address or the destination IP address of the tunnel is the first IP address.

The method according to claim 1, wherein the UE sends a first IP address request message to the trusted non-3GPP access network, and receives the first allocated by the trusted non-3GPP access network to the UE. The IP address includes:

Sending, by the UE, a first IP address request message to the access controller/broadband network gateway AC/BNG, and acquiring the first IP address allocated by the AC/BNG to the UE; or

The UE sends a first IP address request message to the trusted WLAN access gateway TWAG' to obtain the first IP address allocated by the TWAG for the UE.

The method according to claim 1, wherein before the UE transmits the data packet encapsulated by the tunnel, the method further includes:

Receiving, by the UE, the information about the tunnel that is allocated by the trusted non-3GPP access network to the UE, where the tunnel information is sent by the trusted non-3GPP access network to the UE The first IP address request message is subsequently allocated for the UE.

The method according to claim 2 or 3, wherein

When the UE sends the first IP address request message to the AC/BNG, the AC/BNG sends a Radius request message to the trusted wireless local area network access gateway TWAG, and receives the TWAG. Information about the assigned tunnel.

5. The method according to claim 4, wherein

The information of the tunnel includes: a key of the tunnel and/or a local IP address of the tunnel.

The method according to any one of claims 1 to 3, 5, wherein

The first IP address request message and the second IP address request message are all associated by the packet data network PDN connection identifier or are associated by the information of the tunnel.

The method according to claim 6, wherein

The first IP address request message includes: a dynamic host setting protocol DHCP message; and the second IP address request message includes: the DHCP message.

The method according to claim 1, wherein

Before the UE sends the first IP address request message to the trusted non-3GPP access network or when the UE sends the first IP address request message to the trusted non-3GPP access network The UE transmits the access point name APN information through at least one of the following messages: Institute of Electrical and Electronics Engineers IEEE 802.11 message, Dynamic Host Setup Protocol DHCP message, Extended Authentication Protocol EAP message.

A data message transmission method, wherein the method comprises:

The trusted third-generation partner 3GPP access network receives the first Internet Protocol IP address request message sent by the user equipment UE, and allocates the first IP address to the UE;

Receiving, by the trusted non-3GPP access network, a second IP address request message sent by the UE, sending a session request message to the 3GPP core network, and receiving a second IP address allocated by the 3GPP core network to the UE;

The trusted non-3GPP access network transmits a data packet encapsulated by the tunnel, where the source IP address or the destination IP address of the data is a second IP address, and the source IP address or destination of the tunnel The IP address is the first IP address.

10. The method of claim 9, wherein the trusted non-3GPP access Before the network transmits the data packet encapsulated in the tunnel, the method further includes:

After receiving the first IP address request message sent by the UE, the trusted non-3GPP access network allocates information about the tunnel to the UE.

11. The method according to claim 10, wherein

The method according to any one of claims 9 to 11, wherein

A packet data network PDN connection identifier processing method, wherein the method comprises:

The user equipment sends a message carrying the access point name APN information to the AC/BNG through the access point device/home gateway AP/RG;

Receiving, by the UE, the first PDN connection identifier corresponding to the APN information that is allocated by the AC/BNG that is forwarded by the trusted WLAN access gateway TWAG′; or the UE receiving the APN information that is allocated by the TWAG′ a second PDN connection identifier, where the second PDN connection identifier is the TWAG, and is allocated after receiving the message that the AC/BNG sends the APN information.

The method according to claim 14, wherein the UE sends a message carrying the access point name APN information to the AC/BNG through the AP/RG, including:

The UE sends a general advertisement service-access network query protocol GAS-ANQP initial request message carrying the APN information to the AP/RG, and triggers the CAPWAP WTP that the AP/RG will carry the APN information. Event request or remote authentication dial-up user service Radius A request message is sent to the AC/BNG.

The method of claim 15, wherein the UE receives a trusted TWAG, and the first PDN connection identifier corresponding to the APN information that is forwarded by the forwarded AC/BNG comprises: the UE receiving an AP/ a GAS-ANQP initial response message corresponding to the GAS-ANQP initial request message sent by the RG;

The GAS-ANQP initial response message is a CAPWAP WTP event response corresponding to the CAPWAP WTP event request sent by the AC/BNG or a Radius response message corresponding to the Radius request message. Afterwards, the CAPWAP WTP event response and the Radius response message are sent to the AP/RG, and the CAPWAP WTP event response and the Radius response message are the AC/BNG receiving. And sending, to the TWAG, the Radius authentication response message carrying the first PDN connection identifier, to the AC/BNG.

The method according to claim 15, wherein the UE receives the TWAG, and the second PDN connection identifier corresponding to the allocated APN information includes: a GAS-ANQP initial response message;

The GAS-ANQP initial response message is a CAPWAP WTP event response corresponding to the CAPWAP WTP event request sent by the AC/BNG or a Radius response message corresponding to the Radius request message. And sending, to the AP/RG, the CAPWAP WTP event response and the Radius response message both carrying the second PDN connection identifier; the CAPWAP WTP event response and the Radius response message are the AC/BNG receiving And sending, to the TWAG, the Radius authentication response message carrying the second PDN connection identifier, and sending the message to the AC/BNG.

The method according to any one of claims 14 to 17, wherein

The first PDN connection identifier and the second PDN connection identifier are one of the following: The default bearer ID of the first GTP session established by the PDN connection or the session ID of the PMIP session, the Institute of Electrical and Electronics Engineers IEEE 802.Uu message identifier, the xid of the DHCP message, the client connection ID client id, the interface identifier interferce id .

A method for processing a PDN connection identifier of a packet data network, wherein the method includes: the access controller/broadband network gateway AC/BNG receiving the APN information carried by the user equipment UE and carrying the access point name by the AP/RG Message

The AC/BNG allocates a corresponding first PDN connection identifier to the APN information; or the AC/BNG sends a message carrying the APN information to a trusted wireless local area network access gateway TWAG', and receives the a second PDN connection identifier corresponding to the APN information allocated by the TWAG';

The AC/BNG sends the first PDN connection identifier or the second PDN connection identifier to the UE.

The method according to claim 19, wherein the AC/BNG receiving message that the user equipment UE forwards through the AP/RG and carries the APN information includes:

The AC/BNG receives a CAPWAP WTP event request or a Radius request message that is sent by the AP/RG and carries the APN information, where the wireless access point controls and provides a CAPWAP wireless termination point WTP event request or Radius The request message is sent by the AP/RG to the AP/RG after receiving the GAS-ANQP initial request message that is sent by the UE and carrying the APN information.

The method according to claim 19, wherein

The AC/BNG sends a message carrying the APN information to the TWAG, including: the AC/BNG sends a Radius authentication request message carrying the APN information to the TWAG';

Receiving, by the AC/BNG, the second PDN connection identifier corresponding to the APN information that is allocated by the TWAG', includes: the AC/BNG receiving the TWAG' sent corresponding to the The Radius authentication response message of the Radius authentication request message, where the Radius authentication response message carries the second PDN connection identifier.

The method of claim 19, wherein the sending, by the AC/BNG, the first PDN connection identifier or the second PDN connection identifier to the UE comprises:

The AC/BNG sends a CAPWAP WTP event response corresponding to the CAPWAP WTP event request or a Radius response message corresponding to the Radius request message to the AP/RG, triggering the AP/RG to pass the initial corresponding to the GAS-ANQP Sending, by the GAS-ANQP initial response message of the request message, the first PDN connection identifier or the second PDN connection identifier to the UE, where the CAPWAP WTP event response and the Radius response message both carry the a first PDN connection identifier or the second PDN connection identifier.

The method according to any one of claims 19 to 22, wherein

The first PDN connection identifier and the second PDN connection identifier are one of the following:

The default bearer identifier of the first general packet radio service tunneling protocol GTP session established by the PDN connection or the session identifier of the PMIP session, the IEEE 802.1 lu message identifier of the Institute of Electrical and Electronics Engineers, the xid of the DHCP message, the client connection identifier client id The interface identifier is the interceptce id.

24. A data message transmission apparatus, applied to a UE, wherein the apparatus comprises: a first sending module, configured to send a first Internet Protocol IP address request message to a trusted non-third generation partner 3GPP access network ;

a first receiving module, configured to receive a first IP address allocated by the trusted non-3GPP access network to the UE;

a second sending module, configured to send a second IP address request message to the trusted non-3GPP access network;

a second receiving module, configured to receive a second IP address allocated by the 3GPP core network to the UE; The first transmission module is configured to transmit a data packet encapsulated by the tunnel, where the source IP address or the destination IP address of the data is a second IP address, and the source IP address or the destination IP address of the tunnel is First IP address.

25. Apparatus according to claim 24, wherein

The first sending module is configured to send a first IP address request message to the AC/BNG; the first receiving module is configured to acquire the first IP address that the AC/BNG allocates for the UE; or the first The sending module is configured to send the first IP address request message to the trusted wireless local area network access gateway TWAG'; the first receiving module is configured to acquire the TWAG, and the first IP address allocated to the UE .

The device according to claim 24, further comprising:

a third receiving module, configured to receive tunnel information allocated by the trusted non-3GPP access network to the UE, where the tunnel information is that the trusted non-3GPP access network receives the UE sending After the first IP address request message is allocated for the UE.

27. A data message transmission device, applied to a trusted non-3rd generation partner 3GPP access network, wherein the device comprises:

a fourth receiving module, configured to receive a first Internet Protocol IP address request message sent by the user equipment UE;

a first allocation module, configured to allocate a first IP address to the UE;

a fifth receiving module, configured to receive a second IP address request message sent by the UE, where the third sending module is configured to send a session request message to the 3GPP core network;

a sixth receiving module, configured to receive a second IP address that is allocated by the 3GPP core network to the UE;

The second transmission module is configured to transmit a data packet encapsulated by the tunnel, where the source IP address or the destination IP address of the data is a second IP address, and the source IP address or the destination IP address of the tunnel is First IP address.

The device according to claim 27, further comprising:

And a second allocation module, configured to allocate information about the tunnel to the UE after receiving the first IP address request message sent by the UE.

29. A packet data network PDN connection identifier processing apparatus, applied to a user equipment UE, wherein the apparatus includes:

The fourth sending module is configured to send, by the AP/RG, a message carrying the access point name APN information to the AC/BNG;

a seventh receiving module, configured to receive a first PDN connection identifier corresponding to the APN information allocated by the AC/BNG forwarded by the trusted WLAN access gateway TWAG′, or an eighth receiving module, configured to receive the TWAG, The second PDN connection identifier corresponding to the allocated APN information, where the second PDN connection identifier is the TWAG, and is allocated after receiving the message that the AC/BNG sends the APN information.

The device according to claim 29, wherein the fourth sending module includes: a fifth sending module, configured to send a GAS-ANQP initial request message carrying the APN information to the AP/RG, The AP/RG is triggered to send a CAPWAP WTP event request or a Radius request message carrying the APN information to the AC/BNG.

31. Apparatus according to claim 30, wherein

The seventh receiving module is configured to receive a GAS-ANQP initial response message corresponding to the GAS-ANQP initial request message sent by the AP/RG;

The GAS-ANQP initial response message is a CAPWAP WTP event response corresponding to the CAPWAP WTP event request sent by the AC/BNG or a Radius response message corresponding to the Radius request message. Afterwards, the CAPWAP WTP event response and the Radius response message are sent to the AP/RG, and the CAPWAP WTP event response and the Radius response message are the AC/BNG receiving. Sending to the TWAG, carrying the first PDN connection identifier After the Radius authentication response message, it is sent to the AC/BNG.

32. Apparatus according to claim 30, wherein

The eighth receiving module is configured to receive a GAS-ANQP initial response message corresponding to the GAS-ANQP initial request message sent by the AP/RG;

33. A packet data network PDN connection identifier processing device, applied to an access controller/broadband network gateway AC/BNG, wherein the device includes:

a ninth receiving module, configured to receive a message that the user equipment UE forwards through the AP/RG and carries the access point name APN information;

a third allocation module, configured to allocate a corresponding first PDN connection identifier for the APN information; or a sixth sending module, configured to send the message carrying the APN information to a trusted wireless local area network access gateway TWAG' a tenth receiving module, configured to receive the second PDN connection identifier corresponding to the APN information that is allocated by the TWAG′;

And a seventh sending module, configured to send the first PDN connection identifier or the second PDN connection identifier to the UE.

34. Apparatus according to claim 33, wherein

The ninth receiving module is configured to receive a CAPWAP WTP event request or a Radius request message that is sent by the AP/RG and that carries the APN information, where the CAPWAP WTP event request or the Radius request message is the AP/RG Receiving the carried by the UE After the GAS-ANQP initial request message of the APN information is sent to the AP/RG.

35. Apparatus according to claim 34, wherein

The sixth sending module is configured to send a Radius authentication request message carrying the APN information to the TWAG′;

The tenth receiving module, configured to receive the second PDN connection identifier corresponding to the APN information that is allocated by the TWAG′, includes: the AC/BNG receiving the Radius authentication request message sent by the TWAG′ The Radius authentication response message, wherein the Radius authentication response message carries a second PDN connection identifier.

36. Apparatus according to claim 34, wherein

The seventh sending module is configured to set the first PDN connection identifier or the CAPWAP WTP event response corresponding to the CAPWAP WTP event request or the GAS-ANQP initial response message corresponding to the Radius response message of the Radius request message. The second PDN connection identifier is sent to the UE, where the CAPWAP WTP event response and the Radius response message both carry the first PDN connection identifier or the second PDN connection identifier.