CN102421196B - Method for managing resource, system and home base station policy function - Google Patents

Abstract

The present invention relates to a resource management method, system and home base station policy function, the method comprising: the home base station policy function receives a response message requesting QoS authorization sent by a broadband policy control framework (BPCF); the response message requesting QoS authorization indicates When rejecting, the HNB policy function performs admission control according to a preset policy. The resource management method, the system and the strategy function of the home base station of the present invention can realize the rational utilization of resources.

Description

Resource management method, system and home base station policy function

technical field

The present invention relates to the communication field, and in particular, relates to a resource management method, system and home base station policy function.

Background technique

The evolved packet system (Evolved Packet System, referred to as EPS) of the 3rd Generation Partnership Project (3rd Generation Partnership Project, referred to as 3GPP) consists of an evolved universal terrestrial radio access network (Evolved Universal Terrestrial Radio Access Network, referred to as E-UTRAN), a mobility management unit (MobilityManagementEntity, MME for short), Serving Gateway (S-GW for short), Packet Data Network Gateway (P-GW for short), and Home Subscriber Server (HSS for short). Fig. 1 is a schematic diagram of an architecture of a home base station (Home evolved NodeB, HeNB for short) accessing an EPS in a non-roaming scenario according to the related art. The architecture of the EPS will be described below with reference to FIG. 1 .

MME is connected with EUTRAN, S-GW and home base station gateway (HeNBGW), and is responsible for mobility management, processing of non-access stratum signaling, and management of user mobility management context; S-GW is connected with E - The access gateway device connected to UTRAN, forwards data between E-UTRAN and P-GW, and is responsible for caching paging waiting data; P-GW is EPS and packet data network (PacketDataNetwork, referred to as PDN) network The border gateway is responsible for PDN access and data forwarding between EPS and PDN.

EPS supports the access of HeNB, which is a small, low-power base station, deployed in indoor places such as homes and offices. A closed subscriber group (Closed Subscriber Group, CSG for short) is a new concept proposed after the introduction of a home base station. Usually, users in a family or an enterprise form a closed user group, and the closed user group is identified by CSGID. The HNBs serving the users in this CSG have the same CSGID. When a CSG is served by only one HNB, the CSG may also be directly identified by a HNB identifier (for example, BSID). According to the wish of the HNB administrator, CSG users and/or non-CSG users can be classified into different levels, and the service priority, service quality and service category they enjoy can be different according to different priorities.

A user can access HNBs corresponding to multiple closed user groups by signing a contract with an operator, for example, the user's office, home, and so on. Hence the concept of allowing closed user group lists was introduced. This list is saved in the user terminal and the user data server on the network side.

There are three usage modes of the femto base station: closed mode, mixed mode and open mode. When the home base station is in closed mode, only CSG subscribers to which the home base station belongs can access the base station and enjoy services provided by the base station. When the home base station is in the open mode, any operator subscriber can access the base station, and the home base station at this time is equivalent to the macro base station. When the home base station is in the mixed mode, any operator's subscriber or roaming user is also allowed to access and use, but different levels must be distinguished according to whether the user has signed up for the CSG, that is to say, the user who signed up for the CSG is using the hybrid home base station. The base station has a higher business priority and enjoys better service quality and business category.

When the user initiates access, the user data server on the network side will send the closed user group signed by the user and allowed to access to the mobility management entity of the core network. The core network mobility management entity will use this information to perform access control on the UE. If the UE accesses the core network from an unauthorized closed-mode HNB, the core network will reject the access of this type of user.

The HeNB usually accesses the core network of the EPS through a leased fixed network line (also called Broadband Access (BBF for short)). In order to ensure the security of the access, a Security Gateway (SeGW for short) is introduced into the core network for shielding, and the data between the HeNB and the SeGW will be encapsulated by IPSec. The HeNB can be directly connected to the MME and the S-GW of the core network through the IPSec tunnel established between the HeNB and the SeGW, and can also be connected to the MME and the S-GW through the HeNBGW (that is, the HeNBGW is optional in the EPS). At the same time, in order to manage the HeNB, a network element: Home NodeB Management System (HeMS for short) is introduced.

Because the QoS (Quality of Service) of the fixed network line accessed by the HeNB is usually limited by the contract between the owner of the HeNB and the fixed network operator. Therefore, when the 3GPP UE accesses the 3GPP core network to access services through the HeNB, the required QoS cannot exceed the QoS of the fixed network line contract that the fixed network operator can provide. Otherwise, the QoS of the service accessed by the UE will not be guaranteed, especially the guaranteed bandwidth (Guaranteed Bitrate, GBR for short). Therefore, for the 3GPP network, it is necessary to control the total QoS demand of service access of all UEs accessed through the HeNB to not exceed the QoS guarantee of the fixed line line contracted by the HeNB.

In addition, the Universal Mobile Telecommunications System (UMTS for short) also supports the access of a home base station HNB (HomeNodeB). Fig. 2 is a schematic diagram of an architecture of HNB accessing UMTS in a non-roaming scenario according to the related art. Figure 2 is similar to the architecture of Figure 1, the difference is that the Serving General Packet Radio Service Support Node (SGSN for short) is used instead of the S-GW, and the Gateway General Packet Radio Service Support Node (Gateway General Packet Radio Service Supporting Node, GGSN for short) is used instead P-GW. In UMTS, HNBGW is mandatory.

In the case that the HNB accesses through a contracted fixed network line, a scenario where multiple HNBs (for example, HeNB, HNB) access the 3GPP core network through a contracted fixed network line must be considered. At this time, for the 3GPP network, it is necessary to control the total QoS requirements for service access of all user equipment (User Equipment, referred to as UE) accessed through these multiple home base stations not to exceed the Signed QoS guarantee for network lines.

At present, a framework for access policy control of a HNB has been proposed, as shown in FIG. 3 . H(e)HBPolicyFunction (home base station policy function) interfaces with the H(e)NB subsystem (including H(e)NBGW and SeGW), and performs policy control on home base station access. Figure 4 shows the architecture of the HeNBGW that does not exist when the HeNB is connected. At this time, the H(e)NBPolicyFunction interfaces with the SeGW and the MME respectively.

Fig. 5 is a flowchart of interaction between the H(e)NB subsystem and the H(e)NBPolicyFunction after the H(e)NB is powered on in the prior art.

Step S501: After the H(e)NB is powered on, it obtains the IP address of the Customer Premises Equipment (CPE) assigned by the BBF access network, and the H(e)NB uses the CPE IP address to perform IKEv2 signaling interaction with the SeGW to establish an IPSec tunnel . During this process, the SeGW allocates the H(e)NB IP address to the H(e)NB for the H(e)NB to interact with other 3GPP network elements. ;

Step S502: The SeGW notifies the H(e)NBPolicyFunction of the relationship between the CEPIP address and the H(e)NBIP address;

Step S503: H(e)NBPolicyFunction returns an acceptance message after saving the association relationship;

Step S504: H(e)NB establishes S1 or Iuh connection with H(e)NBGW or MME;

Step S505: H(e)NBGW or MME establishes a T2 session with H(e)NBPolicyFunction, which carries CSGID and H(e)NBIP address;

Step S506: H(e)NBPolicyFunction associates the T2 session with step S502 according to the H(e)NBIP address, thereby obtaining the CPEIP address of the H(e)NB, and H(e)NBPolicyFunction determines the H(e)NB according to the CPEIP address The BPCF (BroadbandPolicyControlFramework, broadband policy control framework) of the accessed BBF access network. H(e)NBPolicyFunction establishes an S9* session to BPCF, carrying the CPEIP address;

Step S507: BPCF returns a response message;

Step S508: H(e)NBPolicyFunction returns a response message to H(e)NBGW or MME.

Through the above process, the H(e)NBPolicyFunction establishes an S9* session with the BPCF, which is used to perform policy control on the fixed network Backhaul (backhaul line) accessed by the H(e)NB.

Fig. 6 is a flow chart of interaction between H(e)NBPolicyFunction and BPCF when UE initially attaches or requests service through H(e)NB in the prior art.

Step S601: UE performs initial attach or service request (transition from idle state to connected state);

Step S602: MME or SGSN sends a bearer establishment request or radio access bearer assignment request to the H(e)NB via the H(e)NBGW;

Step S603: After receiving the above message, the H(e)NBGW sends a message requesting bearer authorization to the H(e)NBPolicyFunction, and the message carries the H(e)NBIP address and QoS information. If the H(e)NB is in hybrid mode, it will also carry the CSG membership indication of the UE;

Step S604: H(e)NBPolicyFunction determines the CPEIP address according to the H(e)NBIP address, uses the S9* session established in Figure 5 to request QoS authorization from the BPCF, and carries QoS information;

Step S605: The BPCF performs admission control according to the QoS information and the current resource situation of the fixed network Backhaul accessed by the H(e)NB, and returns a response message to the H(e)NBPolicyFunction. BPCF can accept or reject QoS authorization;

Step S606: H(e)NBPolicyFunction returns a response message to H(e)NBGW to accept or reject the authorization;

Step S607: The H(e)NB returns a bearer establishment or radio access bearer assignment response to the MME or SGSN.

Step S603-Step S606 and Step S607 are performed simultaneously.

If in step S606, the H(e)NBGW receives the authorization rejection instruction, then the H(e)NBGW will initiate a bearer deletion request or a radio access bearer assignment request requesting release of radio access resources.

Fig. 7 is an interaction process between H(e)NBPolicyFunction and BPCF during bearer (PDN context) activation/modification/deactivation process in the prior art.

Step S701: MME or SGSN receives an activation/modification/deactivation bearer request message;

Step S702: MME or SGSN sends a corresponding request message to H(e)NB via H(e)NBGW;

Step S703: After receiving the above message, the H(e)NBGW sends a message requesting bearer authorization to the H(e)NBPolicyFunction, and the message carries the H(e)NBIP address and QoS information. If the H(e)NB is in hybrid mode, it will also carry the CSG membership indication of the UE;

Step S704: H(e)NBPolicyFunction determines the CPEIP address according to the H(e)NBIP address, uses the S9* session established in Figure 5 to request QoS authorization from the BPCF, and carries QoS information;

Step S705: The BPCF performs admission control according to the QoS information and the current resource situation of the fixed network Backhaul accessed by the H(e)NB, and returns a response message to the H(e)NBPolicyFunction. BPCF can accept or reject QoS authorization;

Step S706: H(e)NBPolicyFunction returns a response message to H(e)NBGW to accept or reject the authorization;

Step S707: The H(e)NB returns a bearer establishment or radio access bearer assignment response to the MME or SGSN.

Step S703-step S706 and step S707 are performed simultaneously.

