Mobile Relay, and Method for Enhancing and Processing X2 Interface Proxy

Patent metadata

Field	Value
Publication number	US-2016007256-A1
Application number	US-201314764583-A
Country	US
Kind code	A1
Filing date	Dec 31, 2013
Priority date	Jan 31, 2013
Publication date	Jan 7, 2016
Grant date	—

Abstract

The embodiments of the present document disclose a mobile relay, and a method for enhancing and processing an X2 interface proxy. The method for enhancing an X2 interface proxy comprises: triggering an X2 proxy to relocate from a first node to a second node, or triggering to set up an X2 interface between a third node and the second node; and using the second node as an X2 proxy of the third node and a base station adjacent to the third node.

First claim

What is claimed is:

1 . A method for enhancing an (X2) interface proxy between two nodes, comprising:
triggering an X2 proxy to relocate from a first node to a second node, or triggering to set up an X2 interface between a third node and the second node; and using the second node as an X2 proxy of the third node and a base station adjacent to the third node.

2 . The method of claim 1 , wherein
the base station adjacent to the third node comprises an evolved Node B, a Relay Node, a mobile relay, a Pico or Home evolved Node B (HeNB), or, wherein triggering an X2 proxy to relocate from a first node to a second node, comprises: during or after handover, triggering the X2 proxy to relocate from the first node to the second node; and triggering to set up an X2 interface between a third node and the second node, comprises: during or after handover, triggering to set up the X2 interface between the third node and the second node.

3 . (canceled)

4 . The method of claim 1 , wherein, using the second node as an X2 proxy of the third node and a base station adjacent to the third node, comprises:
during a process that the X2 proxy relocates from the first node to the second node, triggering and activating the second node as the X2 proxy of the third node and the base station adjacent to the third node; or during or after the handover of the third node, the first node, the second node or the third node triggering and activating the second node as the X2 proxy of the third node and the base station adjacent to the third node.

5 . The method of claim 1 , wherein, using the second node as an X2 proxy of the third node and a base station adjacent to the third node, comprises:
carrying an activation indicator in an X2 setup process between the third node or the first node and the second node to use the second node as the X2 proxy of the third node and the base station adjacent to the third node; carrying the activation indicator in the X2 handover process or an S1 handover process of the third node from the first node to the second node to use the second node as the X2 proxy of the third node and the base station adjacent to the third node; carrying the activation indicator in a base station configuration update message between the third node or the first node and the second node; or after the X2 interface between the third node and the second node is set up, triggering the second node by default as the X2 proxy of the third node and the base station adjacent to the third node, preferably, wherein, carrying the activation indicator in the X2 handover process or an S1 handover process of the third node from the first node to the second node, comprises: carrying the activation indicator in a handover request message sent from the first node to the second node, or carry the activation indicator in an radio resource control (RRC) connection reconfiguration complete message sent from the third node to the second node.

6 . (canceled)

7 . (canceled)

8 . A method for processing an X2 proxy between two nodes, comprising:
a third node sending an X2 message to at least one X2 proxy node; an X2 proxy node, which has received the X2 message and has an X2 interface with a target cell, sending the X2 message to the target cell; and the third node receiving a response replied by the X2 proxy node which sends the X2 message to the target cell.

9 . The method of claim 8 , wherein, a third node sending an X2 message to at least one X2 proxy node, comprises:
the third node carrying a same identifier in the various X2 messages sent to at least one X2 proxy node to indicate same information or operation.

10 . The method of claim 8 , further comprising:
according to known information of neighboring cells of a first X2 proxy node and a second X2 proxy node, and information of the target cell to which the X2 message is to be sent, the third node determining to send the X2 message to one of the X2 proxy nodes.

11 . The method of claim 10 , wherein, determining to send the X2 message to one of the X2 proxy nodes, comprises:
the third node determining to send the X2 message to the X2 proxy node whose neighboring cells include the target cell.

12 . The method of claim 8 , further comprising:
deactivating the X2 proxy function of the X2 proxy node.

13 . The method of claim 12 , wherein, deactivating the X2 proxy function of the X2 proxy node, comprises:
carrying a deactivation indicator in an X2 proxy releasing process or an X2 interface releasing process between the third node and the X2 proxy node, to deactivate the X2 proxy function of the X2 proxy node; or when the X2 interface between the third node and the X2 proxy node is released, deactivating the X2 proxy function of the X2 proxy node by default.

14 . The method of claim 8 , further comprising:
the third node receiving a proxy failure response replied by the X2 proxy node which has received the X2 message but cannot perform the X2 proxy, preferably, wherein, the proxy failure response carries reason information for proxy failure;
more preferably, wherein,
the reason information for proxy failure comprises that the same information or operation is sent repeatedly, load exceeds a preset threshold, network failure, there is no X2 interface with the target cell, or the target cell is not the neighboring cell.

15 . The method of claim 8 , further comprising:
a plurality of X2 proxy nodes sending the X2 message indicating same information or a same operation to the target cell, and after receiving a first X2 message, the target cell replying the proxy failure response to a sender of the X2 message which has been received repeatedly, and the X2 proxy nodes, which have received the proxy failure response, replying the proxy failure response to the third node; or one of the X2 proxy nodes which have received the X2 message, sending the X2 message to the target cell, and sending indication information that the X2 proxy has been performed to other X2 proxy nodes which have received the X2 message and have an X2 interface with the target cell; the X2 proxy nodes, which have received the indication information that the X2 proxy has been preformed, sending the proxy failure response to the third node, preferably, wherein, the proxy failure response carries reason information for proxy failure;
more preferably, wherein,
the reason information for proxy failure comprises that the same information or operation is sent repeatedly, load exceeds a preset threshold, network failure, there is no X2 interface with the target cell, or the target cell is not the neighboring cell.

16 . The method of claim 15 , wherein the method comprises:
after receiving the X2 message, according to the previously known information of the neighboring cell of the second X2 proxy node, the first X2 proxy node determining that the target cell of the X2 message is a neighboring cell of both the first X2 proxy node and the second X2 proxy node; the first X2 proxy node sending a corresponding X2 message to the target cell, and indicating to the second X2 proxy node that the X2 proxy of the X2 message has been performed; and after receiving the X2 message sent from the third node and the indicator that the first X2 proxy node has performed the X2 proxy of the X2 message, the second X2 proxy node replying the proxy failure response to the third node, preferably, wherein, the proxy failure response carries reason information for proxy failure;
more preferably, wherein,
the reason information for proxy failure comprises that the same information or

Assignees

• Zte Corp

Inventors

• Chu Li
• Liu Yulan
• Gao Yin
• Huang Ying
• Chen Lin

Classifications

• H04W36/08 Primary

  Reselecting an access point · CPC title

• H04W92/10

  between terminal device and access point, i.e. wireless air interface · CPC title

• H04W36/0064

  of control information between different access points · CPC title

• H04W84/047

  using dedicated repeater stations · CPC title

• H04W92/20

  between access points · CPC title