CN102547873A

CN102547873A - Method and system for controlling resources

Info

Publication number: CN102547873A
Application number: CN2010106022218A
Authority: CN
Inventors: 毛玉欣; 毕以峰; 刘国燕; 周晓云
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2010-12-21
Filing date: 2010-12-21
Publication date: 2012-07-04
Anticipated expiration: 2030-12-21
Also published as: CN102547873B

Abstract

The invention provides a method for controlling resources. The method is characterized by selecting a femtocell strategy function according to routing path information of the femtocell when a femtocell is powered on, establishing a session, and storing the routing path information of the femtocell in the femtocell strategy function. The invention also provides a system for controlling the resources. The method and the system provided by the invention ensure that femtocells on the same routing path select the same femtocell strategy function.

Description

Resource control method and system

Technical Field

The present invention relates to the field of wireless communication, and in particular, to a method and system for resource control.

Background

An Evolved Packet System (EPS) of the third Generation Partnership Project (3rd Generation Partnership Project, abbreviated as 3GPP) is composed of an Evolved Universal Terrestrial Radio Access Network (Evolved Universal Radio Access Network, abbreviated as E-UTRAN), a Mobility Management Entity (MME), a Serving Gateway (S-GW), a Packet data Network Gateway (Packet data Network Gateway, abbreviated as 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 the architecture of the HeNB accessing the EPS in a roaming scenario (Home routing or local breakout) is mainly embodied in an EPS network, and is not related to the present invention, and no description is given here.

MME is connected with EUTRAN, S-GW and home base station gateway (HeNB GW), and is responsible for the related work of control planes such as mobility management, non-access stratum signaling processing and user mobility management context management; 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), 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 for short), a Policy and Charging Rules Function (PCRF for short) makes Policy and Charging Rules, and connects with an Application Function (AF for short) in an operator network Protocol (IP for short) 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 for short) 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 a bearer, ensuring Quality of Service (QoS for short) of Service data, and performing Charging control. When an S5 interface of the S-GW and the P-GW adopts Proxy Mobile IP (PMIP for short), a Bearer Binding and Event reporting function (BBERF for short) resides in the S-GW, and information is exchanged between the S-GW and the PCRF 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 a PCEF.

The PCEF or BBERF selects the PCRF through a DRA (Diameter Routing Agent) function. There may be multiple PCRF nodes in a PLMN (Public Land Mobile Network) of an EPS, and all of the PCRF nodes belong to one or more Diameter domains, which may also be referred to as PCRF domains. A connection of a UE to a PDN Network is called an IP-CAN (IP Connectivity Access Network) session. The policy charging control information of one IP-CAN session is determined by only one PCRF. In order to ensure that all PCEFs or BBERFs associated with an IP-CAN session are associated to the same PCRF, the EPS introduces a logic function module DRA (diameter routing Agent) in each diameter (PCRF) domain. When UE wants to establish an IP-CAN session to a PDN, a DRA selects a PCRF for the IP-CAN session according to the UE identification, the IP address of the UE or APN (Access Point Node, Access Point) information, and the PCEF or BBERF related to the IP-CAN session is associated to the selected PCRF by the DRA. The DRA may select different PCRFs for different IP-CAN sessions of the UE (at this time, the same UE establishes multiple IP-CAN sessions), or may select the same PCRF for all IP-CAN sessions of the UE, i.e., the DRA selection PCRF may be based on the UE level or the IP-CAN level.

The EPS supports HeNB access, the HeNB is a small-sized and low-power base station and is deployed in indoor places such as homes and offices. The HeNB typically leases fixed network lines to access the EPS core network, as shown in fig. 1. In order to ensure access Security, a Security Gateway (SeGW for short) is introduced, and IPSec encapsulation is adopted for data transmitted between the HeNB and the SeGW, so that a fixed network line between the HeNB and the SeGW cannot sense interactive data content of the HeNB and a core network. The fixed network line between the HeNB and the SeGW for HeNB access is referred to as the fixed network backhaul. As shown in fig. 1, the HeNB accesses the EPS core network through a fixed network backhaul, a Home eNodeB Management System (HeMS) in the drawing is used to manage the HeNB, an HeNB GW is an optional network element, and an operator may choose not to deploy the network element in the network.

In addition, a 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, which is similar to fig. 1, except that a Serving General Packet Radio Service Support Node (SGSN) is used instead of the S-GW, and a gateway General Packet Radio Service Support Node (GGSN) is used instead of the P-GW. The HNB GW is a network element that must be deployed in this system. The HNB subsystem and the HeNB subsystem have great similarity. The QoS provided by the fixed network line for HeNB/HNB access is generally limited by the subscription of the HeNB/HNB owner and the fixed network operator, and the subscription QoS of the HeNB/HNB owner and the fixed network operator is called the subscription QoS of the HeNB/HNB.

However, there is a scenario where a plurality of henbs/HNBs share a single subscription QoS. For example, an enterprise needs to deploy a HeNB/HNB network, where the network includes multiple henbs/HNBs, and all of the henbs/HNBs access the EPS network through the same fixed network line (backhaul), and in this scenario, the multiple henbs/HNBs share one subscription QoS.

When the HeNB/HNB accesses the network, the fixed network equipment needs to allocate certain QoS resources for the HeNB/HNB access by combining the subscription QoS of the HeNB/HNB and the network resources available for the current fixed network, and the QoS allocated for the HeNB/HNB when the HeNB/HNB accesses the network is called authorized QoS.

The 3GPP proposes to use a HeNB PF (Policy Function) and a BPCF (BroadBand Forum Policy Control Function) to perform QoS management, where the HeNB PF is disposed in the 3GPP HeNB subsystem and the BPCF is disposed in the BBF network.

Meanwhile, 3GPP also defines procedures of HeNB power-up and handover of a user across henbs, as shown in fig. 3 and fig. 4, respectively.

Fig. 3 illustrates a flow when the HeNB is powered on:

and S301, establishing an IPSec tunnel between the HeNB and the SeGW.

And S302, the SeGW informs the HeNB PF of the binding relationship between the external address of the HeNB (the IP address allocated to the HeNB by the BBF network) and the internal IP address of the HeNB (the IP address allocated to the HeNB by the SeGW). When the HeNB accesses the network in a routing manner, the external address is a CPE (customer premises Equipment) IP address (IPSee tunnel header identifier);

and S303, establishing an Iuh/S1 session between the HeNB and the HeNB GW/MME.

And S304, establishing a session between the HeNB GW/MME and the HeNB PF, and sending the information of the HeNB, such as CSG ID (closed subscriber group identity) and the HeNB internal IP address to the HeNB PF.

And S305. the HeNB PF associates the session established in the step S304 with the session established in the step S302 according to the internal IP address of the HeNB, discovers the BPCF according to the IP address of the CPE, and establishes an S9 session with the BPCF.

And S306, the BPCF returns a response of session establishment completion to the HeNB PF.

Fig. 4 illustrates a flow of a user during a handover across henbs, where a source HeNB, a source BPCF, a source HeNB GW, a source HeNB PF, and a source MME are network elements accessed before UE handover, and the remaining network elements are network elements to which UE is handed over to a target network:

s401, the source HeNB sends a switching notice to the target MME through the source MME.

S402, the target MME sends a switching request to the target HeNB GW.

And S403, the target HeNB GW sends an authorization request for bearer establishment to the target HeNB PF, and the request message contains the IP address of the target HeNB and the CSG information of the switched UE.

And S404, authorizing the target HeNB PF, and modifying an S9 session established when the target HeNB is powered on.

S405, the target HeNB PF returns an authorization response to the target HeNB GW.

And S406, based on the authorization result, the target HeNB GW continuously sends the switching request to the target HeNB, or modifies or rejects the switching request. If modified, it is limited to authorized unauthorized bearers only.

And S407, the target HeNB returns a switching response to the target MME through the target HeNB GW.

S408, the source MME receives an indication of completion of forward reset from the target MME.

And S409, the source MME requests the source HeNB to release the context of the UE by sending a UE context release request to the source HeNB GW.

And S410, the source HeNB GW sends a request corresponding to the release of the bearing resource to the source HeNB PF.

And S411, the source HeNB PF modifies S9 session and requires the source BPCF to release corresponding resources.

And S412, the source HeNB PF returns an authorization response of the resource release request to the source HeNB GW.

And S413, based on the authorization result, the source HeNB GW returns a request message of context release to the source HeNB, and the context is released.

And S414, the source HeNB returns a context release response to the source MME through the source HeNB GW. The handover procedure is completed.

In the procedure shown in fig. 3, to implement QoS management, a session needs to be established between the SeGW and the HeNB PF, and a session needs to be established between the HeNB GW and the HeNB PF. The SeGW and the HeNB GW respectively use the HeNB internal IP addresses to discover the same HeNB PF, and realize the association of the two sessions. The HeNB PF also discovers the BPCF using the outer header information of the IPSec tunnel, i.e. the CPE IP address, and establishes a session with the BPCF.

In the procedure shown in fig. 4, a user is handed over to an HeNB, and this handover procedure is directed to a scenario in which multiple henbs belong to different fixed networks backhaul. At this time, for the core network, it may be regarded that the UE attaches to the target h (e) NB and requests resources, and goes offline from the source h (e) NB and releases resources (in order to ensure service continuity during handover, the principle of the handover process is "connect first and then disconnect", that is, the UE establishes a new connection and allocates corresponding resources first and then releases an old connection), and the resource control in the two processes is relatively independent (since the two h (e) NBs belong to different Backhaul, the application and release of resources do not conflict).

However, for a scenario that the UE performs handover between multiple henbs under the same backhaul, if the UE initiates attachment on the target h (e) NB and requests corresponding QoS resources for the service according to the principle of "connect before disconnect" in the handover process, the core network needs to authorize the QoS request for accessing the target h (e) NB by the UE, but since the resources on the source h (e) NB are not yet released, if the current resources are tight (i.e. the authorized QoS granted to the HeNB of the same backhaul is already fully occupied), the QoS resource request authorization for the handover user may be rejected due to insufficient resources, thereby causing a handover failure across henbs under the same backhaul by the UE.

Disclosure of Invention

The technical problem to be solved by the invention is to provide a resource control system and a resource control method, which are used for avoiding switching failure when UE is switched between HeNBs under the same backhaul.

In order to solve the above problem, the present invention provides a resource control method, including:

when the femtocell is powered on, a femtocell strategy function is selected according to the routing path information of the femtocell, a session is established, and the routing path information of the femtocell is stored in the femtocell strategy function.

Further, the method may further have a characteristic that, when a plurality of home base stations using the same routing path are powered on, the same home base station policy function is selected for the home base stations according to the routing path information.

Further, the method may further have the following characteristic that selecting the femtocell policy function according to the routing path information of the femtocell, and establishing the session includes:

and when the femtocell is accessed in a routing mode, the security gateway discovers the femtocell strategy function according to the routing path information of the femtocell and establishes a session with the femtocell strategy function.

when the femtocell is accessed in a bridging mode, the femtocell or the security gateway finds out the femtocell strategy function according to the routing path information of the femtocell, and establishes a session with the femtocell strategy function.

Further, the method may further have the following characteristic that the discovering of the home base station policy function by the home base station or the security gateway according to the routing path information of the home base station includes:

and the home base station or the security gateway sends the routing path information of the home base station to a Diameter Routing Agent (DRA), and the DRA selects a home base station policy function for the home base station according to the routing path information.

Further, the above method may further have the following features, and the method further includes:

when the home base station is accessed in a bridging mode:

the home base station acquires routing path information of the home base station from a home base station management system (HeMS); or,

