CN104519564A

CN104519564A - A method for interacting with x2 gateway, base station, and x2 gateway

Info

Publication number: CN104519564A
Application number: CN201310447123.5A
Authority: CN
Inventors: 吴蕴璐; 高音; 黄莹
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2013-09-26
Filing date: 2013-09-26
Publication date: 2015-04-15
Also published as: WO2015043289A1

Abstract

The present application discloses a method for interacting with an X2 gateway, a base station, and an X2 gateway. The method comprises a process of performing registration for the present base station, and the process comprises: a home evolved base station (HeNB) or an evolved base station (eNB) sending a first registration request message to the X2 gateway, the first registration request message carrying a base station identifier of the present base station and further carrying the following one or more set of information of the present base station: location information of the HeNB or eNB, serving cell information of the HeNB or eNB, and a closed member group identifier and access mode information of the HeNB; and the X2 gateway receiving the first registration request message, and then storing a matching relationship between the base station identifier of the HeNB or eNB and an address of a transport network layer (TNL), and returning a registration response message. The method for interacting with x2 gateway, base station, and x2 gateway of the present invention achieve registration of the HeNB or eNB to the X2 gateway, thereby providing a user with a wireless communication service with high quality.

Description

Method for interaction between base station and X2gateway, base station and X2gateway

Technical Field

The invention relates to a wireless communication technology, in particular to a method for interaction between a base station and an X2gateway, the base station and the X2 gateway.

Background

A home base station is a small low-power base station, which is deployed in a private location such as a home, a group, a company, or a school as a dedicated resource for a private user, and is connected to a core network of an operator through a cable access device such as a cable, a Digital Subscriber Line (DSL), or an optical fiber. The main function of the femtocell is to provide higher service rate to the user, reduce the cost required by using high-rate service, and make up for the insufficient coverage of the existing distributed cellular wireless communication system. The advantages of the home base station include: low cost, convenient use (plug and play), low output power, saving the expense of operators for erecting and maintaining base stations, solving indoor coverage optimization and the like.

In a Long Term Evolution (LTE) system, a schematic diagram of a network architecture where an Evolved Home base station (HeNB) is located is shown in fig. 1. A terminal (UE) under the HeNB is a Home Evolved NodeB Access Network (HeNBAN) based on an existing air interface protocol Access evolution. The HeNBAN is composed of an HeNB and an Evolved Home base station Gateway (HeNB GW, Home Evolved NodeB Gateway). The functions supported by the HeNB are substantially the same as those of an enhanced Node B (eNB). Only one cell is connected under 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, selecting a Mobility Management Entity (MME) for the UE during the attach process, and the like. The HeNB can be directly connected to an Evolved Packet Core (EPC) through an S1 interface, wherein the HeNB is connected to a Serving Gateway (S-GW) through an S1-U interface, and the HeNB is connected to an MME through an S1-MME interface. The HeNB may also be connected to the EPC through a HeNB GW, where the S1-U interface may terminate at the HeNB GW, or at the EPC, through which the S1-MME interface passes to the EPC. The EPC network element comprises an MME and an S-GW. The MME undertakes related functions such as bearer management and mobility management. The S-GW assumes functions such as data routing for the user plane. In addition, the evolved home base station Management System (HeMS, HeNB Management System) in fig. 1 maintains and manages the HeNB, configures and controls the HeNB according to the requirements of an operator, wherein the most important is to implement a configuration function for the HeNB, and the configured content includes verification of location information, parameters of the HeNB, parameters of a core Network, parameters of a Radio Access Network (RAN, Radio Access Network), and parameters of a Radio Frequency (RF). A security gateway (SeGW) supports security-related functions in the network.

The HeNB provides a service only for a specific user, and thus a concept of Closed Subscriber Group (CSG) is introduced to perform access control. Each HeNB has specific CSG attributes including a closed member group Identity (CSG Identity, abbreviated as CSG ID) and access mode information. Here, three Cell Access modes (Cell Access Mode) are defined for the HeNB: closed (Close) mode, only closed member group members identified by the corresponding CSG ID can access; hybrid (Hybrid) mode, which allows access to all UEs, but closed member group members identified by the corresponding CSG ID enjoy higher priority; open (Open) mode, allowing access for all UEs.

The third Generation Partnership Project (3 GPP, 3rd Generation Partnership Project) at the time of Release10 and Release11 agreed to permit the establishment of an X2 interface for handover purposes under the following scenarios: between an eNB and an HeNB in an open mode, between the eNB and a HeNB in a hybrid mode, from the HeNB in a source closed mode to a target eNB, between the HeNB in the open mode and the HeNB in the open/hybrid mode, from the HeNB in a source closed mode to the HeNB in the target open/hybrid mode, from the HeNB in the source closed mode to the HeNB in the target closed mode, and from the HeNB in the source hybrid/closed mode with the same PLMNID and CSG ID. The connection between the eNB and the HeNB and between the henbs may be direct X2, or may be indirect X2 through a new functional entity X2Gateway (X2 GW, X2 Gateway) like the HeNB GW. In the discussion process of introducing the X2GW scheme, the source side uses a new registration message to establish and store a matching relationship between an RNL ID and a Transport Network Layer (TNL) address, an IP address of X2GW is configured to the HeNB, and a scheme in which the eNB acquires the IP address of X2GW in a configuration manner or through a TNL address discovery process as a candidate scheme of X2GW in X2GW based on an Identification (ID) of a Radio Network Layer (RNL) of the target side, an Identity (Identity) route X2 message, and the HeNB or the eNB use the new registration message when the source side is powered on. The TNL address of the HeNB or eNB may be acquired from the transport layer information when receiving the message. In the existing standard, the HeNB is registered on the HeNB GW through an S1 setup procedure. Since X2GW is a new functional entity distinct from the HeNB GW, as shown in fig. 2. Therefore (H) new registration procedure of eNB on X2GW needs refinement.

