Joint preparation of lower layer triggered mobility and conditional handover

By determining a timing advance value for a CHO candidate cell using an LTM candidate cell's value, the method enables RACH-less handovers, addressing the challenge of seamless transitions in wireless communication networks.

WO2026238334A1PCT designated stage Publication Date: 2026-11-19NOKIA TECHNOLOGIES OY
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/EP2026/060727
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-16
Filing Date
2026-04-14
Publication Date
2026-11-19

AI Technical Summary

Technical Problem

Existing handover procedures in wireless communication, such as Layer 3-based Conditional Handover (CHO) and Layer 1/Layer 2-based Mobility (LTM), face challenges in ensuring seamless transitions without random-access channel procedures, particularly when timing advance values are not synchronized across different cells.

Method used

A method is disclosed where a UE determines a timing advance value for a CHO candidate cell based on an already obtained value for an LTM candidate cell, enabling RACH-less handover by ensuring time synchronization and meeting specific criteria, thereby facilitating joint preparation of LTM and CHO.

Benefits of technology

This approach allows for seamless and robust handovers by eliminating the need for full random-access procedures, reducing interruption time and enhancing network efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure EP2026060727_19112026_PF_FP_ABST
    Figure EP2026060727_19112026_PF_FP_ABST
Patent Text Reader

Abstract

A user device may be configured to receive, from a serving network node, a first configuration for a lower-layer triggered mobility, LTM, and a second configuration for a conditional handover, CHO; receive, from the serving network node, information indicative of a time synchronization between at least one LTM candidate cell associated with the first configuration and at least one CHO candidate cell associated with the second configuration; acquire, from the serving network node, a first timing advance, TA, for the at least one LTM candidate cell; and determine, based on the information indicative of the time synchronization, a second TA for the at least one CHO candidate cell, wherein the second TA is determined using the first TA and radio measurements obtained from the at least one CHO candidate cell and the at least one LTM candidate cell.
Need to check novelty before this filing date? Find Prior Art

Description

JOINT PREPARATION OF LOWER LAYER TRIGGERED MOBILITY AND CONDITIONAL HANDOVERTECHNICAL FIELD

[0001] Various example embodiments generally relate to the field of wireless communication. Some example embodiments relate to a signalling enhancement for joint preparation of lower layer triggered mobility, LTM, and conditional handover, CHO.BACKGROUND

[0002] Handover is a procedure that allows a user equipment (UE) in connected mode to stay connected when the UE moves from one cell to another. New Radio (NR) supports different types of handover procedures, including Layer 3-based CHO, wherein the handover is executed only when the configured CHO execution condition(s) are met, and LTM, wherein the handover is executed based on Layer 1 measurements performed by the UE. The UE can be also configured with multiple handover procedures by the network for additional robustness. However, it would be beneficial to improve one or more aspects related to the handover procedures to ensure a seamless handover in different scenarios.SUMMARY

[0003] This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

[0004] Example embodiments of the present disclosure enable a UE to determine a timing advance value for a CHO candidate cell based on a timing advance value obtained for an LTM candidate cell. Further, a handover to the CHO candidate cell can be executed by the UE without a random-access procedure using the determined timing advance value. This and other benefits may be achieved by the features of the independent claims. Further example embodiments are provided in the dependent claims, the description, and the drawings.

[0005] Example embodiments of the present disclosure can provide apparatuses, methods, computer programs, computer program products, or computer readable media for improving various aspects of handover related procedures. Any example embodiment may be combined with one or more other example embodiments. These and other aspects of the present disclosurewill be apparent from the example embodiment s) described below. According to some aspects, there is provided the subject matter of the independent claims. Some further aspects are defined in the dependent claims.DESCRIPTION OF THE DRAWINGS

[0006] The accompanying drawings, which are included to provide a further understanding of the example embodiments and constitute a part of this specification, illustrate example embodiments and, together with the description, help to explain the example embodiments. In the drawings:

[0007] FIG. 1 illustrates an example of a communication network;

[0008] FIG. 2 illustrates an example of an apparatus configured to practice one or more example embodiments;

[0009] FIG. 3 illustrates an example of signalling and operations for determining a timing advance value for a CHO candidate cell using a timing advance value for an LTM candidate cell;

[0010] FIG. 4 illustrates an example of signalling and operations for execution of a RACH-less CHO using UE based timing advance acquisition;

[0011] FIG. 5 illustrates an example of a method for RACH-less CHO execution;

[0012] FIG. 6 illustrates an example of a method for assisting in RACH-less CHO execution;

[0013] FIG. 7 illustrates an example of a method for determining a timing advance value for a CHO candidate cell; and

[0014] FIG. 8 illustrates an example of a method for assisting in determining a timing advance value for a CHO candidate cell.

[0015] Like references are used to designate like parts in the accompanying drawings.DETAILED DESCRIPTION

[0016] Reference will now be made in detail to example embodiments, examples of which are illustrated in the accompanying drawings. The detailed description provided below in connection with the appended drawings is intended as a description of the present examples and is not intended to represent the only forms in which the present example may be constructed or utilized. The description sets forth the functions of the example and the sequence of stepsfor constructing and operating the example. However, the same or equivalent functions and sequences may be accomplished by different examples.

[0017] FIG. 1 illustrates an example of a communication network. Communication network 100 may comprise one or more access nodes 104, 106. Access node(s) 104, 106 may be part of a radio access network (RAN) configured to enable a device, represented throughout the description by UE 102, to access communication services provided by core network (not shown). In connection with communication network 100, access node(s) 104, 106 and core network may be collectively referred to as the ‘network’. UE 102 may comprise a user device, a terminal apparatus, a terminal device, a mobile device, or the like. A terminal device may comprise a device to which a connection from a communication network is terminated. UE 102 may be configured to communicate with access node(s) 104, 106 over a radio interface, which may be also referred to as an air interface. Access nodes 104, 106 may be also referred to as network devices, radio access network nodes or base stations.

[0018] The radio interface may be configured for example based on the 5G NR (New Radio) standard defined by the 3rdGeneration Partnership Project (3 GPP), or any future standard or technology (e.g., 6G). Access nodes 104, 106 may comprise, for example, 5thgeneration access nodes (gNB). Transmission by an access node to UE 102 may be called downlink (DL) transmission. Transmission by UE 102 to an access node may be called uplink (UL) transmission. UE 102 may be therefore configured to operate as a transmitter for uplink transmissions and as a receiver for downlink transmissions. Access node(s) 104, 106 may be configured to operate as a receiver for uplink transmissions and as a transmitter for downlink transmissions. Communication network 100 may comprise a wireless communication network or a mobile communication network, such as for example a cellular communication network.

[0019] Communication network 100 may be operated based on a protocol stack comprising a plurality of protocol layers. The protocol stack may be arranged based on the open systems interconnection (OSI) model or a layer model of a particular standard such as 3GPP 5G NR. As one example, the protocol stack may comprise a service data adaptation protocol (SDAP) layer, which may receive data from an application layer for transmission. The SDAP layer may be configured to exchange data with the packet data convergence (PDCP) layer. The PDCP layer may be responsible of generation of data bursts comprising one or more data packets, for example based on data obtained from the SDAP layer.

