ES2642689T3 - Flexible handover method and device - Google Patents

Description

DESCRIPTION

Method and flexible transfer device.

Field of the Invention

The present invention relates to mobile communications technologies and, in particular, to a flexible handover method and device 5.

Background of the invention

Indoor coverage of universal mobile telecommunications system signals (universal mobile telecommunications system, UMTS) has always been a problem faced by users and operators. The advent of the Femto network (Femto) is a good solution to this problem. The key elements 10 of the Femto network are a home NodeB (Home NodeB, HNB) and a home gateway NodeB (home gateway NodoB, HNB-GW). The HNB uses a standard air interface; a fixed broadband access network is used between the HNB and the HNB-GW as the return network; after the convergence of the HNB-GW, a standard lu interface is used to access the main network and, in this way, additional coverage of macrocell signals is achieved. Also, a Femto cell (femtocell) has a small coverage range, capable of performing user services more precisely. Therefore, operators pay more and more attention to the Femto network.

Location management is one of the most important functions of the devices on the main network side (main network, CN) and at the end of the radio access network (radio access network, RAN). When a user equipment (user equipment, EU) from the coverage of one cell gradually enters the coverage of another cell, a radioelectric network controller (radioelectric network controller, RNC) of the original cell and a 20 RNC of the cell new cell completes context switching through a signal exchange, to ensure

that the EU is able to receive or initiate services in the new cell. The Third Generation Associated Project

(3rd Generation Associated Project, 3GPP) defines a transfer process (relocation) to meet the requirements of the previous context switching between the RNCs. According to different forms of implementation, the transfer is classified as definitive transfer and flexible transfer. For flexible handover, a lur interface is used to manage radio resources between RNC, so that without a context transfer, a EU is capable

of entering a new cell without losses. In comparative terms, flexible handover has a better

user experience and a higher transfer success rate and, therefore, in a macro network, the flexible transfer form is preferred.

THE NOKIA SIEMENS NETWORKS document: "Macro to femto enhanced mobility for 3G", 3GPP DRAFT; R3- 30 112424_MACRO TO FEMTO ENHANCED MOBILITY FOR 3G, 3RD GENERATION PARTNERSHIP PROJECT

(3GPP), MOBILE COMPETENCE CENTER; 650, ROUTE DES LUCIOLES; F-06921 SOPHIA-ANTIPOLIS CEDEX; FRAnCiA, vol. RAN WG3, no. Zhuhai; 20111010, September 30, 2011 (2011-09-30), describes the enhanced mobility from macro to femto for 3G. A patent application, US 2003/129981 A1, describes an apparatus and method for achieving a transfer between mobile communications systems of different generations. Another patent application 35, US 2003/036387 A1, describes a relocation method, a system and a network element for changing a radioelectric service resources control entity. The HUAWEI document: "Discussion about Soft Handover for Enhanced H2H Mobility", 3GPP DRAFT; R3-102062 DISCSHO ENH H2H MOB REV0, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTER; 650, ROUTE DES LUCIOLES; F-06921 SOPHIA-ANTIPOLIS CEDEX; FRANCE, vol. RAN WG3, no. Madrid Spain; 20100823, August 15, 2010 (2010-08-15), describes the flexible handover for improved H2H mobility. The document "3rd Generation Partnership Project; Technical Specification Group RAN; UMTS and LTE; Mobility Enhancements for H (e) NB (Release 11)", 3GPP STANDARD; 3GPP TR 37.803, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTER; 650, ROUTE DES LUCIOLES; F-06921 SOPHIA-ANTIPOLIS CEDEX; FRANCL, vol. RAN WG3, no. V0.1.2, September 8, 2011 (2011-09-08), pages 1-15 describe improvements in mobility for H (e) NB.

However, due to the spatial nature of the Femto network, 3GPP does not currently define the implementation of flexible handover in the Femto network. Therefore, when a macrocell is adjacent to an HNB cell, a flexible handover process cannot be guaranteed without loss of user plane data.

Compendium of the invention

The present invention offers a flexible handover method and device, capable of implementing a flexible handover process between a macrocell and an HNB cell.

For a first aspect, the present invention offers a flexible handover method, which includes:

receive, by a gateway for access to housing, a request for flexible transfer sent by a node for access to housing, where the request for flexible transfer includes information on the user plan of the node for access to housing and a identifier of an RNC radioelectric network controller, where the plane information

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

of the user of the access node to the house includes an Internet protocol address, IP, of the user's plane and a user datagram protocol port number, UDP;

establish, by the access gateway to the dwelling according to the RNC identifier, a signaling connection mapping between the access node to the dwelling and the RNC, and forward the request for flexible transfer to the RNC based on the information connection resource forwarding assigned to the RNC, where the connection resource forwarding information includes an IP address of the user plane and a UDP port number that points to the access gateway to the dwelling if a means of link between the The access gateway to the dwelling and the RNC is IP over Ethernet, or the connection resource forwarding information includes a channel identifier that points to the access gateway to the dwelling and is needed to establish an adaptation layer link type 2, AAL2, asmchronous transfer mode, ATM, if the means of connection between the access gateway to the dwelling and the RNC is ATM;

receive, by the access gateway to housing, a flexible transfer response returned by the RNC according to the flexible transfer request, where the flexible transfer response includes information on RNC connection resources, where information on resources from RNC connection includes an IP address of the user plane and a UDP port number if the means of link between the access gateway to the home and the RNC is IP over Ethernet, or the RNC connection resource information includes an identifier The channel needed to establish an AAL2 link if the link between the HNB-GW and the RNC is ATM; Y

establish, by the access gateway to the dwelling, a mapping of the user plane connection between the access node to the dwelling and the RNC according to the information of the user plan of the access node to the dwelling, the information of Forwarding of connection resources, which forwards information of the user map assigned to the access node to the dwelling, and the information of connection resources of the RNC, and forwarding the flexible transfer response to the access node to the dwelling based on the Forwarding information of the user plan, where the information for re-sending of the user plan includes an IP address of the user plane and a UDP port number that points to the gateway to the house.

For a second aspect, the present invention offers a flexible handover method, which includes:

receive, from a gateway to the home, a flexible transfer request sent by an RNC radio network controller, where the flexible transfer request includes information on RNC connection resources and an identifier of an access node to the home NodeB home, where the RNC connection resource information includes an internet protocol address, IP, of the user plane and a user datagram protocol port number, UDP, if a means of link between the gateway of access to the dwelling and the RNC is IP over Ethernet, or the RNC connection resource information includes a channel identifier that is needed to establish an adaptation layer link of type 2, AAL2, asmchronous transfer mode, ATM, if a means of liaison between the access gateway to the dwelling and the RNC is ATM;

establish, by the access gateway to the dwelling, according to the identifier of the access node to the dwelling, a signaling connection mapping between the RNC and the access node to the dwelling, and forward the request for flexible transfer to the access node to the home based on the information of the user's plane forwarding assigned by the access gateway to the home, where the information of the user's plane forwarding includes a first information that points to the housing access gateway , the first information including an IP address of the user's plane and a UDP port number;

receive, by the access gateway to the dwelling, a flexible transfer response returned according to the request for flexible transfer by the access node to the dwelling, where the flexible transfer response includes information of the user plan of the node of access to the dwelling, and the information of the user plan of the access node to the dwelling includes an IP address of the user plan and a UDP port number; Y

establish, by the access gateway to the dwelling, a user-side connection mapping between the access node to the dwelling and the RNC according to the information of the user plan of the access node to the dwelling, the information of Forwarding of the user plane, which forwards the connection resources information assigned to the RNC, and the RNC connection resources information, and forwarding the flexible handover response to the RNC based on the connection resources forwarding information, where The connection resources forwarding information includes an IP address of the user plan and a UDP port number that point to the access gateway to the dwelling and which are assigned by the access gateway to the dwelling to the RNC if the means of The link between the access gateway to the dwelling and the RNC is IP over Ethernet, or the connection resource forwarding information includes a channel identifier that is needed to establish an AAL2 link, assigned by the Gateway to access the home to the RNC and which points to the gateway to the home if the means of connection between the gateway to the home and the RNC is ATM.

For the first aspect, the present invention offers a gateway for access to housing, which includes:

a first request reception means, configured to receive a flexible transfer request sent by a housing access node, where the flexible transfer request includes information of the user plan of the housing access node and an identifier of a RNC radioelectric network controller, where the information

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

The user plan of the access node to the home includes an Internet protocol address, IP, the user plan and a user datagram protocol port number, UDP;

a first means of signaling relationship processing, configured to establish, according to the RNC identifier, a signaling connection mapping between the access node to the dwelling and the RNC, and forwarding the flexible transfer request to the RNC based on the connection resource forwarding information assigned to the RNC, where the connection resource forwarding information includes an IP address of the user plan and a UDP port number that point to the access gateway to the dwelling if a link means between the access gateway to the dwelling and the RNC is IP over Ethernet, or the connection resource forwarding information includes a channel identifier that points to the access gateway to the dwelling and is needed to establish a layer link Type 2 adaptation, AAL2, asmchronous transfer mode, ATM, if the means of connection between the access gateway to the dwelling and the RNC is ATM;

a first response receiving means, configured to receive a flexible handover response returned by the RNC according to the flexible handover request, where the flexible handover response includes information on RNC connection resources, where the information on connection resources of the RNC includes an IP address of the user plane and a UDP port number of the RNC if the means of link between the access gateway to the dwelling and the RNC is IP over Ethernet, or the RNC connection resource information includes an identifier The channel needed to establish an AAL2 link if the link between the HNB-GW and the RNC is ATM; Y

a first means of user relationship processing, configured to establish a mapping of the user's plane between the access node to the dwelling and the RNC according to the information of the user plan of the access node to the dwelling, the information of Forwarding of connection resources, which forwards information of the user map assigned to the access node to the dwelling, and the information of connection resources of the RNC, and forwarding the flexible transfer response to the access node to the dwelling based on the User plan forwarding information includes an IP address of the user plan and a UDP port number that points to the access gateway to the home.

For the second aspect, the present invention offers a gateway for access to housing, which includes:

a second request reception means, configured to receive a flexible transfer request sent by an RNC radio network controller, where the flexible transfer request includes information on RNC connection resources and an identifier of a housing access node home NodeB, where the RNC connection resource information includes an internet protocol address, IP, of the user plane and a user datagram protocol port number, UDP, if a means of link between the access gateway to the home and the RNC is IP over Ethernet, or the RNC connection resource information includes a channel identifier that is needed to establish a type 2 adaptation layer link, AAL2, asmchronous transfer mode, ATM, if a means of liaison between the access gateway to the dwelling and the RNC is ATM;

a second means of signaling relationship processing, configured to establish, according to the identifier of the housing access node, a signaling connection mapping between the RNC and the housing access node, and forwarding the request for flexible transfer to the access node to the dwelling based on the information on the re-sending of the user plan assigned by the access gateway to the dwelling to the access node to the dwelling, where the information for the re-sending of the user plan includes a first information which points to the access gateway to the dwelling, the first information including an IP address of the user's plan and a UDP port number;

a second response reception means, configured to receive a flexible handover response returned according to the flexible handover request by the access node to the dwelling, where the flexible handover response includes information of the user plane of the access node to the dwelling, and the information of the user's plan of the access node to the dwelling includes an IP address of the user's drawing and a UDP port number; Y

a second means of user relationship processing, configured to establish a mapping of the user's plane between the access node to the dwelling and the RNC according to the information of the user plan of the access node to the dwelling, the information for forwarding the user plane, which forwards the connection resource information assigned to the RNC, and the RNC connection resource information, and forwarding the flexible handover response to the RNC based on the connection resource forwarding information, where the connection resources forwarding information includes an IP address of the user plan and a UDP port number that point to the access gateway to the dwelling and which are assigned by the access gateway to the dwelling to the RNC if the medium The link between the access gateway to the dwelling and the RNC is IP over Ethernet, or the connection resources forwarding information includes a channel identifier that is needed to establish a AAL2 link, assigned by the housing access gateway to the RNC and pointing to the housing access gateway if the means of link between the housing access gateway and the RNC is ATM.

5

10

fifteen

twenty

25

30

35

40

Four. Five

For the flexible handover method, the housing access gateway, the housing access node, and the RNC radio network controller offered according to the present invention for the second aspect, when the RNC initiates a handover operation flexible to the housing access node, a signaling connection is established with the housing access gateway, and the housing access gateway establishes a signaling connection mapping and a user plane connection mapping between the Housing access node and the RNC, to complete the data forwarding of the user plane and signaling between the housing access node and the RNC, thus implementing a flexible transfer between a macrocell and an access node cell to the House.

Brief description of the drawings

Figure 1A is a schematic network topological diagram of a flexible handover process in the prior art;

Figure 1B is a schematic network topological diagram of a macrocell adjacent to an HNB cell according to an embodiment of the present invention;

Figure 1C is a schematic network topological diagram of an HNB and an RNC that establish a signaling connection and complete a flexible handover function;

Figure 1D is a schematic network topological diagram of an HNB-GW and an RNC that establish a signaling connection and complete a flexible handover function;

Figure 2 is a flow chart of a flexible handover method carried out by an HNB and an RNC according to an embodiment of the present invention;

Figure 3 is a flow chart of a flexible handover method carried out by an HNB and an RNC according to another embodiment of the present invention;

Figure 4A is a flow chart of a flexible handover method performed by an HNB and an RNC when a link between the RNC and the HNB-GW is IP over Ethernet according to an embodiment of the present invention;

Figure 4B is a flow chart of a flexible handover method carried out by an HNB and an RNC when a link between the RNC and the HNB-GW is the ATM according to an embodiment of the present invention;

Figure 5A is a flow chart of a flexible handover method carried out by an HNB and an RNC according to another embodiment of the present invention;

Figure 5B is a flow chart of a flexible handover method carried out by an HNB and an RNC according to even another embodiment of the present invention;

Figure 6 is a flow chart of a flexible handover method carried out by an HNB and an RNC when a link between the RNC and the HNB-GW is IP over Ethernet according to another embodiment of the present invention;

Figure 7A is a schematic network topological diagram of a macrocell adjacent to a HeNB cell according to an embodiment of the present invention;

Figure 7B is a flow chart of a flexible handover method carried out by a HeNB and an RNC when a link between the RNC and the HeNB-GW is IP over Ethernet according to an embodiment of the present invention;

Figure 8A is a schematic structural diagram of a housing access gateway according to an embodiment of the present invention;

Figure 8B is a schematic structural diagram of a housing access gateway according to another embodiment of the present invention;

Figure 9A is a schematic structural diagram of a housing access node according to an embodiment of the present invention;

Figure 9B is a schematic structural diagram of a housing access node according to another embodiment of the present invention;

Figure 10A is a schematic structural diagram of a housing access gateway according to even another embodiment of the present invention;

Figure 10B is a schematic structural diagram of a housing access gateway according to even another embodiment of the present invention;

Figure 11A is a schematic structural diagram of an RNC according to an embodiment of the present invention;

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

Figure 11B is a schematic structural diagram of an RNC according to another embodiment of the present invention; Y

Figure 12 is a schematic structural diagram of a housing access node according to another embodiment of the present invention.

Detailed description of the achievements

Figure 1A is a schematic network topological diagram of a flexible handover process in the prior art.

As shown in Figure 1A, the network mainly includes: a general packet service via radio (general packet service via radio, GPRS) GPRS gateway support node (GPRS gateway support node, GGSN) 11, a GPRS service support node (GRPS service support node, SGSN) 12 connected to the GGSN 11, a first RNC 13, a second RNC 14 that are connected to the SGSN 12, a first NodeB (NodeB) 15 connected to the first RNC 13, and a second NodeB 16 connected to the second RNC 14. The first RNC 13 and the first NodeB15 form a first macrocell, and the second RNC 14 and the second NodeB 16 form a second macrocell. Assuming that an EU 17 gradually moves from the first macrocell to the second macrocell. Before a flexible handover, EU 17 accesses the first NodeB 15; Devices where the context information of EU 17 is located include: GGSN 11, SgSn 12, and the first RNC 13; data paths of EU 17 include: GGSN 11, SGSN 12, first RNC 13, and first Node 15. After the flexible handover, the devices where the context information of EU 17 is located remain unchanged and also include : GGSN 11, SGSN 12, and the first RNC 13; The data paths of EU 17 change, and the data paths of EU 17 after flexible handover include: gGsN 11, SGSN 12, first RNC 13, second RNC 14, and second NodeB 16.

