Synchronization method, radio network and node
Abstract
A synchronization method, a communication handover method, a radio network, and a RAN node are disclosed. The interface information synchronization method includes: judging whether a condition for initiating interface information update is fulfilled; and sending information about the S 1 interface between the RAN node and the core network node, and/or information about the X2 interface between the RAN node and the neighboring RAN node to the neighboring RAN node if the condition for initiating interface information update fulfilled.
Term
1.6 yearsto projected expiry
Projected expiry 24 April 2028, counted from filing; an application has no term until it is granted.
- Priority
- Filed
- Published
- Today
- Projected expiry
19 claims: 12 independent, 7 dependent
- 1An interface information synchronization method, comprising:judging whether a condition for initiating interface information update is fulfilled;sending information about an S 1 interface between a Radio Access Network, RAN, node and a core network node, and/or information about an X2 interface between the RAN node and a neighboring RAN node to the neighboring RAN node if the condition for initiating interface information update is fulfilled.
- 8The method of the claim 1, wherein judging whether a condition for initiating interface information update is fulfilled comprises:if S 1 interface handover is performed and the core network node receives a handover request message from the neighboring RAN node serving as a source node, judging whether the S 1 interface between the RAN node serving as a target node and the core network node is the same as the S1 interface between the neighboring RAN node serving as the source target and the core network node;if the S1 interface between the target node and the core network node is the same as the S1 interface between the source target and the core network node, sending the S 1 and/or X2 interface information to the neighboring RAN node comprises: sending, by the core network node initiatively, the S 1 interface information of the RAN node to the neighboring RAN node;or, initiating the RAN node to send the S1 interface information to the neighboring node.
- 10A communication handover method, comprising:reading, by a source Radio Access Network, RAN, node, stored interface handover entries, wherein, when handover occurs, the interface handover entries include information indicating whether the handover can be performed to the target RAN node through an S1 interface, and the interface handover entries are obtained according to the S 1 and/or an X2 interface information;performing the handover through the S1 interface if the interface handover entries indicate that the handover can be performed to the target RAN node through the S1 interface;otherwise, performing the handover through the X2 interface.
- 11The method of the claim 10, wherein the interface handover entries are obtained according to the S1 and/or X2 interface information comprises:obtaining interface information, wherein the interface information comprises whether the source RAN node and the target RAN node have a same core network node;if the same core network node does not exist, recording information about performing the handover to the target TAN node through the S 1 interface.
- 12The method of the claim 10, wherein the information indicating whether the handover can be performed to the target RAN node through the S1 interface comprises:whether the interface handover entries store the target RAN node;wherein the interface handover entries including the information that the handover can be performed through the S 1 interface to the target RAN node means that the interface handover entries includes the target RAN node.
- 13A communication handover method, comprising:reading, by a source Radio Access Network, RAN, node, interface information when handover occurs, wherein the interface information includes information about whether an X2 interface exists between the source RAN node and a target RAN node and/or information about whether an S1 interface exists between a serving core network of the source RAN node and the RAN node;performing handover through the X2 interface if the interface information indicates that the X2 interface exists between the source RAN node and the target RAN node and/or the S1 interface exists between the serving core network node of the source RAN node and the target RAN node;otherwise, performing handover through the S 1 interface.
- 15A radio network, comprising a first Radio Access Network, RAN, node, a second RAN node, and a serving core network node of the second RAN node; wherein the first RAN node comprises:a judging unit, adapted to judge whether a condition for initiating interface information update is fulfilled;and a sending unit, adapted to send information about an X2 interface between the first RAN node and the second RAN node and/or information about an S1 interface between the first RAN node and the serving core network node to the second RAN node if the condition for initiating interface information update is fulfilled;the second RAN node comprises: a receiving unit, adapted to receive the S 1 and/or X2 interface information;a handover selecting unit, adapted to search for the interface information;if finding information about the X2 interface between the first RAN node and the second RAN node and determining that an S1 interface connection exists between the serving core network node and the first RAN node according to the S1 interface information, initiate a handover operation to the first RAN node through the X2 interface;otherwise, initiate the handover operation to the first RAN node through the S 1 interface.
- 16The radio network of the claim 15, wherein the judging unit is adapted to perform anyone of:judging whether the S 1 and/or X2 interface information is changed;judging whether a timer of the S1 and/or X2 interface information expires;judging whether received information from the second RAN node requesting the S 1 and/or X2 interface information;judging whether the handover operation initiated by the second RAN node to the first RAN node through the X2 interface fails;judging whether the first RAN node is restarted;judging whether an Element Manager System, EMS, of the first RAN node has modified the interface information of the first RAN node.
- 17A Radio Access Network, RAN, node, comprising:a judging unit, adapted to judge whether a condition for initiating interface information update is fulfilled;and a sending unit, adapted to send information about an X2 interface between the RAN node and a neighboring RAN node and/or information about an S 1 interface between the RAN node and a core network node to the neighboring RAN node if the judging unit determines that condition for initiating interface information update is fulfilled.
- 18A Radio Access Network, RAN, node, comprising:a receiving unit, adapted to receive S 1 and/or X2 interface information from a neighboring RAN node;a processing unit, adapted to configure or update the interface information of the neighboring RAN node after the receiving unit receives the S1 and/or X2 interface information;and a handover selecting unit, adapted to search the processing unit for the interface information;if finding the information about the X2 interface between the RAN node and the neighboring RAN node as well as the information about the S1 interface between a serving core network node of the RAN node and the neighboring RAN node, select the X2 interface for initiating a handover operation to the neighboring RAN node;otherwise, select the S1 interface for initiating the handover operation to the neighboring RAN node.
- 19A Radio Access Network, RAN, node, comprising:a receiving unit, adapted to receive S1 and/or X1 interface information from a neighboring RAN node;an interface information generating unit, adapted to judge whether a core network node of the RAN node serving as a source node is the same as a core network node of the neighboring RAN node serving as a target node according to the interface information of the RAN node and the S 1 and/or X1 interface information received by the receiving unit;and generate handover information indicative of handing over to the target RAN node through an S 1 interface if the core network node of the RAN node serving as the source node is not same as the core network node of the neighboring RAN node serving as the target node;and a handover selecting unit, adapted to search for the handover information generated by the interface information generating unit during the handover;if finding the information about the handover performed through the S 1 interface to the target RAN node, select the S2 interface for initiating a handover operation to the neighboring RAN node;otherwise, select the X2 interface for initiating a handover operation to the neighboring RAN node.
Independent claims12
102 paragraphs in 5 sections, as filed
FIELD OF THE INVENTION
0001The present invention relates to the communication field, and in particular, to an interface information synchronization method, a communication handover method, a radio network, and a Radio Access Network (RAN) node.
BACKGROUND
0002The Long Term Evolution/System Architecture Evolution (LTE/SAE) network system project is the biggest new technology development project launched by the 3rd Generation Partnership Project (3GPP) in recent years. The core of such a technology is Orthogonal Frequency Division Multiplexing (OFDM)/Frequency Division Multiple Access (FDMA), and therefore, such a technology has some 4<sup>th</sup> Generation (4G) features and is regarded as a quasi-4G technology. <figref idref="f0001">FIG. 1</figref> shows an architecture of an LTE/SAE in the prior art. The LTE/SAE network system includes an evolved Node B (eNB, an evolved RAN node) and the Mobility Management Entity/Serving System Architecture Evolution Gateway (MME/SGW) that manages the RAN nodes. The interface between the MME/SGW and the eNB is an S1 interface, and the interface between eNBs is an X2 interface.
0003In the current LTE, the communication handover process falls into two types: handover from a source eNB to a target eNB through an X2 interface; and handover from a source eNB to a target eNB through an S 1 interface, as described below:
0004Handover through an X2 interface: In the handover process, the source eNB and the target eNB are governed by the same MME; the MME is unchanged; and the source eNB sends a Handover Request message to the target eNB through an X2 interface to perform handover. In this case, the handover process involves no MME, and is known as handover through an X2 interface. The handover performed through an X2 interface involves use of an S1 interface.
0005Handover through an S 1 interface: When the MME involved in the handover process changes, namely, when the source eNB and the target eNB are not governed by the same MME, the source eNB needs to send a Handover Request message through an S 1 interface, which is known as handover through an S 1 interface.
0006When an eNB initiates handover, as regards how to select either of the foregoing handover methods, the prior art puts forward the following eNB handover selection method: <ul id="ul0001" list-style="none" compact="compact"><li>A. If no X2 interface exists, the handover is performed through the S 1 interface.</li><li>B. If the handover configured in the source eNB to the neighboring target eNB is performed through an S 1 interface, the handover is performed through the S 1 interface. In this method, a static table is reserved in the source eNB first, and a decision is made about whether to perform handover through an S1 interface or an X2 interface according to the interface connection information related to the neighboring eNB and recorded in the static table. However, the prior art describes neither the structure of such a static table nor information about how to use the static table to perform communication handover. </li><li>C. If a rejection message is received from the target eNB during the X2 interface handover, it indicates that the handover cannot be performed through an X2 interface, and therefore, the handover is performed through an S1 interface.</li></ul>
0007In this method, the Handover Request is sent through an X2 interface so long as an X2 interface connection exists. If the target eNB finds it impossible to perform handover through an X2 interface, for example, if it is determined that the same MME connection is lacking, the target eNB sends a handover failure message to the source eNB. The handover failure message carries the corresponding cause value, and instructs the source eNB to send a Handover Require message to the MME again through an S 1 interface. In the process of developing the present invention, the inventor finds at least the following defects in the prior art: <ol id="ol0001" compact="compact"><li>(1) For solution B, the source eNB needs to know the static configuration of the relevant interface of the neighboring eNB. Data needs to change with the change of the configuration of the neighboring eNB. Manual modification of the static configuration consumes much time and effort, and is vulnerable to errors. Besides, the prior art describes neither the structure of the static table nor the information about how to use the static table to perform communication handover.</li><li>(2) In solution C, for the handover which can be performed only through the S 1 interface, sending a Handover Request first through the X2 interface is necessary, which wastes resources and increases delay. According to the X2 interface handover process in the prior art, the target eNB can set up air interface resources upon receiving a Handover Request. However, if solution C is applied, the target eNB needs to judge whether X2 interface handover is practicable after receiving a Handover Request, thus increasing futile operations for the X2 interface-enabled handover processes.</li></ol>
SUMMARY
0008The present invention discloses an interface information synchronization method, a communication handover method, a radio network, and a RAN node, thus improving the efficiency of communication handover.
0009An interface information synchronization method is disclosed in an embodiment of the present invention. The method includes: judging whether a condition for initiating interface information update is fulfilled; sending information about an S 1 interface between a RAN node and a core network node, and/or information about an X2 interface between the RAN node and a neighboring RAN node to the neighboring RAN node if the condition for initiating interface information update is fulfilled. A communication handover method is disclosed in an embodiment of the present invention. The method includes: <ul id="ul0002" list-style="none" compact="compact"><li>reading, by a source RAN node, a stored interface handover entries when handover occurs, where the interface handover entries include information indicating whether the handover can be performed to the target RAN node through an S1 interface, and the interface handover entries are obtained according to the S 1 and/or an X2 interface information; and</li><li>performing the handover through the S1 interface if the interface handover entries include the information that the handover can be performed to the target RAN node through the S 1 interface; otherwise, performing the handover through the X2 interface.</li></ul> A communication handover method is disclosed in an embodiment of the present invention. The method includes: <ul id="ul0003" list-style="none" compact="compact"><li>reading, by a source RAN node, interface information when handover occurs, where the interface information includes information about whether an X2 interface exists between the source RAN node and a target RAN node and/or information about whether an S1 interface exists between a serving core network of the source RAN node and the RAN node; and</li><li>performing handover through the X2 interface if the interface information indicates that the X2 interface exists between the source RAN node and the target RAN node and/or the S1 interface exists between the serving core network node of the source RAN node and the target RAN node; otherwise, performing handover through the S 1 interface.</li></ul> A radio network is disclosed in an embodiment of the present invention. The radio network includes a first RAN node, a second RAN node, and a serving core network node of the second RAN node.
0010The first RAN node includes: <ul id="ul0004" list-style="none" compact="compact"><li>a judging unit, adapted to judge whether a condition for initiating interface information update is fulfilled; and</li><li>a sending unit, adapted to send information about an X2 interface between the first RAN node and the second RAN node and/or information about an S1 interface between the first RAN node and the serving core network node to the second RAN node if the condition for initiating interface information update is fulfilled.</li></ul>
0011The second RAN node includes: <ul id="ul0005" list-style="none" compact="compact"><li>a receiving unit, adapted to receive the S 1 and/or X2 interface information;</li><li>a handover selecting unit, adapted to search for the interface information; if finding information about the X2 interface between the first RAN node and the second RAN node and determining that an S1 interface connection exists between the serving core network node and the first RAN node according to the S1 interface information, initiate a handover operation to the first RAN node through the X2 interface; otherwise, initiate the handover operation to the first RAN node through the S1 interface.</li></ul> A RAN node is disclosed in an embodiment of the present invention. The RAN node includes: <ul id="ul0006" list-style="none" compact="compact"><li>a judging unit, adapted to judge whether a condition for initiating interface information update is fulfilled; and</li><li>a sending unit, adapted to send information about an X2 interface between the RAN node and a neighboring RAN node and/or information about an S1 interface between the RAN node and a core network node to the neighboring RAN node if the judging unit determines that the condition for initiating interface information update is fulfilled.</li></ul> A RAN node is disclosed in an embodiment of the present invention. The RAN node includes: <ul id="ul0007" list-style="none" compact="compact"><li>a receiving unit, adapted to receive S 1 and/or X2 interface information from a neighboring RAN node;</li><li>a processing unit, adapted to configure or update the interface information of the neighboring RAN node after the receiving unit receives the S1 and/or X2 interface information; and</li><li>a handover selecting unit, adapted to search the processing unit for the interface information; if finding the information about the X2 interface between the RAN node and the neighboring RAN node as well as the information about the S1 interface between a serving core network node of the RAN node and the neighboring RAN node, select the X2 interface for initiating a handover operation to the neighboring RAN node; otherwise, select the S1 interface for initiating the handover operation to the neighboring RAN node.</li></ul> A RAN node is disclosed in an embodiment of the present invention. The RAN node includes: <ul id="ul0008" list-style="none" compact="compact"><li>a receiving unit, adapted to receive S1 and/or X1 interface information from a neighboring RAN node;</li><li>an interface information generating unit, adapted to judge whether a core network node of the RAN node serving as a source node is the same as a core network node of the neighboring RAN node serving as a target node according to the interface information of the RAN node and the S1 and/or X1 interface information received by the receiving unit; and generate handover information indicative of handing over to the target RAN node through an S1 interface if the core network node of the RAN node serving as the source node is not same as the core network node of the neighboring RAN node serving as the target node; and</li><li>a handover selecting unit, adapted to search for the handover information generated by the interface information generating unit during the handover; if finding the information about the handover performed through the S1 interface to the target RAN node, select the S2 interface for initiating a handover operation to the neighboring RAN node; otherwise, select the X2 interface for initiating a handover operation to the neighboring RAN node.</li></ul> As described above, in an embodiment of the present invention, the information about the S1 interface between the RAN node and the core network node, and/or information about the X2 interface between the RAN node and the neighboring RAN node is sent to the neighboring RAN node if the condition is fulfilled. When the neighboring RAN node hands over to the RAN node, the neighboring RAN node can determine whether an S 1 interface exists between the neighboring RAN node itself and the core network according to its own S 1 interface information and the received S 1 interface information, and can accurately determine the interface available for handover according to the received X2 interface information. Therefore, the proper interface is selected accurately and quickly, the trouble of judging whether the X2 interface is available for handover in the case of unawareness of the interface information in the prior art is avoided, the handover efficiency is improved, and the system load is reduced. In another embodiment of the present invention, the interface information or the interface handover table is read when handover is performed; a proper interface is selected for handover according to the interface handover requirement recorded in the interface handover table or according to the interface which is determined as available for handover in view of the interface information. The determining mode is: A Handover Request is sent through the X2 interface if the interface information indicates that an X2 interface exists between the source RAN node and the target RAN node and/or an S1 interface exists between the serving core network node of the source RAN node and the target RAN node; otherwise, the Handover Request is sent through an S 1 interface. Therefore, the proper interface is selected accurately and quickly. The trouble of judging whether the X2 interface is available for handover in the case of unawareness of the interface information in the prior art is avoided, the handover efficiency is improved, and the system load is reduced. In another embodiment of the present invention, a judging unit judges whether the interface information needs update, and a sending unit sends the interface information to the neighboring RAN node to synchronize the interface information. The handover selecting unit of the neighboring RAN node may select a proper interface for handover according to interface handover requirement recorded in the interface handover table, or according to the interface available for handover determined in view of the interface information. The judging mode is: A Handover Request is sent through the X2 interface if the interface information indicates that an X2 interface exists between the source RAN node and the target RAN node and/or an S1 interface exists between the serving core network node of the source RAN node and the target RAN node; otherwise, the Handover Request is sent through an S1 interface. Therefore, the proper interface is selected accurately and quickly. The trouble of judging whether the X2 interface is available for handover in the case of unawareness of the interface information in the prior art is avoided, the handover efficiency is improved, and the system load is reduced. In another embodiment of the present invention, interface information may be transmitted between neighboring RAN nodes. Therefore, the RAN node knows the interface information of the neighboring RAN node, and such interface information is a basis for selecting a specific interface for handover. The two technical solutions can work together to select a proper interface for handover accurately and efficiently, and reduce system load.
BRIEF DESCRIPTION OF THE DRAWINGS
0012<ul id="ul0009" list-style="none" compact="compact"><li><figref idref="f0001">FIG. 1</figref> shows a structure of an LTE/SAE network in the prior art;</li><li><figref idref="f0001">FIG. 2</figref> is a flowchart of a communication handover method in an embodiment of the present invention;</li><li><figref idref="f0002">FIG. 3</figref> shows X2 and S1 interface connections in an LTE/SAE network;</li><li><figref idref="f0002">FIG. 4</figref> is a flowchart of interface information synchronization method in another embodiment of the present invention;</li><li><figref idref="f0003">FIG. 5</figref> is a flowchart of a communication handover method in an embodiment of the present invention;</li><li><figref idref="f0003">FIG. 6</figref> is a signaling flowchart of interface information synchronization method in another embodiment of the present invention;</li><li><figref idref="f0004">FIG. 7</figref> is a signaling flowchart of interface information synchronization method in another embodiment of the present invention;</li><li><figref idref="f0004">FIG. 8</figref> is a signaling flowchart of interface information synchronization method in another embodiment of the present invention;</li><li><figref idref="f0005">FIG. 9</figref> shows a structure of a radio network in an embodiment of the present invention; and</li><li><figref idref="f0005">FIG. 10</figref> shows a structure of a RAN node in an embodiment of the present invention.</li></ul>
DETAILED DESCRIPTION
0013A communication handover method is disclosed in an embodiment of the present invention. The method includes: <ul id="ul0010" list-style="none" compact="compact"><li>A RAN node stores the information about the X2 interface between the RAN node and a neighboring RAN node, and/or the information about the S 1 interface between the neighboring RAN node and a core network node. The information about the X2 interface or the S 1 interface may be interface configuration information and/or interface state information. The configuration information and/or state information constitute a configuration table (S1 or X2 interface configuration table of the RAN node).</li></ul>
0014If the S1 or X2 interface configuration/state of the RAN node changes, the RAN node sends the changed S 1 or X2 interface configuration/state information to the neighboring RAN node, notifying the neighboring RAN node to modify the corresponding S1 or X2 interface configuration table.
0015Therefore, RAN nodes in the communication network have the latest S1 or X2 interface configuration table. When handover occurs, the source RAN node searches for the configuration information of the target RAN node in the S1 or X2 interface configuration table. A procedure is used to perform handover from a source RAN node to a target RAN node using X2 interface when S1 interface exists between the target RAN node and a serving core network node of the source RAN node. Otherwise the S1-based handover procedure is used.
0016A communication handover method is disclosed in an embodiment of the present invention. The method includes: <ul id="ul0011" list-style="none" compact="compact"><li>The S 1 interface information between the RAN node and the core network node is transmitted to the neighboring RAN node through an X2 interface. The neighboring RAN node generates an S1 interface handover table according to the S 1 interface information of the neighboring RAN node itself and the received S 1 interface information, where the S 1 interface handover table indicates whether the handover is necessarily performed through the S1 interface. The S1 interface handover table is stored dynamically. Whenever the S 1 interface configuration/state of the neighboring RAN node changes, the change is notified to the RAN node through the X2 interface. The RAN node modifies the S 1 interface handover table according to the S 1 interface information. When handover occurs, the source RAN node searches the S 1 interface handover table for the target RAN node. If finding the target RAN node, the source RAN node selects the S 1 interface for handover; otherwise, the source RAN node selects the X2 interface for handover. Through the method disclosed in the embodiment of the present invention, the RAN nodes may exchange S1 interface information and/or X2 interface information automatically through automatic configuration of the network. More specifically, the interface information for exchanging is: both S 1 interface information and X2 interface information; only S 1 interface information; or only X2 interface information.</li></ul>
0017The RAN node may be an eNB, and the core network node may be an MME.
0018An interface information synchronization method is disclosed in an embodiment of the present invention. The method includes: <ul id="ul0012" list-style="none" compact="compact"><li>judging whether a condition for initiating interface information update is fulfilled;</li><li>sending information about the S1 interface between the RAN node and the core network node, and/or information about the X2 interface between the RAN node and the neighboring RAN node to the neighboring RAN node if the condition for initiating interface information update is fulfilled;</li><li>receiving the S 1 and/or X2 interface information; and</li><li>configuring or updating the interface information of the neighboring RAN node according to the received S 1 and/or X2 interface information.</li></ul>
0019In the embodiment described above, the S1 and/or X2 interface information of the RAN node is sent to the neighboring RAN node when the condition is fulfilled. When the neighboring RAN node hands over to the RAN node, the neighboring RAN node can determine whether an S1 interface exists between the neighboring RAN node itself and the core network according to its own S 1 interface information and the received S 1 interface information, and can accurately determine the interface available for handover according to the received X2 interface information. Therefore, the proper interface is selected accurately and quickly, the trouble of judging whether the X2 interface is available for handover in the case of unawareness of the interface information in the prior art is avoided, the handover efficiency is improved, and the system load is reduced.
0020In the communication handover method disclosed in the embodiment of the present invention, when handover occurs, the source RAN node reads the stored interface handover table (the interface handover table includes the information indicating whether the handover can be performed through an S 1 interface to the target RAN node). The source RAN node performs handover through the S 1 interface if the interface handover table indicates that the handover can be performed through the S1 interface to the target RAN node; otherwise, the source RAN node performs handover through the X2 interface. Therefore, the proper interface is selected accurately and quickly. The trouble of judging whether the X2 interface is available for handover in the case of unawareness of the interface information in the prior art is avoided, the handover efficiency is improved, and the system load is reduced.
0021In the communication handover method disclosed in the embodiment of the present invention, the source RAN node reads interface information when handover occurs, the interface information includes the information about whether an X2 interface exists between the source RAN node and the target RAN node and/or the information about whether an S 1 interface exists between the serving core network node of the source RAN node and the target RAN node. The source RAN node performs handover through the X2 interface if the interface information indicates that an X2 interface exists between the source RAN node and the target RAN node and/or an S 1 interface exists between the serving core network node of the source RAN node and the target RAN node; or else performs handover through the S1 interface. Therefore, the proper interface is selected accurately and quickly. The trouble of judging whether the X2 interface is available for handover in the case of unawareness of the interface information in the prior art is avoided, the handover efficiency is improved, and the system load is reduced.
0022In the communication handover method disclosed in the embodiment of the present invention, the interface information or the interface handover table is read when handover occurs, a proper interface is selected for handover according to the interface handover requirement recorded in the interface handover table or according to the interface which is determined as available for handover in view of the interface information. The judging mode is: A Handover Request is sent through the X2 interface if the interface information includes the information about the X2 interface exists between the source RAN node and the target RAN node and the information about the S1 interface exists between the serving core network node of the source RAN node and the target RAN node; otherwise, the Handover Request is sent through an S1 interface. Therefore, the proper interface is selected accurately and quickly. The trouble of judging whether the X2 interface is available for handover in the case of unawareness of the interface information in the prior art is avoided, the handover efficiency is improved, and the system load is reduced.
0023In order to make the technical solution, objectives and merits of the present invention clearer, the communication handover method under the present invention is detailed below by reference to <figref idref="f0001">FIG. 2</figref>.
0024<figref idref="f0001">FIG. 2</figref> is a flowchart of a communication handover method in an embodiment of the present invention. The process includes at least the following steps: <ul id="ul0013" list-style="none" compact="compact"><li>Step 201: The source RAN node reads S 1 and X2 interface information when handover occurs, the interface information includes the information about whether an X2 interface exists between the source RAN node and the target RAN node and/or the information about whether an S1 interface exists between the serving core network node of the source RAN node and the target RAN node.</li></ul>
0025As described above, the S 1 and the X2 interface information may exist in the form of S 1 and X2 interface configuration table, and may be stored on the source RAN node. Taking the LTE/SAE network shown in <figref idref="f0002">FIG. 3</figref> as an example, RAN node 1 is adjacent to RAN nodes 2 and 3 in the network, and an X2 interface exists between them.
0026Table 1 is an exemplary structure of an S 1 or X2 interface configuration table in the network. For example, in <figref idref="f0002">FIG. 3</figref>, RAN node 1 is adjacent to RAN nodes 2 and 3, and an X2 interface exists between them. RAN node 1 may store the following table: <tables id="tabl0001" num="0001"><table frame="all"><title>Table 1: S 1 or X2 interface configuration table of RAN node 1</title><tgroup cols="4"><colspec colnum="1" colname="col1" colwidth="23mm" /><colspec colnum="2" colname="col2" colwidth="34mm" /><colspec colnum="3" colname="col3" colwidth="34mm" /><colspec colnum="4" colname="col4" colwidth="34mm" /><thead><row><entry valign="top">RAN node</entry><entry valign="top">core network node 1</entry><entry valign="top">core network node 2</entry><entry valign="top">core network node 3</entry></row></thead><tbody><row><entry>RAN node 2</entry><entry>0</entry><entry>1</entry><entry>1</entry></row><row><entry>RAN node 3</entry><entry>0</entry><entry>0</entry><entry>1</entry></row></tbody></tgroup></table></tables>
0027The first column of the table is the information about the neighboring RAN node. The first column includes RAN node 2 and RAN node 3. An X2 interface exists between RAN node 1 and RAN nodes 2 and 3. If the column has no name of a RAN node, it indicates that no X2 interface exists between RAN node 1 and the RAN node.
0028The first row of the table indicates the relevant core network nodes, and the content below the second row indicates whether an S 1 interface exists between each neighboring RAN node and the relevant core network node. "1" indicates that an S1 interface exists between a RAN node and the relevant core network node; and "0" indicates that no S 1 interface exists between them. The foregoing table reveals that: An S1 interface exists between RAN node 2 and core network nodes 2 and 3, but no S1 interface exists between RAN node 2 and core network node 1; an S1 interface exists between RAN node 3 and core network node 3, but no S1 interface exists between RAN node 3 and core network node 1 or 2.
0029In this case, when the source RAN node knows existence of an S1 interface between the source RAN node and the relevant core network node, according to the second row and the content below the second row, the source RAN node may infer whether an S 1 interface exists between the serving core network of the source RAN node and other neighboring RAN nodes. For example, if RAN node 2 and the serving core network node 2 of RAN node 1 correspond to the position "1" in the table but RAN node 1 already knows that an S 1 interface exists between RAN node 1 and core network node 2, it is inferred that an S1 interface exists between RAN node 1 and the serving core network node 2 of RAN node 2.
0030Obviously, the first column of the table indicates whether an X2 interface exists between the source RAN node and other neighboring RAN nodes. The second row of the table indicates whether an S1 interface connection exists between the neighboring RAN node and the core network node. The source RAN node may infer whether an S1 interface exists between the serving core network node of the source RAN node and the neighboring RAN node according to the S 1 interface information of the source RAN node and the S 1 interface information below the second row in the table. Likewise, other neighboring RAN nodes also store similar configuration tables for communication handover. Table 2 and Table 3 are examples: <tables id="tabl0002" num="0002"><table frame="all"><title>Table 2: S1 or X2 interface configuration table of RAN node 2</title><tgroup cols="4"><colspec colnum="1" colname="col1" colwidth="23mm" /><colspec colnum="2" colname="col2" colwidth="34mm" /><colspec colnum="3" colname="col3" colwidth="34mm" /><colspec colnum="4" colname="col4" colwidth="34mm" /><thead><row><entry valign="top">RAN node</entry><entry valign="top">Core network node 1</entry><entry valign="top">Core network node 2</entry><entry valign="top">Core network node 3</entry></row></thead><tbody><row><entry>RAN node 1</entry><entry>1</entry><entry>1</entry><entry>0</entry></row></tbody></tgroup></table></tables><tables id="tabl0003" num="0003"><table frame="all"><title>Table 3: S1 or X2 interface configuration table of RAN node 3</title><tgroup cols="4"><colspec colnum="1" colname="col1" colwidth="23mm" /><colspec colnum="2" colname="col2" colwidth="34mm" /><colspec colnum="3" colname="col3" colwidth="34mm" /><colspec colnum="4" colname="col4" colwidth="34mm" /><thead><row><entry valign="top">RAN node</entry><entry valign="top">core network node 1</entry><entry valign="top">core network node 2</entry><entry valign="top">core network node 3</entry></row></thead><tbody><row><entry>RAN node 1</entry><entry>1</entry><entry>1</entry><entry>0</entry></row></tbody></tgroup></table></tables>
0031Nevertheless, the RAN node may also add its own S1 interface information into the first row of the foregoing configuration table. The second row and the content below it are the information about the neighboring RAN node, as shown in Table 4: <tables id="tabl0004" num="0004"><table frame="all"><title>Table 4: S1 or X2 interface configuration table of RAN node 1</title><tgroup cols="4"><colspec colnum="1" colname="col1" colwidth="23mm" /><colspec colnum="2" colname="col2" colwidth="34mm" /><colspec colnum="3" colname="col3" colwidth="34mm" /><colspec colnum="4" colname="col4" colwidth="34mm" /><thead><row><entry valign="top">RAN node</entry><entry valign="top">Core network node 1</entry><entry valign="top">Core network node 2</entry><entry valign="top">Core network node 3</entry></row></thead><tbody><row><entry>RAN node 1</entry><entry>1</entry><entry>1</entry><entry>0</entry></row><row><entry>RAN node 2</entry><entry>0</entry><entry>1</entry><entry>1</entry></row><row><entry>RAN node 3</entry><entry>0</entry><entry>0</entry><entry>1</entry></row></tbody></tgroup></table></tables>
0032In this way, according to the information in Table 4, when RAN node 1 serves as a source RAN node, it is easy to determine whether an S1 interface exists between the source RAN node and a core network node, and whether an S1 interface exists between another neighboring RAN node and the core network node.
0033When handover needs to occur on the source RAN node, the source RAN node reads the S1 and X2 interface configuration table stored locally first, and then performs the following steps: <ul id="ul0014" list-style="none" compact="compact"><li>Step 202: If the interface configuration table includes the information about the X2 interface exists between the source RAN node and the target RAN node and the information about the S1 interface exists between the serving core network node of the source RAN node and the target RAN node, the source RAN node sends a Handover Request to the target RAN node through the X2 interface; otherwise, the source RAN node sends a Handover Request to the target RAN node through the S1 interface.</li></ul>
0034In practice, the details of this step are as follows: <ul id="ul0015" list-style="none" compact="compact"><li>A. If no target RAN node is found in the first column of the interface configuration table, it indicates that no X2 interface exists between the source RAN node and the target RAN node, and the source RAN node sends a Handover Request message of the S 1 interface directly. If a target RAN node is found, it indicates that an X2 interface exists between the source RAN node and the target neighboring RAN node, and the process proceeds to step C.</li><li>C. The second row and the rows below it in the interface configuration table are searched for the "target RAN node" row and the "serving core network node of the source RAN node" row to check the value at the intersection between such a row and the column. If the value is "0", it indicates that no S 1 interface exists between the serving core network node of the source RAN node and the target RAN node, and the source RAN node sends the Handover Request message of the S 1 interface directly. If the value is "1", it indicates that an S 1 interface exists between the serving core network node of the source RAN node and the target RAN node, and the process proceeds to step E.</li><li>E. Through an X2 interface, a Handover Request is sent to the target RAN node.</li></ul>
0035As revealed in the foregoing description, the RAN node in the radio network judges whether an S 1 interface exists between the RAN node and the core network according to the S 1 interface information of the RAN node and the received S 1 interface information, and can select a proper interface accurately and quickly according to the received X2 interface information. Therefore, the trouble of judging whether the X2 interface is available for handover after receiving a Handover Request in the prior art is avoided, the handover speed is improved, and the system load is reduced.
0036If an S1 interface exists between the serving core network node of the source RAN node and the target RAN node, and if an X2 link exists between the source RAN node and the target RAN node but the X2 link disconnected, then the handover fails if the Handover Request is sent through the X2 interface directly. Therefore, this step is added to judge the X2 interface link state first. If the X2 interface link state is abnormal, the Handover Request is sent through an S 1 interface, thus improving the handover success ratio.
0037For that purpose, a state value is added on the basis of the S1 or X2 interface configuration table to indicate whether the X2 or S 1 interface links are normal. Specifically, a parameter may be added to indicate whether the link is available or existent. Table 5 gives an example: <tables id="tabl0005" num="0005"><table frame="all"><title>Table 5: S1 or X2 interface configuration table on RAN node 1</title><tgroup cols="5"><colspec colnum="1" colname="col1" colwidth="21mm" /><colspec colnum="2" colname="col2" colwidth="32mm" /><colspec colnum="3" colname="col3" colwidth="32mm" /><colspec colnum="4" colname="col4" colwidth="32mm" /><colspec colnum="5" colname="col5" colwidth="14mm" /><thead><row><entry valign="top">RAN node</entry><entry valign="top">core network node 1</entry><entry valign="top">core network node 2</entry><entry valign="top">core network node 3</entry><entry valign="top">X2</entry></row></thead><tbody><row><entry>RAN node 2</entry><entry>0</entry><entry>1</entry><entry>2</entry><entry>1</entry></row><row><entry>RAN node 3</entry><entry>0</entry><entry>0</entry><entry>1</entry><entry>2</entry></row></tbody></tgroup></table></tables>
0038In Table 5, the "X2" column is additional, the "0" value indicates that no link exists, "1" indicates normal, and "2" indicates link failure. The parameters in Table 5 mean that: The X2 link between RAN node 1 and RAN node 2 is normal; the X2 link between RAN node 1 and RAN node 3 is unavailable; no S1 connection exists between RAN node 2 and core network node 1, the S1 connection between RAN node 2 and core network node 2 is normal, and the S1 connection between RAN node 2 and core network node 3 is unavailable; and the X2 link between RAN node 1 and RAN node 3 is unavailable.
0039In other embodiments, the "X2" column may exist in another table. The "X2" column is optional, and is useful in step 201.
0040When the S1 and X2 interface configuration table in Table 5 is in use, if a target RAN node is found in the first column of the S1 and X2 interface configuration table in step A, step B may be performed before step C: <ul id="ul0016" list-style="none" compact="compact"><li>B. The first column of the S1 and X2 interface configuration table is searched for the target RAN node. If a target RAN node is found, the value in the "X2" column of the S1 and X2 interface configuration table is looked up. If the X2 link is found to be unavailable, a Handover Request message is sent through the S 1 interface; otherwise, the process proceeds to step C and then to step D.</li><li>D. It is judged whether S1 connection state of the target RAN node is normal. If the S1 connection state of the target RAN node is normal, a Handover Request is sent through the X2 interface to perform handover; otherwise, a Handover Request message is sent through the S1 interface to perform handover.</li></ul>
0041For example, when source RAN node 1 needs to hand over to target RAN node 2, source RAN node 1 searches Table 5. If the X2 state value is "1", it indicates that the X2 link is normal. Afterward, the state of the core network node connected with RAN node 2 is checked. If the state value of core network node 2 is "1", it indicates that the S 1 link is normal, and the handover is performed through the X2 interface.
0042In other embodiments, an additional option may be set in the S 1 or X2 interface configuration table to indicate whether the handover needs to be performed through the S 1 interface or the X2 interface. If the S 1 and X2 interface configuration table includes the information about the X2 interface between the source RAN node and the target RAN node and the information about the S1 interface between the serving core network node of the source RAN node and the target RAN node, information is set to indicate that the handover needs to be performed through the X2 interface; otherwise, information is set to indicate that the handover needs to be performed through the S 1 interface.
0043Alternatively, a simpler S 1 interface handover table is generated dynamically on the basis of the S 1 or X2 interface configuration table. The S 1 interface handover table indicates whether the handover to the target RAN node needs to be performed through the S 1 interface. The S 1 interface handover table directly decides whether the S 1 interface handover process or the X2 interface handover process applies.
0044The S 1 interface handover table falls into the following two types: <ol id="ol0002" compact="compact"><li>(1) The S1 interface handover table includes MME and S1 interface options.</li></ol>
0045In the S1 or X2 interface configuration table, if the S 1 interface link of the serving MME of the source RAN node in Table 1 or Table 5 is already configured, or if the S 1 interface is in the available state, information needs to be set in the S 1 interface handover table to indicate that the handover to the target RAN node needs to be performed through the S1 interface, as detailed in Table 6: <tables id="tabl0006" num="0006"><table frame="all"><title>Table 6: Interface handover table 1</title><tgroup cols="3"><colspec colnum="1" colname="col1" colwidth="31mm" /><colspec colnum="2" colname="col2" colwidth="22mm" /><colspec colnum="3" colname="col3" colwidth="22mm" /><thead><row><entry valign="top">Core network node</entry><entry valign="top">RAN node 2</entry><entry valign="top">RAN node 3</entry></row></thead><tbody><row><entry>MME1</entry><entry>1</entry><entry>1</entry></row><row><entry>MME2</entry><entry>0</entry><entry>1</entry></row></tbody></tgroup></table></tables>
0046In Table 6, if an S 1 interface connection exists between the serving core network node of the source RAN node and the target RAN node, the value of the S 1 handover option in the interface handover table is 0, indicating that the handover needs to be performed through the X2 interface instead of the S1 interface; otherwise, the value is 1, indicating that the handover needs to be performed through the S1 interface. The S1 interface link state may be considered at the same time. For example, when the S 1 interface link state is normal, the value of the option is 0; otherwise, the value of the option is 1.
0047For the purpose of handover, this table may be searched for the value corresponding to the target RAN node and the serving core network node of the source RAN node, and the handover selection is made according to such a value directly, without the need of searching the S1 or X1 interface configuration table.
0048Table 6 may be generated by reference to Table 5. After receiving the X2 or S 1 interface information of the neighboring RAN node, the source RAN node generates an X2 or S 1 interface configuration table described above, and then generates an S 1 interface handover table (as shown in Table 6) according to whether an S 1 interface connection exists between the source RAN node and the serving core network node of the source RAN node. That is, if the state indicated in the "core network node" column in Table 5 is "available", the handover needs to be performed through the X2 interface; otherwise, the handover needs to be performed through the S 1 interface. <ul id="ul0017" list-style="none" compact="compact"><li>(2) The interface handover table includes only the S 1 interface option.</li></ul>
0049This solution is similar to solution (1), but differs in that: The interface handover table includes only the S 1 interface option of different core network nodes between two RAN nodes, and is simpler. The principles are as follows: <ul id="ul0018" list-style="none" compact="compact"><li>It is assumed that all MMEs connected to the same RAN node are in the same MME pool, and different MME pools are never connected to the same RAN node. Although an X2 interface exists between two RAN nodes, they are connected to two MME pools, and the handover between them needs to be performed through the S1 interface. An interface handover table may be configured, and such RAN nodes are put into the table. The RAN node in such an interface handover table needs to hand over through an S 1 interface.</li></ul>
0050The interface handover table is set in the following way: <ul id="ul0019" list-style="none" compact="compact"><li>I. The S 1 interface information of the target RAN node needs to be obtained first. Through an X2 interface, the target RAN node sends the S1 interface information of the S1 interface between the target RAN node and one MME/multiple MMEs/all MMEs to the source RAN node.</li><li>II. According to the S 1 interface information of the target RAN node and the S 1 interface information of the source RAN node, judging whether both the source RAN node and the target RAN node are connected to the same core network node through an S 1 interface.</li></ul>
0051If the source RAN node and the target RAN node are not connected to the same core network node through an S1 interface, it is only necessary to set information in the interface handover table to indicate that the handover to the target RAN node needs to be performed through an S1 interface.
0052After receiving the S 1 interface information, the source RAN node compares the received S 1 interface information with its own S 1 interface information. If one MME/multiple MMEs/all MMEs are the same, it indicates that the source RAN node and the target RAN node are in the same MME pool; otherwise, it indicates that the source RAN node and the target RAN node are not in the same MME pool. The RAN nodes not in the same MME pool are put into the interface handover table. The S 1 information includes configuration information, and optionally, link state information. As shown in Table 7, RAN node 2 and the source RAN node are not in the same MME pool: <tables id="tabl0007" num="0007"><table frame="all"><title>Table 7: Interface handover table 2</title><tgroup cols="2" rowsep="0"><colspec colnum="1" colname="col1" colwidth="30mm" /><colspec colnum="2" colname="col2" colwidth="26mm" /><thead><row><entry rowsep="1" valign="top">Target RAN node</entry><entry rowsep="1" valign="top">State</entry></row></thead><tbody><row rowsep="1"><entry>eNB2</entry><entry>1</entry></row></tbody></tgroup></table></tables>
0053The communication handover method under the present invention is detailed below by reference to <figref idref="f0002">FIG. 4</figref>. As shown in <figref idref="f0002">FIG. 4</figref>, the communication handover process includes at least the following steps: <ul id="ul0020" list-style="none" compact="compact"><li>Step 401: The source RAN node searches the interface handover table.</li><li>Step 402: <ol id="ol0003" compact="compact"><li>A. If the interface handover table includes a target RAN node or the link state is normal, the handover is performed through the S1 interface.</li><li>B. Otherwise, an attempt is made to hand over through an X2 interface; or, if the link state is abnormal, handover failure is fed back directly.</li></ol></li></ul>
0054If more state information exists in Table 7, and if the state information indicates link normal, the handover is performed through the S 1 interface. This state information is optional.
0055If the S1 or X2 interface of the RAN node changes, a notification needs to be sent to the neighboring RAN node to let the neighboring RAN node update the S1 or X2 interface configuration table. Therefore, an interface information synchronization method in the second embodiment of the present invention is put forward. As shown in <figref idref="f0003">FIG. 5</figref>, the method includes the following steps: <ul id="ul0021" list-style="none" compact="compact"><li>Step 501: A judgment is made about whether a condition for initiating interface information update is fulfilled.</li></ul>
0056In this embodiment, a judgment is made about whether the configuration and/or the state of the S1 interface and/or the X2 interface of the RAN node has changed.
0057Step 502: If the condition for initiating interface information update is fulfilled, the information about the S1 interface between the RAN node and the core network node, and/or the information about the X2 interface between the RAN node and the neighboring RAN node, is sent to the neighboring RAN node.
0058When the configuration and/or the state of the S1 interface and/or the X2 interface of the RAN node changes (for example, the RAN node is connected to another core network node, or the S 1 interface configuration changes, or the address of the X2 interface to the neighboring RAN node changes, or the configuration of both the S1 interface and the X2 interface changes), a message is sent to the neighboring RAN node through the X2 interface, where the message carries the information about the S 1 interface and/or the X2 interface of the RAN node.
0059The information about the S 1 interface and/or the X2 interface of the RAN node may be a special signaling (such as a Config Info message) sent to neighboring RAN node 1, or may be added into another automatic configuration message sent to neighboring RAN node 1.
0060The information about the S1 interface and/or the X2 interface of the RAN node includes: information about the X2 interface between the RAN node and the neighboring RAN node, and/or information about the S1 interface between the RAN node and the core network node. The information about the S 1 interface and/or the X2 interface of the RAN node may include the information indicating whether the S 1 interface and/or the X2 interface between the RAN node and the neighboring RAN node is available, for example, the parameter indicative of the state in the S 1 and X2 interface configuration table in Table 5.
0061Step 503: The neighboring RAN node receives the S1 and/or X2 interface information.
0062Step 504: The neighboring RAN node configures or updates the interface information of the neighboring RAN node according to the received S 1 and/or X2 interface information.
0063In this step, after the neighboring RAN node receives the S 1 and/or X2 interface information, the neighboring RAN node configures the interface information if no old interface information exists; or updates the interface information if old interface information already exists.
0064The foregoing description reveals that: The RAN node in the radio network notifies the latest S1 and/or X2 interface information to the neighboring RAN node automatically when a certain condition is fulfilled. Therefore, the neighboring RAN node keeps aware of the latest X2 interface information and the S1 interface information of the neighboring RAN node. The interface is determined according to the latest S 1 and/or X2 interface information so that the handover operation is performed quickly. The high costs and low efficiency caused by static configuration and manual modification of the RAN node interface information in the prior art are overcome, the trouble of judging whether the X2 interface is available for handover in the prior art is avoided, the handover speed is improved, and the system load is reduced.
0065Besides, the RAN node can also receives the interface information of the neighboring RAN node. The interface information includes: the information about the S1 interface between the neighboring RAN node and the core network node, and/or the information about the X2 interface between the neighboring RAN node and the RAN node.
0066Therefore, the RAN node not only sends interface information to other RAN nodes, but also receives interface information from other RAN nodes as a basis for selecting the interface for handover. If the present invention is applied to all the RAN nodes in the radio network, the RAN nodes exchange the latest S 1 and/or X2 interface information, and any RAN node knows whether to use the X2 interface or the S 1 interface for handover to the target RAN node, thus improving the handover efficiency, avoiding handover failure, and avoiding the interface test operation.
0067Meanwhile, with the S 1 and/or X2 link state being known, the selection of the handover request is more accurate and the handover success ratio is higher.
0068It is worthy of attention that when the S1 or S2 configuration of the RAN node changes, all neighboring RAN nodes can be notified through the X2 interface message anytime. After the interface information of the neighboring RAN node is configured or updated, the following operations are performed:
0069The S1 interface handover table is obtained through calculation according to the interface information of the neighboring RAN node. The S 1 interface handover table includes the information about selecting an S 1 or X2 interface for communication handover. In this way, the interface for handover is determined more quickly, and the speed of the handover operation is improved.
0070In the interface information synchronization method provided in the embodiment of the present invention, the judgment about whether the condition of initiating interface information update is fulfilled in step 501 may be A, B, C, D, E, or F described below: <ul id="ul0022" list-style="none" compact="compact"><li>A. A judgment is made about whether the timer of the S1 and/or X2 interface information of the RAN node expires.</li></ul>
0071All the RAN nodes exchange information with each other periodically. For example, a timer is set on the S 1 and/or X2 interface information. Moreover, before the interface information is sent, a judgment may be made about whether the S 1 and/or X2 interface information or the link state of the RAN node changes; if the interface information or the link state changes, the neighboring RAN node is notified through a message; otherwise, the neighboring RAN node is not notified. Alternatively, no judgment is made, and the interface information is sent upon expiry of the timer. B. A judgment is made about whether a message that the neighboring RAN node requests the S1 and/or X2 interface information is received.
0072The RAN node may request the latest S1 and X2 interface information periodically from the neighboring RAN node through the X2 interface. Upon expiry of the timer of the RAN node, the RAN node requests the X2 and S 1 interface information from the neighboring RAN node.
0073C. A judgment is made about whether the X2 handover operation initiated by the RAN node to the neighboring RAN node fails. For ease of description, the foregoing two nodes are called "source RAN node" and "target RAN node" respectively in the handover process described below.
0074If the source RAN node searches the S1 and X2 interface configuration table and decides to perform handover through an X2 interface, the target RAN node may find that its own S 1 interface link is disconnected after sending a Handover Request message. In this case, the target RAN node sends a Handover Failure message to the source RAN node. The S 1 and X2 interface configuration table may be sent together with the Handover Failure message; or the target RAN node gives a cause value, and the source RAN node requests the new S 1 and X2 interface configuration table from the target RAN node. Alternatively, if the S 1 interface of the target RAN node is unavailable, the core network node sends configuration table information about the S 1 interface to the source RAN node.
0075When the handover operation fails, the S 1 and X2 interface information may be sent in the following way in step 502:
0076The Handover Failure response returned to the source RAN node carries the S 1 and/or X2 interface information of the target RAN node.
0077Alternatively, the Handover Failure response returned to the source RAN node carries the failure cause, and the source RAN node analyzes the cause value after receiving the failure cause. If the failure cause is radio resource allocation failure, it indicates that the handover fails. If the S 1 interface of the target RAN node is not configured or is unavailable, the source RAN node sends a request message, which requires the target RAN node to send an S 1 and/or X2 interface information message. The target RAN node sends its S 1 and/or X2 interface information to the source RAN node.
0078Alternatively, the Handover Failure response returned to the source RAN node carries the failure cause. After the source RAN node receives the failure cause, if the failure cause is lack of an S 1 interface connection between the target RAN node and the core network node, the source RAN node requests the S 1 and X2 interface configuration information of the target RAN node from the core network node. If the target S1 interface configuration recovers to normal, the handover may be performed through the X2 interface, but the source RAN node is still unaware of it. The source RAN node sends an S 1 interface Handover Request to the MME first. After receiving the Handover Request, the MME finds that the MME of the target RAN node is the same as that of the source RAN node. Therefore, the MME may also trigger the source RAN node to modify the configuration information of the target RAN node, or notify the target RAN node to send the S1 interface configuration information to the source RAN node. After receiving the S 1 interface configuration information of the target RAN node, the source RAN node modifies the X2 and S1 configuration table.
0079If the source RAN node searches the S 1 and X2 interface configuration table and decides to perform handover through an X2 interface, the target RAN node may find that its own S 1 interface link is disconnected after sending a Handover Request message. In this case, the target RAN node sends a Handover Failure message to the source RAN node. The S1 and X2 interface configuration table may be sent together with the Handover Failure message; or the target RAN node gives a cause value, and the source RAN node requests the new S 1 and X2 interface configuration table from the target RAN node. Alternatively, if the S 1 interface of the target RAN node is unavailable, the core network node sends configuration table information about the S 1 interface to the source RAN node. <figref idref="f0003">FIG. 6</figref> is a flowchart of interface information synchronization method in an embodiment of the present invention. As shown in <figref idref="f0003">FIG. 6</figref>, the interface information synchronization method of the source RAN node includes at least the following steps: <ul id="ul0023" list-style="none" compact="compact"><li>Step 601: The terminal submits a measurement report.</li><li>Step 602: After the source RAN node receives the measurement report, if the source RAN node decides to hand over and an X2 interface connection exists, the source RAN node sends a Handover Request to the target RAN node through an X2 interface.</li><li>Step 603: If the target RAN node finds that the S 1 interface is disconnected or the radio resource allocation fails, namely, if the handover fails and the condition for initiating interface information update is fulfilled, the target RAN node returns a Handover Failure message to the source RAN node. In this case, the Handover Failure message may carry a failure cause value. If the handover fails because no S 1 interface is configured or the S 1 interface is unavailable, the Handover Failure message may carry an S 1 and X2 interface configuration table. The cause value here may be: lack of configuring the S1 interface of the target RAN node, unavailable S 1 state, radio resource allocation failure, NAS error, transmission channel error, or protocol failure. </li><li>Step 604: After receiving the Handover Failure message, the source RAN node judges the failure cause according to the cause value. If the handover fails because no S 1 interface is configured or the S 1 interface is unavailable, and if the Handover Failure message carries a configuration table, the source RAN node updates the S1 and X2 interface configuration table on the source RAN node directly according to the configuration table. Otherwise, the process proceeds to step 605 if the Handover Failure message carries no configuration table and indicates only the S1 configuration error, and if the cause value is that no S 1 interface is configured or the S 1 interface is unavailable. If the handover fails due to radio resource allocation failure, the process is ended. Step 605: Through an X2 interface, the source RAN node sends a message (such as Config Info Request message) to the target RAN node, requesting new X2 and S 1 interface information.</li><li>Step 606: The information about the S1 interface between the target RAN node and the core network node and/or the information about the X2 interface between the target RAN node and the source RAN node is sent to the source RAN node.</li></ul>
0080In this step, after receiving the message (such as Config Request message), the target RAN node sends a new configuration information table (such as Config Info message) to the source RAN node.
0081<figref idref="f0004">FIG. 7</figref> is a flowchart of interface information synchronization method in another embodiment of the present invention. As shown in <figref idref="f0004">FIG. 7</figref>, the interface information synchronization method of the source RAN node includes at least the following steps: <ul id="ul0024" list-style="none" compact="compact"><li>Step 701: The terminal submits a measurement report.</li><li>Step 702: After the source RAN node receives the measurement report, if the source RAN node decides to hand over, the source RAN node reads the S 1 and X2 interface configuration table and then decides to initiate handover to the target RAN node through an S 1 interface.</li><li>Step 703: The MME receives the Handover Request and judges whether the condition for initiating interface information update is fulfilled. That is, the MME judges whether an S 1 interface connection exists between the target RAN node and the core network node, and between the source RAN node and the core network node. If it is determined that target RAN node and the source RAN node are governed by the same MME, the source RAN node is notified to update the S1 configuration information of the target RAN node. The process proceeds to step 704 or step 704', in which the S1 and/or X2 interface information of the target RAN node is sent to the source RAN node.</li><li>Step 704: The MME sends the S1 interface information of the target RAN node to the source RAN node, where the S 1 interface information may be sent in an independent message or carried in the Handover Response message in the handover process; or</li><li>Step 704': The MME sends a message to the target RAN node, thus initiating the target RAN node to send S1 interface information to the source RAN node, where the S1 interface information may be sent in an independent message or carried in the Handover Response message in the handover process.</li><li>Step 705: The source RAN node modifies the X2 and S1 interface configuration table or the S1 interface handover table.</li></ul><ul id="ul0025" list-style="none" compact="compact"><li>D. A judgment is made about whether the RAN node is restarted.</li><li>E. A judgment is made about whether the Element Manager System (EMS) of the RAN node has modified the interface information of the RAN node.</li></ul>
0082In this case, the process of sending the information about the S 1 interface and/or the X2 interface to the neighboring RAN node includes the following steps:
0083The EMS of the RAN node sends a message that carries the modified S1 and/or X2 interface information to the EMS that governs the neighboring RAN node.
0084<figref idref="f0004">FIG. 8</figref> is a flowchart of interface information synchronization method in another embodiment of the present invention. As shown in <figref idref="f0004">FIG. 8</figref>, when the configuration changes, the change may be notified to the neighboring RAN node Network Management System (NMS) through a message, and the neighboring RAN node NMS notifies the change to the neighboring RAN node. This method includes at least the following steps: <ul id="ul0026" list-style="none" compact="compact"><li>Step 801: A judgment is made about whether a condition for initiating interface information update is fulfilled.</li></ul>
0085If the configuration table of RAN node 1 is changed through modification of EMS1, a Config Modified message is sent to RAN node 1. After receiving the Config Modified message, RAN node 1 updates the stored S1 and X2 interface configuration table. The process proceeds to step 804.
0086Alternatively, if the configuration table of RAN node 1 changes, the information about the S1 interface between RAN node 1 and the core network node and/or the information about the X2 interface between RAN node 1 and the neighboring RAN node are sent to RAN node 2 through an EMS, as detailed below: <ul id="ul0027" list-style="none" compact="compact"><li>Step 802: EMS1 is notified through a Config Request message.</li><li>Step 803: After receiving the Config Request message, EMS1 modifies the corresponding configuration.</li><li>Step 804: EMS 1 sends a Config Request that carries S 1 and/or X2 interface information to the neighboring EMS2. EMS2 modifies the corresponding configuration table according to the S1 and/or X2 interface information.</li><li>Step 805: EMS2 notifies RAN node 2 through a Config Info message that carries the S1 and/or X2 interface information.</li><li>Step 806: RAN node 2 modifies the corresponding configuration table according to the S1 and/or X2 interface information.</li></ul><ul id="ul0028" list-style="none" compact="compact"><li>F. When S 1 interface handover occurs and the core network node receives Handover Request message of the source RAN node, a judgment is made about whether the target RAN node and the source RAN node are connected to the same core network. If such is the case, the S 1 interface information of the target RAN node is sent to the source RAN node; or the target RAN node is triggered to send S1 interface information to the source RAN node.</li></ul>
0087<figref idref="f0005">FIG. 9</figref> shows a structure of a radio network in an embodiment of the present invention. As shown in <figref idref="f0005">FIG. 9</figref>, the radio network includes a core network node 710 and neighboring RAN nodes 720, 730, and 740. The RAN node 720 includes: <ul id="ul0029" list-style="none" compact="compact"><li>a judging unit 721, adapted to judge whether a condition for initiating interface information update is fulfilled; and</li><li>a sending unit 722, adapted to: send the information about the S1 interface between the RAN node 720 and the core network node 710, and/or the information about the X2 interface between the RAN node 720 and the neighboring RAN node 730 to the neighboring RAN node 730 if the condition for initiating interface information update is fulfilled.</li></ul>
0088The neighboring RAN node 730 includes: <ul id="ul0030" list-style="none" compact="compact"><li>a receiving unit 731, adapted to receive the S 1 and/or X2 interface information;</li><li>a processing unit 732, adapted to configure or update the interface information of the neighboring RAN node 730 according to the received S1 and/or X2 interface information; and</li><li>a handover selecting unit 733, adapted to: search the processing unit 732 for the interface information; if finding information about the X2 interface between the two neighboring RAN nodes and determining that an S1 interface connection exists between the serving core network node 710 of the source neighboring RAN node 720 and the neighboring RAN node 730 which serves as a target node according to the S 1 interface information, select the X2 interface to initiate a handover operation; otherwise, select the S 1 interface to initiate a handover operation.</li></ul>
0089The foregoing description reveals that: The judging unit 721 in the radio network judges whether the interface information of the RAN node needs to be updated. If the interface information needs to be updated, the RAN node notifies the latest S1 and/or X2 interface information to the neighboring RAN node 730 automatically. Therefore, the neighboring RAN nodes 730 and 740 keep aware of the latest X2 interface information and S 1 interface information of the neighboring RAN nodes 730 and 740. The interface is determined according to the latest S1 and/or X2 interface information so that the handover operation is performed quickly. The high costs and low efficiency caused by static configuration and manual modification of the RAN node interface information in the prior art are overcome, the trouble of judging whether the X2 interface is available for handover in the prior art is avoided, the handover speed is improved, and the system load is reduced.
0090The judging unit 721 is adapted to: <ul id="ul0031" list-style="none" compact="compact"><li>judge whether the configuration and/or the state of the S1 interface and/or the X2 interface of the RAN node 720 has changed; or</li><li>judge whether the timer of the S1 and/or X2 interface information of the RAN node 720 expires; or</li><li>judge whether a message that the neighboring RAN node 730 requests the S1 and/or X2 interface information is received; or</li><li>judge whether the X2 handover operation initiated by the neighboring RAN node 730 to the RAN node 720 fails; or</li><li>judge whether the RAN node 720 is restarted; or</li><li>judge whether the EMS of the RAN node 720 has modified the interface information of the RAN node 720.</li></ul>
0091As shown in <figref idref="f0005">FIG. 9</figref>, a RAN node is disclosed in an embodiment of the present invention. The RAN node 720 includes: <ul id="ul0032" list-style="none" compact="compact"><li>a judging unit 721, adapted to judge whether a condition for initiating interface information update is fulfilled; and</li><li>a sending unit, adapted to: send the information about the S1 interface between the RAN node 720 and the core network node, and/or the information about the X2 interface between the RAN node 720 and the neighboring RAN node 730 to the neighboring RAN node 730 if the condition for initiating interface information update is fulfilled.</li></ul>
0092The RAN node 720 may further receive the interface information of the neighboring RAN node 730. The interface information includes: the information about the S1 interface between the neighboring RAN node 730 and the core network node, and/or the information about the X2 interface between the neighboring RAN node 730 and the RAN node 720. In this case, the RAN node 720 may further include a handover selecting unit (not illustrated in the figure), which is adapted to: search for the interface information; if finding the information about the X2 interface between the RAN node 720 and the neighboring RAN node 730 as well as the information about the S 1 interface between the serving core network node 710 of the RAN node 720 and the neighboring RAN node 730 which serves as a target node, select the X2 interface for initiating a handover operation; otherwise, select the S 1 interface for initiating a handover operation.
0093As shown in <figref idref="f0005">FIG. 10</figref>, a RAN node is disclosed in another embodiment of the present invention. The RAN node 730 includes: <ul id="ul0033" list-style="none" compact="compact"><li>a receiving unit 731, adapted to receive the S 1 and/or X2 interface information from the neighboring RAN node 720;</li><li>a processing unit 732, adapted to configure or update the interface information of the neighboring RAN node 720 according to the received S 1 and/or X2 interface information; and</li><li>a handover selecting unit 733, adapted to: search the processing unit 732 for the interface information; if finding the information about the X2 interface between the RAN node 730 and the neighboring RAN node 720 as well as the information about the S 1 interface between the serving core network node 710 of the RAN node 730 and the neighboring RAN node 720 which serves as a target node, select the X2 interface for initiating a handover operation; otherwise, select the S 1 interface for initiating a handover operation.</li></ul>
0094As shown in <figref idref="f0004">FIG. 8</figref>, a RAN node 830 is disclosed in the third embodiment of the RAN node of the present invention. The RAN node 830 includes: <ul id="ul0034" list-style="none" compact="compact"><li>a receiving unit 831, adapted to receive the S1 interface information from the neighboring RAN node;</li><li>an interface information generating unit 832, adapted to: judge whether the same core network node exists between the RAN node 830 which serves as a source node and the neighboring RAN node which serves as a target node according to the S1 interface information of the interface information generating unit 832 and the S 1 interface information received by the receiving unit 831; and generate handover information indicative of handing over to the target RAN node through an S1 interface if the same core network node does not exist; and</li><li>a handover selecting unit 833, adapted to: search for the handover information generated by the interface information generating unit 832 during the handover; if finding the information about the handover performed through the S1 interface to the target RAN node, select the S1 interface for initiating a handover operation to the neighboring RAN node; otherwise, select the X2 interface for initiating a handover operation to the neighboring RAN node.</li></ul>
0095The first, second, and third embodiments of the RAN node described above may be applied to the embodiments of the interface information synchronization method and the communication handover method, and can support the X2 and S1 interface information synchronization function and the communication handover function performed according to the X2 and S 1 interface information. The high costs and low efficiency caused by static configuration and manual modification of the RAN node interface information in the prior art are overcome, the trouble of judging whether the X2 interface is available for handover in the prior art is avoided, the handover speed is improved, and the system load is reduced.
0096It is understandable to those skilled in the art that all or part of the steps of the foregoing embodiments may be implemented by hardware instructed by a program. The program may be stored in a computer-readable storage medium. When being executed, the program performs these steps: <ul id="ul0035" list-style="none" compact="compact"><li>judging whether a condition for initiating interface information update is fulfilled;</li><li>sending information about the S 1 interface between the RAN node and the core network node, and/or information about the X2 interface between the RAN node and the neighboring RAN node to the neighboring RAN node if the condition for initiating interface information update is fulfilled;</li><li>receiving the S 1 and/or X2 interface information; and</li><li>configuring or updating the interface information of the neighboring RAN node according to the received S 1 and/or X2 interface information.</li></ul>
0097Alternatively, when being executed, the program performs these steps: <ul id="ul0036" list-style="none" compact="compact"><li>When handover occurs, the source RAN node reads the stored interface handover table, where the interface handover table includes the information indicating whether the handover can be performed through the S 1 interface to the target RAN node.</li></ul>
0098The source RAN node performs handover through the S1 interface if the interface handover table indicates that the handover can be performed through an S 1 interface to the target RAN node, or else performs handover through the X2 interface.
0099Alternatively, when being executed, the program performs these steps: <ul id="ul0037" list-style="none" compact="compact"><li>The source RAN node reads interface information when handover occurs, where: the interface information includes the information about whether an X2 interface exists between the source RAN node and the target RAN node and/or the information about whether an S1 interface exists between the serving core network node of the source RAN node and the target RAN node.</li></ul>
0100The source RAN node performs handover through an X2 interface if the interface information indicates that an X2 interface exists between the source RAN node and the target RAN node and/or an S1 interface exists between the serving core network node of the source RAN node and the target RAN node, or else performs handover through an S1 interface. The storage medium mentioned above may be a ROM/RAM, magnetic disk, compact disk, and so on. It is worthy of attention that the judging unit 721, the sending unit 722, and the handover selecting unit 733 in the first embodiment of the RAN node of the present invention may be integrated in one computation processing module; and the receiving unit 731, the processing unit 732, and the handover selecting unit 733 of the RAN node in the second embodiment of the present invention may be integrated in one processing module, or even all units in an embodiment of the present invention may be integrated in one processing module.
0101Further, it is worthy of attention that the judging unit 721, the sending unit 722, and the handover selecting unit 733 in the first embodiment of the RAN node of the present invention may be hardware or software function modules, and it is the same with the receiving unit 731, the processing unit 732, and the handover selecting unit 733 of the RAN node in the second embodiment. The combination of the foregoing units may be sold or applied as an independent product, or stored in a computer-readable storage medium.
0102Detailed above are a synchronization method, a communication handover method, a radio network, and a RAN node in an embodiment the present invention. Although the invention is described through some exemplary embodiments, the invention is not limited to such embodiments. It is apparent that those skilled in the art can make various modifications and variations to the invention without departing from the spirit and scope of the invention.
Contents5
6 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| EP2560454A4 | Cited by | European Patent Office (EPO) | Search report |
| US9055492B2 | Cited by | United States of America | Applicant |
| WO2024072784A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| EP2472998A1 | Cited by | European Patent Office (EPO) | Search report |
| EP2472998A4 | Cited by | European Patent Office (EPO) | Search report |
| WO2012060757A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| WO2012060757A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US9820195B2 | Cited by | United States of America | Applicant |
| US9414270B2 | Cited by | United States of America | Applicant |
| EP2521419A1 | Cited by | European Patent Office (EPO) | Search report |
| US9801102B2 | Cited by | United States of America | Applicant |
| WO2011136534A3 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| WO2011136534A2 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US9414271B2 | Cited by | United States of America | Applicant |
| WO2007001952A1 | Cites | World Intellectual Property Organization (WIPO) | Search report |
25 members in 6 offices; this record represents the family
Priority claims3
| Document | Office | Kind | Date |
|---|---|---|---|
| 200710103636 | China | – | |
| 200710103636 | China | A | |
| 2008070789 | China | W |
Members25
| Document | Office | Kind | |
|---|---|---|---|
| CN101299876A | China | A | |
| WO2008134962A1 | World Intellectual Property Organization (WIPO) | A1 | |
| EP2139257A1This record | European Patent Office (EPO) | A1 | |
| US2010046476A1 | United States of America | A1 | |
| EP2139257A4 | European Patent Office (EPO) | A4 | |
| CN101299876B | China | B | |
| US2011218003A1 | United States of America | A1 | |
| EP2139257B1 | European Patent Office (EPO) | B1 | |
| AT552714T | Austria | T | |
| ATE552714T1 | Austria | T1 | |
| ES2384411T3 | Spain | T3 | |
| US8249020B2 | United States of America | B2 | |
| US2012269168A1 | United States of America | A1 | |
| EP2519053A1 | European Patent Office (EPO) | A1 | |
| US8630263B2 | United States of America | B2 | |
| EP2519053B1 | European Patent Office (EPO) | B1 | |
| EP2797362A1 | European Patent Office (EPO) | A1 | |
| US8942249B2 | United States of America | B2 | |
| US2015079995A1 | United States of America | A1 | |
| US9730119B2 | United States of America | B2 | |
| EP2797362B1 | European Patent Office (EPO) | B1 | |
| US2017339603A1 | United States of America | A1 | |
| US10237788B2 | United States of America | B2 | |
| US2019174370A1 | United States of America | A1 | |
| US10694430B2 | United States of America | B2 |
73 legal events, as 10 offices reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | Office | |
|---|---|---|---|
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Opt-out of the competence of the unified patent court (upc) registeredP01 | P01 | EP | |
| Fee paymentPLFP | PLFP | FR | |
| Fee paymentPLFP | PLFP | FR | |
| Fee paymentPLFP | PLFP | FR | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| No opposition filed against granted patent, or epo opposition proceedings concluded without decisionGrantedR097 | R097 | DE | |
| No opposition filedOpposition26N | 26N | EP | |
| No opposition filed within time limitOppositionORIGINAL CODE: 0009261PLBE | PLBE | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: NO OPPOSITION FILED WITHIN TIME LIMITSTAA | STAA | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Patent lapsedLapsedMM4A | MM4A | IE | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Patent ceasedCeasedPL | PL | CH | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lt: invalidation of european patent or patent extensionLTIE | LTIE | EP | |
| Translation of granted ep patentGrantedTRGR | TRGR | SE | |
| Definitive protectionFG2A | FG2A | ES | |
| Translation filed for an european patent granted for nl, confirming art. 52 par. 1 or 6 of the patents act 1995GrantedT3 | T3 | NL | |
| Dpma publication of mentioned ep patent grantGrantedR096 | R096 | DE | |
| European patents granted designating irelandGrantedFG4D | FG4D | IE | |
| Reference to at number (ep patent validated in austria)REF | REF | AT | |
| European patent takes effect as a national patent in ch/liEP | EP | CH | |
| Designated contracting statesAK | AK | EP | |
| European patent grantedGrantedFG4D | FG4D | GB | |
| (expected) grantORIGINAL CODE: 0009210GRAA | GRAA | EP | |
| Grant fee paidORIGINAL CODE: EPIDOSNIGR3GRAS | GRAS | EP | |
| Despatch of communication of intention to grant a patentORIGINAL CODE: EPIDOSNIGR1GRAP | GRAP | EP | |
| Information related to disapproval of communication of intention to grant by the applicant or resumption of examination proceedings by the epo deletedORIGINAL CODE: EPIDOSDIGR1GRAJ | GRAJ | EP | |
| Despatch of communication of intention to grant a patentORIGINAL CODE: EPIDOSNIGR1GRAP | GRAP | EP | |
| Information provided on ipc code assigned before grantRIC1 | RIC1 | EP | |
| Title (correction)SYNCHRONIZATION METHOD, RADIO NETWORK AND NODERTI1 | RTI1 | EP | |
| Amendment of ipc main classPREVIOUS MAIN CLASS: H04W0004000000R079 | R079 | DE | |
| Amendment of ipc main classPREVIOUS MAIN CLASS: H04Q0007380000R079 | R079 | DE | |
| First examination report despatched17Q | 17Q | EP | |
| Request for extension of the european patent (deleted)DAX | DAX | EP | |
| Supplementary search report drawn up and despatchedA4 | A4 | EP | |
| Information provided on ipc code assigned before grantRIC1 | RIC1 | EP | |
| Information provided on ipc code assigned before grantRIC1 | RIC1 | EP | |
| Request for examination filed17P | 17P | EP | |
| Designated contracting statesAK | AK | EP | |
| Public reference made under article 153(3) epc to a published international application that has entered the european phaseORIGINAL CODE: 0009012PUAI | PUAI | EP |
Numbers
- Publication
- 2139257
- Application
- 87341475
Titles3
- German
- SYNCHRONISATIONSVERFAHREN, KOMMUNIKATIONSWEITERREICHVERFAHREN, RADIONETZWERK UND STATION
- English
- SYNCHRONIZATION METHOD, COMMUNICATION HANDOVER METHOD, RADIO NETWORK AND NODE
- French
- PROCÉDÉ DE SYNCHRONISATION, PROCÉDÉ DE TRANSFERT DE COMMUNICATION, RÉSEAU ET N UD RADIO
Classification
- CPC, 5
- H04W36/0079
- H04W92/045
- H04W92/20
- H04W36/02
- H04W36/0058
- IPC, 4
- H04Q7 38
- H04W36 02
- H04W92 04
- H04W92 20
Designated states1
- Contracting states, 1
- Türkiye