Disclosure of Invention

The technical problem to be solved by the invention is to provide a method for interaction between a base station and an X2gateway, the base station and the X2gateway, which can realize registration of the base station on the X2 gateway.

In order to solve the above technical problem, a method for a base station to interact with an X2gateway of the present invention includes a process of registering for the base station, where the process includes:

an evolved home base station HeNB or an enhanced base station eNB sends a first registration request message to an X2gateway, wherein the first registration request message carries a base station identifier of the base station and also carries one or more groups of following information of the base station:

location information of the HeNB or eNB;

serving cell information of the HeNB or eNB;

closed member group identification and access mode information of the HeNB;

and after receiving the first registration request message, the X2gateway stores the matching relationship between the base station identifier of the HeNB or the eNB and the TNL address of the transport network layer, and returns a registration response message.

Further, the method also comprises a process for registering for other base stations, and the process comprises the following steps:

the HeNB sends an X2 establishment request message to an X2gateway, if the X2gateway can not route the X2 establishment request message to an opposite-end eNB, a second registration request message is sent to the X2gateway, and the second registration request message carries the base station identifier of the opposite-end eNB and the TNL address of the opposite-end eNB obtained through a TNL address discovery process;

and after receiving the second registration request message, the X2gateway stores the matching relationship between the base station identifier of the opposite-end eNB and the TNL address, and returns a response message.

Further, the first registration request message carries the closed member group identity and access mode information of the HeNB, and the X2gateway stores the closed member group identity and access mode information of the HeNB after receiving the first registration request message;

the method further comprises the following steps:

and after receiving an X2 interface establishment request sent by a source base station, the X2gateway judges whether to allow the establishment of the X2 interface according to the closed member group identifications and the access mode information of the source base station and the target base station.

Further, the X2gateway successfully registers, returns a registration success response message carrying a message type cell, or a message type cell and a danger diagnosis cell, and lets the HeNB or eNB know that the X2gateway has successfully stored the matching relationship between the base station identifier of the HeNB or eNB and the TNL address.

Further, the registration success response message also carries the X2gateway identifier.

Further, the X2gateway also carries information in a registration success response message according to one of the following manners;

the first method is as follows:

if the eNB initiates the first registration request message, the registration success response message carries the service cell information or the base station identification of the HeNB registered under the X2 gateway;

if the HeNB initiates the first registration request message, the registration success response message carries the eNB registered under the X2gateway and the service cell information or the base station identification of the HeNB;

the second method comprises the following steps:

and if the HeNB initiates the first registration request message, the registration success response message does not carry the information of the base station registered under the X2 gateway.

Further, the serving cell information or the base station identifier of the HeNB includes a TNL address of the HeNB, and/or a closed member group identifier and access mode information of the HeNB;

the serving cell information or the base station identifier of the eNB includes a TNL address of the eNB.

Further, the registration success response message returned by the X2gateway includes the closed member group identity and the access mode information of the HeNB registered under the X2 gateway;

the method further comprises the following steps: and the HeNB or the eNB judges whether the establishment of the X2 interface to the HeNB is limited or not according to the closed member group identification and the access mode information of the HeNB registered under the X2gateway, and initiates the establishment process of the X2 interface when the establishment is not limited.

Further, the X2gateway fails to register and returns a registration failure response message; the registration failure response message comprises one or more of the following information:

a registration failure cause, a minimum grant latency, and a hazard diagnosis cell.

Further, still include:

before the HeNB is powered off, sending a third registration request message to an X2gateway, wherein the third registration request message carries a power-off identifier and a base station identifier of the HeNB; after receiving the third registration request message, the X2gateway forwards the third registration request message to the HeNB or eNB to which the HeNB is connected; or,

and after the X2gateway finds that the connection between the gateway and the HeNB is disconnected, sending a fourth registration request message to the HeNB or the eNB which is connected with the HeNB, wherein the fourth registration request message carries the base station identification and the shutdown identification of the HeNB.

Further, a process of deregistration is also included, the process comprising:

before the HeNB is powered off, sending a de-registration message to an X2gateway, wherein the de-registration message contains a base station identification of the HeNB; after receiving the de-registration message, the X2gateway forwards the de-registration message to the HeNB or eNB to which the HeNB is connected; or,

after the connection between the X2gateway and the HeNB is disconnected, a de-registration message is sent to the HeNB or the eNB which is connected with the HeNB, and the de-registration message carries the base station identification of the HeNB.

Further, a process of registering updates is included, the process comprising:

when a serving cell of the HeNB or the eNB changes, sending a registration update message to an X2gateway, wherein the registration update message carries an evolved universal terrestrial radio access network (ECGI) cell global identity of an old serving cell and new serving cell information; after receiving the registration update message, the X2gateway forwards the registration update message to the HeNB or eNB to which the HeNB or eNB is connected; or,

the X2gateway sends a registration update message to the HeNB or eNB which is connected with the HeNB or eNB after the serving cell of the HeNB or eNB changes, and the registration update message carries the ECGI of the old serving cell and the new serving cell information.

Further, a process of registering updates is included, the process comprising:

before the HeNB is powered off, a registration update message is sent to an X2gateway, and the base station identification of the HeNB and information representing the power off of the HeNB are carried; after receiving the registration update message, the X2gateway forwards the registration update message to the HeNB or eNB to which the HeNB is connected; or,

after the X2gateway finds that the connection between the gateway and the HeNB is disconnected, the X2gateway sends a registration update message to the HeNB or the eNB which is connected with the HeNB, and carries the base station identification of the HeNB and information indicating the power-off of the HeNB.

Further, still include:

when the HeNB is powered on again after being powered off, the HeNB sends a registration update message to the X2GW, wherein the registration update message carries a base station identifier of the HeNB and information indicating the power-on of the HeNB; after receiving the registration update message, the X2gateway forwards the registration update message to the HeNB or eNB to which the HeNB is connected; or,

and after the HeNB is powered on again, the X2gateway sends a registration update message to the HeNB or the eNB connected with the HeNB, and carries the base station identification of the HeNB and information indicating the power-on of the HeNB.

Further, a base station comprising: a first registration unit and a communication unit, wherein:

the first registration unit is configured to send a first registration request message to an X2gateway through the communication unit, where the first registration request message carries a base station identifier of the local base station and also carries one or more sets of the following information of the local base station:

location information of the HeNB or eNB;

serving cell information of the HeNB or eNB;

closed member group identification and access mode information of the HeNB;

the communication unit is configured to send the first registration request message to the X2 gateway;

the base station is an evolved home base station HeNB or an enhanced base station eNB.

Further, a second registration unit is included, wherein:

the second registration unit is configured to send an X2 establishment request message to an X2gateway, and if the X2gateway cannot route the X2 establishment request message to an opposite-end eNB, send a second registration request message to the X2gateway, where the second registration request message carries a base station identifier of the opposite-end eNB and a TNL address of the opposite-end eNB obtained through a TNL address discovery process.

Further, the device also comprises a judging unit, wherein:

the judging unit is configured to judge whether to initiate establishment of an X2 interface to the HeNB is limited according to the closed member group identity and the access mode of the HeNB registered by the X2gateway, which are included in the registration success response message received by the communication unit, and initiate an establishment procedure of the X2 interface when the establishment procedure is not limited.

Further, a third registration unit is included, wherein:

and the third registration unit is used for sending a third registration request message to the X2gateway before the HeNB is powered off, wherein the third registration request message carries the power-off identifier and the base station identifier of the HeNB.

Further, a deregistration unit is included, wherein:

the deregistration unit is used for sending a deregistration message to the X2gateway before the HeNB is powered off, wherein the deregistration message contains the base station identification of the HeNB.

Further, the system also comprises a registration updating unit, wherein:

and the registration updating unit is used for sending a registration updating message to the X2gateway when the serving cell changes, wherein the registration updating message carries the global identity ECGI of the evolved universal terrestrial radio access network cell of the old serving cell and the new serving cell information.

Further, the system also comprises a registration updating unit, wherein:

and the registration updating unit is used for sending a registration updating message to the X2gateway before the HeNB is powered off, and the registration updating message carries the base station identification of the HeNB and information indicating the power off of the HeNB.

Further, still include rebooting renewal unit, wherein:

the power-on emphasizing updating unit is used for sending a registration updating message to the X2GW by the HeNB after the power-off HeNB is powered on again, and the registration updating message carries the base station identification of the HeNB and information indicating the power-on of the HeNB.

Further, an X2gateway, comprising: communication unit, matching relation save unit and response unit, wherein:

the communication unit is used for receiving and sending messages;

the matching relation storage unit is used for storing the matching relation between the base station identifier of the evolved home base station HeNB or the enhanced base station eNB and the TNL address of the transmission network layer after the communication unit receives the first registration request message;

and the response unit is used for returning a registration response message.

Further, the matching relationship storing unit is further configured to store the matching relationship between the base station identifier of the opposite-end eNB and the TNL address after the communication unit receives the second registration request message, and return a response message.

Further, the device also comprises a judging unit, wherein:

the judging unit is configured to store the closed member group identifier and the access mode information of the HeNB after the communication unit receives the first registration request message, and judge whether to allow establishment of the X2 interface according to the closed member group identifiers and the access modes of the source base station and the target base station after the communication unit receives an X2 interface establishment request sent by the source base station.

Further, the response unit is specifically configured to, after successful registration, return a registration success response message carrying a message type cell, or a message type cell and a risk diagnosis cell, so that the HeNB or eNB knows that the X2gateway has successfully stored the matching relationship between the base station identifier of the HeNB or eNB and the TNL address.

Further, the registration success response message also carries an X2gateway identifier.

Further, the response unit also carries information in a registration success response message according to one of the following modes;

the first method is as follows:

the second method comprises the following steps:

Further, the response unit is specifically configured to return a registration failure response message when the registration fails; the registration failure response message comprises one or more of the following information:

Further, the system also comprises a notification unit, wherein:

the notifying unit is configured to forward, after the communication unit receives the third registration request message, the third registration request message to a HeNB or an eNB that is connected to the HeNB that initiated the third registration request message; or,

and after the connection with the HeNB is disconnected, sending a fourth registration request message to the HeNB or the eNB which is connected with the HeNB, wherein the fourth registration request message carries the base station identifier and the power-off identifier of the HeNB.

Further, the system also comprises a notification unit, wherein:

the notification unit is further configured to forward, after the communication unit receives the de-registration message, the de-registration message to the HeNB or eNB to which the HeNB initiating the de-registration message is connected; or,

and after the connection with the HeNB is disconnected, sending a de-registration message to the HeNB or the eNB which is connected with the HeNB, wherein the de-registration message carries the base station identification of the HeNB.