From the previous one it can be observed that: when flexible handover occurs, the context information of EU 17 is not transferred, but the first RNC 13 initiates a request to establish a path from the first RNC 13 to the second RNC 14. Meanwhile , the corresponding area interface resources are assigned to the second RNC 14 to allow a data packet of the EU 17 to be transmitted through the path between the first RNC 13 and the second RNC 14 and through the second RNC 14. In comparison with a definitive handover, flexible handover offers a better user experience and a higher handover success rate.

Figure 1B is a schematic network topological diagram of a macrocell adjacent to an HNB cell according to an embodiment of the present invention. As shown in Figure 1B, the network mainly includes: a GGSN 21, an SGSN 22 connected to the GGSN 21, an RNC 23 and an HNB-GW 24 that are connected to the SGSN 22, a NodeB 25 connected to the RNC 23 , and an HNB 26 connected to the HNB-GW 24.

For a network topology where a macrocell is adjacent to an HNB cell, if the previous flexible handover concept is applied directly, the following two flexible handover processes are obtained.

A first flexible handover process includes: establishing, by the HNB 26, a signaling connection with the RNC 23 through a lur interface, and completing a flexible handover function, where the network topology after the connection is shown in Figure 1C. The flexible handover process is the same as the flexible handover process between two macro cells (ie, two RNCs) in the prior art.

However, the amount of HNB 26 is huge, possibly reaching thousands of HNB 26, and the number of lur connections of RNC 23 is far from being able to meet the demands of such amounts of HNB 26. In addition, too many connections Signals are very likely to result in impacts on a network. Also, for RNC 23, the quantity and locations of HNB 26 often change and, therefore, the connection relationships between RNC 23 and HNB 26 are not planned statically, resulting in a high cost of maintenance. Therefore, the flexible handover process is not as practical, and it does not solve the problem of flexible handover between a macrocell and an HNB cell.

A second flexible handover process includes: establishing, by the HNB-GW 24, a connection to the RNC 23 through a lur interface, and completing the flexible handover function, where the network topology after the connection is shown in Figure 1D. The flexible handover process is also the same as the flexible handover process between two RNCs in the prior art.

However, for HNB-GW 24, it is necessary to implement functions of an RNC. That is, a complete radioelectric network subsystem application (RNSAP) application protocol stack must be included, which does not conform to the HNB-GW 24 implementation architecture stipulated by the current protocol, and the cost is high . Therefore, the flexible handover process is also not so practical, and it does not solve the problem of flexible handover between a macrocell and an HNB cell.

Consequently, the present invention offers a flexible handover method implemented based on the current architecture, which is used to solve a flexible handover problem when a macrocell is adjacent to an HNB cell, and also solves the above problems. Next, the flexible transfer method according to the present invention is described in detail through specific embodiments.

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

A flexible transfer method according to an embodiment of the present invention that is described from the perspective of a housing access gateway includes:

receive, by a gateway for access to housing, a request for flexible transfer sent by a node for access to housing, where the request for flexible transfer includes information on the user plan of the node for access to housing and an identifier of an RNC;

establish, by the access gateway to the dwelling according to the RNC identifier, a signaling connection mapping between the access node to the dwelling and the RNC, and forward the request for flexible transfer to the RNC based on the information of connection resources forwarding assigned to the RNC, where the information of connection resources forwarding includes information that points to the housing access gateway;

receive, by means of an access gateway to the dwelling, a flexible transfer response returned by the RNC according to the flexible transfer request, where the flexible transfer response includes information on RNC connection resources; Y

establish, by the access gateway to the dwelling, a mapping of the user plane connection between the access node to the dwelling and the RNC according to the information of the user plan of the access node to the dwelling, the information of forwarding of connection resources, forwarding information of the user map assigned to the access node to the dwelling, and the information of connection resources of the RNC, and forwarding the flexible transfer response to the access node to the dwelling based on the information of re-sending of the user's plan, where the information of re-sending of the user's plane includes information that points to the access gateway to the house.

A flexible transfer method according to an embodiment of the present invention that is described from the perspective of a housing access gateway includes:

send, by a node of access to housing, a request for flexible transfer to a gateway of access to housing, to allow the gateway to access the home to establish a signaling connection mapping between the access node to the dwelling and an RNC according to the flexible transfer request, where the flexible transfer request includes information on the user plan of the housing access node and an RNC identifier; Y

receive, by the access node to the dwelling, a flexible transfer response sent by the access gateway to the dwelling, where the flexible transfer response is returned by the RNC to the access gateway to the dwelling according to the request of flexible transfer forwarded by the access gateway to the house, and is forwarded by the access gateway to the house to the access node to the house after the access gateway to the house establishes a mapping of the user's plane connection between the access node to the dwelling and the RNC according to the flexible transfer response, the flexible transfer response includes forwarding information of the user plan assigned by the access gateway to the housing to the access node to the housing, and the information of Forwarding of the user plan includes information that points to the access gateway to the house.

A flexible transfer method according to another embodiment of the present invention that is described from the perspective of a housing access gateway includes:

receive, by means of an access gateway to housing, a flexible transfer request sent by an RNC, where the flexible transfer request includes information on RNC connection resources and an identifier of a housing access node;

establish, by the access gateway to the dwelling according to the identifier of the access node to the dwelling, a signaling connection mapping between the RNC and the access node to the dwelling, and forward the request for flexible transfer to the node of access to the home based on the information on the re-sending of the user plan assigned to the access node to the house, where the information on the re-sending of the user plan includes information that points to the access gateway to the house;

receive, by a gateway of access to housing, a flexible transfer response returned by the access node to the house according to the flexible transfer request, where the flexible transfer response includes information of the user plane of the access node to the house; Y

establish, by the access gateway to the dwelling, a mapping of the user plane connection between the access node to the dwelling and the RNC according to the information of the user plan of the access node to the dwelling, the information of Forwarding of the user plane, which forwards connection resource information assigned to the RNC, and the RNC connection resource information, and forwarding the flexible handover response to the RNC based on the re-connection of the connection resource information, where the Information on connection resources reenvfo includes information that points to the access gateway to the house.

A flexible handover method according to another embodiment of the present invention that is described from the perspective of an RNC includes:

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

send, by an RNC, a flexible transfer request to a housing access gateway, to allow the housing access gateway to establish a signaling connection mapping between a housing access node and the RNC according to the request for flexible transfer, where the request for flexible transfer includes information on RNC connection resources and an identifier of the access node for housing; Y

receive, by the RNC, a flexible handover response sent by the housing access gateway, where the flexible handover response is returned by the housing access node to the housing access gateway according to the request of Flexible handover forwarded by the housing access gateway, and is forwarded by the housing access gateway to the RNC after the housing access gateway establishes a mapping of the user's plane connection between the access node to housing and the RNC according to the flexible handover response, the flexible handover response includes forwarding connection resource information assigned by the housing access gateway to the RNC, and the connection resource forwarding information includes information that points to the access gateway to the house.

A flexible handover method according to another embodiment of the present invention that is described from the perspective of a housing access node includes:

receive, by a housing access node, a flexible transfer request forwarded by a housing access gateway based on the forwarding information of the user plan assigned to the housing access node, where the transfer request flexible includes a housing access node identifier, the flexible transfer request is sent by an RNC to the housing access gateway, and forwarded after the housing access gateway establishes a signaling connection mapping between the RNC and the access node to the dwelling according to the request for flexible transfer, and the information for forwarding the user plan includes information that points to the access gateway to the dwelling; Y

send, by the access node to the dwelling, a flexible transfer response to the access gateway to the dwelling according to the flexible transfer request, where the flexible transfer response includes information of the user plane of the access node to the housing, to allow the access gateway to the dwelling to establish a mapping of the user's plane connection between the access node to the dwelling and the RNC according to the flexible transfer response, and forward the flexible transfer response to the RNC.

In each of the following embodiments, the housing access gateway is an HNB-GW, and the housing access node is an HNB. Alternatively, the housing access gateway is a HeNB-GW, and the housing access node is a HeNB.

In each of the following embodiments, the housing access node establishes a signaling connection with the RNC through the housing access gateway, and the housing access gateway establishes a signaling connection mapping and a mapping of the user plane connection between the access node to the dwelling and the RNC, to complete the data forwarding of the user plane and signaling between the access node to the dwelling and the RNC, thus implementing a flexible transfer between a macrocell and a cell to access the housing node.

The process of the flexible transfer method according to the present invention is described in detail in the following embodiments, where in each of the following embodiments the access gateway to the house is an HNB-GW, and the access node to the house is an HNB.

Figure 2 is a flow chart of a flexible handover method carried out by an HNB and an RNC according to an embodiment of the present invention. As shown in Figure 2, the method according to the embodiment includes the following steps:

Step 201: An HNB-GW receives a flexible handover request sent by an HNB, where the flexible handover request includes information of the HNB's user plan and an identifier of an RNC.

In the embodiment, the HNB implements a complete RNSAP protocol stack, offers a logical interface, and carries out the necessary processing of resources and signaling, such as the start of measurements and management of radioelectric resources.

The HNB makes a flexible transfer decision according to information, such as measured signal power, and initiates a flexible transfer request to the RNC through the HNB-GW when a flexible transfer requirement is met. Therefore, when the flexible handover requirement is met, the HNB sends a flexible handover request to the HNB-GW, where the flexible handover request carries information of the HNB user's plane and an identifier of the handover destination RNC .

The HNB user plane information mainly includes an internet protocol address (Internet protocol, IP) of the user plane and a user datagram protocol port number (user datagram protocol, UDP), which does not It is limited herein. The identifier of the RNC can be obtained from a signal measured by the HNB.

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

Step 202: The HNB-GW establishes, according to the identifier of the RNC, a signaling connection mapping between the HNB and the RNC, and forwards the request for flexible transfer of the RNC based on the information on the transfer of connection resources assigned to the RNC

In the embodiment, the HNB-GW establishes a signaling connection with the RNC by configuring a physical lur interface.

After receiving the flexible transfer request sent by the HNB, the HNB-GW obtains, from the flexible transfer request, the information of the HNB user plane and the RNC identifier, records the information of the HNB user plane and simultaneously identifies and addresses the RNC according to the RNC identifier.

In addition, an identifier that can unequivocally identify the HNB is stored in advance in the HNB-GW. The HNB identifier is generally determined by the HNB-GW according to a registration request sent by the HNB. During communication, the HNB-GW identifies an HNB according to the stored HNB identifiers. Therefore, when a flexible transfer request is received, the HNB-GW learns and obtains the HNB identifier that sends the flexible transfer request. The identifier of the HNB can be a name (id) or a coupling number of the flow control transmission protocol (flow control transmission protocol, SCTP) of the HNB.

The HNB-GW identifies, according to the RNC identifier, that the HNB needs assistance to perform the flexible handover, and links the HNB identifier with the RNC identifier, so that a signaling connection mapping between the HNB and the RNC. The HNB also assigns the connection resource forwarding information used to establish a connection with the RNC, and forwards the flexible transfer request to the RNC based on the connection resource forwarding information.

The connection resources forwarding information includes information that points to the HNB-GW. The information on the re-envfo of connection resources varies according to the different link between the HNB-GW and the RNC. For example, if the link between the HNB-GW and the RNC is IP over Ethernet (IP over Ethernet), the connection resource forwarding information mainly includes an IP address of the user plane and a UDP port number that They point to the HNB-GW. If the link between the HNB-GW and the RNC is an asmchronous transfer mode (asmchronous transfer mode, ATM), the connection resource forwarding information mainly includes a channel identifier, such as a path identifier virtual (virtual path identifier, VPI), a virtual channel identifier (virtual channel identifier, VCI), and a channel ID (CID), which points to the HNB-GW and is required to establish a layer link of type 2 ATM adaptation (type 2 adaptation layer, AAL2, ATM). The VPI and the VCI are used to distinguish different permanent virtual circuits (permanent virtual circuit, PVC), and the CID is used to distinguish a user in a PVC.

Specifically, after the RNC is addressed according to the RNC identifier, the HNB-GW can eliminate the RNC identifier of the flexible transfer request, replace the information of the HNB user plane in the flexible transfer request with the information for redirection of assigned connection resources, and then send the flexible transfer request to the RNC. For example, if the link between the HNB-GW and the RNC is IP over Ethernet, the HNB-GW replaces an IP address of the user plane and a UDP port number of the HNB in the request for flexible transfer with the address User plane IP and the UDP port number that the HNB-GW points and that are assigned by the HNB-GW. If the link between the HNB-gW and the RNC is ATM, the HNB-GW replaces the IP address of the user plane and the UDP port number of the HNB in the flexible transfer request with the VPI, the VCI, and the CID that point to the HnB-GW and that are assigned by the HNB-GW.

Step 203: The HNB-GW receives a flexible handover response returned by the RNC according to the flexible handover request, where the flexible handover response includes information on RNC connection resources.

After the HNB-GW forwards the flexible transfer request to the RNC, the RNC carries out operations, such as the allocation of resources to prepare for the flexible transfer, and returns a flexible transfer response to the HNB-GW, where the flexible handover response carries the RNC connection resources information. The information on RNC connection resources is also related to the link between the HNB-GW and the RNC. If the link between the HNB-GW and the RNC is IP over Ethernet, the RNC connection resource information mainly includes an IP address of the user plane and a RNC UDP port number. If the link between the HNB-GW and the RNC is ATM, the RNC connection resource information mainly includes a channel identifier, such as a VPI, a VCI, and a CID, which is necessary to establish a AAL2 link.

The HNB-GW receives the flexible handover response sent by the RNC, obtains, from the flexible handover response, the RNC connection resources information, and records the RNC connection resources information.

Step 204: The HNB-GW establishes a mapping of the user plane connection between the HNB and the RNC according to the HNB user plane information, the connection resource forwarding information, which forwards the user plane information assigned to the HNB, and the RNC connection resource information, and forwards the flexible handover response to the HNB based on the forwarding information of the user plane.

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

In the embodiment, the HNB-GW also assigns the user plane forwarding information to the HNB, which is used to establish a connection with the HNB during the flexible handover process. The user plane forwarding information includes information pointed to by the HNB-GW. The user plane forwarding information mainly includes an IP address of the user plane and a UDP port number that points to the HNB-GW. The HNB-GW can assign the user plane forwarding information to the HNB when it receives the flexible transfer request from the HNB or assign the user plane forwarding information to the HNB when it receives the flexible transfer response.

To ensure that the user plane data between the HNB and the RNC can be forwarded to each other, the HNB-GW links the information of the HNB user plane, the user plane forwarding information, the resource forwarding information of connection, and the information of connection resources of the RNC, in order to establish a mapping of the user plane connection between the HNB and the RNC.

Next, the HNB-GW replaces the RNC connection resource information in the flexible handover response with the user plane forwarding information that points to the HNB-GW and that the HNB-GW assigns, and sends the response from Flexible transfer to the HNB.

At this point, the HNB-GW establishes the signaling connection mapping and the user plane connection mapping between the HNB and the RNC, so that the user plane data and signaling between the HNB and the RNC can be Forward successfully, thus implementing the flexible handover between the HNB and the RNC.

In the embodiment, the HNB-GW implements an RNSAP protocol stack proxy, offers a physical luric interface, and establishes a signaling connection with the RNC, to allow the HNB to establish a logical connection with the RNC; The exchange of user plane data and signaling between the HNB and the RNC is completed through the HNB-GW, thus implementing the flexible handover process and solving the flexible handover problem when a macrocell is adjacent to an hNb cell. Flexible handover has a short delay, and a higher handover success rate compared to definitive handover, thus implementing flexible handover between an HNB cell and an RNC cell and improving the user experience. In addition, due to the HNB-GW proxy, the RNC can support a large amount of HNB to simultaneously establish logical connection relationships with the RNC; therefore, the flexible transfer between an RNC cell and an HNB cell is neither limited by the amount of RNC lur connections, nor affected by changes in the location of the HNB. In addition, because the HNB-GW establishes a physical connection with the RNC, the number and location changes of the HNB have no effect on the cost of maintenance or the signaling load, so that the network operates in a state Low load, easy planning and easy maintenance. Likewise, the HNB-GW only acts as a proxy for the RNSAP protocol stack, and does not need to include the RNSAP protocol stack, so that the HNB-GW does not conflict with the architecture stipulated by the protocol, which collaborates with the evolution towards the protocol and results in a lower implementation cost.