If in step S706, the H(e)NBGW receives an authorization rejection indication, then the H(e)NBGW will initiate a bearer deletion request or a radio access bearer assignment request requesting the release of radio access resources in order to reject the bearer of the UE. /modify request.

Through the above three processes, the existing technology can realize that the resources requested by all UEs accessing the H(e)NB will not exceed the sum of the currently available resources of the backhual connected to the H(e)NB, thus ensuring that each UE The smooth progress of each business.

In the above process, when the BPCF rejects the authorization request according to the current resource situation, regardless of the current bearer or the user's current user status, the corresponding bearer establishment or modification request will be rejected. Not reasonable enough.

Contents of the invention

The technical problem to be solved by the present invention is a resource management method, system and strategy function of the home base station, so as to realize rational utilization of resources.

In order to solve the above problems, the present invention provides a resource management method, the method includes:

The home base station policy function (H(e)NBPolicyFunction) receives a response message requesting QoS authorization sent by the broadband policy control framework (BPCF);

When the response message requesting QoS authorization indicates rejection, the home base station policy function performs admission control according to a preset policy.

In order to solve the above technical problems, the present invention also provides a home base station policy function, the home base station policy function (H(e)NBPolicyFunction) includes:

The message receiving module is configured to receive a response message requesting QoS authorization sent by the Broadband Policy Control Framework (BPCF);

The admission control module is connected with the message receiving module, and is configured to execute admission control according to a preset policy when the response message indicates that authorization is denied.

In order to solve the above technical problems, the present invention also provides another resource management method, which is characterized in that the method includes:

The home base station gateway or the mobility management network element requests a bearer authorization message from the home base station policy function (H(e)NBPolicyFunction);

The home base station policy function requests QoS authorization from the broadband policy control framework (BPCF) after receiving the message requesting bearer authorization;

After receiving the message requesting QoS authorization, the BPCF sends a response message requesting QoS authorization to the policy function of the home base station;

When the response message requesting QoS authorization indicates rejection, the home base station policy function performs admission control according to a preset policy.

In order to solve the above technical problems, the present invention also provides another resource management system, which includes:

The home base station gateway or mobility management network element is used to send a message requesting bearer authorization to the home base station policy function (H(e)NBPolicyFunction);

The BPCF is configured to receive a message requesting QoS authorization, and send a response message requesting QoS authorization to the home base station policy function;

The home base station policy function includes a message receiving module, a message sending module connected to the message receiving module, and an admission control module connected to the message sending module and the message receiving module, wherein the message receiving module is used to receive the requested bearer An authorized message and a message requesting QoS authorization; the message sending module is used for the message receiving module to request QoS authorization from the broadband policy control framework (BPCF) after receiving the message requesting bearer authorization;

The admission control module is configured to perform admission control according to a preset policy when the response message indicates that authorization is denied.

The resource management method, system, and HNB policy function of the present invention, in the case of insufficient current resources, the H(e)NBPolicyFunction executes admission control according to a pre-established policy, and releases resources occupied by other bearers in the following manner: The current bearer obtains enough resources to realize resource redistribution and rational utilization.

Description of drawings

The accompanying drawings described here are used to provide a further understanding of the present invention and constitute a part of the application. The schematic embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute improper limitations to the present invention. In the attached picture:

FIG. 1 is a schematic diagram of an architecture of HeNB accessing EPS in a non-roaming scenario according to related technologies;

FIG. 2 is a schematic diagram of an architecture of HNB accessing UMTS in a non-roaming scenario according to related technologies;

Fig. 3 is a framework for access policy control of a home base station in the prior art, where H(e)GW exists;

Fig. 4 is a framework for access policy control of a home base station in the prior art, where there is no H(e)GW;

Fig. 5 is an interactive flowchart when the home base station is powered on in the prior art;

Fig. 6 is an interaction flow chart of the user's initial attachment or service request in the prior art;

Fig. 7 is the interaction flow chart when bearer (PDP context) activates/modifies/deactivates live request in the prior art;

Fig. 8 is an interaction flow chart when a user initially attaches, requests a PDN connection, updates a tracking area/routing area, or requests a service in Embodiment 1 of the present invention;

Fig. 9 is another interactive flow chart of embodiment 2 of the present invention when a user initially attaches, requests a PDN connection, updates a tracking area/routing area, or requests a service;

Fig. 10 is an interactive flow chart when carrying (PDP context) activation/modification/deactivation request according to Embodiment 3 of the present invention;

Fig. 11 is another interactive flow chart when carrying (PDP context) activation/modification/deactivation request according to Embodiment 4 of the present invention;

Fig. 12 is a schematic diagram of the resource management method of the present invention;

Fig. 13 is a schematic diagram of a module structure of a policy function of a home base station according to the present invention.

Detailed ways

According to the existing process, when the H(e)NB is in hybrid mode, if there are already non-CSG member users accessing the H(e)NB access service, the current backhaul resources have been exhausted or are about to be exhausted, when the CSG member When a user initiates access or bearer establishment/modification, BPCF will reject the CSG member user's access or bearer establishment/modification according to the current resource situation, which is obviously unreasonable. Similarly, if a bearer with a lower priority is accessed, access to a bearer with a higher priority is rejected; or if a bearer with a non-emergency service is accessed, access to an emergency service is rejected, unreasonable resource utilization will occur.

In order to make reasonable use of resources, the main idea of the resource management method, system, and HNB policy function of the present invention is that, in the case of insufficient current resources, the H(e)NBPolicyFunction performs admission control according to a pre-established policy, Obtain sufficient resources for the current bearer by releasing the resources occupied by other bearers, so as to realize resource reallocation and rational utilization.

For example, for the mixed mode, when establishing or modifying bearer resources of CSG members is insufficient, the access or bearer of those non-CSG members is interrupted or deleted. In addition, each bearer also has a priority. Therefore, for user bearers with the same CSG membership, when the backhual resources are exhausted and BPCF returns authorization rejection, the resources should be reallocated according to the bearer's priority.

As shown in Figure 12, the resource management method of the present invention includes:

Step 101: The home base station policy function (H(e)NBPolicyFunction) receives a response message requesting QoS authorization sent by the broadband policy control framework (BPCF);

Step 102: When the response message to the request for QoS authorization indicates denial, the policy function of the home base station performs admission control according to a preset policy.

The home base station policy function performing admission control according to a preset policy includes:

The home base station policy function determines whether the bearer requesting QoS authorization preempts other bearer resources according to a preset policy;

When preemption is judged, the HNB policy function triggers a deactivation process of the preempted bearer.

When preemption is judged, the HNB policy function also sends a response message indicating acceptance of bearer authorization to the bearer authorization requesting end, otherwise sends a response message indicating rejection of bearer authorization to the requesting end.

According to guaranteeing different bearers or user's service experience, different policies can be formulated. The policies can include selection range policy of preempted bearers, selection sequence policy of preempted bearers, or conditions of resource preemption, etc.

The policy is: when the home base station mode is a mixed mode, perform admission control according to the Closed Subscriber Group (CSG) membership; or,

Perform admission control based on Allocation Preservation Priority (ARP); or,

When the HNB is in open mode or closed mode, admission control is performed according to ARP; when the HNB mode is hybrid mode, admission control is performed according to Closed Subscriber Group (CSG) membership and/or ARP.

Specifically, different HNB models can formulate different policy content:

When the home base station is in the open mode or the closed mode, according to the allocation retention priority (ARP), the bearer preempts the resources of other user bearers; for example: select from the bearer with a lower allocation retention priority (ARP) than the current bearer to meet the resource preemption conditional preempted bearer;

When the home base station mode is a hybrid mode, when the user corresponding to the bearer is a closed subscriber group (CSG) member, the bearer preempts resources carried by non-CSG member users and/or preempts resources carried by other CSG member users according to ARP; When the user corresponding to the bearer is a non-CSG member, the bearer preempts the resources of other non-CSG member user bearers according to the Allocation Preservation Priority (ARP).

Specifically, when the HNB is in hybrid mode and the user corresponding to the bearer is a CSG member, the selection order of the preempted bearer is to first select from the bearers of non-CSG members, and then select from the bearers of CSG members.

The preempted bearers are one or more, and the resource of the one or more preempted bearers is greater than or equal to the resource requested by the bearer.

When the response message to the request for QoS authorization indicates that the authorization is rejected, it also carries current available resource information; the available resource after the resource preemption is the sum of the current available resource and the preempted resource.

The home base station policy function judges the resources to be preempted, and if the preempted resources are greater than the resources allocated by the current bearer request, then request the BPCF to release the resource difference; if the preempted resources are less than the resources allocated by the current bearer request, then request the BPCF to allocate the balance resource.

The message requesting bearer authorization carries the current bearer identifier, and when the home base station policy function initiates the bearer deactivation process, the message that triggers the deactivation of the preempted bearer carries the bearer identifier of the preempted bearer.

Hereinafter, the present invention will be described in detail with reference to the drawings and examples. It should be noted that, in the case of no conflict, the embodiments in the present application and the features in the embodiments can be combined with each other.

Example 1

Fig. 8 is a flowchart 1 of interaction between H(e)NBPolicyFunction and BPCF when UE initially attaches through H(e)NB, requests PDN connection, tracking area update/routing area update or service request according to an embodiment of the present invention. The process includes the following steps:

Step S801: UE performs initial attachment, request for PDN connection, tracking area update/routing area update or service request (transition from idle state to connected state);

Step S802: the MME or the SGSN sends a bearer establishment request or a radio access bearer assignment request to the H(e)NBGW.

Step S803: After receiving the above message, the H(e)NBGW sends a bearer authorization request message to the H(e)NBPolicyFunction, which carries the H(e)NBIP address, QoS request bearer ID, and QoS information. If the H(e)NB is in hybrid mode, it will also carry the CSG membership indication of the UE. The QoS request bearer identifier is used to uniquely identify the bearer when H(e)NBGW interacts with H(e)NBPolicyFunction. The bearer identifier of the QoS request can be assigned by H(e)NBGW, or a combination of user identifier and EPS bearer identifier (for EPS system) or user identifier and network layer service access point identifier (NetworklayerServiceAccessPointIdentifier, NSAPI for short) (that is, UMTS system The embodiment of the combination of the bearer identification) (for the UMTS system);

For the UMTS system, for the PDP context of Non-GBR (business that does not need to guarantee the bandwidth), the QoS information includes at least Traficclass (service type), ARP (Allocation/RetentionPriority, allocation retention priority), MBR (maximum bit rate); for The PDP context of GBR, the QoS information at least includes Traficclass, ARP, GBR (GuaranteedBitRate, guaranteed bit rate), MBR.

For the EPS system, if the initial access or PDN connection is requested, the QoS information includes QCI (QoSClassIdentifier, Qos Class ID), ARP and UE-AMBR (Terminal Aggregate Maximum Bit Rate). If it is not an initial access or request for a PDN connection, for a Non-GBR bearer, the QoS information includes QCI, ARP, and MBR; for a GBR bearer, the QoS information includes QCI, ARP, GBR, and MBR.

H(e)NBPolicyFunction has the following information at this time: the use mode of the H(e)NB accessed by the bearer (open, closed, mixed mode), if it is a mixed mode, it also has member indication information (CSG member, non-CSG member) ; QoS information of the bearer.

Step S804: H(e)NBPolicyFunction determines the CPEIP address according to the H(e)NBIP address, uses the S9* session established in Figure 5 to request QoS authorization from the BPCF, and carries the requested bandwidth BR-Allocation and the requested resource allocation indication;

Among them, if the QoS information obtained from H(e)NBGW contains GBR, then BR-Allocation can be set as GBR in the QoS information;

If the QoS information obtained from H(e)NBGW does not include GBR, then H(e)NBPolicyFunction can execute two strategies:

(1) Set BR-Allocatin according to MBR or UE-AMBR and local policy

(2) H(e)NBPolicyFunction processes locally, and does not request QoS authorization from BPCF.

Step S805: The BPCF performs admission control according to the BR-Allocation and the current resource situation of the fixed network Backhaul accessed by the H(e)NB, and returns a response message to the H(e)NBPolicyFunction. If the current available bandwidth is greater than or equal to the requested bandwidth BR-Allocation, BPCF returns an acceptance indication; if the current available bandwidth is less than the requested bandwidth BR-Allocation, BPCF rejects the indication and can carry the current available bandwidth BR-Accept;

Step S806: H(e)NBPolicyFunction executes the following policy decisions according to the return message from BPCF.

(a) If H(e)NBPolicyFunction receives an acceptance indication, execute step S809;

(b) If H(e)NBPolicyFunction receives a rejection indication, then H(e)NBPolicyFunction further performs admission control according to the established policy:

(b1) If the access mode of H(e)NB is open mode, H(e)NBPolicyFunction will combine this bearer (PDP context) with other bearer (context) authorized by BPCF established by the user according to ARP (Allocation/RetentionPriority) ) and other bearers (PDP context) authorized by BPCF established by other users accessed by the same H(e)NB:

If the bearer (PDP context) cannot preempt other bearer (PDP context) resources (that is, the ARP (Allocation/RetentionPriority) of the bearer (PDP context) is lower than the ARP (Allocation/RetentionPriority) of other bearers (PDP context)), Then execute step S812;

If the bearer (PDP context) can preempt the resources of other bearers, and the sum of the bandwidth BR-Allocation' of other bearers (PDP context) and the currently available bandwidth BR-Accept returned by BPCF is greater than or equal to the requested bandwidth BR- Allocation, execute step S807; otherwise, execute step S812;

(b2) If the HeNB access mode is hybrid mode, and the UE membership corresponding to the bearer (PDP context) is a non-CSG user, then:

(b21) If there are other BPCF-authorized bearers (PDP contexts) established by the user itself or other BPCF-authorized bearers (PDP contexts) established by other non-CSG users accessed through the same H(e)NB, then H(e)NBPolicyFunction compares the bearer (PDP context) with other bearers (PDP context) according to ARP (Allocation/RetentionPriority), if the bearer (PDP context) cannot preempt resources of other bearers (PDP context), then execute step S812 ; If the bearer (PDP context) can preempt the resources of other bearers (PDP context), and can preempt the bandwidth of other bearers (PDP context) BR-Allocation' and the current available bandwidth BR-Accept returned by BPCF is greater than or equal to the request allocated bandwidth BR-Allocation, execute step S807; otherwise, execute step S812;

(b22) If there is no other BPCF-authorized bearer (PDP context) established by the user itself or other BPCF-authorized bearer (PDP context) established by other non-CSG users accessed through the same H(e)NB , then step S812 is executed.

(b3) If the access mode of the HeNB is hybrid mode, and the membership of the UE corresponding to the bearer (PDP context) is a CSG user, then:

(b31) If there are other BPCF-authorized bearers (PDP contexts) established by other non-CSG users accessed through the H(e)NB, and this bearer (PDP context) can preempt the BPCF-authorized bearers established by other non-CSG users The sum of the bearer (PDP context) bandwidth BR-Allocation' and the current available bandwidth BR-Accept returned by BPCF is greater than or equal to the requested bandwidth BR-Allocation, then perform step S807; (Allocation/RetentionPriority) combine this bearer (PDP context) with other bearers (PDP context) authorized by BPCF established by the user itself or other bearers authorized by BPCF established by other CSG users accessed through the same H(e)NB If the bearer (PDP context) cannot preempt the resources of other bearers (PDP context), step S812 is executed; if the bearer (PDP context) can preempt other bearers authorized by the BPCF established by the CSG user (PDP context) resources, and can preempt the bandwidth BR-Allocation' of other bearers (PDP context) (including bearers established by non-CSG users and bearers established by CSG users) and the current available bandwidth BR-Accept returned by BPCF is greater than or equal to the bandwidth BR-Allocation requested for allocation, execute step S807; otherwise, execute step S812;

(b32) If there is no other bearer (PDP context) authorized by BPCF established by a non-CSG user accessed through the same H(e)NB, then H(e)NBPolicyFunction will bearer according to ARP (Allocation/RetentionPriority) ( PDP context) is compared with other BPCF-authorized bearers (PDP context) established by the user itself or other BPCF-authorized bearers (PDP context) established by other CSG users accessed through the same H(e)NB, if If the bearer (PDP context) cannot preempt resources of other bearers (PDP context), step S812 is executed. If the bearer can preempt the resources of other bearers (PDP context), and the sum of the bandwidth BR-Allocation' of other bearers (PDP context) and the current available bandwidth BR-Accept returned by BPCF is greater than or equal to BR-Allocaton, execute Step S707; otherwise, execute step S812;

(b4) If the access mode of the HeNB is closed mode, then H(e)NBPolicyFunction connects the bearer (PDP context) with other bearer (PDP context) authorized by BPCF or Compared with the BPCF-authorized bearer (PDP context) established by other users accessed by the same H(e)NB, if the bearer (PDP context) cannot preempt the resources of other bearers (PDP context), perform step S812. If the bearer (PDP context) can preempt the resources of other bearers (PDP context), and the sum of the bandwidth BR-Allocation' and the current available bandwidth BR-Accept returned by BPCF is greater than or equal to the requested allocation bandwidth BR-Allocation, execute step S807; otherwise, execute step S812;

Step S807: H(e)NBPolicyFunction sends a bearer (PDP context) deactivation indication to H(e)NBGW, carrying the preempted bearer (PDP context) identifier;

Step S808: The H(e)NBGW initiates the release of resources of the preempted bearer (PDP context) according to the identifier of the bearer (PDP context). For EPS, if the default bearer is released, it will cause the network to detach the UE or disconnect the PDN connection;

If the bandwidth BR-Allocation' of the preempted bearer (PDP context) is not equal to the requested bandwidth BR-Allocation, then H(e)NBPolicyFunction needs to interact with BPCF, if BR-Allocation'>BR-Allocation, then H(e)NBPolicyFunction will request BPCF to release the balance bandwidth BR-Allocation'-BR-Allocation; otherwise, H(e)NBPolicyFunction will request BPCF to allocate the balance bandwidth BR-Allocation-BR-Allocation.

Step S809: The H(e)NBPolicyFunction returns a Bearer Authorization Response message to the H(e)NBGW, carrying an acceptance indication. This message is the response message of step S803;

Step S810: H(e)NBGW sends a radio access bearer assignment request/bearer establishment request message to H(e)NB;

Step S811: After the H(e)NB performs corresponding operations, it returns a response message; the H(e)NBGW further returns a bearer establishment or radio access bearer assignment response message to the MME or SGSN, carrying an acceptance indication. The process ends.

Step S812: The H(e)NBPolicyFunction returns a Bearer Authorization Response message to the H(e)NBGW, carrying a rejection indication. This message is the response message of step S803;

Step S813: The H(e)NBGW returns a bearer establishment or radio access bearer assignment response message to the MME or the SGSN, carrying a rejection indication. For EPS, if the establishment of the default bearer is rejected, it will cause the network to reject the access of the UE. The process ends.

Example 2

Fig. 9 is a flowchart 2 of interaction between H(e)NBPolicyFunction and BPCF when UE initially attaches through H(e)NB, requests PDN connection, tracking area update/routing area update or service request according to an embodiment of the present invention. The process includes the following steps:

Step S901: UE performs initial attachment, request for PDN connection, tracking area update/routing area update or service request (transition from idle state to connected state);

Step S902: the MME or the SGSN sends a bearer establishment request or a radio access bearer assignment request to the H(e)NBGW.

Step S903: After the H(e)NBGW receives the above message, the H(e)NBGW sends a radio access bearer assignment request/bearer establishment request message to the H(e)NB;

Step S904: After the H(e)NB performs the corresponding operation, it returns a response message; the H(e)NBGW further returns a bearer establishment or radio access bearer assignment response message to the MME or SGSN, carrying an acceptance indication. At this point, the establishment of the radio bearer requested by the UE is completed, that is, the H(e)NBGW first allows the establishment of the bearer by default.

Step S905: At the same time as step S903, H(e)NBGW sends a message requesting bearer authorization to H(e)NBH(e)NBPolicyFunction, the message carries H(e)NBIP address, QoS request bearer ID, and QoS information. If the H(e)NB is in hybrid mode, it will also carry the CSG membership indication of the UE. The QoS request bearer identifier is used to uniquely identify the bearer when H(e)NBGW interacts with H(e)NBPolicyFunction. The QoS request bearer identifier can be allocated by H(e)NBGW, or can be embodied by a combination of user identifier and EPS bearer identifier (EPS system) or a combination of user identifier and NSAPI (UMTS system);

For the UMTS system, for the Non-GBR PDP context, the QoS information includes at least Traficclass, ARP, and MBR; for the GBR PDP context, the QoS information includes at least Traficclass, ARP, GBR, and MBR.

For the EPS system, if the initial access or PDN connection is requested, the QoS information includes QCI, ARP and UE-AMBR. If it is not an initial access or request for a PDN connection, for a Non-GBR bearer, the QoS information includes QCI, ARP, and MBR; for a GBR bearer, the QoS information includes QCI, ARP, GBR, and MBR.

H(e)NBPolicyFunction has the following information at this time: the use mode of the H(e)NB accessed by the bearer (open, closed, mixed mode), if it is a mixed mode, it also has member indication information (CSG member, non-CSG member) ; QoS information of the bearer.

Step S906: H(e)NBPolicyFunction determines the CPEIP address according to the H(e)NBIP address, uses the S9* session established in Figure 5 to request QoS authorization from the BPCF, carrying the bandwidth BR-Allocation requested for allocation and the resource allocation requested;

Among them, if the QoS information obtained from H(e)NBGW contains GBR, then BR-Allocation can be set as GBR in the QoS information;

If the QoS information obtained from H(e)NBGW does not include GBR, then H(e)NBPolicyFunction can execute two strategies:

(1) Set BR-Allocatin according to MBR or UE-AMBR and local policy

(2) H(e)NBPolicyFunction processes locally, and does not request QoS authorization from BPCF.

Step S907: The BPCF performs admission control according to the BR-Allocation and the current resource situation of the fixed network Backhaul accessed by the H(e)NB, and returns a response message to the H(e)NBPolicyFunction. If the current available bandwidth is greater than or equal to the requested bandwidth BR-Allocation, BPCF returns an acceptance indication; if the current available bandwidth is less than the requested bandwidth BR-Allocation, BPCF rejects the indication and can carry the current available bandwidth BR-Accept;

Step S908: H(e)NBPolicyFunction executes the following policy decisions according to the return message from BPCF.

(a) If the H(e)NBPolicyFunction receives an acceptance indication, execute step S911;

(b) If H(e)NBPolicyFunction receives a rejection indication, then H(e)NBPolicyFunction further performs admission control according to the established policy:

(b1) If the access mode of H(e)NB is open mode, H(e)NBPolicyFunction will combine this bearer (PDP context) with other bearer (context) authorized by BPCF established by the user according to ARP (Allocation/RetentionPriority) ) and other bearers (PDP context) authorized by BPCF established by other users accessed by the same H(e)NB:

If the bearer (PDP context) cannot preempt other bearer (PDP context) resources (that is, the ARP (Allocation/RetentionPriority) of the bearer (PDP context) is lower than the ARP (Allocation/RetentionPriority) of other bearers (PDP context)), Then execute step S912;

If the bearer (PDP context) can preempt the resources of other bearers, and the sum of the bandwidth BR-Allocation' of other bearers (PDP context) and the currently available bandwidth BR-Accept returned by BPCF is greater than or equal to the requested bandwidth BR- Allocation, execute step S909; otherwise, execute step S912;

(b2) If the HeNB access mode is hybrid mode, and the UE membership corresponding to the bearer (PDP context) is a non-CSG user, then:

(b21) If there are other BPCF-authorized bearers (PDP contexts) established by the user itself or other BPCF-authorized bearers (PDP contexts) established by other non-CSG users accessed through the same H(e)NB, then H(e)NBPolicyFunction compares the bearer (PDP context) with other bearers (PDP context) according to ARP (Allocation/RetentionPriority), if the bearer (PDP context) cannot preempt resources of other bearers (PDP context), then execute step S912 ; If the bearer (PDP context) can preempt the resources of other bearers (PDP context), and can preempt the bandwidth of other bearers (PDP context) BR-Allocation' and the current available bandwidth BR-Accept returned by BPCF is greater than or equal to the request allocated bandwidth BR-Allocation, execute step S909; otherwise, execute step S912;

(b22) If there is no other BPCF-authorized bearer (PDP context) established by the user itself or other BPCF-authorized bearer (PDP context) established by other non-CSG users accessed through the same H(e)NB , then execute step S912.

(b3) If the access mode of the HeNB is hybrid mode, and the membership of the UE corresponding to the bearer (PDP context) is a CSG user, then:

(b31) If there are other BPCF-authorized bearers (PDP contexts) established by other non-CSG users accessed through the H(e)NB, and this bearer (PDP context) can preempt the BPCF-authorized bearers established by other non-CSG users The sum of the bearer (PDP context) bandwidth BR-Allocation' and the current available bandwidth BR-Accept returned by BPCF is greater than or equal to the bandwidth BR-Allocation requested for allocation, then perform step S909; (Allocation/RetentionPriority) combine this bearer (PDP context) with other bearers (PDP context) authorized by BPCF established by the user itself or other bearers authorized by BPCF established by other CSG users accessed through the same H(e)NB Bearer (PDP context) is compared, if the bearer (PDP context) cannot preempt the resources of other bearers (PDP context), then perform step S912; if the bearer (PDP context) can preempt other bearers authorized by the BPCF established by the CSG user (PDP context) resources, and can preempt the bandwidth BR-Allocation' of other bearers (PDP context) (including bearers established by non-CSG users and bearers established by CSG users) and the current available bandwidth BR-Accept returned by BPCF is greater than or equal to the bandwidth BR-Allocation requested for allocation, execute step S909; otherwise, execute step S912;

(b32) If there is no other bearer (PDP context) authorized by BPCF established by a non-CSG user accessed through the same H(e)NB, then H(e)NBPolicyFunction will bearer according to ARP (Allocation/RetentionPriority) ( PDP context) is compared with other BPCF-authorized bearers (PDP context) established by the user itself or other BPCF-authorized bearers (PDP context) established by other CSG users accessed through the same H(e)NB, if If the bearer (PDP context) cannot preempt resources of other bearers (PDP context), step S812 is executed. If the bearer can preempt the resources of other bearers (PDP context), and the sum of the bandwidth BR-Allocation' of other bearers (PDP context) and the current available bandwidth BR-Accept returned by BPCF is greater than or equal to BR-Allocaton, execute Step S909; otherwise, execute step S912;

(b4) If the access mode of the HeNB is closed mode, then H(e)NBPolicyFunction connects the bearer (PDP context) with other bearer (PDP context) authorized by BPCF or Compared with the BPCF-authorized bearer (PDP context) established by other users accessed by the same H(e)NB, if the bearer (PDP context) cannot preempt the resources of other bearers (PDP context), perform step S912. If the bearer (PDP context) can preempt the resources of other bearers (PDP context), and the sum of the bandwidth BR-Allocation' and the current available bandwidth BR-Accept returned by BPCF is greater than or equal to the requested allocation bandwidth BR-Allocation, execute step S909; otherwise, execute step S912;

Step S909: H(e)NBPolicyFunction sends a bearer (PDP context) deactivation indication to H(e)NBGW, carrying the preempted QoS request bearer (PDP context) identifier;

Step S910: The H(e)NBGW initiates the release of resources of the preempted bearer (PDP context) according to the identifier of the QoS request bearer (PDP context). For EPS, if the default bearer is released, it will cause the network to detach the UE or disconnect the PDN connection;

If the bandwidth BR-Allocation' of the preempted bearer (PDP context) is not equal to the requested bandwidth BR-Allocation, then H(e)NBPolicyFunction needs to interact with BPCF, if BR-Allocation'>BR-Allocation, then H(e)NBPolicyFunction will request BPCF to release the balance bandwidth BR-Allocation'-BR-Allocation; otherwise, H(e)NBPolicyFunction will request BPCF to allocate the balance bandwidth BR-Allocation-BR-Allocation.

Step S911: The H(e)NBPolicyFunction returns a Bearer Authorization Reply message to the H(e)NBGW, carrying an acceptance indication. This message is the response message of step S905. The process ends. The H(e)NBGW approves the radio bearer established in step S904;

Step S912: The H(e)NBPolicyFunction returns a bearer authorization response message to the H(e)NBGW, carrying a rejection indication. This message is the response message of step S905;

Step S913: The H(e)NBGW initiates a PDP context deactivation procedure/bearer deactivation procedure, and releases the bearer requested by the UE to be established in step S904. For EPS, if the release is the establishment of the default bearer, it will cause the network to reject the UE's access or disconnect the PDN connection. The process ends.

Example 3

Fig. 10 is an interaction process between H(e)NBPolicyFunction and BPCF during bearer (PDN context) activation/modification/deactivation process according to an embodiment of the present invention. The process includes the following steps:

Step S1001: MME or SGSN receives an activation/modification/deactivation bearer (PDP context) request message from the core network;

Step S1002: MME or SGSN sends activation/modification/deactivation bearer request or radio access bearer assignment request to H(e)NBGW to carry activation/modification/deactivation indication;

Step S1003: After receiving the above message, H(e)NBGW sends a message requesting bearer authorization to H(e)NBPolicyFunction,

If it is an activation request, the message carries the H(e)NBIP address, QoS request bearer identifier, and QoS information. If the H(e)NB is in hybrid mode, it will also carry the CSG membership indication of the UE. The QoS request bearer identifier is used to uniquely identify the bearer when H(e)NBGW interacts with H(e)NBPolicyFunction. The QoS request bearer identifier can be allocated by H(e)NBGW, or can be embodied by a combination of user identifier and EPS bearer identifier (EPS system) or a combination of user identifier and NSAPI (UMTS system);

If it is a modification request, the message carries the QoS request bearer identifier and QoS information;

If it is a deactivation request, the message carries the QoS request bearer identifier.

For the UMTS system, for the Non-GBR PDP context, the QoS information includes at least Traficclass, Allocation/RetentionPriority, and MBR; for the GBR PDP context, the QoS information includes at least Traficclass, Allocation/RetentionPriority, GBR, and MBR.

For Non-GBR bearer in EPS system, QoS information includes QCI, ARP, MBR; for GBR bearer, QoS information includes QCI, ARP, GBR, MBR.

Step S1004: For the activation request, H(e)NBPolicyFunction determines the CPEIP address according to the H(e)NBIP address, uses the S9* session established in Figure 5 to request QoS authorization from BPCF, and carries the requested bandwidth BR-Allocation and requested allocated resources instruct;

Among them, if the QoS information obtained from H(e)NBGW contains GBR, then BR-Allocation can be set as GBR in the QoS information;

If the QoS information obtained from H(e)NBGW does not include GBR, then H(e)NBPolicyFunction can execute two strategies:

(1) Set BR-Allocatio according to MBR or UE-AMBR and local policy

(2) H(e)NBPolicyFunction processes locally, and does not request QoS authorization from BPCF.

For the modification request, H(e)NBPolicyFunction determines the S9* session according to the QoS request bearer ID, and requests the BPCF for QoS authorization to pass through S9.

If the QoS information obtained from H(e)NBGW contains GBR, then BR-Allocation can be set as the difference between the GBR in the QoS information before and after the update. If the bandwidth is increased after the update, H(e)NBPolicyFunction sends a message to BPCF Carry the bandwidth BR-Allocation requested for allocation and the resource allocation request indication; if the bandwidth is reduced after the update, H(e)NBPolicyFunction carries the bandwidth BR-Release request for release and the resource release indication for the BPCF message

If the QoS information obtained from H(e)NBGW does not include GBR, then H(e)NBPolicyFunction can execute two strategies:

(1) Set new bandwidth according to MBR or UE-AMBR and local policy, and set BR-Allocation or BR-Release according to the difference before and after the update.

(2) H(e)NBPolicyFunction processes locally, and does not request QoS authorization from BPCF.

Step S1005: If bandwidth allocation is requested, BPCF performs admission control according to the BR-Allocation and the current resource situation of the fixed network Backhaul accessed by the H(e)NB, and returns a response message to the H(e)NBPolicyFunction. If the current available bandwidth is greater than or equal to BR-Allocation, BPCF returns an acceptance indication; if the current available bandwidth message is BR-Allocation, BPCF rejects the indication, and at the same time can carry acceptable bandwidth BR-Accept. If the bandwidth is requested to be released, the BPCF returns an acceptance indication.

Step S1006: H(e)NBPolicyFunction executes the following policy decisions according to the return message from BPCF.

(a) If H(e)NBPolicyFunction receives an acceptance indication, execute step S909;

(b) If H(e)NBPolicyFunction receives a rejection indication, then H(e)NBPolicyFunction further performs admission control:

(b1) If the access mode of H(e)NB is open mode, H(e)NBPolicyFunction will combine this bearer (PDP context) with other bearer (context) authorized by BPCF established by the user according to ARP (Allocation/RetentionPriority) ) and other bearers (PDP context) authorized by BPCF established by other users accessed by the same H(e)NB:

If the bearer (PDP context) cannot preempt other bearer (PDP context) resources (the ARP (Allocation/RetentionPriority) of the bearer (PDP context) is lower than the ARP (Allocation/RetentionPriority) of other bearers (PDP context)), then execute Step S1012;

If the bearer (PDP context) can preempt the resources of other bearers, and the sum of the bandwidth BR-Allocation' of other bearers (PDP context) and the current available bandwidth BR-Accept returned by BPCF is greater than or equal to BR-Allocation, then execute Step S1007; otherwise, execute step S1012;

(b2) If the HeNB access mode is hybrid mode, and the UE membership corresponding to the bearer (PDP context) is a non-CSG user, then:

(b21) If there are other BPCF-authorized bearers (PDP contexts) established by the user itself or other BPCF-authorized bearers (PDP contexts) established by other non-CSG users accessed through the same H(e)NB, then H(e)NBPolicyFunction compares the bearer (PDP context) with other bearers (PDP context) according to ARP (Allocation/RetentionPriority), if the bearer (PDP context) cannot preempt resources of other bearers (PDP context), then execute step S1012 ; If the bearer (PDP context) can preempt the resources of other bearers (PDP context), and can preempt the bandwidth of other bearers (PDP context) BR-Allocation' and the current available bandwidth BR-Accept returned by BPCF is greater than or equal to BR -Allocation, execute step S1007; otherwise, execute step S1012;

(b22) If there is no other BPCF-authorized bearer (PDP context) established by the user itself or other BPCF-authorized bearer (PDP context) established by other non-CSG users accessed through the same H(e)NB , then execute step S1012.

(b3) If the access mode of the HeNB is hybrid mode, and the membership of the UE corresponding to the bearer (PDP context) is a CSG user, then:

(b31) If there are other BPCF-authorized bearers (PDP contexts) established by other non-CSG users accessed through the H(e)NB, and this bearer (PDP context) can preempt the BPCF-authorized bearers established by other non-CSG users The sum of the bearer (PDP context) bandwidth BR-Allocation' and the current available bandwidth BR-Accept returned by BPCF is greater than or equal to BR-Allocation, then execute step S1007; ) the bearer (PDP context) with other bearers (PDP context) authorized by the BPCF established by the user or other bearers authorized by the BPCF established by other CSG users accessed through the same H(e)NB ) for comparison, if the bearer (PDP context) cannot preempt the resources of other bearers (PDP context), then perform step S1012; if the bearer (PDP context) can preempt other bearers (PDP context) authorized by the BPCF established by the CSG user and can preempt the bandwidth BR-Allocation' of other bearers (PDP context) (including bearers established by non-CSG users and bearers established by CSG users) and the current available bandwidth BR-Accept returned by BPCF is greater than or equal to BR- Allocation, execute step S1007; otherwise, execute step S1012;

(b32) If there is no other bearer (PDP context) authorized by BPCF established by a non-CSG user accessed through the same H(e)NB, then H(e)NBPolicyFunction will bearer according to ARP (Allocation/RetentionPriority) ( PDP context) is compared with other BPCF-authorized bearers (PDP context) established by the user itself or other BPCF-authorized bearers (PDP context) established by other CSG users accessed through the same H(e)NB, if If the bearer (PDP context) cannot preempt the resources of other bearers (PDP context), step S1012 is performed. If the bearer can preempt the resources of other bearers (PDP context), and the sum of the bandwidth BR-Allocation' of other bearers (PDP context) and the current available bandwidth BR-Accept returned by BPCF is greater than or equal to BR-Allocaton, execute Step S1007; otherwise, execute step S1012;

(b4) If the access mode of the HeNB is closed mode, then H(e)NBPolicyFunction connects the bearer (PDP context) with other bearer (PDP context) authorized by BPCF or Compared with the BPCF-authorized bearer (PDP context) established by other users accessed by the same H(e)NB, if the bearer (PDP context) cannot preempt the resources of other bearers (PDP context), execute step S1012. If the bearer (PDP context) can preempt the resources of other bearers (PDP context), and the sum of the bandwidth BR-Allocation' and the current available bandwidth returned by BPCF is greater than or equal to BR- Allocation, execute step S1007; otherwise, execute step S1012;

In other embodiments, when H(e)NBPolicyFunction makes a decision, it only makes decisions according to the CSG membership relationship of the user corresponding to the bearer (PDP context), that is, for the H(e)NB in mixed mode, it judges the bearer (PDP context) of the CSG member user. Context) can preempt the resource of the bearer (PDP context) authorized by the BPCF of the non-CSG member user. For other modes of H(e)NB, no further decision is made;

In other embodiments, H(e)NBPolicyFunction makes a decision only according to the ARP system corresponding to the bearer (PDP context), and judges whether the bearer (PDP context) can preempt the resources of other bearers (PDP context) authorized by BPCF ;

Step S1007: H(e)NBPolicyFunction sends a bearer (PDP context) deactivation indication to H(e)NBGW, carrying the preempted QoS request bearer (PDP context) identifier;

Step S1008: H(e)NBGW initiates the release of resources of the preempted bearer (PDP context) according to the bearer (PDP context) identifier;

If the bandwidth BR-Allocation' and BR-Allocation of the preempted bearer (PDP context) are not equal, then H(e)NBPolicyFunction needs to interact with BPCF, if BR-Allocation'>BR-Allocation, then H(e)NBPolicyFunction BPCF will be requested to release the balance bandwidth BR-Allocation'-BR-Allocation; otherwise, H(e)NBPolicyFunction will request BPCF to allocate the balance bandwidth BR-Allocation-BR-Allocation'.

Step S1009: The H(e)NBPolicyFunction returns a Bearer Authorization Response message to the H(e)NBGW, carrying an acceptance indication. This message is the response message of step S1003;

Step S1010: H(e)NBGW sends a radio access bearer assignment request/bearer establishment request message to H(e)NB;

Step S1011: After the H(e)NB performs the corresponding operation, it returns a response message; the H(e)NBGW further returns a bearer establishment or radio access bearer assignment response message to the MME or SGSN, carrying an acceptance indication. The process ends.

Step S1012: The H(e)NBPolicyFunction returns a Bearer Authorization Response message to the H(e)NBGW, carrying a rejection indication. This message is the response message of step S1003;

Step S1013: The H(e)NBGW returns a bearer establishment or radio access bearer assignment response message to the MME or SGSN, carrying a rejection indication. The process ends.

Example 4

Fig. 11 is another interaction process between H(e)NBPolicyFunction and BPCF during bearer (PDN context) activation/modification/deactivation process according to an embodiment of the present invention. The process includes the following steps:

Step S1101: MME or SGSN receives an activation/modification/deactivation bearer (PDP context) request message from the core network;

Step S1102: MME or SGSN sends activation/modification/deactivation bearer request or radio access bearer assignment request to H(e)NBGW to carry activation/modification/deactivation indication;

Step S1103: After the H(e)NBGW receives the above message, the H(e)NBGW sends an activation/modification/deactivation bearer request or a radio access bearer assignment request carrying an activation/modification/deactivation indication to the H(e)NB;

Step S1104: After the H(e)NB performs the corresponding operation, it returns a response message; the H(e)NBGW further returns to the MME or the SGSN a bearer activation/modification/deactivation request or a radio access bearer assignment request carrying an acceptance indication. At this time, the establishment of the radio bearer requested by the UE is completed. That is, the H(e)NBGW first allows bearer activation/modification/deactivation by default.

Step S1105: This step is executed simultaneously with step S1103. After receiving the above message, H(e)NBGW sends a message requesting bearer authorization to H(e)NBPolicyFunction,

If it is an activation request, the message carries the H(e)NBIP address, QoS request bearer identifier, and QoS information. If the H(e)NB is in hybrid mode, it will also carry the CSG membership indication of the UE. The QoS request bearer identifier is used to uniquely identify the bearer when H(e)NBGW interacts with H(e)NBPolicyFunction. The QoS request bearer identifier can be allocated by H(e)NBGW, or can be embodied by a combination of user identifier and EPS bearer identifier (EPS system) or a combination of user identifier and NSAPI (UMTS system);

If it is a modification request, the message carries the QoS request bearer identifier and QoS information;

If it is a deactivation request, the message carries the QoS request bearer identifier.

For the UMTS system, for the Non-GBR PDP context, the QoS information includes at least Traficclass, Allocation/RetentionPriority, and MBR; for the GBR PDP context, the QoS information includes at least Traficclass, Allocation/RetentionPriority, GBR, and MBR.

For the EPS system, for the Non-GBR bearer, the QoS information includes QCI, ARP, and MBR; for the GBR bearer, the QoS information includes QCI, ARP, GBR, and MBR.

Step S1106: For the activation request, H(e)NBPolicyFunction determines the CPEIP address according to the H(e)NBIP address, uses the S9* session established in Figure 5 to request QoS authorization from BPCF, and carries the requested bandwidth BR-Allocation and the requested allocated resources instruct;

Among them, if the QoS information obtained from H(e)NBGW contains GBR, then BR-Allocation can be set as GBR in the QoS information;

If the QoS information obtained from H(e)NBGW does not include GBR, then H(e)NBPolicyFunction can execute two strategies:

(1) Set BR-Allocatio according to MBR or UE-AMBR and local policy

(2) H(e)NBPolicyFunction processes locally, and does not request QoS authorization from BPCF.

For the modification request, H(e)NBPolicyFunction determines the S9* session according to the QoS request bearer ID, and requests the BPCF for QoS authorization to pass through S9.