Further, the system also comprises a notification unit, wherein:

the notification unit is used for forwarding the registration update message to the HeNB or eNB which has connection with the HeNB or eNB initiating the registration update message after the communication unit receives the registration update message; or,

and after the serving cell of the HeNB or the eNB is changed, sending a registration update message to the HeNB or the eNB which is connected with the HeNB or the eNB, wherein the registration update message carries the ECGI of the old serving cell and the new serving cell information.

Further, the system also comprises a notification unit, wherein:

the notification unit is further configured to forward, after the communication unit receives the registration update message, the registration update message to the HeNB or eNB to which the HeNB initiating the registration update message is connected; or,

and after the connection with the HeNB is disconnected, sending a registration update message to the HeNB or the eNB which is connected with the HeNB, wherein the registration update message carries the base station identification of the HeNB and information indicating the power-off of the HeNB.

Further, the system also comprises a reboot notification unit, wherein:

the reboot notification unit is configured to forward the registration update message to the HeNB or the eNB connected to the HeNB initiating the registration update message after the communication unit receives the registration update message; or,

and after the HeNB is powered on again, sending a registration update message to the HeNB or the eNB connected with the HeNB, wherein the registration update message carries the base station identification of the HeNB and information indicating the power-on of the HeNB.

In summary, the present invention realizes the registration of the HeNB or eNB with the X2gateway, so that the HeNB or eNB can communicate through the X2gateway, thereby providing high-quality wireless communication services to users.

Drawings

Fig. 1 is a schematic diagram of a network architecture in which a HeNB is located in the prior art;

FIG. 2 is a schematic diagram of an E-UTRAN architecture with X2GW deployment;

FIG. 3 is a flowchart illustrating a successful registration process according to a second embodiment of the present invention;

FIG. 4 is a flowchart illustrating a second registration failure according to an embodiment of the present invention;

fig. 5 is a schematic diagram of notifying an (H) eNB connected to a shutdown HeNB of shutdown information of the HeNB by using a registration procedure according to a third embodiment of the present invention;

fig. 6 is a schematic diagram of notifying an (H) eNB connected to a shutdown HeNB of the shutdown information of the HeNB by using a de-registration procedure according to a third embodiment of the present invention;

fig. 7 is a schematic diagram of notifying an (H) eNB connected to a shutdown HeNB of shutdown information of the HeNB by using a registration update procedure according to a third embodiment of the present invention;

FIG. 8 is a schematic flow chart of a fourth embodiment of the present invention;

FIG. 9 is an architecture diagram of a base station in accordance with an embodiment of the present invention;

fig. 10 is an architecture diagram of an X2gateway according to an embodiment of the present invention.

Detailed Description

The first embodiment is as follows:

the embodiment provides a method for interaction between a base station and an X2gateway, which comprises a process of registering for the base station, wherein the process comprises the following steps:

the HeNB or the eNB sends a first registration request message to an X2gateway (X2 GW); the first registration request message carries the base station identifier of the base station and also carries one or more groups of following information of the base station:

location information of the HeNB or eNB;

serving cell information of the HeNB or eNB;

closed member group identification and access mode information of the HeNB;

and after receiving the first registration request message, the X2gateway stores the matching relationship between the base station identifier of the HeNB or the eNB and the TNL address, and returns a registration response message.

If the sending end is the HeNB, the base station identification included in the first registration request message is HeNBID; if the transmitting end is the eNB, the base station identifier included in the first registration request message is the eNB ID. The RNL ID is equivalent to the base station identity, i.e.: the RNL ID is equivalent to the HeNB ID and the RNL ID is also equivalent to the eNB ID, and the base station identity is not distinguished from the RNL ID in the following.

The serving cell information includes PLMN ID, ECGI, PCI, TAC, and the like.

The method also comprises a process of registering for other base stations, wherein when X2GW receives an X2 establishment request message sent by the HeNB but does not have matching information of the RNL ID and the TNL address of the eNB, the HeNB can include a base station identifier and a TNL address of an opposite terminal network element of a registered network element in a second registration request message sent by the HeNB;

the process comprises the following steps:

the HeNB sends an X2 establishment request message to an X2gateway, if the X2gateway cannot route the X2 establishment request message to the opposite-end eNB, a second registration request message is sent to the X2gateway, and the second registration request message carries the base station identifier of the opposite-end eNB and the TNL address of the opposite-end eNB obtained through the TNL address discovery process;

In the application, a first registration request message carries a closed member group identification and access mode information of the HeNB, and an X2gateway stores the closed member group identification and the access mode information of the HeNB after receiving the first registration request message;

the method of the present application further comprises: after receiving the X2 interface establishment request sent by the source base station, the X2gateway judges whether to allow the establishment of the X2 interface according to the closed member group identification and the access mode information of the source base station and the target base station.

And the X2gateway returns a registration response message to the HeNB or the eNB, wherein if the registration is successful, the registration success response message is returned, otherwise, the registration failure response message is returned.

The X2gateway returns a registration response message to the HeNB or eNB, wherein if the registration is successful, the registration success response message is returned, further comprising:

the registration success response message may carry a message type cell, or a message type cell and a Criticality Diagnostics (risk diagnosis) cell, and only let the HeNB or eNB know that X2GW has successfully saved the matching relationship between the RNL ID and the TNL address of the HeNB or eNB;

the registration success response message may carry an X2GW ID;

the X2gateway also carries information in a registration success response message in one of the following ways;

the first method is as follows:

the second method comprises the following steps:

The serving cell information or the base station identity of the HeNB may include a TNL address of the HeNB, and/or a closed member group identity and access mode information of the HeNB;

