CN104427568B - A method and device for realizing 3GPP network traffic offloading - Google Patents

Abstract

The invention discloses a kind of method, apparatus for realizing the unloading of 3GPP network flow, are related to the communications field, can utilize the flow for the special services that the unloading of non-3GPP network gateway is accessed by 3GPP network node.The described method includes: user equipment (UE) determination need to establish the carrying for accessing special services；The 3GPP network insertion node of Xiang Weiqi service sends the request of UE access non-3GPP network gateway；It is completed so that UE is established via the carrying of 3GPP network insertion non-3GPP network gateway, UE accesses the special services by establishing the carrying completed.

Description

A method and device for realizing 3GPP network traffic offloading

technical field

The present invention relates to the field of communications, and in particular, to a method and device for realizing 3GPP network traffic offloading.

Background technique

The applications that can be provided on the network are increasingly abundant, which increases the demand of users to access the network through mobile terminals. In order to provide better services, currently mobile operators have deployed a 3GPP network + non-3GPP network (ie, non-3GPP, such as WLAN) hybrid networking.

There are mainly two ways for user equipment (UE, user equipment) to access the Internet: the first is to access the Internet through a 3GPP network, that is, the UE can use an evolved base station (eNodeB, evolved NodeB), a serving gateway (S-GW, Serving gateway), packet data network gateway (ie PDN gateway, can be abbreviated as P-GW, Packet Data Networkgateway) and other network elements to access the Internet; the second is to access the Internet from a non-3GPP network, usually this method can provide More stable access bandwidth and lower price.

Wherein, for the above-mentioned first access manner, if there are too many users in a cell, or some users occupy a large amount of bandwidth, the overall user experience will be affected.

In order to reduce the bandwidth pressure of the 3GPP core network, the prior art provides a SIPTO (Selected IP Traffic Offload, Selected IP Traffic Offload) solution applied to the 3GPP network, which supports users to access through 3GPP network nodes, The offloading is realized by adding a local packet data network gateway (L-PGW, local PDN gateway).

Specifically, the UE can access the mobile core network (CN, core network) through the base station, the S-GW, and the P-GW. In this solution, the mobility management entity (MME, mobility management entity) can select an L-PGW for the user to conduct traffic uninstallation.

Although the above SIPTO technology can relieve the bandwidth pressure of the mobile core network to a certain extent, it needs to add a network element L-PGW to the 3GPP network, which has a certain impact on the current network architecture and is not convenient for mobile operators to implement.

SUMMARY OF THE INVENTION

The embodiments of the present invention provide a method and device for realizing 3GPP network traffic offloading. Users can use a non-3GPP network gateway to offload traffic of a specific service accessed through a 3GPP network node, that is, use existing equipment to offload part of the traffic on the 3GPP network. The offload is distributed to the non-3GPP network, thereby reducing the burden of the 3GPP core network, and this solution has no impact on the current network architecture, which is beneficial for operators to implement. In addition, in the present invention, a non-3GPP network gateway is used as a device for unloading 3GPP network traffic, which lays a foundation for realizing seamless switching between the 3GPP network access mode and the non-3GPP network access mode, so as to ensure the current access of users. connections to specific services will not be interrupted.

To achieve the above object, the embodiments of the present invention adopt the following technical solutions:

In a first aspect, a method for implementing 3GPP network traffic offloading includes:

The user equipment UE determines that a bearer for accessing a specific service needs to be established, and the specific service is a service accessible via both a 3GPP network and a non-3GPP network;

sending a request for the UE to access the non-3GPP network gateway to the 3GPP network access node serving it; so that the establishment of the bearer for the UE to access the non-3GPP network gateway via the 3GPP network is completed;

The UE accesses the specific service through the established bearer.

In a first possible implementation manner, according to the first aspect,

The request for the UE to access the non-3GPP network gateway includes: the UE identifier, the access point name APN used to point to the non-3GPP network gateway,

Or, the request for the UE to access the non-3GPP network gateway includes: a UE identity, an APN for pointing to the non-3GPP network gateway, and a handover identity.

In a second possible implementation manner, according to the first aspect or the first possible implementation manner, the UE acquires and stores the address information of the non-3GPP network gateway to which it accesses.

In a second aspect, a method for implementing 3GPP network traffic offload is provided, including:

The 3GPP network control network element receives the request sent by the 3GPP network access node for the UE to access the non-3GPP network gateway;

Controlling establishes the bearer for the UE to access the non-3GPP network gateway via the 3GPP network.

In the first possible implementation manner, according to the second aspect,

The request for the UE to access the non-3GPP network gateway includes: the UE identifier, the access point name APN used to point to the non-3GPP network gateway;

Or, the request for the UE to access the non-3GPP network gateway includes: a UE identity, an APN for pointing to the non-3GPP network gateway, and a handover identity.

In the second possible implementation manner, according to the first possible implementation manner, the request for the UE to access the non-3GPP network gateway further includes: location information of the 3GPP network access node;

Alternatively, the request for the UE to access the non-3GPP network gateway further includes: address information of the non-3GPP network gateway.

In a third possible implementation manner, in combination with the second aspect or any of the first two possible implementation manners, the controlling to establish a bearer for the UE to access the non-3GPP network gateway via the 3GPP network includes:

Obtain the address information of the non-3GPP network gateway;

Send a request for the UE to access the non-3GPP network gateway to at least one non-3GPP network gateway corresponding to the address information via the 3GPP network service gateway;

receiving a reply from the non-3GPP network gateway to the request;

If the reply indicates that the bearer between the 3GPP network serving gateway and the non-3GPP network gateway is successfully established, the bearer for the UE to access the 3GPP network serving gateway is established.

In the fourth possible implementation, according to the third possible implementation,

The obtaining of the address information of the non-3GPP network gateway includes: sending a query request to the DNS server; the query request includes: the location information of the 3GPP network access node and the access point name APN for pointing to the non-3GPP network gateway, and receive the address information of the non-3GPP network gateway fed back by the DNS server; or,

Read the address information of the non-3GPP network gateway from the received request for the UE to access the non-3GPP network gateway; or,

Get the address information of the pre-configured non-3GPP network gateway.

In the fifth possible implementation, according to the fourth possible implementation,

The sending a request for the UE to access the non-3GPP network gateway to at least one non-3GPP network gateway corresponding to the address information includes:

When it is necessary to switch the non-3GPP network access to the 3GPP network access, send a request for the UE to access the non-3GPP network gateway to the non-3GPP network gateway corresponding to each of the obtained address information; otherwise, Send a request for the UE to access the non-3GPP network gateway to a corresponding non-3GPP network gateway in the acquired address information.

In a sixth possible implementation manner, according to the second aspect or any one of the first two possible implementation manners, the controlling to establish a bearer for the UE to access the non-3GPP network gateway via the 3GPP network includes:

Send a request for the UE to access the non-3GPP network gateway to the 3GPP network service gateway; so that the 3GPP network service gateway obtains the address information of the non-3GPP network gateway pre-configured by itself, and sends at least one non-3GPP network gateway corresponding to the address information. The 3GPP network gateway sends a request for the UE to access the non-3GPP network gateway;

receiving a reply to the request from the non-3GPP network gateway;

If the reply indicates that the bearer between the 3GPP network serving gateway and the non-3GPP network gateway is successfully established, the bearer for the UE to access the 3GPP network serving gateway is established.

In a seventh possible implementation manner, according to the second aspect, in the case that the bearer of the UE accessing the non-3GPP network gateway via the 3GPP network is not required, the method further includes:

Delete the bearer that the UE accesses the non-3GPP network gateway via the 3GPP network.

In a third aspect, a method for implementing 3GPP network traffic offload is provided, including:

The non-3GPP network gateway receives a request sent by the 3GPP network serving gateway for the UE to access the non-3GPP network gateway;

The reply to the request is forwarded by the 3GPP network service gateway to the 3GPP network control network element; so that the 3GPP network control network element indicates in the reply that the bearer between the 3GPP network service gateway and the non-3GPP network gateway is successfully established In the case of the UE, it is controlled to establish a bearer for the UE to access the 3GPP network serving gateway.

In the second possible implementation manner, according to the third aspect,

The request for the UE to access the non-3GPP network gateway includes: a UE identifier and an APN for pointing to the non-3GPP network gateway;

Or, the request for the UE to access the non-3GPP network gateway includes: a UE identity, an APN for pointing to the non-3GPP network gateway, and a handover identity.

In a third possible implementation manner, according to the second possible implementation manner, if the request for accessing the non-3GPP network gateway of the UE does not include a handover identifier, the method further includes:

Establish the bearer between the 3GPP network service gateway and the non-3GPP network gateway;

assigning address information for accessing the specific service to the UE;

The reply to the request indicates that the bearer establishment between the 3GPP network serving gateway and the non-3GPP network gateway is successful, and includes address information allocated to the UE for accessing the specific service.

In the fourth possible implementation manner, according to the first possible implementation manner, it also includes:

The identifier of the UE currently accessing the non-3GPP network gateway and the identifier of the current access mode of the UE are stored.

In the fifth possible implementation, according to the fourth possible implementation,

If the request for the UE to access the non-3GPP network gateway includes the handover identifier, the method further includes:

Query whether there is a UE identity consistent with the request in the current record of the non-3GPP network gateway;

If it exists, update the identity of the current access mode of the UE, and establish a bearer between the 3GPP network service gateway and the non-3GPP network gateway, and do not re-allocate address information for accessing the specific service for the UE; The reply to the request indicates successful bearer establishment and includes address information previously allocated to the UE for accessing the specific service.

In a sixth possible implementation manner, according to the fourth possible implementation manner, the method further includes:

receiving an authentication message sent by the UE through the access point of the non-3GPP network, where the authentication message includes: the identifier of the UE and the handover identifier;