[0020] The PDCP layer may provide data to one or more instances of the radio link control (RLC) layer. For example, PDCP data may be transmitted on one or more RLC transmissionlegs. Each RLC instance may be associated with corresponding medium access control (MAC) instances of the MAC layer. The MAC layer may provide a mapping between logical channels of upper layer(s) and transport channels of the physical layer, handle multiplexing and demultiplexing of MAC service data units (SDU). Furthermore, the MAC layer may provide error correction functionality based on packet retransmissions, for example according to the hybrid automatic repeat request (HARQ) process. MAC, RLC and PDCP may be referred to as Layer 2 (L2). Physically separate transmission legs may be provided by the physical (PHY) layer, also known as Layer 1 (LI). A radio resource control (RRC) layer of the protocol stack may be configured to manage configuration, connection, and release of radio resources. The RRC layer may be also referred to as Layer 3 (L3). Corresponding protocol stacks may be applied both at access nodes 104, 106 and UE 102.

[0021] In a split access node architecture, part of the protocol layers may be implemented at a central unit (CU) of an access node, e.g., a gNB-CU, which may be configured to handle upper layers of the protocol stack, for example SDAP and PDCP layers. Furthermore, the central unit may be configured to handle RRC operations. A central unit of an access node may be associated with, e.g., configured to control, one or more distributed units (DU) of the access node, e.g., gNB-DU, which may be configured to handle lower layers of the protocol stack, for example RLC, MAC, and LI. Radio unit(s) of the distributed unit(s) may be configured to transmit data to UE(s) and receive data from UE(s) over the radio interface. A central unit may be referred to as a central node and a distributed unit may be referred to as a distributed node.

[0022] Communication network 100 may comprise other network function(s), network device(s), or protocol(s), in addition, or alternative to, those illustrated in FIG. 1. A network device may be configured to implement functionality of one or more network functions. Even though some embodiments have been described in the context of 5G, it is appreciated that embodiments of the present disclosure are not limited to this example network. Example embodiments may be therefore applied in any present or future communication networks. An apparatus, such as for example UE 102 or access node 104, 106, may comprise, or be configured to implement, e.g., by means of software, one or more of the protocol layers described herein.

[0023] An access node 104, 106 may be configured to communicate with UEs via one or more cells 108, 110. For example, access node 104 may be configured to serve UEs at a cell 108. Access node 106 may be configured to serve UEs at a cell 110. A cell may be configured to serve UEs at a certain geographical area at a certain radio frequency, or, a range of radiofrequencies around a centre frequency of the cell. When the UE 102 in connected state moves from the coverage area of one cell to another, a handover procedure is performed. A cell currently serving the UE may be referred to as a serving cell or a source cell. A cell to which the UE is being handed over may be referred to as a candidate cell or a target cell. After a successful handover the target cell becomes the serving cell. A cell that is geographically close to a serving cell and is a potential candidate for handover when UE moves or experiences degraded signal quality may be referred to as a neighboring cell. Intra-gNB, or intra-CU, handover refers to a case wherein the serving cell and the target cell(s) are from the same gNB. Inter-gNB, or inter-CU, handover refers to a case where the serving cell and the target cell both belong to different gNBs.

[0024] CHO refers to a handover that is executed by the UE when one or more configured CHO execution conditions are met. LTM refers to a handover triggered via L1 / L2 signalling performed and reported by the UE. LTM may be referred to as L1 / L2 triggered mobility or L1 / L2 based mobility. LTM may be also provided with conditional configuration. The conditional configuration may be received by the UE from a serving cell, for example, via a RRC reconfiguration message. The conditional configuration may include LTM candidate configurations and the corresponding execution conditions. Further, the candidate cells can provide their own execution conditions for the conditional LTM (C-LTM). C-LTM may be used to perform RACH-less and RACH based intra-CU handovers. RACH refers to a randomaccess channel procedure. A RACH-less handover refers to a handover performed without the random-access channel procedure or without a full random-access channel procedure. Full RACH procedure is considered to comprise all the steps of the RACH procedure, e.g. all four steps of a 4-step RACH (Msgl, Msg2, Msg3, Msg4). Msgl comprises of broadcasting the RACH preamble by the UE in uplink. Msg2 (random access response, RAR) of the RACH procedure includes the transfer of TA value to the UE via RAR. Further, early TA acquisition (early synchronization, ‘early sync’) is supported for the C-LTM.

[0025] In conventional (non-conditional) LTM, the serving DU stores the TA value obtained during early sync and subsequently provides the TA value to the UE via MAC CE cell switch command during the execution phase of the handover. The execution phase is triggered based on UE measurements. Conversely, C-LTM may operate without any such explicit cell change command from the network, and therefore, the network may need to share the TA value with the UE in advance. In case of C-LTM, the TA value may be provided by the network via MACCE (MAC control element) signalling. The TA for the candidate cell may be maintained by a maintenance timer.

[0026] For L3 -based CHO, no early sync procedures are currently defined. Therefore, RACH-less access to the candidate cell may be possible only for a few limited cases. More specifically, CHO RACH-less access to the candidate cell may be performed in case the TA value of the candidate cell is either zero or the same as the TA value of the serving cell. In this case, the TA value (zero or the value of the serving cell) is indicated by the candidate cell in the RRC configuration provided to the UE in a handover command.

[0027] When UE is in connected mode, the UE has TA for the serving cell. In case of LTM, the UE may be configured with a capability to determine the TA towards a neighboring cell based on knowledge about the TA of the serving cell and measurement on the neighboring cell. The configuration may be provided by a source gNB in information elements (IES) indicating an LTM configuration (e.g., LMT-Config) and LTM candidate cell(s) (e.g., LTM-Candidate). The LTM-Config IE can comprise a field for measured TA of the serving cell (e.g., Itm-ServingCellUE-MeasuredTA-ID) and the LTM-Candidate IE can comprise a field for a measured TA of the candidate cell (e.g., Itm-UE-MeasuredTA-ID). If the value of the Itm-ServingCellUE-MeasuredTA-ID of the serving cell matches the Itm-UE-MeasuredTA-ID of the candidate cell, the UE is allowed to perform UE-based TA estimation for that candidate cell during its stay within the current serving cell. For example, the UE can estimate the TA using a first transmission on the candidate cell that is performed after a reception of a cell switch command for the candidate cell.

[0028] The procedure of UE-based TA acquisition is now described with reference to FIG. 1. First, the UE 102 may determine a receive (Rx) timing difference of measured DL synchronization signal from a cell with respect to the serving cell (e.g., cell 108), and multiply the Rx timing difference by two to consider the propagation delay in the round trip of the signal. Here, the signal is assumed to have symmetrical DL and UL path. Further, the TA corresponding to the serving cell of the UE 102 is known by the UE 102. The serving network (e.g., the access node 104) may then configure to the UE 102 to determine TA for a neighboring cell (e.g., cell 110). The configuration may be performed, for example, with the LTM-Config and LTM-Candidate as already described. The UE 102 can determine the TA for the neighboring cell based on the received configuration and L3 measurements on the serving cell and the neighboring cell.

[0029] The timing advance for the neighboring cell can be determined as follows:TAneighborCell ^serving Cell +2( / ?x timing difference between serving cell and neighboring cell) — 2(TAE) — OtherEstError,wherein TAE is a timing advance error. The term “OtherEstError” refers to any measurement error that may stem from factors like:• error caused by the UL / DL reciprocity• estimator implementation error• estimator method error.Herein, OtherEstError is assumed to be zero or to be known by the UE 102. When the cells 108 and 110 are well synchronized, TAE, which is a relative difference in time of transmission of the simultaneous signals between any pair of cells, can be assumed to be zero. It is noted that in order to compute the TA of the neighboring cell based on the TA of the serving cell and related measurements, an assumption is that the neighboring cell and the serving cell are in time sync.

[0030] In one example, the UE 102 may be configured both with intra-CU C-LTM and inter-CU CHO. Such configurations may be performed by the network, for example, to ensure additional robustness. For example, in case the C-LTM cell switch command is not received, the UE 102 may benefit from having also the CHO configuration provided and execute the handover towards a candidate cell autonomously.