the TNL address of the eNB may be included in the serving cell information of the eNB or in the base station identity. Such information in this context refers to information elements in the message.

The registration success response message returned by the X2gateway comprises the closed member group identification and the access mode information of the HeNB registered under the X2 gateway;

The X2gateway returns a registration response message to the HeNB or eNB, wherein if the registration fails, the registration failure response message is returned, further comprising:

the registration failure response message includes one or more of the following information: the reason of registration failure, the waiting time of minimum grant, and the danger diagnosis cell.

The method of the present application further comprises:

the HeNB is normally shut down, the HeNB sends a third registration request message with a shutdown identifier to the X2GW before the HeNB prepares for shutdown, and after receiving the message, the X2GW forwards the message to the HeNB or eNB which is connected with the shutdown HeNB, wherein the message comprises the HeNB ID of the shutdown HeNB; or,

the HeNB is abnormally shut down, the X2GW can discover that the SCTP connection between the HeNB and the HeNB is disconnected, and initiate a fourth registration request message to the HeNB or eNB which is connected with the shut-down HeNB, wherein the message comprises the HeNB ID and the shut-down identifier of the shut-down HeNB discovered by the X2 GW.

Notifying the HeNB status using a de-registration procedure, further comprising:

the HeNB is normally shut down, before the HeNB prepares to shut down, the HeNB sends a new de-registration message to the X2GW to initiate a de-registration process, wherein the message comprises the HeNB ID of the shut-down HeNB, and the X2GW forwards the message to the HeNB or the eNB which is connected with the shut-down HeNB; or,

the HeNB is abnormally shut down, the X2GW can discover that the SCTP connection between the HeNB and the X2, and initiate a new de-registration message to the HeNB or the eNB which is connected with the shut-down HeNB, wherein the message comprises the HeNB ID of the shut-down HeNB.

The method of the present application further comprises a process of registering the update, the process comprising:

when the serving cell of the HeNB or eNB changes, the HeNB or eNB may send a registration update message to X2GW, carrying the ECGI of the old serving cell and the new serving cell information; after receiving the registration update message, the X2gateway forwards the registration update message to the HeNB or eNB which is connected with the HeNB or eNB; or

And after the serving cell of the HeNB or the eNB is changed, the X2gateway sends a registration update message to the HeNB or the eNB which is connected with the HeNB or the eNB, and the ECGI of the old serving cell and the new serving cell information are carried.

when the HeNB is normally powered off, the HeNB sends a registration updating message to the X2GW to initially execute a registration updating process before the HeNB prepares to be powered off, wherein the message comprises a HeNB ID of the HeNB to be powered off and information indicating the power off of the HeNB, and the X2GW forwards the message to the HeNB or an eNB which is connected with the power-off HeNB; or,

when the HeNB is abnormally shut down, the X2GW can find that the SCTP connection between the HeNB and the X2 can be disconnected, and initiate a registration updating message to the HeNB or the eNB which is connected with the shut-down HeNB, wherein the message comprises the HeNB ID of the HeNB to be shut down and information indicating the shut-down of the HeNB.

The application also includes:

when the HeNB is powered on again after being powered off, the HeNB can send a registration update message to the X2GW, wherein the registration update message carries the HeNB ID of the powered-on HeNB and information indicating the power-on of the HeNB; after receiving the registration update message, the X2gateway forwards the registration update message to the HeNB or eNB to which the HeNB is connected; or,

and after the HeNB is powered on again, the X2gateway sends a registration update message to the HeNB or the eNB connected with the HeNB, and carries the base station identification of the HeNB and the information indicating the power-on of the HeNB.

The registration update message indicating power-off or power-on again may be represented by a separate cell, or may be location information of a certain cell, such as a base station identifier, as indication information. For example, the registration update message includes: the base station identifier of the power-off is filled in the servdcells To Delete, and the base station identifier of the power-on is filled in the servdcells To Add.

In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be noted that the embodiments and features of the embodiments in the present application may be arbitrarily combined with each other without conflict.

Example two:

the embodiment is suitable for registration of HeNB and eNB on X2 GW. In the present embodiment, the RNLID and the HeNB ID are equivalent concepts, and the RNL ID and the eNB ID are equivalent concepts.

Fig. 3 is a schematic diagram illustrating successful registration in this embodiment.

Step 301: the HeNB or eNB sends a new X2 message to initiate the registration procedure, which in this embodiment is named (H) eNB REGISTER REQUEST.

(H) The eNB REGISTER REQUEST message includes the HeNB ID or eNB ID. After the HeNB or the eNB establishes the SCTP connection with the X2GW, the HeNB or the eNB includes the HeNB ID or the eNB ID in the (H) eNB REQUEST message, and after the X2GW receives the (H) eNB REGISTER REQUEST message carrying the HeNB ID or the eNB ID, the matching relationship between the RNL ID and the TNL address of the HeNB or the eNB may be established.

If the transmitting end is eNB, (H) eNB REGISTER REQUEST includes eNB ID; if the transmitting end is HeNB, (H) eNB REGISTER REQUEST includes HeNB ID. After receiving (H) the eNB REGISTER REQUEST message, the X2GW stores the matching relationship between the RNL ID and TNL address of the HeNB or eNB for the purpose of subsequent routing of the X2 message.

(H) The eNB REGISTER REQUEST message may further include HeNB or eNB location information, serving Cell information (including Public Land Mobile network identity (PLMN ID), E-UTRAN Cell global identity (ECGI), Physical Cell Identity (PCI), Tracking Area Code (TAC), and the like).

Step 302: if the registration is successful, that is, after the X2GW successfully stores the matching relationship between the RNLID and the TNL address of the HeNB or eNB, the X2GW returns a new X2 response message to the HeNB or eNB, where the new response message is (H) eNB REGISTER REQUEST ACK in this embodiment.

(H) The eNB REGISTER REQUEST ACK message may carry a message type information element and/or Criticality Diagnostics, and only let the HeNB or eNB know that X2GW has successfully saved the matching relationship between the RNL ID and the TNL address of the HeNB or eNB.

(H) The eNB REGISTER REQUEST ACK message may carry the X2GW ID.

(H) The eNB REGISTER REQUEST ACK message may also include serving cell information of (H) enbs registered under X2 GW. If the eNB is the eNB, the reason for returning the HeNB serving cell information or the HeNB ID in the (H) eNB REGISTER REQUEST message is that: the HeNB is connected only to one X2GW, while the eNB may be connected to multiple X2GW, the eNB may know which X2GW the newly discovered target HeNB is connected to through the HeNB serving cell information or HeNB ID returned in the (H) eNB REGISTER REQUEST ACK message.

If the cell is the HeNB, the HeNB or the eNB lower serving cell information is returned in the (H) eNB REGISTER REQUEST ACK message, or the purpose of the HeNB or the eNB ID is as follows: so that the HeNB knows whether the newly discovered HeNB or eNB is connected to the same X2 GW. Or,

(H) the eNB REGISTER REQUEST ACK message includes only the serving cell information or HeNB ID of the HeNB registered under X2 GW. Since the HeNB is connected to only one X2GW, while the eNB may be connected to multiple X2GW, the eNB needs to know which X2GW the newly discovered target HeNB is connected to. Therefore, when the eNB ID included in the (H) eNB REGISTER REQUEST message is 20 bits, which proves that the source of the registration procedure initiation is eNB, the HeNB serving cell information or HeNB ID registered under X2GW is included in the (H) eNB REGISTER REQUEST ACK message. When the eNB ID included in the (H) eNB REGISTER REQUEST message is 28 bits, and it is proved that the source end from which the registration procedure is initiated is the HeNB, the HeNB or eNB serving cell information registered under X2GW, or the HeNB ID or eNB ID may be optionally included in the (H) eNB REGISTER REQUEST ACK message.

(H) The eNB REGISTER REQUEST ACK message may further include the TNL address of the HeNB or eNB to which the serving cell belongs in the serving cell information of the HeNB or eNB registered under X2GW, so as to reduce the TNL address discovery procedure when establishing a connection between the HeNB and eNB pair or the HeNB and HeNB pair.

(H) The eNB REGISTER REQUEST ACK message may include the HeNB ID or eNB ID registered under X2GW, and may further include the TNL address of the HeNB or eNB, so as to reduce the TNL address discovery procedure when establishing a connection between the HeNB and eNB pair or between the HeNB and HeNB pair.

Fig. 4 is a schematic diagram illustrating registration failure in the present embodiment.

Step 402: if the registration fails, i.e. the X2GW cannot successfully store the matching relationship between the RNL ID and TNL address of the HeNB or eNB, the X2GW returns a new X2 response message to the HeNB or eNB, which is named (H) eNB REGISTER request message in this embodiment.

(H) The eNB REGISTER REQUEST FAILURE message includes one or more of a registration FAILURE cause, a minimum granted latency, and a critical diagnosis information element.

Example three:

the HeNB connected to X2GW may experience frequent power on and off. When the HeNB is powered off, the SCTP connection between X2GW and the HeNB is disconnected, but the HeNB or eNB of the opposite end cannot realize the SCTP connection between X2GW and the HeNB is disconnected. In this embodiment, the normal shutdown refers to a scenario in which the HeNB can know when to shut down, for example, a specific shutdown time is set. The abnormal shutdown refers to a scene of sudden power failure, so that the HeNB cannot know in advance when the HeNB is going to be shut down. The HeNB or eNB having a connection with the shutdown HeNB means that the HeNB or eNB having a connection can be known by means of a route storage record or the like.

Fig. 5 is a schematic diagram of notifying the HeNB or eNB connected to the powered-off HeNB of the information about the shutdown of the HeNB by using a registration procedure in this embodiment.

Step 501: when the HeNB is normally powered off, the HeNB may carry an identifier in an (H) eNB REGISTER REQUEST message to indicate that the HeNB is powered off before the HeNB is ready to be powered off, for example, a de-REGISTER identifier may be carried in an (H) eNB REGISTER REQUEST message to indicate that the HeNB is powered off.

Step 502: after receiving the (H) eNB REGISTER REQUEST message with identity, X2GW forwards the message to the HeNB or eNB with which the powered-off HeNB has a connection. The HeNB ID of the powered-off HeNB and an identity indicating that the HeNB has powered-off de-registration (Deregister) are included in the (H) eNBREGISTER REQUEST message.

When the HeNB is abnormally shut down, the HeNB may not predict in advance that shutdown is imminent, X2GW may find that the SCTP connection between itself and the HeNB is broken, and then initiate (H) an eNBREGISTER REQUEST message to the HeNB or eNB with which the shutdown HeNB has a connection. Included in the (H) eNB REGISTER REQUEST message is the HeNB ID of the powered-off HeNB discovered by X2GW and an identification indicating that the HeNB is powered-off.

Step 503: the HeNB or eNB, after obtaining the HeNB shutdown information, sends (H) an eNBREGISTER REQUEST ACK message to X2 GW.