If the QoS information obtained from H(e)NBGW contains GBR, then BR-Allocation can be set as the difference between the GBR in the QoS information before and after the update. If the bandwidth is increased after the update, H(e)NBPolicyFunction sends a message to BPCF Carry the bandwidth BR-Allocation requested for allocation and the resource allocation request indication; if the bandwidth is reduced after the update, H(e)NBPolicyFunction carries the bandwidth BR-Release request for release and the resource release indication for the BPCF message

If the QoS information obtained from H(e)NBGW does not include GBR, then H(e)NBPolicyFunction can execute two strategies:

(1) Set new bandwidth according to MBR or UE-AMBR and local policy, and set BR-Allocation or BR-Release according to the difference before and after the update.

(2) H(e)NBPolicyFunction processes locally, and does not request QoS authorization from BPCF.

Step S1107: If bandwidth allocation is requested, BPCF performs admission control according to the BR-Allocation and the current resource situation of the fixed network Backhaul accessed by the H(e)NB, and returns a response message to the H(e)NBPolicyFunction. If the current available bandwidth is greater than or equal to BR-Allocation, BPCF returns an acceptance indication; if the current available bandwidth message is BR-Allocation, BPCF rejects the indication, and at the same time can carry acceptable bandwidth BR-Accept. If the bandwidth is requested to be released, the BPCF returns an acceptance indication.

Step S1108: H(e)NBPolicyFunction executes the following policy decisions according to the return message from BPCF.

(a) If the H(e)NBPolicyFunction receives an acceptance indication, execute step S1111;

(b) If H(e)NBPolicyFunction receives a rejection indication, then H(e)NBPolicyFunction further performs admission control:

(b1) If the access mode of H(e)NB is open mode, H(e)NBPolicyFunction will combine this bearer (PDP context) with other bearer (context) authorized by BPCF established by the user according to ARP (Allocation/RetentionPriority) ) and other bearers (PDP context) authorized by BPCF established by other users accessed by the same H(e)NB:

If the bearer (PDP context) cannot preempt other bearer (PDP context) resources (the ARP (Allocation/RetentionPriority) of the bearer (PDP context) is lower than the ARP (Allocation/RetentionPriority) of other bearers (PDP context)), then execute Step S1112;

If the bearer (PDP context) can preempt the resources of other bearers, and the sum of the bandwidth BR-Allocation' of other bearers (PDP context) and the current available bandwidth BR-Accept returned by BPCF is greater than or equal to BR-Allocation, then execute Step S1109; otherwise, execute step S1112;

(b2) If the HeNB access mode is hybrid mode, and the UE membership corresponding to the bearer (PDP context) is a non-CSG user, then:

(b21) If there are other BPCF-authorized bearers (PDP contexts) established by the user itself or other BPCF-authorized bearers (PDP contexts) established by other non-CSG users accessed through the same H(e)NB, then H(e)NBPolicyFunction compares the bearer (PDP context) with other bearers (PDP context) according to ARP (Allocation/RetentionPriority), if the bearer (PDP context) cannot preempt resources of other bearers (PDP context), then execute step S1112 ; If the bearer (PDP context) can preempt the resources of other bearers (PDP context), and can preempt the bandwidth of other bearers (PDP context) BR-Allocation' and the current available bandwidth BR-Accept returned by BPCF is greater than or equal to BR -Allocation, execute step S11109; otherwise, execute step S1112;

(b22) If there is no other BPCF-authorized bearer (PDP context) established by the user itself or other BPCF-authorized bearer (PDP context) established by other non-CSG users accessed through the same H(e)NB , execute step S1012.

(b3) If the access mode of the HeNB is hybrid mode, and the membership of the UE corresponding to the bearer (PDP context) is a CSG user, then:

(b31) If there are other BPCF-authorized bearers (PDP contexts) established by other non-CSG users accessed through the H(e)NB, and this bearer (PDP context) can preempt the BPCF-authorized bearers established by other non-CSG users The sum of the bearer (PDP context) bandwidth BR-Allocation' and the current available bandwidth BR-Accept returned by BPCF is greater than or equal to BR-Allocation, then execute step S1109; ) the bearer (PDP context) with other bearers (PDP context) authorized by the BPCF established by the user or other bearers authorized by the BPCF established by other CSG users accessed through the same H(e)NB ) for comparison, if the bearer (PDP context) cannot preempt the resources of other bearers (PDP context), then perform step S1112; if the bearer (PDP context) can preempt other bearers (PDP context) authorized by the BPCF established by the CSG user and can preempt the bandwidth BR-Allocation' of other bearers (PDP context) (including bearers established by non-CSG users and bearers established by CSG users) and the current available bandwidth BR-Accept returned by BPCF is greater than or equal to BR- Allocation, execute step S1109; otherwise, execute step S1112;

(b32) If there is no other bearer (PDP context) authorized by BPCF established by a non-CSG user accessed through the same H(e)NB, then H(e)NBPolicyFunction will bearer according to ARP (Allocation/RetentionPriority) ( PDP context) is compared with other BPCF-authorized bearers (PDP context) established by the user itself or other BPCF-authorized bearers (PDP context) established by other CSG users accessed through the same H(e)NB, if If the bearer (PDP context) cannot preempt resources of other bearers (PDP context), step S1112 is executed. If the bearer can preempt the resources of other bearers (PDP context), and the sum of the bandwidth BR-Allocation' of other bearers (PDP context) and the current available bandwidth BR-Accept returned by BPCF is greater than or equal to BR-Allocaton, execute Step S1109; otherwise, execute step S1012;

(b4) If the access mode of the HeNB is closed mode, then H(e)NBPolicyFunction connects the bearer (PDP context) with other bearer (PDP context) authorized by BPCF or Compared with the BPCF-authorized bearer (PDP context) established by other users accessed by the same H(e)NB, if the bearer (PDP context) cannot preempt the resources of other bearers (PDP context), execute step S1012. If the bearer (PDP context) can preempt the resources of other bearers (PDP context), and the sum of the bandwidth BR-Allocation' and the current available bandwidth returned by BPCF is greater than or equal to BR- Allocation, execute step S1109; otherwise, execute step S1112;

In other embodiments, when H(e)NBPolicyFunction makes a decision, it only makes decisions according to the CSG membership relationship of the user corresponding to the bearer (PDP context), that is, for the H(e)NB in mixed mode, it judges the bearer (PDP context) of the CSG member user. Context) can preempt the resource of the bearer (PDP context) authorized by the BPCF of the non-CSG member user. For other modes of H(e)NB, no further decision is made;

In other embodiments, H(e)NBPolicyFunction makes a decision only according to the ARP system corresponding to the bearer (PDP context), and judges whether the bearer (PDP context) can preempt the resources of other bearers (PDP context) authorized by BPCF ;

Step S1109: H(e)NBPolicyFunction sends a bearer (PDP context) deactivation indication to H(e)NBGW, carrying the preempted QoS request bearer identifier;

Step S1110: The H(e)NBGW initiates the release of resources of the preempted bearer (PDP context) according to the bearer ID of the QoS request. For EPS, if the default bearer is released, it will cause the network to reject the UE's access or disconnect the PDN connection. The process ends. ;

If the bearer (PDP context) bandwidth BR-Allocation' and BR-Allocation are not equal, then H(e)NBPolicyFunction needs to interact with BPCF, if BR-Allocation'>BR-Allocation, then H(e)NBPolicyFunction will request BPCF releases the balance bandwidth BR-Allocation'-BR-Allocation; otherwise, H(e)NBPolicyFunction will request BPCF to allocate the balance bandwidth BR-Allocation-BR-Allocation'.

Step S1111: The H(e)NBPolicyFunction returns a Bearer Authorization Response message to the H(e)NBGW, carrying an acceptance indication. This message is the response message of step S1105. The process ends. H(e)NBGW approves the radio bearer established in step S1104;

Step S1112: H(e)NBPolicyFunction returns a bearer authorization response message to H(e)NBGW, carrying a rejection indication. This message is the response message of step S1105;

Step S1113: The H(e)NBGW initiates a PDP context deactivation procedure/bearer deactivation procedure, and releases the bearer requested by the UE to be established in step S1104. For EPS, if the default bearer is rejected, it will cause the network to reject the UE's access or disconnect the PDN connection. The process ends.

In the above embodiments 1-4, H(e)NBPolicyFunction uses different strategies to determine the preempted bearer according to the mode of the home base station, and the strategy formulated by the system can be flexibly formulated and changed, such as:

In other embodiments, when H(e)NBPolicyFunction makes an admission control decision, it only proceeds according to the CSG membership relationship of the user corresponding to the bearer (PDP context), that is, for the H(e)NB in mixed mode, it judges the bearer of the CSG member user (PDP Context) Whether to preempt resources of BPCF-authorized bearer (PDP Context) of non-CSG member users. For other modes of H(e)NB, no further decision is made;

Or, when H(e)NBPolicyFunction makes an admission control decision, it only proceeds according to the ARP corresponding to the bearer (PDP context), and judges whether the bearer (PDP context) can preempt the resources of other bearers (PDP context) authorized by BPCF.

In addition, in Embodiments 2 and 4, when H(e)NBGW sends a message requesting bearer authorization to H(e)NBPolicyFunction, it also sends a message requesting bearer-related operations to H(e)NB at the same time, that is, H(e) The NBGW first allows bearer activation/modification/deactivation by default, and then, when the BPCF indicates authorization or denial of the QoS authorization request for the corresponding bearer but the resource preemption succeeds, it can speed up the bearer establishment/activation/modification/deactivation process. Understandably, when the bearer authorization response indicates that the authorization is denied, the H(e)NBGW needs to initiate a deactivation procedure of the unauthorized bearer.

For HeNB access, and there is no H(e)NBGW scenario, the mobility management network element (such as the MME in the EPS system) replaces the H(e)NBGW to implement the function of the bearer authorization request end, and the corresponding modification does not involve this The essence of the invention applies equally to the present invention. That is, when the MME receives an initial attach or service request from the UE, or the MME receives a bearer activation/modification/deactivation request from the core network, the MME initiates the interaction with the H(e)NBPolicyFunction, and other steps are performed accordingly Modifications.

According to the above embodiment 1 to embodiment 4, the resource management method of the present invention can also be described as including the following steps:

A. The home base station gateway or the mobility management network element requests a bearer authorization message from the home base station policy function (H(e)NBPolicyFunction);

B. The home base station policy function requests QoS authorization from the broadband policy control framework (BPCF) after receiving the message requesting bearer authorization;

C. The BPCF sends a response message requesting QoS authorization to the home base station policy function after receiving the message requesting QoS authorization;

D. When the response message requesting QoS authorization indicates rejection, the home base station policy function performs admission control according to a preset policy.

In this method, judging that the HNB policy function performs admission control according to a preset policy includes:

The home base station policy function determines whether the bearer requesting QoS authorization preempts other bearer resources according to a preset policy;

When preemption is judged, the HNB policy function triggers a deactivation process of the preempted bearer.

When preemption is judged, the HNB policy function also sends a response message indicating acceptance of bearer authorization to the bearer authorization requesting end, otherwise sends a response message indicating rejection of bearer authorization to the requesting end.

When the response message to the request for QoS authorization indicates that the authorization is rejected, it also carries current available resource information; the available resource after the resource preemption is the sum of the current available resource and the preempted resource.

The home base station policy function judges the resources to be preempted, and if the preempted resources are greater than the resources allocated by the current bearer request, then request the BPCF to release the resource difference; if the preempted resources are less than the resources allocated by the current bearer request, then request the BPCF to allocate the balance resource.

The message requesting bearer authorization carries a QoS request bearer identifier. When the home base station policy function initiates a bearer deactivation process, the message that triggers the deactivation of the preempted bearer carries the QoS request bearer identifier of the preempted bearer. The QoS The requested bearer ID is assigned by the bearer authorization requester or embodied by a combination of the user ID and the network bearer ID.

The message requesting QoS authorization carries the resource allocated by the current bearer request, and the resource allocated by the current bearer request is the guaranteed bit rate (GBR) or the home base station function policy according to the maximum bit rate (MBR), the terminal aggregation maximum bit rate ( UE-AMBR) set the bit rate.

When the HNB gateway or the mobility management network element sends a message requesting bearer authorization, it simultaneously sends a message requesting bearer-related operations to the HNB.

In order to realize the above method, the present invention also provides a home base station policy function, as shown in Figure 13, the home base station policy function (H(e)NBPolicyFunction) includes:

The message receiving module is configured to receive a response message requesting QoS authorization sent by the Broadband Policy Control Framework (BPCF);

The admission control module is connected with the message receiving module, and is used for judging whether the bearer requesting QoS authorization preempts other bearer resources according to a preset strategy when the response message indicates that authorization is denied.

Further, the home base station policy function also includes a message sending module, which is connected to the message receiving module and the admission control module, and is used to send an indication to the corresponding bearer authorization requesting end when the admission control module judges preemption The bearer authorization response message and the message triggering the deactivation of the preempted bearer, when the admission control module judges not to preempt, send a response message indicating to reject the bearer authorization to the requesting end.

The strategies are:

Enforce admission control based on Closed Subscriber Group (CSG) membership, where the femtocell mode is Hybrid; or,

Perform admission control based on Allocation Preservation Priority (ARP); or,

When the HNB is in open mode or closed mode, admission control is performed according to ARP; when the HNB mode is hybrid mode, admission control is performed according to Closed Subscriber Group (CSG) membership and/or ARP.

The strategies can be formulated flexibly according to needs, including but not limited to the following:

Strategy 1: When the home base station mode is hybrid mode, when the user corresponding to the bearer is a closed subscriber group (CSG) member, the bearer preempts the resources carried by other non-CSG member users;

Strategy 2: According to Allocation Preservation Priority (ARP), the bearer preempts resources of other user bearers.

Strategy 3: sub-mode strategy:

When the home base station is in the open mode or the closed mode, according to the allocation retention priority (ARP), the bearer preempts the resources of other user bearers;

When the home base station mode is a hybrid mode, when the user corresponding to the bearer is a closed subscriber group (CSG) member, the bearer preempts resources carried by non-CSG member users and/or preempts resources carried by other CSG member users according to ARP; When the user corresponding to the bearer is a non-CSG member, the bearer preempts the resources of other non-CSG member user bearers according to the Allocation Preservation Priority (ARP).

In the above sub-mode strategy, when the HNB is in hybrid mode and the user corresponding to the bearer is a CSG member, the preempted bearer is selected in the order of first selecting from the bearers of non-CSG members, and then selecting from the bearers of CSG members.

The preempted bearers are one or more, and the resource of the one or more preempted bearers is greater than or equal to the resource allocated by the bearer request.

When the response message to the request for QoS authorization indicates that the authorization is rejected, it also carries current available resource information; the available resource after the resource preemption is the sum of the current available resource and the preempted resource.

When the admission control module judges that resources are preempted and the preempted resources are greater than the resources allocated by the current bearer request, the message sending module is also used to send a message requesting to release the difference resources to the BPCF; When the preempted resource is less than the resource allocated by the current bearer request, the message sending module is further configured to send a message requesting to allocate the difference resource to the BPCF.

The message requesting bearer authorization carries a QoS request bearer identifier. When the home base station policy function initiates a bearer deactivation process, the message that triggers the deactivation of the preempted bearer carries the QoS request bearer identifier of the preempted bearer. The QoS The requested bearer ID is assigned by the bearer authorization requester or embodied by a combination of the user ID and the network bearer ID.

The present invention also provides a resource management system, which includes:

The home base station gateway or mobility management network element is used to send a message requesting bearer authorization to the home base station policy function (H(e)NBPolicyFunction);

The BPCF is configured to receive a message requesting QoS authorization, and send a response message requesting QoS authorization to the home base station policy function;

The home base station policy function includes a message receiving module, a message sending module connected to the message receiving module, and an admission control module connected to the message sending module and the message receiving module, wherein the message receiving module is used to receive the requested bearer An authorized message and a message requesting QoS authorization; the message sending module is used for the message receiving module to request QoS authorization from the broadband policy control framework (BPCF) after receiving the message requesting bearer authorization;

The admission control module is configured to perform admission control according to a preset policy when the response message indicates that authorization is denied.

Further, the admission control refers to judging whether the bearer requesting QoS authorization preempts other bearer resources according to a preset policy; The authorization requester sends a message that triggers the deactivation of the preempted bearer.

Further, the message sending module of the policy function of the home base station is also configured to send a response message indicating that the bearer authorization is accepted to the requester corresponding to the bearer authorization when the admission control module judges the preemption, and when the admission control module judges When not preempting, send a response message indicating that bearer authorization is rejected to the requesting end.

Further, when the response message to the request for QoS authorization indicates that the authorization is rejected, it also carries current available resource information; the available resource after the resource preemption is the sum of the currently available resource and the preempted resource.

Further, when the admission control module judges that resources are preempted and the preempted resources are greater than the resources allocated by the current bearer request, the message sending module is also used to send a message requesting to release the resource difference to the BPCF; resources and the resources to be preempted are less than the resources requested by the current bearer, the message sending module is further configured to send a message requesting to allocate the difference resources to the BPCF.

Further, the message requesting bearer authorization carries a QoS request bearer identifier, the message triggering the deactivation of the preempted bearer carries the QoS request bearer identifier of the preempted bearer, and the QoS request bearer identifier is authorized by the bearer The allocation of the requesting end or the combination of the user ID and the network bearer ID.

Further, the message requesting QoS authorization carries the resource allocated by the current bearer request, and the resource allocated by the current bearer request is guaranteed bit rate (GBR) or home base station function policy according to maximum bit rate (MBR), terminal aggregation maximum Bit rate (UE-AMBR) sets the bit rate.

Further, when the home base station gateway or the mobility management network element sends a message requesting bearer authorization, it simultaneously sends a message requesting bearer-related operations to the home base station.

Obviously, those skilled in the art should understand that each module or each step of the above-mentioned present invention can be realized by a general-purpose computing device, and they can be concentrated on a single computing device, or distributed in a network formed by multiple computing devices Alternatively, they may be implemented in program code executable by a computing device so that they may be stored in a storage device to be executed by a computing device, and in some cases in an order different from that shown here The steps shown or described are carried out, or they are separately fabricated into individual integrated circuit modules, or multiple modules or steps among them are fabricated into a single integrated circuit module for implementation. As such, the present invention is not limited to any specific combination of hardware and software.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and changes. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included within the protection scope of the present invention.

Claims (35)

1. a method for managing resource, is characterized in that, the method comprises:

Home base station policy function (H (e) NBPolicyFunction) receives the response message that broadband policy controls the request QoS mandate that framework BPCF sends;

During the response message instruction refusal that described request QoS authorizes, described home base station policy function is according to preset strategy execution call access control;

Wherein, described strategy is:

Base station from home be open mode or closed mode time, according to ARP perform call access control;

Base station from home pattern is in mixed mode situation, and when the user of the carrying correspondence that request QoS authorizes is closed subscriber group (CSG) member, described carrying is seized the resource of non-CSG Member Users carrying and/or seized the resource of other CSG Member Users carrying according to ARP; When the user of described carrying correspondence is non-CSG member, keep priority ARP according to distribution, the resource of other non-CSG Member Users carryings is seized in described carrying;

Wherein, base station from home be mixed mode and the user of described carrying correspondence for CSG member time, the selecting sequence being preempted carrying is first select from the carrying of non-CSG member, then select from the carrying of CSG member.

2. the method for claim 1, is characterized in that: described home base station policy function comprises according to preset strategy execution call access control:

According to preset strategy, described home base station policy function judges whether the carrying that described request QoS authorizes seizes other bearing resources;

When judging to seize, described home base station policy function triggers the deexcitation flow process being preempted carrying.

3. method as claimed in claim 2, it is characterized in that: when judging to seize, described home base station policy function also sends to the request end of bearer authorization the response message that bearer authorization is agreed in instruction, otherwise sends the response message of instruction refusal bearer authorization to described request end.

4. the method for claim 1, is characterized in that, described strategy is:

When base station from home pattern is mixed mode, when the user of the carrying correspondence that described request QoS authorizes is closed subscriber group (CSG) member, the resource of other non-CSG Member Users carryings is seized in described carrying; Or,

According to distributing the resource keeping the carrying of priority ARP, described request QoS mandate to seize other users carrying.

5. the method for claim 1, is characterized in that, described strategy is:

Base station from home be open mode or closed mode time, according to distribute keep priority ARP, described request QoS authorize carrying seize other users carrying resource.

6. the method according to any one of claim 2 to 5, is characterized in that: what be preempted is carried as the resource that one or more and described one or more resource being preempted carrying is more than or equal to described carrying request dispatching.

7. the method according to any one of claim 2 to 5, is characterized in that: when the response message instruction refusal that described request QoS authorizes is authorized, carry current available resource information simultaneously; Resource seize after available resources be current available resource and be preempted resource sum.

8. the method according to any one of claim 2 to 5, is characterized in that: described home base station policy function judges preempting resources, if be preempted resource to be greater than current carrying request dispatching resource, then to described BPCF request release difference resource; If be preempted resource to be less than current carrying request dispatching resource, then to described BPCF request dispatching difference resource.

9. the method according to any one of claim 2 to 5, it is characterized in that: in the message of request bearer authorization, carry QoS request bearing identification, when described home base station policy function initiates load bearing deactivation flow process, trigger and be preempted in the message of the deexcitation of carrying the QoS request bearing identification carrying and be preempted carrying, described QoS request bearing identification is distributed by the request end of described bearer authorization or is embodied by user ID and network carrying identifier combination.

