WO2009046598A1

WO2009046598A1 - A method for establishing a dedicated bearer for a user terminal

Info

Publication number: WO2009046598A1
Application number: PCT/CN2007/003923
Authority: WO
Inventors: Xiaoyun Zhou; Zaifeng Zong; Min Fang
Original assignee: Zte Corporation
Priority date: 2007-10-12
Filing date: 2007-12-29
Publication date: 2009-04-16
Also published as: CN101141412B; CN101141412A

Abstract

A method for establishing a dedicated bearing for a user terminal is applied in a 3GPP evolved packet system and a non-3GPP IP access system connected to it. The 3GPP evolved packet system includes a policy and charging rule function module. The method includes: when a user device is switched between the 3GPP access and the non-3GPP IP access, when the policy and charging rule function module has determined the switch, it looks up the policy charging control rule corresponding to the established bearer of the user equipment, and reestablishes the dedicated bearer of the user equipment in a target system according to the policy charging control rules. It can be realized to establish the dedicated bearer when switching between the 3GPP access system and the non-3GPP access system.

Description

Method for establishing a dedicated bearer for a user terminal

The present invention relates to a method for establishing a dedicated bearer for a user terminal, and more particularly to a user terminal when switching between a 3GPP (3rd Generation Partnership Project) access network and a non-3GPP access network. A method for establishing a proprietary bearer for it. Background technique

3GPP Evolved Packet System (EPS), EPS system architecture diagram shown in Figure 1, by E-UTRAN (Evolved Universal Terrestrial Radio Access Network, Evolved Universal Terrestrial Radio Access Network), MME (Mobile Management) Unit, Mobility Management Entity), S-GW (Serving Gateway), P-GW (Packet Data Network GateWay, Data Network Gateway), HSS (Home Subscriber Server), 3GPP AAA Server (3GPP Authentication and Authorization) The accounting server), the PCRF (Policy and Charging Rules Function), and other supporting network element devices. Among them, it is responsible for control plane related work such as mobility management, non-access stratum signaling processing, and user mobility management context management; S-GW is an access gateway device connected to E-UTRAN, in E-UTRAN and P - The GW forwards data and is responsible for caching the paging wait data. The P-GW is a border gateway between the 3GPP Evolved Packet System and the PDN (Packet Data Network), which is responsible for accessing the user terminal to the PDN and forwarding data between the EPS and the PDN. The PCRF is a policy and charging rule function entity. It interfaces with the operator's IP service network through the Rx interface to obtain service information. It is connected to the gateway device in the network through the S7/S7a/S7b/S7c interface, and is responsible for initiating IP (Internet Protocol). , Internet Protocol) bears policy decisions, such as bearer establishment, deletion, service data/bearing QoS (Quality Of Service), etc., and performs charging control.

EPS supports interworking with non-3GPP networks, ie, access to non-3GPP IP access networks. As shown in FIG. 1, the interworking between the EPS and the non-3GPP network is implemented through an S2a/b/c interface, and the P-GW is an anchor point between the 3GPP and the non-3GPP network. The non-3GPP access network is divided into a trusted non-3GPP IP access network and an untrusted non-3GPP IP access network. Trusted non-3GPP IP access network can pass directly S2a and the P-GW interface; the untrusted non-3GPP IP access network needs to be connected to the P-GW through an EPDG (Evolved Packet Data Gateway), and the interface between the ePDG and the P-GW is S2b.

In the traditional 3GPP network, the policy and charging enforcement function (PCEF) exists only in the P-GW. The PCRF can complete all the QoS-related policies and accounting, as long as it is interfaced with the P-GW. Function control, the PCRF exchanges information with the P-GW through the S7 interface. However, after the 3GPP network provides interworking functions with non-3GPP, when the interface between the P-GW and the S-GW is based on PMIP (Proxy Mobile IP), due to the limitations of the PMIP interface, some functions of the PCEF, For example, the binding function of the bearer is migrated to the S-GW, and the S-GW and the PCRF exchange information through the S7c interface. When a non-3GPP system accesses the 3GPP system through the S2a/S2b interface, some PCEF functions also reside in the non-3GPP system. When the non-3GPP system is a trusted access system (trusted non-3GPP access), the PCRF exchanges control information and accounting information with the non-3GPP system through the S7a interface; when the non-3GPP system is an untrusted access system When the non-trusted non-3GPP access is used, the PCRF exchanges control information and accounting information with the non-3GPP system through the S7b interface.

In 3GPP systems, services are provided by bearers. The bearer has multiple attributes such as bearer type, rate, priority, and so on. In the EPS system, the first bearer established by a UE (user terminal) with a P-GW during the attach process is called a default bearer, and the bearer established for a specific service in the future is called Dedicated bearer (dedicated bearer). In the EPS system and the non-3GPP access network that support the dynamic policy charging control, the UEs that are not the 3GPP access 3GPP system establish the UE and the non-3GPP access gateway dedicated bearers according to the policy delivered by the PCRF.

FIG. 2 illustrates a process of establishing a dedicated bearer after a UE accesses a 3GPP system (EPS) through a non-3GPP access network by using a trusted non-3GPP access network as an example, and the UE is omitted in the figure. As shown in Figure 2, the process of establishing a proprietary bearer includes the following steps:

201: The PCRF sends a policy charging control rule providing message to the P-GW.

202: After receiving the foregoing policy charging control rule providing message, the P-GW sends a policy charging control rule confirmation message to the PCRF.

203: The PCRF sends a QoS policy providing message to the trusted non-3GPP access system. The above trusted non-3GPP access system may include multiple network element devices, and includes PCEF functions related to bearers.

204: After receiving the foregoing QoS policy providing message, the trusted non-3GPP access system performs an access network specific QoS policy execution mechanism according to the message;

205: The trusted non-3GPP access system sends a QoS policy acknowledgement message to the PCRF to complete the establishment of the dedicated bearer.

After accessing the EPS system through the 3GPP access network, the UE can access the EPS system through the non-3GPP access network due to roaming, etc., that is, the 3GPP access network switches to the non-3GPP access network. Similarly, after accessing the EPS system through the non-3GPP access network, the UE can also be switched to the 3GPP access by the non-3GPP access network. In EPS systems and non-3GPP access networks that support dynamic policy charging control, handover between 3GPP and non-3GPP networks will involve the establishment of default bearers and proprietary bearers.

FIG. 3 illustrates a handover procedure between a 3GPP access and a non-3GPP access by taking a handover procedure of a UE from a 3GPP access to a trusted non-3GPP access as an example. As shown in Figure 3, the switching process includes the following steps:

301: The UE accesses the EPS through the 3GPP access system to establish a bearer; and the PM- or GTP tunnel is established between the S-GW and the P-GW.

302: The UE finds that the non-3GPP access system is trusted and initiates the handover, that is, accesses the EPS by the trusted non-3GPP access system;

303: The UE initiates access authentication to the HSS/AAA through the trusted non-3GPP IP access system.

304: The UE initiates an attach request to the trusted non-3GPP IP access system.

305: The trusted non-3GPP IP access system and the PCRF perform a gateway control session establishment process, and the PCRF sends a default bearer QoS rule to the trusted non-3GPP IP access system.

306: The trusted non-3GPP IP access system sends a proxy binding update message to the P-GW.

307: The P-GW sends a session modification request message to the PCRF, and the PCRF returns a session modification acknowledgement message to the P-GW, and the PCRF sends a default bearer PCC (Policy Charge Control) rule to the P-GW. 308: The P-GW interacts with the HSS/AAA to authorize the UE.

309: The P-GW sends a proxy binding acknowledgement message to the trusted non-3GPP IP access system.

310: The trusted non-3GPP IP access system sends an attach complete message to the UE;

After the step 310 is completed, the PMIP tunnel is established between the trusted non-3GPP IP access system and the P-GW, and the default bearer of the UE is also established.

