WO2011137858A1

WO2011137858A1 - Method and relevant apparatuses for establishing interface between base stations and realizing cell switch

Info

Publication number: WO2011137858A1
Application number: PCT/CN2011/075064
Authority: WO
Inventors: 张亮亮; 周铮; 时洁
Original assignee: 华为技术有限公司
Priority date: 2010-11-17
Filing date: 2011-05-31
Publication date: 2011-11-10
Also published as: CN102469539A

Abstract

Provided are a method and relevant apparatuses for establishing an interface between base stations and realizing cell switch. The method includes that it is determined whether a first HeNB and a second HeNB are located under an identical HeNB GW (201), and if the first HeNB and the second HeNB are located under an identical HeNB GW, the first HeNB establishes an X2 interface between the first HeNB and the second HeNB (202) or makes a subordinate UE of the first HeNB switch to the second HeNB via an X2 interface. With the present invention, the waste of network resource in the switch process can be lowered and the switch is guaranteed to be implemented normally.

Description

Method for establishing interface between base stations and implementing cell handover and related device The present application claims to be submitted to the Chinese Patent Office on November 17, 2010, the application number is 201010547948.0, and the invention name is "establishing an interface between base stations and realizing cell handover. The priority of the Chinese patent application of the method and the related device is hereby incorporated by reference in its entirety. Technical field

The present invention relates to the field of communication technologies, and in particular, to a method and an apparatus for establishing an interface between base stations and implementing cell switching. Background technique

In the mobile communication system, in order to improve the handover efficiency of the cell, two of the network topology structures

A HeNB (Home Evolution Node B), or a direct X2 interface between the HeNB and an eNB (Evolution Node B). In the cell handover procedure, the pair of MME UE SIAP ID and eNB UE SIAP ID are used to indicate terminal related signaling on the SI interface. If the HeNB is connected to the MME through the HeNB GW, the HeNB GW is equivalent to one base station from the perspective of the MME, and the HeNB GW is equivalent to one MME from the perspective of the HeNB. Therefore, on the S1 interface on the HeNB GW-MME side, the MME allocates one MME UE SIAP ID, such as MME UE SIAP ID1, to the UE subordinate to the HeNB. A HeNB GW may be connected to multiple MMEs, and different MMEs may allocate the same MME UE SIAP ID to different terminals in the same HeNB under the HeNB GW. Since the MME UE SIAP ID is located in a connection of different MME-HeNB GWs, the interface between the MME-HeNB GWs does not have a label collision problem. On the HeNB GW-HeNB interface, an ID conflict occurs, which causes the HeNB to fail to identify multiple identical MMEs. The SIAP IDs indicate which terminals are respectively indicated. In order to solve the above problem, the HeNB GW allocates another MME UE SIAP ID, such as the MME UE SIAP ID-la, on the SI interface of the HeNB GW-HeNB side, that is, when the HeNB GW passes the HeNB GW- When receiving the S1 message sent by the MME, the SI interface on the MME side converts the MME UE SIAP ID1 allocated by the MME included in the message into the MME UE SIAP ID-la allocated by itself. After a direct X2 interface is introduced, a switching scenario based on the direct X2 interface is shown in FIG. 1 , which is a schematic diagram of a switching scenario in the prior art. In this scenario, the handover is performed between two HeNBs that have established a direct X2 interface, and the two HeNBs belong to different HeNB GWs, respectively.

The inventor has found that in the above scenario, when switching from HeNB1 to HeNB2, for HeNB1, it only knows the MME UE SIAP ID allocated by the HeNB GW1, and does not know the MME UE SIAP ID allocated by the MME. That is to say, the ID assigned by the MME to the UE is not directly used by the gateway as the ID of the UE, but the ID of the gateway itself is generated according to the ID assigned by the MME based on a certain relationship. Thus, when MMEs that are not related to each other assign the same ID to different terminals, the gateway can distinguish by generating its own ID. The HeNB1 sends the MME UE SIAP ID allocated by the HeNB GW1 to the HeNB2 through the direct X2 interface, and the HeNB2 sends the MME UE SIAP ID to the HeNB GW2, and the HeNB GW2 continues to send the MME UE SIAP ID to the MME, because the MME UE The SIAP ID is allocated by the HeNB GW1. Therefore, the MME cannot identify the received MME UE SIAP ID, and eventually the handover cannot be implemented normally. Conversely, when switching from HeNB2 to HeNB 1, the same problem occurs.

In addition, when the network system cannot perform normal handover, the X2 interface established in the above scenario cannot be fully utilized. The established X2 interface is bound to waste network resources for the entire network system.

Summary of the invention

In order to solve the above technical problem, the embodiments of the present invention provide a method for establishing an interface between base stations, implementing cell handover, and related devices, so as to reduce network resource waste occurring in the X2 handover process.

The embodiment of the invention discloses the following technical solutions:

A method for establishing an interface between the base stations, including: determining whether the first HeNB and the second HeNB are located under the same HeNB GW; if the first HeNB and the second HeNB are located under the same HeNB GW, the first HeNB establishes the first An X2 interface between the HeNB and the second HeNB.

An apparatus for establishing an interface between base stations, comprising: a determining unit, configured to determine whether a first HeNB and a second HeNB are located under a same HeNB GW; and an establishing unit, configured to: if the first HeNB and the second HeNB are located in the same HeNB Under the GW, an X2 interface between the first HeNB and the second HeNB is established.

It can be seen from the above embodiment that before establishing an X2 interface between two HeNBs, first two Whether the HeNB is located under the same gateway, and then determines whether to establish an X2 interface. When two HeNBs are located under the same gateway, an X2 interface can be established, and the X2 interface is used to perform operations related to the handover process, thereby avoiding the failure to implement The waste of network resources caused by establishing an X2 interface during handover.

A method for implementing cell handover includes: determining whether a first HeNB and a second HeNB are located under the same HeNB GW; if the first HeNB and the second HeNB are located under the same HeNB GW, the first HeNB uses the X2 interface to be the first The HeNB subordinate UE switches to the second HeNB.

An apparatus for implementing cell handover, comprising: a determining unit, configured to determine whether a first HeNB and a second HeNB are located under a same HeNB GW; and a handover unit, configured to: if the first HeNB and the second HeNB are located under the same HeNB GW The first HeNB subordinate UE is handed over to the second HeNB by using an X2 interface.

It can be seen from the foregoing embodiment that, before the cell handover, when the two HeNBs are located under the same gateway, the handover can be performed, and the UE identifier received by the MME cannot be identified when the two HeNBs are located under different gateways. Reduce the possibility of switching failures.

A method for implementing a cell handover includes: receiving, by a HeNB GW to which the first HeNB belongs, a first MME UE SIAP ID allocated by the first MME to the UE, and determining whether the first MME UE SIAP ID is different from the first MME The MME UE SIAP ID assigned to the UE by any other MME is the same; if the first MME UE SIAP ID and any other MME other than the first MME are allocated to the MME UE SIAP ID of the UE Not the same, the HeNB GW to which the first HeNB belongs sends the first MME UE SIAP ID to the second HeNB through the first HeNB; the second HeNB provides the first MME UE SIAP ID to the The first MME is configured to indicate to the first MME that the UE that has a handover occurs.

An apparatus for implementing cell handover, comprising: an identifier receiving unit, configured to receive a first MME UE SIAP ID sent by a second HeNB, where the first MME UE SIAP ID is a HeNB GW to which the first HeNB belongs is the UE And an identifier conversion unit, configured to convert the first MME UE SIAP ID into a second MME UE SIAP ID that can be identified by the MME according to a preset mapping relationship, and a first handover indication unit, configured to: use the second MME UE SIAP ID Sending to the MME to indicate to the MME the UE in which the handover occurred.

It can be seen from the above embodiment that if two base stations are not under the same gateway and an interface is established between the two base stations, in order to ensure the normal completion of the handover, in the gateway to which the two base stations belong respectively The mapping relationship between the MME UE SIAP ID allocated by the MME for the UE and the MME UE SIAP ID allocated by the handover peer to the UE is saved, so that when any one of the two gateways receives the MME allocated by the handover peer to the UE, In the case of the UE SIAP ID, the MME UE SIAP ID that the MME allocates for the UE, that is, the MME UE SIAP ID that the MME can identify, can be obtained according to the mapping relationship, thereby ensuring the normal completion of the handover.

An apparatus for implementing cell handover, comprising: an identifier determining unit, configured to receive a first MME UE SIAP ID allocated by the first MME to the UE, and determine whether the first MME UE SIAP ID is other than the first MME The MME UEs that are assigned to the UE by the MME are the same; the identifier sending unit is configured to: if the first MME UE SIAP ID and any other MME except the first MME are allocated to the UE The MME UE SIAP ID is different, and the first MME UE SIAP ID is sent to the second handover indication unit by using the first HeNB, and the second handover indication unit is configured to: use the first MME UE SIAP ID Provided to the first MME, to indicate to the first MME that the UE that has a handover occurs.

As can be seen from the foregoing embodiment, it is also ensured that different MMEs have different MME UE SIAP IDs assigned to the same UEs of the subordinates. When the gateway to which the base station belongs finds that at least two MMEs allocate the same MME UE SIAP ID to the subordinate UEs. Then, the MME is requested to re-allocate the MME UE SIAP ID, so that the gateway to which the base station belongs directly sends the MME UE SIAP ID that can be identified by the MME to the base station gateway of the handover peer, thereby ensuring the normal completion of the handover.

BRIEF DESCRIPTION OF THE DRAWINGS In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following will be implemented. The drawings used in the examples or the description of the prior art are described in the drawings. It is obvious that the drawings in the following description are only some embodiments of the present invention, and are not creative to those skilled in the art. Other drawings can also be obtained from these drawings on the premise of labor.

1 is a schematic diagram of a handover scenario in the prior art;

2 is a flowchart of an embodiment of a method for establishing an interface between base stations according to the present application; FIG. 3 is a flowchart of an embodiment of a method for implementing cell handover according to the present application; A signaling flow diagram for establishing an interface between base stations;

FIG. 5 is another signaling flowchart of establishing an interface between base stations according to the present application;

6 is another signaling flowchart of establishing an interface between base stations according to the present application;

7 is another signaling flowchart of establishing an interface between base stations according to the present application;

FIG. 8 is a flowchart of another embodiment of a method for implementing cell handover according to the present application; FIG. 9 is a flowchart of another embodiment of a method for implementing cell handover according to the present application; A structural diagram of an embodiment of an apparatus for establishing an interface; FIG. 11 is a schematic structural diagram of a judging unit in the present application;

Figure 12 is a schematic structural view of a building unit in the present application;

FIG. 13 is a structural diagram of an embodiment of an apparatus for implementing cell handover according to the present application; FIG. 14 is a structural diagram of another implementation of an apparatus for implementing cell handover according to the present application; A structural diagram of another embodiment of a device for handover; FIG. 16 is a structural diagram of another embodiment of an apparatus for implementing cell handover according to the present application. DETAILED DESCRIPTION OF THE INVENTION In order to solve the above technical problem, the present application provides a method for establishing an interface between base stations. Before establishing an X2 interface between two HeNBs, it is determined whether two HeNBs are located under the same gateway, and then determining whether to establish an X2 interface. When the two HeNBs are located under the same gateway, an X2 interface can be established, and the X2 interface is used to perform operations related to processes such as handover, thereby avoiding waste of resources.

In addition, the method of establishing an interface between the base stations can be applied to the cell handover, that is, before the cell switching, the X2 interface is established according to the method of establishing an interface between the base stations, and then the cell handover is implemented according to the established X2 interface.

Of course, if an interface has been established between the base stations, it can also be determined whether the two HeNBs are located in the same Determining whether to perform handover under a gateway, and performing handover when two HeNBs are located under the same gateway, and avoiding the situation that the UE identifier received by the MME cannot be identified when the two HeNBs are located under different gateways, thereby reducing the possibility of handover failure. Sex.

The above described objects, features, and advantages of the present invention will become more apparent from the aspects of the invention. Embodiment 1

Please refer to FIG. 2, which is a flowchart of an embodiment of a method for establishing an interface between base stations according to the present application. Includes the following steps:

Step 201: Determine whether the first HeNB and the second HeNB are located under the same HeNB GW. The determining, by the first HeNB, that the first HeNB and the second HeNB are located under the same HeNB GW, the first HeNB obtains the HeNB to which the first HeNB belongs. a TAI (Tracking Area Indicator Tracking Area Indicator) list of the GW; the first HeNB determines whether the TAI of the second HeNB is in the obtained TAI list; if the TAI of the second HeNB is in the obtained TAI list, determining the first HeNB It is located under the same HeNB GW as the second HeNB. Specifically, in the HeNB scenario, one HeNB GW has multiple TAIs, and each TAI is assigned to one HeNB under it; different HeNB GWs have different TAI lists, and no overlap occurs. Therefore, the first HeNB can determine whether the second HeNB belongs to one HeNB GW by itself through the TAI list.

The obtaining, by the first HeNB, the TAI list of the HeNB GW to which the first HeNB belongs includes: acquiring, by the first HeNB, the TAI of the HeNB GW to which the first HeNB belongs from the OAM, the O&M, the EMS, the NMS, or the HeNB GW to which the first HeNB belongs. List.

In this embodiment, the first HeNB may first send an acquisition request message to the HeNB GW to which the first HeNB belongs to the OAM, the O&M, the EMS, the NMS, or the HeNB GW to which the first HeNB belongs, and then obtain the TAI list of the HeNB GW to which the first HeNB belongs, and then the OAM, The O-M, the EMS, the NMS, or the HeNB GW replies with the request message of the first HeNB, and sends the TAI list of the HeNB GW to which the first HeNB belongs to the first HeNB. In addition, the OAM, the O0, the EMS, the NMS, or the first HeNB may also actively send the TAI list of the HeNB GW to which the first HeNB belongs to the first HeNB.

In addition, determining whether the first HeNB and the second HeNB are located under the same HeNB GW is specifically: the HeNB GW to which the first HeNB belongs determines whether the first HeNB and the second HeNB are located in the same HeNB. If the first HeNB and the second HeNB are located under the same HeNB GW, the HeNB GW to which the first HeNB belongs sends an indication message indicating that the first HeNB and the second HeNB are located under the same HeNB GW to the first HeNB.

Based on the determining whether the first HeNB and the second HeNB are located under the same HeNB GW, the HeNB GW to which the first HeNB belongs determines whether the TAI of the second HeNB is in its own TAI list; if the TAI of the second HeNB is In the TAI list of the HeNB GW to which the first HeNB belongs, it is determined that the first HeNB and the second HeNB are located under the same HeNB GW.

It should be noted that the “first HeNB” is any HeNB in the network that needs to establish an X2 interface. Moreover, in other embodiments of the invention, "first", "second" are not themselves used to define a technical solution.

Step 202: If the first HeNB and the second HeNB are located under the same HeNB GW, the first HeNB establishes an X2 interface between the first HeNB and the second HeNB.

The first HeNB establishes an X2 interface between the first HeNB and the second HeNB, where the HeNB GW to which the first HeNB belongs acquires the TNL address or IP of the second HeNB from any one of the MME and the second HeNB. The first HeNB receives the TNL address or the IP address sent by the HeNB GW to which the first HeNB belongs; the first HeNB establishes an X2 interface between the first HeNB and the second HeNB according to the TNL address or the IP address.

Preferably, the method further includes: performing, by the first HeNB, a cell handover according to the established X2 interface, where the cell handover is used to switch the first HeNB subordinate UE to the second HeNB.

Different from the prior art, in this embodiment, before the first HeNB establishes an X2 interface with the second HeNB, it is determined whether the first HeNB and the second HeNB are located under the same HeNB GW, if the first HeNB and the second HeNB Located under the same HeNB GW, the first HeNB establishes an X2 interface between the first HeNB and the second HeNB.

On the other hand, if the first HeNB and the second HeNB are not located under the same HeNB GW, the first HeNB may further determine whether to establish an X2 interface with the second HeNB according to other network conditions.

Regardless of other network conditions, preferably, if the TAI of the second HeNB is not in the obtained TAI list, the first HeNB does not establish an X2 interface between the first HeNB and the second HeNB. There is no X2 interface at this time, and the first HeNB can perform the switching operation by using the S1 interface.

It can be seen from the above embodiment that before establishing an X2 interface between two HeNBs, first two Whether the HeNB is located under the same gateway, and then determines whether to establish an X2 interface. When two HeNBs are located under the same gateway, an X2 interface can be established, and the X2 interface is used to perform operations related to the handover process, thereby avoiding the failure to implement The waste of network resources caused by establishing an X2 interface during handover. Embodiment 2

This embodiment also provides a method for implementing cell handover. That is, when it is determined that the first HeNB and the second HeNB are located under the same HeNB GW, the first HeNB switches the first HeNB subordinate UE to the second HeNB. Referring to FIG. 3, which is a flowchart of an embodiment of a method for implementing cell handover in the present application, including the following steps:

Step 301: Determine whether the first HeNB and the second HeNB are located under the same HeNB GW. Step 302: If the first HeNB and the second HeNB are located under the same HeNB GW, the first HeNB switches the first HeNB subordinate UE by using the X2 interface. To the second HeNB.

For the execution of the foregoing step 301, refer to step 201 in the first embodiment, which is not repeatedly described in this embodiment.

In this embodiment, if the X2 interface that has been established between the first HeNB and the second HeNB determines whether the two HeNBs are located under the same gateway, whether to perform handover, when the first HeNB and the second HeNB are located in the same gateway. Perform a switch when it is below. If the X2 interface is not established between the first HeNB and the second HeNB, determining whether the two HeNBs are located under the same gateway determines whether to establish an X2 interface, and establishing an X2 interface when the first HeNB and the second HeNB are located under the same gateway. That is, if the first HeNB and the second HeNB are located under the same HeNB GW in step 302, the first HeNB establishes an X2 interface between the first HeNB and the second HeNB, and then switches the first HeNB subordinate UE to the second. HeNB.

It should be noted that, when the first HeNB and the second HeNB are not located under the same HeNB GW, the first HeNB may further determine, according to other network conditions, whether to switch the first HeNB subordinate UE to the second HeNB.

Preferably, the first HeNB does not switch the first HeNB subordinate UE to the second HeNB if the first HeNB and the second HeNB are not located under the same HeNB GW, regardless of other network conditions.

It can be seen from the above embodiment that the method of establishing an interface between base stations can be applied to 'j, zone switching That is, before the cell handover, the X2 interface is established according to the method of establishing an interface between the base stations, and then the cell handover is implemented according to the established X2 interface. Of course, if an interface is established between the base stations, it can also be determined whether the two HeNBs are located under the same gateway to determine whether to perform handover. When the two HeNBs are located under the same gateway, the handover can be performed, and the two HeNBs are prevented from being located under different gateways. When the UE identifier received by the MME cannot be identified, the possibility of handover failure can be reduced. Embodiment 3

The method for establishing an interface between the base stations is described by using the first HeNB to obtain the TAI list from the HeNB GW to which the first HeNB belongs, and determining whether the TAI of the second HeNB is in the obtained TAI list. Please refer to FIG. 4, which is a signaling flowchart of establishing an interface between base stations according to the present application, including the following steps:

Step 401: The HeNB A requests the HeNB GW1 to which it belongs to obtain the TAI list of the HeNB GW1.

For example, specifically, HeNB A may send an SI message or an X2 message to the HeNB GW1 to which it belongs, requesting to obtain a TAI list of the HeNB GW1.

It should be noted that step 401 is an optional step, and step 402 may be directly performed, that is, the TeNB list information of the HeNB GW1 is directly sent by the HeNB GW1 to the HeNB A.

Step 402: The HeNB GW1 sends the TAI list information of the HeNB GW1 to the HeNB A in response to the request of the HeNB A;

For example, specifically, HeNB A may send an S 1 or X 2 message request to HeNB GW1 to obtain

When the HeNB GW1 has a TAI list, the HeNB GW1 transmits an SI or X2 message carrying the TAI list of the HeNB GW1 to the HeNB A.

Step 403: The HeNB A determines whether the TAI of the HeNB B is in the obtained TAI list. Step 404: If the TAI of the HeNB B is in the obtained TAI list, the HeNB A establishes an X2 interface between the HeNB A and the HeNB B.

If the TAI of the second HeNB is in the obtained TAI list, it indicates that the second HeNB and the first HeNB belong to one HeNB GW. Further, the first HeNB establishes an X2 interface between the first HeNB and the second HeNB.

It should be noted that when the TAI of the HeNB B is not in the TAI of the HeNB GW1 to which the HeNB A belongs. In the list, HeNB A can further determine whether to establish an X2 interface with HeNB B according to other network conditions.

Without considering other network conditions, preferably, if the TAI of HeNB B is not in the obtained TAI list, HeNB A does not establish an X2 interface between HeNB A and HeNB B.

It can be seen from the above embodiment that before the X2 interface is established between the two HeNBs, the first HeNB determines whether the TIAs of the second HeNB are in the TAI list of the HeNB GW to which the first HeNB belongs, and whether the two HeNBs are located in the same gateway. The result of the next step is to determine whether to establish an X2 interface according to the judgment result. When the two HeNBs are located under the same gateway, an X2 interface can be established, and the X2 interface is used to perform operations related to the process such as handover, thereby avoiding waste of resources. Embodiment 4

The method for establishing an interface between the base stations is described below by using the HeNB GW to which the first HeNB belongs to determine whether the HeNB A and the HeNB B are in the same HeNB GW. Specifically, the HeNB GW to which the first HeNB belongs may be determined by determining whether the TAI of the second HeNB is in its own TAI list, and the HeNB GW to which the first HeNB or the first HeNB belongs acquires the TNL address or IP address of the second HeNB as an example. A method of establishing an interface between base stations. Please refer to FIG. 5 , which is another signaling flowchart of establishing an interface between base stations, including the following steps:

Step 501: The HeNB A sends an eNB configuration transfer message carrying the TAI of the HeNB B to the HeNB GW1 to which the HeNB A belongs, and requests to obtain the TNL address or IP address of the HeNB B.

Specifically, the eNB configuration transfer message includes the TAI and eNB ID information of the HeNB B.

Step 502: The HeNB GW1 forwards the received eNB configuration transfer message to the MME.

Step 503: The MME according to the content of the received eNB configuration transfer message

The HeNB GW to which the HeNB B belongs sends an MME configuration transfer message requesting to obtain the TNL address or IP address of the HeNB B;

In this embodiment, the HeNB GW to which the HeNB B belongs is the HeNB GW1. As shown in FIG. 5, the HeNB GW to which the HeNB B belongs may be other HeNB GWs. Step 504: The HeNB GW1 to which the HeNB B belongs forwards the received MME configuration transfer message to the HeNB B.

Step 505: The HeNB B sends an eNB configuration transfer message carrying its own TNL address or IP address to the HeNB GW1 to which the HeNB B belongs.

Step 506: The HeNB GW1 sends the received eNB configuration transfer message carrying the TNL address or IP address of the HeNB B to the MME;

Step 507: The MME sends an MME configuration transfer message carrying the TNL address or IP address of the HeNB B to the HeNB GW1 to which the HeNB A belongs according to the content of the received eNB configuration transfer message;

Step 508: The HeNB GW1 sends an eNB configuration transfer message carrying the TNL address or the IP address of the HeNB B to the HeNB A, and the MME configuration transfer message includes an indication bit for indicating whether the TAI of the HeNB B is in its own TAI. In the list; or used to indicate whether HeNB A and HeNB B are in the same HeNB GW.

Step 509: The HeNB A determines whether to establish an X2 interface with the HeNB B according to the indication in the message.

When the message indicates that the TAI of the HeNB B is in the TAI list of the HeNB GW itself to which the HeNB A belongs, the HeNB A establishes an X2 interface between the HeNB A and the HeNB B.

When the message indicates that the TAI of the HeNB B is not in the TAI list of the HeNB GW itself to which the HeNB A belongs, the HeNB A may further determine whether to establish an X2 interface with the HeNB B according to other network conditions.

It should be noted that the above steps 502-507 are processes for acquiring the TNL address or IP address of the HeNB B by the HeNB GW1 to which the HeNB A belongs. After the HeNB GW1 to which the HeNB A belongs receives the eNB configuration transfer message of the TAI carrying the HeNB B, the HeNB GW1 may first determine whether the TAI of the HeNB B is in its own TAI list or determine the HeNB A. And whether the HeNB B is in the same HeNB GW. After the TAI of the HeNB B is in its own TAI list or it is determined that the HeNB A and the HeNB B are in the same HeNB GW, steps 502-507 are sequentially performed to obtain the TNL of the HeNB B. Address or IP address, and send HeNB A, so that HeNB A establishes an X2 interface according to the TNL address or IP address of HeNB B; conversely, when the TAI of HeNB B is not located in its own TAI list or judges that HeNB A and HeNB B are not in the same HeNB GW, then Steps 502-507 are not performed, and an eNB configuration transfer message is directly sent to HeNB A, and the message indicates that the TAI of HeNB B is not in its own TAI list or that HeNB A and HeNB B are not in the same HeNB GW. Please refer to FIG. 6, which is another signaling flowchart of establishing an interface between base stations according to the present application. As shown in FIG. 6, after the HeNB GW1 to which the HeNB A belongs receives the eNB configuration transfer message of the TAI carrying the HeNB B, the HeNB B determines whether the TAI of the HeNB B is in its own TAI list or determines the HeNB A and the HeNB. Whether B is in the same HeNB GW, when the TAI of HeNB B is not located in its own TAI list or judges that HeNB A and HeNB B are not in the same HeNB GW, directly sends an eNB configuration transfer message to HeNB A, and indicates in the message The TAI of HeNB B is not in its own TAI list.

It can be seen from the foregoing embodiment that before the X2 interface is established between the two HeNBs, the HeNB to which the first HeNB belongs determines whether the two HeNBs are located under the same gateway by determining whether the TAI of the second HeNB is in the TAI list of the second HeNB. Then, the first HeNB is notified to the first HeNB, so that the first HeNB determines whether to establish an X2 interface according to the determination result, and when the two HeNBs are located under the same gateway, an X2 interface can be established, and the X2 interface is used to perform processes related to handover, etc. Operation can avoid waste of resources.

Certainly, the HeNB GW may determine, by other manners, that the HeNB GW to which the first HeNB belongs determines whether the first HeNB and the second HeNB are on the same HeNB GW, for example, determining the second by determining the eNB ID or ECGI of the second HeNB. Whether the HeNB is in the HeNB GW to which the first HeNB belongs is not limited to the method in which the HeNB GW determines whether the second HeNB is under the HeNB GW to which the first HeNB belongs. Specifically, the determining method of the foregoing embodiment may be performed, where the HeNB GW may provide the first HeNB with related information of the HeNB GW subordinate HeNB, such as an eNB ID or an ECGI list, and the first HeNB determines the eNB ID of the second HeNB or Whether the ECGI corresponds to the information provided by the HeNB GW, if the identifier information corresponding to the second HeNB can be found in the list provided by the HeNB GW, the two HeNBs can be considered to be located under the same gateway. For other possible solutions, this embodiment also No restrictions. Embodiment 5

The HeNB GW to which the first HeNB belongs is used to determine whether the TAI of the second HeNB is in its own TAI list, and the HeNB GW to which the first HeNB belongs directly obtains the TNL address or IP address of the second HeNB from the second HeNB as an example. A method of establishing an interface between base stations. Please refer to FIG. 7, which is another signaling flowchart of establishing an interface between base stations according to the present application, including the following steps:

Step 701: The HeNB A sends an eNB configuration transfer message carrying the TAI of the HeNB B to the HeNB GW1 to which the HeNB A belongs, and requests to obtain the TNL address or IP address of the HeNB B.

Step 702: The HeNB GW1 sends an MME configuration transfer message to the HeNB B according to the content of the received eNB configuration transfer message, requesting the TNL address or IP address of the HeNB B to be obtained.

Step 703: HeNB B sends an eNB configuration transfer message carrying its own TNL address or IP address to HeNB GW1;

Step 704: The HeNB GW1 sends an MME configuration transfer message carrying the TNL address or the IP address of the HeNB B to the HeNB A, and the MME configuration transfer message includes an indication bit for indicating whether the TAI of the HeNB B is in its own TAI. Whether the list or whether HeNB A and HeNB B are in the same HeNB GW;

Step 705: The HeNB A determines whether to establish an X2 interface with the HeNB B according to the indication in the message.

When the message indicates that the TAI of the HeNB B is in the TAI list of the HeNB GW itself to which the HeNB A belongs, or indicates that the HeNB A and the HeNB B are in the same HeNB GW, the HeNB A establishes an X2 interface between the HeNB A and the HeNB B.

When the message indicates that the TAI of the HeNB B is not in the TAI list of the HeNB GW itself to which the HeNB A belongs or indicates that the HeNB A and the HeNB B are not in the same HeNB GW, the HeNB A may further determine whether to establish an X2 with the HeNB B according to other network conditions. interface.

It should be noted that the foregoing steps 702-703 are obtained for the HeNB GW1 to which the HeNB A belongs. The process of the TNL address or IP address of HeNB B. After the HeNB GW1 to which the HeNB A belongs receives the eNB configuration transfer message of the TAI carrying the HeNB B, the HeNB GW1 may first determine whether the TAI of the HeNB B is in its own TAI list or determine the HeNB A. And whether the HeNB B is in the same HeNB GW. After determining that the TAI of the HeNB B is in its own TAI list or determining that the HeNB A and the HeNB B are in the same HeNB GW, the steps 702-703 are sequentially performed to obtain the HeNB B. The TNL address or IP address is sent to HeNB A, so that HeNB A establishes an X2 interface according to the TNL address or IP address of HeNB B; otherwise, when it is judged that the TAI of HeNB B is not located in its own TAI list or judges HeNB A and HeNB If the B is not in the same HeNB GW, the eNB configuration transfer message is sent to the HeNB A without performing the steps 702-703, and the TAI of the HeNB B is not in the TAI list.

For ease of understanding, the following example is used to illustrate that the MME may allocate an ID to the UE1 after the UE (represented by the UE1) accesses the base station, and is represented by the MME UE SIAP ID1. This representation is not used for limitation, but different MMEs are not associated with each other. Therefore, the IDs allocated by other MMEs for the own UE (represented by UE2) may be the same as the ID of UE1. For the sake of distinction, the original gateway (represented by gateway 1, for example, HeNB GW1) needs to generate its own UE ID, for example, when two MMEs are used. If the same MME UE S1AP ID is allocated to each terminal, the gateway 1 may generate the MME UE SIAP ID1-a and the MME UE SlAP ID1-b respectively to distinguish the IDs of the two different UEs. In summary, in the prior art, the gateway will process the ID assigned by the MME to generate its own new ID.

It is assumed that the gateway 1 will MME UE S1AP ID1 -a and MME UE S1AP corresponding to UE1 and UE2.

The ID1-b is respectively sent to the original base station (represented by the base station 1, for example, HeNB1) of the gateway 1 to complete the allocation of different UE identifiers. When UE1 needs to switch from base station 1 or is to be handed over to the target base station (represented by base station 2), any network station (gateway or base station, etc.) can determine whether base station 1 and base station 2 have the same gateway, and if not, switch The X2 interface establishment before the process or switching may not be performed. Because the MME UE S 1 AP ID 1 -a corresponding to UE1 is sent by the gateway 1 to the base station 1 and then forwarded to the base station 2, and is forwarded by the base station 2 to the gateway to which the base station 2 belongs (assuming that the gateway to which the base station 2 belongs is different from the gateway 1 at this time) Indicated by the gateway 2, and further forwarded to the MME. Since the MME UE S1AP ID1-a is not the ID originally delivered by the MME, the MME UE SIAP ID1-a cannot be identified by the MME, and the handover cannot be performed, and the handover is established. The X2 interface also wastes resources. When any network The station determines that the gateway to which the base station 2 belongs is also the gateway 1, that is, if the two base stations have the same gateway, the handover or establishment of the interface can be continued. This is because the gateway 1 generates the MME UE SlAP ID1-a by itself, so the gateway 1 has the ability to re-convert the MME UE S1AP ID1-a back to the MME identifiable MME UE S1AP ID1, so when the handover is expanded, The gateway 1 can send the MME UE S1AP ID1 to the MME, so that the MME performs subsequent operations such as path switch procedure.

It can be seen from the above implementation that before the X2 interface is established between the two HeNBs, the HeNB GW to which the first HeNB belongs determines whether the two HeNBs are located under the same gateway by determining whether the TAI of the second HeNB is in its own TAI list. As a result, the first HeNB is notified to the first HeNB, so that the first HeNB determines whether to establish an X2 interface according to the determination result, and when the two HeNBs are located under the same gateway, an X2 interface can be established, and the X2 interface is used to perform processes related to handover. The operation can avoid waste of resources. Embodiment 6

The embodiment of the present application further provides a method for implementing cell handover. For the handover scenario shown in FIG. 1, the HeNB1 transmits the MME UE S1AP ID allocated by the HeNB GW1 to the HeNB2 through the direct X2 interface, and the HeNB2 sends the MME UE SIAP ID to the HeNB GW2, and the HeNB GW2 continues the MME UE S1AP. After the ID is sent to the MME, the MME UE S1AP ID is allocated by the HeNB GW1. Therefore, the MME cannot identify the received MME UE S1AP ID. To ensure normal handover, the MME UE SIAP ID can be converted into a The identifier identified by the MME is converted into an identifier assigned by the original MME to the terminal. This embodiment provides a method for ensuring normal cell handover, and FIG. 8 is a flowchart of an embodiment of a method for implementing cell switching in the present application, including the following steps:

Step 801: The HeNB GW to which the second HeNB belongs receives the first MME UE SIAP ID sent by the second HeNB, where the first MME UE SIAP ID is allocated by the HeNB GW to which the first HeNB belongs to the UE.

For example, as shown in FIG. 1, on the S1 interface on the HeNB GW1-MME side, the MME allocates one MME UE SIAP ID1 for the UE subordinate to the HeNB1, and on the SI interface of the HeNB GW1 - HeNB1 side, the HeNB GW1 Redistributing one MME UE S1AP for the UEs subordinate to HeNB1 IDl-a, that is, when the HeNB GW1 receives the SI message sent by the MME through the SI interface on the HeNB GW1-MME side, the MME UE SIAP ID1 allocated by the MME included in the message is converted into the MME UE allocated by itself. SlAP IDl-a.

The HeNB1 sends the S1 message including the MME UE S1AP ID-a to the HeNB2 of the handover peer through the established X2 interface, and the HeNB2 forwards the message to the associated HeNB GW2.

Step 802: The HeNB GW to which the second HeNB belongs converts the first MME UE SIAP ID into a second MME UE SIAP ID allocated by the MME to the UE according to a preset mapping relationship.

The mapping between the MME UE SIAP ID1 allocated by the MME for the UE and the MME UE SIAP ID 1 -a allocated by the HeNB GW to which the first HeNB belongs is pre-set on the HeNB GW to which the second HeNB belongs. The HeNB GW to which the second HeNB belongs converts the received MME UE SIAP ID 1-a into an MME identifiable MME UE SIAP ID1 according to the mapping relationship, so that the MME UE SIAP ID1 can be identified.

For example, as shown in FIG. 1, after the HeNB GW2 to which the HeNB 2 belongs receives the MME UE S1AP ID1-a, the MME UE SIAP ID1-a is converted into the MME UE SlAP IDl according to the mapping relationship shown in the following table. In the following Table 1, the gateway can generate multiple IDs, such as MME UE SIAP ID la, MME UE SIAP ID 1-b, etc., based on the same MME UE S1AP ID 1 delivered by different MMEs.

Table 1

Step 803: The HeNB GW to which the second HeNB belongs sends the second MME UE SIAP ID to

The MME indicates to the MME that the UE that the handover has occurred.

It should be noted that, when the UE is handed over from the second HeNB to the first HeNB, the second MME UE SIAP allocated by the MME to the UE is also pre-configured on the HeNB GW to which the first HeNB belongs. The mapping between the ID and the third MME UE SIAP ID allocated by the HeNB GW to the UE by the HeNB, and the HeNB GW to which the first HeNB belongs converts the received third MME UE SIAP ID into the MME according to the mapping relationship. The second MME UE SIAP ID allocated by the UE.

The two gateways in this embodiment may have the same mapping relationship, and the MME UE SIAP ID1 sent by the MME is received at the gateway 1, and the MME UE SIAP ID1-a is generated according to the mapping relationship, and sent to the subordinate base station 1, the base station. 1 MME UE SIAP ID1-a is forwarded to the gateway 2 through the base station 2, and the gateway 2 does not directly send the MME UE SIAP ID1-a that the MME cannot identify to the MME, but the MME UE SIAP based on the same mapping relationship as the gateway 1. The IDl-a is converted back to the MME UE SIAP ID1 and then handed over to the MME so that the base station can recognize this identity. The method shown in this embodiment can be performed simultaneously with the UE switching between two gateways, or at other appropriate times. Generally, the MME allocates the MME UE SIAP ID1 to the UE when the UE initially accesses the source base station 1. When the UE performs handover, the MME needs to know which UE needs to perform handover, so as to perform subsequent path change and transmit the UE that needs to be handed over. The path is switched to the target base station. Therefore, the target base station or the gateway 2 to which the target base station belongs sends a message (for example, a path switch request message) to the MME. The MME UE SIAP ID1 allocated by the MME is the UE indicating the handover to the MME, so that the MME can know which UE performs the handover. The MME can change the UE data transmission target base station (base station 2) accordingly.

It can be seen from the foregoing embodiment that if the two base stations are not under the same gateway and an interface is established between the two base stations, in order to ensure the normal completion of the handover, the MME is stored in the gateway to which the two base stations belong respectively. The mapping relationship between the MME UE SIAP ID allocated by the UE and the MME UE SIAP ID allocated by the handover peer to the UE, so that when any one of the two gateways receives the MME UE SIAP ID assigned by the handover peer to the UE, According to the mapping relationship, the MME UE SIAP ID allocated by the MME for the UE, that is, the MME UE SIAP ID that the MME can identify, can be obtained, thereby ensuring the normal completion of the handover. Example 7

The embodiment of the present application further provides a method for implementing cell handover. Please refer to FIG. 9, which is a flowchart of another embodiment of a method for implementing cell handover, including the following steps:

Step 901: The HeNB GW to which the first HeNB belongs receives the first MME UE SIAP ID allocated by the first MME to the UE, and determines whether the first MME UE SIAP ID is different from the first The MME UE SIAP ID assigned to the UE by any other MME outside the MME is the same; for example, the HeNB GW1 is simultaneously connected to the MME1 and the MME2, and the HeNB to which the HeNB1 belongs

When the MME1 receives the MME UE SIAP ID1 allocated by the UE1 served by the HeNB1, the GW1 determines whether the MME UE SIAP IDL is allocated to the other MMEs connected to the HeNB GW1. Step 902: If the first MME UE SIAP ID and The MME UE SIAP ID assigned to the UE by any other MME other than the first MME is the same, and the first HeNB belongs to

The HeNB GW requests the first MME to re-allocate the first MME UE SIAP ID to the UE; for example, if the MME 2 has allocated the MME UE SIAP ID1 to other terminals in the connection between the HeNB GW1 and the MME 2, that is, the MME is the MME. When the UE SIAP ID1, the HeNB GW1 to which the HeNB1 belongs requests the MME1 to re-allocate an MME UE SIAP ID to the UE until the MME1 is re-established.

The MME UE SIAP ID allocated by the UE is different from the MME UE SIAP ID allocated by the MME2 to the UE.

Step 903: The second HeNB provides the first MME UE SIAP ID to the first MME, to indicate to the first MME that the UE that has the handover occurs.

Preferably, the method further includes: if the first MME UE SIAP ID is different from the MME UE SIAP ID allocated to the UE by any other MME except the first MME, the HeNB to which the first HeNB belongs The GW sends the first MME UE SIAP ID to the second HeNB through the first HeNB.

In this embodiment, the original gateway may determine whether the MME UE SIAP IDs of different MMEs are in conflict, and when the newly allocated IDs already exist, re-allocate to ensure that the MME UE SIAP IDs allocated by multiple MMEs are different, and the gateway The received MME UE SIAP ID can be directly forwarded to the subordinate base station without generating the MME UE SIAP ID by itself. For example, the gateway 1 receives the MME UE SIAP ID1 allocated by the MME, and after receiving the IDs assigned by other MMEs, ensures that the other IDs do not conflict with the MME UE SIAP ID1, and forwards the MME UE SIAP ID1 directly to the subordinate original base station. . When the UE is handed over, the MME UE SIAP ID1 is sequentially forwarded to the target base station, the gateway to which the target base station belongs, and the MME to indicate the handover UE to the MME. Because the gateway of this embodiment is different from the prior art, the IDs of all the MMEs are different through the decision process, so it is not necessary to generate its own ID, that is, the MME UE SIAP ID1 does not need to be converted into the MME UE SIAP ID1-a. In the handover scenario, the MME UE SIAP ID1 can be directly forwarded to the MME through multiple forwarding, and the MME can directly identify MME UE SIAP ID1.

It can be seen from the foregoing embodiment that if two base stations are not under the same gateway and an interface is established between the two base stations, in order to ensure the normal completion of the handover, different MMEs need to ensure that the MMEs allocated to the same UE of the subordinate belong to the same UE. The UE SIAP ID is different. When the gateway to which the base station belongs finds that at least two MMEs allocate the same MME UE SIAP ID to the subordinate UE, the MME is requested to re-allocate the MME UE SIAP ID. The MME UE SIAP ID assigned by the MME is sent to the base station gateway of the handover peer, and the MME UE SIAP ID that can be identified by the MME is directly sent to the base station gateway of the handover peer, thereby ensuring that the gateway to which the base station belongs does not perform identity conversion. The normal completion of the switch. Example eight

Embodiments of the present invention also provide an apparatus for establishing an interface between base stations. Referring to FIG. 10, which is a structural diagram of an implementation of an apparatus for establishing an interface between base stations according to the present application, including: a determining unit 1001 and an establishing unit 1002. The internal structure and connection relationship will be further described below in conjunction with the working principle of the device.

The determining unit 1001 is configured to determine whether the first HeNB and the second HeNB are located under the same HeNB GW;

The establishing unit 1002 is configured to establish an X2 interface between the first HeNB and the second HeNB if the first HeNB and the second HeNB are located under the same HeNB GW.

Referring to FIG. 11 , which is a schematic structural diagram of a determining unit in the present application, the method includes: obtaining a subunit 10011, configured to obtain a TAI list of a HeNB GW to which the first HeNB belongs; and a first determining subunit 10012, configured to determine Whether the TAI of the second HeNB is in the obtained TAI list;

The first determining subunit 10013 is configured to determine that the first HeNB and the second HeNB are located under the same HeNB GW if the TAI of the second HeNB is in the obtained TAI list.

Alternatively, the determining unit 1001 includes: an indication receiving unit, configured to receive an indication message that the first HeNB and the second HeNB are located under the same HeNB GW, and determine, according to the indication message that the first HeNB and the second HeNB are located in the same HeNB Under GW.

Please refer to FIG. 12 , which is a schematic structural diagram of a unit established in the present application, including: An address obtaining subunit 10021, configured to acquire a TNL address or an IP address of the second HeNB from any one of the MME and the second HeNB;

The receiving subunit 10022 is configured to receive the TNL address or an IP address sent by the address obtaining subunit.

The establishing subunit 10023 is configured to establish an X2 interface between the first HeNB and the second HeNB according to the TNL address or the IP address.

Preferably, the device further includes:

And a switching unit, configured to implement cell handover according to the established X2 interface, where the cell handover is used to switch the first HeNB subordinate UE to the second HeNB.

It can be seen from the above embodiment that before establishing an X2 interface between two HeNBs, first two

Whether the HeNB is located under the same gateway, and then determines whether to establish an X2 interface. When two HeNBs are located under the same gateway, an X2 interface can be established, and the X2 interface is used to perform operations related to the handover process, thereby avoiding the failure to implement The waste of network resources caused by establishing an X2 interface during handover. Example nine

The embodiment of the invention further provides an apparatus for implementing cell handover. Referring to FIG. 13, which is a structural diagram of an implementation of an apparatus for implementing cell handover, the method includes: a determining unit 1001 and a switching unit 1003. The internal structure and connection relationship will be further described below in conjunction with the working principle of the device.

The determining unit 1001 is configured to determine whether the first HeNB and the second HeNB are located in the same HeNB.

Under GW;

The switching unit 1003 is configured to: if the first HeNB and the second HeNB are located under the same HeNB GW, the first HeNB uses the X2 interface to switch the first HeNB subordinate UE to the second HeNB.

The determining unit 1001 includes: an obtaining subunit, configured to obtain a TAI list of the HeNB GW to which the first HeNB belongs; and a first determining subunit, configured to determine whether the TAI of the second HeNB is in the obtained TAI list; a subunit, configured to determine that the first HeNB and the second HeNB are located under the same HeNB GW if the TAI of the second HeNB is in the obtained TAI list.

Alternatively, the determining unit 1001 includes: an indication receiving unit, configured to receive an indication message indicating that the first HeNB and the second HeNB are located under the same HeNB GW, and determine the first One HeNB and the second HeNB are located under the same HeNB GW.

It can be seen from the foregoing embodiment that the method for establishing an interface between the base stations can be applied to the 'j, zone switch, that is, before the cell handover, the X2 interface is established according to the method for establishing an interface between the base stations, and then The established X2 interface implements cell handover. Of course, if an interface is established between the base stations, it can also be determined whether the two HeNBs are located under the same gateway to determine whether to perform handover. When the two HeNBs are located under the same gateway, the handover can be performed, and the two HeNBs are prevented from being located under different gateways. When the UE identifier received by the MME cannot be identified, the possibility of handover failure can be reduced. Example ten

The embodiment of the invention further provides an apparatus for implementing cell handover. Referring to FIG. 14, which is a structural diagram of another implementation of an apparatus for implementing cell handover, the method includes: an identifier receiving unit 1401, an identifier converting unit 1402, and a first switching indicating unit 1403. The internal structure and connection relationship will be further described below in conjunction with the working principle of the device.

The identifier receiving unit 1401 is configured to receive the first MME UE SIAP ID sent by the second HeNB, where the first MME UE SIAP ID is allocated by the HeNB GW to which the first HeNB belongs to the UE;

The identifier conversion unit 1402 is configured to convert the first MME UE SIAP ID into a second MME UE SIAP ID that can be identified by the MME according to a preset mapping relationship;

The first handover indication unit 1403 is configured to send the second MME UE SIAP ID to the MME, to indicate to the MME that the UE that the handover occurs.

It can be seen from the foregoing embodiment that if the two base stations are not under the same gateway and an interface is established between the two base stations, in order to ensure the normal completion of the handover, the MME is stored in the gateway to which the two base stations belong respectively. The mapping relationship between the MME UE SIAP ID allocated by the UE and the MME UE SIAP ID allocated by the handover peer to the UE, so that when any one of the two gateways receives the MME UE SIAP ID assigned by the handover peer to the UE, The MME UE SIAP ID allocated by the MME for the UE, that is, the MME UE SIAP ID that the MME can identify, can be obtained according to the mapping relationship, thereby ensuring the normal completion of the handover. Embodiment 11 The embodiment of the invention further provides an apparatus for implementing cell handover. Referring to FIG. 15, which is a structural diagram of another implementation of an apparatus for implementing cell handover according to the present application, the method includes: an identifier determining unit 1501, an identifier sending unit 1502, and a second switching indicating unit 1503. The internal structure and connection relationship will be further described below in conjunction with the working principle of the device.

The identifier determining unit 1501 is configured to receive the first MME UE that is allocated by the first MME to the UE.

a SIAP ID, determining whether the first MME UE SIAP ID is the same as an MME UE SIAP ID allocated to the UE by any other MME except the first MME;

The identifier sending unit 1502 is configured to: if the first MME UE SIAP ID is different from the MME UE SIAP ID allocated to the UE by any other MME except the first MME, the first MME UE SIAP The ID is sent to the second handover indication unit 1503 by the first HeNB;

The second handover indication unit 1503 is configured to provide the first MME UE SIAP ID to the first MME, to indicate to the first MME that the UE that has the handover occurs.

Preferably, please refer to FIG. 16, which is a structural diagram of another implementation of an apparatus for implementing cell handover according to the present application. The device further includes: a requesting unit 1504, configured to: if the first MME UE SIAP ID is the same as the MME UE SIAP ID allocated to the UE by any other MME except the first MME, to the An MME requests to re-allocate the first MME UE SIAP ID to the UE.

It can be seen from the foregoing embodiment that if two base stations are not under the same gateway and an interface is established between the two base stations, in order to ensure the normal completion of the handover, different MMEs need to ensure that the MMEs allocated to the same UE of the subordinate belong to the same UE. The UE SIAP ID is different. When the gateway to which the base station belongs finds that at least two MMEs allocate the same MME UE SIAP ID to the subordinate UE, the MME is requested to re-allocate the MME UE SIAP ID. The MME UE SIAP ID assigned by the MME is sent to the base station gateway of the handover peer, and the MME UE SIAP ID that can be identified by the MME is directly sent to the base station gateway of the handover peer, thereby ensuring that the gateway to which the base station belongs does not perform identity conversion. The normal completion of the switch.

The embodiment of the present invention further provides a communication system as shown in FIG. 1, wherein a new function can be introduced at a certain station, such as determining whether different HeNBs are in the same gateway as shown in the previous embodiment at the HeNB. The following functions can also be introduced in the gateway to decide whether to establish a UE for implementation. The switched X2 interface or whether to initiate the handover; as shown in the foregoing embodiment, the mapping relationship is saved in the gateway, and the ID generated by the original HeNB is converted into the identifiable ID sent by the MME when the UE is indicated to the MME. In order to facilitate the successful handover, the ID conflict may be resolved when the MME allocates the UE ID, and the method for determining whether the IDs allocated by different MMEs are duplicated according to the foregoing embodiment is not limited in this embodiment.

When it is to be noted, the names of the various network nodes of the present embodiment are not intended to limit the scope of protection, and should be given the broadest meaning based on the understanding of those skilled in the art. For example, the HeNB can be understood as a small base station, which includes not only a home base station on a chivalry, but also other types of small sites, such as pico, femto, etc., as long as the structure of the network topology is similar to that of FIG. 1, and a similar MME is adopted. The manner in which the terminal assigns an ID can be implemented by the method or device of this embodiment. In this embodiment, the UE should be understood as a terminal that accesses the HeNB, and its type is not limited, and may be a mobile phone, a fixed phone, an ipad, or the like. Of course, the various message names in this embodiment are not used for limitation. The message names in this embodiment are only for easy understanding.

It should be noted that those skilled in the art can understand that all or part of the processes in the foregoing embodiments can be implemented by a computer program to instruct related hardware, and the program can be stored in a computer readable storage. In the medium, the program, when executed, may include the flow of an embodiment of the methods as described above. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

The foregoing provides a method and an embodiment for establishing an interface between base stations and implementing cell handover according to the present invention. The description of the above embodiments is only for helping to understand the method and core idea of the present invention; The present invention is not limited by the scope of the present invention, and the details of the present invention are not limited by the scope of the present invention.

Claims

Rights request

A method for establishing an interface between base stations, comprising:

Determining whether the first HeNB and the second HeNB are located under the same HeNB GW;

If the first HeNB and the second HeNB are located under the same HeNB GW, the first HeNB establishes an X2 interface between the first HeNB and the second HeNB.

The method according to claim 1, wherein the determining whether the first HeNB and the second HeNB are located under the same HeNB GW includes:

The first HeNB obtains a TAI list of the HeNB GW to which the first HeNB belongs;

Determining, by the first HeNB, whether the TAI of the second HeNB is in the obtained TAI list;

If the TAI of the second HeNB is in the obtained TAI list, it is determined that the first HeNB and the second HeNB are located under the same HeNB GW.

The method according to claim 2, wherein the obtaining, by the first HeNB, the TAI list of the HeNB GW to which the second HeNB belongs includes:

The first HeNB acquires a TAI list of the HeNB GW to which the first HeNB belongs from the OAM, the O&M, the EMS, the NMS, or the HeNB GW to which the first HeNB belongs.

The HeNB GW to which the first HeNB belongs determines whether the first HeNB and the second HeNB are located under the same HeNB GW;

If the first HeNB and the second HeNB are located under the same HeNB GW, the HeNB GW of the first HeNB sends an indication message indicating that the first HeNB and the second HeNB are located under the same HeNB GW to the first HeNB.

The method according to claim 4, wherein the determining, by the HeNB GW to which the first HeNB belongs, whether the first HeNB and the second HeNB are located under the same HeNB GW includes:

The HeNB GW to which the first HeNB belongs determines whether the TAI of the second HeNB is in its own TAI list;

If the TAI of the second HeNB is in the TAI list of the HeNB GW to which the first HeNB belongs, it is determined that the first HeNB and the second HeNB are located under the same HeNB GW.

The method according to any one of claims 1 to 5, wherein the first HeNB establishes an X2 interface between the first HeNB and the second HeNB, including:

The HeNB GW to which the first HeNB belongs acquires the TNL address or IP address of the second HeNB from any one of the MME and the second HeNB;

Receiving, by the first HeNB, the TNL address sent by the HeNB GW to which the first HeNB belongs or

IP address;

The first HeNB establishes an X2 interface between the first HeNB and the second HeNB according to the TNL address or the IP address.

The method according to any one of claims 1 to 5, wherein the method further comprises:

The first HeNB implements cell handover according to the established X2 interface, where the cell handover is used to switch the first HeNB subordinate UE to the second HeNB.

8. A method for implementing cell handover, which is characterized by:

If the first HeNB and the second HeNB are located under the same HeNB GW, the first HeNB switches the first HeNB subordinate UE to the second HeNB by using the X2 interface.

The method according to claim 8, wherein the determining whether the first HeNB and the second HeNB are located under the same HeNB GW includes:

The method according to claim 9, wherein the obtaining, by the first HeNB, the TAI list of the HeNB GW to which the second HeNB belongs includes:

The HeNB GW to which the first HeNB belongs determines whether the first HeNB and the second HeNB are located in the same Under the HeNB GW;

The method according to claim 11, wherein the first HeNB belongs to a HeNB.

The GW determines whether the first HeNB and the second HeNB are located under the same HeNB GW, including:

A method for implementing cell handover, which is characterized by:

The HeNB GW to which the second HeNB belongs receives the first MME UE SIAP ID sent by the second HeNB, and the first MME UE SIAP ID is allocated by the HeNB GW to which the first HeNB belongs to the UE;

The HeNB GW to which the second HeNB belongs converts the first MME UE SIAP ID into a second MME UE SIAP ID that can be identified by the MME according to a preset mapping relationship;

The HeNB GW to which the second HeNB belongs sends the second MME UE SIAP ID to the MME to indicate to the MME that the UE that has the handover occurs.

A method for implementing cell handover, which is characterized by:

The HeNB GW to which the first HeNB belongs receives the first MME allocated by the first MME to the UE.

a UE SIAP ID, determining whether the first MME UE SIAP ID is the same as an MME UE SIAP ID allocated to the UE by any other MME except the first MME;

If the first MME UE SIAP ID is different from the MME UE SIAP ID assigned to the UE by any other MME other than the first MME, the HeNB GW to which the first HeNB belongs shall be the first MME UE SIAP Sending, by the first HeNB, the ID to the second HeNB;

The second HeNB provides the first MME UE SIAP ID to the first MME, to indicate to the first MME that the UE that has the handover occurs.

The method according to claim 14, further comprising: If the first MME UE SIAP ID and any other than the first MME

The MME UEs assigned to the UEs have the same SIAP ID, and the HeNB GW to which the first HeNB belongs requests the first MME to re-allocate the first MME UE SIAP ID to the UE.

16. An apparatus for establishing an interface between base stations, comprising:

a determining unit, configured to determine whether the first HeNB and the second HeNB are located under the same HeNB GW;

And an establishing unit, configured to establish an X2 interface between the first HeNB and the second HeNB if the first HeNB and the second HeNB are located under the same HeNB GW.

The device according to claim 16, wherein the determining unit comprises: an obtaining subunit, configured to obtain a TAI list of a HeNB GW to which the first HeNB belongs; and a first determining subunit, configured to determine the second Whether the TAI of the HeNB is in the obtained TAI list; the first determining subunit is configured to determine that the first HeNB and the second HeNB are located under the same HeNB GW if the TAI of the second HeNB is in the obtained TAI list.

The device according to claim 16, wherein the determining unit comprises: an indication receiving unit, configured to receive an indication message indicating that the first HeNB and the second HeNB are located under the same HeNB GW, according to the indication The message determines that the first HeNB and the second HeNB are located under the same HeNB GW.

The apparatus according to any one of claims 16 to 18, wherein the establishing unit comprises:

An address obtaining subunit, configured to acquire a TNL address or an IP address of the second HeNB from any one of the MME and the second HeNB, and establish a subunit, configured to establish, according to the TNL address or the IP address, the first HeNB and the The X2 interface between the second HeNBs.

The apparatus according to any one of claims 16 to 18, wherein the apparatus further comprises:

The port implements cell handover, and the cell handover is used for

+ a determining unit, configured to determine whether the first HeNB and the second HeNB are located under the same HeNB GW;

The switching unit is configured to switch the first HeNB subordinate UE to the second HeNB by using the X2 interface, if the first HeNB and the second HeNB are located under the same HeNB GW.

The device according to claim 21, wherein the determining unit comprises: a obtaining subunit, configured to obtain a TAI list of the HeNB GW to which the first HeNB belongs; and a first determining subunit, configured to determine the second Whether the TAI of the HeNB is in the obtained TAI list; the first determining subunit is configured to determine that the first HeNB and the second HeNB are located under the same HeNB GW if the TAI of the second HeNB is in the obtained TAI list.

The device according to claim 21, wherein the determining unit comprises: an indication receiving unit, configured to receive that the first HeNB and the second HeNB are located in the same HeNB

The indication message under the GW determines that the first HeNB and the second HeNB are located under the same HeNB GW based on the indicated indication message.

24. A device for implementing cell handover, comprising:

An identifier receiving unit, configured to receive a first MME UE SIAP ID sent by the second HeNB, where the first MME UE SIAP ID is allocated by the HeNB GW to which the first HeNB belongs to the UE, and an identifier conversion unit, configured to The preset mapping relationship converts the first MME UE SIAP ID into a second MME UE SIAP ID that can be identified by the MME;

And a first handover indication unit, configured to send the second MME UE SIAP ID to the MME, to indicate to the MME that the UE that the handover occurs.

25. A device for implementing cell handover, comprising:

An identifier determining unit, configured to receive a first MME UE SIAP ID that is allocated by the first MME to the UE, and determine whether the first MME UE SIAP ID is allocated to the UE by using any other MME except the first MME. The MME UE has the same SIAP ID;

And an identifier sending unit, configured to: if the first MME UE SIAP ID is different from an MME UE SIAP ID allocated to the UE by any other MME except the first MME, the first MME UE SIAP ID And sending, by the first HeNB, the second handover indication unit, the second handover indication unit, configured to provide the first MME UE SIAP ID to the first MME, to indicate to the first MME The UE that is handed over.

The device according to claim 25, wherein the device further comprises: a requesting unit, configured to: if the first MME UE SIAP ID and any other MME except the first MME are allocated to The MME UE SIAP ID of the UE is the same, to the first

The MME requests to re-allocate the first MME UE SIAP ID to the UE.