WO2012146129A1

WO2012146129A1 - Bearer management method, system and anchor point supporting multiple access

Info

Publication number: WO2012146129A1
Application number: PCT/CN2012/073839
Authority: WO
Inventors: 卢飞; 梁爽; 宗在峰; 周晓云
Original assignee: 中兴通讯股份有限公司
Priority date: 2011-04-28
Filing date: 2012-04-11
Publication date: 2012-11-01
Also published as: CN102761958A; CN102761958B

Abstract

Disclosed is a bearer management method supporting multiple access. An anchor point determines a radio access technology (RAT) type for bearer setup or update in a bearer management procedure, and notifies the RAT type to a core network gateway in a bearer setup or update procedure. Also disclosed are a bearer management system and an anchor point supporting multiple access. Through the solutions of the present invention, the core network gateway can acquire an RAT type of a bearer and perform accurate differentiated charging according to the RAT type, so as to avoid the problem of inaccurate charging.

Description

Bearer management method, system and anchor point supporting multiple access

The present invention relates to bearer management technologies in the field of mobile communications, and in particular, to a bearer management method, system and anchor point supporting multiple access. Background technique

In the field of mobile communications, Evolved Packet System (EPS) and General Packet Radio Service (GPRS) networks are gradually evolving. The EPS mainly includes the Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and the Evolved Packet Core (EPC). The system's EPC is capable of supporting users' access from the GSM EDGE Radio Access Network (GERAN) and the Universal Terrestrial Radio Access Network (UTRAN).

In the EPC packet core network, it includes a Home Subscriber Server (HSS), a Mobility Management Entity (MME), a Serving Gateway (SGW), and a Packet Data Network Gateway (PGW, PDN). Gateway), Serving GPRS Support Node (SGSN) and Policy and Charging Enforcement Function (PCRF) entities, where:

The HSS/Home Location Register (HLR) is the permanent storage location for user subscription data. It is located in the home network to which the subscriber is contracted and is the primary user database supporting the call/session.

The MME is the location where the subscriber subscription data is stored in the current network, and is responsible for the non-access stratum (NAS, Non-Access Stratum) signaling management of the user equipment (UE) to the network, and the tracking and paging management functions and bearers in the user idle mode. management; The SGW is the gateway of the core network to the wireless system, and is responsible for the user plane bearer of the UE to the core network.

Data caching in UE idle mode, function of initiating service request on the network side, lawful interception, and packet data routing and forwarding functions;

The PGW is the gateway of the EPS and the external network of the system, and is responsible for the functions of the UE's IP address allocation, billing function, packet filtering, and policy application.

The SGSN is a service support point for GERAN and UTRAN users to access the EPC network. The specific functions are similar to those of the MME. They are responsible for the location update, paging management, and bearer management functions of the UE.

The GPRS Gateway Support Node (GGSN) supports the edge routing function of the GPRS network. That is, the GGSN is responsible for routing and forwarding data of the GPRS network, and protecting the integrity of the GPRS network data through the firewall and filtering functions. In addition, the GGSN also has a billing function.

The PGW may include all the functions of the GGSN, and the GGSN may be considered as a sub-function of the PGW and embedded in the PGW. Therefore, the SGSN can connect directly to the PGW and use the Gn/Gp interface.

Dual-mode or tri-mode UEs can access the network through GERAN/UTRAN/EUTRAN, and need to register separately when accessing different networks.

In the early stage of LTE introduction, most of the UEs are multi-mode but single-accessed UEs due to the interference of the wireless spectrum. This causes the UE to perform services only on one network at a time, or even register on one network. Waste of regional wireless resources covered by multiple radio access technologies (RATs) simultaneously. With the development of technology, the wireless interference problem is no longer an important obstacle to the development of dual-mode UE. Operators and equipment vendors are studying how to support dual-mode UEs to simultaneously access different networks and receive services at the same time. The system architecture shown in Figures 1 and 2 can support the UE to access and register at multiple RATs at the same time. As shown in FIG. 1 , the UE simultaneously aggregates to the SGW-PGW through the Radio Network Controller (RNC)-SGSN and the eNodeB-MME access; as shown in FIG. 2, the UE simultaneously accesses and aggregates to the RNC through the NodeB and the eNodeB, and The RNC is directly connected to the SGSN-SGW-PGW. Both the SGW and the PGW can perform differential charging according to different RAT types. Since the current single access system does not have multiple RATs of the UE and different RAT types, it does not appear in bearer management such as bearer establishment and modification. In the process, the gateway does not know the RAT type of the bearer. However, in a multiple access system, multiple bearers of a UE will have different RAT types. In the process of bearer management such as bearer establishment and modification, the current gateway cannot know the RAT type of the bearer, and thus cannot accurately perform the UE. Differential billing, billing is not accurate. Summary of the invention

In view of this, the main purpose of the present invention is to provide a bearer management method, system, and anchor point that support multiple access, so that the core network gateway knows the RAT type of the bearer, and performs accurate differential charging according to the RAT type.

In order to achieve the above object, the technical solution of the present invention is achieved as follows:

The present invention provides a bearer management method for supporting multiple access, the method includes: in a bearer management process, an anchor point determines a RAT type that a bearer establishes or updates, and in a bearer setup or update process, the RAT type Notify the core network gateway.

In the above solution, the anchor point determines that the RAT type of the bearer establishment or update is: the anchor point determines the RAT type of the bearer establishment or update according to the preset local policy.

In the above solution, the local policy is based on radio base station signal quality and/or radio base station load. In the foregoing solution, in the process of establishing or updating a bearer, the RAT type is notified to the core network gateway, that is: in the process of establishing or updating, the anchor point is carried in a bearer setup response message returned to the core network gateway. The RAT type, or the bearer update response message returned to the core network gateway, carries the RAT type, or carries the RAT type in the Radio Access Bearer (RAB) assignment response message sent to the core network gateway.

In the foregoing solution, the method further includes: the core network gateway performing differential charging according to the type of the RAT carried.

The invention provides a bearer management system supporting multiple access, the system comprising: an anchor point, Core network gateway; among them,

The anchor point is used to determine a RAT type of a bearer establishment or update in a bearer management process, and notify the core network gateway of the RAT type in a bearer setup or update process;

The core network gateway is configured to obtain a RAT type of the bearer.

In the above solution, the anchor point includes: a RAT type determining module, a notification module, where the RAT type determining module is configured to determine, in the bearer management process, a RAT type that is established or updated by the bearer;

The notification module is configured to notify the core network gateway of the RAT type determined by the RAT type determining module during the bearer setup or update process.

In the foregoing solution, the RAT type determining module is specifically configured to determine, according to a preset local policy, a RAT type that is established or updated by the bearer in the bearer management process.

In the above solution, the notification module is specifically configured to carry the RAT type in the bearer setup response message returned to the core network gateway in the bearer setup or update process, or in the bearer update response message returned to the core network gateway. The RAT type is carried in the RAB assignment response message carrying the RAT type or in the core network gateway.

In the above solution, the core network gateway is further configured to perform differential charging according to the RAT type of the bearer.

An anchor point provided by the present invention includes: a RAT type determining module and a notification module; wherein

a RAT type determining module, configured to determine, in a bearer management process, a RAT type of a bearer establishment or update;

The invention provides a bearer management method, system and anchor point supporting multiple access. In the bearer management process, the anchor point determines the RAT type of the bearer establishment or update, and is established in the bearer or During the update process, the RAT type is notified to the core network gateway. In this way, the core network gateway can learn the RAT type of the bearer, and can perform accurate differential charging according to the RAT type to avoid the problem of inaccurate charging. DRAWINGS

1 is a system architecture for supporting UEs to access and register at multiple RATs simultaneously in the prior art;

2 is another system architecture for supporting UEs to access and register simultaneously in multiple RATs in the prior art;

3 is a schematic flowchart of a bearer management method for supporting multiple access according to the present invention; FIG. 4 is a schematic structural diagram of a bearer management system supporting multiple access according to the present invention; FIG. FIG. 6 is a schematic flowchart of a method for implementing bearer management for supporting multiple access according to Embodiment 2 of the present invention; FIG. 7 is a schematic diagram of a bearer management method for supporting multiple access according to Embodiment 3 of the present invention; FIG. 8 is a schematic flowchart of a bearer management method for supporting multiple access according to Embodiment 4 of the present invention. detailed description

The basic idea of the present invention is: In the bearer management process, the anchor point determines the RAT type of the bearer establishment or update, and notifies the core network gateway of the RAT type in the bearer setup or update process.

Here, the anchor point is used to aggregate network elements of each RAT type in a multiple access system, as shown in the figure.

SGW in 1 , RNC in Figure 2, etc.;

The RAT type includes: an LTE system, a GERAN system, a UTRAN system, and the like.

The invention will be further described in detail below with reference to the drawings and specific embodiments.

The present invention implements a bearer management method supporting multiple access. As shown in FIG. 3, the method includes the following steps: Step 101: In the bearer management process, the anchor point determines the RAT type that the bearer establishes or updates;

Specifically, in the bearer management process, the anchor point determines the RAT type of the bearer establishment or update according to the preset local policy; the local policy is based on the signal quality of the radio base station and/or the load of the radio base station; for example, the local policy is selected. The radio base station has the best signal quality, and/or the RAT type with the lightest load on the radio base station establishes or updates the bearer.

Step 102: The anchor point notifies the core network gateway of the RAT type during the bearer setup or update process;

Specifically, in the bearer setup or update process, the anchor point carries the RAT type in the bearer setup response message returned to the core network gateway, or carries the RAT type in the bearer update response message returned to the core network gateway, or The RAB assignment response message sent to the core network gateway carries the RAT type and the like.

The carrying may be to add a field indicating the RAT type or an identifier indicating the RAT type in the message body, such as the identifier L indicates the LTE system, the identifier G indicates the GERAN system, the identifier U indicates the UTRAN system, and the like.

Further, the foregoing method further includes the step 103: the core network gateway performs differential charging according to the RAT type of the bearer, for example, the core network gateway performs different standard charging for the LTE system, the UTRAN, and the GERAN system.

In order to implement the foregoing method, the present invention further provides a bearer management system supporting multiple access. As shown in FIG. 4, the system includes: an anchor point 41, and a core network gateway 42;

The anchor point 41 is configured to determine, in a bearer management process, a RAT type that is established or updated by a bearer, and notify the core network gateway 42 of the RAT type in a bearer setup or update process; Obtaining a RAT type of the bearer according to the notification of the anchor point 41;

The anchor point 41 includes: a RAT type determining module 411, a notification module 412; a RAT type determining module 411, configured to determine, in a bearer management process, a RAT type of a bearer establishment or update;

The notification module 412 is configured to notify the core network gateway 42 of the RAT type determined by the RAT type determining module 411 during the bearer setup or update process;

The RAT type determining module 411 is specifically configured to determine, according to a preset local policy, a RAT type of a bearer establishment or update in a bearer management process;

The notification module 412 is specifically configured to carry the RAT type in the bearer setup response message returned to the core network gateway 42 or carry the bearer update response message returned to the core network gateway 42 in the bearer setup or update process. The RAT type, or the RAB assignment response message sent to the core network gateway 42 carries the RAT type and the like;

The core network gateway 42 is further configured to perform differential charging according to the type of the RAT of the bearer. The present invention also provides an anchor point. As shown in FIG. 4, the anchor point 41 includes: a RAT type determining module 411, a notification module 412, where

The RAT type determining module 411 is configured to determine, in the bearer management process, a RAT type that is established or updated by the bearer;

The notification module 412 is specifically configured to carry the RAT type in the bearer setup response message returned to the core network gateway 42 or carry the bearer update response message returned to the core network gateway 42 in the bearer setup or update process. The RAT type, or the RAB assignment response message sent to the core network gateway 42, carries the RAT type and the like. Embodiment 1: This embodiment is based on the system architecture shown in FIG. 1 , and the SGW is used as an anchor point to implement a bearer management method supporting multiple access. As shown in FIG. 5 , the method includes the following steps:

Step 501: The PGW sends a bearer setup request message to the SGW, where the message carries the uplink user plane IP address of the PGW and the tunnel endpoint identifier (TEID, Tunnel Endpoint Identifier). Step 502: The SGW receives the bearer setup request message, and determines according to the local policy. The bearer established RAT type is an LTE system, and the SGW sends a bearer setup request message to the MME, and carries the uplink user plane IP address and TEID of the PGW, the uplink user plane IP address and the TEID of the SGW;

Step 503: The MME receives the bearer setup request message of the SGW, establishes a bearer and allocates an EPS bearer identifier (EBI, EPS Bearer ID), and the MME establishes a session management request message, where the message carries the EBI and the quality of service (QoS, Quality of Service) And the MME sends a bearer setup request message to the eNodeB, where the message carries the session management request message, the EBI, the bearer QoS, the uplink user plane IP address of the SGW, and the TEID;

Step 504: The eNodeB receives the bearer setup request message of the MME, and sends a radio resource connection (RRC) reconfiguration message to the UE, where the message carries the radio bearer QoS, the radio bearer ID, and the session management request message.

Step 505: The UE returns an RRC reconfiguration complete message to the eNodeB.

Step 506: The eNodeB returns a bearer setup response message to the MME, where the message carries the bearer ID, the downlink IP address of the eNodeB, and the TEID.

Step 507, the UE non-access stratum establishes a session management response message, and delivers the message to the eNodeB through a direct transmission message;

Step 508: The eNodeB delivers the session management message to the MME by using the uplink direct transmission message. Step 509: The MME returns a bearer setup response message to the SGW, where the message carries the downlink IP address and TEID of the EBI and the eNodeB.

Step 510: The SGW returns a bearer setup response message to the PGW, where the message carries the EBI, The downlink IP address and TEID of the SGW, and the RAT type;

Here, the RAT type is a LET system.

Step 511: The PGW learns the RAT type of the bearer according to the bearer setup response message returned by the SGW.

In step 502, if the SGW determines that the RAT type of the bearer establishment is a UTRAN or GERAN system, the method for establishing a bearer in the UTRAN system or the GERAN system is similar to the foregoing method, and details are not described herein again.

Embodiment 2:

This embodiment is based on the system architecture shown in FIG. 1, and the SGW is used as an anchor point to implement a bearer management method supporting multiple access. As shown in FIG. 6, the method includes the following steps:

Step 601: The PGW sends a bearer update request to the SGW.

Step 602: The SGW receives the bearer update request, and determines that the RAT type of the bearer update is an LTE system according to the local policy, that is, the bearer is migrated from the UTRAN system or the GERAN system to the LTE system, and the SGW sends a bearer setup request message to the MME, where the message carries The upstream user plane IP address and TEID of the PGW, the uplink user plane IP address of the SGW, and the TEID;

Step 603: The MME receives the bearer setup request message of the SGW, establishes a bearer and allocates an EBI, and the MME establishes a session management request message, where the message carries the EBI, the QoS, and the MME, and sends a bearer setup request message to the eNodeB, where the message carries the session management. Request message, EBI, bearer QoS, uplink user plane IP address and TEID of the SGW;

Step 604: The eNodeB receives the MME reconfiguration request message, and sends an RRC reconfiguration message to the UE, where the message carries the radio bearer QoS, the radio bearer ID, and the session management request elimination step 605, and the UE returns an RRC reconfiguration complete message to the eNodeB.

Step 606: The eNodeB returns a bearer setup response message to the MME, where the message carries the bearer ID, the downlink IP address of the eNodeB, and the TEID. Step 607: The UE non-access stratum establishes a session management response message, and delivers the message to the eNodeB through the uplink direct transmission message.

Step 608: The eNodeB delivers the session management message to the MME by using the uplink direct transmission message. Step 609: The MME returns a bearer setup response message to the SGW, where the message carries the downlink IP address and TEID of the EBI and the eNodeB.

Step 610: The SGW returns a bearer update response message to the PGW, where the message carries a RAT type.

Here, the RAT type is an LTE system.

In the foregoing steps, if there is no step 601 in the bearer update process, the SGW may notify the PGW of the RAT type by using other messages returned to the PGW in step 610;

In this embodiment, because the SGW decides to migrate the UTRAN or the GERAN system to the LTE system, the SGW also needs to release the processing of the bearer of the UTRAN or the GERAN system, and the specific steps include steps 611-616;

Step 611: The SGW sends a bearer release request to the SGSN.

Step 612: The SGSN sends an RAB assignment request message for requesting the RNC to release the bearer to the RNC.

Step 613: After receiving the RAB assignment request message, the RNC sends a radio bearer release request message to the UE.

Step 614: After receiving the radio bearer release request message, the UE sends a radio bearer release response message to the RNC.

Step 615: The RNC returns an RAB assignment response message to the SGSN.

Step 616: The SGSN returns a release response message to the SGW.

In step 602, if the SGW determines that the RAT type of the bearer update is a UTRAN or GERAN system, and the bearer is to be migrated from the LTE system to the UTRAN or GERAN system, the method of updating the bearer to the UTRAN or GERAN system is similar to the above method, and is no longer Narration. Embodiment 3:

This embodiment is based on the system architecture shown in FIG. 2, and the RNC is used as an anchor point to implement a bearer management method supporting multiple access. As shown in FIG. 7, the method includes the following steps:

Step 701: The PGW sends a bearer setup request message to the SGW, where the message carries the uplink user plane IP address and the TEID of the PGW.

Step 702: The SGW receives the bearer setup request message, and sends a bearer setup request message to the SGSN, where the message carries the uplink user plane IP address of the PGW, the TEID, the uplink user plane IP address of the SGW, and the TEID.

Step 703: After receiving the bearer setup request message, the SGSN sends an RAB assignment request message to the RNC, where the message carries the uplink user plane IP address and TEID of the SGSN.

Step 704: After receiving the bearer setup request message of the SGSN, the RNC determines, according to the local policy, that the RAT type of the bearer setup is the LTE system, the RNC sends a bearer setup request message to the eNodeB, and carries the uplink user plane IP address and the TEID of the eNodeB.

Step 705: The eNodeB sends an RRC reconfiguration message to the UE, where the message carries the radio bearer.

QoS;

Step 706: The UE sends an RRC reconfiguration complete message to the eNodeB.

Step 707: The eNodeB sends a bearer setup response message to the RNC, where the message carries the bearer ID, the downlink user plane IP address of the eNodeB, and the TEID.

Step 708: The RNC sends an RAB assignment response message to the SGSN, where the message carries the bearer ID, the downlink user plane IP address of the RNC, the TEID, and the RAT type.

Here, the RAT type is a LET system.

Step 709: The SGSN sends a bearer setup response message to the SGW, where the message carries the bearer ID, the downlink user plane IP address of the SGSN, the TEID, and the RAT type.

Step 710: The SGW sends a bearer setup response message to the PGW, where the message carries the bearer ID, the downlink user plane IP address of the SGW, and the TEID and RAT type. In the step 704, if the RNC determines that the RAT type of the bearer establishment is a UTRAN or a GERAN system, the method for establishing a bearer in the UTRAN system or the GERAN system is similar to the foregoing method, and details are not described herein again.

Embodiment 4:

This embodiment is based on the system architecture shown in FIG. 2, and the RNC is used as an anchor point to implement a bearer management method supporting multiple access. As shown in FIG. 8, the method includes the following steps:

Step 801: The PGW sends a bearer update request to the SGW.

Step 802: The SGW sends a bearer update request to the SGSN.

Step 803: The SGSN sends an RAB Assignment Request message to the RNC to request to update the bearer. Step 804: After receiving the RAB Assignment Request message of the SGSN requesting the update bearer, the RNC determines, according to the local policy, that the RAT type of the bearer update is the LTE system, and the bearer is from the UTRAN. Or the GERAN system is migrated to the LTE system, and the RNC sends a bearer setup request message to the eNodeB, where the message carries the uplink user plane IP address and TEID of the eNodeB;

Step 805: The eNodeB sends an RRC reconfiguration message to the UE, where the message carries the bearer QoS. Step 806: The UE sends an RRC reconfiguration complete message to the eNodeB.

Step 807: The eNodeB sends a bearer setup response message to the RNC, where the message carries the bearer ID, the downlink user plane IP address of the eNodeB, and the TEID.

Step 808: The RNC sends an RAB assignment response message to the SGSN, where the message carries a RAT type.

Step 809, the SGSN returns a bearer update response message to the SGW, where the message carries a RAT type;

Step 810: The SGW returns a bearer update response message to the PGW, where the message carries a RAT type.

In the above method, if the RNC itself determines to migrate the bearer from the UTRAN/GERAN system to the LTE system during the bearer update process, ie, steps 801-803 do not exist, the steps are 808-810 may notify the SGSN, the SGW, and the PGW by using other notification messages; Step 811, the RNC sends a bearer release request message to the NodeB, requesting to release the bearer in the UTRAN or GERAN system;

Step 812: The NodeB sends a radio bearer release request message to the UE.

Step 813: The UE returns a radio bearer release response message to the NodeB.

In step 814, the NodeB returns a release response message to the RNC.

In step 804, if the RNC determines that the RAT type of the bearer update is UTRAN or GERAN, and the bearer is to be migrated from the LTE system to the UTRAN or GERAN system, the method of updating the bearer to the UTRAN or GERAN system is similar to the above method, and is no longer Narration.

With the solution of the present invention, the core network gateway can know the RAT type of the bearer, and can perform accurate differential charging according to the RAT type, thereby avoiding the problem of inaccurate charging.

The above description is only for the preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included. Within the scope of protection of the present invention.

Claims

Claim

A bearer management method supporting multiple access, characterized in that: the method includes: in a bearer management process, an anchor point determines a radio access technology (RAT) type that is established or updated by a bearer, and is established or updated in a bearer. In the process, the RAT type is notified to the core network gateway.

The bearer management method according to claim 1, wherein the anchor point determines that the RAT type of the bearer establishment or update is: the anchor point determines the RAT type of the bearer establishment or update according to the preset local policy. .

3. The bearer management method according to claim 2, wherein the local policy is based on a radio base station signal quality and/or a radio base station load.

The bearer management method according to claim 1, wherein, in the process of establishing or updating a bearer, notifying the core network gateway of the RAT type, in the process of establishing or updating a bearer, the anchor point is The bearer setup response message returned to the core network gateway carries the RAT type, or carries the RAT type in the bearer update response message returned to the core network gateway, or the radio access bearer (RAB) assignment response message sent to the core network gateway Carry the RAT type.

The bearer management method according to claim 1, wherein the method further comprises: the core network gateway performing differential charging according to the RAT type of the bearer.

6. A bearer management system supporting multiple access, characterized in that: the system comprises: an anchor point, a core network gateway;

The core network gateway is configured to obtain a RAT type of the bearer.

The bearer management system according to claim 6, wherein the anchor point comprises: a RAT type determining module, a notification module;

a RAT type determining module, configured to determine, in a bearer management process, a RAT type of a bearer establishment or update; The notification module is configured to notify the core network gateway of the RAT type determined by the RAT type determining module during the bearer setup or update process.

The bearer management system according to claim 7, wherein the RAT type determining module is specifically configured to determine, according to a preset local policy, a RAT type of a bearer establishment or update in a bearer management process.

The bearer management system according to claim 7, wherein the notification module is configured to carry a RAT type, or a bearer setup response message, returned to the core network gateway in a bearer setup or update process. The RAT type is carried in the bearer update response message returned to the core network gateway, or carries the RAT type in the RAB assignment response message sent to the core network gateway.

The bearer management system according to claim 6, wherein the core network gateway is further configured to perform differential charging according to the RAT type of the bearer.

An anchor point, where the anchor point includes: a RAT type determining module, and a notification module;

The anchor point according to claim 11, wherein the RAT type determining module is specifically configured to determine, according to a preset local policy, a RAT type that the bearer establishes or updates in the bearer management process.

The anchor point according to claim 11, wherein the notification module is specifically configured to carry a RAT type in the bearer setup response message returned to the core network gateway during the bearer setup or update process, or The bearer update response message returned to the core network gateway carries the RAT type, or carries the RAT type in the RAB assignment response message sent to the core network gateway.