WO2009062392A1

WO2009062392A1 - Method of system handover, communication system and policy charging rule function entity

Info

Publication number: WO2009062392A1
Application number: PCT/CN2008/001815
Authority: WO
Inventors: Jiande Xi; Xin Zhao
Original assignee: Datang Mobile Communications Equipment Co., Ltd
Priority date: 2007-10-30
Filing date: 2008-10-29
Publication date: 2009-05-22
Also published as: CN101426243A; CN101426243B

Abstract

Method of system handover, communication system and Policy Charging Rule Function PCRF entity are disclosed. The PCRF entity finds the service policy information which is used by the first system for controlling current service of the UE based on UE identifier, service bearer identifier and the network type of the first system; the PCRF entity converts the service policy information into the service policy information which is needed by the second system which corresponds to network type of the second system for controlling current service of the UE; the PCRF returns the service policy information needed by the second system to gateway for policy control in the second system; the gateway for policy control in the second system controls current service which is interactive between the UE and the second system based on the service policy information needed by the second system. The present invention can ensure that the QoS of UE service data before handover is consistent with the QoS of UE service data after handover, accordingly, the present invention can improve experience of users and increase satisfaction of users.

Description

System switching method, communication system and policy charging rule function entity

The present invention relates to the field of communications, and in particular, to a technique for switching between systems. Background technique

With the rapid development of communication technology, in the current ^{3GPP (the th3 rd Generation Project Partner} , Third Generation Partnership) LTE (Long Term Evolution, Long Term Evolution) / SAE (System Architecture Evolution, System Architecture Evolution) Systems Evolution , there has been a 3GPP system and the non-3 GPP (non-the th3 rd Generation Project partner, non third Generation partnership) system coexist, shown in Figure 1, is given in 3GPP LTE EPS (Evolved Packet system, Evolved Packet System) The system architecture when compatible with non-3GPP systems. The upper part of the dotted line in the figure belongs to 3GPP LTE EPS, and the following part of the dotted line belongs to the non-3GPP system. The 3GPP LTE EPS includes the following network elements:

The PDN GW (Packet Data Network Gateway) is configured to perform an operation policy implementation of the operator, a deep detection of the data packet, and a function of assigning a user IP address, where the user IP address corresponds to the non-3GPP home network. Mobile IPv4 HoA (Mobile IPv4 Home of Address, Mobile IPv4 Home Address;).

Serving GW (Serving Gateway), which is a mobility anchor between eNodeBs (evolved NodeBs) in 3GPP systems, and 3GPP E-UTRAN (Evolved Universal Terrestrial Radio Access Network) /GERAN (GSM EDGE Radio Access Network, GSM Evolution Radio Access Network) / UTRAN (Universal Terrestrial Radio Access Network) access network anchor point for data routing Forward.

HSS (Home Subscriber Server), including AAA server and database, is used to store subscription information of packet data.

3GPP AAA Server (3GPP Authentication Authorization and Accounting Server, 3GPP authentication and authorization accounting server), used for authentication and authorization accounting, mainly for non-3GPP systems.

The PCRF (Policy Charging Rule Function) entity is used to implement the service QoS policy of the operator and the corresponding charging rule.

PMIPv6 exists on the connection interface S5 between the Serving GW and the PDN GW.

GTP tunnel, the S5 interface supports IP protocol.

In the non-3GPP system, the mobility of the UE, the user registration process of the layer 2, and the resource status of the air interface link level, the registration process of the IP layer of the management user, and the external agent (FA, Foreign Agent) function of the Mobile IP ( Entities for MIPv4) or Mobile Access Gateway (MAG) functions (for PMIP), and user mobility management functions may be located on the same entity, such as the Access Service Network Gateway (ASN GW, located in the Wimax system, The Access Server Network Gateway may or may not be located on the same entity, such as a Packet Control Function (PCF) entity and a Packet Data Serving Node (PDSN) entity of the CDMA2000 system. The connection between the UE and the non-3GPP access gateway responsible for the MIP FA/PMIPv6 MAG function uses a PPP (Point to Point Protocol) connection. The Mobile IPv4 Home Agent (HA, Home Agent) / ΡΜΙΡνό Local Mobile Agent (LMA, Local Mobile Agent) function is located on the PDN GW.

In order to meet people's communication needs, seamless switching between different systems has become more and more popular. At present, the operator has reached a consensus on the handover framework between the 3GPP system and the non-3GPP system. The following is a procedure for the user terminal to switch from the 3GPP system to the non-3GPP system based on the Mobile IPv4 FA (Foreign Agent) mode, such as As shown in FIG. 2, the method includes the following steps: Step 1: The user terminal sends the uplink data by using the PDN GW to the IP address of the PDN GW, and the uplink data is forwarded to the PDN GW by using the Serving GW route, and the PDN GW refers to the stored service policy information. Uplink data is used for policy control, and the policy-controlled uplink data is sent to an external packet data network PDN (Packet Data Network); the PDN GW receives downlink data from the PDN, and performs policy control on the data according to the stored service policy information. And through The PMIPv6 or GTP tunnel between the Serving GW and the PDN GW sends the policy-controlled downlink data to the Serving GW, and forwards the data to the user terminal via the Serving GW route.

Step 2: The user terminal searches for the trusted non-3GPP system and decides to transfer the service carried out with the current 3GPP system to the non-3GPP system.

Step 3a to step 3b: The user terminal sends an access authentication request (Access Auth) message to the trusted non-3GPP system, where the user identifier MN-NAI and the IP address of the PDN GW requesting to establish an IP connection are carried; the non-3GPP system After receiving the access authentication request message, the IP access gateway interacts with the HSS/AAA server to perform an access authentication and authorization process for the user terminal.

After the user terminal is authenticated and authorized, the 3GPP HSS/AAA server sends the IP address of the PDN GW serving the user terminal to the entity responsible for mobility management in the non-3GPP system, and may also send the user's key information and used for PDN GW information configured by the protocol (including protocol configuration options).

Step 4: The user terminal obtains proxy address routing information by sending an AS (Agent Solicitation) IKK (Agent Advertisement) to the non-3GPP IP access gateway on the PPP connection, where the proxy address routing information is FA-CoA (Foreign Agent Care of Address).

Step 5a: The user terminal sends an RRQ (Mobile IP Registration Request) message to the non-3GPP IP access gateway according to the FA-CoA, where the RRQ message includes: a user identifier MN-NAI.

Step 5b: After receiving the RRQ message, the non-3GPP IP access gateway sends an authentication request message to the HSS/AAA server, and carries the user identifier MN-NAI and the non-3GPP IP access gateway in the sent authentication request message. The address information to determine if you have the external proxy function for the user terminal.

Step 6: After the authentication is passed, the non-3GPP IP access gateway sends the RRQ message to the PDN.

GW.

Step 7: After receiving the RRQ message, the PDN GW interacts with the HSS/AAA server to access the RRQ. The message is authenticated 4 authorized.

Step 8a to Step 8b: After the authentication is passed, the PDN GW allocates an IP address to the user terminal, and responds by an RRP (Registration Response) message, and returns the IP address to the non-3GPP IP access gateway. An MIPv4 tunnel is established between the non-3GPP IP access gateway and the PDN GW. The non-3GPP IP access gateway returns the IP address to the user terminal through the RRP message. At this point, the non-3GPP IP access gateway establishes a PPP connection with the user terminal.

Step 9: The user terminal sends uplink data based on the PPP connection and the MIPv4 tunnel, and receives data sent by the non-3GPP system.

It can be seen from the above steps that the prior art only gives a handover procedure from the 3GPP system to the non-3GPP system, but does not provide measures to reduce data loss and loss of user service data quality of service (QoS). So it will affect the user's experience.

In addition, when the user terminal switches to the non-3GPP system, if the resources occupied by the user terminal in the original 3GPP system are not released, the full utilization of the communication system resources is affected. Summary of the invention

The invention provides a system switching method, a communication system and a policy charging rule function entity, which can ensure the consistency of the QoS of the user terminal service data before and after the system switching, thereby improving the user experience and improving the user satisfaction.

An embodiment of the present invention provides a method for system switching, where the method includes:

The gateway for policy control in the second system sends a request for obtaining the service policy information required by the second system to control the current service of the user terminal to the policy charging rule function entity; the request carries the identifier of the user terminal, Service bearer identity, first system network type, and second system network type;

The policy charging rule function entity finds service policy information used by the first system to control the current service of the user terminal according to the identifier of the user terminal, the service bearer identifier, and the first system network type; The business policy information used is converted to the second system network class The second system corresponding to the type controls the service policy information required for the current service of the user terminal; and returns the service policy information required by the second system to the gateway for policy control in the second system ;

The gateway for policy control in the second system controls the current service that the user terminal interacts with the second system according to the service policy information required by the second system.

The embodiment of the invention further provides a communication system, the communication system comprising a first system and a second system:

The second system includes: a gateway for policy control;

The communication system further includes: a policy charging rule function entity;

The gateway for policy control in the second system is configured to send, to the policy charging rule function entity, a request for acquiring the service policy information required by the second system to control the current service of the user terminal; The identifier of the terminal, the service bearer identifier, the first system network type, and the second system network type;

The policy charging rule function entity is configured to find, according to the identifier of the user terminal, the service bearer identifier, and the first system network type, service policy information used by the first system to control the current service of the user terminal; The service policy information used by the first system is converted into the service policy information required by the second system corresponding to the second system network type for controlling the current service of the user terminal; and the service policy information required by the second system is Returning to the gateway for policy control in the second system;

The gateway for policy control in the second system is further configured to control, according to the service policy information required by the second system, the current service that the user terminal interacts with the second system.

The embodiment of the present invention further provides a policy charging rule function entity, where the policy charging rule function entity includes:

An information processing unit, configured to find, according to the identifier of the user terminal, the service bearer identifier, and the first system network type, service policy information used by the first system to control the current service of the user terminal; Translating the service policy information into the service policy information required by the second system corresponding to the second system network type for controlling the current service of the user terminal; The information transmission unit is configured to return the service policy information required by the second system to the gateway for policy control in the second system.

According to the solution provided by the foregoing embodiment of the present invention, the policy charging rule function entity finds that the first system controls the current service of the user terminal according to the identifier of the user terminal, the service bearer identifier, and the first system network type. The service policy information is: converting the service policy information used by the first system into the service policy information required by the second system corresponding to the second system network type for controlling the current service of the user terminal; The service policy information required by the second system is returned to the gateway for policy control in the second system; the gateway for policy control in the second system, according to the service policy information required by the second system, to the user The current service of the terminal interacting with the second system is controlled. Therefore, with the embodiment of the present invention, the consistency of the QoS of the service data of the user terminal before and after the system switching can be ensured, thereby improving the user experience and improving the user satisfaction. DRAWINGS

1 is a system architecture diagram of a Non-3GPP-compatible system in an EPS system provided by the prior art; FIG. 2 is a flowchart of switching from a 3GPP system to a non-3GPP system provided by the prior art; FIG. 3 is a system according to an embodiment of the present invention; Principle flow chart of the switching method;

FIG. 4 is a flowchart of a handover of a 3GPP system to a non-3GPP system according to an embodiment of the present invention. detailed description

Considering that the QoS policy information of the services before and after the system handover does not match, it will affect the quality of service standards of the services being transmitted. For the same service, the corresponding service QoS policy information is inconsistent in different systems. If the QoS policy information of the service before and after the system handover is not matched, the service quality of the service being transmitted will be affected, and the user will be reduced. Experience. In order to improve the user experience, an embodiment of the present invention provides a system switching method, in which a gateway for policy control in a second system can learn that a user terminal switches from a first system to a second system, and the method The principle flow is shown in Figure 3, including: Step 101: The gateway for policy control in the second system sends a request for acquiring the service policy information required by the second system to control the current service of the user terminal to the policy charging rule function entity; the request carries the user The identity of the terminal, the service bearer identifier, the first system network type, and the second system network type.

In step 101, the gateway for policy control in the second system may, after receiving the request for establishing an IP connection, send, to the policy charging rule function entity, the current service of the second system to the user terminal. And performing a request for controlling the required service policy information; the gateway for policy control in the second system may also send the second system pair to the policy charging rule function entity after successfully establishing an IP connection with the user terminal. The current service of the user terminal performs a request for the service policy information required for control.

Step 102: The policy charging rule function entity finds a service policy used by the first system corresponding to the first system network type to control the current service of the user terminal according to the identifier of the user terminal, the service bearer identifier, and the first system network type. And converting the service policy information used by the first system into the service policy information required by the second system corresponding to the second system network type to control the current service of the user terminal.

Step 103: The policy charging rule function entity returns the service policy information required by the second system to the gateway used for policy control in the second system.

Step 104: The gateway for policy control in the second system controls the current service that the user terminal interacts with the second system according to the service policy information required by the second system.

The gateway for policy control in the second system notifies the entity responsible for the mobility management function of the second system to update the second service system according to the obtained service policy information required by the second system to control the current service of the user terminal. Air interface link level service policy information managed in the system. The air interface link of the current service that the user terminal interacts with the second system is controlled by using the service policy information of the air interface link level.

The foregoing service policy information includes: business service quality policy information.

In order to further improve the user experience, the foregoing embodiment of the present invention may further include: a gateway entity for mobility management and bearer management in the first system, such as MME (Mobility Manage) Entity, mobility management entity/SGSN (Serving GPRS Support Node;), receiving an indication that the carrying user terminal decides to switch from the first system to the second system (the indication is that the user terminal is Before the system switching process is started, according to the non-real-time service type that the ongoing service belongs to, the indication includes the serial number information of the downlink data that the user terminal has successfully received, and then the corresponding gateway is notified to stop the current according to the indication. The ongoing service data is delivered, and the received downlink service data is cached. After the user terminal switches to the second system, the cached service data is transferred to the second system.

The foregoing embodiment of the present invention may further include: after the handover process is completed, notifying the first system to release the resources allocated for the current service of the user terminal, which may be implemented in the following three manners: The first mode:

The access gateway of the second system learns that the user terminal requests the route update, and the reason for the route update is the different system handover, and sends the location update information to the HSS/AAA server according to the route update request, where the location update information includes the reason for the different system handover. .

The HSS/AAA server sends a message to cancel the location to the gateway entity for mobility management and bearer management in the first system, such as the MME/SGSN, according to the different system handover reason.

The gateway entity for mobility management and bearer management in the first system, such as the MME/SGSN, after receiving the cancel location message sent by the HSS/AAA server, determines that the first system needs to be released according to the cancel location message. The service resource allocated by the user terminal notifies the corresponding gateway in the first system, and releases the service resource allocated for the current service of the user terminal.

The second way:

The gateway entity for mobility management and bearer management in the first system, such as the MME/SGSN, learns that the user terminal requests to detach, and the reason for detaching is a different system handover; determining, according to the detach request, that the first system needs to be released For the service resource allocated by the user terminal, the corresponding gateway in the first system is notified to release the service resource allocated for the current service of the user terminal.

The third way:

The packet data network gateway (such as the PDN GW) in the first system learns that the user terminal completes the establishment process of the bearer channel and performs data forwarding normally through the second system access gateway and itself. After that, the gateway entity (such as MME/SGSN) for mobility management and bearer management in the first system is notified to delete the bearer resource.

The gateway entity (for example, the MME/SGSN) for the mobility management and the bearer management in the first system notifies the corresponding gateway in the first system to release the service allocated for the current service of the user terminal according to the notification of deleting the bearer resource. Resources.

The first system may be a 3GPP system, the second system may be a non-3GPP system, and the gateway for policy control in the second system may be a PDN GW or a non-3GPP Access Gateway (such as a PDSN of CDMA2000, Wimax's ASN GW), or both, perform policy control.

The application of the embodiment of the present invention is described in detail in the Mobile IPv4 FA mechanism, and the 3GPP system is switched to the non-3GPP system. The specific process is as shown in FIG. 4, and includes the following steps: Step 1: The user terminal passes the 3GPP system ( As the E-UTRAN/GERAN/UTRAN is connected to the network, the UE uses its specific GTP or PMIPv6 tunnel transmission mode (between the Serving GW and the PDN GW) in the 3GPP system during the IP connection with the 3GPP system. A PMIPv6 or GTP tunnel exists on the connection interface S5, and the S5 interface can support the IP protocol to transmit data.

In step 2a, the user terminal performs signal measurement and finds the trusted non-3GPP system, and decides to perform inter-system handover.

Step 2b: Before starting the handover to the non-3GPP system, the UE determines whether the current service data belongs to the non-real time service type or the real-time service type, and determines whether the 3GPP system needs to cache the current service data.

For non-real-time services, it is necessary to cache service data during the handover process to reduce data loss. Therefore, if the current service belongs to a non-real-time service type, the user terminal determines that the 3GPP system needs to buffer the current service data, and then the MME to the 3GPP system. The /SGSN sends an indication to switch to the non-3GPP system, where the indication includes the sequence number information of the downlink data that the user terminal has successfully received, and then performs step 2c.

For the real-time service, there is no need or need to cache the service data. Therefore, if the current service belongs to the real-time service type, the user terminal determines that the 3GPP system does not need to cache the current service data. It is possible to skip step 2c and directly perform the inter-system handover process.

Step 2c: After receiving the indication, the MME/SGSN of the 3GPP system instructs the PDN GW to suspend transmission of data and perform corresponding buffer processing.

Before the handover procedure is started, the non-real-time service data is cached, so that after the user terminal establishes a bearer connection with the non-3GPP system, the service data buffered in the PDN GW is routed to the non-3GPP system to reduce data loss.

Step 3a to step 3b, the UE initiates an access procedure to the non-3GPP system; the entity responsible for mobility management in the non-3GPP system, such as PCF in CDMA2000, ASN-GW entity in Wimax, sends a layer to the HSS/AAA server. The access authentication request of 2, which carries the MN-NAI of the user terminal, and the IP address of the PDN GW serving the UE.

The HSS/AAA server performs layer 2 access authentication and authorization procedures for the user terminal. The identity of the UE is authenticated in the non-3GPP procedure, and the subscription information of the UE is obtained.

After the access authentication is passed, the HSS/AAA server authorizes the user terminal to allow access to the non-3GPP system, and indicates to the entity responsible for mobility management in the non-3GPP system the PDN GW having the IP HA function, the address of the PDN GW, The user's key information and PDN GW information for protocol configuration (including protocol configuration options) are sent to the entity responsible for mobility management in the non-3GPP system. The entity responsible for mobility management in the non-3GPP system can return the address of the PDN GW and the PDN GW information to the user terminal through the access gateway.

Step 4: The entity responsible for mobility management in the non-3GPP system (such as the PCF in CDMA2000) receives the above information, and notifies the access gateway (such as the AGW/PDSN in CDMA2000) and the UE corresponding to the MN-NAI. The establishment process of the PPP connection.

If the entity responsible for mobility management in the non-3GPP system is the same entity as the access gateway, the ASN-GW (Access Servive Network Gateway) in the Wimax system is not only responsible for mobility management but also responsible for access functions. Then, the entity directly establishes a PPP connection with the user terminal after receiving the above information.

Step 5: After the PPP connection is successfully established, the access gateway of the non-3GPP system (CDMA2000) The AGW/PDSN or the ASM-GW of the Wimax performs the Mobile IPv4 FA function, and sends an AA (Agent Advertisement) message on the PPP connection, which carries the FA CoA address information, or the UE sends the Agent Solicitation on the PPP connection. The message is sent to the access gateway of the non-3GPP system that performs the foreign agent (FA) function, requesting to obtain the FA CoA address information. It can be seen that the user terminal can obtain the proxy address routing information, that is, the FA CoA address information, by the following two methods:

First, the user terminal sends an AS message on the PPP connection to the access gateway of the non-3GPP system (such as PCF in CDMA2000, ASN-GW entity in Wimax), according to the information returned by the access gateway of the non-3GPP system. Obtain FA CoA address information; or,

The access gateway with the Mobile IP FA function in the non-3GPP system sends an AA message on the PPP connection, where the proxy address routing information is the FA CoA address information; the user terminal obtains the FA from the AA message. CoA address information.

Step 6: After acquiring the FA CoA address information, the user terminal initiates a Mobile IP registration process according to the FA CoA address information, that is, sends an MIPv4 RRQ message to the access gateway of the non-3GPP system with the Mobile IP FA function, where the MIPv4 The RRQ message contains the user identifier MN-NAI and the IP address (FA CoA address, HoA address) request information.

Step 7: After receiving the MIPv4 RRQ message sent by the UE, the access gateway of the non-3GPP system initiates an L3 (Layer 3, Layer 3) IP level authentication process to the HSS/AAA server, and sends the authentication process to the HSS/AAA server. Obtain IP-level subscription service QoS policy information. The details are as follows: The access gateway of the non-3GPP system sends an Access Request to the 3GPP HSS/AAA server.

(access request) message, which carries the user identifier MN-NAI, and the address information of the access gateway; determines whether the access gateway of the non-3GPP system is based on the Access Response returned by the 3GPP HSS/AAA server Has the function of an external proxy.

Step 8, after the access gateway of the non-3GPP system determines that it has the function of the external proxy, sends the MIPv4 RRQ message to the PDN GW with the IP HA function indicated in step 3b, which includes the UE identifier MN-NAI and the IP address. Request information.

Step 9. After receiving the MIPv4 RRQ message, the PDN GW and the 3GPP HSS/AAA service The device interacts to authenticate the MIPv4 RRQ message.

Step 10: After the authentication is passed, the PDN GW allocates an IP address to the UE corresponding to the MN-NAI according to the UE identifier MN-NAI and the IP address request information carried in the MIPv4 RRQ message, and responds by using the MIPv4 RRP message, and the IP address is obtained. Returned to the access gateway of the non-3GPP system. Here, the IP address is an IP address assigned to the UE by the original 3GPP system, and corresponding to the home Mobile IP HoA address, the IP address of the UE remains unchanged, and the service continuity can be maintained.

Since the original IP address information of the UE is stored in the PDN GW because it is switched from the 3GPP system to the non-3GPP system, the IP address originally allocated to the UE can be determined according to the user identifier MN-NAI.

After the access gateway of the non-3GPP system receives the MIPv4 RRP message, the MIPv4 tunnel between the access gateway of the non-3GPP system and the PDN GW is established.

In order to maintain the consistency of the service QOS, the access gateway of the non-3GPP needs to obtain the service QoS policy information from the PCRF entity and update the QoS policy information of the air interface link level service managed by the PCF/ASN-GW entity. The QoS policy information of the IP-level service is consistent with the QoS policy information of the air interface link-level service. Since the PCRF entity manages the service QoS policy information suitable for different access type systems, the corresponding service QoS policy information can be selected according to the access type. Thereafter, the access gateway of the non-3 GPP sends a Register Accepted message to the UE, which carries a MIP RRP message indicating that the UE attach is complete. At this time, the user plane IP connection between the UE and the PDN GW is established successfully. Specifically as described in steps 11 and 12:

Step 11: After receiving the MIPv4 RRP message fed back by the PDN GW, the access gateway of the non-3GPP system requests the PCRF entity to obtain the IP-level service QoS policy information of the UE by using the Fetch QoS information signalling message. The message carries information such as the MN-NAI of the user terminal, the service bearer identifier, the network type of the non-3GPP system requesting access, and the network type of the original 3GPP system;

The PCRF entity determines, according to the network type of the non-3GPP system carried in the Fetch QoS information signalling message, that the system currently serving the user terminal is a non-3GPP system. Then, according to the MN-NAI of the user terminal, the service bearer identifier, and the network type of the original 3GPP system, the service QoS policy information used by the original 3GPP system to control the current service of the user terminal is found, and Converting the service QoS policy information used by the original 3GPP system to control the current service of the user terminal to the service QoS policy information required by the non-3GPP system to control the current service of the user terminal, and then the service QoS policy The information is returned to the access gateway of the non-3GPP system for policy control;

The non-3GPP system uses the access control gateway for policy control to save the obtained service QoS policy information, and updates the air interface link level service QoS policy managed by the entity responsible for mobility management (such as the PCF entity in CDMA2000) in the non-3GPP system. The information is such that the IP-level service QoS policy information and the air interface link-level service QoS policy information are consistent.

Similarly, after the PDN GW allocates an IP address to the UE, the Fetch QoS information signalling message is used to request the PCRF entity to obtain the IP-level service QoS policy information of the current service of the UE, where the message carries the MN-NAI of the user terminal, and the service Information such as the bearer identifier, the network type of the non-3GPP system requesting access, and the network type of the original 3GPP system;

The PCRF entity determines, according to the network type of the non-3GPP system carried in the Fetch QoS information signalling message, that the system currently serving the user terminal is a non-3GPP system. Then, according to the MN-NAI of the user terminal, the service bearer identifier, and the network type of the original 3GPP system, the service QoS policy information used by the original 3GPP system to control the current service of the user terminal is found, and the original 3GPP system is used for the user. The service QoS policy information used by the current service control of the terminal is converted into the service QoS policy information required by the non-3GPP system to control the current service of the user terminal, and then the service QoS policy information is returned to the PDN GW. The PDN GW saves the obtained service QoS policy information.

The following example describes in detail the processing of the PCRF entity:

The 3GPP system defines Conversational, Streaming, Interactive, and Background QoS classes for voice communications, streaming downloads, Internet access, and background downloads or emails. Download and more. 14 QoS parameters are used in 3GPP UTRAN/GERAN, including Traffic class, MBR (Maximum Bit Rate), GBR (Proof Guaranteed Bit Rate), Transfer Delay (Transmission Delay), ARP (Allocation) And Retention Priority, Each priority QoS class, THP (Traffic Handling Priority), SDU Error Ratio and Residual bit error ratio, signaling indication, etc., are used to indicate each QoS class of service.

Each of the above four QoS classes of service in the 3GPP EPS can be represented by four QoS parameters. The four QoS parameters include QCI (QoS Class Identifier), ARP, MBR, and GBR.

Non-3GPP's WiMAX access system defines UGS (Unsolicited Grant Service), ErtPS (eRT-VR Data Delivery Service, enhanced real-time polling service), rtPS (RT-VR Data Delivery Service, real-time polling) 5) QoS class of service, NRTPS (nRT-VR Data Delivery Service) and BE (Best Effort), for E1 transmission, VoIP (voice over IP, IP-based Voice transmission), live video, Internet access, etc. The five QoS service levels are represented by eight QoS parameters, including Max sustained traffic rate, Traffic Priority, Request/transmission policy, Maximum Latency. ), Maximum Traffic Burst, Media Flow Type, Minimum Reserved Traffic Rate, Service Class Name.

Non-3GPP's CDMA2000 system defines Conversational, Streaming, Interactive, and Background QoS classes, represented by seven QoS parameters. The seven QoS parameters include bandwidth, delay, jitter, Packet Loss, Priority, Traffic class, and IP QoS Class. The division of the QoS service level in CDMA2000 is basically the same as the division of the QoS service level in 3GPP, and is divided into a session level, a flow level, an interaction level, and a background level. The service types supported by the session level are: telephone, multimedia conference, and signaling; the service types supported by the interaction level are: real-time interactive services; the service types supported by the flow level are: multimedia stream and broadcast video; For: high-throughput data services, low-latency data services, low-priority data services, and standard data services. Taking ftp download as an example, in the 3GPP EPS system, the QoS parameters QCI = 8, MBR = 1 Mbps, GBR = 128 kbps, ARP = 1 (high priority). After the inter-system handover occurs on the user terminal, the ftp download service is carried by the Wimax system. The PCRF entity needs to generate the QoS service level in the Wimax system according to the above four QoS parameters according to the network type accessed by the user terminal. Corresponding 8 QoS parameters. For example, the corresponding QoS service level in the Wimax system is NrtPS, and the corresponding Max sustained traffic rate = 1 Mbps, Traffic Priority (service priority) = 5 (users in the EPS system are considered in the mapping algorithm) Higher level), Request transmission policy = Spreading code generated by an algorithm, Maximum Latency = 100ms, Maximum Traffic Burst = 10ms, Media Flow Type ( Media stream type) = Data, Minimum Reserved Traffic Rate = 128kbps, Service Class Name.

It should be noted that the QoS mapping algorithm scheme between different access types is not involved here, and the above is only an example.

Step 12: The non-3GPP access gateway with the FA function encapsulates the MIPv4 RRP message in the Register Accepted message and forwards it to the user terminal.

After the user terminal receives the Register Accepted message, the PPP connection between the user terminal and the access gateway of the non-3GPP system is established.

So far, the default bearer channel of the user terminal is established, the bearer channel is connected by the PPP between the user terminal and the access gateway of the non-3 GPP system, and the MIPv4 between the access gateway of the non-3 GPP system and the PDN GW. The tunnel is composed.

Step 13: The user terminal sends the uplink service data by using the allocated IP address of the original 3GPP system through the PPP connection; the uplink service data reaches the access gateway of the non-3GPP system, and the access gateway of the non-3GPP system uses the The saved service QoS policy information is used to control the uplink service data, and the controlled uplink service data is sent to the PDN GW through the newly established MIPv4 tunnel; the PDN GW uses the service QoS policy information it holds, The uplink service data is controlled by the policy, and the controlled uplink service data is sent to non-3GPP system.

The PDN GW switches the delivery path to the newly established MIPv4 tunnel, and sends downlink service data from the non-3 GPP system, which may also include the service data cached in the PDN GW, and utilizes the saved service QoS policy information, The downlink service data is controlled by the policy, and the controlled downlink service data is sent to the access gateway of the non-3GPP system through the newly established MIPv4 tunnel; the access gateway of the non-3GPP system utilizes the saved service QoS policy. The information is used to control the downlink service data, and the controlled downlink service data is sent to the user terminal through the newly established PPP connection.

After the handover is completed, the original 3GPP system needs to delete the resources allocated for the UE, as follows: Method 1: The UE actively sends a Route Update message to the entity responsible for mobility management in the non-3GPP system to initiate a route update process. , triggering the PCF/ASN-GW entity to initiate a Location Update process to the HSS/AAA server. During the location update process, the HSS/AAA server sends the original 3GPP MME/SGSN entity according to the information it saves from the original information. A Cancel Location indication is sent indicating that it triggers the deletion of bearer resources allocated for the UE in the 3GPP system. The HSS/AAA server then informs the UE that the routing update is complete through the non-3GPP system. Specifically, the following steps are included:

Step 14: After receiving the attach complete message, the user terminal sends a Route Update message to the non-3GPP system responsible for mobility management (such as PCF of CDMA2000 and ASN GW of Wimax), where: the user terminal is in the non-3GPP system. The reason for the current location information, routing updates is different system switching.

Step 15: The entity responsible for mobility management in the non-3GPP system sends a Location Update message to the 3GPP HSS/AAA server according to the received routing update message, and the reason for the message including the location update is a different system handover, and the currently served network. Type and network element entity identification information.

Step 16. The 3GPP HSS/AAA server sends a Cancel Location indication to the MME/SGSN entity of the 3GPP system according to the information carried in the location update message, instructing the MME/SGSN to delete the corresponding context information and bearer resources.

Step 17, the entity MME/SGSN responsible for mobility management and bearer management in the 3GPP system The eNodeB/RNC, the Serving GW, and the PDN GW of the 3GPP system initiate a process of deleting a bearer resource by using a Delete Bearer Request message, and the eNodeB/RNC, the Serving GW, and the PDN GW delete the respective bearer resources, and feedback Delete. The Bearer Response message is sent to the MME/SGSN.

Step 18: After receiving the Delete Bearer Response message, the MME/SGSN sends the message to the 3GPP.

The HSS/AAA server feeds back an ACK confirmation message.

Step 19: The HSS/AAA server sends a Location Update ACK message to the non-3GPP system responsible for mobility management, indicating that the location update is successful, and the HSS/AAA server saves the user terminal in the non- Location information in the 3GPP system.

Step 20: The non-3GPP system responsible for mobility management sends a route to the user terminal.

Update Ack information indicating that its routing update was successful.

Method 2: After the handover is completed, if the UE supports the dual radio capability, the UE actively sends a Detach Request message to the MME/SGSN entity of the original 3GPP system, and the reason for the de-attachment is a different system handover, indicating the MME/SGSN entity. Initiate the process of deleting a bearer resource. Specifically include:

First, after receiving the attach complete message, the user terminal sends a Detach Request message to the MME/SGSN entity of the 3GPP system, which includes the reason for the user terminal to detach, and the reason is different system handover.

Next, the MME/SGSN entity decides to delete the bearer resource allocated for the UE in the 3GPP system according to the reason of the detachment in the Detach Request message, and initiates deletion to the eNodeB/RNC, Serving GW, and PDN GW of the 3GPP system by using the Delete Bearer Request message. The process of carrying the resources; the eNodeB/RNC, the Serving GW and the PDN GW delete the respective bearer resources, and feed back the Delete Bearer Response message to the MME/SGSN entity.

After receiving the Delete Bearer Response message of the eNodeB/RNC, the Serving GW, and the PDN GW, the MME/SGSN entity determines that the bearer resource allocated for the UE in the 3GPP system has been deleted, and sends a Detach Accept message to the user terminal. The UE is notified that the bearer resources in the 3GPP system have been successfully deleted and successfully detached from the 3GPP system. Method 3: The PDN GW notifies the 3GPP system to delete the corresponding context information and bearer resources. Specifically include:

First, after the UE establishes a bearer between the non-3GPP access gateway and the PDN GW and performs a normal uplink and downlink data forwarding process, the PDN GW notifies the MME/SGSN entity to delete the bearer resource.

Next, the MME/SGSN entity initiates a process of deleting the bearer resource to the eNodeB/RNC, the Serving GW, and the PDN GW of the 3GPP system by using the Delete Bearer Request message; the eNodeB/RNC, the Serving GW, and the PDN GW delete the respective bearer resources, and feed back the Delete Bearer. The Response message is sent to the MME/SGSN entity.

After receiving the Delete Bearer Response message, the MME/SGSN entity determines that the bearer resource allocated by the 3GPP system for the UE has been successfully deleted, and feeds back to the PDN GW that the bearer resource in the 3GPP system has been successfully deleted.

In addition, the access gateway or the PDN GW of the non-3GPP system may obtain the service QoS policy information from the policy charging rule function entity after the system switching is completed, and the obtaining method is the same as the method described in step 11, where It is no longer detailed. It is also within the scope of the present invention to use the method provided by the embodiments of the present invention in the transmission protocol.

Correspondingly, the embodiment of the present invention further provides a communication system, including a first system and a second system, where the second system includes: a gateway for policy control, which can learn that the user terminal switches from the first system to the first The second system, the communication system further includes: a policy charging rule function entity;

The gateway for policy control in the second system is configured to send, to the policy charging rule function entity, a request for acquiring the service policy information required by the second system to control the current service of the user terminal; Carrying the identifier of the user terminal, the service bearer identifier, the first system network type, and the second system network type;

The policy charging rule function entity is configured to find, according to the identifier of the user terminal, the service bearer identifier, and the first system network type, service policy information used by the first system to control the current service of the user terminal; The business policy information used by the first system is converted into the second system The second system corresponding to the network type controls the service policy information required for the current service of the user terminal; and returns the service policy information required by the second system to the second system for policy control. Gateway

In addition, an embodiment of the present invention further provides a policy charging rule function entity, including: an information processing unit and an information transmission unit.

An information processing unit, configured to find, according to the identifier of the user terminal, the service bearer identifier, and the first system network type, service policy information used by the first system to control the current service of the user terminal; The service policy information is converted into service policy information required by the second system corresponding to the second system network type to control the current service of the user terminal.

And an information transmission unit, configured to return the service policy information required by the second system to the gateway for policy control in the second system.

According to the solution provided by the foregoing embodiment of the present invention, the policy charging rule function entity finds that the first system controls the current service of the user terminal according to the identifier of the user terminal, the service bearer identifier, and the first system network type. The service policy information is: converting the service policy information used by the first system into the service policy information required by the second system corresponding to the second system network type for controlling the current service of the user terminal; The service policy information required by the second system is returned to the gateway for policy control in the second system; the gateway for policy control in the second system, according to the service policy information required by the second system, to the user The current service of the terminal interacting with the second system is controlled. Therefore, with the embodiment of the present invention, the consistency of the QoS of the service data of the user terminal before and after the system switching can be ensured, thereby improving the user experience and improving the user satisfaction. The present invention will be described in detail with reference to the preferred embodiments, and those skilled in the art should understand that the technical solutions in the embodiments of the present invention may be modified or substituted without departing from the technical solutions of the embodiments of the present invention. Spirit and scope.

Claims

Rights request

A method for system switching, the method comprising:

The policy charging rule function entity finds service policy information used by the first system to control the current service of the user terminal according to the identifier of the user terminal, the service bearer identifier, and the first system network type; The service policy information used is converted into service policy information required by the second system corresponding to the second system network type for controlling the current service of the user terminal; and the business policy information required by the second system is returned to a gateway for policy control in the second system;

2. The method according to claim 1, wherein the gateway for policy control in the second system sends, to the policy charging rule function entity, the second system to control the current service of the user terminal. Requests for business strategy information, including:

After receiving the request for establishing an IP connection, the gateway for policy control in the second system sends, to the policy charging rule function entity, the service policy information required for the second system to control the current service of the user terminal. Request; or,

The gateway for policy control in the second system, after successfully establishing an IP connection with the user terminal, sends the service policy information required for the second system to control the current service of the user terminal to the policy charging rule function entity. request.

The method according to claim 1 or 2, wherein the service policy information comprises: service quality of service policy information.

4. The method of claim 3, wherein the method further comprises:

The gateway for policy control in the second system is based on the obtained second system to the user terminal. The service policy information required for the pre-service control is updated, and the service policy information of the air interface link level managed by the second system is updated.

The method according to claim 1, wherein the method further comprises: a gateway entity responsible for mobility management and bearer management in the first system, and receiving the user terminal to decide to switch from the first system to the second After the indication of the system, the corresponding gateway is notified to stop the current service data delivery and buffer the received downlink service data according to the indication; after the user terminal is notified that the user terminal switches to the second system, the buffered downlink service is used. The data is transferred to the second system.

The method according to claim 5, wherein the indication is that the user terminal sends the service according to the non-real-time service type before the system switching process is initiated.

The method according to claim 1, wherein the method further comprises: when the access gateway of the second system knows that the user terminal sends a routing update request, and the reason for the routing update is different system switching, according to The route update request sends a location update message to the home subscription subscriber server HSS/authentication authorization accounting AAA server, and the reason for the location update message including the route update is a different system handover;

The HSS/AAA server sends a message of canceling the location to the gateway entity for mobility management and bearer management in the first system according to the reason of the different system handover;

The gateway entity for the mobility management and the bearer management in the first system determines, according to the cancel location message, that the resource allocated by the first system is the current service of the user terminal, and then notifies the corresponding gateway in the first system. The resources allocated for the current service of the user terminal are deleted.

8. The method according to claim 1, wherein the method further comprises: the gateway entity for mobility management and bearer management in the first system knowing that the user terminal requests detachment, and the reason for detaching is When the system is switched, the resource allocated to the current service of the user terminal needs to be deleted according to the request, and the corresponding gateway in the first system is notified to delete the resource allocated for the current service of the user terminal.

The method according to claim 1, wherein the method further comprises: a packet data network gateway PDN GW in the first system, knowing that the user terminal passes the second system After the completion of the bearer channel establishment process and the normal data forwarding, the gateway entity for the mobility management and bearer management in the first system is deleted to delete the first system as the current current of the user terminal. Resources allocated by the business;

The gateway entity for mobility management and bearer management in the first system notifies the corresponding gateway in the first system to delete resources allocated for the current service of the user terminal.

10. A communication system, comprising: a first system and a second system,

The second system includes: a gateway for policy control;

11. A policy charging rule function entity, comprising:

An information processing unit, configured to find, according to the identifier of the user terminal, the service bearer identifier, and the first system network type, service policy information used by the first system to control the current service of the user terminal; Translating the service policy information into the service policy information required by the second system corresponding to the second system network type for controlling the current service of the user terminal; the information transmission unit, configured to use the service policy information required by the second system Returning to the gateway for policy control in the second system.