The above embodiment describes the process of a flexible handover method according to the present invention from the perspective of the HNB-GW; The following embodiment describes the flexible handover method according to the present invention from the perspective of an HNB.

Figure 3 is a flow chart of a flexible handover method carried out by an HNB and an RNC according to another embodiment of the present invention. As shown in Figure 3, the transfer method according to the embodiment includes the following steps:

Step 301: An HNB sends a flexible transfer request to an HNB-GW, to allow the HNB-GW to establish a signaling connection mapping between the HNB and the RNC according to the flexible transfer request, where the flexible transfer request It includes information on the HNB user map and an RNC identifier.

In the embodiment, the HNB implements a complete RNSAP protocol stack, offers logical interfaces, and carries out the necessary resource processing and signaling, such as the start of measurements and management of radioelectric resources.

The HNB makes a flexible transfer decision according to information, such as measured signal power, and initiates a flexible transfer request to the RNC through the HNB-GW when a flexible transfer requirement is met. Therefore, when the flexible handover requirement is met, the HNB sends a flexible handover request to the HNB-GW, where the flexible handover request carries information of the HNB user's plane and an identifier of the handover destination RNC .

The information of the HNB user plane mainly includes an IP address of the user plane and a UDP port number, which is not limited herein. The identifier of the RNC can be obtained from a measured signal from the HNB.

After receiving the flexible transfer request, the HNB-GW obtains, from the flexible transfer request, the information of the HNB user plane and the RNC identifier, records the information of the HNB user plane, and simultaneously identifies and addresses the RNC according to the identifier of the RNC. The HNB-GW identifies, according to the RNC identifier, that the HNB needs assistance to perform the flexible handover and, therefore, links a

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

HNB identifier with the RNC identifier, so that a signaling connection mapping between the HNB and the RNC is established. The HNB also assigns connection resource forwarding information used to establish a connection with the RNC, and forwards the flexible transfer request to the RNC based on the connection resource forwarding information. For information on connection resource forwarding, reference can be made to step 202.

After the HNB-GW forwards the flexible transfer request to the RNC, the RNC carries out operations, such as the allocation of resources, to prepare for the flexible transfer, and returns a flexible transfer response to the HNB-GW , where the flexible handover response carries information on RNC connection resources.

The HNB-GW receives the flexible handover response sent by the RNC, obtains, from the flexible handover response, the RNC connection resources information, and records the RNC connection resources information.

The HNB-GW also assigns to the HNB, user plane forwarding information, which is used to establish a connection with the HNB during the flexible handover process. The user plane forwarding information includes information that points to the HNB-GW. The user plane forwarding information mainly includes an IP address of the user plane and a UDP port number that points to the HNB-GW. The HNB-GW can assign the user plane forwarding information to the HNB when it receives the flexible transfer request from the HNB or assign the user plane forwarding information to the HNB when it receives the flexible transfer response.

To ensure that the user plane data between the HNB and the RNC can be forwarded to each other, the HNB-GW links the user plane information of the HNB, the user plane forwarding information, the resource forwarding information of connection, and the information of connection resources of the RNC, in order to establish a mapping of the user plane connection between the HNB and the RNC. The HNB user plane information corresponds to the user plane forwarding information, the user plane forwarding information corresponds to the connection resources forwarding information, and the connection resources forwarding information corresponds to RNC connection resources and, therefore, the user plane connection mapping is established between the HNB and the RNC, to ensure that the user plane data between the HNB and the RNC is mutually forwarded through the HNB-GW.

Next, the HNB-GW replaces the RNC connection resource information in the flexible handover response with the user plane forwarding information and sends the flexible handover response to the HNB.

Step 302: The HNB receives a flexible handover response sent by the HNB-GW, where the flexible handover response is returned by the RNC to the HNB-GW according to the flexible handover request forwarded by the HNB-GW, and is forwarded to the HNB after the HNB-GW establishes a mapping of the user plane connection between the HNB and the RNC according to the flexible handover response, and the flexible handover response includes forwarding information of the user plane assigned to the HNB by the HNB-GW.

The process of receiving the flexible handover response from the HNB includes: forwarding, by the HNB-GW, the flexible handover request to the RNC, and returning, by the RNC, the flexible handover response to the HNB- GW according to the request for flexible transfer; establish, by the HNB-GW, a mapping of the user plane connection between the HNB and the RNC according to the flexible handover response, and send the handover handover response to the HNB; receive, by the HNB, the flexible handover response forwarded by the HNB-GW. At this point, the HNB-GW establishes the signaling connection mapping and the user plane connection mapping between the HNB and the RNC, so that the user plane data and signaling between the HNB and the RNC can be Forward successfully, thus implementing the flexible handover between the HNB and the RNC.

In the embodiment, the HNB establishes a signaling connection with the RNC through the HNB-GW, the HNB establishes a logical connection with the RNC, and the HNB-GW establishes a physical connection with the RNC, so that the exchange of user plane data and signaling between the HNB and the RNC is completed through the hNB-GW, thus implementing the flexible handover process, solving the flexible handover problem when a macrocell is adjacent to an hNb cell, and improving User experience In addition, due to the HNB-GW proxy, the RNC can support a large amount of HNB to simultaneously establish logical connection relationships with the RNC; therefore, the flexible transfer between an RNC cell and an HNB cell is neither limited by the number of RNC connections, nor affected by changes in the location of the HNB. In addition, because the HNB-GW establishes a physical connection with the RNC, the number and location changes of the HNB have no effect on the cost of maintenance or the signaling load, so that the network operates in a state of Low load, easy planning and easy maintenance. Likewise, the HNB-GW only acts as a proxy for the RNSAP protocol stack, and does not need to include the RNSAP protocol stack, so that the HNB-GW does not conflict with the architecture stipulated by the protocol, which collaborates with the evolution towards the protocol and results in a lower implementation cost.

In each of the above embodiments, before the HNB sends a flexible handover request to the HNB-GW, the HNB-GW establishes a signaling connection with the RNC when configuring a physical luric interface. In addition, before the HNB submits a flexible transfer request for the HNB-GW, the HNB sends a registration request to the

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