After the authentication is successful, query whether there is a UE identity consistent with the authentication message in the current record of the non-3GPP network gateway;

If it exists, update the identifier of the current access mode of the UE, and do not re-allocate the address information for accessing the specific service for the UE;

sending an authentication feedback message to the UE, the authentication feedback message including address information previously allocated to the UE for accessing the specific service;

A delete bearer request is sent to the 3GPP serving gateway, so that the UE accesses the bearer deletion of the non-3GPP network gateway via the 3GPP network.

In a fourth aspect, a user equipment UE is provided, including:

Determining unit: used to determine that a bearer needs to be established for accessing a specific service, and the specific service is a service accessible via both a 3GPP network and a non-3GPP network;

Sending unit: used to send the request for the UE to access the non-3GPP network gateway to the 3GPP network access node serving it; so that the bearer establishment of the UE accessing the non-3GPP network gateway via the 3GPP network is completed ;

Access unit: used for the UE to access the specific service through the established bearer.

In the first possible implementation manner, according to the fourth aspect,

The request for the UE to access the non-3GPP network gateway includes: the UE identifier, the access point name APN used to point to the non-3GPP network gateway;

Or, the request for the UE to access the non-3GPP network gateway includes: a UE identity, an APN for pointing to the non-3GPP network gateway, and a handover identity.

In the second possible implementation manner, according to the fourth aspect or the first possible implementation manner, the method further includes:

Storage unit: used to learn and store the address information of the non-3GPP network gateway it accesses.

In a fifth aspect, a 3GPP network control network element is provided, including:

Receiving unit: used to receive the request sent by the 3GPP network access node for the UE to access the non-3GPP network gateway;

Control unit: used to control the establishment of a bearer for the UE to access the non-3GPP network gateway via the 3GPP network.

In the first possible implementation manner, according to the fifth aspect,

The request for the UE to access the non-3GPP network gateway includes: the UE identifier, the access point name APN used to point to the non-3GPP network gateway;

Or, the request for the UE to access the non-3GPP network gateway includes: a UE identity, an APN for pointing to the non-3GPP network gateway, and a handover identity.

In the second possible implementation, according to the first possible implementation,

The request for the UE to access the non-3GPP network gateway further includes: location information of the 3GPP network access node;

Alternatively, the request for the UE to access the non-3GPP network gateway further includes: address information of the non-3GPP network gateway.

In the third possible implementation manner, according to the fifth aspect or any of the first two possible implementation manners,

The 3GPP network control network element further includes: a first sending unit, where the first sending unit is configured to send a request for the UE to access the non-3GPP network gateway to at least one non-3GPP network gateway corresponding to the address information;

The control unit includes: an acquisition module, a first transmission control module, and a first bearer management module; wherein,

Obtaining module: used to obtain the address information of the non-3GPP network gateway;

A first sending control module: configured to control the first sending unit to send a request for the UE to access the non-3GPP network gateway to at least one non-3GPP network gateway corresponding to the address information via the 3GPP network service gateway;

The receiving unit is further configured to receive a reply from the non-3GPP network gateway to the request;

A first bearer management module: configured to establish that the UE accesses the 3GPP network in the case that the bearer between the 3GPP network serving gateway and the non-3GPP network gateway is successfully established in the reply received by the receiving unit The bearer of the service gateway.

In a fourth possible implementation manner, according to the third possible implementation manner, the acquisition module is specifically used for:

Send a query request to the DNS server; the query request includes: the location information of the 3GPP network access node and the access point name APN for pointing to the non-3GPP network gateway, and receives the non-3GPP network gateway fed back by the DNS server address information; or,

From the request received by the receiving unit for the UE to access the non-3GPP network gateway, read the address information of the non-3GPP network gateway; or,

Get the address information of the pre-configured non-3GPP network gateway.

In a fifth possible implementation manner, according to the fourth possible implementation manner, the first transmission control module is specifically configured to:

In the case that the non-3GPP network access needs to be switched to the 3GPP network access, the first sending unit is controlled to send the UE access to the non-3GPP network gateway corresponding to each of the address information obtained by the obtaining module. A request for entering a non-3GPP network gateway; otherwise, control the first sending unit to send a request for the UE to access a non-3GPP network gateway to a corresponding non-3GPP network gateway in the address information obtained by the obtaining module ask.

In a sixth possible implementation manner, according to the fifth aspect or any of the first two possible implementation manners, the 3GPP network control network element further includes: a second sending unit, configured to send the UE connection to the 3GPP network serving gateway A request to enter a non-3GPP network gateway;

The control unit includes: a second transmission control module and a second bearer management module;

The second sending control module: used to control the second sending unit to send a request for the UE to access the non-3GPP network gateway to the 3GPP network service gateway; so that the 3GPP network service gateway obtains its own pre-configured non-3GPP network address information of the gateway, and send a request for the UE to access the non-3GPP network gateway to at least one non-3GPP network gateway corresponding to the address information;

The receiving unit: further configured to receive a reply to the request from the non-3GPP network gateway;

The second bearer management module: for establishing the UE to access the 3GPP network if the reply received by the receiving unit indicates that the bearer between the 3GPP network serving gateway and the non-3GPP network gateway is successfully established The bearer of the service gateway.

In a seventh possible implementation manner, according to the fifth aspect, the control unit is further configured to:

If the bearer for the UE to access the non-3GPP network gateway via the 3GPP network is unnecessary, the bearer for the UE to access the non-3GPP network gateway via the 3GPP network is deleted.

In a sixth aspect, a non-3GPP network gateway is provided, including:

Receiving unit: used to receive a request sent by the 3GPP network serving gateway for the UE to access the non-3GPP network gateway;

Sending unit: used for forwarding the reply to the request by the 3GPP network service gateway to the 3GPP network control network element; so that the 3GPP network control network element indicates between the 3GPP network service gateway and the non-3GPP network gateway in the reply. In the case that the establishment of the bearer between the UEs is successful, the establishment of the bearer for the UE to access the 3GPP network serving gateway is controlled.

In the first possible implementation manner, in combination with the sixth aspect,

The request for the UE to access the non-3GPP network gateway includes: a UE identifier and an APN for pointing to the non-3GPP network gateway;

Alternatively, it includes: the UE identity, the APN for pointing to the non-3GPP network gateway, and the handover identity.

In the second possible implementation manner, combined with the first possible implementation manner, it also includes:

The first establishing bearer unit: used to establish a bearer between the 3GPP network service gateway and the non-3GPP network gateway;

allocation unit: used to allocate address information for accessing the specific service to the UE;

The reply to the request indicates that the bearer establishment between the 3GPP network serving gateway and the non-3GPP network gateway is successful, and includes address information allocated to the UE for accessing the specific service.

In a third possible implementation manner, combined with the sixth aspect, the method further includes:

Storage unit: used to store the identifier of the currently accessed UE and the identifier of the current access mode of the UE.

In the fourth possible implementation, combined with the third possible implementation, it also includes:

The first query unit: used to query whether there is a UE identity consistent with the request in the current record;

a first updating unit: configured to update the identity of the current access mode of the UE in the saving unit when the first query unit finds that there is a consistent UE identity;

The second establishing bearer unit: used to establish the bearer between the 3GPP network service gateway and the non-3GPP network gateway;

The reply to the request indicates that the bearer is established successfully, and includes the address information previously allocated to the UE for accessing the specific service; wherein the non-3GPP network gateway does not reallocate the UE for accessing the specific service. Address information for the specific service.

In the fifth possible implementation manner, in combination with the third possible implementation manner, the method further includes: a second query unit and a second update unit;

The receiving unit is further configured to: receive an authentication message sent by the UE through an access point of a non-3GPP network, where the authentication message includes: an identifier of the UE and a handover identifier;

The second query unit is used to query whether there is a UE identity consistent with the authentication message in the current record of the non-3GPP network gateway after the authentication is successful;

a second updating unit: configured to update the identity of the current access mode of the UE in the saving unit when the second query unit finds that there is a consistent UE identity;

The sending unit is further configured to: send an authentication feedback message to the UE, where the authentication feedback message includes address information previously allocated to the UE for accessing the specific service; wherein the non-3GPP network gateway does not reallocating address information for accessing the specific service for the UE;

The sending unit is further configured to: send a bearer deletion request to the 3GPP serving gateway, so that the UE accesses the bearer deletion of the non-3GPP network gateway via the 3GPP network.

The embodiments of the present invention provide a method and device for realizing 3GPP network traffic offloading, adopting a non-3GPP network gateway as a device for offloading traffic, that is, offloading 3GPP network traffic through a non-3GPP network, thereby reducing the burden on the 3GPP core network , and this solution has no impact on the current network architecture, which is beneficial for operators to implement. In addition, in the present invention, a non-3GPP network gateway is used as a device for unloading 3GPP network traffic, which lays a foundation for realizing seamless switching between the 3GPP network access mode and the non-3GPP network access mode, so as to ensure the current access of users. connections to specific services are not interrupted.

Description of drawings

In order to illustrate the technical solutions of the embodiments of the present invention more clearly, the following briefly introduces the accompanying drawings that need to be used in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only some of the present invention. In the embodiments, for those of ordinary skill in the art, other drawings can also be obtained according to these drawings without any creative effort.

1 is a schematic diagram of a user equipment accessing a specific service through a 3GPP network and a non-3GPP network in the prior art;

2 is a schematic diagram of a user equipment accessing a specific service through a method provided by an embodiment of the present invention;

3 is a method for implementing 3GPP network traffic offloading provided by an embodiment of the present invention;

4 is a schematic diagram of a user equipment accessing a specific service through another method provided by an embodiment of the present invention;

5 is a flowchart corresponding to another method for implementing 3GPP network traffic offloading provided by an embodiment of the present invention;

6 is a flowchart corresponding to another method for implementing 3GPP network traffic offloading provided by an embodiment of the present invention;

7 is a flowchart corresponding to another method for implementing 3GPP network traffic offloading provided by an embodiment of the present invention;

FIG. 8 is a schematic diagram of a user equipment according to an embodiment of the present invention;

FIG. 9 is a schematic diagram of another user equipment provided by an embodiment of the present invention;

10 is a schematic diagram of a 3GPP network control network element according to an embodiment of the present invention;

FIG. 11 is a schematic diagram of another 3GPP network control network element provided by an embodiment of the present invention;

12 is a schematic diagram of another 3GPP network control network element provided by an embodiment of the present invention;

13 is a schematic diagram of a non-3GPP network gateway according to an embodiment of the present invention;

14 is a schematic diagram of another non-3GPP network gateway provided by an embodiment of the present invention;

15 is a schematic diagram of another non-3GPP network gateway provided by an embodiment of the present invention;

16 is a schematic diagram of another non-3GPP network gateway provided by an embodiment of the present invention;

FIG. 17 is a schematic diagram of another user equipment provided by an embodiment of the present invention;

18 is a schematic diagram of another 3GPP network control network element provided by an embodiment of the present invention;

FIG. 19 is a schematic diagram of another non-3GPP network gateway provided by an embodiment of the present invention.

Detailed ways

The method, device, and system for implementing 3GPP network traffic offloading provided by the embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

The embodiments of the present invention are applied to a mixed networking scenario of a 3GPP network and a non-3GPP network. By way of example, the above-mentioned 3GPP network includes, but is not limited to, a Wideband Code Division Multiple Access (WCDMA, Wideband Code Division Multiple Access) network, a time division synchronized code division multiple access network Address (TDSCDMA, Time Division) Synchronous CodeDivision Multiple Access) network, Long Term Evolution (LTE, Long Term Evolution), non-3GPP network including but not limited to wireless local area network (WLAN, Wireless Local Aero Network), WiMAX.

As shown in FIG. 1 , in the prior art, under the management and control of a 3GPP network control network element, a UE can access a specific service through a 3GPP network access node, a 3GPP service gateway and other devices, that is, a path a in FIG. 1 . The specific service is a service accessible via both a 3GPP network and a non-3GPP network. For example, the above-mentioned specific service may be the Internet. For the convenience of description, the Internet is used as an example for description in the embodiments of the present invention. Of course, a specific service, that is, the b channel in FIG. 2 , can also be accessed through devices such as a non-3GPP network access point and a non-3GPP gateway.

In order to utilize the non-3GPP network gateway to realize 3GPP network traffic offloading, the present invention provides a method for realizing 3GPP network traffic offloading, and establishes the c path in FIG. 2 . As shown in Figure 3, the method specifically includes:

S001. The UE determines that a bearer for accessing the Internet needs to be established.

For example, when the user triggers the shortcut of the UE's browser, the UE determines that a bearer for accessing the Internet needs to be established. For another example, when the user is accessing the Internet through the UE, if the UE finds that it is possible to switch the network (usually from the non) 3GPP network to the 3GPP network, corresponding to Fig. Bearers for accessing the Internet.

S002, the UE sends a request for the UE to access the non-3GPP network gateway to the 3GPP network access node serving the UE.

Optionally, if the bearer is established for the first time this time, the request for the UE to access the non-3GPP network gateway includes: the UE identifier and the access point name APN for pointing to the non-3GPP network gateway. Or, optionally, if the bearer needs to be established due to network handover this time, the request for the UE to access the non-3GPP network gateway includes: the UE identity, the APN for pointing to the non-3GPP network gateway, and the handover identity .

Further optionally, if the bearer needs to be established due to network handover this time, and the UE can know and save the address information of the non-3GPP network gateway to which it accesses, then the request for the UE to access the non-3GPP network gateway It may also include: address information of the non-3GPP network gateway. Of course, if the UE cannot know the address information of the non-3GPP network gateway to which it accesses, the address information of the non-3GPP network gateway can be obtained in subsequent steps.

S003, the 3GPP network access node sends a request for the UE to access the non-3GPP network gateway to the 3GPP network control network element.

Optionally, the 3GPP network access node may directly forward the received request to the 3GPP network control network element. Or, optionally, the 3GPP network access node may process the received request and send it to the 3GPP network control network element. Among them, the processing process may be adding its own location information, and of course, it may also be conventional processing such as adding or subtracting packet headers.

Through the above S003, the 3GPP network control network element receives the request sent by the 3GPP network access node. Afterwards, the 3GPP network controls the network element to control the establishment of the bearer for the UE to access the non-3GPP network gateway via the 3GPP network, specifically including: S004-S012; wherein, S004 is an optional step.

S004, the 3GPP network control network element can obtain the address information of the non-3GPP network gateway.

The obtaining of the address information of the non-3GPP network gateway includes the following three optional ways:

Mode 1: The 3GPP network control network element sends a query request to the DNS server; the query request includes: the location information of the 3GPP network access node and the access point name APN for pointing to the non-3GPP network gateway, and receives the DNS The address information of the non-3GPP network gateway returned by the server.

Manner 2: The 3GPP network control network element reads the address information of the non-3GPP network gateway from the received request for the UE to access the non-3GPP network gateway. This mode specifically refers to the case where the IP address of the non-3GPP network gateway is statically configured in the 3GPP access node.

Mode 3: The 3GPP network controls the network element to obtain the address information of the pre-configured non-3GPP network gateway. This mode specifically refers to the situation that the IP address of the non-3GPP network gateway is statically configured in the 3GPP network control network element.

S005, the 3GPP network control network element sends a request for the UE to access the non-3GPP network gateway to the 3GPP network service gateway.

Optionally, the above request includes the IP address of at least one non-3GPP network gateway.

Or, optionally, if the 3GPP network control network element knows through the prior configuration that the IP address of the non-3GPP network gateway is statically configured in the 3GPP network service gateway, therefore, the 3GPP network control network element sends the UE to the 3GPP network service gateway. In the request to access the non-3GPP network gateway, the IP address of the non-3GPP network gateway can be defaulted. At this time, S004 is not necessary.

Correspondingly, the 3GPP network service gateway receives the request sent by the 3GPP network control network element for the UE to access the non-3GPP network gateway.

S006, the 3GPP network service gateway obtains the address of the non-3GPP network gateway.

Optionally, if the 3GPP network service gateway obtains the IP address of at least one non-3GPP network gateway from the request received by the UE to access the non-3GPP network gateway, the 3GPP network service gateway sends the obtained IP address to the The non-3GPP network gateway corresponding to the IP address sends a request for the UE to access the non-3GPP network gateway.

Or, optionally, if the 3GPP network service gateway does not obtain the IP address of the non-3GPP network gateway from the request received by the UE to access the non-3GPP network gateway, the 3GPP network service gateway obtains its own pre-configured non- - The IP address of the 3GPP network gateway, and sending a request for the UE to access the non-3GPP network gateway to at least one non-3GPP network gateway corresponding to the IP address.

It should be noted that, in the case where the non-3GPP network access needs to be switched to the 3GPP network access, if the UE does not save the address of the non-3GPP network gateway connected before, the non-3GPP network gateway obtained by the 3GPP network service gateway The IP address of the network gateway may be one or more.

S007. The 3GPP network service gateway sends a request for the UE to access the non-3GPP network gateway to at least one non-3GPP network gateway.

Correspondingly, the non-3GPP network gateway receives a request sent by the 3GPP network serving gateway for the UE to access the non-3GPP network gateway.

S008, the non-3GPP network gateway performs processing according to the received request of the UE to access the non-3GPP network gateway.

If the request received by the non-3GPP network gateway for the UE to access the non-3GPP network gateway does not contain a handover identifier, specifically, the non-3GPP network gateway needs to do the following:

First, establish the bearer between the 3GPP network service gateway and the non-3GPP network gateway;

secondly, assigning address information for accessing the specific service to the UE;

Then, the reply to the request indicates that the bearer establishment between the 3GPP network serving gateway and the non-3GPP network gateway is successful, and includes: address information allocated to the UE for accessing the specific service.

And optionally, the non-3GPP network gateway may also store the identifier of the UE currently accessing the non-3GPP network gateway and the identifier of the current access mode of the UE.

If the request for the UE to access the non-3GPP network gateway includes a handover identifier, specifically, the non-3GPP network gateway needs to do the following:

Query whether there is a UE identity consistent with the request in the current record of the non-3GPP network gateway; if so, update the identity of the UE's current access mode, establish a bearer, and do not reassign the UE for access address information of the specific service; the reply to the request indicates that the bearer is established successfully, and includes the address information previously allocated to the UE for accessing the specific service.

S009, the non-3GPP network gateway sends a reply to the above request to the 3GPP network service gateway.

S010, the 3GPP network service gateway performs processing according to the received reply.

Specifically, the 3GPP network service gateway receives the reply from the non-3GPP network gateway to the above request. If the reply indicates that the bearer between the 3GPP network service gateway and the non-3GPP network gateway is successfully established, it needs to go through subsequent steps to establish The UE accesses the bearer of the 3GPP network serving gateway. The processing in this step may be to add address information for accessing the particular service in the received reply.

S011. The 3GPP network service gateway sends the processed reply to the above request to the 3GPP network control network element.

S012 , the 3GPP network controls the network element to control and establish the bearer for the UE to access the 3GPP network serving gateway.

Specifically, if the reply received by the 3GPP network control network element indicates that the bearer between the 3GPP network serving gateway and the non-3GPP network gateway is successfully established, the control to establish the bearer for the UE to access the 3GPP network serving gateway is controlled.

S013, the UE accesses the Internet through the established bearer.

Optionally, if the bearer is established for the first time this time, the UE will access the Internet through the address information allocated to it by the non-3GPP network gateway for accessing the Internet this time; or, optionally, if this time is If a bearer needs to be established due to network handover, the UE will access the Internet through the address information previously allocated to it by the non-3GPP network gateway for accessing the Internet, thereby ensuring that handover will not cause communication interruption.

In a method for implementing 3GPP network traffic offloading provided by the embodiment of the present invention, a non-3GPP network gateway is used as a device for offloading traffic, that is, the traffic of the 3GPP network is offloaded through the non-3GPP network, thereby reducing the burden on the 3GPP core network, and This solution has no impact on the current network architecture and is beneficial for operators to implement.

Through the above steps, the UE can access the Internet using the path c in FIG. 2 .

There is another handover situation. For example, after the UE uses the c path in Figure 2 to access the Internet, if the UE finds a non-3GPP network that meets the conditions, it can also switch from the c path in Figure 2 to the b path.

The specific steps are as follows:

1) The UE sends an authentication message to the authentication server through the access point of the non-3GPP network via the non-3GPP network gateway, where the authentication message includes: the identifier of the UE and the handover identifier.

2) The authentication server performs authentication according to the received authentication message, and sends an authentication feedback message to the non-3GPP network gateway after the authentication server succeeds in authentication.

3) The non-3GPP network gateway inquires whether there is a UE identity consistent with the authentication message in its current record. If it exists, the identifier of the current access mode of the UE is updated, and the address information for accessing the specific service is not reassigned to the UE.

4) The non-3GPP network gateway sends an authentication feedback message to the UE, where the authentication feedback message includes address information previously allocated to the UE for accessing the specific service.

5) The non-3GPP network gateway sends a bearer deletion request to the 3GPP serving gateway, so that the UE accesses the bearer deletion of the non-3GPP network gateway via the 3GPP network.

In a method for implementing 3GPP network traffic offloading provided by the embodiment of the present invention, a non-3GPP network gateway is used as a device for offloading traffic, that is, the traffic of the 3GPP network is offloaded through the non-3GPP network, thereby reducing the burden on the 3GPP core network, and This solution has no impact on the current network architecture and is beneficial for operators to implement. In addition, in the present invention, a non-3GPP network gateway is used as a device for unloading 3GPP network traffic, which lays a foundation for realizing seamless switching between the 3GPP network access mode and the non-3GPP network access mode, so as to ensure the current access of users. connections to specific services are not interrupted.

The present invention provides another method for realizing 3GPP network traffic offloading, wherein the LTE network and WLAN are taken as examples for description. At this time, the 3GPP network access node is an evolved base station (eNodeB, Evolved Node B), and the 3GPP network control network The element is the MME, the 3GPP network service gateway is the S-GW, and the non-3GPP network gateway is a broadband network gateway (BNG, Broadband Network Gateway).

In order to unload the part of the traffic that the UE accesses the Internet through the 3GPP network, the embodiment of the present invention adopts the method described below to establish the connection shown in the direction of line c' in FIG. 4 , that is, use the BNG to unload the traffic that accesses the Internet through the 3GPP network. To realize the above-mentioned offloading function, it is necessary to realize the P-GW function on the basis of the existing BNG.

It should be pointed out that in the process of establishing the connection shown in the direction of line c' in Figure 4, the request of the UE to access the non-3GPP network gateway does not refer to a specific request, but is a general term for a type of request, that is, In the process of establishing the connection shown in the direction of line c' in Figure 4, under the control of the MME, the established bearers include: the bearer between the UE and the eNodeB, the bearer between the eNodeB and the S)GW, the S-GW and the Bearers between BNGs, the specific requests used to establish bearers between different network elements are generally different (requests with different indication information are also different requests), but the purpose is to enable UEs to access non-3GPP network gateway. When the specific steps are described below, for the sake of clarity and to avoid confusion, a request for establishing a bearer between different network elements is directly used for description.

Moreover, when the request of the UE to access the non-3GPP network gateway passes through any network element in the eNodeB, MME, S-GW, and BNG, the processing performed by the above network element includes: adding or reducing packet headers and other conventional processing, and then processing the processed The above-mentioned request forwarding, this processing is a conventional processing in the prior art, so in this embodiment, the conventional processing of this network element is not described in detail. Further, the above network elements may also add or remove certain parameters according to specific conditions.

The specific steps are shown in Figure 5:

S101: The UE sends a PDN connection request to the eNodeB.

The above PDN connection request is a request for the UE to access the non-3GPP network gateway.

The UE adds access point name (APN, access point name) information to the above PDN connection request. The above-mentioned APN can represent a type of service, that is, point to a BNG (there may be only one of the above-mentioned BNGs, or there may be a plurality of the above-mentioned BNGs). For example, the format of the above-mentioned APN may be marked as: offload BNG.

S102: The eNodeB performs processing according to the PDN connection request received by the eNodeB.

Specifically, after receiving the PDN connection request, the eNodeB adds its own location information to the request, and then sends the processed PDN connection request to the MME.

Optionally, the foregoing location information includes: a tracking area code (TAI (Tracking Area Identity) or an eNodeB identity (ID (identity).

S103: The eNodeB sends the processed PDN connection request to the MME.

S104: The MME performs processing according to the PDN connection request sent by the MME received by the eNodeB.

Generally, the session created is a bearer, that is, a default bearer, and a new dedicated bearer can be established under this session later.

Specifically, after receiving the PDN connection request sent by the eNodeB, the MME obtains the information that the UE wishes to offload traffic through the BNG according to the APN in the PDN connection request. Therefore, the MME needs to know the IP address of the above-mentioned BNG. Exemplarily, the MME can learn the IP address of the BNG in the following four ways (one of which has been configured in advance):

Mode 1. The MME dynamically obtains the IP of the BNG according to the principle of geographical proximity.

After receiving the above-mentioned PDN connection request, the MME obtains the above-mentioned APN information and location information from the above-mentioned request, and sends the above-mentioned information to a Domain Name System (DNS, domain name system) server, and the DNS server parses the above-mentioned APN through the location information, and obtains The IP address of the above BNG.

The specific method for the DNS server to obtain the IP address of the BNG will be described in detail below:

First, a special APN can be defined, which can represent a type of service, that is, point to a BNG (there may be only one of the above-mentioned BNGs, or there may be multiple of the above-mentioned BNGs). For example, the format of the above-mentioned APN can be marked as: OffloadBNG.

Second: the BNG needs to be registered in the operator's DNS server in advance, and the registration information of the BNG includes the IP address and location information of the BNG, and the registration information of at least one BNG forms a BNG list. The location information of the BNG in the above-mentioned BNG list may be TAI (Tracking area identity), or the eNodeB ID to which the BNG belongs.

The DNS server receives the location information of the APN and the eNodeB with the offload BNG flag sent by the MME. By parsing the APN information, it is known that the APN points to the BNG, then searches the BNG list, and finds the BNG that is geographically close to the location according to the received location information. The above-mentioned BNG may exist only one or more than one (in this case, the above-mentioned UE is located in an area where multiple BNGs overlap), and the DNS server only needs to report all the IP addresses of the BNGs that meet the conditions to the MME.

Mode 2: Statically configure the IP address of the BNG in the eNodeB.

If the IP address of the BNG is statically configured in the eNodeB, the BNG corresponding to the coverage area of the eNodeB is obtained according to the result of network planning, and configured in the eNodeB. There may be one or multiple BNGs corresponding to one eNodeB (the eNodeB is located in the cross coverage area of multiple BNGs).

If the MME obtains the IP address of the BNG in the above-mentioned manner 2, the above-mentioned S102 further includes: the eNodeB adds the IP address of the BNG that satisfies the condition in the above-mentioned PDN connection request and sends it to the MME.

After the MME receives the PDN connection request sent by the eNodeB, according to the APN in the PDN connection request, it learns that the UE wants to offload the traffic through the BNG. Therefore, the MME learns that it needs to know the IP address of the BNG. Further, the MME obtains the information from the PDN connection request. The IP address of the BNG that meets the condition.

Mode 3: Statically configure the IP address of the BNG in the MME.

If the IP address of the BNG is statically configured in the MME, according to the results of network planning, it can be configured with the MME as the granularity, that is, each MME only saves one BNG IP address, or with the eNodeB as the granularity, that is, each MME contains a list including each eNodeB belonging to the above-mentioned MME and the BNG corresponding to the eNodeB. The MME selects a BNG that satisfies the condition according to the foregoing eNodeB location information, and the foregoing BNG may be one or multiple (the eNodeB is located in the cross coverage area of multiple BNGs).

After the MME receives the PDN connection request sent by the eNodeB, according to the APN in the PDN connection request, it learns that the UE wishes to offload the traffic through the BNG. Therefore, the MME learns that the IP address of the BNG needs to be obtained. Further, the MME selects from the above list of its own. The IP address of the BNG that meets the condition.

The MME uses any of the above methods 1-3 to obtain the IP address of the BNG that meets the conditions. If the above-mentioned BNG has more than one IP address, the MME needs to select one of the above-mentioned IP addresses. For example, the MME can always is the first in the list of BNGs that selects the condition.

The MME adds the IP address of the above-mentioned BNG to the session creation request.

Mode 4: Statically configure the IP address of the BNG in the S-GW.

The specific configuration method is the same as the configuration method described in Method 3 above.

After receiving the PDN connection request sent by the eNodeB, the MME learns the information that the UE wishes to offload traffic through the BNG according to the APN in the PDN connection request. At this time, the MME knows that the S-GW has been configured with the IP address of the relevant BNG, so the MME will create a session request The IP address of the BNG in is set to empty.

S105, the MME sends a session creation request to the S-GW.

The session creation request sent by the MME to the S-GW is a request for the UE to access the non-3GPP network gateway.

S106, the S-GW performs processing according to the received request for creating a session.

Specifically, if the MME adopts the method mode 1-3 in S104, the MME obtains the IP address of the BNG and adds it in the session creation request and sends it to the S-GW, and the S-GW can obtain the IP address of the BNG from the session creation request address;

If the MME adopts method 4 in S104, the S-GW receives the session creation request sent by the MME, and finds that the IP address of the BNG in this request is set to be empty, then further, the S-GW selects the BNG from its own configuration list The IP addresses that meet the conditions are obtained.

If the above-mentioned BNG has more than one IP address, the S-GW needs to select one of the above-mentioned IP addresses. For example, the S-GW may always select the first one in the list of the BNGs that satisfy the condition.

S107: The S-GW sends a session creation request to the BNG according to the obtained IP address of the BNG.

S108. The BNG performs processing according to the received session creation request.

After the above-mentioned BNG receives the above-mentioned session creation request, it needs to reply to the received session creation request. For example, the reply to the session creation request may be Create Session Response, which includes an identifier of session establishment success or session establishment failure.

Generally, when a PDN connection is established, it is an indicator that the session is successfully established. The processing performed by the BNG includes:

1) Establish a bearer with the S-GW.

2) Allocate an IP address to the above-mentioned UE, and this address is used for the UE to access the Internet through the above-mentioned BNG, and the reply to the above-mentioned session creation request also includes this IP address.

