CN102421196A - Resource management method, 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 (EPS) of the 3rd Generation Partnership Project (referred to as 3GPP) consists of the Evolved Universal Terrestrial Radio Access Network (Evolved Universal Terrestrial Radio Access Network, referred to as E -UTRAN), Mobility Management Entity (MME for short), Serving Gateway (S-GW for short), Packet DataNetwork Gateway (P-GW for short), home user server ( Home Subscriber Server, referred to as HSS). 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 (HeNB GW), and is responsible for mobility management, processing of non-access stratum signaling, and management of user mobility management context; S-GW is connected with The access gateway device connected to E-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 (Packet Data Network, referred to as The border gateway of the PDN) network is responsible for accessing the PDN and forwarding data between the EPS and the 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 (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, which is identified by a CSG ID. The femtocells serving users in this CSG have the same CSG ID. When a CSG is served by only one HNB, the CSG may also be directly identified by the HNB identifier (for example, BS ID). 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 access, a Security Gateway (SeGW for short) is introduced into the core network for shielding, and the data between HeNB and SeGW will be encapsulated by IPSec. The HeNB can directly connect to the MME and S-GW of the core network through the IPSec tunnel established between the HeNB and the SeGW, and can also connect to the MME and the S-GW through the HeNB GW (that is, the HeNB GW is optional in the EPS). At the same time, in order to manage the HeNB, a network element: Home eNodeB 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 access service through the HeNB, the required QoS cannot exceed the contracted QoS of the fixed network line that the fixed network operator can provide. Otherwise, the QoS of the UE's access service will not be guaranteed, especially 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 (Home NodeB). 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, referred to as GGSN) replaces P-GW. In UMTS, HNB GW 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 same QoS requirements of these multiple home base stations. Signed QoS guarantee for fixed network lines.

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

Fig. 5 is a flowchart of the interaction between the H(e)NB subsystem and the H(e)NB PolicyFunction 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, Establish an IPSec tunnel. In this process, the SeGW assigns 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)NB Policy Function of the relationship between the CEP IP address and the H(e)NBIP address;

Step S503: After the H(e)NB Policy Function saves the association relationship, it returns an acceptance message;

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

Step S505: H(e)NB GW or MME establishes a T2 session with H(e)NB Policy Function, which carries CSG ID and H(e)NB IP address;

Step S506: H(e)NB Policy Function associates the T2 session with step S502 according to the H(e)NB IP address, thereby obtaining the CPE IP address of the H(e)NB, and H(e)NB Policy Function according to the CPE IP The address determines the BPCF (Broadband Policy Control Framework, Broadband Policy Control Framework) of the BBF access network accessed by the H(e)NB. H(e)NB Policy Function establishes an S9* session to BPCF, carrying the CPE IP address;

Step S507: BPCF returns a response message;

Step S508: H(e)NB Policy Function returns a response message to H(e)NB GW or MME.

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

Fig. 6 is a flowchart of interaction between H(e)NBPolicy Function 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)NB GW;

Step S603: After receiving the above message, the H(e)NB GW sends a message requesting bearer authorization to the H(e)NB Policy Function, and the message carries the H(e)NB IP 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)NB Policy Function determines the CPE IP address according to the H(e)NB IP address, uses the S9* session established in Figure 5 to request QoS authorization from BPCF, and carries QoS information;

Step S605: 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)NB Policy Function. BPCF can accept or reject QoS authorization;

Step S606: H(e)NB Policy Function returns a response message to H(e)NB GW, accepting or rejecting 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)NB GW receives an authorization rejection indication, then the H(e)NB GW will initiate a bearer deletion request or a radio access bearer assignment request requesting release of radio access resources.

Fig. 7 is the interaction process between H(e)NB Policy Function 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)NB GW;

Step S703: After receiving the above message, the H(e)NB GW sends a message requesting bearer authorization to the H(e)NB Policy Function, and the message carries the H(e)NB IP 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: The H(e)NB Policy Function determines the CPE IP address according to the H(e)NB IP address, uses the S9* session established in Figure 5 to request QoS authorization from the BPCF, and carries the 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)NB Policy Function. BPCF can accept or reject QoS authorization;

Step S706: H(e)NB Policy Function returns a response message to H(e)NB GW, accepting or rejecting 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)NB GW receives an indication of authorization rejection, then the H(e)NB GW will initiate a bearer deletion request or a radio access bearer assignment request requesting the release of radio access resources, so as to reject the UE Host/Modify request for .

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 comprising:

The home base station policy function (H(e)NB Policy Function) receives the response message of 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)NB Policy Function) 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)NB PolicyFunction);

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)NBPolicy Function);

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, when the current resources are insufficient, the H(e)NB Policy Function (H(e)NB Policy Function) performs admission control according to a pre-established policy, and releases resources occupied by other bearers. The method is to obtain enough resources for the current bearer, and 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)NB Policy Function (H(e)NB PolicyFunction) performs admission control according to a pre-established policy , obtain sufficient resources for the current bearer by releasing resources occupied by other bearers, and realize resource redistribution 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)NB Policy Function) 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)NB Policy Function 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: MME or SGSN sends a bearer establishment request or radio access bearer assignment request to the H(e)NB GW.

Step S803: After receiving the above message, the H(e)NB GW sends a message requesting bearer authorization to the H(e)NB Policy Function, and the message carries the H(e)NB IP 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)NB GW interacts with H(e)NB Policy Function. The bearer identifier of the QoS request can be assigned by H(e)NB GW, or a combination of user identifier and EPS bearer identifier (for EPS system) or user identifier and network layer service access point identifier (Network layer Service Access Point Identifier, referred to as NSAPI) (that is, the bearer identifier of the UMTS system) (for the UMTS system) combination;

For the UMTS system, for the PDP context of Non-GBR (services that do not require guaranteed bandwidth), the QoS information includes at least Trafic class (service type), ARP (Allocation/RetentionPriority, allocation retention priority), MBR (maximum bit rate); For the PDP context of GBR, the QoS information includes at least Trafic class, ARP, GBR (Guaranteed Bit Rate, guaranteed bit rate), MBR.

For the EPS system, if it is an initial access or request for a PDN connection, the QoS information includes QCI (QoSClass Identifier, Qos Classification 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.

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

Step S804: The H(e)NB Policy Function determines the CPE IP address according to the H(e)NB IP address, uses the S9* session established in Figure 5 to request QoS authorization from the BPCF, and carries the requested bandwidth BR-Allocation and requested allocated resources instruct;

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

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

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

(2) H(e)NB Policy Function 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)NB Policy Function. 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)NB Policy Function executes the following policy decisions according to the return message from BPCF.

(a) If the H(e)NB Policy Function receives an acceptance instruction, execute step S809;

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

(b1) If the access mode of the H(e)NB is the open mode, the H(e)NB Policy Function will share the bearer (PDP context) with the BPCF-authorized other established by the user according to the ARP (Allocation/Retention Priority) Bearer (context) 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)NB Policy Function compares the bearer (PDP context) with other bearers (PDP context) according to ARP (Allocation/RetentionPriority), if the bearer (PDP context) cannot preempt the resources of other bearers (PDP context), execute Step S812: If the bearer (PDP context) can preempt 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 If it is equal to the requested 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 bandwidth BR-Allocation requested for allocation, then step S807 is performed; otherwise, H(e)NB Policy Function further According to ARP (Allocation/RetentionPriority), this bearer (PDP context) is established with other bearers (PDP contexts) authorized by BPCF established by the user itself or 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 the BPCF authorized resources of other bearers (PDP context), 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 currently available bandwidth BR-Accept returned by BPCF sum is greater than or equal to the bandwidth BR-Allocation requested for allocation, then 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 the H(e)NB Policy Function is based on ARP (Allocation/Retention Priority) Connect the bearer (PDP context) with other bearers (PDP context) authorized by BPCF established by the user itself or other bearers (PDP context) authorized by BPCF established by other CSG users accessed through the same H(e)NB In comparison, 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 HeNB is closed mode, then H(e)NB Policy Function will combine the bearer (PDP context) with other bearers (PDP context) authorized by BPCF established by the user according to ARP (Allocation/Retention Priority). context) or 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 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)NB Policy Function sends a bearer (PDP context) deactivation indication to H(e)NB GW, carrying the preempted bearer (PDP context) identifier;

Step S808: The H(e)NB GW initiates the release of resources of the preempted bearer (PDP context) according to the bearer (PDP context) identifier. 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 the H(e)NB Policy Function needs to interact with BPCF, if BR-Allocation'>BR-Allocation , then H(e)NB Policy Function will request BPCF to release the balance bandwidth BR-Allocation'-BR-Allocation; otherwise, H(e)NB Policy Function will request BPCF to allocate balance bandwidth BR-Allocation-BR-Allocation.

Step S809: The H(e)NB Policy Function returns a bearer authorization response message to the H(e)NB GW, carrying an acceptance indication. This message is the response message of step S803;

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

Step S811: After the H(e)NB performs the corresponding operation, it returns a response message; the H(e)NB GW 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)NB Policy Function returns a bearer authorization response message to the H(e)NB GW, carrying a rejection indication. This message is the response message of step S803;

Step S813: The H(e)NB GW returns a bearer establishment or radio access bearer assignment response message to the MME or 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)NB Policy Function 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: MME or SGSN sends a bearer establishment request or radio access bearer assignment request to the H(e)NB GW.

Step S903: After the H(e)NB GW receives the above message, the H(e)NB GW 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)NB GW 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)NB GW first allows the establishment of the bearer by default.

Step S905: At the same time as step S903, H(e)NB GW sends a message requesting bearer authorization to H(e)NBH(e)NB PolicyFunction, the message carries H(e)NB IP 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)NB GW interacts with H(e)NB Policy Function. The QoS request bearer identifier can be allocated by H(e)NB GW, 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 Trafic class, 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.

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

Step S906: The H(e)NB Policy Function determines the CPE IP address according to the H(e)NB IP address, uses the S9* session established in Figure 5 to request QoS authorization from the BPCF, and carries the requested bandwidth BR-Allocation and requested allocated resources instruct;

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

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

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

(2) H(e)NB Policy Function 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)NB Policy Function. 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)NB Policy Function executes the following policy decisions according to the return message from BPCF.

(a) If the H(e)NB Policy Function receives an acceptance instruction, execute step S911;

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

(b1) If the access mode of the H(e)NB is the open mode, the H(e)NB Policy Function will share the bearer (PDP context) with the BPCF-authorized other established by the user according to the ARP (Allocation/Retention Priority) Bearer (context) 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)NB Policy Function compares the bearer (PDP context) with other bearers (PDP context) according to ARP (Allocation/RetentionPriority), if the bearer (PDP context) cannot preempt the resources of other bearers (PDP context), execute Step S912: If the bearer (PDP context) can preempt 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 If it is equal to the requested 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 step S909 is performed; otherwise, the H(e)NB Policy Function further According to ARP (Allocation/RetentionPriority), this bearer (PDP context) is established with other bearers (PDP contexts) authorized by BPCF established by the user itself or 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 S912 is performed; if the bearer (PDP context) can preempt the BPCF authorized resources of other bearers (PDP context), 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 currently available bandwidth BR-Accept returned by BPCF sum is greater than or equal to the bandwidth BR-Allocation requested for allocation, then 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 the H(e)NB Policy Function is based on ARP (Allocation/Retention Priority) Connect the bearer (PDP context) with other bearers (PDP context) authorized by BPCF established by the user itself or other bearers (PDP context) authorized by BPCF established by other CSG users accessed through the same H(e)NB In comparison, if the bearer (PDP context) cannot preempt resources of other bearers (PDP context), step S812 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 S909; otherwise, execute step S912;

(b4) If the access mode of HeNB is closed mode, then H(e)NB Policy Function will combine the bearer (PDP context) with other bearers (PDP context) authorized by BPCF established by the user according to ARP (Allocation/Retention Priority). context) or 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 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)NB Policy Function sends a bearer (PDP context) deactivation indication to H(e)NB GW, carrying the preempted QoS request bearer (PDP context) identifier;

Step S910: The H(e)NB GW 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 the H(e)NB Policy Function needs to interact with BPCF, if BR-Allocation'>BR-Allocation , then H(e)NB Policy Function will request BPCF to release the balance bandwidth BR-Allocation'-BR-Allocation; otherwise, H(e)NB Policy Function will request BPCF to allocate balance bandwidth BR-Allocation-BR-Allocation.

Step S911: The H(e)NB Policy Function returns a bearer authorization response message to the H(e)NB GW, carrying an acceptance indication. This message is the response message of step S905. The process ends. The H(e)NB GW approves the radio bearer established in step S904;

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

Step S913: The H(e)NB GW initiates a PDP context deactivation process/bearer deactivation process, 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 flow between H(e)NB Policy Function 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)NB GW to carry activation/modification/deactivation indication;

Step S1003: After receiving the above message, H(e)NB GW sends a message requesting bearer authorization to H(e)NB Policy Function,

If it is an activation request, the message carries the H(e)NB IP 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)NB GW interacts with H(e)NB Policy Function. The QoS request bearer identifier can be allocated by H(e)NB GW, 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/Retention Priority, MBR; for the GBR PDP context, the QoS information includes at least Trafic class, Allocation/Retention Priority, GBR, 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)NB Policy Function determines the CPE IP address according to the H(e)NB IP address, uses the S9* session established in Figure 5 to request QoS authorization from BPCF, and carries the requested bandwidth BR-Allocation and request allocation resource indication;

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

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

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

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

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