[0031] Based on L3 radio condition, a source-CU may start preparing both intra-CU C-LTM and inter-CU CHO, configured to different candidate cells belonging to different target DUs. Thereafter, the network can share RRC reconfiguration message to the UE 102 consisting of L1 / L3 configuration for C-LTM as well as L3 configuration for CHO. Based on a favourable LI measurement report received by the source-DU from the UE 102, early synchronization is activated for C-LTM. The source-DU triggers early TA acquisition procedure for the UE 102, and the UE 102 acquires the TA corresponding to the C-LTM candidate cell in the target DU along with TA maintenance timer via a MAC CE message from the source-DU.

[0032] However, after obtaining the early TA and synchronization with C-LTM candidate cell, depending on the radio condition, CHO execution condition may be met before the C-LTM execution condition is met. In such situation, the UE 102 may fall back to RACH-based CHO execution, where synchronization and TA acquisition need to be performed again for a different candidate cell. Therefore, the benefits of early synchronization of the C-LTM (e.g.,fast cell switching and increased robustness) may not be leveraged out, thus resulting in increased interruption time.

[0033] Since candidate cells for C-LTM and CHO belong to different CUs, there is a small chance that the candidate cells would belong to the same TA group. Therefore, direct reuse of the acquired TA for the C-LTM candidate cell to access the CHO candidate cell may not be possible.

[0034] An objective is to facilitate an indirect way of avoiding full RACH before CHO execution. A method is disclosed herein, where the TA of a candidate cell corresponding to CHO is obtained by a UE using an already obtained TA of a candidate cell corresponding to C-LTM or LTM. Furthermore, a RACH-less CHO execution is enabled based on the obtained TA for CHO.

[0035] First, a joint preparation of LTM, e.g., C-LTM, and CHO for different candidate cells may be performed for the UE. In one embodiment, the UE may be configured to execute a RACH-less CHO procedure instead of triggering a RACH-based CHO cell switch towards a best candidate cell upon detecting that one or more criteria are met. A first criterion may comprise that at least one CHO execution condition is satisfied first before any C-LTM execution condition is satisfied. A second criterion may comprise that RACH based TA for C-LTM candidate cell (or LTM candidate cell depending on configuration) is already obtained, for example, as a result of early synchronization procedure. A third criterion may comprise that the LTM / C-LTM candidate cell(s) and the CHO candidate cell(s) are in time synchronization. A fourth criterion may comprise that at least one indication that the UE is allowed to determine TA for the CHO candidate cell based on the TA for the LTM / C-LTM candidate cell. Based on the one or more criteria being met, the UE attempts to obtain a UE-based TA estimate to the CHO candidate cell using the obtained TA for the LTM / C-LTM candidate cell and a DL timing difference between the CHO candidate cell and LTM / C-LTM candidate cell.

[0036] In one embodiment, the UE may be configured to receive information indicative of time synchronization between the LTM / C-LTM candidate cell(s) and the CHO candidate cell(s). The UE may be further configured to obtain the UE-based TA estimate to the CHO candidate cell using the obtained TA for the LTM / C-LTM candidate cell and a DL timing difference between the CHO candidate cell and LTM / C-LTM candidate cell based on the received information indicative of the time synchronization.

[0037] During the preparation of CHO and LTM / C-LTM, a network node (e.g., target-CU or source-CU) may be configured to detect that one or more conditions for triggering the RACH-less CHO procedure at the UE is met. A first condition may comprise that the UE is capable of performing UE based TA estimation. A second condition may comprise a time synchronization status of the LTM / C-LTM and CHO candidate cells. Based on the one or more conditions being met, the network node may indicate to the UE that the RACH-less CHO procedure can be performed. In one example, the network node may set the same UE based TA ID for the LTM / C-LTM candidate cell(s) and the CHO candidate cell(s) to provide the indication. In one example, the network node may use a dedicated indicator for the purpose.

[0038] Once the UE has successfully obtained the TA for the CHO, the UE may be configured to notify the CHO candidate cell about a best beam via which beam the EU expects to receive a first PDCCH (physical downlink control channel). This enables to pave the way for seamless RACH-less CHO cell switch to the CHO candidate cell. Finally, the UE may execute a handover to the CHO candidate cell using the TA value obtained for the CHO candidate cell based on the previously obtained TA value for the C-LTM candidate cell.

[0039] FIG. 2 illustrates an example of an apparatus configured to practice one or more example embodiments. Apparatus 200 may comprise a device such as UE 102, or an access node 104, 106, an access point, a base station, a radio network node, or a split portion thereof (e.g., a central or distributed unit of an access node), a network device, a terminal device, an internet-of-things (loT) device, a wearable device, a vehicle, or in general any apparatus configured to implement functionality described herein.

[0040] The apparatus 200 may comprise at least one processor 202. The at least one processor 202 may comprise, for example, one or more of various processing devices, such as for example a co-processor, a microprocessor, a controller, a digital signal processor (DSP), a processing circuitry with or without an accompanying DSP, or various other processing devices including integrated circuits such as, for example, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a microcontroller unit (MCU), a hardware accelerator, a special-purpose computer chip, or the like.

[0041] The apparatus 200 may further comprise at least one memory 204. The memory 204 may be configured to store, for example, computer program code or the like, for example operating system software and application software. The memory 204 may comprise one or more volatile memory devices, one or more non-volatile memory devices, and / or a combination thereof. For example, the memory 204 may be embodied as magnetic storage devices (such as hard disk drives, magnetic tapes, etc.), optical magnetic storage devices, or semiconductor memories (such as mask ROM, PROM (programmable ROM), EPROM(erasable PROM), flash ROM, RAM (random access memory), etc.). The memory 204 is provided as an example of a (non-transitory) computer readable medium. The term “non-transitory,” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM).

[0042] The apparatus 200 may further comprise a communication interface 208 configured to enable the apparatus 200 to transmit information to other devices, such as user devices and / or network devices, and to receive information from the other devices. The communication interface 208 may comprise an external communication interface, such as for example a radio interface between UE 102 and access node(s) 104, 106, or a communication interface between a central unit and distributed unit(s) of an access node (e.g., an Fs-U and / or Fs-C interface). The communication interface 208 may comprise one or more radio transmitters or receivers, which may be coupled to one or more antennas of the apparatus 200, or be configured to be coupled to one or more antennas external to the apparatus 200.

[0043] The apparatus 200 may further comprise other components and / or functions such as a user interface (not shown) comprising at least one input device and / or at least one output device. The input device may take various forms such a keyboard, a touch screen, or one or more embedded control buttons. The output device may for example comprise a display, a speaker, or the like.

[0044] When the apparatus 200 is configured to implement some functionality, some component and / or components of the apparatus 200, such as for example the at least one processor 202 and / or the at least one memory 204, may be configured to implement this functionality. Furthermore, when the at least one processor 202 is configured to implement some functionality, this functionality may be implemented using program code 206 comprised, for example, in the at least one memory 204. The program code 206 may comprise instructions which, when executed by the at least one processor 202, cause the apparatus to implement at least some functionality described herein.

[0045] According to a first aspect, the apparatus 200 may comprise a user device. The user device may comprise the at least one processor 202; and the at least one memory 204 comprising instructions which, when executed by the at least one processor, cause the apparatus 200 at least to receive, from a serving network node, a first configuration for a lower-layer triggered mobility, LTM, and a second configuration for a conditional handover, CHO; acquire, using the first configuration, a first timing advance, TA, for at least one LTM candidate cell; determine that one or more criteria for a handover without a random-access procedure are metfor at least one CHO candidate cell; and upon determining that the one or more criteria are met, determine a second TA for the at least one CHO candidate cell based on: the first TA for the at least one LTM candidate cell, and obtained radio measurements between the at least one LTM candidate cell and the at least one CHO candidate cell; and execute, using the second configuration and the second TA, the handover to the at least one CHO candidate cell without the random-access procedure.

[0046] In an embodiment of the first aspect, the first configuration is for conditional LTM, C-LTM, or for non-conditional LTM.

[0047] In an embodiment of the first aspect, the one or more criteria comprise at least one of the following: the at least one LTM candidate cell is in time synchronization with the at least one CHO candidate cell; at least one of the first configuration or the second configuration comprises an indication that the user device is allowed to use the first TA for the at last one LTM candidate cell to determine the second TA for the at least one CHO candidate cell; one or more execution conditions for CHO are met before at least one execution condition for LTM is met.

[0048] In an embodiment of the first aspect, the instructions, when executed by the at least one processor 202, cause the user device to: receive, from the serving network node, information on that the at least one LTM candidate cell is in time synchronization with the at least one CHO candidate cell; and determine that the at least one LTM candidate cell is in time synchronization with the at least one CHO candidate cell based on the received information.

[0049] In an embodiment of the first aspect, the information on that the at least one LTM candidate cell is in time synchronization with the at least one CHO candidate cell is based on the first configuration and the second configuration including matching identifiers.

[0050] In an embodiment of the first aspect, the instructions, when executed by the at least one processor, cause the user device to: detect, based on the first configuration and the second configuration, that one or more execution conditions for CHO are met before at least one execution condition for LTM is met; and determine, responsive to the detection, to execute the handover to the at least one CHO candidate cell without the random-access procedure.

[0051] In an embodiment of the first aspect, the first TA and the second TA have different values.

[0052] In an embodiment of the first aspect, the instructions, when executed by the at least one processor 202, cause the user device to: transmit, to the serving network node prior to the execution of the handover, an indication of a beam towards the at least one CHO candidatecell; and monitor for a transmission from the at least one CHO candidate cell via the indicated beam.

[0053] In an embodiment of the first aspect, the instructions, when executed by the at least one processor 202, cause the user device to: perform layer 3 measurements corresponding to the at least one CHO candidate cell; and wherein the indication of the beam is based on the layer 3 measurement results.

[0054] In an embodiment of the first aspect, the first configuration is for one of intracentralized unit, intra-CU LTM, intra-CU C-LTM, inter-CU LTM or inter-CU C-LTM; and the second configuration is for inter-CU CHO.

[0055] In an embodiment of the first aspect, the first TA is acquired using an early synchronization procedure.

[0056] In an embodiment of the first aspect, the instructions, when executed by the at least one processor 202, cause the user device to: measure downlink reference signals from the at least one LTM candidate cell and the at least one CHO candidate cell to obtain the radio measurements; determine a timing difference based on the measured reference signals; and compute the second TA using the timing difference.

[0057] According to a second aspect, the apparatus 200 may comprise a network device. The network device may comprise the at least one processor 202; and the at least one memory 204 storing instructions which, when executed by the at least one processor 202, cause the network device at least to: detect that least one lower-layer triggered mobility, LTM, candidate cell and at least one conditional handover, CHO, candidate cell are in time synchronization; transmit, to a user device based on the detected time synchronization, a first configuration for LTM and a second configuration for CHO, wherein at least one of the first configuration or the second configuration comprises information indicative that at least one criteria for a handover without a random-access procedure is met for the at least one CHO candidate cell.

[0058] According to a third aspect, the apparatus 200 may comprise a user device. The user device may comprise the at least one processor 202; and the at least one memory 204 storing instructions which, when executed by the at least one processor 202, cause the user device at least to: receive, from a serving network node, a first configuration for a lower-layer triggered mobility, LTM, and a second configuration for a conditional handover, CHO; receive, from the serving network node, information indicative of a time synchronization between at least one LTM candidate cell associated with the first configuration and at least one CHO candidate cell associated with the second configuration; acquire, from the serving network node, a first timingadvance, TA, for the at least one LTM candidate cell; and determine, based on the information indicative of the time synchronization, a second TA for the at least one CHO candidate cell, wherein the second TA is determined using the first TA and radio measurements obtained from the at least one CHO candidate cell and the at least one LTM candidate cell.

[0059] In an embodiment of the third aspect, the information indicative of the time synchronization is comprised in at least one of the first configuration or the second configuration.

[0060] In an embodiment of the third aspect, the information indicative of the time synchronization between the at least one LTM candidate cell and the at least one CHO candidate cell is based on the first configuration and the second configuration including matching identifiers, which indicates that the user device is allowed to determine the second TA using the first TA.

[0061] In an embodiment of the third aspect, the first configuration is for conditional LTM or for non-conditional LTM.

[0062] In an embodiment of the third aspect, the instructions, when executed by the at least one processor 202, cause the user device to: measure downlink reference signals from the at least one LTM candidate cell and the at least one CHO candidate cell to obtain the radio measurements; determine a timing difference based on the measured reference signals; and compute the second TA using the timing difference.

[0063] In an embodiment of the third aspect, the first TA and the second TA have different values.

[0064] In an embodiment of the third aspect, the instructions, when executed by the at least one processor 202, cause the user device to: detect, based on the first configuration and the second configuration, that one or more execution conditions for the CHO are met before at least one execution conditions for the LTM is not met; and determine to execute a handover to the at least one CHO candidate cell without a random-access procedure using the second TA.

[0065] In an embodiment of the third aspect, the instructions, when executed by the at least one processor 202, cause the user device to: transmit, to the serving network node prior to the execution of the handover, an indication of a beam towards the at least one CHO candidate cell; and monitor for a transmission from the at least one CHO candidate cell via the indicated beam.

[0066] In an embodiment of the third aspect, the first configuration is for one of: intracentralized unit, intra-CU LTM, intra-CU C-LTM, inter-CU LTM or inter-CU C-LTM; and the second configuration is for inter-CU CHO.

[0067] In an embodiment of the third aspect, the first TA for the at least one LTM candidate cell is acquired via an early synchronization procedure.

[0068] According to a fourth aspect, the apparatus 200 comprises a network device. The network device may comprise the at least one processor 202; and the at least one memory 204 storing instructions which, when executed by the at least one processor 202, cause the network device at least to: transmit, to a user device, a first configuration for a lower-layer triggered mobility, LTM, and a second configuration for a conditional handover, CHO; detect that at least one LTM candidate cell associated with the first configuration is in time synchronization with at least one CHO candidate cell associated with the second configuration; and transmit, to the user device, information indicative that the at least one LTM candidate cell is in time synchronization with the at least one CHO candidate cell.

[0069] In an embodiment of the fourth aspect, the information indicative that the at least one LTM candidate cell is in time synchronization with the at least one CHO candidate cell is included in at least one of the first configuration or the second configuration.

[0070] In an embodiment of the fourth aspect, the instructions, when executed by the at least one processor 202, cause the network device to: include, based on the detected time synchronization, matching identifiers to the first configuration and the second configuration, wherein the matching identifiers are indicative that the user device is allowed to determine a timing advance for the at least one CHO candidate using a timing advance obtained for the at least one LTM candidate cell.

[0071] The functionality described herein may be performed, at least in part, by one or more computer program product components such as software components. According to an example embodiment, the apparatus 200 comprises a processor or processor circuitry, such as for example a microcontroller, configured by the program code 206, when executed, to execute the embodiments of the operations and functionality described herein. Program code 206 is provided as an example of instructions which, when executed by the at least one processor 202, cause performance of the apparatus 200.

[0072] Alternatively, or in addition, the functionality described herein can be performed, at least in part, by one or more hardware logic components. For example, and without limitation, illustrative types of hardware logic components that can be used include field-programmablegate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), system-on-a-chip systems (SOCs), complex programmable logic devices (CPLDs), graphics processing units (GPUs), or the like.

[0073] The apparatus 200 may be configured to perform, or cause performance of, method(s) described herein or comprise means for performing method(s) described herein. In one example, the means comprises the at least one processor 202, the at least one memory 204 including instructions (e.g., program code 206) configured to, when executed by the at least one processor 202, cause the apparatus 200 to perform the method(s). In general, computer program instructions may be executed on means providing generic processing functions. Such means may be embedded for example in a personal computer, a smart phone, a network device, or the like. The method(s) may be thus computer-implemented, for example, based on algorithm(s) executable by the generic processing functions, an example of which is the at least one processor 202. The means may comprise transmission or reception means, for example one or more radio transmitters or receivers, which may be coupled or be configured to be coupled to one or more antennas. Although apparatus 200 is illustrated as a single device, it is appreciated that, wherever applicable, functions of apparatus 200 may be distributed to a plurality of devices.

[0074] FIG. 3 illustrates an example of signalling and operations for determining a timing advance value for a CHO candidate cell by using a timing advance value for an LTM candidate cell. The signalling is performed between a user device, such as UE 102, a first gNB, such as gNB 104 and a second gNB such as gNB 106. The first gNB may comprise a source DU (e.g., gNB-DU 300), at least one target DU (e.g., target DU-1 302) and a source CU (e.g., gNB-CU-1 304). The second gNB may comprise a CU (e.g., gNB-CU-2306) and at least one target DU (e.g., target DU-2308).

[0075] At operation 310, the UE 102 is connected to the serving cell in source gNB-DU 300. The UE 102 may be configured, for example, with intra-CU C-LTM and inter-CU CHO. However, the procedure illustrated herein is also applicable in other scenarios, such as intra-CU LTM and inter-CU CHO, inter-CU LTM and inter-CU CHO, as well as inter-CU C-LTM and inter-CU CHO. In addition, the UE 102 is configured with the UE based TA estimation capability.

[0076] At operation 312, the UE 102 transmits a measurement report to the source gNB-DU 300. The measurement report may comprise, for example, L3 measurements performed by the UE 102. The source gNB-DU 300 then transmits the measurement report to source gNB-CU-1 304. The measurement report may be forwarded by the gNB-DU 300 to the gNB-CU-1 304 via UL RRC message transfer.

[0077] At operation 314, the gNB-CU-1 304 analyses the measurement report. Based on the analysis, the gNB-CU-1 304 may determine to trigger simultaneous preparation of C-LTM for a first candidate cell (e.g., target DU-1 302 in gNB-CU-1 304) and CHO for a second candidate cell (e.g., target DU-2308 in gNB-CU-2306). The first candidate cell may be also referred to as a C-LTM candidate cell. The second candidate cell may be referred to as a CHO candidate cell. It is further noted that more than one LTM and / or CHO candidate cell may be simultaneously prepared for a handover.

[0078] At operation 316, the gNB-CU-1 304 may transmit a request for UE context setup to the target DU-1 302 with the first candidate cell. The purpose of the UE context setup procedure is to establish the UE context including, among others, SRB (signaling radio bearer), and DRB (data radio bearer) configuration. At operation 318, the target DU-1 302 may transmit to the gNB-CU-1 304 a UE context response with report configurations for C-LTM.

[0079] At operation 320, the gNB-CU-1 304 transmits a conditional handover request to the target gNB-CU-2306. The CHO request may be transmitted via Xn interface. The CHO request is transmitted with the currently prepared C-LTM configuration, thereby informing the target gNB-CU-2306 about C-LTM candidate cell ID(s). For example, the CHO request may comprise a source RRC container including the C-LTM configuration.

[0080] At operation 322, a request for UE context setup is transmitted by the gNB-CU-2306 to the target DU-2308 with the second candidate cell. At operation 324, the target DU-2308 transmits a UE context setup response to the gNB-CU-2306 with CHO report configurations. The CHO report configurations comprise CHO candidate cell ID(s).

[0081] At operation 326, the target gNB-CU-2306 may determine if one or more criteria for RACH-less CHO is met based on handover configurations of the UE 102. For example, the gNB-CU-2- 306 may first compare the candidate cell IDs obtained at operation 320 and operation 324 to check whether the candidate cells for C-LTM and CHO are in time synchronization. If the first candidate cell associated with the target DU-1 302 and the second candidate cell associated with the target DU-2308 are determined to be in time synchronization by the target gNB-CU-2306, and if the UE 102 is configured with the capability to execute UE based TA computation, the gNB-CU-2306 may decide to initiate the RACH-less CHO for possible future execution of a handover to the second candidate cell.

[0082] At operation 328, the target gNB-CU-2 306 transmits a CHO request acknowledgement to the source gNB-CU-1 304. The CHO request acknowledgement may comprise an indicator for a RACH-less CHO. For example, the target gNB-CU-2 306 may include at least one of a UE based TA estimation indicator or a dedicated RACH-less CHO indicator in the CHO request acknowledgement. The indicator may be provided, for example, as a Boolean flag. For example, when the indicator indicates 1 or true, the gNB-CU-1 304 is informed that a RACH-less CHO can be performed to the second candidate cell. As another example, when the indicator indicates 0 or false, the gNB-CU-1 304 is informed that a RACH-less CHO cannot be performed to the second candidate cell. In one example, when the indicator indicates 1 or true, the indicator indicates that the first candidate cell and the second candidate cell are in time synchronization, and when the indicator indicates 0 or false, the indicator indicates that the first candidate cell and the second candidate cell are not in time synchronization, or vice versa. When the indicator indicates that RACH-less CHO can be performed and / or that the first and the second candidate cells are in time synchronization, the indicator may function as a trigger for the gNB-CU-1 304 to further indicate to the UE 102 that the RACH-less CHO is allowed and / or that UE based TA estimation can be performed by the UE 102 based on the time synchronization.

[0083] In one embodiment, the gNB-CU-1 304 may be configured to check whether the candidate cells are in time synchronization. For example, the gNB-CU-1 304 may obtain the CHO candidate cell ID(s) from the gNB-CU-2306, perform the comparison, and then inform the gNB-CU-2306 about the time synchronization between the LTM and CHO candidate cells. Based on the received information, the gNB-CU-2306 may then determine to initiate the RACH-less CHO.

[0084] At operation 330, the gNB-CU-1 304 transmits the configuration of the prepared cells (e.g., the first and second candidate cell) to source gNB-DU 300. The configuration of prepared cells can be transmitted to the source gNB-DU 300 in a DL RRC message transfer via RRC reconfiguration. The transmitted message may include intra-CU conditional LTM report configuration with execution condition(s) for the first candidate cell and beams, and an early synchronization indicator. The early synchronization indicator instructs the UE 102 to execute early TA acquisition to C-LTM candidate cell (the first candidate cell) at a later step, before executing C-LTM cell switch. Inter-CU RACH-less CHO report configuration contains a corresponding execution condition for the second candidate cell. The inter-CU RACH-lessCHO report configuration may further comprise an indication for using the UE based TA estimation.

[0085] At operation 332, the source gNB-DU 300 transmits RRC reconfiguration message to UE 102. The message comprises the configurations received at operation 330, with information indicative to use the early synchronization for C-LTM and RACH-less CHO. In case the indicator for RACH-less CHO was activated at operation 328, the second candidate cell for CHO will have UE based TA ID which is the same as for the first candidate cell for C-LTM. The UE based TA IDs (e.g., UE-MeasuredTA-ID) may be set by the gNB-CU-1 304 to be the same for the first candidate cell and the second candidate cell based on the activated indicator for RACH-less CHO. Hence, the UE 102 may use TA measurement of the first candidate cell to obtain TA value of the second candidate cell without executing detailed RACH procedure.

[0086] At operation 334, a RRC reconfiguration complete message is transmitted by the UE 102 to the gNB-DU 300. Thereafter, at operation 336, an UL RRC message transfer containing the RRC reconfiguration complete message is sent by the gNB-DU 300 to the gNB-CU-1 304.

[0087] At operation 338, the UE 102 may transmit periodic radio measurement reports (e.g., LI measurements) to the gNB-DU 300 for tracking and sharing radio conditions of the serving and target cells, that is, the first candidate cell and the second candidate cell.

[0088] The gNB-DU 300 may then trigger, based on the received measurement reports, the early synchronization procedure 340. For the prepared first candidate cell corresponding to C-LTM, the gNB-DU 300 may transmit to the UE 102, at operation 342, a PDCCH order to initiate PRACH (physical RACH). The PDCCH order may consist of RACH preambles and other parameters related to PRACH.

[0089] At operation 344, the UE 102 conducts RACH with the first candidate cell in target DU-1 304. At operation 346, TA information is shared by the DU-1 304 with source gNB-DU 300 via gNB-CU-1 306. At operation 348, the source gNB-DU 300 transmits early TA acquisition information to the UE 102. The early TA acquisition information may comprise the TA information (e.g., TA value) and TA maintenance timer for the first candidate cell in target DU-1 304. Once the TA maintenance timer expires, the UE 102 may conclude that the TA value is no longer valid.

[0090] The UE 102 may be configured to check the UE-MeasuredTA-ID of CHO and C-LTM candidate cells obtained at operation 332. In case the UE-MeasuredTA-ID is found to be the same for the first candidate cell and the second candidate cell, the UE 102 executes, at operation 350, UE based TA estimation for the second candidate cell (CHO).

[0091] In general, the execution of the UE based TA estimation for the second candidate cell may be triggered based on any information indicative that LTM candidate cell(s) and CHO candidate cell(s) are in time synchronization. The information indicative of the time synchronization may be, for example, the matching identifiers for UE based TA estimation, indication of the initiated RACH-less CHO, or some dedicated indicator included in the message received by the UE 102 at operation 332 or in a separate message.

[0092] The UE based TA estimation may be performed by the UE 102 based on binder TA measurement of the first candidate cell (C-LTM), received at operation 348, and DL timing difference. The UE 102 may obtain the DL timing difference based on measurement of reference signals from the first candidate cell and the second candidate cell. The UE 102 may compute the TA value for the second candidate cell, for example, by adding the DL timing difference multiplied by two to the TA value of the second candidate cell.

[0093] The procedure of FIG. 3 enables that the TA value of a CHO candidate cell can be obtained using already obtained TA value of an LTM candidate cell by a UE with the UE based TA estimation capability. Hence, detailed RACH before CHO execution can be avoided. Further, the TA value obtained for the LTM will not be wasted in case CHO cell switch is triggered before LTM or C-LTM, and execution of a handover to the CHO candidate cell is facilitated without a need to perform RACH procedure.

[0094] FIG. 4 illustrates an example of signalling and operations for execution of a RACH-less CHO using UE based timing advance acquisition. FIG. 4 depicts the procedure of FIG. 3 continued with the execution of RACH-less CHO, and therefore, description of the operations 310 to 348 is not repeated herein. Further, operations 312 to 328 are not shown in FIG. 4, although said operations may be part of the procedure.

[0095] After acquisition of the TA value for first candidate cell via the early synchronization procedure 340, the UE 102 may continue to evaluate conditions for C-LTM and CHO. The UE 102 may detect that the second candidate cell in target DU-2308 satisfies the CHO cell switch execution condition before the execution condition for C-LTM is satisfied.

[0096] However, for the CHO, early TA is not available and early preparation of C-LTM also becomes unusable. Therefore, the UE 102 is configured to obtain the TA value for the second candidate cell using the obtained TA value of the first candidate cell and the DL timing difference, at operation 350.

[0097] In one embodiment, the UE 102 may be configured to compute the TA value for the second candidate cell based on detection of one or more criteria for the RACH-less CHO beingmet. The one or more criteria may comprise, for example, time synchronization of the first candidate cell and the second candidate cell, an indication for RACH-less CHO received in the configuration of prepared cells at operation 332, and / or detection of one or more CHO execution conditions being met before at least one execution condition for C-LTM (or LTM) is met.

[0098] At operation 400, the UE 102 may send a beam indicator message to the source gNB-DU 300. The beam indicator message may comprise early L3 measurement results corresponding to the second candidate cell. The measurement results may highlight an optimal beam (e.g., SSB beam index) for the second candidate cell. The beam indicator message may be transmitted via a MAC CE message. The beam indicator message is then relayed to the second candidate cell, e.g., via the gNB-CU-1 304, gNB-CU-2306 and target-DU-2308 at operations 402, 404 and 406, respectively. The beam indicator message may be relayed between the CU entities via Xn interface (at operation 404) and between CU and DU entities via Fl interface (at operations 402 and 406).

[0099] At operation 408, the UE 102 attempts to execute cell switch with RACH-less CHO to the second candidate cell and starts PDCCH monitoring.

[0100] At operation 410, the second candidate cell may trigger configured grant to the UE 102 via the optimal beam informed to the second candidate cell at operation 352. The UE 102 may then receive, at operation 412, a first PDCCH transmitted by the target DU-2308 in DL via the optimal beam reported by the UE 102.

[0101] At operation 414, the inter-CU RACH-less CHO to the second candidate cell in target DU-2308 in target CU-2306 is executed. The RACH-less CHO may be executed seamlessly by the UE 102 using the UE based TA value obtained at operation 350. Hence, the UE is able to take benefit of the already acquired TA value for LTM purposes and thereby avoiding the detailed RACH procedure for CHO.

[0102] In case inter- or intra-CU LTM and inter-CU CHO are prepared for the UE at operation 314, the serving cell and the candidate cells for CHO and LTM are assumed to have the same UE based TA ID. Using the UE based TA ID, whenever the preparation of LTM is commenced, the UE 102 may be configured to compute the TA value towards the LTM candidate cell and save the TA value for future use. However, based on radio conditions, the CHO execution condition may get satisfied. At such situation, the UE 102 also computes the UE based TA value for CHO candidate cell using the TA value of the LTM candidate cell, asdescribed herein. Therefore, the UE can execute cell switch to the CHO candidate cell by avoiding RACH-based TA estimation in different handover scenarios.

[0103] FIG. 5 illustrates an example of a method 500 for RACH-less CHO execution, according to an example embodiment. Method 500 may be performed by a user device, e.g., UE 102, or by a control apparatus configured to control the functioning thereof, when installed therein.

[0104] At operation 502, the method may comprise receiving, by the user device from a serving network node, a first configuration for a lower-layer triggered mobility, LTM, and a second configuration for a conditional handover, CHO.

[0105] At operation 504, the method may comprise acquiring, by the user device, using the first configuration, a first timing advance, TA, for at least one LTM candidate cell.

[0106] At operation 506, the method may comprise determining, by the user device, that one or more criteria for a handover without a random-access procedure are met for at least one CHO candidate cell.

[0107] At operation 508, the method may comprise, upon determining that the one or more criteria are met, determining, by the user device, a second TA for the at least one CHO candidate cell based on: the first TA for the at least one LTM candidate cell; and obtained radio measurements between the at least one LTM candidate cell and the at least one CHO candidate cell.

[0108] At operation 510, the method may comprise executing, by the user device using the second configuration and the second TA, the handover to the at least one CHO candidate cell without the random-access procedure.

[0109] In an embodiment of the method 500, the first configuration is for conditional LTM, C-LTM, or for non-conditional LTM.

[0110] In an embodiment of the method 500, the one or more criteria comprise at least one of the following: the at least one LTM candidate cell is in time synchronization with the at least one CHO candidate cell; at least one of the first configuration or the second configuration comprises an indication that the user device is allowed to use the first TA for the at last one LTM candidate cell to determine the second TA for the at least one CHO candidate cell; one or more execution conditions for CHO are met before at least one execution condition for LTM is met.[OHl] In an embodiment of the method 500, the method further comprises receiving, by the user device from the serving network node, information on that the at least one LTM candidatecell is in time synchronization with the at least one CHO candidate cell; and determining, by the user device, that the at least one LTM candidate cell is in time synchronization with the at least one CHO candidate cell based on the received information.

[0112] In an embodiment of the method 500, the information on that the at least one LTM candidate cell is in time synchronization with the at least one CHO candidate cell is based on the first configuration and the second configuration including matching identifiers.

[0113] In an embodiment of the method 500, the method comprises detecting, by the user device, based on the first configuration and the second configuration, that one or more execution conditions for CHO are met before at least one execution condition for LTM is met; and determining, by the user device responsive to the detection, to execute the handover to the at least one CHO candidate cell without the random-access procedure.

[0114] In an embodiment of the method 500, the first TA and the second TA have different values.

[0115] In an embodiment of the method 500, the method comprises transmitting, by the user device to the serving network node prior to the execution of the handover, an indication of a beam towards the at least one CHO candidate cell; and monitoring, by the user device, for a transmission from the at least one CHO candidate cell via the indicated beam.

[0116] In an embodiment of the method 500, the method comprises performing, by the user device, layer 3 measurements corresponding to the at least one CHO candidate cell; and wherein the indication of the beam is based on the layer 3 measurement results.

[0117] In an embodiment of the method 500, the first configuration is for one of intracentralized unit, intra-CU LTM, intra-CU C-LTM, inter-CU LTM or inter-CU C-LTM; and the second configuration is for inter-CU CHO.

[0118] In an embodiment of the method 500, the first TA is acquired using an early synchronization procedure.

[0119] In an embodiment of the method 500, the method comprises measuring, by the user device, downlink reference signals from the at least one LTM candidate cell and the at least one CHO candidate cell to obtain the radio measurements; determining, by the user device, a timing difference based on the measured reference signals; and computing, by the user device, the second TA using the timing difference.

[0120] FIG. 6 illustrates an example of a method 600 for assisting in RACH-less CHO execution, according to an example embodiment. Method 600 may be performed by a networkdevice, e.g., access node 104 or 106, or by a control apparatus configured to control the functioning thereof, when installed therein.

[0121] At operation 602, the method may comprise detecting, by the network device, that least one lower-layer triggered mobility, LTM, candidate cell and at least one conditional handover, CHO, candidate cell are in time synchronization

[0122] At operation 604, the method may comprise transmitting, by the network device to a user device based on the detected time synchronization, a first configuration for LTM and a second configuration for CHO, wherein at least one of the first configuration or the second configuration comprises information indicative that at least one criteria for a handover without a random-access procedure is met for the at least one CHO candidate cell.

[0123] FIG. 7 illustrates an example of a method 700 for determining a timing advance value for a CHO candidate cell, according to an example embodiment. Method 700 may be performed by a user device, e.g., UE 102, or by a control apparatus configured to control the functioning thereof, when installed therein.

[0124] At operation 702, the method may comprise receiving, by the user device from a serving network node, a first configuration for a lower-layer triggered mobility, LTM, and a second configuration for a conditional handover, CHO.

[0125] At operation 704, the method may comprise receiving, by the user device from the serving network node, information indicative of a time synchronization between at least one LTM candidate cell associated with the first configuration and at least one CHO candidate cell associated with the second configuration.

[0126] At operation 706, the method may comprise acquiring, by the user device from the serving network node, a first timing advance, TA, for the at least one LTM candidate cell.

[0127] At operation 708, the method may comprise determining, by the user device based on the information indicative of the time synchronization, a second TA for the at least one CHO candidate cell, wherein the second TA is determined using the first TA and radio measurements obtained from the at least one CHO candidate cell and the at least one LTM candidate cell.

[0128] In an embodiment of the method 700, he information indicative of the time synchronization is comprised in at least one of the first configuration or the second configuration.

[0129] In an embodiment of the method 700, the information indicative of the time synchronization between the at least one LTM candidate cell and the at least one CHO candidate cell is based on the first configuration and the second configuration includingmatching identifiers, which indicates that the user device is allowed to determine the second TA using the first TA.

[0130] In an embodiment of the method 700, the first configuration is for conditional LTM, or for non-conditional LTM.

[0131] In an embodiment of the method 700, the method comprises measuring, by the user device, downlink reference signals from the at least one LTM candidate cell and the at least one CHO candidate cell to obtain the radio measurements; determining, by the user device, a timing difference based on the measured reference signals; and computing, by the user device, the second TA using the timing difference.

[0132] In an embodiment of the method 700, the first TA and the second TA have different values.

[0133] In an embodiment of the method 700, the method further comprises detecting, by the user device based on the first configuration and the second configuration, that one or more execution conditions for the CHO are met before at least one execution conditions for the LTM is not met; and determining, by the user device, to execute a handover to the at least one CHO candidate cell without a random-access procedure using the second TA.

[0134] In an embodiment of the method 700, the method comprises transmitting, by the user device to the serving network node prior to the execution of the handover, an indication of a beam towards the at least one CHO candidate cell; and monitoring, by the user device, for a transmission from the at least one CHO candidate cell via the indicated beam.

[0135] In an embodiment of the method 700, the first configuration is for one of intracentralized unit, intra-CU LTM, intra-CU C-LTM, inter-CU LTM or inter-CU C-LTM; and the second configuration is for inter-CU CHO.

[0136] In an embodiment of the method 700, the first TA for the at least one LTM candidate cell is acquired via an early synchronization procedure.

[0137] FIG. 8 illustrates an example of a method 800 for assisting in determining a timing advance value for a CHO candidate cell, according to an example embodiment. Method 800 may be performed by a network device, e.g., access node 104 or 106, or by a control apparatus configured to control the functioning thereof, when installed therein.

[0138] At operation 802, the method may comprise transmitting, by the network device to a user device, a first configuration for a lower-layer triggered mobility, LTM, and a second configuration for a conditional handover, CHO.

[0139] At operation 804, the method may comprise detecting, by the network device, that at least one LTM candidate cell associated with the first configuration is in time synchronization with at least one CHO candidate cell associated with the second configuration.

[0140] At operation 806, the method may comprise transmitting, by the network device to the user device, information indicative that the at least one LTM candidate cell is in time synchronization with the at least one CHO candidate cell.

[0141] In an embodiment of the method 800, the information indicative that the at least one LTM candidate cell is in time synchronization with the at least one CHO candidate cell is included in at least one of the first configuration or the second configuration.

[0142] In an embodiment of the method 800, the method further comprises including, by the network device based on the detected time synchronization, matching identifiers to the first configuration and the second configuration, wherein the matching identifiers are indicative that the user device is allowed to determine a timing advance for the at least one CHO candidate using a timing advance obtained for the at least one LTM candidate cell.

[0143] Further features of the methods directly result for example from functionality of UE 102, or access node(s) 104, 106, as described throughout the description, claims, and drawings, and are therefore not repeated here. An apparatus, for example a device such as UE 102, or an access node, may be configured to perform or cause performance of any aspect of the method(s) described herein. Further, a computer program, a computer program product, or a (non-transitory) computer-readable medium may comprise instructions for causing, when executed by an apparatus, the apparatus to perform any aspect of the method(s) described herein. Further, an apparatus may comprise means for performing any aspect of the method(s) described herein. According to an example embodiment, the means comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform any aspect of the method(s).

[0144] Any range or device value given herein may be extended or altered without losing the effect sought. Also, any embodiment may be combined with another embodiment unless explicitly disallowed.

[0145] Although the subject matter has been described in language specific to structural features and / or acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as examples of implementing the claims and other equivalent features and acts are intended to be within the scope of the claims.

[0146] It will be understood that the benefits and advantages described above may relate to one embodiment or may relate to several embodiments. The embodiments are not limited to those that solve any or all of the stated problems or those that have any or all of the stated benefits and advantages. It will further be understood that reference to 'an' item may refer to one or more of those items.

[0147] The steps or operations of the methods described herein may be carried out in any suitable order, or simultaneously where appropriate. Additionally, individual blocks may be deleted from any of the methods without departing from the scope of the subject matter described herein. Aspects of any of the example embodiments described above may be combined with aspects of any of the other example embodiments described to form further example embodiments without losing the effect sought.

[0148] The term 'comprising' is used herein to mean including the method, blocks, or elements identified, but that such blocks or elements do not comprise an exclusive list and a method or apparatus may contain additional blocks or elements.

[0149] As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two or more elements are joined by “and” or “or”, mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.

[0150] Although subjects may be referred to as ‘first’ or ‘second’ subjects, this does not necessarily indicate any order or importance of the subjects. Instead, such attributes may be used solely for the purpose of making a difference between subjects.

[0151] As used in this application, the term ‘circuitry’ may refer to one or more or all of the following: (a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry) and (b) combinations of hardware circuits and software, such as (as applicable) :(i) a combination of analog and / or digital hardware circuit(s) with software / firmware and (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and (c) hardware circuit(s) and or processor(s), such as a microprocessor s) or a portion of a microprocessor s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation. This definition of circuitry applies to all uses of this term in this application, including in any claims.

[0152] As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

[0153] It will be understood that the above description is given by way of example only and that various modifications may be made by those skilled in the art. The above specification, examples and data provide a complete description of the structure and use of exemplary embodiments. Although various embodiments have been described above with a certain degree of particularity, or with reference to one or more individual embodiments, those skilled in the art could make numerous alterations to the disclosed embodiments without departing from scope of this specification.

Claims

28CLAIMS1. A user device, comprising:at least one processor;and at least one memory storing instructions that, when executed by the at least one processor, cause the user device at least to:receive, from a serving network node, a first configuration for a lower-layer triggered mobility, LTM, and a second configuration for a conditional handover, CHO;receive, from the serving network node, information indicative of a time synchronization between at least one LTM candidate cell associated with the first configuration and at least one CHO candidate cell associated with the second configuration;acquire, from the serving network node, a first timing advance, TA, for the at least one LTM candidate cell; anddetermine, based on the information indicative of the time synchronization, a second TA for the at least one CHO candidate cell, wherein the second TA is determined using the first TA and radio measurements obtained from the at least one CHO candidate cell and the at least one LTM candidate cell.

2. The user device of claim 1, wherein the information indicative of the time synchronization is comprised in at least one of the first configuration or the second configuration.

3. The user device of claim 2, wherein the information indicative of the time synchronization between the at least one LTM candidate cell and the at least one CHO candidate cell is based on the first configuration and the second configuration including matching identifiers, which indicates that the user device is allowed to determine the second TA using the first TA.

4. The user device of any preceding claim, wherein the first configuration is for conditional LTM or for non-conditional LTM.

5. The user device of any preceding claim, wherein the instructions, when executed by the at least one processor, cause the user device to:measure downlink reference signals from the at least one LTM candidate cell and the at least one CHO candidate cell to obtain the radio measurements;determine a timing difference based on the measured reference signals; and compute the second TA using the timing difference.

6. The user device of any preceding claim, wherein the first TA and the second TA have different values.

7. The user device of any preceding claims, wherein the instructions, when executed by the at least one processor, cause the user device to:detect, based on the first configuration and the second configuration, that one or more execution conditions for the CHO are met before at least one execution conditions for the LTM is not met; anddetermine to execute a handover to the at least one CHO candidate cell without a random-access procedure using the second TA.

8. The user device of claim 7, wherein the instructions, when executed by the at least one processor, cause the user device to:transmit, to the serving network node prior to the execution of the handover, an indication of a beam towards the at least one CHO candidate cell; andmonitor for a transmission from the at least one CHO candidate cell via the indicated beam.

9. The user device of any preceding claim, wherein the first configuration is for one of: intra-centralized unit, intra-CU LTM, intra-CU C-LTM, inter-CU LTM or inter-CU C-LTM; and the second configuration is for inter-CU CHO.

10. The user device of any preceding claim, wherein the first TA for the at least one LTM candidate cell is acquired via an early synchronization procedure.

11. A network device, comprising:at least one processor; andat least one memory including instructions that, when executed by the at least one processor, cause the network device to:transmit, to a user device, a first configuration for a lower-layer triggered mobility, LTM, and a second configuration for a conditional handover, CHO;detect that at least one LTM candidate cell associated with the first configuration is in time synchronization with at least one CHO candidate cell associated with the second configuration; andtransmit, to the user device, information indicative that the at least one LTM candidate cell is in time synchronization with the at least one CHO candidate cell.

12. The network device of claim 11, wherein the information indicative that the at least one LTM candidate cell is in time synchronization with the at least one CHO candidate cell is included in at least one of the first configuration or the second configuration.

13. The network device of claim 12, wherein the instructions, when executed by the at least one processor, cause the network device to:include, based on the detected time synchronization, matching identifiers to the first configuration and the second configuration, wherein the matching identifiers are indicative that the user device is allowed to determine a timing advance for the at least one CHO candidate using a timing advance obtained for the at least one LTM candidate cell.

14. A method, comprising:receiving, by a user device from a serving network node, a first configuration for a lower-layer triggered mobility, LTM, and a second configuration for a conditional handover, CHO;receiving, by the user device from the serving network node, information indicative of a time synchronization between at least one LTM candidate cell associated with the first configuration and at least one CHO candidate cell associated with the second configuration;acquiring, by the user device from the serving network node via an early synchronization procedure, a first timing advance, TA, for the at least one LTM candidate cell; anddetermining, by the user device based on the information indicative of the time synchronization, a second TA for the at least one CHO candidate cell, wherein the second TAis determined using the first TA and radio measurements obtained from the at least one CHO candidate cell and the at least one LTM candidate cell.

15. A method, comprising:transmitting, by a network device to a user device, a first configuration for a lower-layer triggered mobility, LTM, and a second configuration for a conditional handover, CHO;detecting, by the network device, that at least one LTM candidate cell associated with the first configuration is in time synchronization with at least one CHO candidate cell associated with the second configuration; andtransmitting, by the network device to the user device, information indicative that the at least one LTM candidate cell is in time synchronization with the at least one CHO candidate cell.