Step 504: x2GW forwards the (H) eNB REGISTER REQUEST ACK message to the HeNB.

Fig. 6 is a schematic diagram of notifying a HeNB or an eNB having a connection with a shutdown HeNB of shutdown information using a deregistration procedure in this embodiment.

Step 601: when the HeNB is normally powered off, the HeNB sends a new X2 message, named HeNBDE-REGISTER in this embodiment, to X2GW to initiate a de-registration procedure before preparing to power off. The HeNB DE-REGISTER message includes the HeNBID of the powered-off HeNB.

Step 602: the X2GW forwards the HeNB DE-REGISTER message to the HeNB or eNB with which the powered-off HeNB has a connection.

When the HeNB is abnormally shut down, the HeNB cannot predict in advance that the shutdown is about to be performed, the X2GW can find that the SCTP connection between the HeNB and the HeNB is disconnected, and then an HeNBDE-REGISTER message is initiated to the HeNB or eNB which is connected with the shut-down HeNB. The HeNBDE-REGISTER message includes the HeNB ID of the powered-off HeNB.

Fig. 7 is a schematic diagram of notifying a HeNB connected to a shutdown HeNB or shutdown information about the HeNB by using a registration update procedure in this embodiment.

Step 701: when the HeNB is normally powered off, the HeNB sends a new X2 message, named (H) eNB REGISTER UPDATE in this embodiment, to the X2GW to initially perform a registration UPDATE procedure before preparing to power off. (H) The eNB REGISTER UPDATE message includes the HeNB ID of the HeNB to be powered off. When the powered-off HeNB is powered on again, the HeNB may send (H) an eNB REGISTER UPDATE to include the powered-on HeNB ID.

Step 702: x2GW forwards the (H) eNB REGISTER UPDATE message to the HeNB or eNB with which the powered-off HeNB has a connection.

When the HeNB is abnormally shut down, the HeNB may not predict in advance that shutdown is about to occur, X2GW may find that the SCTP connection between itself and the HeNB is disconnected, and then initiate (H) an eNB register update message to the HeNB that has a connection with the shutdown HeNB or vice versa. (H) The eNB register update message includes the HeNB ID of the HeNB to be powered off. When the powered-off HeNB is powered on again, X2GW may send (H) an eNB REGISTER UPDATE to include the powered-on HeNBID.

Example four:

after discovering the eNB cell, the HeNB sends an X2 establishment request message to the X2GW, but at the moment, the X2GW does not have the matching information of the RNL ID and the TNL address of the eNB, and the X2GW cannot route the X2 establishment request message to the newly discovered eNB. The present embodiment shows a procedure how to transmit the RNL ID and TNL address of the newly found eNB to the X2GW using a registration message so that the X2GW can correctly route the X2 setup request message.

Step 801: the HeNB completes the registration procedure on X2GW, which is described in the first embodiment, and therefore is not described again.

Step 802: after discovering the cell served by the eNB, the HeNB decides to establish an X2 connection to the eNB.

Step 803: the HeNB initiates an X2 setup request message with the target eNB ID identification to X2 GW.

Step 804: the X2GW has no matching relation between the RNL ID and the TNL address of the eNB, so that an X2 establishment failure message with a specific identifier is replied to the HeNB.

Step 805: and after receiving the X2 establishment failure message with the specific identification, the HeNB initiates a TNL address discovery process to acquire the TNL address of the eNB.

Step 806: the HeNB sends a new message to initiate the registration procedure, which in this embodiment is named (H) eNB REGISTER REQUEST. (H) The eNB REGISTER REQUEST message includes the RNL ID and TNL address of the eNB.

Step 807: after the registration is successful, that is, after the X2GW successfully stores the matching relationship between the RNL ID of the eNB and the TNL address, the X2GW returns a new response message to the HeNB, where the new response message is (H) eNB REGISTER REQUEST ACK in this embodiment.

Step 808: the HeNB initiates an X2 establishment request message with the ID of the target eNB to X2GW, and the X2GW routes the X2 establishment request message to the eNB according to the stored matching relation between the RNL ID and the TNL address of the eNB.

Step 809: the eNB replies an X2 establishment response message, and the X2GW routes the X2 establishment request message to the HeNB according to the stored matching relationship between the RNLID and the TNL address of the HeNB.

Example five:

in HeNB, the establishment of the current X2 interface is only for handover purposes. The HeNB includes the CSG ID and access mode information in a registration new message sent to X2GW, which is named (H) eNB REGISTER REQUEST in this embodiment. When the HeNB or eNB is registered with X2GW, the X2GW includes the CSG ID and access mode information of the HeNB registered under X2GW in the registration response message replied to the HeNB or eNB, which is called (H) eNB REGISTER REQUEST ACK in this embodiment. Since the current protocol is limited to the scenario of X2 handover, X2 handover from eNB to HeNB in closed mode, X2 handover from HeNB in open mode to HeNB in closed mode, X2 handover from HeNB in hybrid mode to HeNB in closed mode with different CSG ID, and X2 handover from HeNB in closed mode to closed HeNB with different CSG ID are excluded. The registration process is utilized to interact CSG ID and access mode information, which is beneficial to a HeNB or eNB terminal to judge and decide to initiate the establishment process of an X2 interface in a non-restricted scene, thereby avoiding the establishment of an X2 interface between a source and a target in a restricted scene. Of course, the HeNB may also carry the CSG ID and the access mode information in an (H) eNB REGISTER REQUEST sent to the X2GW, and in the X2 establishment procedure initiated by the HeNB or eNB, the X2GW determines whether to permit the establishment of the X2 interface between the source and the target according to the restriction scenario.

