CONFIRMATION

TECHNICAF FIEFD

Some example embodiments may relate generally to an apparatus and a method for optimization of conditional handover confirmation.

CROSS-REFERENCE TO RELATED APPLICATIONS:

[0001] This application claims priority to U.S. Provisional Patent Application No. 62/669,465 filed on May 10, 2018. The entire content of the above-referenced application is hereby incorporated by reference.

BACKGROUND

[0002] This section is intended to provide a background or context to the invention that is recited in the claims. The description herein may include concepts that could be pursued, but are not necessarily ones that have been previously conceived, implemented or described. Therefore, unless otherwise indicated herein, what is described in this section is not prior art to the description and claims in this application.

[0003] Examples of mobile or wireless telecommunication systems may include the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Long Term Evolution (LTE) Evolved UTRAN (E-UTRAN), LTE-Advanced (LTE-A), LTE-A Pro, and/or fifth generation (5G) radio access technology or new radio (NR) access technology. 5G or NR wireless systems refer to the next generation (NG) of radio systems and network architecture, and is expected to deliver extreme broadband and ultra-robust, low latency connectivity and massive networking to support the Internet of Things (IoT). With IoT and machine-to-machine (M2M) communication becoming more widespread, there will be a growing need for networks that meet the needs of lower power, high data rate, and long battery life. It is noted that, in 5G or NR, the nodes that can provide radio access functionality to a user equipment (i.e., similar to Node B in UTRAN or eNB in LTE) may be referred to as a next generation or 5G Node B (gNB). Conditional Handover (CHO) is a feature that is currently under consideration for next evolution of radio network systems. It is mainly considered for 5G/NR, which is under the responsibility of the 3 ^rd generation partnership project (3GPP).

SUMMARY

[0004] In general, example embodiments of the present disclosure provide a solution for contention resolution in random access procedure.

[0005] In a first aspect, there is provided an apparatus. The apparatus comprises at least one processor; and at least one memory including computer program codes; the at least one memory and the computer program codes are configured to, with the at least one processor, cause the apparatus to receive a conditional handover command; start a timer; determine whether a condition for handover is fulfilled before the timer expires; and if the condition is fulfilled before the timer expires, connect to a target cell and indicate to the target cell that the handover has been performed.

[0006] In a second aspect, there is provided a method. The method comprises receiving a conditional handover command; starting a timer; determining whether a condition for handover is fulfilled before the timer expires; and if the condition is fulfilled before the timer expires, connecting to a target cell and indicate to the target cell that the handover has been performed.

[0007] In a third aspect, there is provided an apparatus. The apparatus comprises means for receiving a conditional handover command; means for starting a timer; means for determining whether a condition for handover is fulfilled before the timer expires; and means for if the condition is fulfilled before the timer expires, connecting to a target cell and indicate to the target cell that the handover has been performed.

[0008] In a fourth aspect, there is provided an apparatus. The apparatus comprises circuitry configured to perform at least the method according to the second aspect.

[0009] In a fifth aspect, there is provided a non-transitory computer readable medium. The non- transitory computer readable medium comprises program instructions stored thereon, when executed in hardware, for performing at least the method according to the second aspect.

[0010] In a sixth aspect, there is provided a computer program product. The computer program produce comprises instructions for performing a process including at least the method according to the second aspect.

BRIEF DESCRIPTION OF THE DRAWINGS

[0011] For a more complete understanding of example embodiments of the present invention, reference is now made to the following descriptions taken in connection with the accompanying drawings in which:

[0012] Figure 1 illustrates a conditional handover (CHO) message flow in accordance with various example embodiments. [0013] Figure 2 illustrates a CHO message flow with a timer in accordance with various example embodiments.

[0014] Figure 3 illustrates another CHO message flow with a timer in accordance with various example embodiments.

[0015] Figure 4 illustrates a simplified block diagram of an example apparatus that is suitable for use in practicing various example embodiments of this application.

DETAILED DESCRIPTON

[0016] The description below generally refers to 5G NR terms, however this is not intended to be limiting. The description is equally applicable to other wireless networks and technologies. It will be also readily understood that the components of certain example embodiments, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of some example embodiments of systems, methods, apparatuses, and computer program products, as represented in the attached figures and described below, is not intended to limit the scope of certain embodiments but is representative of selected example embodiments.

[0017] The features, structures, or characteristics of example embodiments described throughout this specification may be combined in any suitable manner in one or more embodiments. For example, the usage of the phrases“certain embodiments,”“some embodiments,” or other similar language, throughout this specification refers to the fact that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment. Thus, appearances of the phrases“in an example embodiment,”“in some embodiments,”“in other embodiments,” or other similar language, throughout this specification do not necessarily all refer to the same group of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0018] In a traditional handover (or basic handover, BHO), the process is usually triggered by a user equipment (UE) observing conditions that trigger a measurement report based on network configuration. The UE sends to a source Node B (NB) controlling a source cell a measurement report, which may point out a target cell, and normally, may indicate that this target cell has a better channel quality than the source cell. The source NB then may send a message to the NB controlling the target cell (target NB) for a handover preparation. This message usually carries the UE context that includes the data radio bearers (DRBs) that are used by the UE, the corresponding configuration for layer, like packet data convergence protocol (PDCP) layer, radio link control (RLC) layer, etc., and the radio configuration.

[0019] The target NB may reply with an acknowledgment which contains the certain configuration such as for example radio resource control (RRC) configuration that the UE will use when it accesses the target cell. This configuration may include a new configuration of the UE including radio configuration that should be used in target cell. The source NB then may send to the UE a handover command. In some example embodiments, the handover command may be included in a RRC reconfiguration message. After receiving the handover command, the UE may immediately establish connection to the target cell, without sending any confirmation message to the source NB. The UE may send a message such as for example, a RRC reconfiguration complete message to the target NB and applies the RRC configuration received in the handover command. The target NB then may inform the source cell that the handover was successful and the source cell can release the resources allocated to the UE.

[0020] On the other hand, in the case of conditional handover (CHO), after receiving a handover command, the UE will not immediately establish a connection to the target cell, but will wait until a given condition is met.

[0021] Figure 1 illustrates a CHO message flow in accordance with various example embodiments. In an example embodiment of Figure 1, a UE sends a measurement report to a source NB controlling a source cell at step 101. The report may indicate a target cell with a channel quality that makes the target cell a potential handover target, such as for example, the channel quality of the target cell being better than that of the source cell minus a given threshold. At step 102, the source NB sends a CHO request to the target NB controlling the target cell. The CHO request may contain the UE context. The target NB replies at step 103 with a CHO acknowledgement. This acknowledgement may include certain parameters such as for example RRC target configuration that the UE will use at the target cell.

[0022] At step 104, the source NB sends to the UE a CHO Command included in a RRC reconfiguration message. This message contains the RRC target configuration delivered by the target cell and optionally a condition for the CHO to be executed. At step 105, the UE sends a RRC reconfiguration complete message to the source NB to confirm the reception of the RRC reconfiguration message. The UE then waits for the conditions for CHO to be fulfilled and in the same time may continue communication with the source cell. At step 106, the condition for CHO is fulfilled. The condition may be for example that the target cell channel quality is above a threshold or better than the channel quality of the source cell plus or minus a threshold. Then the UE connects to the target cell, and sends another RRC reconfiguration complete message to the target cell at step 107. At step 108, the target NB informs the source NB that the CHO was successful.

[0023] In the case of CHO, the UE can quickly perform the HO when the radio conditions are met, as some of the preparation messages between the source cell and the target cell has already been exchanged. In BHO, there are messages exchanged between UE and source cell and between source NB and target NB that slow down the process when the handover parameters are met. [0024] In the case of CHO, when the UE waits for the conditions for CHO to be fulfilled, the configuration of the UE may change. The network may have to send another RRC reconfiguration message to change the UE configuration. This could happen for example if a voice call is terminated so that the network needs to de-configure the associated DRBs. This mean that the network needs to know what the UE RRC configuration is and thus needs to know if the UE has received and implemented the RRC reconfiguration message that contained the CHO command. Note that the RRC reconfiguration message could also contain other reconfiguration not related to the CHO, for example an update on the radio configuration or a change of configuration of the layers like PDCP, RLC, etc.

[0025] If the UE fails to send the RRC reconfiguration complete message at step 105 because of bad radio condition, the UE will try to reconnect to the network, but then there is some uncertainty about the UE configuration because the network does not know whether the last RRC reconfiguration message has been implemented or not. Because of this uncertainty, the network usually rejects the UE reconnection and send it to idle mode. This may delay the execution of CHO. Especially, if the CHO command (included in the RRC Reconfiguration message) is sent late, it is possible that the condition to trigger the execution of the CHO is immediately met. In this case, the UE will not perform the CHO if it can't send the RRC reconfiguration complete message even if the condition to execute the CHO is met. That means the UE will lose time because of trying to send the RRC reconfiguration complete message instead of executing the CHO to the target cell. On the other hand, the UE also may have difficulties to send the RRC reconfiguration complete message leading to call drop as described above. Therefore, a scheme for conditional handover confirmation optimization may be needed.

[0026] In an example embodiment, when the UE is configured for CHO and the condition to execute the CHO is immediately met, or met within a given time, the UE does not send an acknowledge message, such as for example RRC reconfiguration complete message, to the source cell, but executes the CHO and sends a message to the target cell. If the condition to trigger the CHO is not met within a given time, the UE may send an acknowledge message to the source cell.

[0027] Figure 2 illustrates a CHO message flow with a timer in accordance with various example embodiments. In an example embodiment of Figure 2, a UE sends a measurement report to a source NB controlling a source cell at step 201. The report may indicate a target cell with a channel quality that makes the target cell a potential handover target, such as for example, the channel quality of the target cell being better than that of the source cell minus a given threshold. At step 202, the source NB sends a CHO request to the target NB controlling the target cell. The CHO request may contain the UE context. The target NB replies at step 203 with a CHO acknowledgement. This acknowledgement may include certain parameters such as for example RRC target configuration that the UE will use at the target cell. [0028] At step 204, the source NB sends to the UE a CHO Command included in a RRC reconfiguration message. This message contains the RRC target configuration delivered by the target cell and optionally a condition for the CHO to be executed. At step 205, the UE starts a timer and waits for the conditions for CHO to be fulfilled. In the same time the UE may continue communication with the source cell. At step 206, the condition for CHO is fulfilled before the timer expires. The condition may be for example that the target cell channel quality is above a threshold or better than that of the source cell plus or minus a threshold. Then the UE connects to the target cell, and sends a RRC reconfiguration complete message to the target cell at step 207. At step 208, the target NB informs the source NB that the CHO was successful.

[0029] Figure 3 illustrates another CHO message flow with a timer in accordance with various example embodiments. In an example embodiment of Figure 3, a UE sends a measurement report to a source NB controlling a source cell at step 301. The report may indicate a target cell with a channel quality that makes the target cell a potential handover target, such as for example, the channel quality of the target cell being better than that of the source cell minus a given threshold. At step 302, the source NB sends a CHO request to the target NB controlling the target cell. The CHO request may contain the UE context. The target NB replies at step 303 with a CHO acknowledgement. This acknowledgement may include certain parameters such as for example RRC target configuration that the UE will use at the target cell.

[0030] At step 304, the source NB sends to the UE a CHO Command included in a RRC reconfiguration message. This message contains the RRC target configuration delivered by the target cell and optionally a condition for the CHO to be executed. At step 305, the UE starts a timer and waits for the conditions for CHO to be fulfilled. In the same time the UE may continue communication with the source cell. At step 306, the timer expires before the condition for CHO is met. The UE then sends a RRC reconfiguration complete message to the source cell to confirm the reception of the RRC reconfiguration message at step 307. At step 308, the condition for CHO is fulfilled. The condition may be for example that the target cell channel quality is above a threshold or better than that of the source cell plus or minus a threshold. Then the UE connects to the target cell, and sends another RRC reconfiguration complete message to the target cell at step 309. At step 310, the target NB informs the source NB that the HO was successful.

[0031] In an example embodiment, the timer may be configured based on cell load or measurement result of source cell or/and target cell. It may be derived from CHO success rate from source cell to target cell, or may be derived from the number of radio link failures that happen during CHO from source to target cell. In an example embodiment, the start of the timer may be conditioned by the channel quality level of the serving cell, the target cell or the difference of the two. For example, if the UE is far from the target cell so that the channel quality level of the target is way below the source cell, there may be no need to trigger the timer and the UE can send a RRC reconfiguration complete message immediately to the source cell.

[0032] Reference is made to Figure 4 for illustrating a simplified block diagram of an example apparatus that is suitable for use in practicing various example embodiments of this application. In Figure 4, a user equipment, UE, 401, is adapted for communication with other network entity, which is not shown for brevity. The UE 401 includes at least one processor 405, at least one memory (MEM) 404 coupled to the at least one processor 405, and a suitable transceiver (TRANS) 403 (having a transmitter (TX) and a receiver (RX)) coupled to the at least one processor 405. The at least one MEM 404 stores a program (PROG) 402. The TRANS 403 is for bidirectional wireless communications with other network entity.

[0033] The UE 401 may further include a CHO process unit 406. The unit 406, together with the at least one processor circuitry 405 and the PROG 402, may be utilized by the UE 401 in conjunction with various example embodiments of the application, as described herein.