and the security gateway authorizes authentication to a broadband forum through third generation partnership project authorization authentication to acquire the routing path information of the home base station.

Further, the method may further have the following characteristic that, when a user switches from a source femtocell to a target femtocell, the femtocell policy function obtains routing path information of the source femtocell and the target femtocell, and determines whether the routing path information of the source femtocell and the target femtocell is the same, and if the routing path information of the source femtocell and the target femtocell is the same, the user access is admitted.

Further, the method may further have the following characteristic that, when a user switches from a source femtocell to a target femtocell, the femtocell policy function obtains routing path information of the source femtocell and the target femtocell, and determines that the routing path information of the source femtocell is different from that of the target femtocell, if the available authorized service quality resource of the target femtocell meets the authorized service quality resource request of the user, the user access is admitted, otherwise, the user access is denied.

Further, the method may further have the following characteristic that the step of acquiring the routing path information of the source femtocell and the target femtocell by the femtocell policy function includes:

the home base station strategy function acquires the address and/or the identification of the source home base station and the address and/or the identification of the target home base station from an authorization request;

and the femtocell strategy function acquires the routing path information of the source femtocell and the routing path information of the target femtocell according to the mapping relation between the address and/or the identification of the femtocell and the routing path information, the address and/or the identification of the source femtocell and the address and/or the identification of the target femtocell.

Further, the method may further have the following characteristic that the routing path information is an IP address of the customer premises equipment or a virtual local area network identifier.

The present invention also provides a resource control system, comprising: selecting a device and a home base station policy function, wherein:

the selection device is used for selecting the strategy function of the home base station according to the routing path information of the home base station and establishing a session when the home base station is powered on;

and the femtocell strategy function is used for storing the routing path information of the femtocell when the femtocell is powered on.

Further, the system may further have a feature that the selecting device is a security gateway when the femtocell accesses in a routing manner.

Further, the system may further have a feature that, when the femtocell accesses in a bridge manner, the selecting device is a femtocell or a security gateway.

Further, the system may further have a feature that the home base station or the security gateway is configured to send routing path information of the home base station to the DRA, so that the DRA selects a home base station policy function for the home base station according to the routing path information.

Further, the above system may further have a feature that the femtocell is configured to obtain routing path information of the femtocell from a femtocell management system (HeMS) when the femtocell accesses in a bridging manner; or,

the security gateway is used for authorizing authentication to a broadband forum through a third generation partnership project to acquire routing path information of the home base station when the home base station is accessed in a bridging mode.

Further, the system may further have a feature that the femtocell policy function is further configured to, when a user switches from a source femtocell to a target femtocell, obtain routing path information of the source femtocell and the target femtocell, and determine whether the routing path information of the source femtocell and the target femtocell is the same, and if the routing path information of the source femtocell and the target femtocell is the same, admit the user access.

Further, the system may further have a feature that the femtocell policy function is further configured to, when a user switches from a source femtocell to a target femtocell, acquire routing path information of the source femtocell and the target femtocell, and determine that the routing path information of the source femtocell is different from the routing path information of the target femtocell, admit the user access if an available authorized qos resource of the target femtocell satisfies an authorized qos resource request of the user, and deny the user access if the available authorized qos resource of the target femtocell does not satisfy the authorized qos resource request of the user.

Further, the system may further have the following feature that the home base station policy function is configured to: acquiring the address and/or the identification of the source home base station and the address and/or the identification of the target home base station from the authorization request; and acquiring the routing path information of the source home base station and the routing path information of the target home base station according to the mapping relation between the address and/or the identification of the home base station and the routing path information, the address and/or the identification of the source home base station and the address and/or the identification of the target home base station.

Furthermore, the system may further have a characteristic that the routing path information is an IP address of the customer premises equipment or a virtual local area network identifier.

According to the method, the HeNBs under the same backhaul select the same HeNB PF, and the UE accepts the switching request when switching between the HeNBs under the same backhaul, so that the switching failure is avoided.

Drawings

Fig. 1 is a schematic diagram of an architecture of an HeNB accessing an EPS in the prior art;

fig. 2 is a schematic architecture diagram of an HNB accessing UMTS through a fixed network in the prior art of the present invention;

fig. 3 is a flow diagram of a HeNB power-on and HeNB PF session establishment in the prior art of the present invention;

FIG. 4 is a QoS management flow of the user in the prior art of the present invention when switching across HeNB;

fig. 5 is a flowchart illustrating a first procedure in the embodiment of the present invention (an HeNB accesses in a bridge mode, backhaul information of the HeNB is acquired by a 3GPP AAA, and a session is established between an HeNB GW and an HeNB PF);

fig. 6 is a flowchart illustrating a second procedure of the embodiment of the present invention (the HeNB accesses in a bridge mode, backhaul information of the HeNB is acquired by a 3GPP AAA, and the HeNB PF establish a session);

fig. 7 is a flowchart illustrating a third procedure in the embodiment of the present invention (the HeNB accesses in a bridge mode, backhaul information of the HeNB is acquired by the HeMS, and a session is established between the HeNB GW and the HeNB PF);

fig. 8 is a flowchart illustrating a fourth embodiment of the present invention (the HeNB accesses in a routing manner, and backhaul information thereof is carried to the SeGW by IKEv2, and the HeNB GW and the HeNB PF establish a session);

fig. 9 is a flow diagram of a fifth embodiment of the present invention (a network is not deployed with a HeNB GW, a HeNB accesses in a bridge mode, and an MME establishes a session with a HeNB PF);

fig. 10 is a flow chart of the inventive scheme.

Detailed Description

When the UE is switched within the same backhaul and the UE is switched from the source HeNB to the target HeNB, the QoS resources of the fixed network backhaul used do not change, and if the core network policy control device can sense that the UE is switched within the same backhaul, even if the QoS resources of the backhaul are in short supply, the switching request of the user can still be authorized, and at this time, the switching principle of "first connection and then disconnection" described in fig. 4 cannot be applied to the scenario of the UE switching across henbs within the same backhaul.

