CN102387487A

CN102387487A - Service admission control method and system thereof

Info

Publication number: CN102387487A
Application number: CN2010102666004A
Authority: CN
Inventors: 毕以峰; 周晓云; 霍玉臻; 宗在峰
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2010-08-27
Filing date: 2010-08-27
Publication date: 2012-03-21
Also published as: WO2012024997A1

Abstract

The invention discloses a service admission control method. The method comprises the following steps that: when a home evolved NodeB (HeNB)/ a home NodeB (HNB) powers on, an admission control network element acquires authorization resource information from a fixed network; according to the authorization resource information, the admission control network element performs the admission control to a user equipment (UE) accessed from the HeNB/ HNB. The invention also correspondingly discloses a service admission control system. In the invention, under the condition that the UE accesses to a core network through the HeNB/ HNB, only when the fixed network and a mobile network have enough resources, the core network admits the service initiated by the UE. Therefore, by using the method and the system of the invention, service admission control performance of the system can be raised; simultaneously, a system resource management capability can be raised so as to guarantee quality of service (QoS) when the UE accesses to the service and improve user experience.

Description

Method and system for controlling service admission

Technical Field

The present invention relates to the field of wireless communications, and in particular, to a method and system for controlling service admission.

Background

An Evolved Packet System (EPS) of the third Generation Partnership Project (3rd Generation Partnership Project (3 GPP) is composed of an Evolved universal Terrestrial Radio Access Network (E-UTRAN), a Mobility Management Entity (MME), a Serving Gateway (S-GW), a Packet Data Network Gateway (P-GW), and a Home Subscriber Server (HSS).

Fig. 1 is a schematic diagram of an architecture of an evolved Home base station (HeNB) accessing an EPS in a non-roaming scenario according to the related art, where as shown in fig. 1, an MME is connected to an EUTRAN, an S-GW, and a Home base station gateway (HeNB GW) and is responsible for related operations of a control plane such as mobility management, processing of non-access stratum signaling, and management of a user mobility management context; the S-GW is an access gateway device connected with the E-UTRAN, forwards data between the E-UTRAN and the P-GW, and is responsible for caching paging waiting data; the P-GW is a border gateway between the EPS and a Packet Data Network (PDN) network, and is responsible for accessing the PDN and forwarding data between the EPS and the PDN.

If the EPS system supports Policy and Charging Control (PCC), a Policy and Charging Rules Function (PCRF) makes Policy and Charging Rules, and connects to an Application Function (AF) in an operator network Protocol (IP) service network through an interface Rx to obtain service information for generating service information of the PCC Policy. When an S5 interface between the S-GW and the P-GW adopts a GTP protocol, a Policy and Charging Enforcement Function (PCEF) resides in the P-GW, and the PCRF exchanges information with the P-GW through a Gx interface, and is responsible for initiating establishment, modification, and release of bearers, ensuring Quality of Service (QoS) of Service data, and performing Charging control. When an S5 interface of the S-GW and the P-GW adopts Proxy Mobile IP (PMIP), a Bearer Binding and Event Reporting Function (BBERF) resides in the S-GW, and the S-GW and the PCRF exchange information through a Gxc interface, and the BBERF is responsible for initiating establishment, modification, and release of a Bearer, ensuring service quality of service data, and performing charging control by the PCEF.

The EPS supports the access of HeNB, which is a small-sized and low-power base station and is deployed in indoor places such as homes, offices, enterprise buildings and the like. Closed Subscriber Group (CSG) is a concept proposed after introducing a home base station. Typically, a user in a home or an enterprise forms a closed subscriber group, which is identified by a CSG ID. The home base stations serving the users within this closed subscriber group have the same CSG ID. When a closed subscriber group is served by only one home base station, the closed subscriber group may also be directly identified using a home base station identification (e.g., BS ID). According to the wish of the home base station manager, the CSG user and/or the non-CSG user can be distinguished into different grades, and the service priority enjoyed by the CSG user and/or the non-CSG user can be different in service quality and service type if the priority is different. The user can access to the home base stations corresponding to a plurality of closed user groups, such as the office and the home of the user, by signing with the operator. The concept of allowing a closed user group list is thus introduced. This list is stored in the user's terminal and in the user data server on the network side.

The usage modes of the home base station are divided into three types: closed mode, mixed mode, and open mode. When the home base station is in a closed mode, only the CSG subscriber to which the home base station belongs can access the base station and enjoy the service provided by the base station; when the home base station is in an open mode, any operator signed user can access the base station, and the home base station is equal to the macro base station; when the femtocell is in the hybrid mode, any operator subscribed user or roaming user is allowed to access, but different levels are distinguished according to the information whether the user subscribes to the CSG, that is, the user subscribing to the CSG has higher service priority when using the hybrid femtocell, and enjoys better service quality and service class.

The HeNB usually accesses a core network (as shown in fig. 1) of the EPS through a leased fixed network line, in order to ensure the Security of the access, a Security Gateway (SeGW) is introduced into the core network for shielding, and data between the HeNB and the SeGW is encapsulated by using internet protocol Security (IPSec). The HeNB can be directly connected to the MME and the S-GW of the core network through the IPSec tunnel established with the SeGW, and can also be connected to the MME and the S-GW through the HeNB GW.

In addition, Universal Mobile Telecommunications System (UMTS) supports access to a home base station hnb (home nodeb). Fig. 2 is a schematic diagram of an architecture of an HNB access UMTS in a non-roaming scenario according to the related art, where the architecture in fig. 2 is similar to that in fig. 1, except that a Serving General Packet Radio Service Support Node (SGSN) is used instead of an S-GW, and a Gateway General Packet Radio Service Support Node (GGSN) is used instead of a P-GW.

In the current research process, some architectural preliminary solutions are already used to implement admission management and resource management for services, as shown in fig. 1, a HeNB Policy Function entity (HeNBPF) is disposed between a 3GPP HeNB subsystem (composed of a SeGW, a HeNB GW, and other network elements, such as HeMS, etc.) and a BroadBand Forum Policy control Function entity (BBF BPCF), to implement admission management for services and resource management for a mobile network.

However, in a scenario where a subscriber accesses a core network through a HeNB/HNB, the QoS of a fixed network line accessed by the HeNB/HNB is generally limited by a subscription between the owner of the HeNB/HNB and the fixed network operator. Therefore, when the UE accesses the 3GPP core network access service through the HeNB/HNB, the required QoS cannot exceed the subscribed QoS of the fixed network line that can be provided by the fixed network operator, otherwise, the QoS of the UE access service cannot be Guaranteed, especially for Guaranteed Bit Rate (GBR) service. Therefore, for 3GPP networks and fixed networks, when a new service is initiated, the service can be admitted only under the condition that the fixed network guarantees sufficient resources/bandwidth and also considers that the mobile network resources are sufficient, otherwise, the service should be rejected.

Disclosure of Invention

In view of this, the main objective of the present invention is to provide a method and a system for controlling service admission, which can improve the performance of the system for controlling service admission and improve the resource management capability of the system, thereby ensuring the QoS of the UE access service and improving the user experience.

In order to achieve the purpose, the technical scheme of the invention is realized as follows:

a method of controlling service admission, comprising:

when an HeNB/HNB is powered on, an admission control network element acquires authorized resource information from a fixed network;

and the admission control network element performs admission control on the user UE accessed from the HeNB/HNB according to the authorization resource information.

The authorized resource information is an authorized quality of service QoS,

the authorized QoS includes one or more of: bandwidth, quality of service class identification, guaranteed bit rate.

Under the condition that the HeNB is powered on, the admission control network element is an evolved home base station gateway HeNB GW, a mobile management unit MME or the HeNB; and under the condition that the HNB is electrified, the admission control network element is a home base station gateway HNB GW or HNB.

Under the condition that the admission control network element is an HeNB GW, when the HeNB is powered on, the admission control network element acquires authorized resource information from a fixed network as follows:

the HeNB is powered on and registered to the HeNB GW, and the HeNB GW requests authorized QoS to the policy function entity of the evolved home base station;

and the evolved home base station strategy functional entity requests authorized QoS to the fixed network resource management unit and feeds the authorized QoS back to the HeNB GW after acquiring the authorized QoS, and the HeNB GW stores the QoS.

When the admission control network element is an HNB GW, and when the HNB is powered on, the admission control network element acquires the authorized resource information from the fixed network:

the HNB is electrified and registered in the HNB GW, and the HNB GW requests authorized QoS to a home base station strategy functional entity;

the strategy function entity of the home base station requests the authorized QoS to the fixed network resource management unit, and feeds the authorized QoS back to the HNB GW after acquiring the authorized QoS, and the HNB GW stores the QoS.

Under the condition that the admission control network element is an MME, when the HeNB is powered on, the admission control network element acquires authorized resource information from the fixed network as follows:

the HeNB is powered on and registered in the MME, and the MME requests authorized QoS from an evolved home base station policy function entity;

and the evolution home base station strategy functional entity requests authorized QoS from the fixed network resource management unit and feeds the obtained authorized QoS back to the MME, and the MME stores the QoS.

When the admission control network element is an HeNB, and the HeNB is powered on, the admission control network element obtains the authorized resource information from the fixed network as follows:

the HeNB is powered on and registered to a HeNB GW/MME, and the HeNB GW/MME requests authorized QoS to an evolved home base station policy function entity; the evolution home base station strategy functional entity requests authorized QoS to a fixed network resource management unit and feeds back the obtained authorized QoS to the HeNB GW/MME; the HeNBGW/MME sends the authorized QoS to the HeNB, which stores the authorized QoS, or,

the HeNB is powered on and requests authorized QoS to an evolved home base station strategy functional entity; and the evolved home base station strategy functional entity requests authorized QoS to the fixed network resource management unit and feeds back the obtained authorized QoS to the HeNB, and the HeNB stores the authorized QoS.

When the admission control network element is an HNB, and the HNB is powered on, the admission control network element acquires the authorized resource information from the fixed network as follows:

the HNB is electrified and registered in the HNB GW, and the HNB GW requests authorized QoS to a home base station strategy functional entity; the strategy functional entity of the home base station requests authorized QoS to a fixed network resource management unit and feeds back the obtained authorized QoS to HNB GW; the HNB GW feeds back the authorized QoS to the HNB, the HNB stores the authorized QoS, or,

after the HNB is electrified, requesting authorized QoS (quality of service) to a home base station strategy functional entity; and the strategy functional entity of the home base station requests the authorized QoS to the fixed network resource management unit and feeds back the obtained authorized QoS to the HNB, and the HNB stores the authorized QoS.

The admission control network element obtains the authorized resource information from the fixed network as follows: and when the authorized resource information changes, the fixed network actively sends the modified authorized resource information to the admission control network element through the femtocell strategy function entity.

The QoS requested to be authorized by the fixed network resource management unit carries tunnel information/local information, the fixed network resource management unit searches a backhaul network where the HeNB/HNB is located according to the tunnel information/local information, and authorizes the QoS for the HeNB/HNB according to the use condition of the current backhaul network resource.

Under the condition that the admission control network element is HeNB GW/HNB GW, the tunnel information/local information is carried by the HeNB/HNB and/or is encapsulated into HeNB/HNB registration information by SeGW and is sent to the HeNB GW/HNB GW; under the condition that the admission control network element is an MME, the tunnel information/local information is carried by the HeNB and/or is encapsulated into HeNB registration information by the SeGW and is sent to the MME; and under the condition that the admission control network element is the HeNB/HNB, the tunnel information/local information is acquired by the HeNB/HNB.

The tunnel information/local information includes one or more of: the fixed network allocates an IP address for the terminal, the SeGW address, the address and port number after NAT conversion, and the HeNB identifier.

The fixed network resource management unit is BPCF, and the evolved home base station strategy functional entity/home base station strategy functional entity is HeNB PF/HNB PF.

The method further comprises the following steps:

the fixed network carries a semi-static indication when returning the authorized resource information to the admission control network element,

and after receiving the semi-static indication, the admission control network element performs admission control according to the authorized resource information without inquiring a fixed network.

The method further comprises the following steps: and the admission control network element records the use state of the current fixed network resource.

The admission control network element performs admission control on the UE accessed from the HeNB/HNB according to the authorization resource information, and comprises the following steps:

when UE accesses the HeNB/HNB, initiates attachment, establishes a PDN connection request, and carries establishment/modification/deletion request through the HeNB/HNB, or initiates a carrying establishment/modification/deletion request on a core network side, the admission control network element performs admission decision according to QoS fed back by a fixed network, namely when fixed network resources are satisfied, the admission control network element accepts the request; and when the fixed network resources are not satisfied, the admission control network element refuses the request, or the admission control network element decides to preempt the existing used resources to satisfy the request.

A system for controlling service admission, comprising: the system comprises a HeNB/HNB, an admission control network element and a fixed network; wherein,

the admission control network element is used for acquiring authorized resource information from the fixed network when the HeNB/HNB is powered on; and according to the authorization resource information returned by the fixed network, carrying out admission control on the UE accessed from the HeNB/HNB;

and the fixed network is used for providing the authorized resource information of the HeNB/HNB.

And the authorized resource information returned by the fixed network is authorized QoS.

When the HeNB is powered on, the admission control network element acquires the authorized resource information from the fixed network as follows:

the HeNB is powered on and registered to the HeNB GW, and the HeNB GW requests authorized QoS from an evolved home base station policy function entity;

When the HNB is powered on, the admission control network element acquires the authorized resource information from the fixed network as follows:

HNB is electrified and registered in HNB GW, and the HNB GW requests authorized QoS to a home base station strategy functional entity;

When the HeNB is powered on, the admission control network element acquires the authorization resource information from the fixed network as follows:

the HeNB is powered on and registered to a HeNB GW/MME, and the HeNB GW/MME requests authorized QoS to an evolved home base station policy function entity; the evolution home base station strategy functional entity requests authorized QoS to a fixed network resource management unit and feeds back the obtained authorized QoS to the HeNB GW/MME; the HeNB BGW/MME feeds back the authorized QoS to the HeNB, the HeNB stores the authorized QoS,

or, the HeNB powers on and requests authorized QoS to the policy function entity of the evolved home base station; and the evolved home base station strategy functional entity requests authorized QoS to the fixed network resource management unit and feeds back the obtained authorized QoS to the HeNB, and the HeNB stores the authorized QoS.

the HNB is electrified and registered in the HNB GW, and the HNB GW requests authorized QoS to a home base station strategy functional entity; the strategy functional entity of the home base station requests authorized QoS to a fixed network resource management unit and feeds back the obtained authorized QoS to HNB GW; the HNB GW feeds back the authorized QoS to the HNB, the HNB stores the authorized QoS,

or, after the HNB is electrified, the HNB requests the authorized QoS to the strategy functional entity of the home base station; and the strategy functional entity of the home base station requests the authorized QoS to the fixed network resource management unit and feeds back the obtained authorized QoS to the HNB, and the HNB stores the authorized QoS.

The fixed network is also used for carrying a semi-static indication when the authorization resource information is returned to the admission control network element;

and the admission control network element is further configured to perform admission control according to the authorized resource information after receiving the semi-static indication, without querying a fixed network.

And the admission control network element is also used for recording the use state of the current fixed network resource.

The method and the system for controlling service admission of the invention admit the service initiated by the UE only when the fixed network and the mobile network are ensured to have enough resources under the scene that the UE is accessed into the core network through the HeNB/HNB, so the invention can improve the performance of the system for controlling service admission and improve the resource management capability of the system, thereby ensuring the QoS of the UE access service and improving the user experience.

Drawings

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

fig. 2 is a schematic architecture diagram of HNB access UMTS in a non-roaming scenario according to the related art;

FIG. 3 is a flow chart illustrating a method for controlling service admission according to the present invention;

fig. 4 is a schematic diagram of a power-on registration process of a HeNB in embodiment 1 of the present invention;

fig. 5 is a schematic flow diagram of an admission control performed by a HeNBGW when a UE is attached by a HeNB or establishes a PDN connection in embodiment 2 of the present invention;

fig. 6 is a schematic flow diagram of an admission control executed by a HeNB when a terminal or a core network side initiates a dedicated bearer establishment or modification operation after a UE is attached by the HeNB in embodiment 3 of the present invention;

fig. 7 is a schematic flowchart of a flow in which a HeNB performs resource update registration when a UE or a core network side initiates a dedicated bearer deactivation operation after the UE attaches to the HeNB according to embodiment 4 of the present invention;

fig. 8 is a flowchart illustrating a procedure that a HeNB performs resource update registration when a terminal or a network side initiates a user detach operation after the terminal attaches to the HeNB in embodiment 5 of the present invention;

fig. 9 is a flowchart illustrating admission control performed by a HeNB GW in embodiment 6 of the present invention;

fig. 10 is a schematic flow chart of an MME acquiring authorized QoS when a HeNB is powered on in embodiment 7 of the present invention;

fig. 11 is a schematic flow chart of a HeNB obtaining authorized QoS when the HeNB is powered on in embodiment 8 of the present invention;

fig. 12 is another schematic flow diagram of a HeNB obtaining authorized QoS when the HeNB is powered on in embodiment 8 of the present invention.

Detailed Description

The basic idea of the invention is: under the scene that the UE is accessed into the core network through the HeNB/HNB, the core network only receives the service initiated by the UE when the fixed network and the mobile network are ensured to have enough resources.

Fig. 3 is a schematic flow chart of a method for controlling service admission according to the present invention, as shown in fig. 3, the method includes:

step 301: and when the HeNB/HNB is electrified, the admission control network element acquires the authorized resource information from the fixed network.

Here, the authorized resource information generally refers to authorized QoS, and the authorized QoS includes one or more of the following: bandwidth, quality of service class identification, guaranteed bit rate. The fixed network refers to a fixed access network, and includes an existing wireless local area network, Asymmetric Digital Subscriber Line (ADSL) access, and the like.

It should be noted that, when the HeNB is powered on, the admission control network element is a HeNB GW, an MME or an HeNB; in the case that the HNB is powered on, the admission control network element is an HNB GW or an HNB, specifically:

when the admission control network element is HeNB GW/HNB GW, the HeNB/HNB is electrified and registers to the HeNB GW/HNB GW, and the HeNB GW/HNB GW requests authorized QoS (namely the QoS which can be ensured by the HeNB/HNB) from the HeNB PF/HNB PF; the HeNB PF/HNB PF requests the authorized QoS to a fixed network resource management unit (BPCF), the HeNB PF/HNB PF acquires the authorized QoS and then feeds the QoS back to the HeNB GW/HNB GW, and the HeNB GW/HNB GW stores the QoS. When UE accesses the HeNB/HNB, UE attaches through the HeNB/HNB, establishes PDN connection, requests for bearer establishment/modification, or a core network side requests for bearer establishment/modification, HeNB GW/HNB GW decides whether the service can be admitted or not according to QoS fed back by a fixed network, the current resource use condition and the existing mechanism thereof.

When the admission control network element is MME, the HeNB is powered on and registered in MME, and the MME requests authorized QoS from HeBPF; the HeNB PF requests authorized QoS from a fixed network resource management unit (BPCF), the HeNB PF acquires the QoS and then feeds the QoS back to the MME, and the MME stores the QoS. When UE accesses the HeNB/HNB, the UE attaches through the HeNB, establishes PDN connection, requests bearer establishment/modification, or a core network side requests the bearer establishment/modification, the MME decides whether the service can be admitted or not according to QoS fed back by the fixed network, the use condition of current resources and the existing mechanism thereof.

When the admission control network element is an HeNB/HNB, the HeNB/HNB can be powered on and registered to a HeNB GW/HNB GW, and the HeNB GW/HNB GW requests authorized QoS from a HeNB PF/HNB PF; the HeNB PF/HNB PF requests the authorized QoS to a fixed network resource management unit (BPCF); the HeNB PF/HNBPF acquires the authorized QoS and feeds the QoS back to the HeNB GW/HNB GW; the HeNB GW/HNB GW feeds the QoS back to the HeNB/HNB, and the HeNB/HNB stores the QoS. Or after the HeNB/HNB is powered on, the authorized QoS (the QoS which can be ensured by the HeNB/HNB) can be requested from the HeNB PF/HNB PF; the HeNB PF/HNB PF requests an authorized QoS to a fixed network resource management unit (BPCF), the HeNB PF/HNB PF acquires the QoS and feeds the QoS back to the HeNB/HNB, and the HeNB/HNB stores the QoS. And then, when the UE accesses the HeNB/HNB, the UE initiates an attachment, a PDN connection establishment request and a request for bearer establishment/modification/deletion through the HeNB/HNB, or a core network side initiates a request for bearer establishment/modification/deletion, the HeNB/HNB decides whether the service can be admitted or not according to the QoS fed back by the fixed network, the use condition of the current resources and the existing mechanism thereof.

Of course, when the authorized resource information changes, the fixed network may also actively send the modified authorized resource information to the admission control network element through the femtocell policy function entity.

It should be noted that, in the above scheme, the admission control network element sends a HeNB policy control function entity (PF) to the HeNB, the HeNB PF carries tunnel information/local information when requesting an authorized QoS from the fixed network BPCF, the BPCF searches a backhaul network where the HeNB/HNB is located according to the tunnel information/local information, and authorizes the QoS for the HeNB/HNB according to a use condition of a current backhaul network resource. The tunnel information/local information includes one or more of the following information: the fixed Network allocates an IP Address for the terminal, the SeGW Address, an Address and a port number after NAT (Network Address Translation) Translation, and the identification of the HeNB.

When the HeNB GW/HNB GW is used as an admission control network element, the tunnel information/local information can be carried by the HeNB/HNB and/or encapsulated by the SeGW into HeNB/HNB registration information and sent to the HeNB GW/HNB GW; when the MME is used as an admission control network element, the tunnel information/local information can be carried by the HeNB and/or encapsulated into HeNB registration information by the SeGW to be sent to the MME; and when the HeNB/HNB is taken as an admission control network element, the tunnel information/local information HeNB/HNB is acquired by the HeNB/HNB.

And the fixed network judges the position of the HeNB and the authorized QoS which can be provided at the position according to the tunnel information/local information. The fixed network can also determine authorized resources by combining the HeNB/HNB grade and other factors.

It should be noted that, when the admission control network element is an HeNB, the admission control network element may register with the MME, and the MME feeds back the authorized QoS to the HeNB/HNB, and the flow is similar to the above registration to the HeNB GW, and will not be described in detail here.

When the fixed network returns the corresponding authorized resource information to the admission control network element, the fixed network can also carry a semi-static indication which indicates that the authorized resource is effective in the registration state of the HeNB/HNB, and the admission control network element can carry out admission control according to the authorized resource information without inquiring the fixed network again after receiving the semi-static indication.

Step 302: and the admission control network element performs admission control on the UE accessed from the HeNB/HNB according to the authorized resource information.

Specifically, when the UE accesses the HeNB/HNB, initiates an attach, a PDN connection establishment request, a bearer establishment/modification/deletion request through the HeNB/HNB, or initiates a bearer establishment/modification/deletion request on the core network side, the admission control network element performs an admission decision according to the QoS fed back by the fixed network, that is, when the fixed network resources are satisfied, the admission control network element accepts the request; and when the fixed network resources are not satisfied, the admission control network element refuses the request, or the admission control network element decides to preempt the existing used resources to satisfy the request.

In general, admission control includes two aspects: 1. admission control of user access/PDN connections; 2. bearer initiated admission control.

Specifically, when the UE accesses the HeNB/HNB, attaches/establishes a PDN connection through the HeNB/HNB, requests bearer establishment/modification, or requests bearer establishment/modification on the core network side, the HeNB/HNB performs admission decision according to QoS fed back by the fixed network.

It should be noted that, the admission control process also relates to related resource management, and generally, when the UE or the core network side initiates detachment, releases PDN connection, and requests bearer release, the admission control network element records the use state of the current fixed network resource.

The invention also provides a system for controlling service admission, which comprises: the system comprises a HeNB/HNB, an admission control network element and a fixed network; wherein,

the HeNB is powered on and registered to a HeNB GW, and the HeNB GW requests authorized QoS from an evolved home base station policy function entity HeNB PF;

the HeNB PF requests the authorized QoS from the fixed network resource management unit BPCF and feeds the authorized QoS back to the HeNB GW after acquiring the authorized QoS, and the HeNB GW stores the QoS.

the HNB is electrified and registered in the HNB GW, and the HNB GW requests authorized QoS from a home base station strategy function entity HNB PF;

the HNB PF requests the authorized QoS from the fixed network resource management unit BPCF, and feeds the authorized QoS back to the HNB GW after acquiring the authorized QoS, and the HNB GW stores the QoS.

the HeNB is powered on and registered to the MME, and the MME requests authorized QoS from the HeNB PF;

the HeNB PF requests the BPCF for authorized QoS, and feeds back the obtained authorized QoS to the MME, and the MME stores the QoS.

the HeNB is powered on and registered to a HeNB GW/MME, and the HeNB GW/MME requests authorized QoS from a HeNB PF; the HeNB PF requests authorized QoS from the BPCF and feeds back the obtained authorized QoS to the HeNB GW/MME; the HeNB GW/MME feeds back the authorized QoS to the HeNB, the HeNB stores the authorized QoS,

or the HeNB powers on and then requests authorized QoS to the HeNB PF; the HeNB PF requests the authorized QoS from the BPCF and feeds the acquired authorized QoS back to the HeNB, and the HeNB stores the authorized QoS.

the HNB is electrified and registered to the HNB GW, and the HNB GW requests authorized QoS to the HNB PF; HNBPF requests authorized QoS to BPCF, and feeds back the obtained authorized QoS to HNB GW; the HNB GW feeds back the authorized QoS to the HNB, the HNB stores the authorized QoS,

or after the HNB is electrified, the authorized QoS is requested to the HNB PF; the HNB PF requests the authorized QoS from the BPCF and feeds the obtained authorized QoS back to the HNB, and the HNB stores the authorized QoS.

The admission control network element obtaining authorized resource information from the fixed network may further be: and when the authorized resource information changes, the fixed network actively sends the modified authorized resource information to the admission control network element through the femtocell strategy function entity.

The technical solution of the present invention is further described in detail with reference to the following examples.

Example 1

In this embodiment, admission control is performed by the HeNB GW. In the power-on registration process of the HeNB, the HeNB gateway (HeNB) acquires authorized QoS information from the fixed network and stores the information. When the terminal is attached, accessed, DN connected and established, bearing is modified, detached or PDN connected and released through the HeNB, the HeNB GW carries out admission control on the service/user according to authorized QoS, service level, user level and the like.

Fig. 4 is a schematic diagram of a power-on registration process of a HeNB in embodiment 1 of the present invention, and as shown in fig. 4, the process includes:

step 401: and the HeNB is powered on and is accessed to the fixed network, and the fixed network allocates a local IP address for the HeNB through a relevant mechanism, wherein the address is used as an external IP address for encapsulating the data packet.

Step 402: the HeNB and the SeGW establish an IPsec tunnel to ensure the security and the integrity of data in the transmission process.

Step 403: and the HeNB registers to the HeMS to acquire the relevant configuration information.

Step 404, the HeNB registers to the HeNB GW. In the registration process, the HeNB GW acquires tunnel information/local information of the IPsec tunnel between the HeNB and the SeGW.

The method for acquiring the tunnel information/local information by the HeNB GW may be as follows: the HeNB carries the tunnel information/local information to the HeNB GW through a registration message sent to the HeNB GW by the HeNB; or when the registration message sent to the HeNB GW by the HeNB passes through the SeGW, the SeGW sends the tunnel information/local information to the HeNB GW; or the SeGW sends the information to the HeNB GW through separate signaling.

Note that this does not necessarily occur during the registration of the HeNB with the HeNB GW.

Step 405- > 406: the HeNB GW sends a resource request message to a fixed network resource management unit (serving as BPCF here) through the HeNB PF, and carries IPsec tunnel information/local information.

Step 407-: the fixed network resource management unit (here, the BPCF serves as) finds a Backhaul network (Backhaul) where the HeNB is located according to the obtained IPsec tunnel information/local information, determines the use condition of the current fixed network resource, authorizes a specific QoS guarantee for the HeNB, and returns a resource request response message to the HeNB GW through the HeNB PF.

The fixed network resource management unit is used by the BPCF, and the specific implementation depends on the specific condition of the fixed network, or may be used by other network elements as a "fixed network resource management unit", or may be implemented by a common negotiation of multiple fixed network resource management units (such as the BPCF and the BNG/BRAS).

The authorized QoS is distributed to the HeNB by the fixed network according to the information of the fixed network resource use condition, the HeNB level, the fixed network user level and the like.

The granted QoS may be information of available bandwidth, guaranteed bit rate, etc.

Step 409: the HeNB GW stores the authorized QoS for subsequent traffic/user admission control and resource management.

Step 410-412: after the HeNB is powered on, the HeNB is in a registered state, the fixed network readjusts the authorized QoS for the HeNB, and at this time, a fixed network resource management unit (BPCF here) pushes the adjusted authorized QoS information to the HeNB GW through the HeNB PF, and the HeNB GW stores the information and is used for subsequent service/user admission control and resource management.

The names of the "resource request", "resource request response", and "resource information update" messages in the above flow are general names, and the specific implementation is that messages with different names can be adopted.

Example 2

Fig. 5 is a schematic flowchart of an admission control performed by a HeNBGW when a UE is attached to a HeNB or establishes a PDN connection in embodiment 2 of the present invention, and as shown in fig. 5, the flow includes:

step 501: the HeNB is powered on and completes registration, and the HeNB GW acquires the QoS authorized by the fixed network.

Step 502: UE initiates an attachment or PDN connection establishment operation, and the wireless side and the core network execute related processing, wherein the related processing comprises air interface, core network signaling transmission, core network bearing establishment, PCC session establishment, strategy issuing and the like.

Step 503: if the flow is the attachment flow, the EPS core network (such as MME) sends an 'initial context establishment request/attachment acceptance' message to the HeNB; if the procedure is PDN connection establishment, the EPS core network (such as MME) sends a message of 'bearing establishment request/PDN connection acceptance' to the HeNB.

A type of operation in which PDN connection establishment is operated: when the terminal is attached to the EPS network, a first PDN connection is established, which is called as default PDN connection; the terminal may then initiate establishment of a second and a third … … PDN connections, establishing a plurality of Additional PDN connections. The PDN connection establishment referred to in the flowchart refers to the establishment of an additional PDN connection, the same applies below.

Step 504: the HeNB GW intercepts an 'initial context establishment request/attachment acceptance' message or a 'bearer establishment request/PDN connection acceptance' message sent to the HeNB by the MME, and makes an admission decision according to the current fixed network resource use condition recorded by the HeNB GW, the resources requested in the interception message, the type and level of the user/PDN connection and the like.

The current fixed network resource use condition recorded by the HeNB GW refers to: the HeNB GW acquires the authorized QoS, namely the fixed network can provide certain resource guarantee for the HeNB. Before the UE initiates attachment or PDN connection establishment through the HeNB, it is possible that other UEs already occupy certain resources (fixed network resources) of the HeNB, and after the HeNB GW deducts the used resources from the authorized resources, the remaining fixed network resource status is referred to as "current fixed network resource usage status" herein.

The result of admission decision by the HeNB GW is: successful admission and refusal of admission. These two cases are discussed in categories below:

in case of successful admission:

and step 505, the HeNB GW forwards an initial context establishment request/attachment acceptance message or a bearer establishment request/PDN connection acceptance message to the HeNB.

Step 506: and completing the attachment/PDN connection establishment of the UE according to the prior art operation flow of the HeNB.

In case of rejection of admission:

step 505': the HeNB GW feeds back an attach/PDN connection establishment failure response to the core network (here, MME).

Step 506': and performing relevant processing on the attachment/PDN connection establishment failure according to the HeNB existing technology.

Example 3

Fig. 6 is a schematic flowchart of a procedure in which, in embodiment 3 of the present invention, after a UE attaches to a HeNB, when a terminal or a core network side initiates a dedicated bearer establishment or modification operation, the HeNB performs admission control, and as shown in fig. 6, the procedure includes:

step 601: the HeNB is powered on and completes registration, the HeNB GW acquires the QoS authorized by the fixed network, and the UE is attached to the EPS network through the HeNB. The UE or the network side initiates the establishment or modification operation of the special bearing, and the message flow is processed by the relevant network element to the EPS core network element MME.

Step 602: if the special bearer establishment process is adopted, the EPS core network (here, a network element MME) sends a 'bearer establishment request/session management request' message to the HeNB; if the flow is the bearing modification flow, the EPS core network (here, a network element MME) sends a message of 'bearing modification request/session management request' to the HeNB.

Step 603: the HeNB GW intercepts a 'bearer establishment request/session management request' message or a 'bearer modification request/session management request' message sent by an MME to the HeNB, and makes an admission decision according to the current fixed network resource use condition recorded by the HeNB GW, the resources requested in the intercepted message, the type and level of the user/bearer and the like.

The result of admission decision by the HeNB GW is: successful admission and denial of admission, both of which are discussed below in categories.

In case of successful admission:

step 604: the HeNB GW will forward a bearer setup request/session management request message or a bearer modification request/session management request message to the HeNB.

Step 605: and completing the dedicated bearer establishment/bearer modification operation according to the HeNB prior art operation flow.

In case of rejection of admission:

step 604': the HeNB GW feeds back an acknowledgement of the dedicated bearer establishment/bearer modification failure to the core network (here, MME).

Step 605': and carrying out related processing on the dedicated bearer establishment/bearer modification failure according to the existing HeNB technology.

Example 4

Fig. 7 is a schematic flowchart of a procedure in which, in embodiment 4 of the present invention, after a UE attaches to a HeNB, when the UE or a core network side initiates a dedicated bearer deactivation operation, the HeNB performs resource update registration, and as shown in fig. 7, the procedure includes:

step 701: the HeNB is powered on and completes registration, the HeNB GW acquires the QoS authorized by the fixed network, and the UE is attached to the EPS network through the HeNB. And the UE or the network side initiates the deactivation operation of the special bearing, and the message flows to an EPS core network element MME through the processing of the related network element.

Step 702: the EPS core network (here, network element MME) sends a "bearer deactivation request" message to the HeNB.

Step 703: the HeNB GW intercepts a 'bearing deactivation request' message sent to the HeNB by the MME, and updates the registered current fixed network resource use condition according to the content in the message.

This step is an optional step.

Step 704: the HeNB GW forwards a 'bearer deactivation request' message to the HeNB.

Step 705: the bearer deactivates the air interface resource, which is the prior art.

Step 706: the HeNB feeds back a bearer deactivation response/bearer context deactivation acceptance message to the core network (here, MME), and carries a success or failure indication.

Step 707: the HeNB GW intercepts a 'bearing deactivation response/bearing context deactivation acceptance' message sent to the MME by the HeNB, and updates the registered current fixed network resource use condition according to the content in the message.

Step 708: the HeNB GW forwards a "bearer deactivation response/bearer context deactivation accept" message to the core network (here, MME). The core network performs relevant processing according to the message.

Example 5

Fig. 8 is a schematic flowchart of a procedure in which, in embodiment 5 of the present invention, after a terminal is attached to a HeNB, and when a terminal or a network side initiates a user detach operation, the HeNB performs resource update registration, as shown in fig. 8, the procedure includes:

step 801: the HeNB is powered on and completes registration, the HeNB GW acquires the QoS authorized by the fixed network, and the UE is attached to the EPS network through the HeNB. And the UE or the network side initiates a user detachment operation, and the message flow is processed by the relevant network element to the EPS core network element MME.

Step 802: the EPS core network (here, network element MME) sends an "S1 interface UE context release order" message to the HeNB.

Step 803: the HeNB GW intercepts an 'S1 interface UE context release command' message sent to the HeNB by the MME, and updates the registered current fixed network resource use condition according to the message.

This step is an optional step.

Step 804: the HeNB GW forwards the "S1 interface UE context release order" message to the HeNB.

Step 805: the bearer deactivates air interface resources and releases Radio Resource Control (RRC) connection.

Step 806: the HeNB feeds back an "S1 interface UE context release complete" message to the core network (here, MME), and carries a success or failure indication.

Step 807: the HeNB GW intercepts an 'S1 interface UE context release completion' message sent to the MME by the HeNB, and updates the registered current fixed network resource use condition according to the content in the message.

Step 808: the HeNB GW forwards an "S1 interface UE context release complete" message to the core network (here, MME). The core network performs relevant processing according to the message.

It should be noted that, this embodiment describes a user detach procedure, and similarly, for PDN connection release, the HeNB GW needs to re-register and record resources, except that the "UE context release command/complete over S1 interface" message is changed to "bearer deactivation request/response" signaling.

Example 6

In this embodiment, after the UE is attached by the HeNB, the UE or the core network side initiates a dedicated bearer establishment/modification operation, and needs to occupy more fixed network resources, the HeNB GW finds that the currently available fixed network resources cannot meet the dedicated bearer, and the HeNB GW performs admission control according to the QoS level of the bearer, the level of the PDN connection to which the bearer belongs, the level of the user to which the bearer belongs, and the like. For example: and if the priority of the newly-built bearer is higher than the priority of the established bearer, the HeNB GW releases the resources by deactivating the established bearer for establishing the newly-built bearer. Fig. 9 is a schematic flowchart of admission control performed by a HeNB GW in embodiment 6 of the present invention, and as shown in fig. 9, the flow includes:

step 901-902: the same as step 601-602.

Step 903: the HeNB GW intercepts a 'bearing establishment request/bearing modification request/session management request' message sent to the HeNB by the MME, and performs admission control according to the message content and the current fixed network resource use condition.

The HeNB GW finds that the currently available fixed network resources can not meet the special load, and performs preemptive admission control according to the QoS level of the load, the level of PDN connection of the load, the level of a user and the like. For example: and if the priority of the newly-built bearer is higher than the priority of the established bearer, the HeNB GW releases resources by deactivating the established bearer, so as to accept the newly-built bearer by preempting the resources of the existing service.

Step 904-905: and the HeNB GW sends a bearer deactivation request to the HeNB, and the HeNB carries out corresponding bearer release.

Step 906-908 the corresponding resource release of the deactivated bearer.

Example 7

In this embodiment, admission control is performed by the MME. In the power-on registration process of the HeNB, the MME acquires and stores authorized QoS information from the fixed network. When a terminal/network performs operations such as HeNB attachment/access/PDN connection establishment/bearer modification/detachment/PDN connection release, the MME performs admission control or manages resources for services/users according to authorized QoS, service level, user level, and the like.

This embodiment is equivalent to migrating functional modules for acquiring authorized QoS information, service admission control, and resource update registration by the HeNB GW to the MME in embodiments 1 to 6.

Since the HeNB GW does not exist, the HeNB registers directly with the MME, which requests authorized QoS from the fixed network through the HeNB PF. The specific flow is shown in fig. 10, and the description of the flow corresponds to that of fig. 4, and the modification is to change the HeNB GW into the MME.

After the MME acquires the authorized QoS, the MME performs admission control and resource registration management functions when the terminal/network attaches/accesses/PDN connection establishment/bearer modification/detach/PDN connection release through the HeNB. Specific embodiments exist corresponding to and similar to embodiments 2 to 6, and no flow chart is given here, and specific differences are described as follows:

in embodiments 2 to 6, before the EPS core network/MME sends a message such as a dedicated bearer establishment request, an initial context establishment, an attach acceptance, a PDN connection acceptance, a bearer modification request, a session management request, and an S1 interface UE context deletion to the HeNB, the MME makes an admission decision according to an authorized QoS/usage status of a current fixed network resource, and then sends an instruction to the HeNB according to a decision result.

Example 8

In this embodiment, the HeNB performs admission control, and the HeNB directly requests the HeNB PF in the power-on registration process to acquire authorized QoS (as shown in fig. 11) or acquires authorized QoS through the HeNB GW and then issues the QoS to the HeNB (as shown in fig. 12), and the HeNB stores authorized QoS information. When the terminal performs operations such as attach, access, PDN connection establishment, bearer modification, detach, PDN connection release, etc. through the HeNB, the HeNB performs admission control or manages resources for a service/user according to authorized QoS, service level, user level, etc.

This embodiment is equivalent to migrating a functional module for controlling admission of a service to a HeNB GW and registering resource update to the HeNB.

The scheme is also suitable for HNB, and only the HeNB, the HeNB GW and the MME are required to be correspondingly changed into HNB, HNB GW and SGSN.

It will be apparent to those skilled in the art that the modules or steps of the present invention described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and alternatively, they may be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, and in some cases, the steps shown or described may be performed in an order different than that described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple ones of them may be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.

The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.

Claims

1. A method for controlling service admission, the method comprising:

2. The method of claim 1, wherein the authorized resource information is authorized quality of service (QoS),

3. The method according to claim 2, characterized in that, in case of HeNB power-on, the admission control network element is an evolved home base station gateway, HeNB GW, a mobility management unit, MME, or a HeNB; and under the condition that the HNB is electrified, the admission control network element is a home base station gateway HNB GW or HNB.

4. The method according to claim 3, wherein when the admission control network element is an HeNB GW, and the HeNB is powered on, the admission control network element obtains the authorized resource information from the fixed network:

5. The method according to claim 3, wherein when the admission control network element is an HNB GW, and when the HNB is powered on, the admission control network element obtains the authorized resource information from the fixed network:

6. The method according to claim 3, wherein when the admission control network element is an MME and the HeNB is powered on, the admission control network element obtains the authorized resource information from the fixed network by:

7. The method of claim 3, wherein when the admission control network element is an HeNB and the HeNB is powered on, the admission control network element obtains the authorized resource information from the fixed network by:

8. The method according to claim 3, wherein when the admission control network element is an HNB, and when the HNB is powered on, the admission control network element obtains the authorized resource information from the fixed network:

9. The method of claim 1, wherein the step of the admission control network element obtaining the authorized resource information from the fixed network comprises: and when the authorized resource information changes, the fixed network actively sends the modified authorized resource information to the admission control network element through the femtocell strategy function entity.

10. The method according to any one of claims 4 to 8, wherein the request for the authorized QoS to the fixed network resource management unit carries tunnel information/local information, and the fixed network resource management unit searches the backhaul network where the HeNB/HNB is located according to the tunnel information/local information, and authorizes the QoS to the HeNB/HNB according to the current usage status of the backhaul network resources.

11. The method of claim 10, wherein in case that the admission control network element is a HeNBGW/HNB GW, the tunnel information/local information is carried by the HeNB/HNB itself and/or is encapsulated by the SeGW into HeNB/HNB registration information to be sent to the HeNB GW/HNB GW; under the condition that the admission control network element is an MME, the tunnel information/local information is carried by the HeNB and/or is encapsulated into HeNB registration information by the SeGW and is sent to the MME; and under the condition that the admission control network element is the HeNB/HNB, the tunnel information/local information is acquired by the HeNB/HNB.

12. The method of claim 11, wherein the tunnel/local information comprises one or more of: the fixed network allocates an IP address for the terminal, the SeGW address, the address and port number after NAT conversion, and the HeNB identifier.

13. The method according to any of claims 4 to 8, wherein the fixed network resource management unit is BPCF, and the evolved home base station policy function entity/home base station policy function entity is HeNB PF/HNB PF.

14. The method of any one of claims 1 to 8, further comprising:

15. The method of any one of claims 1 to 8, further comprising: and the admission control network element records the use state of the current fixed network resource.

16. The method according to any of claims 2 to 8, wherein the admission control network element performs admission control on the UE accessed from the HeNB/HNB according to the authorized resource information by:

17. A system for controlling service admission, the system comprising: the system comprises a HeNB/HNB, an admission control network element and a fixed network; wherein,

18. The system of claim 17, wherein the authorized resource information returned by the fixed network is an authorized quality of service QoS.

19. The system according to claim 16, wherein in case of a HeNB being powered on, the admission control network element is an evolved home base station gateway, HeNB GW, a mobility management unit, MME, or a HeNB; and under the condition that the HNB is electrified, the admission control network element is a home base station gateway HNB GW or HNB.

20. The system of claim 19, wherein when the HeNB is powered on, the admission control network element obtaining the authorized resource information from the fixed network is:

21. The system according to claim 19, wherein when the HNB is powered on, the admission control network element obtaining the authorized resource information from the fixed network is:

22. The system according to claim 19, wherein the admission control network element obtaining the authorized resource information from the fixed network when the HeNB is powered on is:

23. The system of claim 197, wherein the admission control network element obtaining the authorized resource information from the fixed network when the HeNB is powered on is:

24. The system according to claim 19, wherein when the HNB is powered on, the admission control network element obtaining the authorized resource information from the fixed network is:

25. The system of claim 16, wherein the admission control network element obtaining the authorized resource information from the fixed network is: and when the authorized resource information changes, the fixed network actively sends the modified authorized resource information to the admission control network element through the femtocell strategy function entity.

26. The system of any one of claims 20 to 24,

27. The system of claim 26, wherein in case that the admission control network element is a HeNBGW/HNB GW, the tunnel information/local information is carried by the HeNB/HNB itself and/or is encapsulated by the SeGW into HeNB/HNB registration information to be sent to the HeNB GW/HNB GW; under the condition that the admission control network element is an MME, the tunnel information/local information is carried by the HeNB and/or is encapsulated into HeNB registration information by the SeGW and is sent to the MME; and under the condition that the admission control network element is the HeNB/HNB, the tunnel information/local information is acquired by the HeNB/HNB.

28. The system of claim 27, wherein the tunnel/local information comprises one or more of: the fixed network allocates an IP address for the terminal, the SeGW address, the address and port number after NAT conversion, and the HeNB identifier.

29. The system according to any of the claims 20 to 24, wherein the fixed network resource management unit is BPCF, and the evolved home base station policy function entity/home base station policy function entity is HeNB PF/HNB PF.

30. The system of any one of claims 17 to 24,

31. The system of any one of claims 17 to 24,

32. The system according to any of claims 18 to 24, wherein the admission control network element performs admission control on the UE accessed from the HeNB/HNB according to the granted resource information by: