Abstract: A method for handover of a mobile terminal from a source node to a target node in a wireless telecommunications network, including the steps of: adding an indication in the preparation phase by which source node indicates to the target node if it is the one preferred or not. If a target node is not the one preferred but is still selected by the UE, it may indicate this to the source node as by a specific new message that comes earlier in the handover process than a message requesting the source node to release resources following successful handover to a new node. The source node can then in this case cancel handover preparations to other target nodes earlier and also start data forwarding where applicable earlier.
HANDOVER METHOD AND APPARATUS IN A WIRELESS TELECOMMUNICATIONS NETWORK
FIELD OF THE INVENTION
The present invention relates to a method and apparatus for handover in a wireless telecommunications network, and more particularly, but not exclusively, to a method and apparatus implemented in accordance with the 3rd Generation Partnership Project (3GPP) evolved Universal Terrestrial Radio Access Network (E-UTRAN) and evolved Universal Terrestrial Radio Access (E-UTRA) specifications.
BACKGROUND OF THE INVENTION
Currently, 3 GPP is considering development of E-UTRA and E-UTRAN as set out in the technical specification 3GPP TS 36.300 v 8.1.0 (2007- 06), incorporated herein by way of reference, and related documents. 3GPP Long Term Evolution (LTE) aims to enhance the Universal Mobile Telecommunications System (UMTS) standard, for example, by improving efficiency and services.
In E-UTRAN, user equipment (UE) communicates with a network node, NodeB (eNB), with data being sent on radio bearers (RBs) over a radio link between them. The eNB interfaces with a Mobile Management Entity/System Architecture Evolution Gateway (MME/SAE GW) via an interface designated as SI. An E-UTRAN network includes a plurality of eNBs and MME/SAE GWs.
In LTE, all the Radio Access Network (RAN) fimctions are integrated in each node, eNB. Downlink user data, that is Internet Protocol (IP) packets, are transmitted from the SAE GW to the eNB. As the UE is handed over from a first, source, eNB tosecond, target, eNB, the SAE GW is updated with the second eNB address and the SAE GW starts to send data to that target eNB.
However, to avoid data loss, any data that is already buffered in the source eNB must be forwarded to the target eNB. Also, data that has been sent to the source eNB during the handover (HO) procedure, before the SAE GW is updated with the new eNB address, is also forwarded by the source eNB to the target eNB.
To preserve the order of packets sent to the UE, the target eNB must strive to send data over the radio in the same order as sent by the SAE GW. That is, first data buffered by the eNB is sent to the target eNB, followed by data in transit from the SAE GW during the HO process, and only when these have all been sent should the target eNB send to the UE fresh data that it receives directly from the SAE GW.
The message flow for the HO process appUed to a UE 1 is shown in Figure 1, which illustrates a network including a source eNB 2, a target eNB 3 and an MME/SAE GW 4. When the source eNB 2 makes a handover decision based on measurement reports from the UE 1, it sends a Handover Request message, at step 4, to the target eNB 3. At the Admission Control step 5, the target eNB 3 configures the required resources and sends a Handover Request Acknowledge message, at step 6, to the source eNB 2. Following the Handover Command, at step 7, from the source eNB 2 to the UE 1, the UE 1 detaches from the old cell and synchronises to the new cell associated with the target eNB 3. Also, data packets buffered at the source eNB 2 and any in transit are forwarded to the target eNB 3 from the source eNB 2. Following the Handover Confirm message at step 10 from the UE 1 to the target eNB 3, a Handover Complete message, at step 11, is sent to the MME/SAE GW 4 by the target eNB 3. Data packets from the soixrce eNB 2 continue to be delivered to the target eNB 3. Once all the forwarded data from source eNB 2 has been received by the target eNB 3, the target eNB 3 can then send to the UE 1 fresh data arriving over SI from MME/SAE GW.
In LTE, the data forwarding phase, where data is sent to the target eNB from the source eNB, currently starts when the source eNB receives the Handover Request Ack message, at step 6 in Figure 1, from the target eNB which indicates the end of the preparation phase for that target eNodeB.
However, it has recently been proposed that the source eNodeB 2 be able to trigger multiple preparation procedures towards several target eNodeBs 5 and 6, as shown in Figure 2, where the same references are used for the same items. For the purposes of explanation, only two target eNBs are illustrated, but there may be more than two target eNBs available. The source eNB 2 sends Handover Request messages, at steps 4a and 4b, to the target eNBs 5 and 6. The source eNodeB 2 receives
Handover Request Ack messages, shown at step 6a and step 6b, from each of the multiple target eNodeBs 5 and 6, but, at that time, does not know which of the target eNodeBs 5 and 6 will be finally selected as the one to which the UE 1 will hand over. The UE 1 will finally succeed in being handed over to only one of the target eNodeBs 5 and 6. Therefore, when the source eNodeB 2 receives the Handover Request Ack messages, at steps 6a and 6b, it does not know towards which of the target eNodeBs 5 and 6 it should trigger data forwarding.
There have been two previous proposals to deal with data forwarding where multiple target eNBs exist to ensure that the finally elected target eNodeB will receive the forwarded data.
In a first proposal, as shown in Figure 3, the source eNodeB 2 triggers multiple data forwarding procedxu-es towards all prepared target eNodeBs 5 and 6 from which it has received Handover Request Ack messages, at steps 6a and 6b. This approach is inefficient, cumbersome and bandwidth consuming, as it involves forwarding the data towards target eNodeBs which will not eventually be elected to form a connection with the UE.
In a second proposal, as shown in Figure 4, the source eNodeB 2 triggers the data forwarding towards only a preferred target eNodeB 5 at the time it receives the Handover Request Ack messages at steps 6a and 6b. The preferred target eNB 5 may, for example, be that one having the highest probability of the UE 1 successfully handing over to it. The probability of success can be assessed in various ways, for example, based on channel quality. The manner in which a target eNB 5 is designated as the preferred target eNB depends on a particular implementation of a network. The source eNB 2 only triggers the data forwarding towards any other target eNodeB 6 if and when it gets an indication, on receipt of a Release Resource message at step 13, from that other non-preferred target eNodeB 6 that it has finally been selected by the UE 1. Thus, when one of the non-preferred target eNBs is finally selected, that indication to the source eNodeB 2 comes quite late in the handover process and makes the data forwarding process quite complex.
BRIEF SUMMARY OF THE INVENTION
According to a first aspect of the invention, a method for handover of a mobile terminal from a source node to a target node in a wireless telecommvmications network, includes the steps of: identifying a pluraUty of target nodes; identifying a preferred target node from the plurality for the mobile terminal to hand over to; and the source node indicating to the preferred target node that it is the preferred target node. A target node may be preferred, for example, because it is most likely to be the one to which the mobile terminal will successfully hand over, or because it involves the most efficient use of resources, or for some other reason, the designation process depending on how the network is implemented and its priorities. The method is applicable to networks implemented in accordance with Long Term Evolution, LTE, standards, but may also be used in other types of network where mobile terminals are connected to different nodes to achieve mobility, or between nodes of different technology types.
In one method in accordance with the invention, when a target node other than the preferred target node is chosen to connect to the mobile terminal, the chosen target node sends a message to the source node to inform it of the choice and, following receipt of the message, and before the source node is sent a request to release resources, the source node begins forwarding data to the chosen target node. This enables data forwarding to the actual node selected for connection to the mobile terminal, where that node is not the designated preferred node, to begin sooner than in the previous second proposal. Before the source node receives the message, it may forward data to the preferred target node. By forwarding data to the preferred node as soon as the source node receives a handover request acknowledgement message from it, the data forwarding remains optimally efficient in the vast majority of cases where the preferred target node becomes node selected by the mobile terminal.
In a method in accordance with the invention, when the preferred target node is selected to connect to the mobile terminal, no message is sent to the source node by the preferred target node to inform it of the selection before the source node is sent by this target node a request to release resources. This ensures that there is no significant additional signalling required to implement the invention.
In a method in accordance with the invention, the source node sends a handover request to the pluraUty of target nodes and includes an indication in the handover request which indicates the preferred target node. Alternatively, the preferred status of a node may be transmitted via a separate message additional to the handover request message, but this increases signalling overheads. In a method in accordance with the invention, the handover request message sent to the preferred target node includes an information element informing it that it is the preferred target node and the handover request messages sent to non-preferred target nodes do not include the information element. The handover request message may, for example, include a flag which is set to 'preferred' or 'non-preferred', or alternatively, the handover request message may include an information element only where the handover request message is sent to the preferred node, and any non-preferred node infers from its absence that it is not the preferred node.
In a method in accordance with the invention, when a target node other than the preferred target node is chosen to connect to the mobile terminal and the chosen target node sends a message to the source node to inform it of the choice, following receipt of the message, and before the source node is sent a request to release resources, the source node sends a Handover Cancel message to the preferred target node to cancel prepared context related to the mobile terminal and held by preferred target node. The source node may also send a Handover Cancel message to each other non-selected target node when it receives the message form the chosen target node informing it of the choice.
According to a second aspect of the invention, a wireless telecommunications network is arranged to implement the method in accordance with the invetion.
BRIEF DESCRIPTION OF THE DRAWINGS
Some embodiments and methods in accordance with the invention are now described, by way of example only, and with reference to the accompanying drawings, in which:
Figures 1 to 4 schematically illustrate prior art networks and messaging during handover; and
Figure 5 schematically illustrates a network and messaging during handover in accordance with the invention.
DETAILED DESCRIPTION
With reference to Figure 5, when measurement reports from the UE 1 indicate to the source eNB 2 that the UE 1 should hand over to another eNB, it sends a Handover Request message, at steps 4a and 4b, to multiple target eNBs 5 and 6. One of the target eNBs is designated by the source eNB 2 as the preferred target eNB, for example, because it is most likely to be the one to which the UE 1 will successfully hand over, or because it involves the most efficient use of resources, or for some other reason, the designation process depending on how the network is implemented. The Handover Request message sent at step 4a to the preferred eNB 5 also includes an indication that it is the preferred eNB. The indication is an additional information element included in the message. The Handover Request message to the other target eNBs, at step 4b, does not include any indication that they are preferred.
Following receipt of the Handover Ack messages at steps 6a and 6b from preferred and non-preferred eNBs 5 and 6, the source eNB 2 begins forwarding data to the preferred eNB 5.
In most cases, the UE 1 will then attach to the preferred eNB 5, and the handover procedure will continue as set out in Figure 1. However, where instead the UE 1 establishes a connection with a non-preferred eNB 6, as shown in Figure 5, and sends a Handover Confirm message, at step 10, to the non-preferred target eNB 6, the eNB 6 then sends a new Handover Confirm message, at step lObis, to the source eNB 2. Immediately after receiving the Handover Confirm message lObis, the source eNB 2 then stops data forwarding to the preferred eNB 5 and begins to send data to the selected target eNB 6 chosen by the UE 1. Thus, data begins to be forwarded to the elected target eNB 6 before the source eNB 2 receives a Release Resource message, at step 13.
The information element in the Handover Request message, at step 4, indicates to the target eNodeB if it is preferred or not in this handover. Thus, if the eNB 5 is preferred, it never sends the new message, at step lObis, when it becomes selected by the UE 1. Therefore, the new message lObis is only sent when a non-preferred target
eNodeB 6 is selected by the UE 1, which means in fewer cases. This improves the bandwidth occupancy, for example, without increasing the signalling load.
In addition, an optional, but advantageous procedure, is to cancel the context prepared in the preferred eNodeB 5 as soon as possible in cases where a non-preferred eNodeB 6 is selected by the UE 1. This is done, in one method in accordance with the invention, by the source eNodeB 2 sending a Cancel message, shown as chain broken line 7, to the preferred target eNodeB 5 as soon as receiving the new message 10bis. Altematively, no Cancel message is sent and reception of the Release Resource message at step 13 is used to cancel the prepared context. Furthermore, after the source eNB 2 receives message lObis, it may send Cancel messages to other non-selected, non-preferred target eNBs to immediately cancel pending prepared contexts that they hold.
The present invention may be embodied in other specific forms and implemented in other methods without departing from its spirit or essential characteristics. The described embodiments and methods are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes that come within the meaning and range of equivalency of the claims are to be embraced within their scope.
CLAIMS
1. A method for handover of a mobile terminal from a source node to a target node in
a wireless telecommunications network, including the steps of:
identifying a plurality of target nodes;
identifying a preferred target node from the plurality for the mobile terminal to hand over to; and
the source node indicating to the preferred target node that it is the preferred target node.
2. The method as claimed in claim 1 and including the steps of:
when a target node other than the preferred target node is chosen to connect to the mobile terminal, the chosen target node sending a message to the source node to inform it of the choice and, following receipt of the message, and before the source node is sent a request to release resources, the source node begins forwarding data to the chosen target node.
3. The method as claimed in claim 2 and wherein, before the source node receives the message, it forwards data to the preferred target node.
4. The method as claimed in claim 2 or 3 and wherein, when the preferred target node is selected to connect to the mobile terminal, no message is sent to the source node by the preferred node to inform it of the selection before the source node is sent a request to release resources.
5. The method as claimed in any preceding claim and wherein the source node sends a handover request to the plurality of target nodes and includes an indication in the handover request which indicates which node is the preferred target node and which node is not.
6. The method as claimed in claim 5 and wherein the handover request message sent
to the preferred target node includes an information element informing it that it is the
preferred target node and the handover request messages sent to non-preferred target
nodes do not include the information element.
7. The method as claimed in any preceding claim and, when a target node other than the preferred target node is chosen to connect to the mobile terminal and the chosen target node sends a message to the source node to inform it of the choice, following receipt of the message, and before the source node is sent a request to release resources, the source node sends a handover cancel message to the preferred target node to cancel prepared context related to the mobile terminal and held by the preferred target node.
8. The method as claimed in claim 7 and wherein the source node sends a handover cancel message to each non-selected target node when it receives the message form the chosen target node informing it of the choice.
9. The method as claimed in any preceding claim and implemented in accordance with Long Term Evolution, LTE, standards.
10. A wireless telecommunications network arranged to implement the method as
claimed in any preceding claim.
| Section | Controller | Decision Date |
|---|---|---|
| # | Name | Date |
|---|---|---|
| 1 | 764-chenp-2010 description(complete) 09-02-2010.pdf | 2010-02-09 |
| 1 | 764-CHENP-2010-Correspondence to notify the Controller (Mandatory) [14-08-2018(online)].pdf | 2018-08-14 |
| 2 | 764-chenp-2010 claims 09-02-2010.pdf | 2010-02-09 |
| 2 | 764-CHENP-2010-HearingNoticeLetter.pdf | 2018-07-06 |
| 3 | Correspondence by Agent_Assignment_15-03-2018.pdf | 2018-03-15 |
| 3 | 764-chenp-2010 abstract 09-02-2010.pdf | 2010-02-09 |
| 4 | 764-CHENP-2010-ABSTRACT [13-03-2018(online)].pdf | 2018-03-13 |
| 4 | 764-chenp-2010 form-2 09-02-2010.pdf | 2010-02-09 |
| 5 | 764-CHENP-2010-CLAIMS [13-03-2018(online)].pdf | 2018-03-13 |
| 5 | 764-chenp-2010 drawings 09-02-2010.pdf | 2010-02-09 |
| 6 | 764-CHENP-2010-COMPLETE SPECIFICATION [13-03-2018(online)].pdf | 2018-03-13 |
| 6 | 764-chenp-2010 form-5 09-02-2010.pdf | 2010-02-09 |
| 7 | 764-CHENP-2010-DRAWING [13-03-2018(online)].pdf | 2018-03-13 |
| 7 | 764-chenp-2010 form-3 09-02-2010.pdf | 2010-02-09 |
| 8 | 764-CHENP-2010-FER_SER_REPLY [13-03-2018(online)].pdf | 2018-03-13 |
| 8 | 764-chenp-2010 form-1 09-02-2010.pdf | 2010-02-09 |
| 9 | 764-chenp-2010 power of attorney 09-02-2010.pdf | 2010-02-09 |
| 9 | 764-CHENP-2010-OTHERS [13-03-2018(online)].pdf | 2018-03-13 |
| 10 | 764-chenp-2010 pct 09-02-2010.pdf | 2010-02-09 |
| 10 | 764-CHENP-2010-Proof of Right (MANDATORY) [13-03-2018(online)].pdf | 2018-03-13 |
| 11 | 764-chenp-2010 correspondence others 09-02-2010.pdf | 2010-02-09 |
| 11 | 764-CHENP-2010-FER.pdf | 2017-09-13 |
| 12 | 764-chenp-2010 form 3 05-08-2010.pdf | 2010-08-05 |
| 12 | 764-CHENP-2010 CORRESPONDENCE OTHERS 14-08-2014.pdf | 2014-08-14 |
| 13 | 764-CHENP-2010 FORM-13 03-12-2010.pdf | 2010-12-03 |
| 13 | 764-CHENP-2010 FORM-3 14-08-2014.pdf | 2014-08-14 |
| 14 | 764-CHENP-2010 CORRESPONDENCE OTHERS 14-02-2014.pdf | 2014-02-14 |
| 14 | 764-chenp-2010 correspondence others 03-12-2010.pdf | 2010-12-03 |
| 15 | 764-CHENP-2010 FORM-3 14-02-2014.pdf | 2014-02-14 |
| 15 | abs 764-chenp-2010 abstract 09-12-2010.jpg | 2010-12-09 |
| 16 | 764-CHENP-2010 CORRESPONDENCE OTHERS 09-10-2013.pdf | 2013-10-09 |
| 16 | 764-CHENP-2010 FORM-18 30-06-2011.pdf | 2011-06-30 |
| 17 | 764-CHENP-2010 FORM-13 30-06-2011.pdf | 2011-06-30 |
| 17 | 764-CHENP-2010 FORM-3 09-10-2013.pdf | 2013-10-09 |
| 18 | 764-CHENP-2010 CORRESPONDENCE OTHERS 21-06-2013.pdf | 2013-06-21 |
| 18 | 764-CHENP-2010 CORRESPONDENCE OTHERS 30-06-2011.pdf | 2011-06-30 |
| 19 | 764-CHENP-2010 AMENDED PAGES OF SPECIFICATION 30-06-2011.pdf | 2011-06-30 |
| 19 | 764-CHENP-2010 FORM-3 21-06-2013.pdf | 2013-06-21 |
| 20 | 764-CHENP-2010 AMENDED CLAIMS 30-06-2011.pdf | 2011-06-30 |
| 21 | 764-CHENP-2010 AMENDED PAGES OF SPECIFICATION 30-06-2011.pdf | 2011-06-30 |
| 21 | 764-CHENP-2010 FORM-3 21-06-2013.pdf | 2013-06-21 |
| 22 | 764-CHENP-2010 CORRESPONDENCE OTHERS 21-06-2013.pdf | 2013-06-21 |
| 22 | 764-CHENP-2010 CORRESPONDENCE OTHERS 30-06-2011.pdf | 2011-06-30 |
| 23 | 764-CHENP-2010 FORM-3 09-10-2013.pdf | 2013-10-09 |
| 23 | 764-CHENP-2010 FORM-13 30-06-2011.pdf | 2011-06-30 |
| 24 | 764-CHENP-2010 FORM-18 30-06-2011.pdf | 2011-06-30 |
| 24 | 764-CHENP-2010 CORRESPONDENCE OTHERS 09-10-2013.pdf | 2013-10-09 |
| 25 | abs 764-chenp-2010 abstract 09-12-2010.jpg | 2010-12-09 |
| 25 | 764-CHENP-2010 FORM-3 14-02-2014.pdf | 2014-02-14 |
| 26 | 764-CHENP-2010 CORRESPONDENCE OTHERS 14-02-2014.pdf | 2014-02-14 |
| 26 | 764-chenp-2010 correspondence others 03-12-2010.pdf | 2010-12-03 |
| 27 | 764-CHENP-2010 FORM-13 03-12-2010.pdf | 2010-12-03 |
| 27 | 764-CHENP-2010 FORM-3 14-08-2014.pdf | 2014-08-14 |
| 28 | 764-chenp-2010 form 3 05-08-2010.pdf | 2010-08-05 |
| 28 | 764-CHENP-2010 CORRESPONDENCE OTHERS 14-08-2014.pdf | 2014-08-14 |
| 29 | 764-chenp-2010 correspondence others 09-02-2010.pdf | 2010-02-09 |
| 29 | 764-CHENP-2010-FER.pdf | 2017-09-13 |
| 30 | 764-chenp-2010 pct 09-02-2010.pdf | 2010-02-09 |
| 30 | 764-CHENP-2010-Proof of Right (MANDATORY) [13-03-2018(online)].pdf | 2018-03-13 |
| 31 | 764-chenp-2010 power of attorney 09-02-2010.pdf | 2010-02-09 |
| 31 | 764-CHENP-2010-OTHERS [13-03-2018(online)].pdf | 2018-03-13 |
| 32 | 764-chenp-2010 form-1 09-02-2010.pdf | 2010-02-09 |
| 32 | 764-CHENP-2010-FER_SER_REPLY [13-03-2018(online)].pdf | 2018-03-13 |
| 33 | 764-chenp-2010 form-3 09-02-2010.pdf | 2010-02-09 |
| 33 | 764-CHENP-2010-DRAWING [13-03-2018(online)].pdf | 2018-03-13 |
| 34 | 764-chenp-2010 form-5 09-02-2010.pdf | 2010-02-09 |
| 34 | 764-CHENP-2010-COMPLETE SPECIFICATION [13-03-2018(online)].pdf | 2018-03-13 |
| 35 | 764-chenp-2010 drawings 09-02-2010.pdf | 2010-02-09 |
| 35 | 764-CHENP-2010-CLAIMS [13-03-2018(online)].pdf | 2018-03-13 |
| 36 | 764-chenp-2010 form-2 09-02-2010.pdf | 2010-02-09 |
| 36 | 764-CHENP-2010-ABSTRACT [13-03-2018(online)].pdf | 2018-03-13 |
| 37 | Correspondence by Agent_Assignment_15-03-2018.pdf | 2018-03-15 |
| 37 | 764-chenp-2010 abstract 09-02-2010.pdf | 2010-02-09 |
| 38 | 764-CHENP-2010-HearingNoticeLetter.pdf | 2018-07-06 |
| 38 | 764-chenp-2010 claims 09-02-2010.pdf | 2010-02-09 |
| 39 | 764-CHENP-2010-Correspondence to notify the Controller (Mandatory) [14-08-2018(online)].pdf | 2018-08-14 |
| 39 | 764-chenp-2010 description(complete) 09-02-2010.pdf | 2010-02-09 |
| 1 | Searchstrategy(764CHENP2010)_24-08-2017.pdf |