10. the method according to any one of claim 2 to 5, it is characterized in that: the resource of carrying current carrying request dispatching in the message that described request QoS authorizes, the resource of described current carrying request dispatching is the bit rate ensureing that bit rate GBR or base station from home function policy are arranged according to maximum bit rate MBR, terminal Aggregate Maximum Bit Rate UE-AMBR.

11. 1 kinds of home base station policy function entities, is characterized in that, this home base station policy function (H (e) NBPolicyFunction) entity comprises:

Message reception module, controls the response message of the request QoS mandate that framework BPCF sends for receiving broadband policy;

Call access control module, is connected with described message reception module, for when described response message instruction refusal is authorized, according to preset strategy execution call access control;

Wherein, described strategy is:

Base station from home be open mode or closed mode time, according to ARP perform call access control;

Base station from home pattern is in mixed mode situation, when the user of the carrying correspondence that described request QoS authorizes is closed subscriber group (CSG) member, described carrying is seized the resource of non-CSG Member Users carrying and/or is seized the resource of other CSG Member Users carrying according to ARP; When the user of described carrying correspondence is non-CSG member, keep priority ARP according to distribution, the resource of other non-CSG Member Users carryings is seized in described carrying;

Wherein, base station from home be mixed mode and the user of described carrying correspondence for CSG member time, the selecting sequence being preempted carrying is first select from the carrying of non-CSG member, then select from the carrying of CSG member.

12. home base station policy function entities as claimed in claim 11, is characterized in that: described call access control refers to and judges whether the carrying that described request QoS authorizes seizes other bearing resources according to preset strategy; Described home base station policy function entity also comprises message transmission module, with described message reception module and call access control model calling, during for judging to seize in described call access control module, the bearer authorization request end to correspondence sends the message triggering and be preempted the deexcitation of carrying.

13. home base station policy function entities as claimed in claim 12, it is characterized in that: the message transmission module of described home base station policy function entity, time also for judging to seize in described call access control module, request end to corresponding bearer authorization sends the response message that bearer authorization is agreed in instruction, sends the response message of instruction refusal bearer authorization when described call access control module judges not seize to described request end.

14. home base station policy function entities as claimed in claim 11, it is characterized in that: described strategy is: when base station from home pattern is mixed mode, when the user of the carrying correspondence that described request QoS authorizes is closed subscriber group (CSG) member, the resource of other non-CSG Member Users carryings is seized in described carrying; Or,

According to distributing the resource keeping the carrying of priority ARP, described request QoS mandate to seize other users carrying.

15. home base station policy function entities as claimed in claim 11, it is characterized in that, described strategy is:

Base station from home be open mode or closed mode time, according to distribute keep priority ARP, described request QoS authorize carrying seize other users carrying resource.

16. home base station policy function entities according to any one of claim 12 to 15, is characterized in that: what be preempted is carried as the resource that one or more and described one or more resource being preempted carrying is more than or equal to described carrying request dispatching.

17. home base station policy function entities according to any one of claim 12 to 15, is characterized in that: when the response message instruction refusal that described request QoS authorizes is authorized, carry current available resource information simultaneously; Resource seize after available resources be current available resource and be preempted resource sum.

18. home base station policy function entities according to any one of claim 12 to 15, it is characterized in that: described call access control module judges preempting resources and is preempted resource when being greater than current carrying request dispatching resource, described message transmission module is also for sending request the message of release difference resource to described BPCF; Described call access control module judges preempting resources and is preempted resource when being less than current carrying request dispatching resource, and described message transmission module is also for sending request the message of distributing difference resource to described BPCF.

19. home base station policy function entities according to any one of claim 12 to 15, it is characterized in that: in the message of request bearer authorization, carry QoS request bearing identification, trigger and be preempted in the message of the deexcitation of carrying the QoS request bearing identification carrying and be preempted carrying, described QoS request bearing identification is distributed by the request end of described bearer authorization or is embodied by user ID and network carrying identifier combination.

20. 1 kinds of method for managing resource, it is characterized in that, the method comprises:

Home base-station gateway or mobile management network element send request the message of bearer authorization to home base station policy function (H (e) NBPolicyFunction);

Controlling framework BPCF to broadband policy after home base station policy function receives the message of described request bearer authorization asks QoS to authorize;

The backward described home base station policy function of message that described BPCF reception described request QoS authorizes sends request the response message that QoS authorizes;

During the response message instruction refusal that described request QoS authorizes, described home base station policy function is according to preset strategy execution call access control;

Wherein, described strategy is:

Base station from home be open mode or closed mode time, according to ARP perform call access control;

Base station from home pattern is in mixed mode situation, when the user of the carrying correspondence that described request QoS authorizes is closed subscriber group (CSG) member, described carrying is seized the resource of non-CSG Member Users carrying and/or is seized the resource of other CSG Member Users carrying according to ARP; When the user of described carrying correspondence is non-CSG member, keep priority ARP according to distribution, the resource of other non-CSG Member Users carryings is seized in described carrying;

Wherein, base station from home be mixed mode and the user of described carrying correspondence for CSG member time, the selecting sequence being preempted carrying is first select from the carrying of non-CSG member, then select from the carrying of CSG member.

21. methods as claimed in claim 20, is characterized in that: sentence described home base station policy function and comprise according to preset strategy execution call access control:

According to preset strategy, described home base station policy function judges whether the carrying that described request QoS authorizes seizes other bearing resources;

When judging to seize, described home base station policy function triggers the deexcitation flow process being preempted carrying.

22. methods as claimed in claim 21, it is characterized in that: when judging to seize, described home base station policy function also sends to the request end of bearer authorization the response message that bearer authorization is agreed in instruction, otherwise sends the response message of instruction refusal bearer authorization to described request end.

23. methods as claimed in claim 21, is characterized in that:

When the response message instruction refusal that described request QoS authorizes is authorized, carry current available resource information simultaneously; Resource seize after available resources be current available resource and be describedly preempted resource sum.

24. methods as claimed in claim 21, is characterized in that: described home base station policy function judges preempting resources, if be preempted resource to be greater than current carrying request dispatching resource, then to described BPCF request release difference resource; If be preempted resource to be less than current carrying request dispatching resource, then to described BPCF request dispatching difference resource.

25. methods as claimed in claim 21, it is characterized in that: in the message of described request bearer authorization, carry QoS request bearing identification, when described home base station policy function initiates load bearing deactivation flow process, trigger and be preempted in the message of the deexcitation of carrying the QoS request bearing identification carrying and be preempted carrying, described QoS request bearing identification is distributed by the request end of described bearer authorization or is embodied by user ID and network carrying identifier combination.

26. methods as claimed in claim 21, it is characterized in that: the resource of carrying current carrying request dispatching in the message that described request QoS authorizes, the resource of described current carrying request dispatching is the bit rate ensureing that bit rate GBR or base station from home function policy are arranged according to maximum bit rate MBR, terminal Aggregate Maximum Bit Rate UE-AMBR.

27. methods as claimed in claim 21, is characterized in that: when home base-station gateway or mobile management network element send request the message of bearer authorization, send request the message of carrying associative operation to base station from home simultaneously.

28. 1 kinds of resource management systems, is characterized in that, this system comprises:

Home base-station gateway or mobile management network element, for sending request the message of bearer authorization to home base station policy function (H (e) NBPolicyFunction);

Broadband policy controls framework BPCF, for receiving the message that request QoS authorizes, and sends request the response message of QoS mandate to described home base station policy function;

The message transmission module that home base station policy function comprises message reception module, is connected with described message reception module, and the call access control module to be connected with described message transmission module and message reception module, wherein, message reception module is for receiving the message of described request bearer authorization and asking the message of QoS mandate; Described message transmission module, controls framework BPCF to broadband policy after receiving the message of described request bearer authorization ask QoS to authorize for message reception module;

Described call access control module, for when described response message instruction refusal is authorized, according to preset strategy execution call access control;

Described strategy refers to, base station from home be open mode or closed mode time, according to ARP perform call access control; Base station from home pattern is in mixed mode situation, when the user of the carrying correspondence that described request QoS authorizes is closed subscriber group (CSG) member, described carrying is seized the resource of non-CSG Member Users carrying and/or is seized the resource of other CSG Member Users carrying according to ARP; When the user of described carrying correspondence is non-CSG member, keep priority ARP according to distribution, the resource of other non-CSG Member Users carryings is seized in described carrying;

Wherein, base station from home be mixed mode and the user of described carrying correspondence for CSG member time, the selecting sequence being preempted carrying is first select from the carrying of non-CSG member, then select from the carrying of CSG member.

29. systems as claimed in claim 28, is characterized in that:

Described call access control refers to and judges whether the carrying that described request QoS authorizes seizes other bearing resources according to preset strategy; Described message transmission module, time also for judging to seize in described call access control module, the bearer authorization request end to correspondence sends the message triggering and be preempted the deexcitation of carrying.

30. systems as claimed in claim 29, it is characterized in that: the message transmission module of described home base station policy function, time also for judging to seize in described call access control module, request end to corresponding bearer authorization sends the response message that bearer authorization is agreed in instruction, sends the response message of instruction refusal bearer authorization when described call access control module judges not seize to described request end.

31. systems as claimed in claim 29, is characterized in that:

When the response message instruction refusal that described request QoS authorizes is authorized, carry current available resource information simultaneously; Resource seize after available resources be current available resource and be describedly preempted resource sum.

32. systems as claimed in claim 29, it is characterized in that: described call access control module judges preempting resources and is preempted resource when being greater than current carrying request dispatching resource, described message transmission module is also for sending request the message of release difference resource to described BPCF; Described call access control module judges preempting resources and is preempted resource when being less than current carrying request dispatching resource, and described message transmission module is also for sending request the message of distributing difference resource to described BPCF.

33. systems as claimed in claim 29, it is characterized in that: in the message of described request bearer authorization, carry QoS request bearing identification, described triggering is preempted in the message of the deexcitation of carrying the QoS request bearing identification carrying and be preempted carrying, and described QoS request bearing identification is distributed by the request end of described bearer authorization or embodied by user ID and network carrying identifier combination.

34. systems as claimed in claim 29, it is characterized in that: the resource of carrying current carrying request dispatching in the message that described request QoS authorizes, the resource of described current carrying request dispatching is the bit rate ensureing that bit rate GBR or base station from home function policy are arranged according to maximum bit rate MBR, terminal Aggregate Maximum Bit Rate UE-AMBR.

35. systems as claimed in claim 29, is characterized in that: when home base-station gateway or mobile management network element send request the message of bearer authorization, send request the message of carrying associative operation to base station from home simultaneously.