Therefore, aiming at the problem that the existing inter-HeNB switching mechanism cannot meet the requirement of resource management when inter-HeNB switching occurs in the same backhaul, the invention provides a strategy control method, which leads the resource authorization request messages before and after the inter-HeNB switching of the UE to be routed to the same HeNB PF by associating the same HeNB PF with the HeNB using the same fixed network backhaul, thereby ensuring that the HeNB PF senses that the switching occurs in the same backhaul, and further avoiding the need of updating the authorization resources of the fixed network backhaul for the user switching. Under the condition of resource shortage, the access of the switching user in backhaul can be ensured.

The implementation scheme is shown in fig. 10:

(1) when the HeNB is powered on, the HeNB PF is selected for the HeNB according to backhaul information of the HeNB, a session is established, and the backhaul information of the HeNB is stored on the HeNB PF.

If the HeNB is accessed in a routing mode, the process of selecting the HeNB PF for the HeNB is that the SeGW discovers the HeNB PF according to the backhaul information and establishes a session with the HeNB PF.

If the HeNB is accessed in a bridging mode, the process of selecting the HeNB PF for the HeNB is that the HeNB or the SeGW discovers the HeNB PF according to the backhaul information and establishes a session with the HeNB PF.

Further, in the process of selecting the HeNB PF for the HeNB according to backhaul information of the HeNB, a DRA (Diameter Routing Agent) program may be used, the SeGW or the HeNB sends the backhaul information to the DRA, and the DRA selects the HeNB PF for the HeNB according to the backhaul information.

Further, in the above-mentioned case,

and when a plurality of HeNBs with the same backhaul are powered on, selecting the same HeNB PF for the HeNB according to the backhaul information.

Further, in the above-mentioned case,

and judging whether the HeNB belongs to the same backhaul according to the backhaul information. The backhaul information is CPE IP address information or VLAN identification information or other information.

Further, in the above-mentioned case,

when the HeNB is accessed in a bridging manner,

the process of selecting the HeNB PF for the HeNB is that when the HeNB and the SeGW establish the IPSec tunnel, the SeGW discovers the HeNB PF according to backhaul information of the HeNB, and establishes a session with the HeNB PF.

The SeGW acquires backhaul information of the HeNB from a BBF AAA through a 3GPP AAA;

or,

and selecting a HeNB PF for the HeNB, discovering the HeNB PF by the HeNB according to the backhaul information, and establishing a session with the HeNB PF. And the HeNB acquires backhaul information from the HeMS.

(2) When UE is switched from a source HeNB to a target HeNB, a HeNB PF acquires backhaul information of the source HeNB and the target HeNB, and judges whether to accept user access or not according to the backhaul information of the target HeNB and the backhaul information of the source HeNB, or whether to update S9 conversation for the user.

And if the backhaul information of the target HeNB is the same as the backhaul information of the source HeNB, the HeNB PF judges that the target HeNB is switched in the same backhaul, and accepts switched user access without updating the S9 session.

And if the backhaul information of the target HeNB is inconsistent with the backhaul information of the source HeNB, the HeNB PF judges that the handover is the handover of the backhaul, and if the available authorized service quality resources of the target HeNB meet the authorized service quality resource request of the user, the user access is admitted and the S9 session is updated, otherwise, the user access is rejected.

The step of acquiring backhaul information of the source HeNB and the target HeNB by the HeNB PF comprises the following steps:

the HeNB PF acquires the address and/or the identification of the source HeNB and the address and/or the identification of the target HeNB from an authorization request;

and the HeNB PF acquires the routing path information of the source HeNB and the routing path information of the target HeNB according to the mapping relation between the address and/or the identification of the HeNB and the backhaul information, the address and/or the identification of the source HeNB and the address and/or the identification of the target HeNB.

The problems and corresponding solutions to which the present invention relates are applicable to both HeNB and HNB subsystems. The invention thus describes problems and solutions only with the HeNB subsystem as an example. The corresponding problems and solutions apply equally to HNB subsystems. In the HNB subsystem, the SGSN corresponds to the MME in the HeNB subsystem.

The first embodiment is as follows:

the procedure in the first embodiment is directed to an architecture in which the HeNB GW and the SeGW respectively establish interfaces with the HeNB PF.

The embodiment describes that the HeNB accesses the network in a bridging manner, and because in the bridging manner, even if the henbs belonging to the same backhaul have different CPE IP address information, the CPE IP addresses are sent to the HeNB PF as backhaul information, and it is still impossible to determine whether the henbs belong to the same backhaul. The VLAN ID identification is used in this embodiment as backhaul information. The realization method is that the SeGW acquires backhaul information of the HeNB from the BBF AAA through the 3GPP AAA, discovers the HeNB PF according to the backhaul information, and establishes a session; the UE is switched across HeNB, and the HeNB PF executes admission control for the switching. The flow chart is described as shown in FIG. 5:

and S501, powering on the HeNB-1, executing fixed network authentication, and storing backhaul information of the HeNB-1 by the BBF AAA. After the authentication is passed, the fixed network equipment, such as BRAS, allocates a local IP address for the HeNB-1.

And S502, the HeNB-1 executes an IKEv2 authentication process and sends an authentication request to the SeGW.

S503.segw sends an authentication request to the 3GPP AAA.

S504, after the 3GPP AAA receives the authentication request aiming at the HeNB-1, the backshual information of the HeNB-1 is obtained from the BBF AAA.

The process of discovering the BBF AAA by the 3GPP AAA can be based on the HeNB-1 identification information, on the premise that the HeNB-1 uses the same identification information when executing the fixed network authentication and executing the IKEv2 authentication, or when the HeNB-1 executes the fixed network authentication, the BBF AAA stores the local IP address of the HeNB-1, and the subsequent 3GPP AAA discovers the BBF AAA according to the local IP address (namely IPSec tunnel information) of the HeNB-1.