3) Record the identifier of the UE and the current connection mode identifier, where the current connection mode identifier is used to indicate that the eNodeB or the WLAN is currently used to access the BNG.

S109 , the BNG sends a reply to the above session creation request to the S-GW.

S110. The S-GW performs processing according to the received reply to the session creation request.

Specifically, if any one of the above methods 1-3 is adopted, the S-GW will process the reply to the session creation request it receives. At this time, the above request may not carry the IP address of the BNG currently establishing the bearer, because The MME is already aware of this information;

If the above method 4 is adopted, the S-GW may add the IP address of the BNG for which the bearer is currently established to the reply to the above-mentioned session creation request, so that the MME can know the BNG that the UE is currently connected to.

S111. The S-GW sends the processed reply to the session creation request to the MME.

S112: The MME controls the establishment of the corresponding bearer between the eNodeB and the S-GW and the bearer between the UE and the eNodeB according to the received reply to the session creation request.

Optionally, if the UE and the network support related functions, the MME may also carry the IP address of the BNG in the corresponding indication information when controlling the establishment of the bearer between the eNodeB and the S-GW and the radio bearer between the UE and the eNodeB. Sent to the UE, the UE can obtain the IP address of the BNG from the above request and save it.

At this time, the above-mentioned UE establishes the connection shown in the direction of line b in FIG. 1 , and the traffic of the UE to access the Internet is offloaded through the above-mentioned BNG.

According to the method described above, there are also the following two switching scenarios:

Handover scenario 1: As shown in Figure 4, the UE has established a connection in the b' line direction, and accesses the BNG through the WLAN to access the Internet. When the UE detects that the signal strength of the WLAN is lower than the threshold, in order to ensure that the connection to the Internet is not interrupted, the UE will initiate the switching process from the WLAN access mode to the eNodeB access mode (to establish the direction of line c' in Figure 4 ). connection to continue accessing the Internet.

The specific steps for switching scenario 1 are shown in Figure 6:

S201. The UE sends a PDN connection request to the eNodeB.

The above request may carry an identifier indicating a handover request, for example, it may be HandoverIndication.

When the above-mentioned UE detects that the above-mentioned WLAN signal strength is lower than the threshold, in order to ensure the continuity of the currently accessed Internet connection, it is desirable to switch from the WLAN access BNG mode to the eNodeB access BNG mode.

The UE sends a PDN connection request to its home eNodeB, and the UE will carry relevant information in the above request, and the above relevant information includes APN information.

Optionally, the above-mentioned related information may also include location information.

Alternatively, if the UE can obtain the IP address of the BNG from the WLAN and the above PDN connection request message is extended to support carrying the IP address of the BNG, the above related information may include the IP address of the BNG.

S202, the eNodeB performs processing according to the received PDN connection request.

Specifically, after receiving the PDN connection request, the eNodeB adds its own location information to the request. Optionally, the foregoing location information may include: a tracking area code (TAI (Tracking Area Identity) or an eNodeB identity (ID (identity).

S203. The eNodeB sends the processed PDN connection request to the MME.

S204, the MME performs processing according to the received PDN connection request.

Specifically, the MME obtains information from the PDN connection request:

If the obtained information directly includes the IP address of the BNG, then the IP address of the BNG is unique;

If there is no IP address of BNG in the information obtained above, but APN information and location information can be obtained (where the location information is only provided in Mode 1), then the APN information and location information are used, and any of the first four methods described in S104 above is used. One (one of them has been configured in advance) to learn the IP address of the BNG:

If the MME adopts the IP address of the BNG learned in any of the modes 1-3, the learned IP address of the BNG may be one or more, which is different from the non-handover PDN connection establishment (the MME obtains the PDN connection request from the The acquired information also includes the identification of whether the current PDN connection request is a handover, so that the MME can know whether the current PDN connection request is a handover). Create session request.

If the MME adopts the IP address of the BNG obtained in method 4, the MME will learn the information that the UE wishes to offload the traffic through the BNG according to the APN in the PDN connection request. At this time, the MME knows that the S-GW has been configured with the relevant IP address of the BNG. The IP address of the BNG in the MME create session request is set to null.

S205. The MME sends the processed session creation request to the S-GW.

S206, the S-GW performs processing according to the session creation request received by the S-GW.

Specifically, if the S-GW can obtain the IP address of the BNG from the session creation request, the obtained IP address of the BNG at this time may be one or more;

If the MME adopts the method 4 in S104 in S204, the S-GW receives the session creation request sent by the MME, and finds that the IP address of the BNG in this request is set to be empty, then further, the S-GW configures itself from the The addresses that meet the conditions are obtained from the IP addresses of the BNGs in the list. At this time, the obtained IP addresses of the BNGs may be one or more.

S207. The S-GW sends the processed session creation request to the BNG.

S208. The BNG performs processing according to the session creation request received by the BNG.

Specifically, after the BNG receives the above-mentioned session creation request, it will check the identity of the UE currently recorded by itself and the identity of the current connection mode, and make the following judgments:

If the BNG finds that one of the currently recorded UE identities is the same as the UE identity that sent the above session creation request, the BNG establishes a bearer with the S-GW, and the BNG carries the road establishment success ID in the reply to the above session creation request.

It is mainly pointed out that after the BNG finds the identity of the UE, it can know what kind of access mode the current connection mode is through the current connection mode identification. The above two access modes need to be entered from different interfaces of the BNG. , so after the BNG bearer is established, it needs to switch the traffic to the new bearer and release the original session.

Then, the BNG updates the connection mode identifier corresponding to the above-mentioned UE.

If the BNG does not find the UE identity that sends the session creation request in the currently recorded UE IDs, the BNG will carry the road establishment failure ID in the reply to the session creation request.

Because there is only one BNG currently connected to the UE, there is only one BNG that carries the road establishment success flag in the reply to the above session creation request. The above IP address for accessing the Internet is used, thus ensuring the continuity of the UE's current Internet connection.

S209. The BNG sends a reply to the above session creation request to the S-GW.

S210. The S-GW performs processing according to the received reply to the session creation request.

Specifically, there may be one or more responses to the session creation request received by the S-GW, but only one of the responses to the session creation request sent by the BNG carries the route-building success identifier and the IP assigned by the BNG for the UE to access the Internet address.

For the BNG whose reply message carries the road establishment success identifier, and the above method 4 is adopted, the S-GW needs to further add the IP address of the BNG to the above reply to the session creation request, so that the MME can know the current UE connection BNG.

S211. The S-GW sends the processed reply to the session creation request to the MME.

S212 , the MME controls the establishment of the bearer between the eNodeB and the S-GW and the bearer between the UE and the eNodeB according to the received reply to the session creation request.

Through the above steps S201-S212, the above-mentioned UE will switch from the way of accessing the above-mentioned BNG from the WLAN to the way of accessing the above-mentioned BNG by the eNodeB, while ensuring the continuity of the above-mentioned Internet connection.

Handover scenario 2: As shown in Figure 4, the UE has established a connection in the b' line direction, accesses the BNG through the eNodeB, and accesses the Internet, but when the above-mentioned UE detects that the above-mentioned WLAN signal strength is higher than or equal to the threshold, the UE will initiate The switching process from the eNodeB access mode to the WLAN access mode is to establish a connection in the direction of the c' line to continue accessing the Internet.

As shown in Figure 7, the specific steps for switching scenario 2 are as follows:

S301. The UE associates with an access point (AP, Access Point) of the WLAN.

When the above-mentioned UE detects that the above-mentioned WLAN signal strength is higher than or equal to the threshold, it wishes to switch from the current eNodeB access mode to the WLAN access BNG mode. Then, the UE first associates with the AP of the WLAN (this step is in the prior art, and the detailed process is not repeated here).

S302, the UE sends an authentication message to the BNG.

Illustratively, in this embodiment, the authentication mode of EAP-SIM/AKA/AKA' is used as an example, the UE sends an authentication message to the BNG, and the above-mentioned authentication message includes the Handover Indication.

S303. The BNG sends the received authentication message to the authentication server.

After receiving the above authentication message, the BNG can learn the identity of the UE and the connection type (handover request). The BNG sends the above authentication message to the authentication server (the specific authentication process is in the prior art, which is not repeated here).

S304, the authentication server performs authentication processing according to the authentication message received by the authentication server.

S305, the authentication server sends the authentication feedback message to the BNG.

S306. The BNG performs processing according to the received authentication feedback message.

Specifically, after the BNG receives the authentication feedback message sent by the authentication server, if the feedback message indicates that the authentication is successful, the BNG searches its currently recorded UE identity, and if it finds that one of its currently recorded UE identities is the same as the above-mentioned UE identity that initiated the authentication , the BNG can continue to use the current IP address for accessing the Internet to the UE (ie, assign the current IP address for accessing the Internet to the UE), which ensures the continuity of the connection that previously accessed the Internet.

S307. The BNG sends the processed authentication feedback message to the UE.

The processed authentication feedback message may include the IP address allocated by the BNG to the UE for accessing the Internet.

S308. The BNG sends a bearer deletion request to the S-GW.

The BNG switches the current bearer traffic accessed from the S-GW to the access from the WLAN through the handover request indicated by the learned connection type, and the BNG updates the connection mode identifier corresponding to the above UE.

The BNG sends a bearer deletion request to the S-GW. For example, the above bearer deletion request may be Delete BearerRequest.

S309, the UE performs processing according to the authentication feedback message of the BNG received by the UE.

Specifically, the UE receives the authentication feedback message from the BNG, and obtains the IP address for accessing the Internet from it. If the IP address for accessing the Internet is the same as the previous IP address, the UE also switches the current access traffic through the eNodeB to the WLAN access.

S310. The S-GW performs processing according to the received bearer deletion request.

S311. The S-GW sends the processed bearer deletion request to the MME.

S312. The MME performs processing according to the bearer deletion request received by the MME.

Specifically, after receiving the bearer deletion request, the MME controls to delete the bearer between the eNode and the S-GW, and between the UE and the eNodeB.

S313. The MME feeds back a bearer deletion response to the S-GW.

For example, the above-mentioned delete bearer response may be a Delete Bearer Response.

S314. The S-GW sends a bearer deletion response to the BNG.

Through the above steps S301-S314, the above-mentioned UE switches from the state of accessing the above-mentioned BNG from the eNodeB to the state of accessing the above-mentioned BNG through the WLAN, while ensuring the continuity of the above-mentioned Internet connection.

There is also such a situation. If the location of the UE changes, it may cause that the AP of the above-mentioned WLAN does not belong to the BNG that has been accessed through the eNodeB before. At this time, the UE will also be authenticated successfully, but the BNG is currently recorded. If the above UE identity is not found in the UE identity, the BNG will assign a new Internet IP address to the UE. After the UE receives the new IP address, for example, the following processing can be performed:

In order to ensure the continuity of the Internet connection currently accessed by the UE, the UE can be configured by default to not perform handover in this case, continue to use the eNodeB access mode, and use the Internet accessed through the BNG accessed by the eNodeB. At this time, the UE may not respond to the DHCPOffer message of the BNG. After the UE enters the idle state, the UE can perform BNG re-selection.

Whether to perform handover can also be configured by the UE, and whether to handover can be determined by displaying prompt information to the user or by pre-configuring or monitoring whether the current user's service has continuity requirements through software. At this time, if the UE decides to switch, the UE directly uses the new IP address to access the Internet from the WLAN. The session between the UE and the original BNG will be deleted by the original BNG after a certain period of inactivity.

In a method for implementing 3GPP network traffic offloading provided by the embodiment of the present invention, a non-3GPP network gateway is used as a device for offloading traffic, that is, the traffic of the 3GPP network is offloaded through the non-3GPP network, thereby reducing the burden on the 3GPP core network, and This solution has no impact on the current network architecture and is beneficial for operators to implement. In addition, in the present invention, a non-3GPP network gateway is used as a device for unloading 3GPP network traffic, which lays a foundation for realizing seamless switching between the 3GPP network access mode and the non-3GPP network access mode, so as to ensure the current access of users. connections to specific services are not interrupted.

An embodiment of the present invention also provides a user equipment 70, as shown in FIG. 8, including:

Determining unit 71: for determining a bearer for accessing a specific service needs to be established, and the specific service is a service accessible via both a 3GPP network and a non-3GPP network;

Sending unit 72: configured to send a request for the UE to access the non-3GPP network gateway to the 3GPP network access node serving it; so that a bearer for the UE to access the non-3GPP network gateway via the 3GPP network is established Finish;

Access unit 73: used for the UE to access the specific service through the established bearer.

As shown in FIG. 9 , optionally, a storage unit 74 may be further included: for acquiring and storing the address information of the non-3GPP network gateway accessed by the storage unit 74 .

The embodiment of the present invention also provides a 3GPP network control network element 90, as shown in FIG. 10, including:

Receiving unit 91: configured to receive a request sent by a 3GPP network access node for the UE to access a non-3GPP network gateway;

Control unit 92: for controlling and establishing a bearer for the UE to access a non-3GPP network gateway via a 3GPP network.

Optionally, as shown in FIG. 11 , the 3GPP network control network element may further include: a first sending unit 93, where the first sending unit 93 is configured to send at least one non-3GPP network gateway corresponding to the address information Send a request for the UE to access the non-3GPP network gateway.

The control unit 92 includes: an acquisition module 921, a first transmission control module 922, and a first bearer management module 923; wherein,

Obtaining module 921: used to obtain the address information of the non-3GPP network gateway;

The first sending control module 922 is configured to control the first sending unit 93 to send a request for the UE to access the non-3GPP network gateway to at least one non-3GPP network gateway corresponding to the address information via the 3GPP network service gateway;

The receiving unit 91 is further configured to receive a reply to the request from the non-3GPP network gateway;

The first bearer management module 923 is configured to, in the case where the reply received by the receiving unit 91 indicates that the bearer between the 3GPP network serving gateway and the non-3GPP network gateway is successfully established, establish that the UE accesses the Bearer of 3GPP network service gateway.

The obtaining module 921 is specifically used for:

Send a query request to the DNS server; the query request includes: the location information of the 3GPP network access node and the access point name APN for pointing to the non-3GPP network gateway, and receives the non-3GPP network gateway fed back by the DNS server or, from the request received by the receiving unit 91 for the UE to access the non-3GPP network gateway, read the address information of the non-3GPP network gateway; or, obtain the preconfigured non-3GPP network gateway address information Address information.

The first sending control module 922 is specifically configured to:

When it is necessary to switch the non-3GPP network access to the 3GPP network access, control the first sending unit 93 to send the UE to the non-3GPP network gateway corresponding to each of the address information obtained by the obtaining module A request for accessing a non-3GPP network gateway; otherwise, control the first sending unit 93 to send the UE to access a non-3GPP network to a corresponding non-3GPP network gateway in the address information obtained by the obtaining module Gateway request.

Or, optionally, as shown in FIG. 12 , the 3GPP network control network element may further include: a second sending unit 94, configured to send a request for the UE to access the non-3GPP network gateway to the 3GPP network serving gateway;

The control unit 92 includes: a second transmission control module 924 and a second bearer management module 925;

The second sending control module 924 is configured to control the second sending unit 94 to send a request for the UE to access the non-3GPP network gateway to the 3GPP network service gateway; so that the 3GPP network service gateway obtains its own pre-configured non- address information of the 3GPP network gateway, and send a request for the UE to access the non-3GPP network gateway to at least one non-3GPP network gateway corresponding to the address information;

The receiving unit 91 is further configured to receive a reply to the request from the non-3GPP network gateway;

The second bearer management module 925 is configured to establish that the UE accesses the bearer if the reply received by the receiving unit 91 indicates that the bearer between the 3GPP network serving gateway and the non-3GPP network gateway is successfully established. Bearer of 3GPP network service gateway.

The control unit 92 is further configured to delete the bearer for the UE to access the non-3GPP network gateway via the 3GPP network when the bearer for the UE to access the non-3GPP network gateway via the 3GPP network is not required

The embodiment of the present invention also provides a non-3GPP network gateway 120, as shown in FIG. 13, including:

Receiving unit 121: configured to receive a request sent by the 3GPP network serving gateway for the UE to access the non-3GPP network gateway;

Sending unit 122: used for forwarding the reply to the request by the 3GPP network service gateway to the 3GPP network control network element; so that the 3GPP network control network element indicates the 3GPP network service gateway and the non-3GPP network gateway in the reply If the establishment of the bearer between them is successful, the establishment of the bearer for the UE to access the 3GPP network serving gateway is controlled.

Optionally, as shown in FIG. 13 , the non-3GPP network gateway may further include:

Saving unit 123: used to save the identifier of the currently accessed UE and the identifier of the current access mode of the UE.

Further optionally, as shown in FIG. 14 , the non-3GPP network gateway may further include:

The first establishing bearer unit 124: used to establish a bearer between the 3GPP network service gateway and the non-3GPP network gateway;

Allocating unit 125: for allocating address information for accessing the specific service to the UE;

The reply to the request indicates that the bearer establishment between the 3GPP network serving gateway and the non-3GPP network gateway is successful, and includes address information allocated to the UE for accessing the specific service.

Further optionally, as shown in FIG. 15 , the non-3GPP network gateway may further include:

The first query unit 126: used to query whether there is a UE identity consistent with the request in the current record;

A first updating unit 127: configured to update the identifier of the current access mode of the UE in the saving unit when the first query unit 126 finds that there is a consistent UE identifier;

The second establishing bearer unit 128: used to establish a bearer between the 3GPP network service gateway and the non-3GPP network gateway;

The reply to the request indicates that the bearer is established successfully, and includes the address information previously allocated to the UE for accessing the specific service; wherein, the non-3GPP network gateway does not reallocate the UE for accessing the specific service. Address information for the specific service.

Or, further optionally, as shown in FIG. 16 , the non-3GPP network gateway may further include: a second query unit 129 and a second update unit 130;

The receiving unit 121 is further configured to receive an authentication message sent by the UE through the access point of the non-3GPP network, where the authentication message includes: the identifier of the UE and the handover identifier;

The second query unit 129 is configured to query whether there is a UE identity consistent with the authentication message in the current record of the non-3GPP network gateway after the authentication is successful;

Second updating unit 130: configured to update the identifier of the current access mode of the UE in the saving unit when the second query unit 129 finds that there is a consistent UE identifier;

The sending unit 121 is further configured to send an authentication feedback message to the UE, where the authentication feedback message includes address information previously allocated to the UE for accessing the specific service; wherein the non-3GPP network gateway does not reallocating address information for accessing the specific service for the UE;

The sending unit 121 is further configured to send a bearer deletion request to the 3GPP serving gateway, so that the UE accesses the bearer deletion of the non-3GPP network gateway via the 3GPP network.

An apparatus for implementing 3GPP network traffic offloading provided by the embodiment of the present invention adopts a non-3GPP network gateway as a device for offloading traffic, that is, the traffic of the 3GPP network is offloaded through the non-3GPP network, thereby reducing the burden on the 3GPP core network, and This solution has no impact on the current network architecture and is beneficial for operators to implement. In addition, in the present invention, a non-3GPP network gateway is used as a device for unloading 3GPP network traffic, which lays a foundation for realizing seamless switching between the 3GPP network access mode and the non-3GPP network access mode, so as to ensure the current access of users. connections to specific services are not interrupted.

This embodiment of the present invention also provides a user equipment 160, as shown in FIG. 17, including:

A transmitter 161, a memory 162, and a processor 163 connected to the memory.

Wherein, a set of program codes are stored in the memory, and the processor is configured to call the program codes stored in the memory, and execute a method for implementing 3GPP network traffic offloading corresponding to any user equipment in the above embodiment, except for sending For other operations, the transmitter is used to send the processing result of the processor.

The embodiment of the present invention also provides a 3GPP network control network element 170, as shown in FIG. 18, including:

A receiver 171, a memory 172, and a processor 173 connected to the memory.

The receiver is configured to receive information sent by other devices to the 3GPP network control network element, a set of program codes are stored in the memory, and the processor is configured to call the program codes stored in the memory to execute the above Operations other than receiving in a method for implementing 3GPP network traffic offloading corresponding to any 3GPP network control network element in the embodiment.

Optionally, the 3GPP network control network element may further include a transmitter 174 for sending the result processed by the processor, and the processor is used for calling the program code stored in the memory to execute any 3GPP in the above embodiment. The network controls operations other than receiving and sending in a method for implementing 3GPP network traffic offloading corresponding to a network element.

The embodiment of the present invention also provides a non-3GPP network gateway 180, as shown in FIG. 19, including:

A receiver 181, a memory 182, and a processor 183 connected to the memory.

The receiver 181 is used for receiving information sent by other devices to the non-3GPP network gateway, a set of program codes are stored in the memory, and the processor 183 is used for calling the program codes stored in the memory 182 , and perform operations other than receiving in a method for implementing 3GPP network traffic offloading corresponding to any non-3GPP network gateway in the foregoing embodiment.

Optionally, the non-3GPP network gateway may further include a transmitter 184 for transmitting the processing result of the processor; a set of program codes are stored in the memory, and the processor 183 is used for calling the The program code stored in the memory 182 executes operations other than receiving and sending in a method for implementing 3GPP network traffic offloading corresponding to any non-3GPP network gateway in the foregoing embodiment.

In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may be physically included individually, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware, or may be implemented in the form of hardware plus software functional units.

The above-mentioned integrated units implemented in the form of software functional units can be stored in a computer-readable storage medium. The above-mentioned software functional unit is stored in a storage medium, and includes several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute some steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, Read-Only Memory (ROM for short), Random Access Memory (RAM for short), magnetic disk or CD, etc. that can store program codes medium.

Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present invention, but not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand: it can still be Modifications are made to the technical solutions described in the foregoing embodiments, or some technical features thereof are equivalently replaced; and these modifications or replacements do not make the essence of the corresponding technical solutions depart from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims (34)

1. A method for implementing 3GPP network traffic offload, comprising:

user Equipment (UE) determines that a bearer for accessing a specific service needs to be established, wherein the specific service is accessible through a 3GPP network and a non-3GPP network;

the UE sends a request for accessing the non-3GPP network gateway to a 3GPP network access node serving the UE; completing the establishment of a bearer for the UE to access the non-3GPP network gateway through a 3GPP network, wherein the bearer for the UE to access the non-3GPP network gateway through the 3GPP network comprises the bearer between a 3GPP network service gateway and the non-3GPP network gateway and the bearer for the UE to access the 3GPP network service gateway;

and the UE accesses the specific service through the established bearer.

2. The method of claim 1,

the request for the UE to access the non-3GPP network gateway comprises the following steps: UE identification and access point name APN used for pointing to non-3GPP network gateway;

or, the request for the UE to access the non-3GPP network gateway includes: a UE identity, an APN for pointing to a non-3GPP network gateway, and a handover identity.

3. The method of claim 1 or 2, further comprising:

and the UE acquires and stores the address information of the non-3GPP network gateway accessed by the UE.

4. A method for implementing 3GPP network traffic offload, comprising:

a 3GPP network control network element receives a request of user equipment UE accessing a non-3GPP network gateway sent by a 3GPP network access node;

controlling to establish a bearer for the UE to access a non-3GPP network gateway through a 3GPP network, wherein the bearer for the UE to access the non-3GPP network gateway through the 3GPP network comprises a bearer between a 3GPP network service gateway and the non-3GPP network gateway and a bearer for the UE to access the 3GPP network service gateway.

5. The method of claim 4,

the request for the UE to access the non-3GPP network gateway comprises the following steps: UE identification and access point name APN used for pointing to non-3GPP network gateway;

or, the request for the UE to access the non-3GPP network gateway includes: a UE identity, an APN for pointing to a non-3GPP network gateway, and a handover identity.

6. The method of claim 5,

the request for the UE to access the non-3GPP network gateway further comprises: location information of a 3GPP network access node;

or, the request for the UE to access the non-3GPP network gateway further includes: address information of non-3GPP network gateways.

7. The method of any of claims 4-6, wherein the controlling establishing the bearer for the UE to access a non-3GPP network gateway via a 3GPP network comprises:

acquiring address information of a non-3GPP network gateway;

sending a request for UE to access the non-3GPP network gateway to the non-3GPP network gateway corresponding to at least one address information through a 3GPP network service gateway;

receiving a reply of the non-3GPP network gateway to the request;

and if the reply indicates that the bearer establishment between the 3GPP network service gateway and the non-3GPP network gateway is successful, establishing the bearer of the UE accessed to the 3GPP network service gateway.

8. The method of claim 7, wherein the obtaining address information of the non-3GPP network gateway comprises:

sending a query request to a DNS server; the query request includes: the location information of the 3GPP network access node and the access point name APN used for pointing to the non-3GPP network gateway, and the address information of the non-3GPP network gateway fed back by the DNS server is received; or,

reading address information of a non-3GPP network gateway from the received request of the UE accessing the non-3GPP network gateway; or,

and acquiring the address information of the pre-configured non-3GPP network gateway.

9. The method of claim 8, wherein the sending the request for the UE to access the non-3GPP network gateway corresponding to the at least one address information comprises:

under the condition that non-3GPP network access needs to be switched to 3GPP network access, a request of UE for accessing the non-3GPP network gateway is sent to the non-3GPP network gateway corresponding to each acquired address information; otherwise, sending a request for accessing the non-3GPP network gateway by the UE to the non-3GPP network gateway corresponding to one of the obtained address information.

10. The method of any of claims 4-6, wherein the controlling establishing the bearer for the UE to access a non-3GPP network gateway via a 3GPP network comprises:

sending a request for UE to access a non-3GPP network gateway to a 3GPP network service gateway; the 3GPP network service gateway acquires address information of a non-3GPP network gateway pre-configured by the 3GPP network service gateway, and sends a request of UE accessing the non-3GPP network gateway to at least one non-3GPP network gateway corresponding to the address information;

receiving a reply of the non-3GPP network gateway to the request;

and if the reply indicates that the bearer establishment between the 3GPP network service gateway and the non-3GPP network gateway is successful, establishing the bearer of the UE accessed to the 3GPP network service gateway.

11. The method of claim 4, wherein in a case that the UE does not need to access the bearer of the non-3GPP network gateway via a 3GPP network, the method further comprises:

and deleting the bearer of the UE accessing the non-3GPP network gateway through the 3GPP network.

12. A method for implementing 3GPP network traffic offload, comprising:

a non-3GPP network gateway receives a request sent by a 3GPP network service gateway for UE to access the non-3GPP network gateway;

forwarding, by the 3GPP network service gateway, a reply to the request to a 3GPP network control element; so that the 3GPP network control network element controls to establish the bearer of the UE accessing the 3GPP network service gateway under the condition that the reply indicates that the bearer establishment between the 3GPP network service gateway and the non-3GPP network gateway is successful.

13. The method of claim 12,

the request for the UE to access the non-3GPP network gateway comprises the following steps: UE identification and APN used for pointing to non-3GPP network gateway;

or, the request for the UE to access the non-3GPP network gateway includes: a UE identity, an APN for pointing to a non-3GPP network gateway, and a handover identity.

14. The method of claim 13, wherein if the request for the UE to access the non-3GPP network gateway does not include a handover id, the method further comprises:

establishing a load bearing between a 3GPP network service gateway and a non-3GPP network gateway;

allocating address information for accessing a specific service to the UE;

the reply to the request indicates that bearer establishment between the 3GPP network serving gateway and the non-3GPP network gateway is successful, and includes: address information allocated to the UE for accessing the specific service.

15. The method of claim 12, further comprising:

and storing the identifier of the UE currently accessed to the non-3GPP network gateway and the identifier of the current access mode of the UE.

16. The method of claim 15, wherein if the request for the UE to access the non-3GPP network gateway includes a handover identifier, the method further comprises:

inquiring whether a UE identifier consistent with the request exists in the current record of the non-3GPP network gateway or not;

if the access mode exists, updating the identifier of the current access mode of the UE, establishing a bearer between a 3GPP network service gateway and a non-3GPP network gateway, and not reallocating address information for accessing a specific service for the UE; the reply to the request indicates that the bearer establishment was successful and includes address information previously assigned to the UE for accessing the particular service.

17. The method of claim 15, further comprising:

receiving an authentication message sent by a UE through an access point of a non-3GPP network, wherein the authentication message comprises: an identity and a handover identity of the UE;

after the authentication is successful, inquiring whether a UE identifier consistent with the authentication message exists in the current record of the non-3GPP network gateway;

if the access mode exists, updating the identifier of the current access mode of the UE, and not reallocating address information for accessing the specific service for the UE;

transmitting an authentication feedback message to the UE, the authentication feedback message including address information previously allocated to the UE for accessing the specific service;

and sending a request for deleting the bearer to a 3GPP service gateway so that the UE accesses the bearer of the non-3GPP network gateway through a 3GPP network to delete the bearer.

18. A User Equipment (UE), comprising:

a determination unit: for determining that a bearer needs to be established for accessing a particular service, the particular service being a service accessible via both a 3GPP network and a non-3GPP network;

a transmission unit: a request for the UE to access a non-3GPP network gateway is sent to a 3GPP network access node serving the UE; completing the establishment of a bearer for the UE to access the non-3GPP network gateway through a 3GPP network, wherein the bearer for the UE to access the non-3GPP network gateway through the 3GPP network comprises the bearer between a 3GPP network service gateway and the non-3GPP network gateway and the bearer for the UE to access the 3GPP network service gateway;

an access unit: for the UE to access the specific service through the established bearer.

19. The UE of claim 18,

the request for the UE to access the non-3GPP network gateway comprises the following steps: UE identification and access point name APN used for pointing to non-3GPP network gateway;

or the request for the UE to access the non-3GPP network gateway comprises: a UE identity, an APN for pointing to a non-3GPP network gateway, and a handover identity.

20. The UE of claim 18 or 19, further comprising:

a storage unit: for learning and storing address information of non-3GPP network gateways to which it has access.

21. A 3GPP network control element, comprising:

a receiving unit: receiving a request sent by a 3GPP network access node for a UE to access a non-3GPP network gateway;

a control unit: and the bearer is used for controlling the establishment of the bearer for accessing the UE to the non-3GPP network gateway through the 3GPP network, wherein the bearer for accessing the UE to the non-3GPP network gateway through the 3GPP network comprises the bearer between the 3GPP network service gateway and the non-3GPP network gateway and the bearer for accessing the 3GPP network service gateway by the UE.

22. The 3GPP network control network element of claim 21,

the request for the UE to access the non-3GPP network gateway comprises the following steps: UE identification and access point name APN used for pointing to non-3GPP network gateway;

or, the request for the UE to access the non-3GPP network gateway includes: a UE identity, an APN for pointing to a non-3GPP network gateway, and a handover identity.

23. The 3GPP network control network element of claim 22,

the request for the UE to access the non-3GPP network gateway further comprises: location information of a 3GPP network access node;

or, the request for the UE to access the non-3GPP network gateway further includes: address information of non-3GPP network gateways.

24. A 3GPP network control element according to any of claims 21-23, wherein the 3GPP network control element further comprises: a first sending unit, configured to send a request for accessing a non-3GPP network gateway by a UE to the non-3GPP network gateway corresponding to the address information of at least one of the non-3GPP network gateways;

the control unit includes: the system comprises an acquisition module, a first sending control module and a first bearing management module; wherein,

an acquisition module: the method comprises the steps of obtaining address information of a non-3GPP network gateway;

a first transmission control module: the first sending unit is used for controlling the first sending unit to send a request of UE accessing the non-3GPP network gateway to the non-3GPP network gateway corresponding to at least one address information through a 3GPP network service gateway;

the receiving unit is further configured to receive a reply to the request from the non-3GPP network gateway;

the first bearing management module: and the UE is used for establishing the bearer for accessing the 3GPP network service gateway under the condition that the reply received by the receiving unit indicates that the bearer establishment between the 3GPP network service gateway and the non-3GPP network gateway is successful.

25. The 3GPP network control element of claim 24, wherein the obtaining module is specifically configured to:

sending a query request to a DNS server; the query request includes: the location information of the 3GPP network access node and the access point name APN used for pointing to the non-3GPP network gateway, and the address information of the non-3GPP network gateway fed back by the DNS server is received; or,

reading address information of a non-3GPP network gateway from a request of the UE accessing the non-3GPP network gateway received by a receiving unit; or,

and acquiring the address information of the pre-configured non-3GPP network gateway.

26. The 3GPP network control element of claim 25, wherein the first transmission control module is specifically configured to:

under the condition that non-3GPP network access needs to be switched to 3GPP network access, the first sending unit is controlled to send a request of UE for accessing the non-3GPP network gateway to the non-3GPP network gateway corresponding to each address information acquired by the acquisition module; otherwise, controlling the first sending unit to send a request for accessing the non-3GPP network gateway by the UE to the non-3GPP network gateway corresponding to one of the address information acquired by the acquisition module.

27. A 3GPP network control element according to any of claims 21-23, wherein the 3GPP network control element further comprises: a second sending unit, configured to send, to the 3GPP network serving gateway, a request for accessing the non-3GPP network gateway by the UE;

the control unit includes: a second sending control module and a second bearing management module;

the second transmission control module: the second sending unit is used for controlling the second sending unit to send a request of UE accessing the non-3GPP network gateway to the 3GPP network service gateway; the 3GPP network service gateway acquires address information of a non-3GPP network gateway pre-configured by the 3GPP network service gateway, and sends a request of UE accessing the non-3GPP network gateway to at least one non-3GPP network gateway corresponding to the address information;

the receiving unit: and is further configured to receive a reply to the request from the non-3GPP network gateway;

the second bearer management module: and configured to establish a bearer for the UE to access the 3GPP network service gateway if the reply received by the receiving unit indicates that the bearer establishment between the 3GPP network service gateway and the non-3GPP network gateway is successful.

28. The 3GPP network control element of claim 21, wherein the control unit is further configured to delete the bearer for the UE to access a non-3GPP network gateway via a 3GPP network if the bearer for the UE to access the non-3GPP network gateway via the 3GPP network is not required.

29. A non-3GPP network gateway, comprising:

a receiving unit: a request for receiving a UE access non-3GPP network gateway sent by a 3GPP network service gateway;

a transmission unit: for forwarding, by the 3GPP network serving gateway, a reply to the request to a 3GPP network control element; so that the 3GPP network control network element controls to establish the bearer of the UE accessing the 3GPP network service gateway under the condition that the reply indicates that the bearer establishment between the 3GPP network service gateway and the non-3GPP network gateway is successful.

30. The non-3GPP network gateway of claim 29, wherein,

the request for the UE to access the non-3GPP network gateway comprises the following steps: UE identity and APN for pointing to a non-3GPP network gateway,

alternatively, it comprises: a UE identity, an APN for pointing to a non-3GPP network gateway, and a handover identity.

31. The non-3GPP network gateway of claim 30, further comprising:

the first bearing unit is established: the gateway is used for establishing a load between a 3GPP network service gateway and a non-3GPP network gateway;

a distribution unit: address information for allocating the UE to access a specific service;

the reply to the request indicates that bearer establishment between the 3GPP network serving gateway and the non-3GPP network gateway is successful, and includes: address information allocated to the UE for accessing the specific service.

32. The non-3GPP network gateway of claim 29, further comprising:

a storage unit: and the method is used for storing the identifier of the currently accessed UE and the identifier of the current access mode of the UE.

33. The non-3GPP network gateway of claim 32, further comprising:

a first query unit: the UE is used for inquiring whether the UE identification consistent with the request exists in the current record or not;

a first update unit: the identifier is used for updating the identifier of the current access mode of the UE in the storage unit under the condition that the first query unit queries that the consistent UE identifier exists;

and a second bearing establishing unit: the gateway is used for establishing a load between a 3GPP network service gateway and a non-3GPP network gateway;

the reply to the request indicates a successful bearer establishment and includes address information previously assigned to the UE for accessing a specific service; wherein the non-3GPP network gateway does not reallocate address information for the UE for accessing the specific service.

34. The non-3GPP network gateway of claim 32, further comprising: a second query unit and a second update unit;

the receiving unit is further configured to: receiving an authentication message sent by a UE through an access point of a non-3GPP network, wherein the authentication message comprises: the identity of the UE and a handover identity;

the second query unit: the network gateway is used for inquiring whether the current record of the non-3GPP network gateway has the UE identification consistent with the authentication information after the authentication is successful;

a second updating unit: the second query unit is used for updating the identifier of the current access mode of the UE in the storage unit under the condition that the second query unit queries that the consistent UE identifier exists;

the sending unit is further configured to: transmitting an authentication feedback message to the UE, the authentication feedback message including address information previously allocated to the UE for accessing a specific service; wherein the non-3GPP network gateway does not reallocate address information for the UE for accessing the specific service;

the sending unit is further configured to: and sending a request for deleting the bearer to a 3GPP service gateway so that the UE accesses the bearer of the non-3GPP network gateway through a 3GPP network to delete the bearer.