HNB-GW to register with the HNB-GW, and the HNB-GW determines and stores an HNB identifier according to the registration request. The HNB-GW can obtain a name (HNB id of the registration request, and use the name of the HNB as the identifier of the HNB. The HNB-GW can also assign a SCTP coupling number to the HNB according to the registration request received, and use the SCTP coupling number as the identifier of the HNB.

Also, in each of the above embodiments, after the HNB receives the flexible handover response forwarded by the HNB-GW, any one or more of the following operations may be included:

The HNB sends a signaling message to the HNB-GW; The HNB-GW resends the signaling message to the RNC according to the signaling connection mapping between the HNB and the RNC. Specifically, the HNB can send a signaling message to the HNB-GW through a SCTP connection with the HNB-GW; The HNB-GW finds the RNC according to the signaling connection map between the HNB and the RNC, and forwards the signaling message to the RNC through an SCCP connection with the RNC.

The HNB sends downlink data to the HNB-GW according to the user plane forwarding information; the HNB-GW forwards the downlink data to the RNC according to the user plane connection mapping between the HNB and the RNC based on the connection resource forwarding information that points to the HNB-GW and is assigned to the RNC

The RNC sends uplink data to the HNB-GW based on the connection resources forwarding information; the HNB-GW forwards the uplink data to the HNB according to the user plane connection mapping between the HNB and the RNC based on the forwarding information of the user plane that points to the HNB-GW and is assigned to the HNB; and the HNB receives the uplink data sent by the RNC and forwarded by the HNB-GW.

Also, after the end of the service, the HNB sends a flexible transfer termination request to the HNB-GW; The hNB-GW forwards the flexible handover termination request to the RNC according to the signaling connection mapping between the HNB and the RNC, receives a flexible handover termination response sent by the RNC, and forwards the handover handover termination response to the HNB according to the signaling connection mapping between the HNB and the RNC. Next, the HNB-GW eliminates the signaling connection mapping between the HNB and the RNC and the user plane connection mapping between the HNB and the RNC, and releases the forwarding information from the user plane and the forwarding information. of connection resources. The RNC and the HNB also release resources.

Figure 4A is a flow chart of a flexible handover method performed by an HNB and an RNC when a link between the RNC and an HNB-GW is IP over Ethernet according to an embodiment of the present invention. As depicted in Figure 4A, the method according to the embodiment includes the following steps:

Step 1a: Configure, for an RNC in an HNB-GW, a destination signaling point of signal connection control part (signal connection control part, SCCP), to establish a signaling connection with the RNC.

Stage 1b: An HNB sends a registration request to the HNB-GW, to register it with the HNB-GW.

The registration request according to the embodiment includes: an HNB name (which is an HNB id known in the art). After the HNB registers with the HNB-Gw, the HNB-GW obtains the HNB id of the registration request, and uses the HNB id as an identifier of the HNB. Alternatively, after the hNb is registered with the HNB-GW, the HNB-GW assigns a SCTP coupling number to the HNB, and uses the assigned SCTP coupling number to unequivocally identify the HNB.

Stage 1c: When an EU moves from the HNB cell coverage to the cell coverage of a NodeB under the RNC, the HNB determines that it is necessary to initiate a flexible transfer to the RNC.

Stage 1d: The HNB sends a flexible transfer request (such as RL) to the HNB-GW.

The flexible handover request carries an IP address of the user's plane and a UDP port number of the HNB, which is registered as <ip1, port1>, and an RNC id.

Stage 1e: When the request for flexible handover is received, the HNB-GW registers a mapping between a SCTP coupling number (or the HNB id) and the RNC id id, that is, a signaling connection mapping between the RNC and the HNB, and simultaneously records the IP address of the user plane and the UDP port number <ip1, port1> of the HNB.

Stage 1f: The HNB-GW assigns a local IP and UDP ports <ip2, port2> and <ip3, port3>, which are to be used to establish user plane connections with the HNB and RNC respectively, replace <ip1, port1> in the flexible transfer request with <ip3, port3>, eliminates the RNC id of the flexible transfer request, and forwards the flexible transfer request to the RNC.

Step 1g: After receiving the flexible handover request sent by the HNB-GW, the RNC assigns an IP address of the user's plane and a UDP port <ip4, port4> to prepare for the flexible handover, and returns a

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

Flexible handover response (such as an RL configure resp) to the HNB-GW, where the flexible handover response carries <ip4, port4>.

Stage 1h: After receiving the flexible handover response, the HNB-GW records mappings between <ip1, port1>, <ip2, port2>, <ip3, port3>, and <ip4, port4>, that is, connection mapping of the user plane between the RNC, the HNB-GW, and the HNB, replaces the user plane information <ip4, port4> of the RNC in the flexible handover response with <ip2, port2>, and resends the handover response flexible to the HNB.

<ip1, port1> corresponds to <ip2, port2>, <ip2, port2> corresponds to <ip3, port3>, <ip3, port3> corresponds to <ip4, port4>, and <ip1, port1> can be correspond with <ip4, port4> to <ip2, port2> and <ip3, port3>.

Stage 1i: The HNB continues to send signals subsequent to the HNB-GW.

The HNB can send a post-HNB-GW signal through a SCTP connection to the HNB-GW.

Step 1j: The HNB-GW resends the post-RNC signaling according to the signaling connection mapping between the RNC and the HNB, to ensure the resending of signaling messages between the HNB and the RNC.

The HNB-GW identifies the RNC according to the signaling connection mapping between the RNC and the HNB, and forwards to the RNC, through an SCCP connection with the RNC, the subsequent signaling sent by the HNB.

Subsequent signaling includes downlink synchronization (DL sync) and uplink synchronization (UL sync).

Stage 1k: When downlink data is forwarded to the RNC, the HNB uses <ip1, port1> and <ip2, port2> carried in the previous flexible handover response to encapsulate the downlink data, and send the downlink data to the HNB-GW.

The downlink data has a source IP address that is ip1, a source port number that is port, a destination IP address that is ip2, and a destination port number that is port2.

Stage 1l: After receiving the downlink data, the HNB-GW replaces <ip1, port1> and <ip2, port2> in the downlink data received with <ip3, port3> and <ip4, port4> respectively according to user plane connection mapping between the RNC, the HNB-GW, and the HNB, and sends the downlink data to the RNC.

Specifically, the <ip3, port3> that corresponds to <ip1, port1> can be found according to the mappings between <ip1, port1> and <ip2, port2>, and between <ip2, port2> and <ip3, port3>; the <ip4, port4> that corresponds to <ip2, port2> can be found according to the mappings between <ip2, port2> and <ip3, port3>, and between <ip3, port3> and <ip4, port4>; Downlink data is re-encapsulated by using <ip3, port3> and <ip4, port4> found before being sent to the RNC.

After replacement (or re-encapsulation), the source IP address of the downlink data changes to ip3, the source port number changes to port3, the destination IP address changes to ip4, and the destination port number changes to port 4.

Stage 1m: When uplink data is forwarded to the HNB, the RNC uses <ip4, port4> and <ip3, port3> that are carried on the request for prior flexible transfer to encapsulate the uplink data, and send the uplink data uplink to the hNB-GW.

The uplink data has a source IP address that is ip4, a source port number that is port4, a destination IP address that is ip3, and a destination port number that is port3.

Stage 1n: After receiving the uplink data, the HNB-GW replaces <ip4, port4> and <ip3, port3> in the uplink data received with <ip2, port2> and <ip1, port1> respectively according to user plane connection mapping between the RNC, the HNB-GW, and the HNB, and sends the uplink data to the HNB.

Specifically, the <ip1, port1> that corresponds to <ip3, port3> can be found according to the mappings between <ip1, port1> and <ip2, port2>, and between <ip2, port2> and <ip3, port3>; the <ip2, port2> that corresponds to <ip4, port4> can be found according to the mappings between <ip2, port2> and <ip3, port3>, and between <ip3, port3> and <ip4, port4>; The uplink data is re-encapsulated by using the <ip1, port1> and <ip2, port2> found before being sent to the HNB.

After replacement (or re-encapsulation), the source IP address of the uplink data changes to ip2, the source port number changes to port2, the destination IP address changes to ip1, and the destination port number changes to puertol.

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

The HNB-GW ensures that the user plane data is forwarded between the RNC and the HNB.

Stage 1: After the service ends, the HNB sends a flexible transfer termination request (such as pet RL removal) to the HNB-GW.

Stage 1p: The HNB-GW forwards the request for completion of flexible handover to the RNC according to the signaling connection mapping between the RNC and the HNB.

Stage 1q: After receiving the flexible handover termination request, the RNC releases local resources, and returns a flexible handover termination response (such as eliminating RL) to the HNB-GW.

Stage 1: The HNB-GW forwards the flexible handover termination response to the HNB according to the signaling connection mapping between the RNC and the HNB; After forwarding the flexible handover termination response to the HNB, it eliminates the local signaling connection mapping between the RNC and the HNB and the user plane connection mapping between the RNC, the HNB-GW, and the HNB, and free local user plane resources.

Stage 1s: The HNB receives the completion response of the flexible handover, and releases resources from the local user's plane, and the flexible handover process ends.

In the embodiment, the HNB-GW establishes a signaling connection with the RNC, so that the HNB only needs to establish a logical connection with the RNC, and exchanges user plane data and signaling with the RNC through the HNB- GW, thus implementing the flexible transfer between a macrocell and an HNB cell.

Figure 4B is a flow chart of a flexible handover method carried out by an HNB and an RNC when a link between the RNC and an HNB-GW is ATM according to an embodiment of the present invention. As depicted in Figure 4B, the method according to the embodiment includes the following steps:

Step 2a: Configure, in an HNB-GW, an SCCP destination signaling point towards an RNC, in order to establish a signaling connection with the RNC.

Stage 2b: An HNB sends a registration request to the HNB-GW, to register it with the HNB-GW.

After the HNB registers with the HNB-GW, the HNB-GW uniquely identifies the HNB through a SCTP coupling number or an HNB id.

Stage 2c: When an EU moves from the HNB cell coverage to the cell coverage of a NodeB under the RNC, the HNB determines that it is necessary to initiate a flexible transfer to the RNC.

Stage 2d: The HNB sends a flexible transfer request (such as RL) to the HNB-GW.

The flexible handover request carries an IP address of the user plane and a UDP port number of the HNB, which are registered as <ip1, port1>, and an RNC id.

Stage 2e: When the request for flexible handover is received, the HNB-GW registers a mapping between a SCTP coupling number (or the HNB id) and the RNC id, that is, a signaling connection mapping between the RNC and the HNB, and simultaneously records the IP address of the user plane and the UDP port number <ip1, port1> of the HNB.

Stage 2f: The HNB-GW determines that the type of a lur interface is ATM, identifies that an AAL2 link with the RNC needs to be established; therefore, it allocates a local AAL2 resource <VPI1, VCI1, CID1>, and sends an establishment request (pet est) to the RNC.

Stage 2g: After receiving the establishment request sent by the HNB-GW, the RNC assigns a local AaL2 resource <vPl2, VCI2, CID2>, and returns an establishment confirmation (conf est) to the HNB-GW, where the Confirmation of establishment takes <VPI2, VCI2, CID2>.

Stage 2h: After receiving the confirmation of establishment, the HNB-GW records mappings between <VPI1, VCI1, CID1>, <VPI2, VCI2, CID2>, <ip1, port1> and <ip2, port2>, that is, mappings of connection of the user plane between the RNC, the HNB-GW, and the HNB, assigns a local IP address and a UDP port <ip2, port2> to the HNB, in order to establish a connection of the user plane with the HNB , then replaces the user plane information <ip1, port1> of the HNB in the flexible transfer request with <VPI1, vCl1, CID1>, eliminates the RNC id in the flexible transfer request, and then resends the flexible transfer request to the RNC.

<VPI1, VCI1, CID1> corresponds to <VPI2, VCI2, CID2>, <ip1, port1> corresponds to <ip2, port2>, <VPI1, VCI1, CID1> corresponds to <ip2, port2>, and < VPl2, VCI2, CID2> can correspond to <ip1, port1> through the mapping between <VPI1, vCl1, CID1> and <ip2, port2>.

Stage 2i: After receiving the flexible handover request sent by the HNB-GW, the RNC prepares for the handover handover, and returns a flexible handover response (as set up RL) to the HNB-GW.

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

Step 2j: After receiving the flexible handover response, the HNB-GW replaces the user plane information <VPI1, VCI1, CID1> of the RNC in the flexible handover response with <ip2, port2>, and forwards the response of Flexible transfer to the HNB.

Stage 2k: The HNB continues to send signals subsequent to the HNB-GW.

The HNB can send a post-HNB-GW signal through a SCTP connection to the HNB-GW.

Stage 2l: The HNB-GW resends the post-RNC signaling according to the signaling connection mapping between the RNC and the HNB, to ensure the resending of signaling messages between the HNB and the RNC.

The HNB-GW identifies the RNC according to the signaling connection mapping between the RNC and the HNB, and forwards to the RNC, through an SCCP connection with the RNC, the subsequent signaling sent by the HNB.

Subsequent signaling includes downlink synchronization (DL sync) and uplink synchronization (UL sync).

Stage 2m: When the downlink data is forwarded to the RNC, the HNB uses <ip1, port1> and <ip2, port2> that is carried in the previous flexible handover response to encapsulate the downlink data, and sends the data downlink to the HNB-GW.

The downlink data has a source IP address that is ip1, a source port number that is port, a destination IP address that is ip2, and a destination port number that is port2.

Stage 2n: After receiving the downlink data, the HNB-GW replaces <ip1, port1> and <ip2, port2> in the downlink data received with <VPI1, VCI1, ClDl> and <VPI2, VCI2, CID2 > respectively according to the user plane connection mappings between the RNC, the HNB-GW, and the HNB, and sends the downlink data to the RNC.

Specifically, the <VPI1, VCI1, CID1> that corresponds to <ip1, port1> is found according to the mapping between <ip1, port1> and <ip2, port2>, and between <VPI1, VCI1, CID1> and <ip2, port2>; The <VPI2, VCI2, CID2> corresponding to <ip2, port2> is found according to the mapping between <VPI1, VCI1, CID1> and <VPI2, VCI2, ClD2>, and between <VPI1, VCI1, CID1> and < ip2, port2>; Downlink data is re-encapsulated by using the <VPI1, VCI1, CID1> and <VPI2, VCI2, CID2> found before being sent to the RNC. Stage 2: When uplink data is forwarded to the HNB, the RNC uses <VPI2 + VCI2 + CID2> and <VPI1, VCI1, CID1> that is carried in the request for prior flexible handover to encapsulate the uplink data, and send the uplink data to the HNB-GW.

Step 2p: After receiving the uplink data, the HNB-GW replaces <VPI2, VCI2, CID2> and <VPI1, VCI1, CID1> in the uplink data received with <ip2, port2> and <ip1, port1 > respectively according to the user plane connection mappings between the RNC, the HNB-GW, and the HNB, and sends the uplink data to the RNC.

Specifically, the <ip1, port1> that corresponds to <VPI1, VCI1, CID1> is found according to the mapping between <ip1, port1> and <ip2, port2>, and between <VPI1, VCI1, CID1> and <ip2, port2>; The <ip2, port2> that corresponds to <VPI2, VCI2, CID2> is found according to the mapping between <VPI1, VCI1, CID1> and <VPI2, VCI2, CID2>, and between <VPI1, VCI1, CID1> and < ip2, port2>; Downlink data is re-encapsulated by using the <ip1, port1> and <ip2, port2> found before being sent to the RNC.

After replacement (or re-encapsulation), the source IP address of the uplink data changes to ip2, the source port number changes to port2, the destination IP address changes to ip1, and the destination port number changes to puertol.

The HNB-GW guarantees the forwarding of the user plane data between the RNC and the HNB.

Stage 2q: After the service is stopped, the HNB sends a flexible transfer termination request (such as pet elimination rL) to the HNB-GW.

Stage 2r: The HNB-GW forwards the request for completion of flexible handover to the RNC according to the signaling connection mapping between the RNC and the HNB.

Stage 2s: After receiving the flexible transfer termination request, the RNC releases local resources, and returns a flexible transfer termination response (such as eliminating RL) to the HNB-GW.

Stage 2t: The HNB-GW forwards the flexible handover termination response to the HNB according to the signaling connection mapping between the RNC and the HNB; After forwarding the flexible handover termination response to the HNB, it eliminates the local signaling connection mapping between the RNC and the HNB and the user plane connection mapping between the RNC, the HNB-GW, and the HNB, and free local user plane resources.

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

Stage 2u: The HNB receives the completion response of the flexible handover, and releases resources from the local user's plane, and the flexible handover process ends.

Compared to the embodiment shown in Figure 4A, the difference in the embodiment lies in that, the link between the RNC and the HnB-GW is ATM, and the carrier of the lur interface between the HNB-GW and the RNC is ATM, and according to the protocol, it is necessary to allocate the AAL2 resource; therefore, during the flexible handover process, a process of establishing and releasing the AAL2 link is added.

In the embodiment, the HNB-GW establishes a signaling connection with the RNC, so that the HNB only needs to establish a logical connection with the RNC, and exchange user plane data and signaling with the RNC through the HNB- GW, thus implementing the flexible transfer between a macrocell and an HNB cell.

Figure 5A is a flow chart of a flexible handover method carried out by an HNB and an RNC according to another embodiment of the present invention. As shown in Figure 5A, the method according to the embodiment includes the following steps:

Step 501: An HNB-GW receives a flexible transfer request sent by an RNC, where the flexible transfer request includes information on RNC connection resources and an identifier of an HNB.

In the embodiment, the RNC implements a complete RNSAP protocol stack, supports lur interfaces, and carries out necessary resource processing and signaling, such as the start of measurements and management of radioelectric resources.

The RNC makes a flexible handover decision based on information, such as measured signal power, and initiates a flexible handover request to the HNB through the HNB-GW when a flexible handover requirement is met. Therefore, when the flexible transfer requirement is met, the RNC sends a flexible transfer request to the HNB-GW, where the flexible transfer request carries information of RNC connection resources and an identifier of the transfer destination HNB .

The information of connection resources of the RNC varies according to the different means of connection between the HNB-GW and the RNC. For example, if the link between the HNB-GW and the RNC is IP over Ethernet, the RNC connection resource information mainly includes an IP address of the user plane and a UDP port number. If the link between the HNB-GW and the RNC is ATM, the RNC connection resource information mainly includes a channel identifier, such as a VPI, a VCI, and a CID, which is needed to establish an AAL2 link.

The HNB identifier can be an HNB name (i.e., HNB id) or HNB randomization code information, or other information that is predetermined by the HNB and RNC and can be used by the RNC to uniquely identify The HNB The HNB identifier can be obtained from a signal measured by the RNC. For example, when the HNB identifier is the randomization code information of the HNB or the HNB id, the RNC can obtain, from a measured handover message, the randomization code information of the HNB or the HNB id. For a single RNC, the randomization code information of the HNB or of the HNB id can uniquely identify an HNB.

Step 502: The HNB-GW establishes, according to the HNB identifier, a signaling connection mapping between the RNC and the HNB, and forwards the flexible handover request to the HNB based on the forwarding information of the user plane assigned to the HNB

In the embodiment, the HNB-GW establishes a signaling connection with the RNC by configuring a physical lur interface.

After receiving the flexible transfer request sent by the RNC, the HNB-GW obtains, from the flexible transfer request, the HNB identifier and the RNC connection resource information, records the RNC connection resource information, and simultaneously identifies and addresses the HNB according to the HNB identifier.

In the HNB-GW, HNB identifiers are stored in advance, and the HNB-GW can unequivocally locate an HNB and relevant information (such as an HNB id or SCTP coupling number) of the HNB according to the HNB identifier. Generally, during communication, the HNB-GW identifies an HNB according to the HNB id or SCTP coupling numbers stored, while the HNB id or SCTP coupling numbers are generally determined by the HNB-GW according to the registration requests sent by the HNB. The HNB-GW identifies, according to the HNB identifier, that the RNC needs assistance to perform the flexible handover, thus establishing a signaling connection mapping between the HNB and the RNC. When a signaling connection is established with the RNC, the HNB-GW stores an SCCP signaling point related to the RNC, where the SCCP signaling point can uniquely identify the RNC; therefore, the HNB-GW can link the HNB identifier with the SCCP signaling point corresponding to the RNC, to establish the signaling connection mapping between the HNB and RNC.

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

The HNB-GW also assigns the user plane forwarding information to the HNB, which is used to establish a connection with the HNB during the flexible handover process. The user plane forwarding information includes information that points to the hNB-GW, and mainly includes an IP address of the user plane and a UDP port number that are assigned by the HNB-GW to the HNB. Next, the HNB-GW replaces the RNC connection resource information in the flexible transfer request with the user plane forwarding information, and resends the flexible transfer request to the HNB.

Step 503: The HNB-GW receives a flexible handover response returned by the HNB according to the flexible handover request, where the handover handover response includes information of the HNB user plane.

After the HNB-GW forwards the flexible handover request to the HNB, the HNB performs the allocation of resources to prepare for the flexible handover, and returns a flexible handover response to the HNB-GW, where the handover response flexible takes the user plane information to the hNb. The HNB user plane information mainly includes the IP address of the user plane and the UDP port number.

The HNB-GW receives the flexible handover response sent by the HNB, obtains, from the flexible handover response, the information of the HNB user plane, and records the information of the HNB user plane.

Step 504: The HNB-GW establishes a mapping of the user plane connection between the HNB and the RNC according to the HNB user plane information, the user plane forwarding information, which forwards connection resource information assigned to the RNC, and the RNC connection resources information, and forwards the flexible handover response to the RNC based on the connection resources forwarding information.

In the embodiment, the HNB-GW also assigns, to the RNC, the connection resources forwarding information, which is used to establish a connection with the RNC during the flexible handover process.

The connection resources forwarding information includes information that points to the HNB-GW. The information on the re-envfo of connection resources varies according to the different link between the HNB-GW and the RNC. For example, if the link between the HNB-GW and the RNC is IP over Ethernet, the connection resource forwarding information mainly includes an IP address of the user plane and a UDP port number pointing to the HNB- GW and that are assigned by the HNB-GW to the RNC. If the link between the HNB-GW and the RNC is ATM, the connection resource forwarding information mainly includes a channel identifier, such as a VPI, a VCI, and a CID, which is needed to establish a AAL2 link, assigned by the HNB-GW to the RNC and points to the HNB-GW.

To ensure that the user plane data between the HNB and the RNC can be forwarded to each other, the HNB-GW links the information of the HNB user plane, the user plane forwarding information, the resource forwarding information of connection, and the information of connection resources of the RNC, in order to establish a mapping of the user plane connection between the HNB and the RNC.

Then, the HNB-GW replaces the HNB user plane information in the flexible handover response with the RNC connection resource information, and sends the flexible handover response to the RNC.

At this point, the HNB-GW establishes the signaling connection mapping and the user plane connection mapping between the HNB and the RNC, so that the user plane data and signaling between the HNB and the RNC can be Forward successfully, thus implementing the flexible handover between the HNB and the RNC.

In the embodiment, the HNB-GW implements a RNSAP protocol stack proxy, establishes a signaling connection with the RNC, and offers a physical interface, to allow the HNB to establish a logical connection with the RNC; The exchange of user plane data and signaling between the HNB and the RNC is completed through the HNB-GW, thus implementing the flexible handover process, solving the flexible handover problem when a macrocell is adjacent to an HNB cell, and improving the user experience. In addition, due to the HNB-GW proxy, the rNc can support a large amount of hNb to simultaneously establish logical connection relationships with the RNC; therefore, the flexible transfer between an RNC cell and an HNB cell is neither limited by the amount of RNC Iur connections, nor affected by changes in the location of the HNB. In addition, because the HNB-GW establishes a physical connection with the RNC, the number and location changes of the HNBs have no effect on the cost of maintenance and the signaling load, so that the network operates in a state Low load, easy planning and easy maintenance. Likewise, the HNB-GW only acts as a proxy for the RNSAp protocol stack, and does not need to include the RNSAP protocol stack, so that the HNB-GW does not conflict with the architecture stipulated by the protocol, which collaborates with the evolution towards the protocol and results in a lower implementation cost.

The above embodiment describes the process of a flexible handover method according to the present invention from the perspective of the HNB-GW; The following embodiment describes the flexible handover method according to the present invention from the perspective of the RNC.

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

Figure 5B is a flow chart of a flexible handover method carried out by an HNB and an RNC according to another embodiment of the present invention. As shown in Figure 5B, the method according to the embodiment includes the following steps:

Step 601: An RNC sends a flexible transfer request to an HNB-GW, to allow the HNB-GW to establish a signaling connection mapping between an HNB and the RNC according to the flexible transfer request, where the flexible transfer request includes information on RNC connection resources and an HNB identifier.

In the embodiment, the RNC makes a flexible handover decision according to information, such as measured signal power, and initiates a flexible handover request to the HNB through the HNB-GW when a handover requirement is met, where the request Flexible handover carries information on RNC connection resources and an identifier of the handover destination HNB.

For information on connection resources of the RNC and the HNB identifier, reference can be made to step 501.

For the process of establishing, by the HNB-GW, a signaling connection map between the HNB and the RNC according to the flexible transfer request, reference can be made to step 502, which is not described again in detail In the present memory.

Step 602: The RNC receives a flexible handover response sent by the HNB-GW, where the flexible handover response is returned by the HNB to the HNB-GW according to the flexible handover request forwarded by the HNB-GW, and is forwarded to the RNC after the HNB-GW establishes a mapping of the user plane connection between the HNB and the RNC according to a flexible handover response, and the handover handover response includes information on connection resources forwarded to the RNC by the HNB-GW.

For processes in which the HNB-GW forwards a flexible handover request to the HNB, the HNB returns a flexible handover response to the HNB-GW, and the HNB-Gw establishes a user plane connection mapping between the HNB and the RNC according to the flexible handover response, and forwards the flexible handover response to the RNC, reference may be made to step 502 through step 504, which is not described again in detail herein.

The RNC receives the flexible handover response forwarded by the HNB-GW. At this point, the HNB-GW establishes the signaling connection mapping and the user plane connection mapping between the HNB and the RNC, so that the user plane data and signaling between the HNB and the RNC can be Forward successfully, thus implementing the flexible transfer between the HNB and the RNC.

Likewise, the flexible handover method described from the perspective of the HNB includes the following stages: the HNB receives the flexible handover request forwarded, by the HNB-GW, according to the user plane forwarding information assigned to the HNB, when the request Flexible handover includes the HNB identifier, the flexible handover request is sent from the RNC to the HNB-GW, and forwarded after the HNB-GW establishes the signaling connection mapping between the RNC and the HNB according to the request Flexible handover Next, the HNB sends the flexible handover response to the HNB-GW according to the flexible handover request, where the handover handover response includes the information of the HNB user plane, to allow the HNB-GW to establish the connection mapping of the user plane between the HNB and the RNC according to the flexible handover response, and forward the flexible handover response to the RNC.

For detailed descriptions of the above operations, reference may be made to step 501 through step 504, which is not described again in detail herein.

In the flexible handover method according to the embodiment, the HNB-GW implements an RNSAP protocol stack proxy, establishes a signaling connection with the RNC, and offers a physical luric interface, to allow the HNB to establish a logical connection with the RNC; The exchange of user plane data and signaling between the HNB and the RNC is completed through the HNB-GW, thus implementing the flexible handover process, solving the flexible handover problem when a macrocell is adjacent to an HNB cell, and improving the user experience. In addition, due to the HNB-GW proxy, the RNC can support a large amount of HNB to simultaneously establish logical connection relationships with the RNC; therefore, the flexible handover between an HNB cell and an RNC cell is neither limited by the amount of RNC lur connections, nor affected by changes in the location of the HNB. In addition, because the HNB-GW establishes a physical connection with the RNC, the number and location changes of the HNBs have no effect on the cost of maintenance and the signaling load, so that the network operates in a state Low load, easy planning and easy maintenance. Likewise, the HNB-GW only acts as a proxy for the RNSAP protocol stack, and does not need to include the RNSAP protocol stack, so that the HNB-GW does not conflict with the architecture stipulated by the protocol, which collaborates with the evolution towards the protocol.

In each of the above embodiments, before the RNC sends a flexible handover request to the HNB-GW, the HNB-GW establishes a signaling connection with the RNC when configuring a physical luric interface. Also,

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

before the RNC submits a flexible transfer request to the HNB-GW, the HNB sends a registration request to the HNB-GW, to register with the HNB-GW. The HNB-GW determines and saves the HNB identifier according to the record received from the HNB. For example, when the HNB identifier is an HNB id or HNB randomization code information, the HNB encapsulates the HNB id or the HNB randomization code information on a registration request and sends the registration request to the HNB -GW; the HNB-GW obtains the HNB id or the HNB randomization code information from the registration request, and uses the HNB id or the HNB randomization code information as the HNB identifier. In addition, after receiving the registration request, the HNB_GW also assigns a SCTP coupling number to the HNB.

In each of the above embodiments, after the RNC receives a flexible handover response forwarded by the HNB-GW, the method also includes one or more of the following operations:

The RNC can send a signaling message to the HNB-GW through a SCTP connection with the HNB-GW; The HNB-GW identifies the RNC according to the signaling connection map between the HNB and the RNC, and forwards the signaling message to the HNB through the SCCP connection to the RNC.

The RNC sends downlink data to the HNB-GW according to the connection resource forwarding information; The HNB-GW identifies the HNB according to the user plane connection mapping between the HNB and the RNC, and forwards the downlink data to the HNB based on the user plane forwarding information that points to the HNB-GW and assigned to the HNB.

The HNB sends uplink data to the HNB-GW according to the user plane forwarding information; The HNB-GW identifies the RNC according to the user plane connection mapping between the HNB and the RNC, and forwards the uplink data to the RNC based on the connection resource forwarding information that points to the HNB-GW and assigned to the RNC; The RNC receives the uplink data sent by the HNB and forwarded by the HNB-GW.

Also, after the end of the service, the RNC sends a request for completion of flexible transfer to the HNB-GW; the HNB-GW forwards the flexible handover termination request to the HNB according to the signaling connection mapping between the HNB and the rNc, receives a flexible handover termination response sent by the NB, and forwards the handover handover termination response to the RNC according to the signaling connection mapping between the HNB and the RNC. After forwarding the flexible handover termination response, the HNB-GW eliminates the signaling connection mapping between the HNB and the RNC and the user plane connection mapping between the HNB and the RNC, and releases the forwarding information of the plane of the user and the information of redirection of connection resources. The RNC and the HNB also release local resources.

Figure 6 is a flow chart of a flexible handover method carried out by an HNB and an RNC when a link between the RNC and the HNB-GW is IP over Ethernet according to another embodiment of the present invention. As shown in Figure 6, the method according to the embodiment includes the following steps:

Step 3a: Configure, in an HNB-GW, an SCCP destination signaling point towards an RNC, in order to establish a signaling connection with the RNC.

Stage 3b: An HNB sends a registration request to the HNB-GW to register with the HNB-GW, where the registration request carries an HNB identifier.

If the HNB identifiers carried in the registration requests are HNB randomization code information, the HNB-GW records the randomization code information of each HNB. If the HNB identifiers carried in the registration requests are HNB id, the HNB-GW records the HNB id of each HNB. In the embodiment, the HNB identifier is registered as id C.

Step 3c: After the HNB registers with the HNB-GW, the HNB-GW uniquely identifies the HNB through a SCTP coupling number or an HNB id.

After the HNB registers with the HNB-GW, the HNB-GW uniquely identifies the HNB by using the HNB id or the SCTP coupling number assigned to the HNB. In other words, for the HNB-GW, the SCTP coupling number can also uniquely identify the HNB.

Based on the above description, the HNB-GW can also establish a mapping between the HNB identifier (such as HNB randomization code information or the HNB id) and the SCTP coupling number, and use the coupling number SCTP assigned to the HNB to uniquely identify the HNB; that is, id C can also represent the SCTP coupling number.

Stage 3d: When an EU moves from the cell coverage of a NodeB to the cell coverage of the HNB, the RNC determines that it is necessary to initiate a flexible handover to the HNB.

Stage 3e: The RNC sends a flexible transfer request (such as RL) to the HNB-GW.

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

The flexible handover request carries an IP address from the user plane and a RNC UDP port number, <ip1, port1>, and id C.

Step 3f: When the request for flexible handover is received, the HNB-GW finds the corresponding HNB according to id C, records a mapping between the SCCP signaling point and the HNB, that is, a signaling connection mapping between the RNC and the HNB, and simultaneously records the IP address of the user plane and the UDP port number <ip1, port1> of the RNC.

Step 3g: The HNB-GW assigns a local IP address and UDP ports <ip2, port2> and <ip3, port3>, which are to be used to establish a connection of the user plane with the RNC and HNB respectively, replace < ip1, port1> in the flexible transfer request with <ip3, port3>, and forward the flexible transfer request to the HNB.

Stage 3h: After receiving the flexible handover request sent by the HNB-GW, the HNB assigns an IP address of the user's plane and a UDP port <ip4, port4> to prepare for the flexible handover, and returns a handover response flexible (as an resp configure RL) to the hNB-GW, where the flexible handover response carries <ip4, port4>.

Stage 3i: After receiving the flexible handover response, the HNB-GW records mappings between <ip1, port1>, <ip2, port2>, <ip3, port3>, and <ip4, port4>, that is, connection mapping of the user plane between the RNC, the HNB-GW, and the HNB, replaces the user plane information <ip4, port4> of the HNB in the flexible handover response with <ip2, port2>, and resends the handover response flexible to the RNC.

<ip1, port1> corresponds to <ip2, port2>, <ip2, port2> corresponds to <ip3, port3>, <ip3, port3> corresponds to <ip4, port4>, and <ip1, port1> can be correspond to <ip4, port4> up to <ip2, port2> and <ip3, port3>.

Stage 3j: The RNC continues to send signals subsequent to the HNB-GW.

The RNC sends a post-HNB-GW signaling through a SCTP connection to the HNB-GW.

Step 3k: The HNB-GW resends the post-HNB signaling according to the signaling connection mapping between the RNC and the HNB, to ensure the resending of signaling messages between the RNC and the HNB.

The HNB-GW identifies the RNC according to the signaling connection mapping between the RNC and the HNB, and forwards, through an SCCP connection with the RNC, to the RNC the subsequent signaling sent by the HNB.

Subsequent signaling includes downlink synchronization (DL sync) and uplink synchronization (UL sync).

Step 3l: When the downlink data is forwarded to the HNB, the RNC uses <ip1, port1> and <ip2, port2> that is carried in the previous flexible handover response to encapsulate the downlink data, and sends the data downlink to the HNB-GW.

The downlink data has a source IP address that is ip1, a source port number that is port, a destination IP address that is ip2, and a destination port number that is port2.

Stage 3m: After receiving the downlink data, the HNB-GW replaces <ip1, port1> and <ip2, port2> in the downlink data with <ip3, port3> e <ip4, port4> respectively according to the mapping of connecting the user plane between the RNC, the HNB-GW, and the HNB, and sends the downlink data to the HNB.

Specifically, the <ip3, port3> that corresponds to <ip1, port1> can be found according to the mappings between <ip1, port1> and <ip2, port2>, and between <ip2, port2> and <ip3, port3>; the <ip4, port4> that corresponds to <ip2, port2> can be found according to the mappings between <ip2, port2> and <ip3, port3>, and between <ip3, port3> and <ip4, port4>; Downlink data is re-encapsulated by using <ip3, port3> and <ip4, port4> found before being sent to the RNC.

After replacement (or re-encapsulation), the source IP address of the downlink data changes to ip3, the source port number changes to port3, the destination IP address changes to ip4, and the destination port number changes to port 4.

Step 3n: When uplink data is forwarded to the RNC, the HNB uses <ip4, port4> and <ip3, port3> that is carried on the request for prior flexible handover to encapsulate the uplink data, and sends the data from uplink uplink to the HNB-GW.

The uplink data has a source IP address that is ip4, a source port number that is port4, a destination IP address that is ip3, and a destination port number that is port3.

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

Stage 3: After receiving the uplink data, the HNB-GW replaces <ip4, port4> and <ip3, port3> in the uplink data received with <ip2, port2> and <ip1, port1> respectively according to user plane connection mapping between the RNC, the HNB-GW, and the HNB, and sends the uplink data to the RNC.

Specifically, the <ip1, port1> that corresponds to <ip3, port3> can be found according to the mappings between <ip1, port1> and <ip2, port2>, and between <ip2, port2> and <ip3, port3>; the <ip2, port2> that corresponds to <ip4, port4> can be found according to the mappings between <ip2, port2> and <ip3, port3>, and between <ip3, port3> and <ip4, port4>; The uplink data is re-encapsulated by using the <ip1, port1> and <ip2, port2> found before being sent to the HNB.

After replacement (or re-encapsulation), the source IP address of the uplink data changes to ip2, the source port number changes to port2, the destination IP address changes to ip1, and the destination port number changes to puertol.

The HNB-GW guarantees the forwarding of the user plane data between the RNC and the HNB.

Stage 3p: After the end of the service, the RNC sends a request for completion of flexible transfer (such as pet removal RL) to the HNB-GW.

Step 3q: The HNB-GW forwards the flexible handover termination request to the HNB according to the signaling connection mapping between the RNC and the HNB.

Stage 3: After receiving the flexible handover termination request, the HNB releases local resources, and returns a flexible handover termination response (such as eliminating RL) to the HNB-GW.

Step 3s: The HNB-GW forwards the flexible handover termination response to the RNC according to the signaling connection mapping between the RNC and the HNB, and after re-sending the flexible handover termination response to the RNC, eliminates the connection mapping mapping of local signaling between the RNC and the HNB and the user plane connection mappings between the RNC, the HNB-GW, and the HNB, and free resources from the local user plane.

Stage 3t: The RNC receives the flexible handover completion response, and releases local user plan resources, and the flexible handover process ends.

In the embodiment, the HNB-GW establishes a signaling connection with the RNC, so that the HNB only needs to establish a logical connection with the RNC, and the exchange of user plane data and signaling with the RNC is completed through of the HNB-GW, thus implementing the flexible handover between a macrocell (ie, an RNC cell) and an HNB cell.

In addition, the flexible handover process between the HNB and the RNC when the link between the RNC and the HNB-GW is ATM is similar to the previous process; the difference lies in the fact that the link between the RNC and the HNB-GW is ATM, and the carrier of the lur interface between the HNB-GW and the RNC is ATM, which requires the allocation of AAL2 resources according to the protocol; therefore, during the flexible handover process, a process of establishing and releasing an AAL2 link is added, which, therefore, is not described in detail again herein.

It should be noted that, in the following embodiments, relatively simple scenarios in flexible handover are used as examples for the sake of illustration. If the flexible handover process between the RNC and the HNB involves other processes, such as a radio link addition message (RL addition), a radio link elimination message (RL removal), and that the RNC and the HNB they are subjected to a flexible transfer to the outside and then they are subjected to a flexible transfer to the interior, an implementation can always be carried out through a method similar to that of the previous embodiments, which is not described in detail again herein. . To control an abnormal situation that occurs during the flexible handover process between the RNC and the HNB, reference can be made to the forms of control adopted when an abnormal situation occurs during the flexible handover process between two macro cells or between two RNCs.

Figure 7A is a schematic network topological diagram of a macrocell adjacent to a HeNB cell according to an embodiment of the present invention. As shown in Figure 7A, a network topology according to the embodiment includes: a main network (main network, CN) / mobility management entity (mobility management entity, MME) 71, an RNC 72, a HeNB-GW 73, a NodeB 74, and a HeNB 75. The CN / MME 71 connects to RNC 72 and HeNB-GW 73 separately, RNC 72 is connected to NodeB 74, and HeNB-GW 73 is connected to HeNB 75. In the embodiment, HeNB 75 is connected to MME 71 through HeNB-GW 73, which is not limited herein. In real applications, HeNB-GW 73 may not physically exist, and MME 71 implements functions of HeNB-GW 73. That is, in the embodiment, an example is taken that HeNB-GW 73 exists physically; If HeNB-GW 73 does not physically exist, MME 71 implements the functions of HeNB-GW 73 described in each embodiment of the present invention.

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

The MME 71 is a control domain node in a 4G network, and the CN 71 is a control domain node in a 2 / 3G network. Assuming that in the embodiment the MME 71 and the CN 71 are integrated into a single network element, which can be physically divided into two network elements and that does not affect each embodiment of the present invention.

The flexible handover method according to a previous embodiment of the present invention that is described from the perspective of the housing access gateway and the housing access node, and the flexible handover method according to another embodiment prior to the present invention. which is described from the perspective of the access gateway to housing, the access node to housing, and the rNc also applies to the HeNB and the RNC. In the network structure shown in Figure 7A, the HeNB-GW is the gateway for access to housing, and the HeNB is the node for access to housing. The detailed flexible handover process is not described again in detail herein.

The flexible handover process between the HeNB and the RNC is described below in detail in the following embodiment of the present invention by taking as an example that the link between the RNC and the HeNB-GW is IP over Ethernet, and the HeNB sends a request for flexible transfer to the RNC.

Figure 7B is a flow chart of a flexible handover method performed by a HeNB and an RNC when a link between a RNC and a HeNB-GW is IP over Ethernet according to an embodiment of the present invention. As shown in Figure 7B, the method according to the embodiment includes the following steps:

Step 4a: Configure, in a HeNB-GW, an SCCP destination signaling point towards an RNC, in order to establish a signaling connection with the RNC.

Stage 4b: A HeNB sends a registration request to the HeNB-GW, to register it with the HeNB-GW.

The registration request in the embodiment includes: a HeNB name (which is a HeNB id known in the art). After the HeNB is registered with the HeNB-GW, the HeNB-GW obtains the HeNB id of the registration request, and uses the HeNB id as an identifier of the HNB. Alternatively, after the HeNB is registered with the HeNB-GW, the HeNB-GW assigns a SCTP coupling number to the HeNB, and uses the assigned SCTP coupling number to uniquely identify the HeNB.

Step 4c: When a EU moves from the cell coverage of the HeNB to the cell coverage of a NodeB under the RNC, the HeNB determines that it is necessary to initiate a flexible transfer to the RNC.

Stage 4d: The HeNB sends a request for flexible transfer (such as pet RL) to the HeNB-GW.

The transfer request carries an IP address of the user's plane and UDP port number of the HeNB, which are registered as <ip1, port1>, and an RNC id. In addition, the flexible transfer request may also have a global eNB name (global eNB id), where the global eNB id can also uniquely identify the HeNB.

Step 4e: When the request for flexible handover is received, the HeNB-GW registers a mapping between a SCTP coupling number (or the global eNB id or the HeNB id) and the RNC id, that is, it establishes a connection mapping of signaling between the RNC and the HNB, and simultaneously records the IP address of the user plane and the UDP port number <ip1, port1> of the HNB.

Step 4f: The HeNB-GW assigns local IP addresses and UDP ports <ip2, port2> and <ip3, port3>, which are used to establish a connection of the user plane with the HeNB and RNC respectively, replace <ip1, port1 > in the flexible transfer request with <ip3, port3>, eliminates the RNC id of the flexible transfer request, and forwards the flexible transfer request to the RNC.

Step 4g: After receiving the flexible handover request sent by the HeNB-GW, the RNC assigns an IP address of the user's plane and a UDP port <ip4, port4> to prepare for the flexible handover, and returns a handover response flexible (as an RL establishment resp) to the HeNB-GW, where the flexible handover response carries <ip4, port4>.

Stage 4h: After receiving the flexible handover response, the HeNB-GW records mappings between <ip1, port1>, <ip2, port2>, <ip3, port3>, and <ip4, port4>, that is, it establishes mapping of connection of the user plane between the RNC, the HeNB-GW, and the HeNB, replaces the user plane information <ip4, port4> of the RNC in the flexible handover response with <ip2, port2>, and resends the response of Flexible transfer to the HeNB.

<ip1, port1> corresponds to <ip2, port2>, <ip2, port2> corresponds to <ip3, port3>, <ip3, port3> corresponds to <ip4, port4>, and <ip1, port1> can be correspond with <ip4, port4> to <ip2, port2> and <ip3, port3>.

Stage 4i: The HeNB continues to send subsequent signals to the HeNB-GW.

The HeNB can send a post-HeNB-GW signal through a SCTP connection to the HeNB-GW.

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

Step 4j: The HeNB-GW resends the post-RNC signaling according to the signaling connection mapping between the RNC and the HeNB, to ensure the resending of signaling messages between the HeNB and the RNC.

The HeNB-GW identifies the RNC according to the signaling connection mapping between the RNC and the HeNB, and forwards, through an SCCP connection with the RNC, to the RNC the subsequent signaling sent by the HeNB.

Subsequent signaling includes downlink synchronization (DL sync) and uplink synchronization (UL sync).

Step 4k: When the downlink data is forwarded to the RNC, the HeNB uses <ip1, port1> and <ip2, port2> that is carried in the previous flexible handover response to encapsulate the downlink data, and sends the data downlink to the HeNB-GW.

The downlink data has a source IP address that is ip1, a source port number that is port, a destination IP address that is ip2, and a destination port number that is port2.

Stage 4l: After receiving the downlink data, the HeNB-GW replaces <ip1, port1> and <ip2, port2> in the downlink data received with <ip3, port3> and <ip4, port4> respectively according to the mapping the user plane connection between the RNC, the HeNB-GW, and the HeNB, and sends the downlink data to the RNC.

Specifically, the <ip3, port3> that corresponds to <ip1, port1> can be found according to the mappings between <ip1, port1> and <ip2, port2>, and between <ip2, port2> and <ip3, port3>; the <ip4, port4> that corresponds to <ip2, port2> can be found according to the mappings between <ip2, port2> and <ip3, port3>, and between <ip3, port3> and <ip4, port4>; Downlink data is re-encapsulated by using the <ip3, port3> and <ip4, port4> found before being sent to the RNC.

After replacement (or re-encapsulation), the source IP address of the downlink data changes to ip3, the source port number changes to port3, the destination IP address changes to ip4, and the destination port number changes to port 4.

Step 4m: When uplink data is forwarded to the HeNB, the RNC uses <ip4, port4> and <ip3, port3> that is carried on the request for prior flexible handover to encapsulate the uplink data, and sends the data uplink to the HeNB-GW.

The uplink data has a source IP address that is ip4, a source port number that is port4, a destination IP address that is ip3, and a destination port number that is port3.

Step 4n: After receiving the uplink data, the HeNB-GW replaces <ip4, port4> and <ip3, port3> in the uplink data received with <ip2, port2> and <ip1, port1> respectively according to user plane connection mappings between the RNC, the HeNB-GW, and the HeNB, and sends the uplink data to the HeNB.

Specifically, the <ip1, port1> that corresponds to <ip3, port3> can be found according to the mappings between <ip1, port1> and <ip2, port2>, and between <ip2, port2> and <ip3, port3>; the <ip2, port2> that corresponds to <ip4, port4> can be found according to the mappings between <ip2, port2> and <ip3, port3>, and between <ip3, port3> and <ip4, port4>; The uplink data is re-encapsulated by using the <ip1, port1> and <ip2, port2> found before being sent to the HeNB.

After replacement (or re-encapsulation), the source IP address of the uplink data changes to ip2, the source port number changes to port2, the destination IP address changes to ip1, and the destination port number changes to puertol.

The HeNB-GW guarantees the forwarding of the user plane data between the RNC and the HeNB.

Stage 4: After the end of the service, the HeNB sends a request for termination of flexible transfer (such as pet elimination RL) to the HeNB-GW.

Step 4p: The HeNB-GW forwards the request for completion of flexible handover to the RNC according to the signaling connection mapping between the RNC and the HeNB.

Step 4q: After receiving the flexible handover termination request, the RNC releases local resources, and returns a flexible handover termination response (such as eliminating RL) to the HNB-GW.

Step 4: The HeNB-GW forwards the flexible handover termination response to the HeNB according to the signaling connection mapping between the RNC and the HeNB, and after resending the flexible handover termination response to the HeNB, eliminates the connection mapping mapping of local signaling between the RNC and the HeNB and the user plane connection mappings between the RNC, the HeNB-GW, and the HeNB, and free resources from the local user plane.

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

Stage 4s: The HeNB receives the completion response of the flexible handover, and releases resources from the local user's plane, and the flexible handover process ends.

In the embodiment, the HeNB-GW establishes a signaling connection with the RNC, so that the HeNB only needs to establish a logical connection with the RNC, and the exchange of user plane data and signaling with the RNC is completed through of the HeNB-GW, thus implementing the flexible transfer between a macrocell and a HeNB cell.

Figure 8A is a schematic structural diagram of a housing access gateway according to an embodiment of the present invention. As shown in Figure 8A, the access gateway to the housing according to the embodiment includes: a first request reception module 82, a first signaling relationship processing module 82, a first response reception module 83 , and a first module of user relationship processing 84.

The first request reception module 81 is connected to a housing access node and is configured to receive a flexible transfer request sent by the housing access node, where the flexible transfer request includes user plane information of the housing access node and an identifier of an RNC. The first signaling relationship processing module 82 is connected to the first request reception module 81 and the RNC, and is configured to establish a signaling connection mapping between the housing access node and the RNC according to the identifier of the RNC in the flexible transfer request received by the first request reception module 81, and forward the flexible transfer request to the RNC based on connection resource forwarding information assigned to the rNc. The information on the re-envfo of connection resources includes information that points to the gateway for access to housing. The first response reception module 83 is connected to the RNC, and is configured to receive a flexible handover response returned by the RNC according to the flexible handover request, where the handover handover response includes information of RNC connection resources. The first user relationship processing module 84 is connected to the first response reception module 83 and the housing access node, and is configured to establish a mapping of the user's plane connection between the housing access node and the RNC according to the information of the user plan of the access node to the dwelling, the information of the forwarding of connection resources, which forwards information of the user plan assigned to the access node of the dwelling, and the information of connection resources of the RNC in the first response reception module 83, and forwards the flexible handover response to the access node to the dwelling based on the user plane forwarding information. The user plan forwarding information includes information that points to the access gateway to the house.

Each functional module of the access gateway to the dwelling according to the embodiment can be configured to execute the processes of the flexible transfer method according to an embodiment of the present invention that is described from the perspective of the access gateway to the dwelling and the method Flexible handover shown in Figure 2, and the detailed operating principles are not described here again. For more details, reference can be made to the description of the method according to the embodiment.

The gateway of access to housing in the realization can be an HNB-GW; therefore, the housing access node is an HNB. The access gateway to housing can also be a HeNB-GW; therefore, the housing access node is a HeNB.

In the embodiment, the access gateway to the dwelling acts as a proxy for the RNSAP protocol stack between the access node to the dwelling and the RNC, offers a physical luric interface, and establishes a signaling connection with the RNC, for allow the housing access node to establish a logical connection with the RNC; The exchange of user plan data and signaling between the housing access node and the RNC is completed through the housing access gateway, thus implementing the flexible transfer process, and solving the flexible transfer problem when a macrocell is adjacent to a cell of access node to the house. Because the flexible handover has a short delay, and a higher handover success rate compared to the definitive handover, the housing access gateway according to the realization allows the flexible handover to be implemented between an access cell to housing and an RNC cell, and the user experience is improved. Furthermore, due to the proxy of the access gateway to the dwelling according to the embodiment, the RNC can admit a large number of access nodes to the dwelling to simultaneously establish logical connection relations with the RNC; therefore, the flexible transfer between an RNC cell and a housing access node cell is neither limited by the number of RNC connections, nor affected by changes in the location of the housing access nodes. In addition, because the access gateway to housing according to the realization establishes a physical connection with the RNC, the amount and changes of location of the access nodes to the house have no effect on the cost of maintenance and the burden of signaling, so that the network operates in a state of low load, easy planning and easy maintenance. Also, the access gateway to the house according to the embodiment only acts as a proxy for the RNSAP protocol stack, and does not need to include the RNSAP protocol stack, so that the access gateway to the housing does not conflict with the architecture stipulated by the protocol, which collaborates with the evolution towards the protocol and results in a lower implementation cost.

Figure 8B is a schematic structural diagram of a housing access gateway according to another embodiment of the present invention. The realization is implemented based on the realization shown in the

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

Figure 8A, and shown in Figure 8B, the access gateway to the house according to the embodiment also includes: a first reception configuration module 85 and a first identifier determination module 86.

The first interface configuration module 85 is connected to an RNC and is configured to configure a physical physical interface before the first request reception module 81 receives a request for flexible transfer of a housing access node, and establish a signaling connection with the RNC.

The first identifier determination module 86 is connected to the housing access node, and is configured to receive a registration request from the housing access node before the first request reception module 81 receives the transfer request flexible of the access node to the dwelling, determine an identifier of the access node to the dwelling according to the registration request, and save the identifier of the access node to the dwelling.

Likewise, the first identifier determination module 86 can specifically obtain, from the registration request sent by the housing access node, a name of the housing access node (an id of the housing access node), and use the name of the housing access node as the identifier of the housing access node; or be specifically configured to assign a coupling number to the housing access node according to the registration request, and use the assigned coupling number as the identifier of the housing access node.

The first signaling relationship processing module 82 according to the embodiment is specifically configured to establish a signaling connection mapping between the housing access node and the RNC according to the RNC identifier, assigning connection resources forwarding information to the RNC, remove the RNC identifier of the flexible transfer request, replace the user plane information of the access node to the housing in the flexible transfer request with the information on the transfer of connection resources, and forward the transfer request flexible to the RNC.

The access gateway to the housing according to the embodiment also includes any one or a combination of the following modules: a first signaling message forwarding module 87, a first downlink data forwarding module 88, and a first module uplink data forwarding 89.

The first signaling message forwarding module 87 is connected to the housing access node and the RNC, and is configured to receive a signaling message sent by the housing access node, and forwarding the signaling message to the RNC according to the signaling connection mapping between the housing access node and the RNC.

The first downlink data forwarding module 88 is connected to the housing access node and the RNC, and is configured to receive downlink data sent according to the user plane forwarding information by the access node to the housing, and forwarding the downlink data to the RNC according to the connection mapping of the user plane between the access node to the housing and the RNC based on the information on the redirection of connection resources.

The first uplink data forwarding module 89 is connected to the housing access node and the RNC, and is configured to receive uplink data sent by the RNC according to the connection resources forwarding information, and forwarding the uplink data to the access node to the dwelling according to the connection mapping of the user plane between the access node to the dwelling and the RNC based on the information for the re-envfo of the user plane.

The access gateway to the dwelling according to the embodiment can also include: a first module for the completion of the request for completion 90. The first module for the processing of the request for completion 90 is connected to the access node for the home and the RNC; and is configured to receive a flexible transfer termination request sent by the housing access node, forward the flexible transfer termination request to the RNC according to the signaling connection mapping between the housing access node and the RNC , eliminate the signaling connection mapping between the access node to the dwelling and the RNC and the connection mapping of the user plane between the access node to the dwelling and the RNC, and release the forwarding information of the user plane and information on connection resources forwarding.

Each of the functional modules may be configured to execute corresponding processes in the embodiment of the above method (the flexible handover method shown in Figure 4A or Figure 4B), and the operating principles detailed therein are not described. again in detail herein. For more details, reference can be made to the description of the method embodiments.

In the embodiment, the access gateway to the dwelling acts as a proxy for the RNSAP protocol stack between the access node to the dwelling and the RNC, offers a physical luric interface, and establishes a signaling connection with the RNC, for allow the housing access node to establish a logical connection with the RNC; The exchange of user plan data and signaling between the access node to the dwelling and the RNC is completed through the access gateway to the dwelling, thus implementing the flexible transfer process, and solving the problem of

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

Flexible handover when a macrocell is adjacent to a housing access node cell. Meanwhile, the access gateway to housing according to the realization also has the following advantages: improve the user experience; prevent the flexible transfer between an RNC cell and a housing access node cell being limited by the amount of RNC lur connections and being affected by changes in the location of the housing access nodes; allow the network to operate in a state of low load, easy planning and easy maintenance; avoid conflicts with the architecture stipulated by the protocol, collaborating with the development in pursuit of the protocol and resulting in a lower implementation cost.

Figure 9A is a schematic structural diagram of a housing access node according to an embodiment of the present invention. As shown in Figure 9A, the housing access node according to the embodiment includes: a first transfer request sending module 91 and a first transfer response reception module 92.

The first transfer request submission module 91 is connected to a housing access gateway, and is configured to send a flexible transfer request to the housing access gateway, to allow the housing access gateway establish a signaling connection mapping between the housing access node and an RNC according to the flexible transfer request, where the flexible transfer request includes information on the user plan of the housing access node and an RNC identifier. The first transfer response reception module 92 is connected to the housing access gateway, and is configured to receive a flexible transfer response sent by the housing access gateway, where the flexible transfer response is returned by the RNC to the housing access gateway according to the flexible transfer request forwarded by the housing access gateway, and is forwarded to the housing access node after the housing access gateway establishes a mapping of connection of the user plane between the access node to the dwelling and the RNC according to the flexible transfer response, and the flexible transfer response includes forwarding information of the user plane assigned by the access gateway to the housing to the access node to the House. The user plan forwarding information includes information that points to the access gateway to the house.

Each of the functional modules of the access node to the dwelling according to the embodiment can be configured to execute the processes of the flexible transfer method according to an embodiment of the present invention described from the perspective of the access node to the dwelling and the Flexible handover method shown in Figure 3, and the operating principles detailed therein are not described again in detail herein. For more details, reference can be made to the description of the method according to the embodiment.

The gateway of access to housing in the realization can be an HNB-GW; therefore, the housing access node is an HNB. The access gateway to housing can also be a HeNB-GW; therefore, the housing access node is a HeNB.

The access node to the dwelling according to the realization establishes, based on a physical connection established between the access gateway to the dwelling and the RNC, a logical connection with the RNC, and completes the exchange of user plane data and signaling with the RNC through the access gateway to the house, thus implementing the flexible transfer between a macrocell and an HNB cell, and improving the user experience.

Figure 9B is a schematic structural diagram of a housing access node according to another embodiment of the present invention. The realization is implemented based on the realization shown in Figure 9A, and as shown in Figure 9B, the access node to the house according to the realization also includes: a first registration request submission module 93.

The first registration request submission module 93 is connected to the housing access gateway, and is configured to send a registration request to the housing access gateway before the first transfer request submission module 91 send a flexible transfer request to the housing access gateway, to allow the housing access gateway to determine and store an identifier of the housing access node according to the registration request. The registration request includes a name of the housing access node, and the identifier of the housing access node can be the name of the housing access node or a coupling number assigned by the housing access gateway to the access node to the house according to the registration request.

Also, the housing access node according to the embodiment also includes any one or a combination of the following modules: a first signaling message sending module 94, a first downlink data sending module 95, and a first uplink data reception module 96.

The first signaling message sending module 94 is connected to the housing access node, and is configured to send a signaling message to the housing access gateway, to allow the housing access gateway to resend the signaling message to the RNC according to the signaling connection mapping between the housing access node and the RNC.

The first downlink data sending module 95 is connected to the housing access node, and is configured to send downlink data to the housing access gateway according to the information of

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

Forwarding of the user plane, to allow the access gateway to the house to forward the downlink data to the RNC according to the mapping of the user plane connection between the access node to the house and the RNC based on the resource connection forwarding information.

The first uplink data reception module 96 is connected to the home access gateway, and is configured to receive uplink data sent by the RNC and forwarded by the home access gateway according to the connection mapping of the user plane between the access node to the dwelling and the RNC based on the information of the user plane forwarding.

The access node to the house according to the realization also includes: a first module of submission of request for completion 97.

The first termination request submission module 97 is connected to the access node of the dwelling, and is configured to send a flexible transfer termination request to the access node to the dwelling, to allow the access gateway to the dwelling forward the flexible transfer termination request to the RNC according to the signaling connection mapping between the housing access node and the RNC, eliminate the signaling connection mapping between the housing access node and the RNC and the mapping of connection of the user's plane between the access node to the dwelling and the RNC, and release the forwarding information of the user's plane and the forwarding information of connection resources assigned to the RNC.

Each of the above functional modules may be configured to execute corresponding processes in the above method embodiments (the flexible handover method shown in Figure 4A or Figure 4B), and the operating principles detailed therein are not described again in detail herein. For more details, reference can be made to the description of the method embodiments.

The access node to the dwelling according to the realization establishes, based on a physical connection established between the access gateway to the dwelling and the RNC, a logical connection with the RNC, and completes the exchange of user plane data and signaling with the RNC through the access gateway to the house, thus implementing the flexible transfer between a macrocell and a cell for the access node to the house, and improving the user experience.

Figure 10A is a schematic structural diagram of a housing access gateway according to another embodiment of the present invention. As shown in Figure 10A, the access gateway to the housing according to the embodiment includes: a second request reception module 31, a second signaling relationship processing module 32, a second response reception module 33 , and a second module of user relationship processing 34.

The second request reception module 31 is connected to an RNC, and is configured to receive a flexible transfer request sent by the RNC, where the flexible transfer request includes information on RNC connection resources and an identifier of a node of access to housing The second signaling relationship processing module 32 is connected to the second request reception module 31 and the housing access node, and is configured to establish a signaling connection mapping between the RNC and the access node to the housing according to the identifier of the housing access node in the flexible transfer request received by the second request reception module 31, and forward the flexible transfer request to the housing access node based on plan forwarding information of the user assigned to the housing access node. The user plan forwarding information includes information that points to the access gateway to the house. The second response reception module 33 is connected to the housing access node, and is configured to receive a flexible handover response returned by the housing access node according to the flexible handover request, where the handover handover response includes information on the user plan of the access node to the house. The second user relationship processing module 34 is connected to the second response reception module 33 and the RNC, and is configured to establish a mapping of the user plane connection between the housing access node and the RNC according to the information on the user plan of the access node to the dwelling, the forwarding information of the user plan, which forwards information on connection resources assigned to the RNC, and the information on connection resources of the RNC in the transfer response received by the second response reception module 33, and forward the flexible handover response to the RNC based on the connection resources forwarding information. The information on the re-envfo of connection resources includes information that points to the gateway for access to housing.

Each functional module of the access gateway to the dwelling according to the embodiment can be configured to execute the process of the flexible transfer method shown in Figure 5A, and the operating principles detailed therein are not described again in detail in This memory. For more details, reference can be made to the description of the method realization.

The gateway of access to housing in the realization can be an HNB-GW; therefore, the housing access node is an HNB. The access gateway to housing can also be a HeNB-GW; therefore, the housing access node is a HeNB.

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

In the embodiment, the access gateway to the dwelling acts as a proxy for the RNSAP protocol stack between the access node to the dwelling and the RNC, offers a physical interface, and establishes a signaling connection with the RNC, for allow the housing access node to establish a logical connection with the RNC; The exchange of user plan data and signaling between the housing access node and the RNC is completed through the housing access gateway, thus implementing the flexible transfer process, and solving the flexible transfer problem when a macrocell is adjacent to a cell of access node to the house. Because the flexible handover has a short delay, and a higher handover success rate compared to the definitive handover, the access gateway to the house in the realization allows the handover to be implemented between an access node cell to housing and an RNC cell, and the user experience is improved. In addition, due to the proxy of the access gateway to housing in the realization, the RNC can admit a large number of access nodes to the house to simultaneously establish logical connection relationships with the RNC; therefore, the flexible transfer between an RNC cell and a housing access node cell is neither limited by the number of RNC connections, nor affected by changes in the location of the housing access nodes. In addition, because the access gateway to housing in the realization establishes a physical connection with the RNC, the amount and changes of location of the access nodes to the house have no effect on the cost of maintenance and the burden of signaling, so that the network operates in a state of low load, easy planning and easy maintenance. Also, the access gateway to the house in the embodiment acts only as a proxy of the RNSAP protocol stack, and does not need to include the RNSAP protocol stack, so that the access gateway to the housing does not conflict with the architecture stipulated by the protocol, which collaborates with the development towards the protocol and results in a lower implementation cost.

Figure 10B is a schematic structural diagram of a housing access gateway according to another embodiment of the present invention. The embodiment is implemented based on the embodiment shown in Figure 10A, and as shown in Figure 10B, the access gateway housing according to the embodiment also includes: a second interface configuration module 35 and a second identifier determination module 36.

The second interface configuration module 35 is connected to the RNC, and is configured to configure a physical interface, to establish a signaling connection with the RNC.

The second identifier determination module 36 is connected to a housing access node, and is configured to receive a request to register the housing access node, determine an identifier of the housing access node according to the request of registration, and save the identifier of the access node to the house.

Likewise, the second identifier determination module 36 is specifically configured to obtain, from the registration request sent by the housing access node, a name of the housing access node, and use the name of the access node to housing as the identifier of the access node to housing; alternatively, it is specifically configured to obtain, from the registration request, information on the randomization code of the housing access node, and use the randomization coupling number of the housing access node as the identifier of the node of access to housing

Also, the access gateway to the housing according to the embodiment also includes any one or a combination of the following modules: a second signaling message forwarding module 37, a second downlink data forwarding module 38, and a second uplink data forwarding module 39.

The second signaling message forwarding module 37 is connected to the RNC and the housing access node, and is configured to receive a signaling message sent by the RNC, and forwarding the signaling message to the housing access node according to the signaling connection mapping between the HNB and the RNC.

The second downlink data forwarding module 38 is connected to the RNC and the housing access node, and is configured to receive downlink data sent by the RNC according to the connection resources forwarding information, and forwarding the Downlink data to the access node to the dwelling according to the mapping of the user plane connection between the access node to the dwelling and the RNC based on the information for the re-envfo of the user plane.

The second uplink data forwarding module 39 is connected to the RNC and the housing access node, and is configured to receive uplink data sent by the housing access node according to the plane forwarding information. user, and forwarding the uplink data to the RNC according to the connection mapping of the user plane between the access node to the dwelling and the RNC based on the information for the forwarding of connection resources.

The access gateway to the house according to the realization also includes: a second module for request completion processing 40.

The second termination request processing module 40 is connected to the RNC and the access node of the dwelling, and is configured to receive a flexible transfer termination request sent by the RNC,

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

forward the request for completion of flexible transfer to the access node of the dwelling according to the signaling connection mapping between the access node to the dwelling and the RNC, eliminate the signaling connection mapping between the access access node and the RNC and the user plane connection mapping between the housing access node and the RNC, and releasing the user plane forwarding information and the connection resource forwarding information.

Each of the above functional modules may be configured to execute the corresponding flexible handover method processes according to another embodiment of the present invention that is described from the perspective of the housing access node gateway and the flexible handover method that shown in Figure 6, and the operating principles detailed therein are not described again in detail herein. For more details, reference can be made to the description of the method realization.

In the embodiment, the access gateway to the dwelling acts as a proxy for the RNSAP protocol stack between the access node to the dwelling and the RNC, offers a physical luric interface, and establishes a signaling connection with the RNC, for allow the housing access node to establish a logical connection with the RNC; The exchange of user plan data and signaling between the housing access node and the RNC is completed through the housing access gateway, thus implementing the flexible transfer process, and solving the flexible transfer problem when a macrocell is adjacent to a cell of access node to the house. The access gateway to the house according to the embodiment also has the following advantages: improve the user experience, prevent flexible transfer between an RNC cell and a housing access node cell is limited by the number of lur connections RNC and that is affected by changes of location of the nodes of access to housing; allow the network to operate in a state of low load, easy planning and easy maintenance; avoid conflicts with the architecture stipulated by the protocol, collaborating with the development in pursuit of the protocol and resulting in a lower implementation cost.

Figure 11A is a schematic structural diagram of an RNC according to an embodiment of the present invention. As shown in Figure 11A, the RNC according to the embodiment includes: a second transfer request sending module 41 and a second transfer response reception module 42.

The second transfer request submission module 41 is connected to a housing access gateway, and is configured to send a flexible transfer request to the housing access node, to allow the housing access gateway to establish a signaling connection mapping between a housing access node and the RNC according to the flexible transfer request, where the flexible transfer request includes information on RNC connection resources and an identifier of the housing access node. The second transfer response reception module 42 is connected to the housing access gateway, and is configured to receive a flexible transfer response sent by the housing access gateway, where the flexible transfer response is returned by The access node to the dwelling to the access gateway to the dwelling according to the request for flexible transfer forwarded by the access gateway to the dwelling, and is forwarded to the RNC after the housing access gateway establishes a mapping of connection of the user plane between the access node to the dwelling and the RNC according to the flexible transfer response, and the flexible transfer response includes forwarding information on connection resources assigned by the access gateway to the RNC. The information on the re-envfo of connection resources includes information that points to the gateway for access to housing.

Each of the functional modules of the RNC according to the embodiment may be configured to execute the processes of the flexible handover method according to another embodiment of the present invention that is described from the perspective of the RNC and the flexible handover method shown in Figure 5B, and the operating principles detailed therein are not described again in detail herein. For more details, reference can be made to the description of the method realization.

The gateway of access to housing in the realization can be an HNB-GW; therefore, the housing access node is an HNB. The access gateway to housing can also be a HeNB-GW; therefore, the housing access node is a HeNB.

The RNC according to the embodiment allows, based on a physical connection established with the access gateway to the house, the housing access node establishes a logical connection with the RNC, and completes the exchange of user plane data and signaling with the access node to the dwelling through the access gateway to the dwelling, thus implementing the flexible transfer between a macrocell and a cell of the access node to the dwelling, and improving the user experience.

Figure 11B is a schematic structural diagram of an RNC according to another embodiment of the present invention. The embodiment is implemented based on the embodiment shown in Figure 11A, and as shown in Figure 11B, the rNc according to the embodiment also includes any one or a combination of the following modules: a second module of signaling message forwarding 43, a second downlink data send module 44, and a second uplink data reception module 45.

The second signaling message sending module 43 is connected to the housing access gateway, and is configured to send a signaling message to the housing access gateway according to the information

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

of connection resources forwarding, to allow the housing access gateway to forward the signaling message to the housing access node according to the signaling connection mapping between the housing access node and the RNC.

The second downlink data sending module 44 is connected to the housing access gateway, and is configured to send downlink data to the housing access gateway according to the connection resource forwarding information, to allow that the access gateway to the dwelling forwards the downlink data to the access node to the dwelling according to the mapping of the user's plane connection between the access node to the dwelling and the RNC based on the information for the forwarding of the drawing of the user assigned to the HNB.

The second uplink data reception module 45 is connected to the housing access gateway, and is configured to receive uplink data sent by the housing access node and forwarded by the housing access gateway according to the mapping of the user plane connection between the access node to the dwelling and the RNC based on the information of connection resources forwarding.

The RNC, according to the embodiment, also includes: a second module for sending a request for completion 46.

The second termination request submission module 46 is connected to the access gateway of the dwelling, and is configured to send a flexible transfer termination request to the access gateway to the dwelling, to allow the access gateway to the housing forwards the request for completion of flexible handover to the HNB according to the signaling connection mapping between the housing access node and the RNC, eliminating the signaling connection mapping between the housing access node and the RNC and the mapping of the user's plane connection between the housing access node and the RNC, and releasing the connection resource forwarding information and the user plane forwarding information assigned to the housing access node.

Each of the above functional modules may be configured to execute corresponding processes in the method realization (the flexible handover method shown in Figure 6), and the operating principles detailed therein are not described again in detail in This memory. For more details, reference can be made to the description of the method embodiments.

The RNC according to the embodiment allows, based on a physical connection established with the access gateway to the dwelling, the access node establishes a logical connection with the RNC, and completes the exchange of user plane data and signaling with the Housing access node through the housing access gateway, thus implementing the flexible transfer between a macrocell and a housing access node cell, and improving the user experience.

Figure 12 is a schematic structural diagram of a housing access node according to another embodiment of the present invention. As shown in Figure 12, the housing access node according to the embodiment includes: a transfer request reception module 51 and a transfer response send module 52.

The transfer request reception module 51 is connected to a housing access gateway, and is configured to receive a flexible transfer request forwarded by the housing access gateway based on the user plane forwarding information assigned to the housing access node, where the flexible transfer request includes an identifier of the housing access node, and the flexible transfer request is sent by an RNC to the housing access gateway, and is forwarded after that the housing access gateway establishes a signaling connection mapping between the RNC and the housing access node according to the flexible transfer request. The user plan forwarding information includes information that points to the access gateway to the house. The transfer response delivery module 52 is connected to the transfer request reception module 51 and the housing access gateway, and is configured to send a flexible transfer response to the housing access gateway according to the request flexible handover, where the flexible handover response includes information on the user plan of the housing access node, to allow the housing access gateway to establish a mapping of the user's plane connection between the access node to the home housing and the RNC according to the flexible transfer response, and forward the flexible transfer response to the RNC.

Each functional module of the RNC according to the embodiment can be configured to execute the process of the above flexible transfer method described from the perspective of the housing access node, and the detailed operating principles thereof are not described again in detail in the present memory For more details, reference can be made to the description of the method realization.

The HNB according to the embodiment also includes: a second registration request submission module 53.

The second registration request submission module 53 is connected to the housing access gateway, and is configured to send a registration request to the housing access gateway, to allow the housing access gateway to determine an identifier of the housing access node according to the registration request. The identifier of the housing access node can be a name of the housing access node, or randomization code information of the housing access node.

The node of access to housing in the realization can be an HNB; therefore, the access gateway to housing is an HNB-GW. The access node to housing can also be a HeNB; therefore, the gateway to access housing is a HeNB-GW.

The access node to the dwelling according to the realization establishes, based on a physical connection established between the 5 access gateway to the dwelling and the RNC, a logical connection with the RNC, and completes the exchange of user plane data and signaling with the RNC through the access gateway to the house, thus implementing the flexible transfer between a macrocell and a cell of access node to the house, and improving the user experience.

A person with ordinary experience in the art may understand that some or all stages of the 10 methods in the embodiments can be implemented by a program that instructs relevant hardware. The program can be stored in a computer readable storage medium. When the program is executed, the previous steps of the methods are carried out in the embodiments. The storage medium can be any medium capable of storing program codes, such as ROM, RAM, magnetic disk, or optical disk, or similar elements.

fifteen

Claims (15)

5 10 fifteen twenty 25 30 35 40 Four. Five fifty 1. A flexible handover method comprising: receive (201, 1d, 2d, 4d), by a housing access gateway, a flexible transfer request sent by a housing access node, where the flexible transfer request includes user plan information of the access node to the house and an identifier of a radio network controller, RNC, where the information of the user plane of the access node to the house comprises an internet protocol address, IP, of the user plane and a number of user datagram protocol port, UDP; establish (202, 1e, 2e, 4e), by the housing access gateway according to the RNC identifier, a signaling connection mapping between the housing access node and the RNC, and forward the request for Flexible transfer to the RNC based on the connection resource forwarding information assigned to the RNC, where the connection resource forwarding information comprises an IP address of the user plane and a UDP port number pointing to the access gateway to the dwelling if a means of link between the access gateway to the dwelling and the RNC is IP over Ethernet, or the connection resource forwarding information comprises a channel identifier that points to the access gateway to the dwelling and which it is necessary to establish an adaptation layer link of type 2, AAL2, asmchronous transfer mode, ATM, if a means of link between the access gateway to the dwelling and the RNC is ATM; receive (203, 1g, 2g, 4g), by a housing access gateway, a flexible transfer response returned by the RNC according to the flexible transfer request, where the flexible transfer response includes information on resources from RNC connection, where the RNC connection resource information mainly comprises an IP address of the user plane and an RNC UDP port number if the means of link between the access gateway to the dwelling and the RNC is IP over Ethernet, or the RNC connection resource information comprises a channel identifier that is needed to establish an AAL2 link if the means of link between the housing access gateway and the RNC is ATM; Y establish (204, 1h, 2h, 4h), by the access gateway to the dwelling, a mapping of the user's plane connection between the access node to the dwelling and the RNC according to the information of the user plane of the node of access to housing, information on the re-connection of connection resources, which forwards information on the user's plan assigned to the access node for housing, and the information on connection resources of the RNC, and forwarding the flexible handover response to the node of access to the dwelling based on the information of the user's plane forwarding, where the information of the user's plane forwarding comprises an IP address of the user's plane and a UDP port number that points to the access gateway to the living place. 2. The flexible transfer method according to claim 1, wherein the forwarding, by the access gateway to the dwelling, of the request for flexible transfer to the RNC based on the information on the transfer of connection resources assigned to the RNC understands: delete (1f, 2f, 2h, 4h), by the access gateway to the dwelling, the RNC identifier of the flexible transfer request; replace (1f, 2h, 4h), by means of the access gateway to the dwelling, the information of the user plan of the access node to the dwelling in the request for flexible transfer with the information on the transfer of connection resources; Y Forward (1f, 2h, 4h), by the access gateway to the house, the request for flexible transfer to the RNC. 3. The flexible handover method according to claim 1 or 2, wherein after the re-sending, by the gateway of access to the house, of the flexible handover response to the housing access node based on the information of Forwarding of the user plane, the method comprises: receive (1i, 2k, 4i), by the access gateway to the dwelling, a signaling message sent by the access node to the dwelling, and forward (1j, 21, 4j) the signaling signal to the RNC according to the signaling connection mapping between the housing access node and the RNC; or receive (1k, 2m, 4k), by the access gateway to the dwelling, downlink data sent according to the forwarding information of the user's plane by the access node to the dwelling, and forward (11, 2n , 41) the downlink data to the RNC according to the connection mapping of the user plane between the access node to the dwelling and the RNC and based on the information on the redirection of connection resources; or receive (1m, 2o, 4m), by the access gateway to the house, uplink data sent by the RNC according to the information of connection resources forwarding, and forward (1n, 2p, 4n) the data of uplink to the access node to the dwelling according to the mapping of the connection of the user plane between the access node to the dwelling and the RNC and based on the information of the user plane forwarding. 5 10 fifteen twenty 25 30 35 40 Four. Five fifty 4. The flexible transfer method according to any one of claims 1 to 3, wherein after the resubmission, by the access gateway to the dwelling, of the flexible transfer request to the access node to the dwelling based on the Forwarding information of the user plane, the method comprises: receive (1o, 2q, 4o), by the access gateway to the house, a request for completion of flexible transfer sent by the access node to the house, Forward (1p, 2r, 4p) the request for completion of flexible transfer to the RNC according to the signaling connection mapping between the housing access node and the RNC. eliminate (1r, 2t, 4q) the signaling connection mapping between the housing access node and the RNC and the user plane connection mapping between the housing access node and the RNC, and release (1st, 2nd, 4th) the forwarding information from the user plane and the forwarding information of connection resources. 5. The flexible handover method according to any one of claims 1 to 4, wherein the signaling connection mapping between the housing access node and the RNC is established by linking the identifier of the housing access node with the identifier of the RNC, and the mapping of the user plane connection between the access node to the dwelling and the RNC is established by linking the information of the user plan of the access node to the dwelling, the information of the user plane forwarding , the information of connection resources forwarding, and the information of connection resources of the RNC, where the information of the user plan of the access node for the home corresponds to the information of the connection of the user plane, the information of User plane forwarding corresponds to the connection resources forwarding information, and the connection resources forwarding information corresponds to the RNC connection resources information . 6. A flexible handover method comprising: receive (501, 3e), by a housing access gateway, a flexible transfer request sent by an RNC radio network controller, where the flexible transfer request comprises information on RNC connection resources and an identifier of a housing access node, where the RNC connection resource information comprises an internet protocol address, IP, of the user plane and a user datagram protocol port number, UDP if a means of The link between the home access gateway and the RNC is IP over Ethernet, or the RNC connection resource information comprises a channel identifier that is needed to establish a type 2 adaptation layer link, AAL2, so asmchronous transfer, ATM, if a means of connection between the gateway to the house and the RNC is ATM; establish (502, 3f), by the access gateway to the dwelling, according to the identifier of the access node to the dwelling, a signaling connection mapping between the RNC and the access node to the dwelling, and forward the request flexible transfer to the access node to the dwelling based on the forwarding information of the user plan assigned by the access gateway to the dwelling to the access node to the dwelling, where the forwarding information of the user drawing comprises a first information pointing to the access gateway to the dwelling, the first information comprising an IP address of the user plan and a UDP port number; receive (503, 3h), by the access gateway to the dwelling, a flexible transfer response returned by the access node to the dwelling, where the flexible transfer response comprises information of the user plane of the access node to the dwelling, and the information of the user's plan of the access node to the dwelling comprises an IP address of the user's drawing and a UDP port number; Y establish (504, 3i), by the access gateway to the dwelling, a mapping of the user's plane between the access node to the dwelling and the RNC according to the information of the user plan of the access node to the housing, the forwarding information of the user plan, which forwards the connection resources information assigned to the RNC, and the RNC connection resources information, and forwarding the flexible transfer response to the RNC based on the forwarding information of connection resources, where the connection resources forwarding information comprises an IP address of the user plan and a UDP port number that points to the access gateway to the dwelling and which are assigned by the access gateway to the dwelling to the RNC if the link means between the access gateway to the dwelling and the RNC is IP over Ethernet, or the connection resource forwarding information comprises a channel identifier that is needed to establish an AAL2 link , assigned by the housing access gateway to the RNC and pointing to the housing access gateway if the means of connection between the housing access gateway and the RNC is ATM 7. The flexible transfer method according to claim 6, wherein after forwarding, by means of the access gateway to the dwelling, the flexible transfer response to the RNC based on the information on the transfer of connection resources, the method understands: 5 10 fifteen twenty 25 30 35 40 Four. Five fifty receive (3j), by the access gateway to the house, a signaling message sent by the RNC, and forward (3k) the signaling message to the access node to the house according to the signaling connection mapping between the access node to housing and the RNC; or receive (31), by the access gateway to the dwelling, downlink data sent by the RNC according to the connection resources forwarding information, and forward (3m) the downlink data to the access node to the housing according to the mapping of the user plane connection between the access node to the house and the RNC and based on the information of the user plane forwarding; or receive (3n), by the access gateway to the dwelling, uplink data sent by the access node to the dwelling according to the forwarding information of the user plane, and forward (3rd) the uplink data to the RNC according to the mapping of the user's plane between the access node to the dwelling and the RNC, and based on the information on the redirection of connection resources. 8. The flexible transfer method according to claim 6 or 7, wherein after forwarding, by means of the access gateway to the dwelling, the flexible transfer response to the RNC based on the information on the transfer of connection resources, The method comprises: receive (3p), by the access gateway to the house, a request for completion of flexible transfer sent by the RNC, forward (3q) the request for completion of flexible transfer to the access node to the dwelling according to the signaling connection mapping between the access node to the dwelling and the RNC, eliminate (3s) the signaling connection mapping between the housing access node and the RNC and the mapping of connection of the user plan between the access node to the dwelling and the RNC, and release (3t) the user plane forwarding information and the connection resources forwarding information. 9. The flexible handover method according to any of claims 6 to 8, wherein the signaling connection mapping between the RNC and the housing access node is established by linking the identifier of the housing access node with a signaling point of signal connection control part, SCCP, corresponding to the RNC; Y The mapping of the connection of the user plane between the access node to the dwelling and the RNC is established by linking the information of the user plan of the access node to the dwelling, the information of the forwarding of the user plane, the forwarding information of connection resources, and the information of connection resources of the rNc. 10. An access gateway to housing, comprising: a first request reception module (81), configured to receive a flexible transfer request sent by a housing access node, wherein the flexible transfer request comprises information of the user plan of the housing access node and an identifier of a radioelectric network controller, RNC, where the information of the user plane of the access node to the home comprises an internet protocol address, IP, of the user plane and a user datagram protocol port number , UDP; a first signaling relationship processing module (82), configured to establish, according to the RNC identifier, a signaling connection mapping between the housing access node and the RNC, and forwarding the flexible transfer request to the RNC based on the connection resource forwarding information assigned to the RNC, where the connection resource forwarding information comprises an IP address of the user plane and a UDP port number that points to the access gateway to the home if A means of link between the access gateway to the dwelling and the RNC is iP over Ethernet, or the connection resource forwarding information comprises a channel identifier that points to the access gateway to the dwelling and is needed to establish a type 2 adaptation layer link, AAL2, asmchronous transfer mode, ATM, if the link between the access gateway to the dwelling and the RNC is ATM; a first response reception module (83), configured to receive a flexible handover response returned by the RNC according to the flexible handover request, wherein the handover handover response comprises information of RNC connection resources, where the information of RNC connection resources mainly comprises an IP address of the user plane and a UDP port number if the means of connection between the access gateway to the dwelling and the RNC is IP over Ethernet, or the connection resource information of the RNC comprises a channel identifier that is needed to establish an AAL2 link if the means of link between the housing access gateway and the RNC is ATM; Y a first user relationship processing module (84), configured to establish a mapping of the user's plane between the access node to the dwelling and the RNC according to the information of the user drawing of the access node to the dwelling, the connection resources forwarding information, which forwards information of the user map assigned to the housing access node, and the RNC connection resources information, and forwarding 3. 4 5 10 fifteen twenty 25 30 35 40 Four. Five fifty 55 the flexible handover response to the access node to the dwelling based on the user plane forwarding information, where the user plane forwarding information comprises an IP address of the user plane and a UDP port number that point to the access gateway to the house. 11. The access gateway to the dwelling according to claim 10, wherein the first signaling relationship processing module (82) is configured to eliminate the RNC identifier of the flexible transfer request, replace the user plane information of the node of access to the house in the request of flexible transfer with the information of forwarding of connection resources, and to forward the request of flexible transfer to the RNC. 12. The access gateway to housing according to claim 10 or 11, which also includes: a first signaling message forwarding module (87), configured to receive a signaling message sent by the housing access node, and forwarding the signaling message to the RNC according to the signaling connection mapping between the access node to housing and the RNC; a first downlink data forwarding module (88), configured to receive downlink data sent by the housing access node according to the user plane forwarding information, and forwarding the downlink data to the RNC according to the mapping of the user's plane connection between the access node to the dwelling and the RNC, and based on the information of connection resources forwarding; Y a first uplink data forwarding module (89), configured to receive uplink data sent by the RNC according to the connection resource forwarding information, and forwarding the uplink data to the housing access node according to the mapping of the connection of the user plane between the access node to the dwelling and the RNC, and based on the information of the user plane forwarding. 13. The access gateway to housing according to any of claims 10 to 12, which further comprises: a first completion request processing module (90), configured to receive a flexible handover termination request sent by the housing access node, forward the flexible handover termination request to the RNC according to the signaling connection mapping between the housing access node and the RNC, eliminate the signaling connection mapping between the housing access node and the RNC and the user plane connection mapping between the housing access node and the RNC , and release the forwarding information from the user plane and the forwarding information of connection resources. 14. An access gateway to housing, comprising: a second request reception module (31), configured to receive a flexible handover request sent by an RNC radio network controller, wherein the flexible handover request comprises RNC connection resource information and an identifier of a node of access to the home NodeB home, where the RNC connection resource information includes an internet protocol address, IP, of the user plane and a user datagram protocol port number, UDP if a link between the access gateway to the dwelling and the RNC is IP over Ethernet, or the RNC connection resource information comprises a channel identifier that is needed to establish a type 2 adaptation layer link, AAL2, for transfer mode asmcrona, ATM, if a means of liaison between the access gateway to the dwelling and the RNC is ATM; a second signaling relationship processing module (32), configured to establish, according to the identifier of the housing access node, a signaling connection mapping between the RNC and the housing access node, and forwarding the request for flexible transfer to the access node to the home based on the forwarding information of the user plan assigned by the access gateway to the housing access node, where the information for forwarding the user plan comprises a first information that points to the access gateway to the dwelling, the first information comprising an IP address of the user's plane and a UDP port number; a second response reception module (33), configured to receive a flexible handover response returned by the housing access node according to the flexible handover request, wherein the handover handover response comprises information of the node user's plane of access to the dwelling, and the information of the user plan of the access node to the dwelling comprises an IP address of the user plane and a UDP port number; Y a second user relationship processing module (34), configured to establish a signaling connection mapping between the housing access node and the RNC according to the user plane information of the housing access node, the information for forwarding the user plane, which forwards the connection resource information assigned to the RNC, and the RNC connection resource information, and forwarding the flexible handover response to the RNC based on the connection resource forwarding information, where the connection resources forwarding information, where the connection resources forwarding information comprises an IP address of the user plane and a UDP port number that points to the access gateway to the dwelling and which are assigned by the RNC access gateway to housing if the means of link between the gateway access to the home and the RNC is IP over Ethernet, or the connection resource forwarding information comprises a channel identifier that is needed to establish an AAL2 link, assigned by the housing access gateway to the RNC and which points to the access gateway to housing if the means of connection between the access gateway to housing and the RNC is ATM 5 15. The access gateway to housing according to claim 14, which further includes: a second signaling message forwarding module (37), configured to receive a signaling message sent by the RNC, and forwarding the signaling message to the housing access node according to the signaling connection mapping between the access node to housing and the RNC; a second downlink data forwarding module (38), configured to receive downlink data sent by the RNC according to the connection resources forwarding information, and forwarding the downlink data to the housing access node according to the mapping of the user's plane connection between the access node to the dwelling and the RNC, and based on the information of the user's plane forwarding; Y a second uplink data forwarding module (39), configured to receive uplink data sent by the housing access node according to the user plane forwarding information, and forwarding the uplink data to the RNC according to the mapping of the user plane connection between the access node to the dwelling and the RNC, and based on the information on the redirection of connection resources. 16. The access gateway to housing according to claim 14 or 15, which also includes: a second completion request processing module (40), configured to receive a flexible handover termination request sent by the RNC, forward the flexible handover termination request to the access node 20 according to the connection connection mapping signaling between the housing access node and the RNC, eliminating the signaling connection mapping between the housing access node and the RNC and the user plane connection mapping between the housing access node and the RNC, and release the forwarding information from the user plane and the forwarding information of connection resources.