And S505, after the authentication is passed, the 3GPP AAA returns an authentication response to the SeGW, and returns the backhaul information of the HeNB-1 acquired from the BBFAAA to the SeGW.

S506, the SeGW allocates an IP address (hereinafter referred to as the internal IP address of the HeNB-1) for the HeNB-1, and the internal IP address of the HeNB-1 is contained in an IKEv2 authentication response message and returned to the HeNB-1.

And S507, establishing an IPSec tunnel between the HeNB-1 and the SeGW.

And S508, the SeGW discovers and selects the HeNB PF for the HeNB-1 according to the backhaul information of the HeNB-1 acquired in the step S505, and establishes a session. And simultaneously, the SeGW sends the internal IP address and backhaul information of the HeNB-1 to the HeNB PF.

Wherein: the process that the SeGW finds the HeNB PF can use a DRA finding program, at the moment, the SeGW sends backhaul information to the DRA, the DRA finds the HeNB PF, meanwhile, the SeGW sends the internal IP address of the HeNB-1 to the DRA for storage, so that after the step S510, the HeNB GW-1 sends the same internal IP address of the HeNB-1 to the DRA, the DRA searches for the HeNB PF which is the same as that in the step S508 for the HeNB GW-1.

And S509, establishing an Iuh/S1 session between the HeNB-1 and the HeNB GW-1, and sending the internal IP address of the HeNB-1 to the HeNB GW-1.

S510, the HeNB GW-1 finds the HeNB PF according to the internal IP address of the HeNB-1, and establishes a session (since the SeGW establishes the association between the internal IP address of the HeNB-1 and the HeNB PF after selecting the HeNB PF, the HeNB GW-1 can find the same HeNB PF according to the internal IP address of the HeNB-1).

And S511. the HeNB PF discovers the BPCF according to the backhaul information of the HeNB-1 and establishes an S9 session with the BPCF.

And S512, the process executed by powering on the HeNB-2 can refer to the power-on process of the HeNB-1, namely the steps S501 to S511. The flow sequences are completely the same, and the information carried by part of the messages is different. The difference is that when the HeNB-2 is powered on and the SeGW establishes the IPSec tunnel, the SeGW allocates an internal IP address for the HeNB-2, the IP address is different from the internal IP address of the HeNB-1, but backhaul information of the HeNB-2 is the same as backhaul information of the HeNB-1, so that backhaul information according to which the SeGW selects the HeNB PF is the same, but the internal IP address of the HeNB-2 and the backhaul information need to be sent to the HeNB PF. And when the HeNB GW-2 selects the HeNB PF, the session is ensured to be associated to the same HeNB PF according to the internal IP address of the HeNB-2.

Wherein: the HeNB GW-1 and the HeNB GW-2 may also be the same HeNB GW.

Since the HeNB-1 and the HeNB-2 belong to the same backhaul network, the used backhaul information is the same, so that the same HeNB PF can be found for the HeNB-1 and the HeNB-2, and the session is associated to the same HeNB PF.

Next, the procedure of steps S513-S522 is a procedure of performing admission control for handover of the UE from HeNB-1 to HeNB-2, and HeNB PF is a procedure of performing admission control for handover.

S513. the HeNB-1 receives a switching request from the UE, and requires to be switched from the HeNB-1 to the HeNB-2, the HeNB-1 sends a switching notification to an MME-1 (source MME), the notification message carries identification information of the HeNB-2, and simultaneously the message can also carry an IP address and/or identification information of the HeNB-1, wherein the IP address can be an internal IP address of the HeNB-1 and/or an external IP address (namely IPSec tunnel header information) allocated for the message by a BBF fixed network.

S514, if the switching is the switching across MME, the MME-1 (source MME) sends a switching notification message to the MME-2 (target MME), wherein the message carries the IP address and/or the identification information of the HeNB-1, and the IP address can be the internal IP address of the HeNB-1 and/or an external IP address (namely IPSec tunnel header information) allocated to the BBF fixed network by the BBF fixed network.

Wherein, if MME-1 receives the switching notification message from HeNB-1 and only contains identification information or internal IP address information of HeNB-1, the identification information or the internal IP address information can be mapped into external IP address information (namely IPSec tunnel header information) locally;

if the message from the HeNB-1 is received without carrying the IP address and/or the identification information of the HeNB-1, the MME-1 can acquire the IP address information of the HeNB-1 from the head part of the received switching notification message, wherein the address is the internal IP address of the HeNB-1, and can further acquire the external IP address and/or the identification information of the HeNB-1 based on the internal IP address mapping.

And S515, the MME-2 sends a switching request message to the HeNB GW-2, wherein the message carries the IP address and/or the identification of the HeNB-1. Wherein the IP address can be an internal IP address of the HeNB-1 and/or an external IP address allocated by the BBF fixed network.

And S516, after receiving the message, the HeNB GW-2 sends an authorization request message to the HeNB PF for requesting QoS resources, wherein the message carries the IP address and/or the identification of the HeNB-1, and the IP address can be the internal IP address of the HeNB-1 and/or the external IP address allocated to the HeNB-1 by the BBF fixed network.

And S517, after the HeNB PF receives the authorization request message, finding backhaul information corresponding to the HeNB-1 according to the IP address and/or the identification of the HeNB-1, and finding backhaul information corresponding to the HeNB-2 according to the IP address and/or the identification of the HeNB-2, wherein if the backhaul information is the same, the HeNB PF judges that inter-HeNB switching inside the same backhaul occurs, so that the HeNB PF accepts the authorization request without sending information to the BPCF, and requires the BPCF to modify fixed network resources.

And S518. the HeNB PF returns an authorization response to the HeNB GW-2.

And S519, the HeNB GW-2 sends a switching request to the HeNB-2.

And S520, the HeNB-2 returns a response of successful switching to the HeNB GW-2, and the HeNB GW-2 simultaneously sends the switching response to the MME-2.

And S521. after receiving the switching response, the MME-2 initiates a Forward location change completion (Forward Relocation Complete) message to the MME-1 to trigger the corresponding QoS resource release process on the HeNB-1.

S522, please refer to steps S409-S414 in FIG. 4 for the QoS resource release process of HeNB-1.

And the fixed network equipment allocates a local IP address for the HeNB-1 in the authentication process of the HeNB-1 and saves backhaul information of the HeNB-1 in the BBF AAA. When the HeNB-1 establishes an IPSec tunnel with the SeGW, the SeGW acquires backhaul information of the HeNB-1 from the BBF AAA through the 3GPP AAA. After the IPSec tunnel establishment is completed, the SeGW allocates an internal IP address for the HeNB-1. And then, the SeGW discovers and selects the HeNB PF for the HeNB-1 according to backhaul information of the HeNB-1, establishes a session, and sends the internal IP address and backhaul information of the HeNB-1 to the HeNB PF. And when the session is established between the HeNB GW-1 and the HeNB PF subsequently, the same HeNB PF can be discovered according to the internal IP address of the HeNB-1. Thus, the power-on of the HeNB-1 is ensured according to the internal IP address of the HeNB-1, and the SeGW and the HeNB GW-1 can find the same HeNB PF and establish a session to implement association.

And when the HeNB-2 belonging to the same fixed network backhaul is powered on, executing a flow similar to the HeNB-1. Because the backhaul information used by the HeNB-2 is the same as that of the HeNB-1, the same HeNB PF is ensured to be discovered for the power-on of the HeNB-1 and the HeNB-2 according to the backhaul information, so that the QoS resource authorization requests initiated for the HeNB-1 and the HeNB-2 can be associated to the same HeNB PF.

When the UE is switched to the HeNB-2 from the HeNB-1, because the HeNB PF serves the HeNB-1 and the HeNB-2, QoS resource authorization requests before and after switching can be routed to the same HeNB PF, the HeNB PF can judge that the requests are caused by cross-HeNB switching under the same backhaul according to the same backhaul information used before and after switching, but not the QoS resource authorization requests caused by new user access, so the requests can be admitted, and the BPCF does not need to make any authorization change on fixed network resources.

Example two

The second embodiment describes that the HeNB also accesses the network in a bridging manner, and uses the VLAN ID as backhaul information. The SeGW acquires backhaul information of the HeNB from the BBF AAA through the 3GPP AAA, discovers the HeNB PF according to the backhaul information, and establishes a session; the UE is switched across HeNB, and the HeNB PF executes admission control for the switching. The difference from the first embodiment is that the HeNB GW and the HeNB PF establish a session, and the second embodiment is that the HeNB and the HeNB PF establish a session. The flow is realized as follows:

and S601. the processes of the power-on process of the HeNB-1, the authentication process, the local IP address allocation, the IPSec tunnel establishment and the HeNB PF selection are the same as the process of the figure 5, please refer to S501-S508. And the SeGW discovers and selects the HeNB PF according to backhaul information of the HeNB-1 acquired from the AAA, and establishes a session. And the internal IP address and backhaul information of the HeNB-1 are sent to the HeNB PF.

And S602, the HeNB-1 finds the same HeNB PF as the one in S601 according to the internal IP address, and requests the HeNB PF to carry out resource authorization.

S603.HeNB PF discovers BPCF according to backhaul information of HeNB-1 received in S601, and establishes S9 session.

And S604, the procedure of the power-on process of the HeNB-2 is similar to that of the power-on process of the HeNB-1. Wherein the SeGW selects the same HeNBPF serving the HeNB-1 according to backhaul information of the HeNB-2.

S605, refer to steps S513 to S522 shown in fig. 5 for a procedure of implementing inter-HeNB handover within the same backhaul.

Example three:

the third embodiment describes that the HeNB accesses the network in a bridging manner, and uses the VLAN ID as backhaul information. And an interface is established between the HeMS and the AAA fixed network. And the HeNB acquires backhaul information from the HeMS. The implementation process is shown in fig. 7:

and S701, powering on the HeNB-1 to complete fixed network authentication, and allocating a local IP address to the fixed network equipment by the fixed network equipment.

S702, IKEv2 authentication is completed between the HeNB-1 and the SeGW, an IPSec tunnel is established, and the SeGW is the HeNB-1 access network and completes the authentication to the 3GPP AAA.

And S703, the HeNB-1 completes the registration to the HeMS, and the HeMS inquires backhaul information of the HeNB-1 from the BBF AAA and returns the backhaul information to the HeNB-1.

And S704, establishing an Iuh/S1 session between the HeNB-1 and the HeNB GW-1, and sending backhaul information of the HeNB-1 to the HeNB GW-1.

And S705, the HeNB GW-1 finds and selects the HeNB PF to establish a session according to the backhaul information, and sends the backhaul information to the HeNB PF.

The procedure of selecting HeNB PF by HeNB GW-1 may use DRA procedure, among others.

S706.henb PF discovers BPCF according to backhaul information and establishes S9 session.

And S707, electrifying the HeNB-2, wherein the process is the same as the electrifying process of the HeNB-1, the HeNB-2 sends backhaul information acquired from the HeMS to the HeNB GW-2, and the HeNB GW-2 can select the HeNB PF which is the same as the HeNB-1 service according to the backhaul information because the backhaul information of the HeNB-2 is the same as the backhaul information of the HeNB-1.

S708, refer to S513 to S522 in the first embodiment for a handover procedure of the ue across the henbs in the same backhaul.

The above description is that an interface is set between the HeMS and the BBF AAA, and when the HeNB is powered on, the HeMS obtains backhaul information of the HeNB from the BBF AAA, and in addition, the HeMS may also set an interface with an NMS (Network Management System) or an OSS (operation support System) device to obtain backhaul information of the HeNB. Or backhaul information of the HeNB may be preconfigured on the HeMS. For this reason, the procedure of acquiring backhaul information from the HeMS by the HeNB and other procedures are the same as the procedure described in fig. 7, and a description thereof is not repeated.

