WO2012079443A1

WO2012079443A1 - Method for switching resource control among base stations

Info

Publication number: WO2012079443A1
Application number: PCT/CN2011/082498
Authority: WO
Inventors: 芮通; 周晓云; 毛玉欣
Original assignee: 中兴通讯股份有限公司
Priority date: 2010-12-13
Filing date: 2011-11-21
Publication date: 2012-06-21
Also published as: CN102547884A; CN102547884B

Abstract

A method for switching resource control among base stations. The method includes: when user equipment switches from a source Home NodeB to a target Home NodeB, and after a broadband forum (BBF) admission control network element receives an admission request message from the target Home NodeB policy function, judging whether the source Home NodeB and the target Home NodeB belong to the same routing path; if yes, permitting the admission request. In the method and system provided by the embodiments of the present invention, when the UE is switching, the UE is admitted when it is judged that the UE is across the same routing path, thereby avoiding switching failure.

Description

Method for switching resource control between base stations

Technical field

The present invention relates to the field of mobile communications, and in particular, to a method for switching resource control between base stations. Background technique

The 3rd Generation Partnership Project (3GPP) Evolved Packet System (EPS) is an Evolved Universal Terrestrial Radio Access Network (Evolved Universal Terrestrial Radio Access Network). E-UTRAN, Mobility Management Entity (MME), Serving Gateway (S-GW), Packet Data Network Gateway (P-GW or PDN GW), Home Subscriber Server (HSS), 3GPP Authentication, Authorization and Accounting (AAA), Policy and Charging Rules Function (referred to as Policy and Charging Rules Function) PCRF) consists of entities and other supporting nodes. 1 is a schematic diagram of a system architecture of an EPS according to the related art. As shown in FIG. 1, the mobility management entity is responsible for control planes such as mobility management, processing of non-access stratum signaling, and management of user mobility management context. The S-GW is an access gateway device connected to the E-UTRAN, which forwards data between the E-UTRAN and the P-GW, and is responsible for buffering paging waiting data; the P-GW is an EPS and packet data network ( Packet Data Network (referred to as PDN) The border gateway of the network, responsible for PDN access and forwarding data between EPS and PDN; S-GW and P-GW are both core network gateways; PCRF is policy and charging rule function The entity, which is connected to the service network protocol (Internet Protocol, IP for short) service network, obtains service information, and is connected to the gateway device in the network through the Gx/Gxa/Gxc interface, and is responsible for initiating the IP bearer. The establishment of the service, guarantees the quality of service (QoS), and performs charging control.

The EPS supports interworking with non-3GPP systems, wherein interworking with non-3GPP systems is implemented through the S2a/b/c interface, and the P-GW acts as an anchor between 3GPP and non-3GPP systems. In the system architecture diagram of EPS, non-3GPP systems are classified into trusted non-3GPP IP access and untrusted non-3GPP IP access. The trusted non-3GPP IP access can be directly connected to the P-GW through the S2a interface; the untrusted non-3GPP IP access needs to be connected to the P-GW through an Evolved Packet Data Gateway (ePDG), ePDG and The interface between the P-GWs is S2b. The S2c provides user plane-related control and mobility support between the user equipment (User Equipment, UE for short) and the P-GW. The supported mobility management protocol supports dual stacks. Mobile IPv6 Support for Dual Stack Hosts and Routers (referred to as DSMIPv6).

In the EPS system, the Policy and Charging Enforcement Function (PCEF) entity exists in the P-GW, and the PCRF and the P-GW exchange information through the Gx interface (see Figure 1). When the interface between the P-GW and the S-GW is based on Proxy Mobile IPv6 (PMIPv6), the S-GW also has Bearer Binding and Event Report Function (BBERF). The entity performs Quality of Service (QoS) control on the service data flow, and the S-GW and the PCRF exchange information through the Gxc interface (see Figure 1). When accessed through a trusted non-3GPP access system, the BBERF is also resident in the trusted non-3GPP access gateway. The trusted non-3GPP access gateway exchanges information with the PCRF through the Gxa interface (see Figure 1). When the UE roams, the S9 interface functions as an interface between the home PCRF and the visited PCRF, and provides an application function (Application Function, abbreviated as AF) for the UE, and sends the policy and charging control to the PCRF through the Rx interface. Policy and Charging Control (referred to as PCC) policy business information. In 3GPP, the corresponding PDN network can be found by the Access Point Name (APN). A connection from a UE to a PDN network is usually referred to as an IP Connectivity Access Network (IP-CAN) session. During the establishment of the IP-CAN session, the BBERF and the PCEF respectively establish a Diameter session with the PCRF, and through these Diameter sessions, the policy charging information and the information for formulating the policy for controlling the IP-CAN session are transmitted.

The corresponding BBF (Broadband Forum) proposes the Broadband Forum Policy Control Function (BPCF). As shown in Figure 2, the main function of BPCF is to formulate corresponding strategies; PEF ( Policy Enforcement Point (policy enforcement point) usually resides in fixed-line transmission equipment, such as: BRAS (Broadband Remote Access Server)/BNG (Broadband Network Gateway), the corresponding policy based on BPCF Carry out execution; AAA (Authentication, Authorization and Accounting), which stores user subscription information. AF (Application Function), which formulates policies for BPCF and provides corresponding business information. In the fixed network, the policy control is implemented. Compared with the mobile network, the fixed network policy decision entity needs to perform resource admission control in addition to the policy based on the service and the subscription. According to the access location of the UE, the flow of the data flow of the UE is determined. The path, based on making a judgment on the resource on the path, whether to accept the service.

The FMC (Fixed Mobile Convergence) scenario that operators are paying attention to is based on the research on 3GPP and BBF interconnection. For the scenario where the user accesses the mobile core network through the BBF fixed network, it is necessary to guarantee the QoS on the routing path of the entire data (data will be transmitted through the fixed network and the mobile network). When the mobile user UE accesses through the BBF fixed network, the PCRF not only needs to formulate policies based on services and subscriptions, but also needs to initiate an admission control request to the BPCF through the S9* (between PCRF and BPCF) interfaces (the request message may contain a user location, The information such as the identifier is used to inform the BPCF user of the access location), and the existing BPCF performs the admission control step:

1. Identify the access location of the UE;

2. Determine the flow path of the UE data stream, for example: RG (Residential Gateway), AN (Access Note, access point, for example, DSLAM Digital Subscriber Line Access Multiplexer, digital subscriber line access multiplexing device), BRAS/BNG and other equipment;

3. Determine the resources of each node on the path. If the resources on the node can meet the requirements of the data flow, allow admission.

After the BPCF completes the admission control decision, it returns the result to the PCRF.

Therefore, the BPCF does the access control related information of the user UE, and the PCRF can inform the BPCF through S9*.

For the scenario in which the UE accesses through the H(e)NB (Home eNodeB, the home base station, which is a home deployment device of the eNodeB), the existing standard proposes to set a new network element H(e)NB PF (Policy Function , the policy function), as shown in FIG. 5, is used for implementing admission control with the BPCF in the scenario, and the advantage of this is that the level of admission control is H(e)NB, and no need to be refined to the user; When the H(e)NB is powered on, the H(e)NB PF requests QoS information (specific bandwidth information, such as bandwidth information) for the H(e)NB through the S9* to the BPCF; it may be formulated based on the subscription and the carrier configuration. Based on the current resource allocation of the BBF access network, the BPCF decides whether to accept the QoS information requested by the H(e)NB, and feeds the result back to the PCRF. If the BBF fixed network accepts the QoS information requested by the H(e)NB, when the subsequent UE accesses and initiates the service through the H(e)NB (in this case, it may be necessary to request corresponding QoS for the service, such as bandwidth), There is no need to request admission control from the BPCF. The mobile core network element (for example: H(e)NB PF) decides whether to allow the service request to be accepted.

In order to enable the BPCF to perform admission control based on the QoS request for the H(e)NB, the H(e)NB PF needs to pass the requested QoS information and the access information of the H(e)NB to the BPCF through S9* (reference map) The BPCF admission control principle shown in 2, when the BBF fixed network treats the H(e)NB of the mobile network as a UE, and the BPCF is based on the received access information of the H(e)NB (for example: H(e) NB address information) determining the location of the H(e)NB, knowing the Backhaul (routing path) through which the H(e)NB data passes, and combining the received QoS request information to determine whether the resources on the Backhaul are allowed, It is finally decided to accept or reject the QoS request of the H(e)NB.

In the prior art, the SecGW (Security Gateway, Security Gateway) and the H(e)NB PF exchange the address information of the H(e)NB, but obtain the QoS information request of the H(e)NB based on the H(e)NB PF. The way of H(e)NB PF is divided into two types:

1) As shown in FIG. 6, the H(e)NB GW/MME and the H(e)NB PF interact (when the H(e)NB GW is not deployed in the network, the MME and the H(e)NB PF interact at this time. ), passing the requested QoS information.

2) As shown in Figure 7, H(e)NB and H(e)NB PF exchange QoS information requests.

Due to the difference in the deployment of the actual operating network, the address allocation of the H(e)NB is different. There are two types of address allocation methods (the difference is that the function of deploying the RG is different: bridging mode and routing mode):

1) As shown in the routing mode of Figure 8, the UE accesses the RG through the H(e)NB, and accesses the BRAS/BNG through the AN aggregation. At this time, the RG has a routing function, and the IP address of the UE is allocated by the RG (for example, : H(e)NB accesses the RG, authenticates the RG with the username and password, the authentication succeeds RG assigns the internal address to the H(e)NB;), and the RG's IP address is assigned by the BRAS/BNG (for example: in When the RG is powered on, the RG initiates authentication to the BRAS/BNG, and the BRAS/BNG assigns an address to the RG. At this time, the RG needs to perform IP address translation, and converts the private URL of the H(e)NB into a public network address CPE (Customer Premise). Equipment - User Premises Equipment / Client Equipment) address, which can be the address assigned by the BRAS/BNG to the RG.

2) As shown in Figure 9 bridge mode, the UE accesses through H(e)NB (may exist in network deployment)

RG, if there is a bridging function at this time, RG is only a Layer 2 device, and no IP address is assigned to the user. The connection between H(e)NB and BRAS/BNG is a Layer 2 connection), and then through AN. Access to BRAS/BNG, the IP address of the H(e)NB is allocated by BRAS/BNG.

In the prior art, when the UE switches between H(e)NBs, the current scenario is based on the fact that the two H(e)NBs belong to different access backhauls (for example: access through different RGs) , as shown in Figure 10a. At this point, for the core network, it can be seen as the UE attaching to the Target H(e)NB (target H(e)NB) and requesting resources, at Source H(e)NB (source H(e)NB) Offline and release resources (to ensure business continuity during handover, the principle of the handover process is "first connect and then break", that is, the UE first establishes a new connection and allocates the corresponding resources, and then releases the old connection), these two processes The resource control is relatively independent (since 2 H(e)NBs belong to different Backhaul, the application and release of resources will not conflict). However, for the handover scenarios where the two H(e)NBs belong to the same Backhaul (for example, access through the same RG), there is no research, as shown in Figure 10b.

Summary of the invention

The technical problem to be solved by the present invention is to provide a method and system for controlling resource switching between base stations, so that the UE avoids handover failure when switching over H(e)NBs under the same Backhaul.

In order to solve the above problems, the present invention provides a method for switching resource control between base stations, including:

When the user equipment switches from the source home base station to the target home base station, the broadband forum (BBF) admission control network element receives the admission request message of the target home base station policy function, and determines whether the source home base station and the target home base station belong to the same Routing path, if yes, allows admission requests.

Preferably, the above method may further have the following features, the method further comprising:

When the user equipment switches from the source home base station to the target home base station, the target mobility management unit/service The GPRS support node (MME/SGSN) sends a handover request message to the target home base station gateway or the target home base station, where the handover request message carries the address and/or identifier of the source home base station; After receiving the handover request message, the target home base station sends an authorization request message to the target home base station policy function, where the authorization request message carries an address and/or an identifier of the source home base station;

After receiving the authorization request message, the target home base station policy function sends an admission request message to the BBF admission control network element, where the admission request message carries an address and/or an identifier of the source home base station, and An address and/or an identifier of the target home base station;

The BBF admission control network element determines whether the source home base station and the target home base station belong to the same route according to the address and/or the identifier of the source home base station carried in the admission request message, and the address and/or the identifier of the target home base station. path.

Preferably, the above method may also have the following characteristics: the address is an internal address allocated by the mobile network and/or a local address allocated by the BBF fixed network.

Preferably, the foregoing method may further have the following feature: the BBF admission control network element determines the source family according to the address and/or identifier of the source home base station carried in the admission request message, and the address and/or identifier of the target home base station. Whether the base station and the target home base station belong to the same routing path include: the BBF admission control network element directly acquiring the source home base station according to the identifier and/or address of the source home base station and the target home base station carried in the admission request message And/or an external address of the target home base station, or mapping the identity or address of the home base station and/or the target base station to an external address;

The BBF admission control network element determines whether the source home base station and the target home base station belong to the same routing path according to the external addresses of the source home base station and the target home base station.

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

The source home base station sends a handover notification message to the target MME/SGSN; the target MME/SGSN acquires an address and/or an identifier of the source home base station from the handover notification message; or, from the handover notification Obtaining an address of the source home base station in a message header of the message;

Or,

The source home base station sends a handover notification message to the source MME/SGSN; Obtaining, by the source MME/SGSN, an address and/or an identifier of the source home base station from the handover notification message; or acquiring an address of the source home base station from a message header of the handover notification message; The MME/SGSN sends a relocation request message to the target MME/SGSN, where the relocation request message carries an address and/or an identifier of the source home base station;

And obtaining, by the target MME/SGSN, an address and/or an identifier of the source home base station from the relocation request message. Preferably, the method may further include the following feature, the method further includes: when the home base station policy function establishes a session with the BBF admission control network element, in the power-on process of the home base station, The external address, and the internal address and/or identification information are sent to the BBF admission control network element, and the BBF admission control network element stores an external address of the home base station, and an internal address and/or identification information.

Preferably, the foregoing method may further have the following features: the BBF admission control network element includes a Broadband Forum Policy Control Function (BPCF), or includes a BPCF and other BBF fixed network elements for admission control.

The present invention also provides a system for switching resource control between base stations, including a broadband forum (BBF) admission control network element, where:

The broadband control forum (BBF) admission control network element is configured to: when the user equipment switches from the source home base station to the target home base station, after receiving the admission request message of the target home base station policy function, determining whether the source home base station and the target home base station are Belong to the same routing path, and if so, allow admission requests.

Preferably, the system may further have the following features, the system further comprising: a target mobility management unit/service GPRS support node (MME/SGSN), a target home base station gateway or a target home base station, and a target home base station policy function, where:

The target MME/SGSN is configured to: when the user equipment switches from the source home base station to the target home base station, send a handover request message to the target home base station gateway or the target home base station, where the handover request message carries the source home base station Address and / or logo;

The target home base station gateway or the target home base station is configured to: after receiving the handover request message, send an authorization request message to the target home base station policy function, where the authorization request is cancelled Carrying an address and/or an identifier of the source home base station;

The target home base station policy function is configured to: after receiving the authorization request message, send an admission request message to the BBF admission control network element, where the admission request message carries an address and/or an identifier of the source home base station And an address and/or an identifier of the target home base station;

The BBF admission control network element is configured to: determine, according to an address and/or an identifier of the source home base station carried in the admission request message, and an address and/or an identifier of the target home base station, whether the source home base station and the target home base station belong to The same routing path.

Preferably, the above system may also have the following characteristics: the address is an internal address allocated by the mobile network and/or a local address allocated by the BBF fixed network.

Preferably, the foregoing system may further have the following feature: the BBF admission control network element is configured to: directly obtain the source according to the identifier and/or address of the source home base station and the target home base station carried in the admission request message An external address of the home base station and/or the target home base station, or mapping the identity or address of the home base station and/or the target base station to an external address; determining the source according to the external address of the source home base station and the target home base station Whether the home base station and the target home base station belong to the same routing path.

Preferably, the above system may further have the following features, the system further comprising: a source home base station, where:

The source home base station is configured to: send a handover notification message to the target MME/SGSN; the target MME/SGSN is further configured to: obtain an address and/or an identifier of the source home base station from the handover notification message; Or acquiring an address of the source home base station from a message header of the handover notification message;

Or the system further includes a source home base station and a source MME/SGSN, where

The source home base station is configured to: send a handover notification message to the source MME/SGSN;

The source MME/SGSN is configured to: obtain an address and/or an identifier of the source home base station from the handover notification message; or obtain an address of the source home base station from a message header of the handover notification message; Sending a relocation request message to the target MME/SGSN, where the relocation request message carries an address and/or an identifier of the source home base station;

The target MME/SGSN is further configured to: obtain the source from the relocation request message The address and/or identity of the home base station.

Preferably, the foregoing system may further have the following features: the home base station policy function is further configured to: when establishing a session with the BBF admission control network element in the power-on process of the home base station, the external address of the home base station, and The internal address and/or the identification information is sent to the BBF admission control network element. The BBF admission control network element is further configured to: save an external address of the home base station, and an internal address and/or identification information.

Preferably, the system may also have the following features: the BBF admission control network element includes a Broadband Forum Policy Control Function (BPCF), or includes a BPCF and other BBF fixed network elements for admission control.

In the method and system provided by the embodiment of the present invention, when the UE performs handover, when the UE is determined to cross the same backhaul, the UE is admitted, thereby avoiding the handover failure. BRIEF abstract

The accompanying drawings are intended to provide a In the drawing:

1 is a schematic diagram of a system architecture of an EPS;

Figure 2 is a BBF BPCF architecture diagram;

3 is a schematic diagram of a UE accessing an EPS core network through a fixed network BBF;

4 is a schematic diagram of a UE accessing an EPS core network through an H (e)NB mode;

Figure 5 is an architectural diagram of introducing H(e)NB PF under the FMC policy control architecture;

6 is a schematic diagram of interaction between H(e)NB PF and H(e)NB GW/MME and Sec-GW; FIG. 7 is a schematic diagram of interaction between H(e)NB PF and H(e)NB and Sec-GW;

Figure 8 is a schematic diagram of address allocation of RG as a routing method;

Figure 9 is a schematic diagram of address allocation of RG as a bridging mode;

Figure 10a is a diagram of UE switching between different Backhaul H(e)NBs;

Figure 1 Ob is a diagram of UE switching between H(e)NBs of the same Backhaul; Figure 11a is a flow chart of powering up the H(e)NB for the architecture shown in Figure 6;

Figure l ib is a flow diagram of the interaction between the H(e)NB GW/MME and the H(e)NB PF in the architecture shown in Figure 6;

Figure 12a is a flowchart of powering up the H(e)NB in the architecture shown in Figure 7;

Figure 12b is a flow diagram of an embodiment of H(e)NB and H(e)NB PF interactions for the architecture shown in Figure 7. Preferred embodiment of the invention

The technical solutions of the present invention are further described in detail below with reference to the accompanying drawings and specific embodiments to enable those skilled in the art to understand the invention. .

For the switching scenario where the two H(e)NBs belong to the same Backhaul, as shown in FIG. 10b, during the handover process, the UE initiates attachment on the Target H(e)NB and requests corresponding QoS resources for the service. The resources of the UE on the Source H(e)NB have not been released (because of the handover principle, "first connect and then break"). The core network needs to authorize the newly requested QoS resources of the UE when the Target H(e)NB accesses, and since the resources on the Source H(e)NB have not been released, if the current resources are tight, and the core network cannot determine this It is a Backhaul switch, and the QoS resource request authorization at this time may be rejected by the core network. In the routing mode (as shown in Figure 8), H(e)NB PF can judge that two H(e)NBs are from the same RG according to the same CPE address in the address of H(e)NB (the same Backhaul) ), can solve this problem, if the resources on the current Backhaul are not enough, the core network perceives that this is a cross-H(e)NB switch under Backhaul, which can accept new QoS requests; but in the bridge mode (Figure 9) As shown in the figure, since the address of H(e)NB is allocated by the fixed network BBF, the mobile core network (for example: H(e)NB PF) cannot know that the two H(e)NBs are from the same Backhaul (BBF solid) The network is Η (» ΝΒ allocation address according to the fixed network BBF address allocation principle, which is unknown to the mobile core network), resulting in the mobile core network can not accept new QoS resource request, will reject the request, then the UE The switch will fail.

The present invention provides a method for switching resource control between base stations, including:

When the user equipment switches from the source home base station to the target home base station, the broadband forum (BBF) is connected. After receiving the admission request message of the target home base station policy function, the control network element determines whether the source home base station and the target home base station belong to the same routing path, and if yes, allows the admission request.

The method further includes:

When the user equipment is handed over from the source home base station to the target home base station, the target mobility management unit/serving GPRS support node (MME/SGSN) sends a handover request message to the target home base station gateway or the target home base station, where the handover request message carries An address and/or an identifier of the source home base station; after receiving the handover request message, the target home base station gateway or the target home base station sends an authorization request message to the target home base station policy function, where the authorization request message is sent Carrying an address and/or an identifier of the source home base station;

The BBF admission control network element determines whether the source home base station and the target home base station belong to the same route according to the address and/or the identifier of the source home base station carried in the admission request message, and the address and/or the identifier of the target home base station. path. Specifically, the BBF admission control network element directly acquires an external address of the source home base station and/or the target home base station according to the identifier and/or address of the source home base station and the target home base station carried in the admission request message, Or mapping an identifier or an address of the home base station and/or the target base station to an external address; the BBF admission control network element 4 determining the source home base station according to an external address of the source home base station and the target home base station Whether the target home base station belongs to the same routing path.

The address is an internal address allocated by the mobile network and/or an external address allocated by the BBF fixed network.

The source home base station sends a handover notification message to the target MME/SGSN; the target MME/SGSN obtains an address and/or an identifier of the source home base station from the handover notification message; or Obtaining an address of the source home base station in a message header of the handover notification message; or

The source home base station sends a handover notification message to the source MME/SGSN;

Obtaining, by the source MME/SGSN, an address of the source home base station from the handover notification message And/or identifying; or: obtaining an address of the source home base station from a message header of the handover notification message; the source MME/SGSN sending a relocation request message to the target MME/SGSN, the relocation request The message carries the address and/or identifier of the source home base station;

And obtaining, by the target MME/SGSN, an address and/or an identifier of the source home base station from the relocation request message.

When the home base station policy function establishes a session with the BBF admission control network element, the home base station's external address, and the internal address and/or identification information are sent to the home base station. The BBF admission control network element, the BBF admission control network element stores an external address of the home base station, and an internal address and/or identification information.

The BBF admission control network element includes a Broadband Forum Policy Control Function (BPCF), or includes a BPCF and other BBF fixed network elements for admission control.

Embodiment 1

The embodiment includes two parts, and a part is a HeNB power-on process based on the architecture shown in FIG. 6, as shown in FIG. 11a, including:

Step 101: When the H(e)NB is powered on, an IP-Sec tunnel is established between the H(e)NB and the Sec-GW. Step 102: The Sec-GW sends an update H(e)NB binding message to the H(e)NB PF, where the message carries the address of the H(e)NB, where the address includes an internal address allocated by the mobile network and/or a BBF solid The external address assigned by the network.

Step 103: The H(e)NB PF returns a response to the Sec-GW.

Step 104: An S1/Iuh session is established between the H(e)NB and the H(e)NB GW/MME. During the session establishment, the H(e)NB sends the address and/or identifier information of the H(e)NB to the H(e)NB GW/MME, where the address includes the internal address assigned by the mobile network and/or the external address assigned by the BBF fixed network.

Step 105: The H(e)NB GW/MME initiates a setup session message to the H(e)NB PF, where the message may carry an external address of the H(e)NB, and an internal address and/or identification information, where the internal address is moved. Network allocation, external addresses are assigned by the BBF fixed network.

Step 106: The H(e)NB PF initiates a session establishment message to the BPCF, where the message may carry an external address of the H(e)NB, and an internal address and/or identification information, where the internal address is used by the mobile network. Allocation, external addresses are assigned by the BBF fixed network.

Step 107: After receiving the session establishment message, the BPCF stores the external address of the H(e)NB, and the internal address and/or the identification information, and saves the external address of the H(e)NB and the internal address. And/or identification information.

Another part of this embodiment is based on the H(e)NB GW/MME and the architecture shown in Figure 6.

A flow chart of H(e)NB PF interaction, as shown in Figure 1 lb, includes:

Step 201: When the UE switches between the H(e)NBs, the Source H(e)NB decides to trigger the SI-based handover.

Step 202: If the handover is a cross-MME/SGSN handover, the source H(e)NB sends a handover notification to the Source MME/SGSN, where the message carries the identifier of the Target H(e)NB, and the message may also carry the Source H(e). The address and/or identification information of the NB, where the address may be an internal address allocated by the mobile network and/or an external address assigned by the BBF fixed network.

Step 203: If the current handover is a cross-MME/SGSN handover, the source MME/SGSN may forward a relocation request message to the Target MME/SGSN, where the message may carry the address and/or identification information of the Source H(e)NB, where The address can be an internal address assigned by the mobile network and/or an external address assigned by the BBF fixed network. among them:

If the source MME/SGSN receives the identifier information or the internal address information from the source H(e)NB, the identifier information or the internal address information may be locally mapped to the external address information (see H in the first embodiment). e) The MME saves the H(e)NB address information in the NB power-on process); If the message from the Source H(e)NB does not carry the address and/or identification information of the Source H(e)NB, Source MME/ The SGSN may obtain the address information of the Source H(e)NB from the header of the received Source H(e)NB message, which is the internal address of the Source H(e)NB, and may also be obtained based on the internal address mapping. Source H(e)NB external address and/or identification information.

If the handover is not across the MME/SGSN, then the Target MME/SGSN and the Source MME/SGSN are the same. After receiving the handover notification, the MME/SGSN directly sends a handover request to the Target H(e)NB GW.

Step 204: After receiving the message from the source H(e)NB or the Source MME/SGSN, the Target MME/SGSN sends a handover request message to the Target H(e)NB GW, where the message carries the Source. The address and/or identity of H(e)NB. The address may be an internal address assigned by the mobile network and/or an external address assigned by the BBF fixed network.

Step 205: After receiving the handover request message, the Target H(e)NB GW sends an authorization request message (for QoS resource request) to the H(e)NB PF, where the message carries the address of the Source H(e)NB and/or Identification, where the address can be an internal address assigned by the mobile network and/or an external address assigned by the BBF fixed network.

Step 206: After receiving the authorization request message, the Target H(e)NB PF sends an admission request message to the BPCF, where the message carries the address and/or identifier of the Target H(e)NB, and carries the Source H(e)NB. Address and/or identification, where the address can be an internal address assigned by the mobile network and/or an external address assigned by the BBF fixed network.

Step 207: After receiving the accept request message, the BPCF determines, according to the external addresses of the source H(e)NB and the target H(e)NB, whether the two H(e)NBs belong to the same Backhaul; specifically, because H(e) The external address of the NB is allocated by the fixed network BBF to the H(e)NB, and the BBF fixed network can know the location of the H(e)NB according to the address information, thereby knowing the access backulul information of the H(e)NB; The H(e)NB and the target H(e)NB do not belong to the same Backhaul. The access Backhaul to which the current target H(e)NB belongs is in short supply and can reject the admission request. If Source H(e)NB and target H(e)NB belong to one access Backhaul, the request can be accepted even if the current Backhaul resource is scarce.

If the message contains only the identifier of the Source H(e)NB or the internal address information (there is no external address of the Source H(e)NB), the BPCF may assign other BBF fixed network elements (may not be the admission control of the BPCF). Decision), you can first map the source H (e) NB identification information or internal address to external address information (for example: based on the locally stored H (e) NB external address and the identity / internal address mapping relationship) Admission control.

Step 208: The BPCF returns a response to the Target H(e)NB PF.

Step 209: The Target H(e)NB PF returns the result of the admission request to the Target H(e)NB GW. Step 210: The Target H(e)NB GW sends a handover request to the Target H(e)NB.

Step 211: The Target H(e)NB returns a handover request response to the Target MME/SGSN.

Step 212: After receiving the handover request response, the Target MME/SGSN sends the response to the source MME/SGSN. A Forward Relocation Complete message is initiated to trigger subsequent release of Source H(e)NB resources.

Embodiment 2

This embodiment includes two parts, a part of which is shown in Figure 12a, which is based on the architecture shown in Figure 7.

H(e)NB power-on flowchart, including:

Step 301: When the H(e)NB is powered on, an IP-Sec tunnel is established between the H(e)NB and the Sec-GW. Step 302: The Sec-GW sends an update H(e)NB binding message to the H(e)NB PF, where the message carries the address of the H(e)NB, where the address includes an internal address allocated by the mobile network and/or a BBF solid The external address assigned by the network can also carry the identity of the H(e)NB.

Step 303: The H(e)NB PF returns a response to the Sec-GW.

Step 304: The H(e)NB PF sends a setup session message to the BPCF, where the message may carry an external address of the H(e)NB, and an internal address and/or identification information. The internal address is allocated by the mobile network, and the external address is set by the BBF. Fixed network allocation.

Step 305: After receiving the session establishment message, the BPCF stores the external address of the H(e)NB, and the internal address and/or identification information, and saves the external address of the H(e)NB, and the internal address and / or identification information.

Step 306: An S1/Iuh session is established between the H(e)NB and the H(e)NB GW/MME. During the session establishment, the H(e)NB sends the address and/or identification information of the H(e)NB to the H(e)NB GW/MME, where the address includes the internal address assigned by the mobile network and/or the external address assigned by the BBF fixed network.

Another part of the embodiment is shown in Figure 12b. The flowchart of the interaction between the H(e)NB GW/MME and the H(e)NB PF based on the architecture shown in Figure 7 includes:

Step 401: When the UE switches between the H(e)NBs, the Source H(e)NB decides to trigger the SI-based handover.

Step 402: If the handover is a cross-MME/SGSN handover, Source H(e)NB to Source

The MME/SGSN sends a handover notification message, where the message carries the identifier of the Target H(e)NB, and the message may also carry the address and/or identification information of the source H(e)NB, where the address may be an internal address allocated by the mobile network and / or an external address assigned by the BBF fixed network. Step 403: The source MME/SGSN sends a relocation request message to the Target MME/SGSN, where the message may carry the address and/or identification information of the Source H(e)NB, where the address may be an internal address allocated by the mobile network and/or The external address assigned by the BBF fixed network.

The source MME/SGSN may locally map the identifier information or the internal address information to the external address information if the switch notification message from the source H(e)NB receives only the identifier information or the internal address information (see the embodiment). In the H (e)NB power-on process, the MME stores the H(e)NB address information).

Step 404: After receiving the message from the source H(e)NB or the Source MME/SGSN, the Target MME/SGSN sends a handover request to the Target H(e)NB, where the message carries the address of the Source H(e)NB and/or Or logo. The address can be the internal address assigned by the mobile network and / or the external address assigned by the BBF fixed network.

If the message from the source H(e)NB or the Source MME/SGSN carries the address and/or identification information of the Source H(e)NB, the Target MME/SGSN uses the Source H(e) in the message. The address and/or identification information of the NB is sent to the Target H(e)NB (display mode); if it is received from the source H(e)NB or the Source MME/SGSN, it is not carried.

Source H(e)NB address and / or identification information, Target MME / SGSN can obtain the source H (e) NB address information from the header of the received Source H (e) NB message, the address is Source H(e)NB internal address (implicit mode).

If the handover is not a cross-MME/SGSN handover, the Target MME/SGSN and the Source MME/SGSN are the same. After receiving the handover notification, the MME/SGSN directly sends a handover request to the Target H(e)NB.

Step 405: After receiving the message, the Target H(e)NB sends an authorization request message (for QoS resource request) to the H(e)NB PF, where the message carries the address and/or identifier of the source H(e)NB, where the address It can be the internal address assigned by the mobile network and/or the external address assigned by the BBF fixed network.

Step 406: After receiving the authorization request message, the Target H(e)NB PF sends an admission request message to the BPCF, where the message carries the address and/or identifier of the Target H(e)NB, and carries the address of the Source H(e)NB. And/or identification, where the address can be an internal address assigned by the mobile network and/or an external address assigned by the BBF fixed network. Step 407: After receiving the accept request message, the BPCF determines, according to the addresses of the source H(e)NB and the target H(e)NB, whether the two H(e)NBs belong to the same Backhaul, if the source H(e)NB and The target H(e)NB does not belong to the same Backhaul. The access Backhaul to which the current target H(e)NB belongs is in short supply and can reject the admission request. If Source H(e)NB and target H(e)NB belong to one access Backhaul, the Backhaul resource is currently in short supply, and the request can be accepted.

If the message contains only the identifier of the Source H(e)NB or the internal address information (there is no external address of the Source H(e)NB), the BPCF may assign other BBF fixed network elements (may not be accepted by the BPCF). Control decision), mapping the identification information or internal address of the source H(e)NB to external address information (for example: based on the mapping relationship between the external address of the locally saved H(e)NB and the identifier/internal address), and then according to Source The external addresses of H(e)NB and target H(e)NB determine whether the two H(e)NBs belong to the same Backhaul (for example: Since the external address of H(e)NB is determined by the fixed network BBF as H(e) NB allocation, BBF fixed network can know the location of H(e)NB based on the address information, thus knowing the access backulul information of H(e)NB);

Step 408: The BPCF returns a response to the Target H(e)NB PF.

Step 409: The Target H(e)NB PF returns the result of the admission request to the Target H(e)NB. Step 410: The Target H(e)NB returns a handover request response to the Target MME/SGSN.

Step 411: After receiving the message, the Target MME/SGSN initiates a Forward Relocation Complete message to the Source MME/SGSN, and triggers subsequent release of the Source H(e)NB resource.

The broadband forum (BBF) accepts the control network element, and is configured to: after receiving the admission request message of the target home base station policy function, when the user equipment is handed over from the source home base station to the target home base station, determine whether the source home base station and the target home base station are Belong to the same routing path, and if so, allow admission requests.

The system further includes: a target mobility management unit/serving GPRS support node (MME/SGSN), a target home base station gateway or a target home base station, and a target home base station strategy function Yes, where:

The target MME/SGSN is configured to send, when the user equipment is switched from the source home base station to the target home base station, a handover request message to the target home base station gateway or the target home base station, where the handover request message carries the source home base station Address and / or logo;

And the target home base station gateway or the target home base station, after receiving the handover request message, sending an authorization request message to the target home base station policy function, where the authorization request message carries the source home base station Address and / or logo;

The target home base station policy function, after receiving the authorization request message, sends an admission request message to the BBF admission control network element, where the admission request message carries an address and/or an identifier of the source home base station And an address and/or an identifier of the target home base station;

The BBF admission control network element is configured to directly acquire the external source base station and/or the target home base station according to the identifier and/or address of the source home base station and the target home base station carried in the admission request message. Addressing, or mapping the identity or address of the home base station and/or the target base station to an external address; determining an external address of the source home base station and the target home base station to determine whether the source home base station and the target home base station belong to the same Routing path.

The system further includes: a source home base station, where:

The source home base station is configured to send a handover notification message to the target MME/SGSN;

The target MME/SGSN is further configured to acquire an address and/or an identifier of the source home base station from the handover notification message; or acquire an address of the source home base station from a message header of the handover notification message;

The source home base station is configured to send a handover notification message to the source MME/SGSN;

The source MME/SGSN is configured to acquire, by using the handover notification message, the source home base station And obtaining an address of the source home base station from a message header of the handover notification message; sending a relocation request message to the target MME/SGSN, where the relocation request message carries the The address and/or identity of the source home base station;

The target MME/SGSN is further configured to obtain an address and/or an identifier of the source home base station from the relocation request message.

The home base station policy function is further configured to send an external address of the home base station, and an internal address and/or identification information when establishing a session with the BBF admission control network element during the powering on of the home base station. Receiving a control network element to the BBF;

The BBF admission control network element is further configured to save an external address of the home base station, and an internal address and/or identification information.

Industrial Applicability The method and system provided by the embodiments of the present invention, when the UE performs handover, accepts the UE when it determines that the UE crosses the same backhaul, thereby avoiding the handover failure.

Claims

Claim

A method for switching resource control between base stations, comprising:

2. The method according to claim 1, wherein the method further comprises:

3. The method of claim 2, wherein the address is an internal address assigned by the mobile network and/or a local address assigned by the BBF fixed network.

4. The method according to claim 3, wherein the BBF admission control network element determines, according to an address and/or an identifier of the source home base station carried in the admission request message, and an address and/or an identifier of the target home base station. Whether the source home base station and the target home base station belong to the same routing path include: the BBF admission control network element directly acquiring the source according to the identifier and/or address of the source home base station and the target home base station carried in the admission request message An external address of the home base station and/or the target home base station, or mapping the identity or address of the home base station and/or the target base station to an external address;

The BBF admission control network element is based on an external address of the source home base station and the target home base station Determining whether the source home base station and the target home base station belong to the same routing path.

5. The method of claim 2, wherein the method further comprises

Or,

Obtaining, by the source MME/SGSN, an address and/or an identifier of the source home base station from the handover notification message; or acquiring an address of the source home base station from a message header of the handover notification message; The MME/SGSN sends a relocation request message to the target MME/SGSN, where the relocation request message carries an address and/or an identifier of the source home base station;

The method according to claim 1, wherein the method further comprises: when the home base station policy function establishes a session with the BBF admission control network element, in the power-on process of the home base station, The external address of the base station, and the internal address and/or identification information are sent to the BBF admission control network element, and the BBF admission control network element stores an external address of the home base station, and an internal address and/or identification information.

The method according to any one of claims 1 to 6, wherein the BBF admission control network element comprises a Broadband Forum Policy Control Function (BPCF), or comprises a BPCF and other BBF fixed network elements for admission control .

8. A system for switching resource control between base stations, comprising a broadband forum (BBF) admission control network element, wherein:

9. The system of claim 8, wherein the system further comprises: a target mobility management ticket Element/Serving GPRS Support Node (MME/SGSN), target home base station gateway or target home base station, target home base station policy function, where:

The target home base station gateway or the target home base station is configured to: after receiving the handover request message, send an authorization request message to the target home base station policy function, where the authorization request message carries the source home base station Address and / or logo;

10. The system of claim 9, wherein the address is an internal address assigned by the mobile network and/or a local address assigned by the BBF fixed network.

The system according to claim 10, wherein the BBF admission control network element is configured to: directly obtain an identifier according to an identifier and/or an address of a source home base station and a target home base station carried in the admission request message Determining an external address of the source home base station and/or the target home base station, or mapping the identity or address of the home base station and/or the target base station to an external address; determining, according to the external address of the source home base station and the target home base station Whether the source home base station and the target home base station belong to the same routing path.

12. The system of claim 9, wherein the system further comprises: a source home base station, wherein:

The source home base station is configured to: send a handover notification message to the target MME/SGSN; the target MME/SGSN is further configured to: obtain an address and/or an identifier of the source home base station from the handover notification message; Or acquiring an address of the source home base station from a message header of the handover notification message; Or the system further includes a source home base station and a source MME/SGSN, where the source home base station is configured to: send a handover notification message to the source MME/SGSN;

The target MME/SGSN is further configured to: obtain an address and/or an identifier of the source home base station from the relocation request message.

13. The system of claim 8 wherein

The home base station policy function is further configured to: when establishing a session with the BBF admission control network element in the power-on process of the home base station, send the external address of the home base station, and the internal address and/or the identification information to the The BBF accepts the control network element;

The BBF admission control network element is further configured to: save an external address of the home base station, and an internal address and/or identification information.

14. The system according to any one of claims 8 to 13, wherein the BBF admission control network element comprises a Broadband Forum Policy Control Function (BPCF), or comprises a BPCF and other BBF fixed network elements for admission control. .