If the QoS information obtained from H(e)NB GW 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, the H(e)NBPolicy Function will transfer The message carries the bandwidth BR-Allocation requested for allocation and the resource allocation request indication; if the bandwidth is reduced after the update, the H(e)NB Policy Function sends the BPCF message to carry the bandwidth BR-Release request for release and the resource release indication request

If the QoS information obtained from H(e)NB GW does not include GBR, then H(e)NB PolicyFunction 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)NB Policy Function processes locally, and does not request QoS authorization from BPCF.

Step S1005: If bandwidth allocation is requested, BPCF performs admission control according to BR-Allocation and the current resource situation of the fixed network Backhaul accessed by H(e)NB, and returns a response message to H(e)NB PolicyFunction. 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)NB Policy Function executes the following policy decisions according to the return message from BPCF.

(a) If the H(e)NB Policy Function receives an acceptance instruction, execute step S909;

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

(b1) If the access mode of the H(e)NB is the open mode, the H(e)NB Policy Function will share the bearer (PDP context) with the BPCF-authorized other established by the user according to ARP (Allocation/Retention Priority). Bearer (context) 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/Retention Priority) of the bearer (PDP context) is lower than the ARP (Allocation/Retention Priority) 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)NB Policy Function compares the bearer (PDP context) with other bearers (PDP context) according to ARP (Allocation/RetentionPriority), if the bearer (PDP context) cannot preempt the resources of other bearers (PDP context), execute Step S1012; if the bearer (PDP context) can preempt 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-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 perform step S1007; otherwise, then H(e)NB Policy Function further according to ARP(Allocation /RetentionPriority) and other bearers (PDP context) authorized by BPCF established by the user or other bearers authorized by BPCF established by other CSG users accessed through the same H(e)NB ( PDP context) 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 the BPCF authorized other bearer (PDP context) established by the CSG user context), 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 the H(e)NB Policy Function is based on ARP (Allocation/Retention Priority) Connect the bearer (PDP context) with other bearers (PDP context) authorized by BPCF established by the user itself or other bearers (PDP context) authorized by BPCF established by other CSG users accessed through the same H(e)NB In comparison, if the bearer (PDP context) cannot preempt 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 HeNB is closed mode, then H(e)NB Policy Function will combine the bearer (PDP context) with other bearers (PDP context) authorized by BPCF established by the user according to ARP (Allocation/Retention Priority). context) or 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 the H(e)NB Policy Function makes a decision, it is only based on the CSG membership of the user corresponding to the bearer (PDP context), that is, for the H(e)NB in the mixed mode, the bearer of the CSG member user is judged (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;

In other embodiments, when making decisions, the H(e)NB Policy Function only makes decisions based on the ARP system corresponding to the bearer (PDP context), and judges whether the bearer (PDP context) can preempt other bearers (PDP context) authorized by BPCF H;

Step S1007: H(e)NB Policy Function sends a bearer (PDP context) deactivation indication to H(e)NB GW, carrying the preempted QoS request bearer (PDP context) identifier;

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

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

Step S1009: The H(e)NB Policy Function returns a bearer authorization response message to the H(e)NB GW, carrying an acceptance indication. This message is the response message of step S1003;

Step S1010: H(e)NB GW 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)NB GW 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)NB Policy Function returns a bearer authorization response message to the H(e)NB GW, carrying a rejection indication. This message is the response message of step S1003;

Step S1013: The H(e)NB GW 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 flow between H(e)NB Policy Function 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)NB GW to carry activation/modification/deactivation indication;

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

Step S1104: After the H(e)NB performs the corresponding operation, it returns a response message; the H(e)NB GW further returns to the MME or SGSN to send an activation/modification/deactivation bearer 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)NB GW sends a message requesting bearer authorization to H(e)NB Policy Function,

If it is an activation request, the message carries the H(e)NB IP 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)NB GW interacts with H(e)NB Policy Function. The QoS request bearer identifier can be allocated by H(e)NB GW, 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/Retention Priority, MBR; for the GBR PDP context, the QoS information includes at least Trafic class, Allocation/Retention Priority, GBR, 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)NB Policy Function determines the CPE IP address according to the H(e)NB IP address, uses the S9* session established in Figure 5 to request QoS authorization from BPCF, and carries the requested bandwidth BR-Allocation and request allocation resource indication;

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

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

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

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

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

If the QoS information obtained from H(e)NB GW 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, the H(e)NBPolicy Function will transfer The message carries the bandwidth BR-Allocation requested for allocation and the resource allocation request indication; if the bandwidth is reduced after the update, the H(e)NB Policy Function sends the BPCF message to carry the bandwidth BR-Release request for release and the resource release indication request

If the QoS information obtained from H(e)NB GW does not include GBR, then H(e)NB PolicyFunction 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)NB Policy Function processes locally, and does not request QoS authorization from BPCF.

Step S1107: If bandwidth allocation is requested, BPCF performs admission control according to BR-Allocation and the current resource situation of the fixed network Backhaul accessed by H(e)NB, and returns a response message to H(e)NB PolicyFunction. 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)NB Policy Function executes the following policy decisions according to the return message from BPCF.

(a) If the H(e)NB Policy Function receives an acceptance instruction, execute step S1111;

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

(b1) If the access mode of the H(e)NB is the open mode, the H(e)NB Policy Function will share the bearer (PDP context) with the BPCF-authorized other established by the user according to ARP (Allocation/Retention Priority). Bearer (context) 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/Retention Priority) of the bearer (PDP context) is lower than the ARP (Allocation/Retention Priority) 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)NB Policy Function compares the bearer (PDP context) with other bearers (PDP context) according to ARP (Allocation/RetentionPriority), if the bearer (PDP context) cannot preempt the resources of other bearers (PDP context), execute Step S1112; if the bearer (PDP context) 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 is 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 , 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 perform step S1109; otherwise, H(e)NB Policy Function further according to ARP(Allocation /RetentionPriority) and other bearers (PDP context) authorized by BPCF established by the user or other bearers authorized by BPCF established by other CSG users accessed through the same H(e)NB ( PDP context) 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 the BPCF authorized other bearer (PDP context) established by the CSG user context), 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 the H(e)NB Policy Function is based on ARP (Allocation/Retention Priority) Connect the bearer (PDP context) with other bearers (PDP context) authorized by BPCF established by the user itself or other bearers (PDP context) authorized by BPCF established by other CSG users accessed through the same H(e)NB In comparison, if the bearer (PDP context) cannot preempt resources of other bearers (PDP context), step S1112 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 S1109; otherwise, execute step S1012;

(b4) If the access mode of HeNB is closed mode, then H(e)NB Policy Function will combine the bearer (PDP context) with other bearers (PDP context) authorized by BPCF established by the user according to ARP (Allocation/Retention Priority). context) or 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 the H(e)NB Policy Function makes a decision, it is only based on the CSG membership of the user corresponding to the bearer (PDP context), that is, for the H(e)NB in the mixed mode, the bearer of the CSG member user is judged (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;

In other embodiments, when making decisions, the H(e)NB Policy Function only makes decisions based on the ARP system corresponding to the bearer (PDP context), and judges whether the bearer (PDP context) can preempt other bearers (PDP context) authorized by BPCF H;

Step S1109: H(e)NB Policy Function sends a bearer (PDP context) deactivation indication to H(e)NB GW, carrying the preempted QoS request bearer identifier;

Step S1110: The H(e)NB GW initiates the release of resources of the preempted bearer (PDP context) according to the bearer identifier 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)NB Policy Function needs to interact with BPCF, if BR-Allocation'>BR-Allocation, then H(e)NB The Policy Function will request the BPCF to release the balance bandwidth BR-Allocation'-BR-Allocation; otherwise, the H(e)NB Policy Function will request the BPCF to allocate the balance bandwidth BR-Allocation-BR-Allocation'.

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

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

Step S1113: The H(e)NB GW initiates the PDP context deactivation procedure/bearer deactivation procedure, and releases the bearer requested to be established by the UE 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, the H(e)NB Policy Function 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 the H(e)NB Policy Function makes an admission control decision, it is only performed according to the CSG membership of the user corresponding to the bearer (PDP context), that is, for the H(e)NB in the mixed mode, it judges the CSG member user Whether the bearer (PDP context) of the user 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;

Or, when the H(e)NB Policy Function 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)NB GW sends a message requesting bearer authorization to H(e)NB Policy Function, it simultaneously sends a message requesting bearer-related operations to H(e)NB, that is, H(e)NB (e) NB GW first allows bearer activation/modification/deactivation by default, and then, when BPCF indicates authorization or denial of the QoS authorization request for the corresponding bearer but the resource preemption succeeds, it can speed up the establishment/activation/modification/deactivation of the bearer Activation process. Understandably, when the bearer authorization response indicates that the authorization is denied, the H(e)NB GW needs to initiate a deactivation process of the unauthorized bearer.

For HeNB access, and there is no H(e)NB GW scenario, the mobility management network element (such as MME in the EPS system) replaces the H(e)NB GW to implement the function of the bearer authorization request end, and the corresponding modification does not As far as the essence of the present invention is concerned, the present invention is equally applicable. 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)NB Policy Function, and other steps also Make the corresponding modification.

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)NB PolicyFunction);

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)NB Policy Function) 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)NBPolicy Function);

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 (39)

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

Base station from home policing feature (H (e) NB Policy Function) receives the response message of the request QoS mandate of broadband policy control architecture (BPCF) transmission;

When the response message indication that described request QoS authorizes was refused, said base station from home policing feature was admitted control according to the strategy execution that presets.

2. the method for claim 1 is characterized in that: said base station from home policing feature admits control to comprise according to the strategy execution that presets:

Said base station from home policing feature judges according to the strategy that presets whether the carrying that described request QoS authorizes seizes other bearing resources;

Judge that when seizing, said base station from home policing feature triggers the said deexcitation flow process of being seized carrying.

3. method as claimed in claim 2; It is characterized in that: judge when seizing; Said base station from home policing feature is also sent the response message that bearer authorization is agreed in indication to the request end of bearer authorization, otherwise sends the response message of indication refusal bearer authorization to the described request end.

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

The base station from home pattern is under the situation of mixed mode, carries out according to closed user group (CSG) member relation and admits control; Or,

Keep priority (ARP) to carry out admittance control according to distributing; Or,

When base station from home is open mode or closed mode, carry out admittance control according to ARP; The base station from home pattern is under the mixed mode situation, carries out admittance control according to closed user group (CSG) member relation and/or ARP.

5. method as claimed in claim 4 is characterized in that, said strategy is:

The base station from home pattern is under the situation of mixed mode, and when said user of carrying correspondence was closed user group (CSG) member, the resource that other non-CSG Member Users are carried was seized in said carrying; Or,

Keep priority (ARP) according to distributing, the resource that other users are carried is seized in said carrying.

6. method as claimed in claim 4 is characterized in that, said strategy is:

When base station from home is open mode or closed mode, keep priority (ARP) according to distributing, the resource that other users are carried is seized in said carrying;

The base station from home pattern is under the mixed mode situation, and when said user of carrying correspondence was closed user group (CSG) member, said carrying was seized the resource of non-CSG Member Users carrying and/or seized the resource that other CSG Member Users are carried according to ARP; Said when to carry corresponding user be non-CSG member, keep priority (ARP), said carrying to seize the resource of other non-CSG Member Users carryings according to distributing.

7. method as claimed in claim 6 is characterized in that:

Base station from home is the corresponding user of mixed mode and said carrying during for CSG member, is seized the selecting sequence of carrying and selects from non-CSG member's carrying for first, from CSG member's carrying, selects again.

8. like each described method in the claim 2 to 7, it is characterized in that: said seized be carried as the resource that one or more and said one or more resource of being seized carrying is distributed more than or equal to said carrying request.

9. like each described method in the claim 2 to 7, it is characterized in that: when the response message indication refusal that described request QoS authorizes is authorized, carry current available resource information simultaneously; Available resources behind the said resource race to control are current available resource and said by the preempting resources sum.

10. like each described method in the claim 2 to 7, it is characterized in that: said base station from home policing feature is judged preempting resources, if by preempting resources greater than current carrying request Resources allocation, then discharge the difference resource to said BPCF request; If less than current carrying request Resources allocation, then distributed the difference resource to said BPCF request by preempting resources.

11. like each described method in the claim 2 to 7; It is characterized in that: carry QoS request bearing identification in the message of described request bearer authorization; When said base station from home policing feature is initiated the load bearing deactivation flow process; Triggering is seized in the message of deexcitation of carrying carries the QoS request bearing identification of being seized carrying, and said QoS request bearing identification is distributed by the request end of said bearer authorization or by ID and the embodiment of network carrying identifier combination.

12. like each described method in the claim 2 to 7; It is characterized in that: carry the resource that current carrying request distributes in the message that described request QoS authorizes, the bit rate of the resource that said current carrying request distributes for ensureing that bit rate (GBR) or base station from home function policy are provided with according to maximum bit rate (MBR), terminal Aggregate Maximum Bit Rate (UE-AMBR).

13. a base station from home policing feature is characterized in that, this base station from home policing feature (H (e) NB Policy Function) comprising:

Said message sink module is used to receive the response message that request QoS that broadband policy control architecture (BPCF) sends authorizes;

Said admittance control module is connected with said message sink module, is used for when said response message indication refusal is authorized, admitting control according to the strategy execution that presets.

14. base station from home policing feature as claimed in claim 13 is characterized in that: said admittance control refers to judge according to the strategy that presets whether the carrying that described request QoS authorizes seizes other bearing resources; Said base station from home policing feature also comprises message transmission module; Be connected with said message sink module and admittance control module; Be used for when said admittance control module judgement is seized, sending the message that triggers the deexcitation of being seized carrying to the bearer authorization request end of correspondence.

15. base station from home policing feature as claimed in claim 14; It is characterized in that: the message transmission module of said base station from home policing feature; Also be used for when said admittance control module judgement is seized; The response message that bearer authorization is agreed in indication is sent in request end to corresponding bearer authorization, the response message of when said admittance control module judgement is not seized, sending indication refusal bearer authorization to the described request end.

16. method as claimed in claim 13 is characterized in that, said strategy is:

The base station from home pattern is under the situation of mixed mode, carries out according to closed user group (CSG) member relation and admits control; Or,

Keep priority (ARP) to carry out admittance control according to distributing; Or,

When base station from home is open mode or closed mode, carry out admittance control according to ARP; The base station from home pattern is under the mixed mode situation, carries out admittance control according to closed user group (CSG) member relation and/or ARP.

17. base station from home policing feature as claimed in claim 16; It is characterized in that: said strategy is: the base station from home pattern is under the situation of mixed mode; When said user of carrying correspondence was closed user group (CSG) member, the resource that other non-CSG Member Users are carried was seized in said carrying; Or,

Keep priority (ARP) according to distributing, the resource that other users are carried is seized in said carrying.

18. base station from home policing feature as claimed in claim 16 is characterized in that, said strategy is:

When base station from home is open mode or closed mode, keep priority (ARP) according to distributing, the resource that other users are carried is seized in said carrying;

The base station from home pattern is under the mixed mode situation, and when said user of carrying correspondence was closed user group (CSG) member, said carrying was seized the resource of non-CSG Member Users carrying and/or seized the resource that other CSG Member Users are carried according to ARP; Said when to carry corresponding user be non-CSG member, keep priority (ARP), said carrying to seize the resource of other non-CSG Member Users carryings according to distributing.

19. base station from home policing feature as claimed in claim 18; It is characterized in that; Base station from home is the corresponding user of mixed mode and said carrying during for CSG member, is seized the selecting sequence of carrying and selects from non-CSG member's carrying for first, from CSG member's carrying, selects again.

20., it is characterized in that like each described base station from home policing feature in the claim 14 to 19: said seized be carried as the resource that one or more and said one or more resource of being seized carrying is distributed more than or equal to said carrying request.

21., it is characterized in that: when the response message indication refusal that described request QoS authorizes is authorized, carry current available resource information simultaneously like each described base station from home policing feature in the claim 14 to 19; Available resources behind the said resource race to control are current available resource and said by the preempting resources sum.

22. like each described base station from home policing feature in the claim 14 to 19; It is characterized in that: said admittance control module judges preempting resources and by preempting resources during greater than current carrying request Resources allocation, said message transmission module also is used for discharging to the said BPCF request of sending the message of difference resource; Said admittance control module judges preempting resources and by preempting resources during less than current carrying request Resources allocation, said message transmission module also is used for distributing to the said BPCF request of sending the message of difference resource.

23. like each described base station from home policing feature in the claim 14 to 19; It is characterized in that: carry QoS request bearing identification in the message of described request bearer authorization; Said triggering is seized in the message of deexcitation of carrying carries the QoS request bearing identification of being seized carrying, and said QoS request bearing identification is distributed by the request end of said bearer authorization or by ID and the embodiment of network carrying identifier combination.

24. a method for managing resource is characterized in that, this method comprises:

Home base-station gateway or mobile management network element are to the message of base station from home policing feature (H (e) NB PolicyFunction) request bearer authorization;

Authorize to broadband policy control architecture (BPCF) request QoS after the message of base station from home policing feature reception described request bearer authorization;

Send the response message that request QoS authorizes to said base station from home policing feature after the message that said BPCF reception described request QoS authorizes;

When the response message indication that described request QoS authorizes was refused, said base station from home policing feature was admitted control according to the strategy execution that presets.

25. method as claimed in claim 24 is characterized in that: declare said base station from home policing feature and admit control to comprise according to the strategy execution that presets:

Said base station from home policing feature judges according to the strategy that presets whether the carrying that described request QoS authorizes seizes other bearing resources;

Judge that when seizing, said base station from home policing feature triggers the said deexcitation flow process of being seized carrying.

26. method as claimed in claim 25; It is characterized in that: judge when seizing; Said base station from home policing feature is also sent the response message that bearer authorization is agreed in indication to the request end of bearer authorization, otherwise sends the response message of indication refusal bearer authorization to the described request end.

27. method as claimed in claim 25 is characterized in that: when the response message indication refusal that described request QoS authorizes is authorized, carry current available resource information simultaneously; Available resources behind the said resource race to control are current available resource and said by the preempting resources sum.

28. method as claimed in claim 25 is characterized in that: said base station from home policing feature is judged preempting resources, if by preempting resources greater than current carrying request Resources allocation, then discharge the difference resource to said BPCF request; If less than current carrying request Resources allocation, then distributed the difference resource to said BPCF request by preempting resources.

29. method as claimed in claim 25; It is characterized in that: carry QoS request bearing identification in the message of described request bearer authorization; When said base station from home policing feature is initiated the load bearing deactivation flow process; Triggering is seized in the message of deexcitation of carrying carries the QoS request bearing identification of being seized carrying, and said QoS request bearing identification is distributed by the request end of said bearer authorization or by ID and the embodiment of network carrying identifier combination.

30. method as claimed in claim 25; It is characterized in that: carry the resource that current carrying request distributes in the message that described request QoS authorizes, the bit rate of the resource that said current carrying request distributes for ensureing that bit rate (GBR) or base station from home function policy are provided with according to maximum bit rate (MBR), terminal Aggregate Maximum Bit Rate (UE-AMBR).

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

32. a resource management system is characterized in that, this system comprises:

Home base-station gateway or mobile management network element are used for sending the message of asking bearer authorization to base station from home policing feature (H (e) NBPolicy Function);

Said BPCF is used to receive the message that request QoS authorizes, and sends the response message that request QoS authorizes to said base station from home policing feature;

The base station from home policing feature comprises message sink module, the message transmission module that is connected with said message sink module; And the admittance control module that is connected with the message sink module with said message transmission module; Wherein, the message sink module is used to receive the message of described request bearer authorization and the message that request QoS authorizes; Said message transmission module is used for authorizing to broadband policy control architecture (BPCF) request QoS after the message that the message sink module receives the described request bearer authorization;

Said admittance control module is used for when said response message indication refusal is authorized, admitting control according to the strategy execution that presets.

33. system as claimed in claim 32 is characterized in that: said admittance control refers to judge according to the strategy that presets whether the carrying that described request QoS authorizes seizes other bearing resources; Said message transmission module also is used for when said admittance control module judgement is seized, sending the message that triggers the deexcitation of being seized carrying to the bearer authorization request end of correspondence.

34. 33 system as claimed in claim; It is characterized in that: the message transmission module of said base station from home policing feature; Also be used for when said admittance control module judgement is seized; The response message that bearer authorization is agreed in indication is sent in request end to corresponding bearer authorization, the response message of when said admittance control module judgement is not seized, sending indication refusal bearer authorization to the described request end.

35. system as claimed in claim 33 is characterized in that: when the response message indication refusal that described request QoS authorizes is authorized, carry current available resource information simultaneously; Available resources behind the said resource race to control are current available resource and said by the preempting resources sum.

36. system as claimed in claim 33; It is characterized in that: said admittance control module judges preempting resources and by preempting resources during greater than current carrying request Resources allocation, said message transmission module also is used for discharging to the said BPCF request of sending the message of difference resource; Said admittance control module judges preempting resources and by preempting resources during less than current carrying request Resources allocation, said message transmission module also is used for distributing to the said BPCF request of sending the message of difference resource.

37. system as claimed in claim 33; It is characterized in that: carry QoS request bearing identification in the message of described request bearer authorization; Said triggering is seized in the message of deexcitation of carrying carries the QoS request bearing identification of being seized carrying, and said QoS request bearing identification is distributed by the request end of said bearer authorization or by ID and the embodiment of network carrying identifier combination.

38. system as claimed in claim 33; It is characterized in that: carry the resource that current carrying request distributes in the message that described request QoS authorizes, the bit rate of the resource that said current carrying request distributes for ensureing that bit rate (GBR) or base station from home function policy are provided with according to maximum bit rate (MBR), terminal Aggregate Maximum Bit Rate (UE-AMBR).

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

Images