Example four:

in the scenarios described in the first to third embodiments, the HeNB accesses the network in a bridging manner. In the bridge mode, even if a plurality of henbs belong to the same backhaul, the CPE IP addresses used by them are different, but the VLAN ID is used as backhaul information because the same VLAN ID is used.

The fourth embodiment describes a scenario in which the HeNB accesses the network in a routing manner. In the routing mode, a plurality of henbs belonging to the same backhaul are assigned the same CPE IP address, and thus, in the routing mode, the CPE IP address can be used as backhaul information of the HeNB.

Fig. 8 illustrates the discovery of the HeNB PF by the SeGW based on the CPE IP address. When a plurality of HeNB belonging to the same backhaul are powered on, the established session is associated to the same HeNBPF according to the CPE IP address, and the flow is described as follows:

and S801, electrifying the HeNB-1, and allocating an intranet IP address to the RG.

And S802, IKEv2 negotiation is carried out between the HeNB-1 and the SeGW, and as the HeNB-1 accesses the network in a routing mode, when a negotiation message passes through the RG, the RG converts the intranet IP address of the HeNB-1 into the CPE IP address. And an IPSec tunnel is established between the HeNB-1 and the SeGW. The CPE IP address is part of the IPSec tunnel information.

And S803. the SeGW acquires the IP address of the CPE in the IKEv2 negotiation process, discovers the HeNB PF according to the IP address of the CPE, establishes a session and sends the internal IP address of the HeNB-1 and the IP address of the CPE to the HeNB PF.

Wherein: the procedure for discovering HeNB PFs by the SeGW may be via DRA procedures. The specific process is as follows: the SeGW sends a CPE IP address to the DRA, the DRA selects the HeNB PF according to the CPE IP address, and the corresponding relation between the CPE IP address and the HeNB PF identification is stored. And subsequently, when the HeNB-2 is powered on, the SeGW also reports the same CPE IP address, and the DRA can also find the same HeNB PF for the HeNB-2 and establish a session according to the corresponding relation between the CPE IP address and the HeNB PF identification.

Or on the premise that the HeNB-1 and the HeNB-2 use the same SeGW, the SeGW sends the HeNB-1 intranet IP address to the DRA, the DRA discovers the HeNB PF according to the HeNB-1 intranet IP address, and sends the corresponding relation between the HeNB-1 intranet IP address and the HeNB PF identification to the SeGW. And establishing a corresponding relation among the CPE IP address, the HeNB-1 intranet IP address and the HeNB PF identifier in the SeGW. And when the HeNB-2 is powered on subsequently, the SeGW discovers the same HeNB PF for the HeNB-2 according to the corresponding relation between the intranet IP address of the HeNB-2 and the IP address of the CPE and the corresponding relation between the IP address of the CPE and the PF identifier of the HeNB, and establishes a session.

And S804, establishing an Iuh/S1 session between the HeNB-1 and the HeNB GW-1, wherein the session carries the internal IP address allocated by the SeGW for the HeNB-1.

And S805, the HeNB GW-1 discovers the HeNB PF which is the same as the step S803 through the internal IP address of the HeNB-1, and establishes a session.

S806.henb PF discovers BPCF from CPE IP address (i.e. IPSec tunnel information) and establishes S9 session.

S807, when the HeNB-2 belonging to the same backhaul is electrified, the process is the same as the process of electrifying the HeNB-1, refer to S801-S806. The difference is that the SeGW sends the internal IP address of the HeNB-2 to the HeNB PF when it discovers the HeNB PF and establishes a session. And the subsequent HeNB GW-2 discovers the same HeNB PF according to the internal IP address of the HeNB-2 and establishes a session.

S808, refer to S513 to S522 of the first embodiment, which is a procedure for handover of the UE across the henbs in the same backhaul.

Example five:

embodiments one to four describe scenarios in which a network deploys a HeNB GW. However, according to the deployment requirement of the HeNB subsystem, the HeNB GW may be optionally deployed, and the fifth embodiment describes a scenario in which the HeNB accesses in a bridge mode when the HeNB GW is not deployed in the network. The process is realized as follows:

and S901, powering on the HeNB-1, executing authentication, and acquiring a local IP address allocated to the HeNB-1 by the fixed network equipment.

And S902. a process of IKEv2 authentication negotiation between the HeNB-1 and the SeGW, an IPSec tunnel establishment process, and a process of selecting the HeNB PF by the SeGW please refer to S502-S508 or S701-S703.

And S903, establishing an Iuh/S1 session between the HeNB-1 and the MME-1, and sending the internal IP address of the HeNB-1 to the MME-1.

And S904, the MME-1 discovers the HeNB PF according to the internal IP address of the HeNB-1, establishes a session and sends the internal IP address and backhaul information to the HeNB PF.

S905.henb PF discovers BPCF according to backhaul information, and establishes S9 session.

And S906. the power-on process of the HeNB-2 refers to the power-on process of the HeNB-1.

And S907, the HeNB-1 receives the switching request of the UE and sends a switching request message to the MME-1, wherein the message carries the HeNB-2 identification and the address or the identification of the HeNB-1.

And S908, the MME-1 sends a switching notice to the MME-2 according to the HeNB-2 identification, and the address or the identification of the HeNB-1 is carried in the switching notice.

And S909. the MME-2 sends a resource authorization request message caused by switching to the HeNB PF, wherein the message carries the address or the identification of the HeNB-1.

And S910, after the HeNB PF receives the resource authorization request message, finding backhaul information corresponding to the HeNB-1 and the HeNB-2 according to the address or the identifier of the HeNB-1 used before switching and the address or the identifier of the HeNB-2 after switching, and perceiving that the backhaul information is the same, thereby judging that cross-HeNB switching in the same backhaul occurs, and authorizing the resource authorization request.

And S911, the HeNB PF returns a response of resource authorization to the MME-2.

And S912, the MME-2 sends a switching request to the HeNB-2.

And S913, reserving resources by the HeNB-2 according to the switching request, and returning a response of successful switching to the MME-2.

S914, MME-2 sends the notice of the completion of the forward reset to MME-1.

And S915. the HeNB-1 releases corresponding resources according to the process described in the step S909-S913, so that the resource changing process on the HeNB before and after the switching is completed.

In the above process, since the switching occurs in the same backhaul, the corresponding fixed network resource is not changed, and thus the S9 session does not need to be updated. Similarly, when the network is not deployed with the HeNB GW, the HeNB uses a scenario of routing access, and the handover procedure may refer to the handover procedure in the fifth embodiment, which is not described repeatedly herein.

The features of the above embodiments may be combined arbitrarily without conflict.

When the home base station accesses in a routing mode, the selection device is a security gateway; and when the home base station is accessed in a bridging mode, the selection device is the home base station or the security gateway.

And the home base station or the security gateway is used for sending the routing path information of the home base station to the DRA so that the DRA selects a home base station policy function for the home base station according to the routing path information.

The femtocell is used for acquiring routing path information of the femtocell from a femtocell management system (HeMS) when the femtocell is accessed in a bridging mode; or,

The femtocell strategy function is also used for acquiring the routing path information of the source femtocell and the target femtocell when a user switches from the source femtocell to the target femtocell, judging whether the routing path information of the source femtocell and the target femtocell is the same or not, and if the routing path information of the source femtocell and the target femtocell is the same, accepting the user access.

The femtocell strategy function is also used for acquiring the routing path information of the source femtocell and the target femtocell when a user is switched from the source femtocell to the target femtocell, and when the routing path information of the source femtocell and the target femtocell is different, if the available authorized service quality resource of the target femtocell meets the authorized service quality resource request of the user, the user access is admitted, otherwise, the user access is refused.

Wherein the home base station policy function is to: acquiring the address and/or the identification of the source home base station and the address and/or the identification of the target home base station from the authorization request; and acquiring the routing path information of the source home base station and the routing path information of the target home base station according to the mapping relation between the address and/or the identification of the home base station and the routing path information, the address and/or the identification of the source home base station and the address and/or the identification of the target home base station.

And the routing path information is an IP address of customer premises equipment or a virtual local area network identifier.

In summary, the embodiments of the present invention solve the problem of how to implement service admission management and resource management, so that the total QoS requirement does not exceed the QoS that can be provided by the subscribed fixed network line accessed by the femtocell.

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 present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for resource control, comprising:

2. The method according to claim 1, wherein when a plurality of home base stations using the same routing path are powered on, the same home base station policy function is selected for the home base stations according to routing path information.

3. The method according to claim 1, wherein the selecting the femtocell policy function according to the routing path information of the femtocell, and the establishing the session comprises:

4. The method according to claim 1, wherein the selecting the femtocell policy function according to the routing path information of the femtocell, and the establishing the session comprises:

5. A method according to claim 3 or 4, wherein the discovering of the home base station policy function by the home base station or the security gateway according to the routing path information of the home base station comprises:

6. The method of claim 5, wherein the method further comprises:

when the home base station is accessed in a bridging mode:

7. The method according to claim 1, wherein the method further comprises, when a user is handed over from a source home base station to a target home base station, the home base station policy function obtaining routing path information of the source home base station and the target home base station and determining whether the routing path information of the source home base station and the target home base station are the same, and if the routing path information of the source home base station and the target home base station are the same, admitting the user access.

8. The method according to claim 1, wherein the method further comprises, when a user is handed over from a source femtocell to a target femtocell, the femtocell policy function obtaining routing path information of the source femtocell and the target femtocell, and determining that the routing path information of the source femtocell and the target femtocell are not the same, admitting the user access if the available authorized qos resources of the target femtocell satisfy the authorized qos resource request of the user, and otherwise, rejecting the user access.

9. The method according to claim 7 or 8, wherein the step of the home base station policy function obtaining the routing path information of the source home base station and the target home base station comprises:

10. The method of any one of claims 1 to 4, 6 to 8, wherein the routing path information is a customer premises equipment IP address or a virtual local area network identification.

11. A resource control system, comprising: selecting a device and a home base station policy function, wherein:

12. The system of claim 11,

and when the home base station accesses in a routing mode, the selection device is a security gateway.

13. The system of claim 11,

and when the home base station is accessed in a bridging mode, the selection device is the home base station or the security gateway.

14. The system of claim 12 or 13,

15. The system of claim 14,

16. The system according to claim 11, wherein the hnb policy function is further configured to, when a user is handed over from a source hnb to a target hnb, obtain routing path information of the source hnb and the target hnb, determine whether the routing path information of the source hnb and the target hnb is the same, and if the routing path information of the source hnb and the target hnb is the same, admit the user access.

17. The system according to claim 11, wherein the hnb policy function is further configured to, when a user is handed over from a source hnb to a target hnb, obtain routing path information of the source hnb and the target hnb, and determine that the routing path information of the source hnb and the target hnb is not the same, admit the user for access if an available authorized qos resource of the target hnb meets an authorized qos resource request of the user, and deny the user for access if the available authorized qos resource of the target hnb does not meet the authorized qos resource request of the user.

18. The system of claim 16 or 17,

the home base station policy function is to: acquiring the address and/or the identification of the source home base station and the address and/or the identification of the target home base station from the authorization request; and acquiring the routing path information of the source home base station and the routing path information of the target home base station according to the mapping relation between the address and/or the identification of the home base station and the routing path information, the address and/or the identification of the source home base station and the address and/or the identification of the target home base station.

19. The system of any one of claims 11 to 13, 14 to 17, wherein the routing path information is a customer premises equipment IP address or a virtual local area network identification.