[0034] In general, the various example embodiments of the apparatus 401 can include, but are not limited to, cellular phones, personal digital assistants (PDAs) having wireless communication capabilities, portable computers having wireless communication capabilities, image capture devices such as digital cameras having wireless communication capabilities, gaming devices having wireless communication capabilities, music storage and playback appliances having wireless communication capabilities, internet appliances permitting wireless internet access and browsing, as well as portable units or terminals that incorporate combinations of such functions.

[0035] In some example embodiments, the UE 401 may include one or more processors, one or more computer-readable storage medium (for example, memory, storage, or the like), one or more radio access components (for example, a modem, a transceiver, or the like), and/or a user interface. In some embodiments, the UE 401 may be configured to operate using one or more radio access technologies, such as GSM, LTE, LTE-A, NR, 5G, WLAN, narrow band IoT, Bluetooth, near field communication (NFC), MulteFire, and/or any other radio access technologies. It should be noted that one of ordinary skill in the art would understand that UE 401 may include components or features not shown in Figure 4, such as for example, an input and/or output device (EO device), or a user interface, such as a graphical user interface or touchscreen.

[0036] The PROGs 402 is assumed to include program instructions that, when executed by the associated processor, enable the electronic apparatus to operate in accordance with the example embodiments of this disclosure, as discussed herein.

[0037] The example embodiments of this disclosure may be implemented by computer software or computer program code executable by one or more of the processor circuitries 405 of the UE 401, or by hardware, or by a combination of software and hardware. [0038] The MEM 404 may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as non-limiting examples. The processor circuitry 405 may be of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multi-core processor architecture, as non-limiting examples.

[0039] Without in any way limiting the scope, interpretation, or application of the claims appearing below, a technical effect of one or more of the example embodiments disclosed herein may be to allow a source cell to know the state of a UE and possibly reconfigure it if needed during a conditional handover procedure. Another technical effect may be a prompt execution of CHO upon the fulfillment of condition without delay, therefore minimizing call drop.

[0040] Embodiments of the present invention may be implemented in software, hardware, application logic or a combination of software, hardware and application logic. The software, application logic and/or hardware may reside on an apparatus such as a user equipment, a gNB or other mobile communication devices. If desired, part of the software, application logic and/or hardware may reside on a network element, part of the software, application logic and/or hardware may reside on a UE 401, and part of the software, application logic and/or hardware may reside on other chipset or integrated circuit. In an example embodiment, the application logic, software or an instruction set is maintained on any one of various conventional computer-readable media. In the context of this document, a“computer-readable medium” may be any media or means that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device. A computer-readable medium may comprise a non-transitory computer-readable storage medium that may be any media or means that can contain or store the instructions for use by or in connection with an instruction execution system, apparatus, or device.

[0041] It is also noted herein that while the above describes example embodiments of the invention, these descriptions should not be viewed in a limiting sense. Rather, there are several variations and modifications which may be made without departing from the scope of the present invention.

[0042] Further, the various names, such as for example, the names of channels or messages used for illustration are not intended to be limiting in any respect, as they may be identified by any suitable names.

[0043] If desired, the different functions discussed herein may be performed in a different order and/or concurrently with each other. Furthermore, if desired, one or more of the above-described functions may be optional or may be combined. As such, the foregoing description should be considered as merely illustrative of the principles, teachings and example embodiments of this invention, and not in limitation thereof.

[0044] According to a first embodiment, a method may include receiving a conditional handover command; starting a timer; determining whether a condition for handover is fulfilled before the timer expires; and if the condition is fulfilled before the timer expires, connecting to a target cell and indicating to the target cell that the handover has been performed.

[0045] In a variant, if the timer expires before the condition is fulfilled, indicating to a serving cell that the conditional handover command has been received.

[0046] In a further variant, the conditional handover command includes the condition for the handover to be executed.

[0047] In a further variant, the timer is started only if the channel quality of source cell, target cell or both fulfill certain condition.

[0048] According to a second embodiment, an apparatus can include at least one processor and at least one memory and computer program code. The at least one memory and the computer program code can be configured to, with the at least one processor, cause the apparatus at least to perform a method according to the first embodiment, and any of its variants.

[0049] According a third embodiment, an apparatus can include means for performing the method according to the first embodiment, and any of its variants.

[0050] According to a fourth embodiment, a computer program product may encode instructions for performing a process including a method according to the first embodiment, and any of its variants.

[0051] According to a fifth embodiment, a non-transitory computer-readable medium may encode instructions that, when executed in hardware, perform a process including a method according to the first embodiment, and any of its variants.

[0052] According to a sixth embodiment, a computer program code may include instructions for performing a method according to the first embodiment, and any of its variants.