As shown in fig. 9, the present application also provides a base station, including: a first registration unit and a communication unit, wherein:

location information of the HeNB or eNB;

serving cell information of the HeNB or eNB;

closed member group identification and access mode information of the HeNB;

The base station further comprises a second registration unit, wherein:

The base station further comprises a judging unit, wherein:

The base station further comprises a third registration unit, wherein:

The base station further comprises a de-registration unit, wherein:

The base station further comprises a registration update unit, wherein:

The base station further comprises a reboot update unit, wherein:

As shown in fig. 10, the present application further provides an X2gateway, including: communication unit, matching relation save unit and response unit, wherein:

the communication unit is used for receiving and sending messages;

and the response unit is used for returning a registration response message.

And the matching relationship storage unit is further configured to store the matching relationship between the base station identifier of the opposite-end eNB and the TNL address after the communication unit receives the second registration request message, and return a response message.

The X2gateway further comprises a determination unit, wherein:

The response unit is specifically configured to, after successful registration, return a registration success response message carrying a message type cell, or a message type cell and a risk diagnosis cell, so that the HeNB or the eNB knows that the X2gateway has successfully stored the matching relationship between the base station identifier of the HeNB or the eNB and the TNL address.

The registration success response message also carries an X2gateway identifier.

The response unit also carries information in a registration success response message according to one of the following modes;

the first method is as follows:

the second method comprises the following steps:

The service cell information or the base station identification of the HeNB comprises a TNL address of the HeNB and/or a closed member group identification and access mode information of the HeNB;

The response unit is specifically used for returning a registration failure response message after the registration fails; the registration failure response message comprises one or more of the following information:

The X2gateway includes a notification element, wherein:

The X2gateway further comprises a notification unit, wherein:

The X2gateway further comprises a reboot notification unit, wherein:

While the invention has been described with reference to specific embodiments, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims.

It will be apparent to those skilled in the art that the modules or steps of the present invention described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and alternatively, they may be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, and in some cases, the steps shown or described may be performed in an order different than that described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple ones of them may be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.

Claims

1. A method for interaction between a base station and an X2gateway comprises a process of registering for the base station, wherein the process comprises the following steps:

location information of the HeNB or eNB;

serving cell information of the HeNB or eNB;

closed member group identification and access mode information of the HeNB;

2. The method of claim 1, further comprising a process for registering with other base stations, the process comprising:

3. The method of claim 1 or 2, wherein:

the first registration request message carries the closed member group identification and the access mode information of the HeNB, and the X2gateway stores the closed member group identification and the access mode information of the HeNB after receiving the first registration request message;

the method further comprises the following steps:

4. The method of claim 1, wherein:

and the X2gateway successfully registers, returns a registration success response message carrying a message type cell or a message type cell and a danger diagnosis cell, and leads the HeNB or the eNB to know that the X2gateway successfully stores the matching relation between the base station identifier of the HeNB or the eNB and the TNL address.

5. The method of claim 4, wherein:

the registration success response message also carries an X2gateway identifier.

6. The method of claim 4 or 5, wherein:

the X2gateway also carries information in a registration success response message according to one of the following modes;

the first method is as follows:

the second method comprises the following steps:

7. The method of claim 6, wherein:

8. The method of claim 1 or 2, wherein:

9. The method of claim 1 or 2, wherein:

the X2gateway fails to register and returns a registration failure response message; the registration failure response message comprises one or more of the following information:

10. The method of claim 1 or 2, further comprising:

11. The method of claim 1 or 2, further comprising a de-registration procedure comprising:

12. The method of claim 1 or 2, further comprising a process of registering updates, the process comprising:

13. The method of claim 1, further comprising a process of registering updates, the process comprising:

14. The method of claim 1 or 13, further comprising:

15. A base station, comprising: a first registration unit and a communication unit, wherein:

location information of the HeNB or eNB;

serving cell information of the HeNB or eNB;

closed member group identification and access mode information of the HeNB;

16. The base station of claim 15, further comprising a second registration unit, wherein:

17. The base station according to claim 15 or 16, further comprising a determining unit, wherein:

18. The base station of claim 15 or 16, further comprising a third registration unit, wherein:

19. The base station of claim 15 or 16, further comprising a de-registration unit, wherein:

20. The base station of claim 15 or 16, further comprising a registration update unit, wherein:

21. The base station of claim 15, further comprising a registration update unit, wherein:

22. The base station of claim 15 or 21, further comprising a reboot update unit, wherein:

23. An X2gateway, comprising: communication unit, matching relation save unit and response unit, wherein:

the communication unit is used for receiving and sending messages;

and the response unit is used for returning a registration response message.

24. The X2gateway of claim 23, wherein:

25. The X2gateway of claim 23 or 24, further comprising a determining unit, wherein:

26. The X2gateway of claim 23, wherein:

27. The X2gateway of claim 26, wherein:

the registration success response message also carries an X2gateway identifier.

28. The X2gateway of claim 26 or 27, wherein:

the first method is as follows:

the second method comprises the following steps:

29. The X2gateway of claim 28, wherein:

30. The X2gateway of claim 23 or 24, wherein:

31. The X2gateway of claim 23 or 24, further comprising a notification unit, wherein:

32. The X2gateway of claim 23 or 24, further comprising a notification unit, wherein:

33. The X2gateway of claim 23 or 24, further comprising a notification unit, wherein:

34. The X2gateway of claim 23, further comprising a notification unit, wherein:

35. The X2gateway of claim 23 or 34, further comprising a reboot notification unit, wherein: