CN101166109A - Method and system for managing default bearer parameters - Google Patents

Abstract

The present invention provides a method and system for managing default bearer parameters. When a user moves between two different access systems, the policy and charging control function entity (PCRF) is used to manage the default bearer; wherein, The policy and charging control function entity receives the charging and policy rule request carrying the user identification information, updates the charging and policy rule according to the user identification information, and then sends the updated charging and policy rule. It is used to manage the default bearer of users who move between different IP connection access systems and are in the idle state.

Description

Method and system for managing default bearing parameters

Technical Field

The invention relates to a network technology, in particular to a technology for managing default load by a user moving between different IP connection access systems in a network, and specifically relates to a method and a system for managing default load parameters.

Background

To guarantee the competitiveness of 3GPP systems for 10 years or more in the future, a work of evolution of access technologies is being performed within the 3GPP organization. The use of packet technology within 3GPP systems requires further enhancements, particularly to enhance the ability of 3GPP systems to handle the rapidly growing IP data traffic. The most important parts of this type of technological evolution include: reduced latency, higher user data rates, enhanced system capacity and coverage, and reduced overall operator cost. Furthermore, the evolved network structure is also an important index for the backward compatibility of the existing network.

The network architecture of the above access technology evolution needs to satisfy several principles: firstly, in an initialization stage of a terminal access network, basic IP connection needs to be established in an evolved network; the evolved network architecture must minimize the time delay of the user data; the definition of each functional module in the evolution network architecture should avoid the function overlapping or repetition to avoid unnecessary signaling interaction and time delay.

As shown in fig. 1, which is a schematic diagram of a network architecture of System Architecture Evolution (SAE) in the prior art, a core network of a wireless evolution network mainly includes four logic function modules, namely, a Mobility Management Entity (MME), a User Plane Entity (UPE), a 3GPP Anchor (Anchor), and an SAE Anchor. Wherein, the MME is responsible for the mobility management of a control plane, including the management of user context and mobile state, the allocation of user temporary identity, security function and the like, and corresponds to the control plane part of the SGSN in the current Universal Mobile Telecommunications System (UMTS); UPE is responsible for initiating paging for downlink data in idle state, managing and storing IP bearing parameters and routing information in network, etc., for data plane part of GRPS support node (SGSN) serving inside current UMTS system; the 3GPP Anchor is a user plane Anchor point between different access systems in the 3GPP system; the SAE Anchor is the user plane Anchor point between the 3GPP access system and the non-3 GPP system in the SAE. The sum of SAE Anchor and 3GPPANCHOR is called an Inter-access system Anchor (Inter AS Anchor). Non-3 GPP IP Access (Non 3GPP IP Access) refers to various Access systems that are IP based and not defined by the 3GPP organization, which may be worldwide interoperability for microwave Access (WiMax), Asymmetric Digital Subscriber Line (ADSL), and so on. In the prior art, the function and presence of each interface as shown in fig. 1 has not yet been finalized. How the four functional modules of MME, UPE, 3GPP Anchor, SAE Anchor in fig. 1 are combined in the corresponding entities is also uncertain.

A Wireless Local Area Network (WLAN) is a widely existing wireless access system. In order to enable a user to more conveniently access a 3GPP system and use various services in the 3GPP system, the 3GPP has established an Interworking Wireless Local Area Network (IWLAN) project and studied the interworking problem between the WLAN and the 3GPP system, so that the user of the 3GPP system can access the 3GPP system through the WLAN. The IWLAN system architecture is shown in fig. 2. It should be noted that, according to the latest research results of 3GPP, the architecture is not only applicable to the access system of WLAN mode, but also applicable to any access mode based on IP technology, such as WiMAX, ADSL, etc.

The control and charging Policy (PCC) is a unified control and charging policy architecture in 3GPP, which is independent from the specific network at the bottom layer and is applicable to various different IP connectivity access networks (IP-CAN). As shown in fig. 3, in the control and charging policy architecture, an Application Function (AF) provides filter information for policy control and charging and related parameters required for quality of service (QoS) control to a policy and charging control function (PCRF), which controls Policy and Charging Enforcement Function (PCEF) using these parameters to perform corresponding policy control, QoS control, charging, and other functions. For different IP-CAN, the PCEF is located in its respective gateway, e.g. for GPRS, the PCEF is located in the GGSN; for IWLAN, the PCEF is located in the Packet Data Gateway (PDG).

In the existing SAE specification of 3GPP, the registration procedure of a user is shown in fig. 4, and the procedure includes the following steps: step 401, network discovery and access system selection are performed at a User Equipment (UE) end; step 402, UE sends out an attachment request to the current MME/UPE; step 403, the current MME/UPE sends old registration information to the old MME/UPE; step 404, the old MME/UPE sends user information to the current MME/UPE; step 405, authentication is carried out between the UE and the current MME/UPE, and between the current MME/UPE and the HSS; step 406, the current MME/UPE registers MME to HSS; step 407, deleting the UE registration information between the old MME/UPE and the HSS; step 408, HSS sends registration confirmation to current MME/UPE; step 409, selecting an internal system mobility anchor point gateway by the current MME/UPE; step 410, user plane channel configuration is carried out between the UE and the current MME/UPE, and between the current MME/UPE and the InterAS Anchor; step 411, configuring the service quality of the IP bearer between the Evolved radio access network (Evolved RAN) and the current MME/UPE; step 412, the current MME/UPE sends an attach accept to the UE; step 413, the UE sends an attach confirmation to the current MME/UPE.

The above procedure is a procedure for establishing a default bearer when a user accessing SAE through LTE is registered. In step 410 of the process, after the user has registered with the system, the system establishes a bearer for the user, which is the default bearer. In order to increase the support for voice service and improve the connection speed of the mobile device, when the user attaches to the network in the SAE network, a bearer connection is established with the network to realize the "always on" function of the user, and the bearer connection is a default bearer.

As can be known from the above procedure of establishing a default bearer during user registration in the prior art, the default bearer establishment procedure in the SAE specification only relates to the 3GPP access system, but there is no method for establishing a default bearer when a user accesses through a non-3 GPP access system, so that the user accessing from the non-3 GPP system cannot obtain the "always-on" capability.

Chinese patent application 200610106547.5 provides a method for establishing a default bearer for a user accessing from a non-3 GPP access system, and the flow is shown in fig. 5, and the flow includes the following steps: step 501, UE accesses a non-3 GPP access system; step 502, UE inquires GW address; step 503, the UE sends a bearer establishment request to the GW; step 504, the GW sends an authentication request to the HSS/AAA server; step 505, the HSS/AAA sends authentication response to GW; step 506, establishing a security tunnel between the GW and the SAE anchor point; step 507, establishing default load between GW and SAE anchor point and distributing user service address; step 508, carrying out bearing establishment between GW and UE; step 509, the UE registers with SAE anchor via IP multimedia core network subsystem (IMS). The entire disclosure of this patent application is incorporated herein as background document 1.

As can be seen from the above procedure of establishing a default bearer for a user accessing from a non-3 GPP access system, when the user registers from the non-3 GPP access system, the network establishes the default bearer for the user (as shown in step 507 in fig. 5), and assigns a service address to the user, so that the user also has an "always on" capability.

However, although there has been a method of establishing a default bearer when accessing from the LTE access and from the non-3 GPP access system in the related art, there is no corresponding default bearer management method when a user in an idle (idle) state moves between the LTE access system and the non-3 GPP access system. Moreover, there is no direct interface between MME in SAE and GW (GW may be PDG for IWLAN) in non-3 GPP access system, and interaction between them can not be directly performed to complete the management of default bearer.

Documents in the prior art: 1)3GPP TR 23.882: 3GPP System architecture evolution; 2)3GPP TS 23.234: 3GPP system to Wireless Local Area network networking; 3)3GPP TS 23.203: policy and changing controlled architecture, the entire disclosure of which is also incorporated herein in its turn as background documents 2, 3, 4.

Disclosure of Invention

The invention provides a method and a system for managing default bearer establishment parameters, which are used for managing default bearers of users moving between different IP connection access systems and in idle states.

One of the objectives of the present invention is to provide a method for managing default bearer setup parameters, wherein when a user moves between two different access systems, a policy and charging control function (PCRF) is used to manage the default bearer; the policy and charging control function entity receives the charging and policy rule request carrying the user identification information, updates the charging and policy rule according to the user identification information, and then sends out the updated charging and policy rule.

The policy and charging control function entity receiving the charging and policy rule request carrying the user identification information means that: the policy and charging control function entity receives a charging and policy rules request with a user ID from the gateway.

And the policy and charging control function entity records the user ID and the ID of the gateway.

The charging and policy rule request also carries access system type information.

And storing control and charging Policy (PCC) rule information corresponding to the access system type information in a policy and charging control function entity, wherein the policy and charging control function entity locally retrieves corresponding control and charging policy rule information according to the user ID and the access system type information.

The strategy and charging control function entity sends strategy request to a subscription specification library (SPR), the strategy request is provided with access system type information and user ID, the subscription specification library retrieves corresponding strategy rule information according to the access system type information and the user ID, and sends the strategy rule information to the strategy and charging control function entity.

The updating of the charging and policy rules according to the user identification information means: the policy and charging control function entity generates policy and charging rules and related quality of service (QoS) parameters according to the locally retrieved policy information, and then updates the policy rules corresponding to the user ID and the related information of the gateway according to the user ID.

The updating of the charging and policy rules according to the user identification information means: the strategy and charging control function entity generates strategy and charging rules and related service quality parameters according to the strategy information received from the signed specification base, and then updates the strategy rules corresponding to the user ID and the related information of the gateway according to the user ID.

The method further comprises the following steps: the strategy and charging control function entity sends bearing deleting information with user ID to the original gateway, and the bearing deleting information is used for indicating the original gateway to delete the default bearing corresponding to the user; the original gateway initiates deletion of default load in the original system; the strategy and charging control function entity sends new strategy and charging regulation related information to a new gateway; the new gateway establishes a default bearer in the new system based on the received default bearer QoS parameters.

The access system comprises: a System Architecture Evolution (SAE) system and a wireless local area Internet (IWLAN) system; the gateway is a Mobility Management Entity (MME) or a 3GPP Anchor (Anchor) or a System architecture evolution Anchor (SAE Anchor) for a System architecture evolution (NAS) system; the gateway is a Packet Data Gateway (PDG) or a system architecture evolution anchor for a wireless local area internet system. The gateway is also used for executing policy and charging.

Another object of the present invention is to provide a default bearer setup parameter management system, comprising: user equipment, an access system, a core network and a policy and charging control function entity; the user equipment is connected with the core network through the access system, and the policy and charging control function entity is connected with the core network; the user equipment is used for moving between two different access systems; the policy and charging control function entity is used for receiving the charging and policy rule request carrying the user identification information, updating the charging and policy rule according to the user identification information, and then sending the updated charging and policy rule.

The system further comprises: and the gateway sends a charging and policy rule request with a user ID to the policy and charging control function entity.

The system further comprises: the said signing specification base searches the corresponding strategy rule information according to the said access system type information and user ID, and sends the strategy rule information to the said strategy and charging control function entity.

The gateway comprises a policy and charging execution function entity for executing policy and charging.

The invention has the beneficial effects that: the invention realizes the scheme of managing the default load of the user moving between different IP connection access systems and in idle state by utilizing and expanding the related entities and processes in the PCC. By the scheme, the default bearer management when the user moves among different access technologies in the whole SAE system is realized, so that the user can obtain the default bearer in the whole SAE system (only accessed from a 3GPP access system or accessed from a non-3 GPP system), and the capability of always-on is obtained.

Drawings

FIG. 1 is a diagram of a prior art SAE network architecture;

FIG. 2 is a schematic diagram of a prior art IWLAN system architecture;

FIG. 3 is a schematic diagram of a PCC system architecture in the prior art;

FIG. 4 is a flow chart of user registration for SAE specification in the prior art;

fig. 5 is a flowchart of a registration process when a user accesses through a non-3 GPP access system in the prior art;

FIG. 6 is a flow chart of the present invention for establishing a default bearer;

FIG. 7 is a schematic view of a system according to embodiments 1, 2, 3, 4 of the present invention;

fig. 8 is a flowchart of updating a default bearer of a user according to embodiment 1 of the present invention;

fig. 9 is a flowchart of updating a default bearer of a user according to embodiment 2 of the present invention;

fig. 10 is a flowchart of updating a default bearer of a user according to embodiment 3 of the present invention;

fig. 11 is a flowchart of updating a default bearer of a user according to embodiment 4 of the present invention;

FIG. 12 is a schematic view of a system according to embodiments 5, 6, 7, 8 of the present invention;

fig. 13 is a flowchart of updating a default bearer of a user according to embodiment 5 of the present invention;

fig. 14 is a flowchart of updating a default bearer of a user according to embodiment 6 of the present invention;

fig. 15 is a flowchart of updating a user default bearer according to embodiment 7 of the present invention;

fig. 16 is a flowchart of updating a default bearer of a user according to embodiment 8 of the present invention;

FIG. 17 is a schematic view of a system according to embodiments 9, 10, 11, 12 of the present invention;

fig. 18 is a flowchart of updating a default bearer of a user according to embodiment 9 of the present invention;

fig. 19 is a flowchart of updating a user default bearer according to embodiment 10 of the present invention;

fig. 20 is a flowchart of updating a user default bearer according to embodiment 11 of the present invention;

fig. 21 is a flowchart of updating a default bearer of a user according to embodiment 12 of the present invention;

FIG. 22 is a schematic view of a system according to embodiments 13, 14, 15, 16 of the present invention;

fig. 23 is a flowchart of updating a default bearer of a user according to embodiment 13 of the present invention;

fig. 24 is a flowchart of updating a default bearer of a user according to embodiment 14 of the present invention;

fig. 25 is a flowchart of updating a user default bearer according to embodiment 15 of the present invention;

fig. 26 is a flowchart of updating a user default bearer according to embodiment 16 of the present invention;

FIG. 27 is a schematic view of a system according to embodiments 17, 18, 19, 20 of the present invention;

fig. 28 is a flowchart of updating a default bearer of a user according to embodiment 17 of the present invention;

fig. 29 is a flowchart of updating a user default bearer according to embodiment 18 of the present invention;

fig. 30 is a flowchart of updating a user default bearer according to embodiment 19 of the present invention;

fig. 31 is a flowchart of updating a user default bearer according to embodiment 20 of the present invention.

Detailed Description

The following describes embodiments of the present invention with reference to the drawings. The invention uses PCRF to manage the default load of the user moving between different IP connection access systems and in idle state. When the user moves from one IP connection access system to another IP connection access system, PCRF informs the original system to delete the original default load and instructs the current system to establish a new default load. The method is not only applicable between a 3GPP system and a non-3 GPP system, but also applicable between any two different IP connection access systems.

For any two IP connected access systems, the PCRF can be used to manage the default bearer as the user moves between the two access systems. After receiving the request of a new gateway, the PCRF indicates the PCRF to delete the default bearer established for the user in the old system according to the ID of the old gateway originally registered by the user recorded in the PCRF, updates the gateway to which the user belongs to the ID of the new gateway, then the PCRF requests new PCC rule information from the SPR according to the type of an access system carried by the new gateway or retrieves locally stored related PCC rule information from the PCRF, and finally indicates the new gateway to establish the default bearer in the new system. The flow of the method of the invention is shown in FIG. 6. The process comprises the following steps:

step 601, the user sends a registration request to a new gateway;

step 602, the new gateway sends a charging and policy rules request message to the PCRF, where the new access system type and UE ID are brought up;

step 603, if the user reserves PCC rule information corresponding to all access types in the PCRF when the user requests charging and policy rules in the PCRF for the first time, the PCRF may locally retrieve corresponding PCC rule information according to the UE ID and the access system type. Otherwise, PCRF sends policy request message to SPR, requesting PCC rule information used by the user in the new access system, wherein the new access system type and UE ID are added, SPR retrieves corresponding policy rule information according to the new access system type and UE ID, and sends the policy rule information to PCRF through policy response message;

step 604, the PCRF generates policy and charging rules and relevant QoS parameters according to the policy information received from the SPR or retrieved locally, and then updates its corresponding policy rules and gateway-related information according to the UE ID;

step 605, PCRF sends bearer deletion message to original gateway to instruct it to delete default bearer corresponding to the user, where the UE ID is taken down. In addition, a timer can be arranged in the original gateway, and when the timer is overtime, the subsequent deleting operation is carried out to slow down the ping-pong effect;

step 606, the original gateway initiates deletion of default bearers in the original system;

step 607, the original gateway sends a bearer deletion confirmation message to the PCRF, which is optional;

step 608, the PCRF issues new policy and charging rule related information to the new gateway;

step 609, the new gateway establishes a default bearer in the new system according to the received default bearer QoS parameter;

step 610, the new gateway sends a registration response message to the user;

step 611, the new gateway sends a bearer deletion confirmation message to the PCRF, which is optional;

wherein, steps 605 to 607 and steps 608 to 611 do not have a strict sequence; step 610 and step 611 are also not in strict sequence.

As can be seen from the above steps, the PCRF is configured to perform the policy and charging control function, and the gateway includes a PCEF configured to perform the policy and charging enforcement function.

Example 1

The user moves from SAE system to IWLAN system, the gateway in SAE system is 3GPP Anchor (Anchor), the gateway in IWLAN is PDG, and the PCRF retains the PCC rule information of all available access systems of the user. The system structure of embodiment 1 is shown in fig. 7, wherein the PCRF is connected to the 3GPP anchor and the PDG through S7, respectively. In embodiment 1, a process for updating the default bearer of the user is shown in fig. 8, and the process includes the following steps:

step 801, a user accesses an IWLAN access network; step 802, the user queries available PDG addresses; step 803, the user sends a tunnel establishment request to the PDG; step 804, PDG replaces user to send authentication request to HSS/AAAServer; step 805, HSS/AAA Server authenticates user, and sends result to PDG through authentication response message; step 806, PDG sends charging and policy rules request message to PCRF, where new access system type and UE ID are up-loaded; step 807, PCRF will search corresponding PCC rule information locally according to UE ID and access system type; step 808, the PCRF generates policy and charging rules and relevant QoS parameters according to the policy information retrieved locally, and then updates its corresponding policy rules and gateway-related information according to the UE ID; step 809, the PCRF sends a bearer deletion message to the 3GPP Anchor to instruct it to delete the default bearer corresponding to the user, where the UE ID is taken down. In addition, a timer can be set in the 3GPP Anchor, and when the timer is overtime, subsequent deleting operation is carried out to slow down the ping-pong effect; step 810, 3GPP Anchor, MME, UPE, EnodeB interact, delete default load in SAE system; step 811, the 3GPP Anchor sends a bearer deletion confirmation message to the PCRF, which is optional; step 812, the PCRF issues new policy and charging rule related information to the PDG; step 813, PDG establishes default bearer in IWLAN system according to received default bearer QoS parameters; step 814, PDG sends tunnel establishment response message to the user; step 815, PDG sends bearer deletion acknowledgement message to PCRF, which is optional; wherein, the steps 809 to 811 are not in strict sequence with the steps 812 to 815; step 814 is also not in strict sequence with step 815.

Example 2

The user moves from SAE system to IWLAN system, the gateway in SAE system is 3GPP Anchor, the gateway in IWLAN is PDG, PCRF inquires new PCC rule information of access system to SPR each time. The system structure of embodiment 2 is shown in fig. 7, and the flow of updating the user default bearer is shown in fig. 9. The process comprises the following steps:

step 901, a user accesses an IWLAN access network; step 902, the user queries available PDG addresses; step 903, the user sends a tunnel establishment request to the PDG; step 904, PDG replaces user to send authentication request to HSS/AAAServer; step 905, HSS/AAA Server authenticates user, and sends result to PDG through authentication response message; step 906, PDG sends charging and policy rules request message to PCRF, where new access system type and UE ID are up-loaded; step 907, the PCRF requests the SPR to obtain PCC rule information of the user in the new access system; step 908, the PCRF generates policy and charging rules and relevant QoS parameters according to the policy information responded by the SPR, and then updates its corresponding policy rules and gateway-related information according to the UE ID; step 909, PCRF sends bearer deletion message to 3GPP Anchor, instructing it to delete the default bearer corresponding to the user, where the UE ID is taken down. In addition, a timer can be set in the 3GPP Anchor, and when the timer is overtime, subsequent deleting operation is carried out to slow down the ping-pong effect; step 910, 3GPP Anchor, MME, UPE, EnodeB interact, delete default load in SAE system; step 911, the 3GPP Anchor sends a bearer deletion confirmation message to the PCRF, which is optional; step 912, PCRF issues new policy and charging rule related information to PDG; step 913, PDG establishes a default bearer in the IWLAN system according to the received default bearer QoS parameter; step 914, PDG sends tunnel establishment response message to user; step 915, PDG sends bearer deletion confirmation message to PCRF, which is optional; as can be seen from the above steps, the procedure of embodiment 2 is similar to that of embodiment 1, except that in step 907, the PCRF requests the SPR to obtain the PCC rule information of the subscriber in the new access system, which is different from step 807.

Example 3

The user moves from the IWLAN system to the SAE system, the gateway in the SAE system is a 3GPP Anchor, the gateway in the IWLAN is a PDG, and PCC rule information of all available access systems of the user is reserved in the PCRF. The system structure of embodiment 3 is shown in fig. 7, and the flow of updating the user default bearer is shown in fig. 10. The process comprises the following steps:

step 1001, the user sends a registration request to the MME; step 1002, MME replaces user to carry out authentication and authentication in HSS; step 1003, HSS returns authentication result to MME; step 1004, MME instructs UPE to send a request for establishing bearer to 3GPP Anchor; step 1005, the 3GPP Anchor sends a charging and policy rule request message to the PCRF, where a new access system type and a UE ID are provided; step 1006, the PCRF may locally retrieve corresponding PCC rule information according to the UE ID and the access system type; step 1007, the PCRF generates policy and charging rules and related QoS parameters according to the policy information retrieved locally, and then updates its corresponding policy rules and gateway related information according to the UE ID; step 1008, the PCRF sends a bearer deletion message to the PDG instructing it to delete the default bearer corresponding to the user, where the UE ID is taken down. In addition, a timer can be arranged in the original gateway, and when the timer is overtime, the subsequent deleting operation is carried out to slow down the ping-pong effect; step 1009, PDG and SAE Anchor interactively delete the default bearer in the IWLAN system; step 1010, PDG sends bearer deletion acknowledgement message to PCRF, which is optional; step 1011, the PCRF issues new policy and charging rule related information to the 3GPP Anchor; step 1012, the 3GPP Anchor establishes a default bearer in the SAE system according to the received default bearer QoS parameter; step 1013, establishing a wireless side bearer in the SAE system; step 1014, the MME sends a registration response message to the user; step 1015, MME sends a bearer deletion acknowledgement message to PCRF over UPE, 3GPP Anchor, which is optional; wherein, the steps 1008 to 1010 and the steps 1011 to 1015 have no strict sequence; step 1014 is also not in strict sequence with step 1015.

Example 4

The user moves from the IWLAN system to the SAE system, the gateway in the SAE system is 3GPP Anchor, the gateway in the IWLAN is PDG, and PCRF inquires the PCC rule information of the new access system to SPR each time. The system structure of embodiment 4 is shown in fig. 7, and the flow of updating the user default bearer is shown in fig. 11. The process comprises the following steps:

step 1101, the user sends a registration request to the MME; step 1102, the MME replaces the user to perform authentication in the HSS; step 1103, the HSS returns the authentication result to the MME; step 1104, the MME indicates the UPE to send a request for establishing a bearer to the 3GPP Anchor; step 1105, the 3GPP Anchor sends a charging and policy rule request message to the PCRF, where a new access system type and UE ID are provided; step 1106, the PCRF requests the SPR to obtain PCC rule information of the subscriber in the new access system; step 1107, the PCRF generates policy and charging rules and relevant QoS parameters according to the obtained policy information, and then updates its corresponding policy rules and gateway relevant information according to the UE ID; step 1108, the PCRF sends a bearer deletion message to the PDG instructing it to delete the default bearer corresponding to the user, where the UE ID is taken down. In addition, a timer can be arranged in the original gateway, and when the timer is overtime, the subsequent deleting operation is carried out to slow down the ping-pong effect; step 1109, PDG and SAE Anchor delete the default load in IWLAN system interactively; step 1110, PDG sends bearer deletion acknowledgement message to PCRF, which is optional; step 1111, the PCRF issues new policy and charging rule related information to the 3GPP Anchor; step 1112, the 3gpp ranchor establishes a default bearer in the SAE system according to the received default bearer QoS parameter; step 1113, establish the wireless side bearing in SAE system; step 1114, the MME sends a registration reply message to the user; step 1115, the MME sends a bearer deletion confirmation message to the PCRF through the UPE, 3GPP Anchor, which is optional; wherein, the steps 1108 to 1110 do not have a strict sequence with the steps 1111 to 1115; step 1114 is also not in strict order of sequence with step 1115. The procedure of this embodiment 4 is similar to that of embodiment 3, except that in step 1106, the PCRF requests the SPR to obtain the PCC rule information of the subscriber in the new access system.

Example 5

The user moves from an SAE system to an IWLAN system, a gateway in the SAE system is a 3GPP Anchor, a gateway in the IWLAN is the SAE Anchor, and PCC rule information of all available access systems of the user is reserved in PCRF. The system structure of embodiment 5 is shown in fig. 12, and the flow of updating the user default bearer is shown in fig. 13. The process comprises the following steps:

step 1301, accessing an IWLAN access network by a user; step 1302, the user queries available PDG addresses; step 1303, the user sends a tunnel establishment request to the PDG; step 1304, the PDG replaces the user to send an authentication and authorization request to the HSS/AAAServer; step 1305, HSS/AAA Server authenticates user, and sends result to PDG through authentication response message; step 1306, PDG sends a bearer establishment request to SAE Anchor; step 1307, SAE Anchor sends charging and policy rule request message to PCRF, where new access system type and UE ID are up-carried; step 1308, the PCRF may locally retrieve corresponding PCC rule information according to the UE ID and the access system type; step 1309, the PCRF generates policy and charging rules and relevant QoS parameters according to the policy information retrieved locally, and then updates its corresponding policy rules and gateway relevant information according to the UE ID; step 1310, PCRF sends bearer deletion message to 3GPP Anchor, indicating it to delete the default bearer corresponding to the user, where the UE ID is taken down. In addition, a timer can be set in the 3GPP Anchor, and when the timer is overtime, subsequent deleting operation is carried out to slow down the ping-pong effect; step 1311, 3GPP Anchor, MME, UPE, and EnodeB interact, and delete the default bearer in the SAE system; step 1312, the 3GPP Anchor sends a bearer deletion confirmation message to the PCRF, where the message is optional; step 1313, the PCRF issues new policy and charging rule related information to the SAE Anchor; step 1314, SAE Anchor indicates PDG to establish default bearer in IWLAN system according to received default bearer QoS parameter; step 1315, PDG sends tunnel establishment response message to the user; step 1316, PDG sends bearer deletion confirm message to PCRF through SAE Anchor, the message is optional; wherein, the steps 1310 to 1312 and 1313 to 1316 have no strict sequence; step 1315 is also not in strict order of sequence with step 1316.

Example 6

The user moves from an SAE system to an IWLAN system, a gateway in the SAE system is a 3GPP Anchor, a gateway in the IWLAN is the SAE Anchor, and PCRF inquires PCC rule information of a new access system from SPR each time. The system structure of this embodiment 6 is shown in fig. 12, and the flow of updating the user default bearer is shown in fig. 14. The process comprises the following steps:

step 1401, user accesses IWLAN access network; step 1402, the user queries available PDG addresses; step 1403, the user sends a tunnel establishment request to the PDG; step 1404, PDG sends authentication request to HSS/AAAServer instead of user; step 1405, HSS/AAA Server authenticates user, and sends result to PDG through authentication response message; step 1406, PDG sends bearer establishment request to SAE Anchor; step 1407, SAE Anchor sends charging and policy rule request message to PCRF, where new access system type and UE ID are carried up; step 1408, PCRF requests SPR to obtain PCC rule information of the subscriber in the new access system; step 1409, the PCRF generates the policy and charging rules and the related QoS parameters according to the policy information obtained from the SPR, and then updates the corresponding policy rules and the gateway related information according to the UE ID; step 1410, the PCRF sends a bearer deletion message to the 3GPP Anchor, instructing it to delete the default bearer corresponding to the user, where the UE ID is taken down. In addition, a timer can be set in the 3GPPANCHOR, and when the timer is overtime, subsequent deleting operation is carried out to slow down the ping-pong effect; step 1411, 3GPP Anchor, MME, UPE, EnodeB interact, delete default load in SAE system; step 1412, the 3GPP Anchor sends a bearer deletion confirmation message to the PCRF, where the message is optional; step 1413, the PCRF issues new policy and charging rule related information to SAE Anchor; step 1414, SAE Anchor indicates PDG to establish default bearer in IWLAN system according to received default bearer QoS parameter; step 1415, the PDG sends a tunnel establishment response message to the user; step 1416, the PDG sends a bearer deletion confirmation message to the PCRF over SAE Anchor, which is optional; wherein, the steps 1410 to 1412 and the steps 1413 to 1416 have no strict sequence; step 1415 is also not in strict chronological order with step 1416. The procedure of this embodiment 6 is similar to that of embodiment 5, except that in step 1408, the PCRF requests the SPR to obtain PCC rule information of the subscriber in the new access system.

Example 7

The user moves from the IWLAN system to the SAE system, the gateway in the SAE system is a 3GPP Anchor, the gateway in the IWLAN is an SAE Anchor, and PCC rule information of all available access systems of the user is reserved in the PCRF. The system structure of this example 7 is shown in FIG. 12. The procedure for updating the user default bearer is shown in fig. 15. The process comprises the following steps:

step 1501, the user sends a registration request to the MME; step 1502, the MME replaces the user to perform authentication in HSS; step 1503, the HSS returns the authentication result to the MME; step 1504, the MME instructs the UPE to send a request to establish a bearer to the 3GPP Anchor; step 1505, the 3GPP Anchor sends a charging and policy rule request message to the PCRF, where a new access system type and UE ID are brought up; step 1506, the PCRF may locally retrieve corresponding PCC rule information according to the UE ID and the access system type; step 1507, the PCRF generates policy and charging rules and relevant QoS parameters according to the policy information retrieved locally, and then updates the corresponding policy rules and relevant gateway information according to the UE ID; step 1508, the PCRF sends a bearer deletion message to the saearchor, instructing it to delete the default bearer corresponding to the user, where the ue id is taken down. In addition, a timer can be arranged in the original gateway, and when the timer is overtime, the subsequent deleting operation is carried out to slow down the ping-pong effect; step 1509, SAE Anchor and PDG delete the default bearer in IWLAN system; step 1510, SAE Anchor sends a bearer deletion confirmation message to PCRF, which is optional; 1511, the PCRF issues new policy and charging rule related information to the 3GPP Anchor; step 1512, the 3GPP Anchor establishes a default bearer in the SAE system according to the received default bearer QoS parameter; step 1513, establish the wireless side bearing in SAE system; step 1514, the MME sends a registration reply message to the user; step 1515, MME sends bearer deletion acknowledgement message to PCRF through UPE, 3GPP Anchor, the message is optional; in the above flow, steps 1508 to 1510 and steps 1511 to 1515 do not have a strict sequence; step 1514 is also not in strict chronological order with step 1515.

Example 8

The user moves from the IWLAN system to the SAE system, the gateway in the SAE system is a 3GPP Anchor, the gateway in the IWLAN is the SAE Anchor, and the PCRF inquires the SPR about the PCC rule information of the new access system each time. The system structure of this embodiment 8 is shown in fig. 12, and the flow of updating the user default bearer is shown in fig. 16. The process comprises the following steps:

step 1601, the user sends a registration request to the MME; step 1602, the MME replaces the user to perform authentication in the HSS; step 1603, the HSS returns the authentication result to the MME; step 1604, the MME instructs the UPE to send a request to establish a bearer to the 3GPP Anchor; step 1605, the 3GPP Anchor sends a charging and policy rule request message to the PCRF, wherein a new access system type and a UE ID are provided; step 1606, PCRF requests SPR to obtain PCC rule information of the subscriber in the new access system; step 1607, PCRF generates policy and charging rules and relevant QoS parameters according to the policy information obtained from SPR, and then updates the corresponding policy rules and relevant gateway information according to UEID; step 1608, PCRF sends bearer delete message to SAE Anchor to instruct it to delete the default bearer corresponding to the user, where the UE ID is taken down. In addition, a timer can be arranged in the original gateway, and when the timer is overtime, the subsequent deleting operation is carried out to slow down the ping-pong effect; step 1609, SAE Anchor and PDG delete the default load in IWLAN system; step 1610, SAE Anchor sends a bearer deletion confirmation message to PCRF, where the message is optional; step 1611, the PCRF issues new policy and charging rule related information to the 3GPP Anchor; step 1612, the 3GPP Anchor establishes a default bearer in the SAE system according to the received default bearer QoS parameter; step 1613, establishing a radio side bearer in the SAE system; step 1614, the MME sends a registration response message to the user; step 1615, the MME sends a bearer deletion confirmation message to the PCRF through the UPE and the 3GPP Anchor, where the message is optional; in the above flow, steps 1608 to 1610 and steps 1611 to 1615 are not in strict sequence; step 1614 is not in strict sequence with step 1615. The procedure of this embodiment 8 is similar to that of embodiment 7, except that in step 1606, the PCRF requests to the SPR to obtain the PCC rule information of the subscriber in the new access system.

Example 9

The user moves from SAE system to IWLAN system, the gateway in SAE system and IWLAN is SAEAnchor, and PCRF retains PCC rule information of all available access systems of the user. The system structure of this embodiment 9 is shown in fig. 17, and the flow of updating the user default bearer is shown in fig. 18. The process comprises the following steps:

step 1801, the user accesses the IWLAN access network; step 1802, the user queries available PDG addresses;

step 1803, the user sends a tunnel establishment request to the PDG; step 1804, PDG replaces user to send authentication request to HSS/AAA Server; step 1805, HSS/AAA Server authenticates user, and sends result to PDG through authentication response message; step 1806, PDG sends bearer establishment request to saearchor; step 1807, SAE Anchor sends charging and policy rule request message to PCRF, where new access system type and UE ID are up-loaded; step 1808, the PCRF may retrieve the corresponding PCC rule information locally according to the ue id and the access system type; step 1809, the PCRF generates policy and charging rules and relevant QoS parameters according to the policy information retrieved locally, and then updates its corresponding policy rules and gateway-related information according to the UE ID; step 1810, the PCRF sends a bearer deletion message to the SAE Anchor to instruct it to delete the default bearer corresponding to the user, where the UE ID is taken down. In addition, a timer can be set in the 3GPP Anchor, and when the timer is overtime, subsequent deleting operation is carried out to slow down the ping-pong effect; step 1811, SAE Anchor, 3GPP Anchor, MME, UPE, EnodeB to interact, delete the default load in SAE system; step 1812, the 3GPP Anchor sends a bearer deletion confirmation message to the PCRF through SAE Anchor, and the message is optional; step 1813, PCRF issues new policy and charging rule related information to SAE Anchor; step 1814, SAE Anchor indicates PDG to establish default bearer in IWLAN system according to received default bearer QoS parameter; step 1815, PDG sends tunnel establishment response message to the user; step 1816, PDG sends bearer deletion acknowledgement message to PCRF through SAE Anchor, this message is optional; wherein, the sequence of step 1810 to step 1812 does not have strict sequence with the sequence of step 1813 to step 1816; step 1815 does not have a strict sequence with step 1816.

Example 10

The user moves from SAE system to IWLAN system, the gateway in SAE system and IWLAN is SAEAnchor, PCRF inquires new PCC rule information of access system to SPR each time. The system structure of this embodiment 10 is shown in fig. 17, and the flow of updating the user default bearer is shown in fig. 19, and the flow includes the following steps:

step 1901, the user accesses the IWLAN access network; step 1902, the user queries available PDG addresses; step 1903, the user sends a tunnel establishment request to PDG; step 1904, PDG sends authentication request to HSS/AAAServer instead of user; step 1905, the HSS/AAA Server authenticates the user and sends the result to PDG through the authentication response message; step 1906, PDG sends bearer establishment request to SAE Anchor; step 1907, SAE Anchor sends charging and policy rule request message to PCRF, where new access system type and UE ID are up-loaded; step 1908, the PCRF requests the SPR to obtain PCC rule information of the user in the new access system; step 1909, the PCRF generates policy and charging rules and related QoS parameters according to the policy information obtained from the SPR, and then updates its corresponding policy rules and gateway related information according to the UE ID; step 1910, the PCRF sends a bearer deletion message to the SAE Anchor to instruct it to delete the default bearer corresponding to the user, where the UE ID is taken down. In addition, a timer can be set in the 3GPPANCHOR, and when the timer is overtime, subsequent deleting operation is carried out to slow down the ping-pong effect; step 1911, SAE Anchor, 3GPP Anchor, MME, UPE, EnodeB interact, delete default load in SAE system; step 1912, the 3GPP Anchor sends a bearer deletion confirmation message to the PCRF through the SAE Anchor, where the message is optional; step 1913, the PCRF issues new policy and charging rule related information to the saearchor; step 1914, SAE Anchor indicates PDG to establish default bearer in IWLAN system according to received default bearer QoS parameter; step 1915, PDG sends tunnel establishment response message to user; step 1916, PDG sends bearer deletion confirm message to PCRF through SAE Anchor, where the message is optional; wherein, the steps 1910 to 1912 and the steps 1913 to 1916 have no strict sequence; step 1915 is also not strictly sequential to step 1916. The procedure of this embodiment 10 is similar to that of embodiment 9, except that in step 1908, the PCRF requests the SPR to obtain the PCC rule information of the subscriber in the new access system.

Example 11

The user moves from the IWLAN system to the SAE system, the gateways in the SAE system and the IWLAN are SAEAnchor, and the PCRF reserves the PCC rule information of all the available access systems of the user. The system structure of this embodiment 11 is shown in fig. 17, and the flow of updating the default bearer of the user is shown in fig. 20, and the flow includes the following steps:

step 2001, the user sends a registration request to the MME; step 2002, the MME replaces the user to perform authentication in the HSS; step 2003, HSS returns the authentication result to MME; step 2004, MME indicates UPE to send request for establishing bearing to SAE Anchor through 3GPP Anchor; step 2005, SAE Anchor sends charging and policy rule request message to PCRF, where new access system type and UE ID are brought up; step 2006, the PCRF may retrieve the corresponding PCC rule information locally according to the UE ID and the access system type; step 2007, PCRF generates policy and charging rules and relevant QoS parameters according to the policy information retrieved locally, and then updates the corresponding policy rules and relevant gateway information according to the UE ID; step 2008, PCRF sends a bearer deletion message to SAE Anchor, indicating that it deletes the default bearer corresponding to the user, wherein the UE ID is taken down. In addition, a timer can be arranged in the original gateway, and when the timer is overtime, the subsequent deleting operation is carried out to slow down the ping-pong effect; step 2009, SAE Anchor and PDG delete the default bearer in IWLAN system; step 2010, SAE Anchor sends a bearer deletion confirmation message to PCRF, wherein the message is optional; step 2011, PCRF issues new policy and charging rule related information to SAE Anchor; step 2012, SAE Anchor establishes a default bearer in the SAE system according to the received default bearer QoS parameter; step 2013, establishing a wireless side bearer in the SAE system; step 2014, the MME sends a registration response message to the user; step 2015, MME sends bearer deletion confirmation message to PCRF through UPE, 3GPP Anchor, which is optional; wherein, steps 2008 to 2010 and steps 2011 to 2015 have no strict sequence; step 2014 and step 2015 are not in strict sequence.

Example 12

The user moves from the IWLAN system to the SAE system, the gateways in the SAE system and the IWLAN are SAEAnchor, and the PCRF inquires the SPR about the PCC rule information of the new access system each time. The system structure of this embodiment 12 is shown in fig. 17, and the flow of updating the user default bearer is shown in fig. 21, and the flow includes the following steps:

step 2101, the user sends a registration request to the MME; step 2102, the MME replaces the user to perform authentication in HSS; step 2103, the HSS returns the authentication result to the MME; step 2104, MME instructs UPE to send a request to establish bearer to SAE Anchor through 3GPP Anchor; step 2105, SAE Anchor sends charging and policy rule request message to PCRF, where new access system type and UE ID are up-loaded; step 2106, the PCRF requests the SPR to obtain PCC rule information of the user in the new access system; step 2107, the PCRF generates a policy and charging rule and related QoS parameters according to the policy information obtained from the SPR, and then updates the corresponding policy rule and the related information of the gateway according to the UE ID; step 2108, the PCRF sends a bearer deletion message to the SAE Anchor to instruct it to delete the default bearer corresponding to the user, where the UE ID is taken down. In addition, a timer can be arranged in the original gateway, and when the timer is overtime, the subsequent deleting operation is carried out to slow down the ping-pong effect; step 2109, SAE Anchor and PDG delete the default bearer in IWLAN system interactively; step 2110, SAE Anchor sends a bearer deletion confirmation message to PCRF, and the message is optional; step 2111, PCRF issues new policy and charging rule related information to SAE Anchor; step 2112, SAE Anchor establishes default load in SAE system according to received default load QoS parameter; step 2113, establishing the wireless side bearer in the SAE system; step 2114, the MME sends a registration response message to the user; step 2115, the MME sends a bearer deletion confirmation message to the PCRF through the UPE, 3GPP Anchor, the message being optional; wherein, the steps 2108 to 2110 and the steps 2111 to 2115 have no strict sequence; step 2114 is not in strict sequence with step 2115. The procedure of this embodiment 12 is similar to that of embodiment 11, except that in step 2106, the PCRF requests the SPR to obtain PCC rule information of the subscriber in the new access system.

Example 13

The user moves from SAE system to IWLAN system, the gateway in SAE system is MME, the gateway in IWLAN is PDG, and PCRF keeps PCC rule information of all available access systems of the user. The system configuration of embodiment 13 is shown in fig. 22, and the flow of updating the user default bearer is shown in fig. 23. The process comprises the following steps:

step 2301, the user accesses the IWLAN access network; step 2302, the user queries available PDG addresses; step 2303, the user sends a tunnel establishment request to PDG; step 2304, PDG replaces user to send authentication request to HSS/AAAServer; step 2305, HSS/AAA Server authenticates user, and sends result to PDG through authentication response message; step 2306, PDG sends charging and policy rules request message to PCRF, where new access system type and UE ID are up-loaded; step 2307, the PCRF may retrieve the corresponding PCC rule information locally according to the UE ID and the access system type; step 2308, the PCRF generates policy and charging rules and relevant QoS parameters according to the policy information retrieved locally, and then updates its corresponding policy rules and gateway-related information according to the UE ID; step 2309, the PCRF sends a bearer deletion message to the MME instructing it to delete the default bearer corresponding to the user, where the UE ID is taken down. In addition, a timer can be set in the MME, and when the timer is overtime, subsequent deletion operation is carried out to slow down the ping-pong effect; step 2310, 3GPP Anchor, MME, UPE and EnodeB interact, and delete the default bearer in the SAE system; step 2311, the MME sends a bearer deletion confirmation message to the PCRF, which is optional; step 2312, the PCRF issues new policy and charging rule related information to the PDG; step 2313, the PDG establishes default load in the IWLAN system according to the received default load QoS parameter; step 2314, the PDG sends a tunnel establishment response message to the user; step 2315, the PDG sends a bearer deletion confirmation message to the PCRF, which is optional; wherein, the steps 2309 to 2311 and the steps 2312 to 2315 are not in strict sequence; step 2314 is also not strictly sequential to step 2315.

Example 14

The user moves from SAE system to IWLAN system, the gateway in SAE system is MME, the gateway in IWLAN is PDG, PCRF inquires new PCC rule information of access system to SPR each time. The system architecture of this embodiment 14 is shown in fig. 22, and the flow of updating the user default bearer is shown in fig. 24, and the flow includes the following steps:

step 2401, the user accesses an IWLAN access network; step 2402, the user queries available PDG addresses; step 2403, the user sends a tunnel establishment request to the PDG; step 2404, the PDG replaces the user to send an authentication and authorization request to the HSS/AAAServer; step 2405, HSS/AAA Server authenticates user, and sends result to PDG through authentication response message; step 2406, the PDG sends a charging and policy rules request message to the PCRF, where the new access system type and UE ID are up-loaded; step 2407, the PCRF requests the SPR to obtain PCC rule information of the user in the new access system; step 2408, PCRF generates policy and charging rules and relevant QoS parameters according to the policy information obtained from SPR, and then updates the corresponding policy rules and relevant gateway information according to UEID; step 2409, the PCRF sends a bearer deletion message to the MME instructing it to delete the default bearer corresponding to the user, where the UE ID is taken down. In addition, a timer can be set in the MME, and when the timer is overtime, subsequent deletion operation is carried out to slow down the ping-pong effect; step 2410, interacting 3GPP Anchor, MME, UPE and EnodeB, and deleting default load in the SAE system; step 2411, the MME sends a bearer deletion confirmation message to the PCRF, wherein the message is optional; step 2412, the PCRF issues new policy and charging rule related information to the PDG; step 2413, PDG establishes default load in IWLAN system according to received default load QoS parameter; step 2414, the PDG sends a tunnel establishment response message to the user; step 2415, the PDG sends a bearer deletion confirmation message to the PCRF, which is optional; wherein, the sequence of the steps 2409 to 2411 and the sequence of the steps 2412 to 2415 are not strict; step 2414 does not have a strict sequence with step 2415. As can be seen from the above steps, the procedure of this embodiment 14 is similar to that of embodiment 13, except that in step 2407, the PCRF requests the SPR to obtain the PCC rule information of the subscriber in the new access system.

Example 15

The user moves from the IWLAN system to the SAE system, the gateway in the SAE system is MME, the gateway in the IWLAN is PDG, and PCC rule information of all available access systems of the user is reserved in PCRF. The system architecture of this embodiment 15 is shown in fig. 22, and the flow of updating the user default bearer is shown in fig. 25, and the flow includes the following steps:

step 2501, the user sends a registration request to the MME; step 2502, the MME replaces the user to perform authentication in HSS; step 2503, the HSS returns the authentication result to the MME; step 2504, MME sends charging and policy rules request message to PCRF, where new access system type and UE ID are up-loaded; step 2505, the PCRF may locally retrieve corresponding PCC rule information according to the UE ID and the access system type; step 2506, the PCRF generates policy and charging rules and relevant QoS parameters according to the policy information retrieved locally, and then updates its corresponding policy rules and gateway-related information according to the UE ID; step 2507, PCRF sends bearer deletion message to PDG, instructing it to delete the default bearer corresponding to the user, where the lower band UE ID. In addition, a timer can be arranged in the original gateway, and when the timer is overtime, the subsequent deleting operation is carried out to slow down the ping-pong effect; step 2508, PDG and SAE Anchor delete the default bearer in the IWLAN system interactively; step 2509, PDG sends bearer deletion confirmation message to PCRF, which is optional; step 2510, the PCRF issues new policy and charging rule related information to the MME; step 2511, the MME establishes a default bearer in the SAE system according to the received default bearer QoS parameters; step 2512, establishing a wireless side bearer in the SAE system; step 2513, the MME sends a registration response message to the user; step 2514, the MME sends a bearer deletion acknowledgement message to the PCRF, which is optional; wherein, steps 2507 to 2509 do not have a strict sequence with steps 2510 to 2514; step 2513 is also not in strict chronological order with step 2514.

Example 16

The user moves from the IWLAN system to the SAE system, the gateway in the SAE system is MME, the gateway in the IWLAN is PDG, and the PCRF queries the SPR for the PCC rule information of the new access system each time. The system configuration of this embodiment 16 is shown in fig. 22, and the flow of updating the user default bearer is shown in fig. 26, and the flow includes the following steps:

step 2601, the user sends a registration request to the MME; step 2602, the MME replaces the user to perform authentication in the HSS; step 2603, the HSS returns the authentication result to the MME; step 2604, MME sends charging and policy rules request message to PCRF, where new access system type and UE ID are up-loaded; step 2605, the PCRF requests the SPR to obtain PCC rule information of the user in the new access system; step 2606, the PCRF generates policy and charging rules and relevant QoS parameters according to the policy information obtained from the SPR, and then updates its corresponding policy rules and gateway-related information according to the UE ID; step 2607, PCRF sends bearer deletion message to PDG to instruct it to delete the default bearer corresponding to the user, where the ue id is taken down. In addition, a timer can be arranged in the original gateway, and when the timer is overtime, the subsequent deleting operation is carried out to slow down the ping-pong effect; step 2608, PDG and SAE Anchor delete the default bearer in IWLAN system interactively; step 2609, PDG sends bearer deletion confirmation message to PCRF, which is optional; step 2610, PCRF issues new policy and charging rule related information to MME; step 2611, MME sets up default load in SAE system according to default load QoS parameter received; step 2612, establish the wireless side bearing in the SAE system; step 2613, MME sends registration response message to user; step 2614, the MME sends a bearer deletion confirmation message to the PCRF, which is optional; wherein, the sequence of the steps 2607 to 2609 and the sequence of the steps 2610 to 2614 are not strict; step 2613 is also not in strict order of sequence with step 2614. The procedure of this embodiment 16 is similar to that of embodiment 15, except that in step 2605, the PCRF requests the SPR to obtain the PCC rule information of the subscriber in the new access system.

Example 17

The user moves from an SAE system to an IWLAN system, a gateway in the SAE system is MME, a gateway in the IWLAN is SAE Anchor, and PCC rule information of all available access systems of the user is reserved in PCRF. The system structure is shown in fig. 27, and the flow for updating the default bearer of the user is shown in fig. 28, and the flow includes the following steps:

step 2801, the user accesses the IWLAN access network; step 2802, the user queries available PDG addresses; step 2803, the user sends a tunnel establishment request to PDG; step 2804, PDG replaces user to send authentication request to HSS/AAAServer; step 2805, the HSS/AAA Server authenticates the user and sends the result to PDG through authentication response message; step 2806, PDG sends bearer establishment request to SAE Anchor; step 2807, SAE Anchor sends charging and policy rule request message to PCRF, where new access system type and UE ID are up-loaded; step 2808, the PCRF may retrieve the corresponding PCC rule information locally according to the UE ID and the access system type; step 2809, PCRF generates policy and charging rules and relevant QoS parameters according to the policy information retrieved locally, and then updates its corresponding policy rules and gateway relevant information according to the UE ID; step 2810, PCRF sends bearer deletion message to MME, instructing it to delete the default bearer corresponding to the user, where the UE ID is taken down. In addition, a timer can be set in the MME, and when the timer is overtime, subsequent deletion operation is carried out to slow down the ping-pong effect; step 2811, 3GPP Anchor, MME, UPE and EnodeB interact, and delete the default bearer in the SAE system; step 2812, the MME sends a bearer deletion confirmation message to the PCRF, which is optional; PCRF issues new policy and charging rule related information to SAE Anchor; step 2813, SAE Anchor indicates PDG to establish default bearer in IWLAN system according to received default bearer QoS parameter; step 2814, PDG sends a tunnel establishment response message to the user; step 2815, PDG sends bearer deletion confirm message to PCRF through SAE Anchor, which is optional; wherein, steps 2810 to 2812 and steps 2813 to 2816 have no strict sequence; step 2815 and step 2816 are also not in strict sequence.

Example 18

The user moves from an SAE system to an IWLAN system, a gateway in the SAE system is MME, a gateway in the IWLAN is SAE Anchor, and PCRF queries SPR to inquire PCC rule information of a new access system each time. The system configuration of this embodiment 18 is shown in fig. 27, and the flow of updating the user default bearer is shown in fig. 29, and the flow includes the following steps:

step 2901, the user accesses the IWLAN access network; step 2902, the user queries available PDG addresses; step 2903, the user sends a tunnel establishment request to PDG; step 2904, PDG replaces user to send authentication request to HSS/AAAServer; step 2905, HSS/AAA Server authenticates user, and sends result to PDG through authentication response message; step 2906, the PDG sends a bearer establishment request to the SAE Anchor; step 2907, SAE Anchor sends charging and policy rule request message to PCRF, where new access system type and UE ID are up-loaded; step 2908, the PCRF requests the SPR to obtain PCC rule information of the user in the new access system; step 2909, the PCRF generates policy and charging rules and relevant QoS parameters according to the policy information obtained from the SPR, and then updates its corresponding policy rules and gateway-related information according to the UE ID; step 2910, PCRF sends bearer deletion message to MME instructing it to delete default bearer corresponding to the user, where UE ID is taken down. In addition, a timer can be set in the MME, and when the timer is overtime, subsequent deletion operation is carried out to slow down the ping-pong effect; step 2911, 3GPP Anchor, MME, UPE, EnodeB interact, delete default bearer in SAE system; step 2912, the MME sends a bearer deletion confirmation message to the PCRF, which is optional; PCRF issues new policy and charging rule related information to SAE Anchor; step 2913, SAE Anchor instructs PDG to establish default bearer in IWLAN system according to received default bearer QoS parameter; step 2914, PDG sends a tunnel establishment response message to the user; step 2915, PDG sends bearer deletion confirm message to PCRF over SAE Anchor, which is optional; wherein, steps 2910 to 2912 and steps 2913 to 2916 have no strict sequence; step 2915 and step 2916 also do not have a strict sequence. The procedure of this embodiment 18 is similar to that of embodiment 17, except that in step 2908, the PCRF requests the SPR to obtain the PCC rule information of the subscriber in the new access system.

Example 19

The user moves from the IWLAN system to the SAE system, the gateway in the SAE system is MME, the gateway in the IWLAN is SAE Anchor, and the PCRF keeps PCC rule information of all available access systems of the user. The system configuration of this embodiment is shown in fig. 27, and the flow of updating the user default bearer is shown in fig. 30. The process comprises the following steps:

step 3001, the user sends a registration request to the MME; step 3002, the MME replaces the user to perform authentication in HSS; step 3003, the HSS returns the authentication result to the MME; step 3004, MME sends charging and policy rules request message to PCRF, where new access system type and UE ID are up-loaded; step 3005, the PCRF may locally retrieve the corresponding PCC rule information according to the UE ID and the access system type; step 3006, the PCRF generates policy and charging rules and related QoS parameters according to the policy information retrieved locally, and then updates its corresponding policy rules and gateway related information according to the UE ID; step 3007, the PCRF sends a bearer deletion message to the SAE Anchor to instruct it to delete the default bearer corresponding to the user, where the UE ID is taken down. In addition, a timer can be arranged in the original gateway, and when the timer is overtime, the subsequent deleting operation is carried out to slow down the ping-pong effect; step 3008, SAE Anchor and PDG delete default bearer in IWLAN system interactively; step 3009, SAE Anchor sends bearer deletion confirm message to PCRF, which is optional; step 3010, PCRF issues new policy and charging rule related information to MME; step 3011, MME interacts with UPE and 3GPP Anchor according to received default bearer QoS parameter to establish default bearer in SAE system; step 3012, establish the wireless side bearer in the SAE system; step 3013, MME sends registration reply message to user; step 3014, MME sends bearer deletion confirm message to PCRF, which is optional; wherein, steps 3007 to 3009 do not have a strict sequence with steps 3010 to 3014; step 3013 is not strictly sequential to step 3014.

Example 20

The user moves from the IWLAN system to the SAE system, the gateway in the SAE system is MME, the gateway in the IWLAN is SAE Anchor, and PCRF queries SPR to inquire PCC rule information of a new access system each time. The system configuration of this embodiment is shown in fig. 27, and the flow of updating the user default bearer is shown in fig. 31. The process comprises the following steps:

step 3101, the user sends a registration request to the MME; step 3102, the MME replaces the user to authenticate in HSS; step 3103, HSS returns the authentication result to MME; step 3104, the MME sends a charging and policy rules request message to the PCRF, where the new access system type and UE ID are brought up; step 3105, the PCRF may locally retrieve corresponding PCC rule information according to the UE ID and the access system type; step 3106, the PCRF generates policy and charging rules and relevant QoS parameters according to the locally retrieved policy information, and then updates its corresponding policy rules and gateway-related information according to the UE ID; step 3107, PCRF sends bearer delete message to SAE Anchor to instruct it to delete the default bearer corresponding to the user, where the UE ID is taken down. In addition, a timer can be arranged in the original gateway, and when the timer is overtime, the subsequent deleting operation is carried out to slow down the ping-pong effect; step 3108, SAE Anchor and PDG delete the default bearer in IWLAN system interactively; step 3109, SAE Anchor sends bearer deletion confirm message to PCRF, which is optional; step 3110, the PCRF issues new policy and charging rule related information to the MME; step 3111, the MME establishes a default bearer in the SAE system according to the received default bearer QoS parameter and the interaction with UPE and 3GPP Anchor; step 3112, establishing a radio side bearer in the SAE system; step 3113, the MME sends a registration response message to the user; step 3114, the MME sends a bearer deletion confirmation message to the PCRF, where the message is optional; wherein, steps 3107 to 3109 do not have a strict sequence with steps 3110 to 3114; step 3113 is also not in strict sequence with step 3114. The procedure of this embodiment is similar to embodiment 19, except that in step 5, the PCRF requests the SPR to obtain the PCC rule information of the subscriber in the new access system.

The technical scheme of the invention has the following beneficial effects: the invention realizes the scheme of managing the default load of the user moving between different IP connection access systems and in idle state by utilizing and expanding the related entities and processes in the PCC. By the scheme, the default bearer management when the user moves among different access technologies in the whole SAE system is realized, so that the user can obtain the default bearer in the whole SAE system (only accessed from a 3GPP access system or accessed from a non-3 GPP system), and the capability of always-on is obtained.

The foregoing detailed description is, therefore, to be construed as merely illustrative, and not a limitation of the invention.

Claims (20)

1. A management method of default load establishing parameter is characterized in that when a user moves between two different access systems, a policy and charging control function entity is adopted to manage the default load; wherein,

the policy and charging control function entity receives the charging and policy rule request carrying the user identification information, updates the charging and policy rule according to the user identification information, and then sends out the updated charging and policy rule.

2. The method as claimed in claim 1, wherein the policy and charging control function entity receiving the charging and policy rules request carrying the subscriber identity information is:

the policy and charging control function entity receives a charging and policy rules request with a user ID from the gateway.

3. The method of claim 2, wherein the policy and charging control function entity records the user ID and the gateway ID.

4. The method of claim 2 wherein the charging and policy rules request further includes access system type information.

5. The method as claimed in claim 4, wherein the control and charging policy rule information corresponding to the access system type information is stored in a policy and charging control function entity, and the policy and charging control function entity locally retrieves the corresponding control and charging policy rule information according to the user ID and the access system type information.

6. The method as claimed in claim 4, wherein the policy and charging control function entity sends a policy request to a subscription profile base, the policy request has access system type information and a user ID, the subscription profile base retrieves corresponding policy rule information according to the access system type information and the user ID, and sends the policy rule information to the policy and charging control function entity.

7. The method as claimed in claim 5, wherein said updating charging and policy rules based on said subscriber identity information comprises: the strategy and charging control function entity generates strategy and charging rules and related service quality parameters according to the strategy information retrieved locally, and then updates the strategy rules corresponding to the user ID and the related information of the gateway according to the user ID.

8. The method as claimed in claim 6, wherein said updating charging and policy rules based on said subscriber identity information comprises: the strategy and charging control function entity generates strategy and charging rules and related service quality parameters according to the strategy information received from the signed specification base, and then updates the strategy rules corresponding to the user ID and the related information of the gateway according to the user ID.

9. The method of claim 7 or 8, further comprising:

the strategy and charging control function entity sends bearing deleting information with user ID to the original gateway, and the bearing deleting information is used for indicating the original gateway to delete the default bearing corresponding to the user;

the original gateway initiates deletion of default load in the original system;

the strategy and charging control function entity sends new strategy and charging regulation related information to a new gateway;

the new gateway establishes a default bearer in the new system based on the received default bearer QoS parameters.

10. The method of claim 2, wherein said access system comprises: a system architecture evolution system and a wireless local area internet system;

the gateway is a mobility management entity or a 3GPP anchor point or a system architecture evolution anchor point for a system architecture evolution system;

the gateway is a packet data gateway or a system architecture evolution anchor point for the wireless local area internet system;

the gateway is also used for executing policy and charging.

11. A system for managing default bearer establishment parameters, comprising: user equipment, an access system and a core network; the method is characterized by comprising the following steps: a policy and charging control function entity; the user equipment is connected with the core network through the access system, and the policy and charging control function entity is connected with the core network; wherein,

the user equipment is used for moving between two different access systems;

the policy and charging control function entity is used for receiving the charging and policy rule request carrying the user identification information, updating the charging and policy rule according to the user identification information, and then sending the updated charging and policy rule.

12. The system of claim 11, comprising: and the gateway sends a charging and policy rule request with a user ID to the policy and charging control function entity.

13. The system of claim 12 wherein said policy and charging control function records said user ID and said gateway ID.

14. The system of claim 12 wherein the charging and policy rules request further includes access system type information.

15. The system of claim 14, wherein the control and charging policy rule information corresponding to the access system type information is stored in a policy and charging control function entity, and the policy and charging control function entity locally retrieves the corresponding control and charging policy rule information based on the user ID and the access system type information.

16. The system of claim 14, comprising: the said signing specification base searches the corresponding strategy rule information according to the said access system type information and user ID, and sends the strategy rule information to the said strategy and charging control function entity.

17. The system of claim 15, wherein said updating charging and policy rules based on said subscriber identity information comprises: the strategy and charging control function entity generates strategy and charging rules and related service quality parameters according to the strategy information retrieved locally, and then updates the strategy rules corresponding to the user ID and the related information of the gateway according to the user ID.

18. The system of claim 16, wherein said updating charging and policy rules based on said subscriber identity information comprises: the strategy and charging control function entity generates strategy and charging rules and related service quality parameters according to the strategy information received from the signed specification base, and then updates the strategy rules corresponding to the user ID and the related information of the gateway according to the user ID.

19. The system according to claim 17 or 18, wherein said gateway comprises: an original gateway and a new gateway, wherein:

the strategy and charging control function entity sends bearing deletion information with user ID to the original gateway, and the bearing deletion information is used for indicating the original gateway to delete the default bearing corresponding to the user equipment;

the original gateway initiates deletion of default load in the original system;

the strategy and charging control function entity sends new strategy and charging regulation related information to a new gateway;

the new gateway establishes a default bearer in the new system based on the received default bearer QoS parameters.

20. The system of claim 12, wherein said access system comprises: a system architecture evolution system and a wireless local area internet system;

the gateway is a mobility management entity or a 3GPP anchor point or a system architecture evolution anchor point for a system architecture evolution system;

the gateway is a packet data gateway or a system architecture evolution anchor point for the wireless local area internet system; the gateway comprises a policy and charging execution function entity for executing policy and charging.

Images