The above trusted non-3GPP access system may include multiple network element devices, and includes PCEF functions related to the bearers.

It can be seen from the above switching process that when the UE is handed over from the 3GPP access system to the non-3GPP access system, the PCEF function module in the trusted non-3GPP access system and the P-GW establishes a default for the UE according to the policy delivered by the PCRF. Host (steps 305 and 307).

How to establish a proprietary bearer when switching between a 3GPP access system and a non-3GPP access system is an unsolved problem. Summary of the invention

The technical problem to be solved by the present invention is to overcome the deficiencies of the prior art, and to provide a default bearer for the UE when the UE switches between the 3GPP access system and the non-3GPP access system. There are methods of hosting.

In order to solve the above problem, the present invention provides a method for establishing a dedicated bearer for a user terminal, which is applied to a 3GPP evolved packet system and a non-3GPP IP access system connected thereto, where the 3GPP evolved packet system includes a policy and The charging rule function module, the method includes: when the user equipment switches between the 3GPP access and the non-3GPP IP access, and the policy and charging rule function module determines that the handover is performed, the searching and the user equipment are established. Carrying related policy charging control rules, and re-establishing the dedicated bearer of the user equipment in the destination system according to the policy charging control rule.

Further, the policy and charging rule function module determines that the handover includes: the gateway device in the destination system notifies the corresponding policy and charging rule function module of the cross-system handover event indication.

Further, the policy and charging rule function module determines that the switching includes: The gateway device in the system requests the policy charging control rule from the policy and charging rule function module. Further, the re-establishing the dedicated bearer of the user equipment in the destination system according to the policy charging control rule includes: the policy and charging rule function module sending the policy charging control rule to the gateway device of the destination system; The gateway device in the destination system acquires the policy charging control rule for establishing a dedicated bearer.

Further, the gateway device is the user terminal corresponding to a data network gateway or a service gateway or a trusted non-3GPP access gateway or an evolved data gateway.

The method includes: the user terminal initiates an access request to a destination access system.

Further, the gateway device is the data network gateway, and the data network gateway includes the handover event indication in the session modification request message and sent to the policy and charging rule function module.

Further, the gateway device is the serving gateway or a trusted non-3GPP access gateway or an evolved data gateway, and the serving gateway or the trusted non-3GPP access gateway or the evolved data gateway includes the handover event indication The policy and charging rule function module is sent in a gateway control session establishment request message.

Further, the message that the gateway device in the destination system requests the policy charging control rule from the policy and charging rule function module includes: a session modification request, a gateway control session establishment request message, or a policy and charging control rule request message.

Further, the message that the gateway device in the destination system requests the policy charging control rule from the policy and charging rule function module includes the type information of the access network where the gateway device is located.

Further, the session modification request message, the gateway control session establishment request message, or the policy and charging control rule request message includes identification information of the user terminal; and the policy and charging rule function module receives the session modification. After the request message or the gateway controls the session establishment request message or the policy and charging control rule request message, the policy charging control rule of all bearers corresponding to the user terminal is searched according to the identifier information.

Further, the identifier information of the user terminal is an IP address of the user terminal.

Further, the non-3GPP IP access system is a trusted non-3GPP IP access system or not Trusted non-3GPP IP access systems.

Further, the non-3GPP IP access system includes a bearer-related policy and charging execution function.

When the UE determines that the handover is performed, the UE finds that the user equipment has been established when the UE switches from the 3GPP access system to the non-3GPP IP access system (or from the non-3GPP access system to the 3GPP access system). Carrying the relevant policy charging control rule, and delivering the corresponding default bearer and the dedicated bearer rule to the destination system gateway device, and the gateway device establishes a default bearer and a dedicated bearer according to the rule, which makes up the prior art. blank.

BRIEF abstract

Figure 1 is a system architecture diagram of EPS;

2 is a process for establishing a dedicated bearer after a UE accesses a 3GPP system (EPS) through a non-3GPP access network;

FIG. 3 is a handover procedure of a UE accessing from 3GPP to trusted non-3GPP access;

4 is a method of the present invention for establishing a dedicated bearer for a UE when the 3GPP access is switched to the trusted non-3GPP access;

5 is a method for establishing a dedicated bearer for a UE when the present invention switches from 3GPP access to access by untrusted non-3GPP;

6 is a method of the present invention for establishing a dedicated bearer for a UE when it is switched from a trusted or untrusted 3GPP access to a 3GPP access.

Preferred embodiment of the invention

The invention will now be described in detail in conjunction with the drawings and embodiments.

Embodiment 1

This embodiment describes a method for establishing a dedicated bearer for a user terminal when the UE is switched from 3GPP access to trusted non-3GPP access. In the case of 3GPP access, the S-GW and the P-GW adopt the PMIPv6 or GTP protocol, and when the trusted non-3GPP accesses, the non-3GPP access can be trusted. The PMIPv6 protocol is adopted between the system and the P-GW. As shown in FIG. 4, the method for establishing a handover and a dedicated bearer from a 3GPP access to a trusted non-3GPP IP access network by the UE includes the following steps:

401 - 406: the same as steps 301 ~ 306 respectively;

407: The P-GW sends a session modification request message to the PCRF.

The session modification request message includes the identifier information of the UE, such as the IP address of the UE. The message further includes a handover event indication, which is used to identify that the UE is performing handover of the 3GPP to the trusted non-3GPP IP access network.

408: The PCRF sends a session modification acknowledgement message to the P-GW.

409: The P-GW interacts with the HSS/AAA to authorize the UE.

410: The P-GW sends a proxy binding acknowledgement message to the trusted non-3GPP IP access system.

411: The trusted non-3GPP IP access system sends an attach complete message to the UE, where the default bearer setup of the UE is completed.

412: After receiving the foregoing session modification request message that includes the handover event indication, the PCRF searches for the policy charging control rule of the dedicated bearer established by the UE according to the IP address of the UE; if the corresponding policy charging control rule is found, the description is If the UE already has a dedicated bearer (3GPP access dedicated bearer) before the handover, the next step is performed, otherwise the method ends.

413 - 417: the same as steps 201 ~ 205 respectively;

In step 413-417, the policy charging control rule providing message and the QoS policy providing message sent by the PCRF provide policy charging control rules and QoS policies according to the policy of the original 3GPP access dedicated bearer of the UE. Control rules and QoS policy generation.

So far, the establishment of the default bearer and the dedicated bearer (non-3GPP access proprietary bearer) of the UE is completed.

It should be noted that the above steps 408 - 411 and steps 412 - 417 can be performed in parallel, that is, after the PCRF receives the session modification request message including the handover event indication sent by the P-GW, the default bearer and the dedicated start can be started simultaneously. There is a build of the bearer.

The above trusted non-3GPP access system may include multiple network element devices, and includes PCEF functions related to bearers. If, in step 405, the trusted non-3GPP IP access gateway sends the gateway control session establishment request message to the PCRF, the access network type information of the access gateway is carried, and the PCRF finds that the type of the access network is different from the saved access network type. The UE has a handover, and the PCRF sends a policy charging control rule corresponding to the bearer established by the UE in the 3GPP system to the trusted non-3GPP IP access gateway for establishing a default bearer and a dedicated in the trusted non-3GPP IP access system. There are bearers.

Embodiment 2

This embodiment describes a method for establishing a dedicated bearer for a user terminal when the UE is switched from 3GPP access to untrusted non-3GPP access. In the case of 3GPP access, the PM-IPv6 or GTP protocol is adopted between the S-GW and the P-GW. When the non-3GPP access is trusted, the PMIPv6 protocol is adopted between the ePDG and the P-GW. As shown in FIG. 5, the method for establishing a handover and a dedicated bearer of a UE from a 3GPP access to an untrusted non-3GPP IP access network includes the following steps:

501: The UE accesses the EPS through the 3GPP access system, and respectively establishes a default bearer and a dedicated bearer; and a PMIP or a GTP tunnel is established between the S-GW and the P-GW;

502: The UE finds that the non-3GPP access system is untrusted and initiates the handover, that is, the EPS is accessed by the untrusted non-3GPP access system.

503: The UE initiates an IKEv2 tunnel establishment process. The UE is authenticated and the APN (Access Point Name) that it wants to access is authorized. The address of the P-GW selected by the user terminal when accessed by the 3GPP is also returned to the ePDG in this step;

504: The ePDG sends a proxy binding update message to the P-GW.

505: The P-GW sends an IP-CAN session modification message requesting execution policy to the PCRF, where the message carries the identifier of the UE (such as an IP address) and a handover event indication.

506: After receiving the foregoing session modification request message that includes the indication of the handover event, the PCRF searches for the policy of the default bearer and the dedicated bearer established by the 3GPP according to the identifier of the UE (such as the IP address). . If so, it maps to the corresponding policy charging control rules accessed by non-3GPP and returns them to the P-GW through the IP-CAN session modification message.

The P-GW establishes a corresponding default bearer and a dedicated bearer according to the policy charging control rule;

507: The P-GW sends a proxy binding update confirmation message to the ePDG.

508: The ePDG and the UE continue to perform IKEv2 exchange and complete IP address configuration. 509: An IPSec tunnel is established between the UE and the ePDG, and a PMIPv6 tunnel is established between the ePDG and the P-GW.

Embodiment 3

This embodiment describes a method for establishing a dedicated bearer for a user terminal when the UE is switched to a 3GPP access by a trusted or untrusted non-3GPP access. In the case of 3GPP access, the S-GW and the P-GW adopt the PMIPv6 or GTP protocol, and when the trusted or untrusted non-3GPP access is used, the trusted non-3GPP access gateway or the ePDG and the P-GW are adopted. PMIPv6 protocol. As shown in FIG. 6, the method for establishing handover of a UE from a non-3GPP access to a 3GPP IP access network and establishing a dedicated bearer includes the following steps:

601: The UE accesses the EPS through a trusted or untrusted non-3GPP access system, and establishes a default bearer and a dedicated bearer respectively. The PMIPv6 protocol is adopted between the trusted non-3GPP access gateway or the ePDG and the P-GW;

602: The UE finds that the E-UTRAN accesses and decides to initiate the handover.

603: The UE sends an attach request to the MME.

604: The UE interacts with the HSS to authenticate the UE.

605: After the authentication is successful, the MME performs a location update process and acquires user data from the HSS. The address of the P-GW selected by the user terminal when accessed by the non-3GPP is also returned to the MME in this step;

606: The MME selects an S-GW, and sends a default bearer request to the MME, where the message carries the ID of the UE (such as an IP address);

607: The S-GW sends a gateway control session establishment request message to the PCRF, where the message carries the ID of the UE (such as an IP address) and the type of the access network (the value is 3GPP);

608: After receiving the foregoing gateway control session establishment message, the PCRF finds that the UE has changed the type of the access network. Therefore, according to the ID of the UE, the policy charging control rule of the default bearer and the dedicated bearer that the UE has established when accessed by the non-3GPP is searched. If yes, the corresponding policy charging control rules (referred to herein as QoS rules) when accessed by 3GPP are mapped, and they are returned to the S-GW through the gateway control session establishment confirmation message. The S-GW establishes a corresponding default bearer and a dedicated bearer according to the QoS rule; 609: The S-GW returns a default bearer response message to the MME.

610: Establish a wireless and access bearer;

611: The S-GW sends a proxy binding update to the P-GW.

612: The P-GW sends a policy and charging rule request message to the PCRF, where the message carries the ID of the UE (such as an IP address).

613: After receiving the foregoing policy and charging rule request message, the PCRF searches for the policy charging control rule of the default bearer and the dedicated bearer that the UE has established when accessed by the non-3GPP according to the ID of the UE. They are mapped into corresponding policy charging control rules when accessed by 3GPP, and they are returned to the P-GW through the policy and charging rule request acknowledgement message. The P-GW establishes a corresponding default bearer and a dedicated bearer according to the foregoing rules;

614: The P-GW returns a proxy binding acknowledgement message to the S-GW.

615: The UE can now send and receive data via E-URTAN.

It is a matter of course that the invention may be embodied in various other forms without departing from the spirit and scope of the invention.

Claims

Claim

A method for establishing a dedicated bearer for a user terminal, which is applied to a 3GPP evolved packet system and a non-3GPP IP access system connected thereto, where the 3GPP evolved packet system includes a policy and charging rule function module. The method includes: when the user equipment switches between the 3GPP access and the non-3GPP IP access, if the policy and charging rule function module determines the handover, the search and the user equipment are established. Carrying the relevant policy charging control rule, and re-establishing the dedicated bearer of the user equipment in the destination system according to the policy charging control rule.

2. The method for establishing a dedicated bearer for a user terminal according to claim 1, wherein the policy and charging rule function module determines that the handover comprises:: the gateway device in the target system switches across systems. The event indication informs the corresponding policy and charging rule function module.

The method for establishing a dedicated bearer for a user terminal according to claim 1, wherein the policy and charging rule function module determines that the handover includes: a gateway device in a destination system to a policy and a meter The fee rule function module requests a policy charging control rule.

The method for establishing a dedicated bearer for a user terminal according to any one of claims 1 to 3, wherein the dedicated bearer of the user equipment is re-established in the destination system according to the policy charging control rule, including The policy and charging rule function module sends the policy charging control rule to the gateway device of the destination system; the gateway device in the destination system acquires the policy charging control rule for establishing a dedicated bearer.

The method for establishing a dedicated bearer for a user terminal according to claim 4, wherein the gateway device is a data network gateway or a service gateway or a trusted non-trust device of the user terminal.

3GPP access gateway or evolved data gateway.

6. The method for establishing a dedicated bearer for a user terminal according to claim 1, wherein the terminal initiates an access request to the destination access system.

The method for establishing a dedicated bearer for a user terminal according to claim 5, wherein the gateway device is the data network gateway, and the data network gateway indicates the handover event The function is included in the session modification request message and sent to the policy and charging rule function module.

The method for establishing a dedicated bearer for a user terminal according to claim 5, wherein the gateway device is the serving gateway or a trusted non-3GPP access gateway or an evolved data gateway, and the service gateway Or the trusted non-3GPP access gateway or the evolved data gateway sends the handover event indication to the policy and charging rule function module in the gateway control session establishment request message.

The method for establishing a dedicated bearer for a user terminal according to claim 3, wherein the message that the gateway device in the destination system requests the policy charging control rule from the policy and charging rule function module includes: a session modification request The gateway controls the session establishment request message or the policy and charging control rule request message.

The method for establishing a dedicated bearer for a user terminal according to claim 3 or 9, wherein the gateway device in the destination system requests the policy charging control rule from the policy and charging rule function module. The type information of the access network where the gateway device is located.

The method for establishing a dedicated bearer for a user terminal according to any one of claims 7, 8 or 9, wherein the session modification request message, the gateway control session establishment request message or the policy and charging control rule The request message includes the identification information of the user terminal, and the policy and charging rule function module receives the session modification request message or the gateway control session establishment request message or the policy and charging control rule request message, according to the The identification information finds a policy charging control rule of all bearers corresponding to the user terminal.

The method for establishing a dedicated bearer for a user terminal according to claim 11, wherein the identification information of the user terminal is an IP address of the user terminal.

13. The method for establishing a dedicated bearer for a user terminal according to claim 1, wherein the non-3GPP IP access system is a trusted non-3GPP IP access system or an untrusted non-3GPP IP access system.

The method for establishing a dedicated bearer for a user terminal according to claim 13, wherein the non-3GPP IP access system includes a bearer-related policy and a charging execution function.