WO2015043292A1

WO2015043292A1 - X2 message notification method, home evolved nodeb, and x2 gateway

Info

Publication number: WO2015043292A1
Application number: PCT/CN2014/082418
Authority: WO
Inventors: 吴蕴璐; 黄莹; 高音
Original assignee: 中兴通讯股份有限公司
Priority date: 2013-09-25
Filing date: 2014-07-17
Publication date: 2015-04-02
Also published as: CN104469883A

Abstract

The present invention provides an X2 message notification method, a home evolved NodeB (HeNB), and an X2 gateway (GW). The method comprises the following steps: an HeNB receiving an X2 message of a X2 GW, the X2 message carrying a cause value used for indicating that the X2 message cannot be routed to a target NodeB; and the HeNB performing corresponding processing according to the cause value. By using the present invention, a cause that an X2 establishment request message cannot be routed to a target evolved NodeB (eNB) can be learned, and an HeNB can add a radio network layer identifier (RNL ID) and a transport network layer (TNL) address of the eNB to an X2 message sent to an X2 GW, so that the X2 GW stores a matching relationship between the RNL ID and the TNL address of the eNB, so as to ensure that the X2 establishment request message can be correctly routed to the target eNB subsequently.

Description

Method for X2 message notification and home base station, X2 gateway

Technical field

The present invention relates to an X2 message notification technology, and in particular, to a method for X2 message notification, and a home base station and an X2 gateway.

Background technique

The home base station is a small, low-power base station that is deployed as a dedicated resource for private users in private places such as homes, groups, companies, or schools, and is connected by cable, digital subscriber line (DSL), or fiber optic cable. The incoming device is connected to the carrier's core network. The main role of the home base station is to provide users with higher service rates and to reduce the cost of using high-rate services, while at the same time making up for the inadequate coverage of existing distributed cellular wireless communication systems. The advantages of the home base station include: low cost, easy to use (plug and play), low output power, saving the cost of the operator to set up and maintain the base station, and solving indoor coverage optimization.

Evolved home base station in Long Term Evolution (LTE) system

(HeNB, Home Evolved NodeB) The schematic diagram of the network architecture, as shown in Figure 1. The UE (User Equipment) under the HeNB accesses the evolved Home Evolved NodeB Access Network (HeNBAN) based on the associated air interface protocol. The HeNBAN is composed of a HeNB and an evolved Home Base Station Gateway (HeNB GW, Home Evolved NodeB Gateway). The functions supported by the HeNB are basically the same as those of the enhanced base station (eNB, evolved Node B), and only one cell is connected to one HeNB. The HeNB GW is an optional network element. The main functions of the HeNB GW are: relaying the UE-related S1 message, terminating the non-UE-related S1 message, and selecting the mobility management entity (MME, Mobility Management Entity) for the UE in the attaching process. The SI interface is an interface between the eUTRAN (Evolved Radio Access Network) and the CN Node (Core Network Node). The HeNB can directly connect to the Evolved Packet Core (EPC) through the S1 interface, where the HeNB passes the S1- The U interface is connected to a Serving Gateway (S-GW), and the HeNB is connected to the MME through an SI-MME interface. The HeNB may also connect to the EPC through the HeNB GW, where the S1-U interface may terminate at the HeNB GW or terminate at the EPC, and the S1-MME interface passes through the HeNB GW to the EPC. EPC network elements include MME and S-GW. The MME is responsible for related functions such as bearer management and mobility management. The S-GW assumes functions such as data routing on the user side. In addition, the evolved home base station management system (HeMS, HeNB Management System) in FIG. 1 maintains and manages the HeNB, and configures and controls the HeNB according to the requirements of the operator, where the most important is to implement configuration functions for the HeNB, and the configured content. It includes verification of location information, parameters of the HeNB, parameters of the core network, parameters of the radio access network (RAN, Radio Access Network), and parameters of the radio frequency (RF, Radio Frequency). The Security Gateway (SeGW, Security Gateway) supports security-related functions in the network.

The HeNB only provides services for specific users, so the concept of Closed Subscriber Group (CSG) is introduced to perform access control. Each HeNB has a specific CSG attribute, including a closed member group identifier (CSG ID, CSG Identity) and an access mode. Here, three cell access modes are defined for the HeNB: Closed mode, only members of the closed member group identified by the corresponding CSG ID can access; Hybrid mode allows all UEs to be connected Incoming, but members of the closed member group with the corresponding CSG ID identifier enjoy higher priority; Open mode allows all UEs to access.

The 3rd Generation Partnership Project (3GPP, 3rd Generation Partnership Project)

Release 10 and Release 11 agree to permit the establishment of a direct X2 interface for handover purposes in the following scenarios: between the eNB and the HeNB in the open mode, between the HeNB in the eNB and the hybrid mode, and the HeNB in the source closed mode to the target eNB, The HeNB in the open mode and the HeNB in the open/hybrid mode, the HeNB in the source closed mode to the HeNB in the target open/hybrid mode, the HeNB in the source hybrid/closed mode with the same PLMN ID and CSG ID, to the HeNB in the target closed mode. The HeNB may be a direct X2 connection between the eNB and the HeNB, or may be an indirect X2 connection through a new functional entity X2 gateway (X2 Gateway, X2 GW) similar to the HeNB GW. During the discussion of the introduction of the X2 GW scheme, the source side routes the X2 message based on the target side's Radio Network Layer (RNL), and the (H)eNB uses the new registration message when it is powered on. The X2 GW establishes and maintains a matching relationship between the RNL ID and the Transport Network Layer (TNL) address, the IP address configuration of the X2 GW, and the HeNB, the eNB, or the TNL address discovery process to learn the X2 GW. The scheme of the IP address is used as a candidate for the X2 GW. The following problems exist in the candidate solution: Since the IP address of the X2 GW is configured for the HeNB, the HeNB After powering on, the new registration message can be used to establish and save the matching relationship between the RNL ID and the TNL address in the X2 GW. When the eNB obtains the TNL address of the X2 GW through the process of TNL address discovery, or when the eNB does not register with the X2 GW configured with the IP address after the eNB is powered on, if the HeNB discovers the cell served by the eNB, and It is decided to establish an indirect X2 connection with the eNB. The HeNB sends an X2 setup request message matching relationship with the RNL ID identifier of the target eNB, and the X2 GW cannot route the X2 setup request message to the target eNB. In order to solve the problem, after the HeNB learns that the X2 GW cannot route the X2 setup request message to the target eNB, the HeNB carries the RNL ID and the TNL address of the eNB in the X2 setup request message, the registration message, or the registration update message sent to the X2 GW. The proposal was presented. How the HeNB knows that the X2 GW is unable to route the X2 Setup Request message to the target eNB due to the absence of the RNL ID and TNL address matching relationship of the target eNB is a problem to be solved by the present invention.

When the HeNB and the HeNB or the eNB are connected to different X2 GWs, the HeNB cannot establish an indirect X2 interface through the X2 GW. How does the HeNB know that the HeNB or the eNB that is discovered is not connected to the same X2 GW, so as to avoid a large amount of row overhead caused by the HeNB continuously trying to establish an indirect X2 connection to the discovered HeNB or eNB is a problem to be solved by the present invention. .

The direct X2 interface between the eNB and the HeNB pair and the HeNB and the HeNB pair cannot be established at the same time and the X2 interface that establishes the proxy through the X2 GW. That is, a direct X2 interface is not established between an eNB and a HeNB pair, and a H2 pair is not established, and an X2 interface proxyed by the X2 GW is not established. As shown in FIG. 2, HeNB2 and HeNB3 intend to establish a proxy X2 connection through the X2 GW, and eNB 1 and HeNB2 intend to establish a proxy X2 connection through the X2 GW, but eNB 1 and HeNB 3 intend to establish a direct X2 connection. The IP address of the X2 GW is configured for the HeNB. Therefore, after the HeNB2 and the HeNB3 are powered on, a new registration message can be used to establish and maintain a matching relationship between the RNL ID and the TNL address in the X2 GW. At the same time, when the IP address of the X2 GW is configured for the eNB, after the eNB is powered on, a new registration message can be used to establish and save the matching relationship between the RNL ID and the TNL address in the X2 GW. A direct X2 connection is established between eNB 1 and HeNB 3. Considering the problem of reducing the number of TNL address discovery processes when designing the X2 GW scheme, how does HeNB3 obtain the TNL address of eNB1, thereby effectively Reducing the number of TNL address discovery processes is also a problem to be solved by this patent. Summary of the invention

The technical problem to be solved by the embodiments of the present invention is to provide a method for notifying the X2 message and the home base station and the X2 gateway, so as to know the reason why the X2 setup request message cannot be routed to the target eNB, or reduce the number of TNL address discovery processes.

In order to solve the above technical problems, the following technical solutions are used:

A method for notification of X2 messages, including:

The home base station receives an X2 message of the X2 gateway, where the X2 message carries a cause value indicating that the route cannot be routed to the target base station;

The home base station initiates a transport network layer address discovery process according to the cause value, to the

The X2 gateway sends the information required by the X2 gateway, or the home base station does not initiate an X2 setup request according to the cause value.

Optionally, the cause value includes: failing to be routed to the target base station because there is no matching relationship between the radio network layer identifier of the target base station and the transport network layer address;

The step of the home base station initiating a transport network layer address discovery process according to the cause value, and sending the information required by the X2 gateway to the X2 gateway includes:

The home base station initiates a transport network layer address discovery process, and acquires a transport network layer address of the target base station;

The home base station sends an X2 message to the X2 gateway, where the X2 message carries a radio network layer identifier of the target base station and an acquired transport network layer address of the target base station.

Optionally, the cause value includes: the home base station and the target base station are not connected to the same X2 gateway and cannot be routed to the target base station;

The step of the home base station not initiating the X2 establishment request according to the cause value includes: the home base station does not initiate the X2 establishment when rediscovering the cell served by the target base station and determining to establish an indirect X2 connection to the target base station request.

Optionally, the X2 message includes an X2 setup failure message. A home base station includes a receiving module and a processing module, where:

The receiving module is configured to: receive an X2 message of the X2 gateway, where the X2 message carries a cause value indicating that the route cannot be routed to the target base station;

The processing module is configured to: initiate a transport network layer address discovery process according to the cause value, send information required by the X2 gateway to the X2 gateway, or not initiate an X2 setup request.

The processing module is configured to initiate a transport network layer address discovery process according to the cause value, and send the information required by the X2 gateway to the X2 gateway: initiate a transport network layer address discovery process, and acquire the target base station Transmitting a network layer address; sending an X2 message to the X2 gateway, the X2 message carrying a radio network layer identifier of the target base station and an acquired transport network layer address of the target base station.

The processing module is configured to not initiate an X2 setup request according to the cause value according to the following manner: When the cell served by the target base station is rediscovered and an indirect X2 connection to the target base station is determined, an X2 setup request is not initiated.

Optionally, the X2 message received by the receiving module includes an X2 setup failure message.

A method for notification of X2 messages, including:

The home base station sends a first X2 message to the X2 gateway, where the first X2 message carries indication information that returns the address of the target base station;

The X2 gateway returns a second X2 message to the home base station, where the second X2 message carries a transport network layer address of the target base station saved by the X2 gateway or a transport network layer address that does not carry the target base station;

Receiving, by the home base station, the second X2 message, where the home base station is configured according to the second X2 Establishing a direct X2 connection with the target base station or initiating a transport network layer address discovery process. Optionally, when the second X2 message carries the transport network layer address of the target base station saved by the X2 gateway, the home base station establishes a direct X2 connection with the target base station or initiates transmission network layer address discovery. The step of the process includes: after obtaining the transport network layer address of the target base station, establishing a direct X2 connection with the target base station;

When the second X2 message does not carry the transport network layer address of the target base station, the step of the home base station establishing a direct X2 connection with the target base station or initiating a transport network layer address discovery process includes: initiating a transport network layer The address discovery process acquires a transport network layer address of the target base station.

Optionally, the first X2 message includes: an X2 setup request message,

The second X2 message includes: an X2 setup failure message.

A home base station includes a sending module, a receiving module, and a processing module, where:

The sending module is configured to: send a first X2 message to the X2 gateway, where the first X2 message carries indication information that returns a target macro base station address;

The receiving module is configured to: receive a second X2 message returned by the X2 gateway, where the second X2 message carries a transport network layer address of the target macro base station saved by the X2 gateway or does not carry the target macro base station Transport network layer address;

The processing module is configured to: establish a direct X2 connection with the target base station or initiate a transport network layer address discovery process according to the second X2 message.

Optionally, the processing module is configured to establish a direct X2 connection with the target base station or initiate a transport network layer address discovery process according to the second X2 message according to: when the second X2 message carries the X2 When the home network base station obtains the transport network layer address of the target base station, the home base station establishes a direct X2 connection with the target base station; when the second X2 message is not carried When the target base station transmits the network layer address, the home base station initiates a transport network layer address discovery process, and acquires a transport network layer address of the target base station.

Optionally, the first X2 message includes: an X2 setup request message, The second X2 message includes: an X2 setup failure message.

A method for notification of X2 messages, including:

The X2 gateway receives the X2 setup request message sent by the home base station;

If the connection between the home base station and the target base station is a direct X2 connection, the X2 gateway sends an X2 message to the home base station, where the X2 message carries a transport network layer that is saved by the target base station at the X2 gateway. Address or instructions for carrying a direct connection.

Optionally, the X2 message includes an X2 setup failure message.

An X2 gateway includes a receiving module and a sending module, where:

The receiving module is configured to: receive an X2 setup request message sent by the home base station; the sending module is configured to: if the connection between the home base station and the target base station is a direct X2 connection, return an X2 message to the home base station, where The X2 message carries the transport network layer address saved by the macro base station at the X2 gateway and the indication information carrying the direct connection.

Optionally, the X2 message includes an X2 setup failure message.

The method for the X2 message notification of the foregoing technical solution and the home base station and the X2 gateway may know the reason that the X2 setup request message cannot be routed to the target eNB, and the HeNB may carry the RNL ID and the TNL address of the eNB in the X2 message sent to the X2 GW. The X2 GW saves the matching relationship between the RNL ID and the TNL address of the eNB, so as to ensure that the subsequent X2 setup request message is correctly routed to the target eNB, and also avoids unnecessary unnecessary X2 signaling overhead, or reduces the number of TNL address discovery processes. . BRIEF abstract

1 is a schematic diagram of a network architecture in which a HeNB is located in a related art;

2 is a schematic diagram of an E-UTRAN architecture of a related art X2 GW deployment;

3 is a schematic structural diagram of a HeNB according to an embodiment of the present invention;

4 is a schematic flowchart of a method according to Embodiment 1 of the present invention; FIG. 5 is a schematic flowchart of a method according to Embodiment 2 of the present invention; FIG.

6 is a schematic flowchart of a method according to Embodiment 3 of the present invention;

FIG. 7 is a schematic structural diagram of a HeNB according to an embodiment of the present invention;

8 is a schematic flowchart of a method according to Embodiment 4 of the present invention;

FIG. 9 is a schematic structural diagram of an X2 GW according to an embodiment of the present invention.

Preferred embodiment of the invention

Embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be noted that, in the case of no conflict, the features in the embodiments and the embodiments in the present application may be arbitrarily combined with each other.

An embodiment of the present invention provides a method for notifying an X2 message, including the following steps: Step 11: The HeNB receives an X2 message of the X2 GW, where the X2 message carries a cause value indicating that the target eNB or the target HeNB cannot be routed. ;

Step 12: The HeNB initiates a transmission network layer address discovery process according to the cause value, and sends the information required by the X2 gateway to the X2 gateway, or the HeNB does not initiate an X2 establishment request according to the cause value.

A HeNB is provided correspondingly according to the embodiment of the present invention. As shown in FIG. 3, the HeNB of this embodiment includes

The receiving module 301 is configured to: receive an X2 message of the X2 gateway, where the X2 message carries a cause value indicating that the route cannot be routed to the target base station;

The processing module 302 is configured to: initiate a transport network layer address discovery process according to the cause value, send the information required by the X2 gateway to the X2 gateway, or not initiate an X2 setup request.

In an optional embodiment (corresponding to the first embodiment), the receiving module 301, the received value of the X2 message carries: the number of the wireless network layer identifier of the target base station is not matched with the transmission network layer address. Routing to the target base station;

The processing module 302 is configured to initiate a transport network layer address discovery process according to the cause value, and send the information required by the X2 gateway to the X2 gateway: initiate a transport network layer address discovery process, and obtain the target The transmission network layer address of the base station; to the X2 gateway And sending an X2 message, where the X2 message carries a radio network layer identifier of the target base station and an acquired transport network layer address of the target base station.

In an optional embodiment (corresponding to the second embodiment), the receiving module 301 receives the cause value of the X2 message: the home base station and the target base station are not connected to the same X2 gateway and cannot be routed to the target. Base station

The processing module 302 is configured to not initiate an X2 setup request according to the cause value according to the following manner: When the cell served by the target base station is found and the indirect X2 connection to the target base station is determined to be established, the X2 setup request is not initiated.

The method and the HeNB of the embodiment of the present invention can enable the HeNB to learn the reason why the X2 GW cannot route the X2 setup request message to the target eNB, and accordingly take corresponding measures.

Embodiment 1

In this embodiment, the eNB obtains the TNL address of the X2 GW through the process of TNL address discovery, and the X2 GW does not find the storage itself when receiving the X2 setup request message from the HeNB with the RNL ID of the target eNB. The matching relationship between the RNL ID and the TNL address of the target eNB, and therefore the X2 setup request message cannot be routed to the target eNB.

The X2 GW carries a new cause value in the X2 message sent to the HeNB, such as "matching information is not available", "agnostic target address", "routing is not supported", etc., so that the source HeNB knows that the X2 GW is due to no The target eNB's RNL ID and TNL address match relationship cannot be routed to the target eNB end. The X2 message can be an X2 setup failure message.

The source HeNB may send the RNL ID of the target eNB and the TNL address of the target eNB obtained through the TNL address discovery process to the X2 GW in a subsequent process, for example, causing the HeNB to establish a request message, a registration message, or a registration in the X2 sent to the X2 GW. The update message carries the RNL ID and the TNL address of the eNB, so that the X2 GW establishes a connection with the SCTP (STREAM CONTROL TRANSMISSION PROTOCOL) of the eNB, and causes the X2 GW to maintain the matching relationship between the RNL ID and the TNL address of the eNB. Thereby ensuring that the subsequent X2 setup request message is correctly routed to the target eNB.

FIG. 4 is a schematic flowchart of the embodiment, as shown in FIG. 4, including the following steps:

Step 401: The IP address of the X2 GW is configured for the HeNB, and after the HeNB is powered on, The matching relationship between the RNL ID and the TNL address is established and saved in the X2 GW through the registration process. Step 402: After discovering the cell served by the eNB, the HeNB decides to establish an indirect X2 connection to the eNB.

Step 403: The HeNB sends an X2 setup request message with the RNL ID of the target eNB to the X2 GW.

Step 404: At this time, the matching relationship between the RNL ID and the TNL address of the eNB is not saved at the X2 GW, the X2 GW cannot route the X2 setup request message to the target eNB, and the X2 GW returns the X2 message to the HeNB, and carries the new X2 message in the returned X2 message. The cause value, such as "matching information not available", "unknown target address", "routing is not supported", etc., so that the source HeNB knows that the X2 GW is unable to match the RNL ID and TNL address of the target eNB. Route X2 establishes a request message to the target eNB. The X2 message can be an X2 setup failure message.

Step 405: The HeNB initiates a TNL address discovery process to obtain the TNL address of the eNB. Step 406: The source HeNB learns, by step 404, that the X2 GW cannot route the X2 setup request message to the target eNB, and carries the RNL ID of the eNB in the X2 setup request message, the registration message, or the registration update message sent to the X2 GW, and in step 405. The TNL address of the acquired eNB. After obtaining the RNL ID and the TNL address of the eNB, the X2 GW can maintain the matching relationship between the RNL ID and the TNL address of the eNB, and establish an SCTP connection between the X2 GW and the eNB.

Step 407: The HeNB sends an X2 setup request message with the RNL ID of the target eNB to the X2 GW. The X2 GW routes the X2 setup request message to the corresponding target eNB according to the matching relationship between the RNL ID and the TNL address of the stored eNB.

Step 408: The eNB replies with an X2 setup response message with the RNL ID of the target HeNB to the X2 GW, and the X2 GW routes the X2 setup response message to the corresponding target HeNB according to the matching relationship between the stored ReNB ID and the TNL address of the HeNB. At the office.

Embodiment 2

When HeNB1 is registered on X2 GW1, HeNB2 or eNB2 is registered in X2 GW2. In this scenario, HeNB1 and HeNB2 or eNB2 cannot establish an indirect X2 interface through X2 GW1.

The X2 GW carries a new cause value in the X2 message sent to the HeNB, for example "not in the same The source HeNB learns that the source HeNB is not connected to the newly discovered HeNB or eNB on the same X2 GW. The X2 message may be an X2 setup failure message. The source HeNB may no longer attempt to establish a new discovery. Indirect X2 connection of the HeNB or eNB, thereby avoiding a large amount of unnecessary X2 signaling overhead.

FIG. 5 is a schematic flowchart of the embodiment, as shown in FIG. 5, including the following steps:

Step 501: The IP address of the X2 GW1 is configured for the HeNB1. After the power is turned on, the matching relationship between the RNL ID and the TNL address of the HeNB1 is established and saved in the X2 GW1 through the registration process.

Step 502: The IP address of the X2 GW2 is configured for the HeNB2 or the eNB2. After the power is turned on, the RNL ID and the TNL address of the HeNB2 or the eNB2 are established and saved in the X2 GW2 through the registration procedure.

Step 503: After discovering the cell served by HeNB2 or eNB2, HeNB1 decides to establish an indirect X2 connection to HeNB2 or eNB2.

Step 504: HeNB1 sends an X2 setup request message with the RNL ID of the target HeNB2 or eNB2 to X2 GW1.

Step 505: X2 GW1 returns an X2 message to HeNB1, and may carry a new cause value in the returned X2 message, because there is no matching relationship between the RNL ID and the TNL address of the HeNB2 or the matching relationship between the RNL ID and the TNL address of the eNB2 in the X2 GW1. , for example, "not under the same X2 GW" and so on. The X2 message can be an X2 setup failure message.

After receiving the X2 message with the special cause value, the HeNB1 can learn that the HeNB1 is not connected to the same X2 GW as the HeNB2 or the eNB2, and then the HeNB1 re-discovers the cell served by the HeNB2 or the eNB2, and decides to establish to the HeNB2 or the eNB2. When the indirect X2 connection is made, the X2 setup request message to X2 GW1 can be avoided.

Embodiment 3

In this embodiment, it is assumed that the manner in which the eNB and the HeNB pair, the HeNB, and the HeNB pair establish an X2 connection (direct X2 connection or indirect X2 connection) is stored at the HeNB.

When the source HeNB decides to establish a direct X2 connection to the target eNB according to its saved X2 connection mode, the source HeNB carries the request return target in the X2 message sent to the target eNB. The indication information of the TNL address of the eNB, where the X2 message may be an X2 setup request message. After the X2 GW receives the X2 message, if there is already a matching relationship between the RNL ID and the TNL address of the target eNB at the X2 GW, the X2 GW does not route the X2 message according to the matching relationship between the stored RNL ID and the TNL address of the target eNB. To the corresponding target eNB, the X2 message is sent to the source HeNB, and the X2 message carries the TNL address of the target eNB, and the X2 message may be an X2 setup failure message, so that the subsequent source HeNB directly initiates direct transmission to the target eNB. The establishment of the X2 connection.

FIG. 6 is a schematic flowchart of the embodiment. As shown in FIG. 6, the method includes the following steps:

Step 601: The IP address of the X2 GW is configured for the HeNB2. After the HeNB2 is powered on, the registration process is used to establish and save the matching relationship between the RNL ID and the TNL address of the HeNB2 in the X2 GW.

Step 602: The IP address of the X2 GW is configured for the HeNB3. After the HeNB3 is powered on, the registration process is used to establish and save the matching relationship between the RNL ID and the TNL address of the HeNB3 in the X2 GW.

Step 603: If the IP address of the X2 GW is configured for the eNB 1, the eNB 1 establishes and stores the matching relationship between the RNL ID and the TNL address of the eNB1 in the X2 GW through the registration process after the eNB 1 is powered on. The eNB 1 can also obtain the TNL address of the X2 GW through the TNL address discovery process, that is, the step 603 is omitted. Then, after the step 602, there is no matching relationship between the RNL ID and the TNL address of the eNB 1 in the X2 GW.

Step 604: After the HeNB3 discovers the cell served by the eNB1, it establishes a direct X2 connection to the eNB1 according to the manner of the X2 connection stored at the HeNB3.

Step 605: HeNB3 sends an X2 message with the RNL ID of the target eNB1 to the X2 GW. The X2 message also carries indication information requesting to return the TNL address of the eNB 1. The X2 message can be an X2 setup request message.

Step 606: If the X2 GW saves the RNL ID and the TNL address matching relationship of the eNB 1 in step 603, after the X2 GW receives the X2 setup request message with the indication information requesting to return the TNL address of the eNB1, the X2 GW does not Routing the X2 setup request message to the corresponding target eNB 1 according to the stored matching relationship between the RNL ID and the TNL address of the eNB1, but replying The X2 message is sent to HeNB3, and the message may be a 建立2 setup failure message, and the TNL address saved when eNB1 registers at the X2 GW is returned to HeNB3 in the X2 message.

If the step 603 is not performed, the X2 GW does not save the RNL ID and the TNL address matching relationship of the eNB1, and then returns the X2 message to the HeNB3 after receiving the X2 setup request message with the indication information requesting the return of the TNL address of the eNB1. The message may be an X2 setup failure message, and the message does not carry the TNL address information of the eNB1. After receiving the message, HeNB3 may initiate a TNL address discovery process to acquire the TNL address of eNB 1.

Step 607: After obtaining the TNL address of the eNB1, the HeNB3 establishes a direct X2 connection with the eNB1.

Step 608: After the HeNB2 finds the cell served by the eNB1, it establishes an indirect X2 connection to the eNB 1 according to the manner of the X2 connection stored at the HeNB2.

Step 609: HeNB2 sends an X2 setup request message with the RNL ID of the target eNB1 to the X2 GW. If the X2 GW stores the matching relationship between the RNL ID and the TNL address of the eNB1, the X2 GW according to the stored RNL ID and TNL of the eNB1. The matching relationship of the addresses to route the X2 setup request message to the corresponding target eNB 1. The eNB 1 replies with the X2 Setup Response message with the RNL ID of the target HeNB2 to the X2 GW, and the X2 GW routes the X2 Setup Response message to the corresponding target HeNB2 according to the matching relationship between the stored RNL ID of the HeNB2 and the TNL address.

An HeNB is provided in this embodiment. As shown in FIG. 7, the method includes:

The sending module 701 is configured to: send a first X2 message to the X2 gateway, where the first X2 message carries indication information that returns a target macro base station address;

The receiving module 702 is configured to: receive a second X2 message returned by the X2 gateway, where the second X2 message carries a transport network layer address of the target macro base station saved by the X2 gateway or does not carry the target macro base station Transport network layer address;

The processing module 703 is configured to: establish a direct X2 connection with the target base station or initiate a transport network layer address discovery process according to the second X2 message.

The processing module 701 is configured to send, according to the second X2 message, information required by the X2 GW to the X2 gateway according to the second X2 message or not to initiate an X2 setup request: when the second X2 message carries the When the X2 gateway saves the transmission network layer address of the target base station, After the home base station obtains the transport network layer address of the target base station, establishing a direct X2 connection with the target base station; when the second X2 message does not carry the transport network layer address of the target base station, the family The base station initiates a transport network layer address discovery process to obtain a transport network layer address of the target base station.

The sending, by the sending module 701, the first X2 message includes: an X2 setup request message,

The receiving module 702, the received second X2 message includes: an X2 setup failure message. Embodiment 4

It is assumed in this embodiment that the manner in which the eNB and the HeNB pair, the HeNB, and the HeNB pair establish an X2 connection (direct X2 connection or indirect X2 connection) is stored at the X2 GW.

When X2 GW receives the X2-HeNB transmits the setup request message, and decided to establish the time of the target eNB directly X2 connection according save an X2 connection, if X2 GW Department has targeted _e NB the RNL ID and TNL address The matching relationship, the X2 GW does not route the X2 message to the corresponding target eNB according to the matching relationship between the stored RNL ID and the TNL address of the target eNB, but sends the X2 message to the source HeNB, and carries the target eNB in the X2 message. The TNL address, the X2 message may be an X2 setup failure message, such that the subsequent source HeNB directly initiates the establishment of a direct X2 connection to the target eNB.

When the X2 GW receives the X2 setup request message sent by the source HeNB and determines the direct X2 connection to the target eNB according to the saved X2 connection manner, if there is no matching relationship between the RNL ID and the TNL address of the target eNB at the X2 GW The X2 GW sends the X2 message to the source HeNB, and carries the direct connection indication information in the X2 message, where the message may be an X2 setup failure message, so that the subsequent source HeNB initiates the TNL address discovery process to acquire the TNL address of the eNB to establish A direct X2 connection to the target eNB.

FIG. 8 is a schematic flowchart of the embodiment, as shown in FIG. 8, including the following steps:

Step 801 - Step 803 : The same as Step 301 - Step 303 in Embodiment 2, and details are not described herein.

Step 804: HeNB3 discovers the cell served by eNB1.

Step 805: HeNB3 sends an X2 setup request message with the RNL ID of the target eNB1 to X2 GW„

Step 806: The X2 GW determines that a direct X2 connection is established between the HeNB3 and the eNB 1 according to the stored manner of the X2 connection. If the X2 GW saves the RNL ID and the TNL address matching relationship of the eNB1 in step 803, the X2 GW does not according to the matching relationship between the stored RNL ID and the TNL address of the eNB1 after receiving the X2 setup request message of step 805. The X2 setup request message is routed to the corresponding target eNB1, but the X2 message is replied to the HeNB3. The message may be an X2 setup failure message, and the TNL address saved when the eNB1 registers at the X2 GW is returned to the HeNB3 in the X2 message.

The X2 GW determines that a direct X2 connection is to be established between HeNB3 and eNB1 according to the manner of the stored X2 connection. If the step 803 is not performed, the X2 GW does not save the RNL ID and the TNL address matching relationship of the eNB1. Then, after receiving the X2 setup request message of the step 805, the X2 GW returns an X2 message to the HeNB3, and the message may be an X2 setup failure message. The X2 GW carries the indication of the direct connection in the X2 message. After receiving the X2 message carrying the direct connection indication information, the HeNB3 may initiate a TNL address discovery process to obtain the TNL address of the eNB1.

Step 807: The same as step 307 in the second embodiment, and details are not described herein again.

Step 808: HeNB2 discovers the cell served by eNB1.

Step 809: The HeNB2 sends an X2 setup request message with the RNL ID of the target eNB1 to the X2 GW. The X2 GW determines that an indirect X2 connection is to be established between the HeNB2 and the eNB1 according to the stored X2 connection. If the matching relationship between the RNL ID and the TNL address of the eNB 1 is stored at the X2 GW, the X2 GW routes the X2 setup request message to the corresponding target eNB1 according to the stored matching relationship between the RNL ID and the TNL address of the eNB 1. The eNB1 replies with the X2 setup response message with the RNL ID of the target HeNB2 to the X2 GW, and the X2 GW routes the X2 setup response message to the corresponding target HeNB2 according to the matching relationship between the RNL ID and the TNL address of the stored HeNB2.

An X2 GW is provided for the embodiment. As shown in FIG. 9, the method includes:

The receiving module 901 is configured to: receive an X2 setup request message sent by the home base station; the sending module 902 is configured to: if the connection between the home base station and the target macro base station is a direct X2 connection, return an X2 message to the home base station, where The X2 message carries the transport network layer address saved by the macro base station at the X2 gateway and the indication information carrying the direct connection. The sending, by the sending module 902, the X2 message may include an X2 setup failure message.

The above is only an alternative embodiment of the present invention, and is not intended to limit the present invention. The present invention may be embodied in various other embodiments without departing from the spirit and scope of the invention. Various changes and modifications can be made in accordance with the invention, but such changes and modifications are intended to be included within the scope of the appended claims.

Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. The steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps are fabricated as a single integrated circuit module. Thus, the invention is not limited to any particular combination of hardware and software.

Industrial Applicability The method for the X2 message notification of the foregoing technical solution and the home base station and the X2 gateway may be aware of the reason that the X2 setup request message cannot be routed to the target eNB, and the HeNB may carry the RNL ID of the eNB in the X2 message sent to the X2 GW. And the TNL address, so that the X2 GW saves the matching relationship between the RNL ID and the TNL address of the eNB, so as to ensure that the subsequent X2 setup request message is correctly routed to the target eNB, and also avoids unnecessary unnecessary X2 signaling overhead or reduces TNL address discovery. The number of processes. Therefore, the present invention has strong industrial applicability.

Claims

claims

1. An X2 message notification method, including:

The home base station receives the X2 message from the X2 gateway, and the X2 message carries a reason value indicating that it cannot be routed to the target base station;

The home base station initiates a transmission network layer address discovery process according to the cause value, and reports to the

The X2 gateway sends the information required by the X2 gateway, or the home base station does not initiate an X2 establishment request based on the cause value.

2. The X2 message notification method as claimed in claim 1, wherein:

The reason values include: unable to route to the target base station because there is no matching relationship between the wireless network layer identifier of the target base station and the transmission network layer address;

The steps for the X2 gateway to send the information required by the X2 gateway include:

The home base station initiates a transmission network layer address discovery process to obtain the transmission network layer address of the target base station;

The home base station sends an X2 message to the X2 gateway, where the X2 message carries the wireless network layer identifier of the target base station and the obtained transmission network layer address of the target base station.

3. The X2 message notification method as claimed in claim 1, wherein:

The reason values include: The home base station and the target base station are not connected to the same X2 gateway and cannot be routed to the target base station;

The step of the home base station not initiating an X2 establishment request based on the reason value includes: when the home base station rediscovers a cell served by the target base station and decides to establish an indirect X2 connection to the target base station, it does not initiate an X2 establishment request. ask.

4. The X2 message notification method as claimed in claim 1, wherein:

The X2 message includes an X2 establishment failure message.

5. A home base station, including a receiving module and a processing module, wherein:

The receiving module is configured to: receive an X2 message from an X2 gateway, where the X2 message carries a reason value indicating that it cannot be routed to the target base station; The processing module is configured to: initiate a transmission network layer address discovery process according to the cause value, send the information required by the X2 gateway to the X2 gateway, or not initiate an X2 establishment request.

6. The home base station as claimed in claim 5, wherein:

The processing module is configured to initiate a transmission network layer address discovery process according to the cause value in the following manner, and send the information required by the X2 gateway to the X2 gateway: initiate a transmission network layer address discovery process, and obtain the target base station the transmission network layer address; sending an X2 message to the X2 gateway, where the X2 message carries the wireless network layer identifier of the target base station and the obtained transmission network layer address of the target base station.

7. The home base station as claimed in claim 5, wherein:

The processing module is configured to not initiate an X2 establishment request according to the reason value in the following manner: When the cell served by the target base station is discovered again and it is decided to establish an indirect X2 connection to the target base station, the X2 establishment request is not initiated.

8. The home base station as claimed in claim 5, wherein:

The X2 message received by the receiving module includes an X2 establishment failure message.

9. An X2 message notification method, including:

The home base station sends a first X2 message to the X2 gateway, where the first X2 message carries indication information for returning the target base station address;

The X2 gateway returns a second X2 message to the home base station, where the second X2 message carries the transmission network layer address of the target base station saved by the X2 gateway or does not carry the transmission network layer address of the target base station;

The home base station receives the second X2 message, and the home base station establishes a direct X2 connection with the target base station or initiates a transmission network layer address discovery process according to the second X2 message.

10. The X2 message notification method as claimed in claim 9, wherein: When the second X2 message carries the transport network layer address of the target base station saved by the X2 gateway, the step of the home base station establishing a direct X2 connection with the target base station or initiating a transport network layer address discovery process includes : After obtaining the transmission network layer address of the target base station, establish a direct X2 connection with the target base station;

When the second X2 message does not carry the transport network layer address of the target base station, the steps of the home base station establishing a direct X2 connection with the target base station or initiating a transport network layer address discovery process include: initiating a transport network layer Address discovery process: obtain the transmission network layer address of the target base station.

11. The X2 message notification method as claimed in claim 9 or 10, wherein:

The first X2 message includes: X2 establishment request message,

The second X2 message includes: X2 establishment failure message.

12. A home base station, including a sending module, a receiving module and a processing module, wherein: the sending module is configured to: send a first X2 message to the X2 gateway, where the first X2 message carries instruction information for returning the address of the target macro base station ;

The receiving module is configured to: receive the second X2 message returned by the X2 gateway, the second

The X2 message carries the transmission network layer address of the target macro base station saved by the X2 gateway or does not carry the transmission network layer address of the target macro base station;

The processing module is configured to: establish a direct X2 connection with the target base station or initiate a transmission network layer address discovery process according to the second X2 message.

13. The home base station as claimed in claim 12, wherein:

The processing module is configured to establish a direct X2 connection with the target base station or initiate a transmission network layer address discovery process according to the second X2 message in the following manner: When the second X2 message carries all the information saved by the X2 gateway When the second X2 message does not carry the target base station, the home base station establishes a direct X2 connection with the target base station after obtaining the transmission network layer address of the target base station. When the transmission network layer address is obtained, the home base station initiates a transmission network layer address discovery process to obtain the transmission network layer address of the target base station.

14. The home base station as claimed in claim 12 or 13, wherein: The first X2 message includes: X2 establishment request message,

The second X2 message includes: X2 establishment failure message.

15. An X2 message notification method, including:

The X2 gateway receives the X2 establishment request message sent by the home base station;

If the connection between the home base station and the target base station is a direct X2 connection, the X2 gateway sends an X2 message to the home base station, and the X2 message carries the transmission network layer of the registration time saved by the target base station at the X2 gateway. address or carry instructions for a direct connection.

16. The X2 message notification method as claimed in claim 15, wherein:

The X2 message includes an X2 establishment failure message.

17. An X2 gateway, including a receiving module and a sending module, where:

The receiving module is configured to: receive the X2 establishment request message sent by the home base station; the sending module is configured to: return an X2 message to the home base station if the connection between the home base station and the target base station is a direct X2 connection, so The X2 message carries the transport network layer address saved at the registration time of the macro base station at the X2 gateway or carries direct connection indication information.

18. The X2 gateway as claimed in claim 17, wherein:

The X2 message includes an X2 establishment failure message.