Method and apparatus for layer1 / layer2 triggered mobility (LTM) operation

The CLTM method in wireless communication systems addresses latency and overhead issues in LTM operations by using a RACH-less handover process with TA command-based cell switching, improving mobility efficiency.

WO2026235029A1PCT designated stage Publication Date: 2026-11-12SHARP KK
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2026/016589
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-05
Filing Date
2026-04-24
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Existing wireless communication systems, particularly 5G NR, face challenges in improving Layer 1/Layer 2 Triggered Mobility (LTM) operations, leading to increased latency and signaling overhead during handover processes.

Method used

Implementing a UE and BS method for Conditional Layer 1/Layer 2 Triggered Mobility (CLTM) that includes receiving a Timing Advance (TA) command via a MAC Control Element, performing a RACH-less cell switch, and determining an actual TA value based on subcarrier spacing, allowing for efficient handover without random access procedures.

Benefits of technology

Reduces handover latency and signaling overhead by enabling RACH-less cell switching, enhancing mobility management in wireless networks.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2026016589_12112026_PF_FP_ABST
    Figure JP2026016589_12112026_PF_FP_ABST
Patent Text Reader

Abstract

A method performed by a User Equipment (UE) for performing a conditional Layer 1 / Layer 2 Triggered Mobility (CLTM) operation is provided. The method receives, from a serving cell, a Medium Access Control (MAC) Control Element (CE) including a Timing Advance (TA) command indicating a TA index for a CLTM candidate cell. The method stores the TA index for the CLTM candidate cell in response to receiving the MAC CE. The method performs a Random Access Channel (RACH)-less CLTM cell switch to the CLTM candidate cell. The method determines an actual TA value applied in the CLTM candidate cell based on the TA index and a subcarrier spacing (SCS) of an uplink transmission that occurs first in time after performing the RACH-less CLTM cell switch.
Need to check novelty before this filing date? Find Prior Art

Description

METHOD AND APPARATUS FOR LAYER1 / LAYER2 TRIGGERED MOBILITY (LTM) OPERATION

[0001] The present disclosure is related to wireless communication and, more specifically, to a User Equipment (UE), Base Station (BS), and method for a Layer 1 / Layer 2 Triggered Mobility (LTM) operation in the wireless communication networks.

[0002] Various efforts have been made to improve different aspects of wireless communication for the cellular wireless communication systems, such as the 5thGeneration (5G) New Radio (NR), by improving data rate, latency, reliability, and mobility. The 5G NR system is designed to provide flexibility and configurability to optimize network services and types, accommodating various use cases, such as enhanced Mobile Broadband (eMBB), massive Machine-Type Communication (mMTC), and Ultra-Reliable and Low-Latency Communication (URLLC). As the demand for radio access continues to grow, however, there exists a need for further improvements in the next-generation wireless communication systems, such as improvements in the LTM operation.

[0003] The present disclosure is related to a UE, a BS, and a method for a conditional Layer 1 / Layer 2 Triggered Mobility (CLTM) operation in the wireless communication networks.

[0004] In a first aspect of the present disclosure, a UE for performing a CLTM operation is provided. The UE includes at least one processor and at least one non-transitory computer-readable medium that is coupled to the at least one processor and that stores one or more computer-executable instructions. The one or more computer-executable instructions, when executed by the at least one processor, cause the UE to: receive, from a serving cell, a Medium Access Control (MAC) Control Element (CE) including a Timing Advance (TA) command indicating a TA index for a CLTM candidate cell; store the TA index for the CLTM candidate cell in response to receiving the MAC CE; perform a Random Access Channel (RACH)-less CLTM cell switch to the CLTM candidate cell; and determine an actual TA value applied in the CLTM candidate cell based on the TA index and a subcarrier spacing (SCS) of an uplink transmission that occurs first in time after performing the RACH-less CLTM cell switch.

[0005] In some implementations of the first aspect, the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to start or restart a first Time Alignment Timer (TAT) that is associated with the CLTM candidate cell in response to receiving the MAC CE, and consider the TA index for the CLTM candidate cell as valid until the first TAT expires.

[0006] In some implementations of the first aspect, the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to start or restart a second TAT in response to performing the RACH-less CLTM cell switch while the first TAT is running. The second TAT is associated with a Primary Timing Advance Group (PTAG) of the CLTM candidate cell. The second TAT is set to a duration equal to a remaining time of the first TAT when the RACH-less CLTM cell switch is performed.

[0007] In some implementations of the first aspect, the MAC CE further includes a Timing Advance Group (TAG) indication field that indicates one of multiple TAGs configured for the CLTM candidate cell, to which the TA command is applied.

[0008] In some implementations of the first aspect, the MAC CE further includes a candidate configuration Identifier (ID) field that indicates a CLTM candidate configuration corresponding to the CLTM candidate cell.

[0009] In some implementations of the first aspect, the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to receive, from the serving cell, a Radio Resource Control (RRC) parameter indicating a TA offset. The actual TA value applied in the CLTM candidate cell is further determined based on the TA offset.

[0010] In a second aspect of the present application, a BS for configuring a CLTM operation is provided. The BS includes at least one processor and at least one non-transitory computer-readable medium that is coupled to the at least one processor and that stores one or more computer-executable instructions. The one or more computer-executable instructions, when executed by the at least one processor, cause the BS to transmit, to a UE, a MAC CE including a TA command indicating a TA index for a CLTM candidate cell. The UE stores the TA index for the CLTM candidate cell in response to receiving the MAC CE. The UE performs a RACH-less CLTM cell switch to the CLTM candidate cell. The UE determines an actual TA value applied in the CLTM candidate cell based on the TA index and an SCS of an uplink transmission that occurs first in time after performing the RACH-less CLTM cell switch.

[0011] In some implementations of the second aspect, the UE starts or restarts a first TAT that is associated with the CLTM candidate cell in response to receiving the MAC CE, and the UE considers the TA index for the CLTM candidate cell as valid until the first TAT expires.

[0012] In some implementations of the second aspect, the UE starts or restarts a second TAT in response to performing the RACH-less CLTM cell switch while the first TAT is running. The second TAT is associated with a PTAG of the CLTM candidate cell. The second TAT is set to a duration equal to a remaining time of the first TAT when the RACH-less CLTM cell switch is performed.

[0013] In some implementations of the second aspect, the MAC CE further includes a TAG indication field that indicates one of multiple TAGs configured for the CLTM candidate cell, to which the TA command is applied.

[0014] In some implementations of the second aspect, the MAC CE further includes a candidate configuration ID field that indicates a CLTM candidate configuration corresponding to the CLTM candidate cell.

[0015] In some implementations of the second aspect, the one or more computer-executable instructions, when executed by the at least one processor, further cause the BS to transmit, to the UE, an RRC parameter indicating a TA offset. The UE determines the actual TA value applied in the CLTM candidate cell further based on the TA offset.

[0016] In a third aspect of the present application, a method performed by a UE for performing a CLTM operation is provided. The method includes receiving, from a serving cell, a MAC CE including a TA command indicating a TA index for a CLTM candidate cell; storing the TA index for the CLTM candidate cell in response to receiving the MAC CE; performing a RACH-less CLTM cell switch to the CLTM candidate cell; and determining an actual TA value applied in the CLTM candidate cell based on the TA index and an SCS of an uplink transmission that occurs first in time after performing the RACH-less CLTM cell switch.

[0017] Aspects of the present disclosure are best understood from the following detailed disclosure when read with the accompanying drawings. Various features are not drawn to scale. Dimensions of various features may be arbitrarily increased or reduced for clarity of discussion.

[0018] FIG. 1 is a diagram illustrating a CLTM procedure, according to an example implementation of the present disclosure.

[0019] FIG. 2 is a diagram illustrating a CLTM preparation procedure, according to an example implementation of the present disclosure.

[0020] FIG. 3 is a flowchart illustrating a method / process performed by a UE for performing a CLTM operation, according to an example implementation of the present disclosure.

[0021] FIG. 4 is a block diagram illustrating a node for wireless communication, according to an example implementation of the present disclosure.

[0022] Some of the abbreviations used in the present disclosure include: 3GPP      3rd Generation Partnership Project 5G      5thGeneration 5GC      5G Core Network ACK      Acknowledgment AI      Artificial Intelligence AMF      Access and Mobility Management Function BWP      Bandwidth Part BS      Base Station CA      Carrier Aggregation CORESET      Control resource set CC      Component Carrier CE      Control Element CFRA      Contention-Free RA CG      Configured Grant CLTM      Conditional LTM CP      Cyclic Prefix CQI      Channel Quality Indicator CRI      CSI-RS resource indicator CSC      Cell Switch Command CSI      Channel State Information CU      Central Unit DC      Dual Connectivity DCI      Downlink Control Information DL      Downlink DU      Distributed Unit EPC      Evolved Packet Core E-UTRA      Evolved Universal Terrestrial Radio Access FR      Frequency Range HARQ      Hybrid Automatic Repeat Request ID      Identifier IE      Information Element L1 / L2 / L3      Layer 1 / Layer 2 / Layer 3 LTE      Long Term Evolution LTM      Layer1 / Layer2 Triggered Mobility MAC      Medium Access Control MCG      Master Cell Group ML      Machine Learning MN      Master Node MR-DC      Multi-RAT Dual Connectivity NACK      Negative Acknowledgment NCC      Next Hop Chaining Counter NR      New RAT / Radio NW      Network PBCH      Physical Broadcast Channel PCell      Primary Cell PCI      Physical Cell ID PDCP      Packet Data Convergence Protocol PDCCH      Physical Downlink Control Channel PDSCH      Physical Downlink Shared Channel PHY      Physical PMI      Precoding Matrix Indicator PRACH      Physical Random Access Channel PSCell      Primary SCG Cell PTAG      Primary TAG PUCCH      Physical Uplink Control Channel PUSCH      Physical Uplink Shared Channel RA      Random Access RACH      Random Access Channel RAN      Radio Access Network RAR      Random Access Response RAT      Radio Access Technology Rel      Release RLC      Radio Link Control RRC      Radio Resource Control RS      Reference Signal SCell      Secondary Cell SCG      Secondary Cell Group SCS      Subcarrier Spacing SDAP      Service Data Adaptation Protocol SI      System Information SN      Secondary Node SpCell      Special Cell SR      Scheduling Request SRS      Sounding Reference Signal SS      Synchronization Signal SSB      SS / PBCH Block TA      Timing Advance TAG      Timing Advance Group TAT      Time Alignment Timer TB      Transport Block TCI      Transmission Configuration Indication TR      Technical Report TRP       Transmission Reception Point TS      Technical Specification UCI      Uplink Control Information UE      User Equipment UL      Uplink UPF      User Plane Function URLLC      Ultra Reliable Low Latency Communication

[0023] The following contains specific information related to implementations of the present disclosure. The drawings and their accompanying detailed disclosure are merely directed to implementations. However, the present disclosure is not limited to these implementations. Other variations and implementations of the present disclosure will be obvious to those skilled in the art.

[0024] Unless noted otherwise, like or corresponding elements among the drawings may be indicated by like or corresponding reference numerals. Moreover, the drawings and illustrations in the present disclosure are generally not to scale and are not intended to correspond to actual relative dimensions.

[0025] For the purposes of consistency and ease of understanding, like features may be identified (although, in some examples, not illustrated) by the same numerals in the drawings. However, the features in different implementations may be different in other respects and may not be narrowly confined to what is illustrated in the drawings.

[0026] References to “one implementation,” “an implementation,” “example implementation,” “various implementations,” “some implementations,” “implementations of the present application,” etc., may indicate that the implementation(s) of the present application so described may include a particular feature, structure, or characteristic, but not every possible implementation of the present application necessarily includes the particular feature, structure, or characteristic. Further, repeated use of the phrase “In some implementations,” or “in an example implementation,” “an implementation,” do not necessarily refer to the same implementation, although they may. Moreover, any use of phrases like “implementations” in connection with “the present application” are never meant to characterize that all implementations of the present application must include the particular feature, structure, or characteristic, and should instead be understood to mean “at least some implementations of the present application” includes the stated particular feature, structure, or characteristic. The term “coupled” is defined as connected, whether directly or indirectly through intervening components, and is not necessarily limited to physical connections. The term “comprising,” when utilized, means “including, but not necessarily limited to”; it specifically indicates open-ended inclusion or membership in the so-described combination, group, series, and the equivalent.

[0027] The expression “at least one of A, B and C” or “at least one of the following: A, B and C” means “only A, or only B, or only C, or any combination of A, B and C.” The terms “system” and “network” may be used interchangeably. The term “and / or” is only an association relationship for describing associated objects and represents that three relationships may exist such that A and / or B may indicate that A exists alone, A and B exist at the same time, or B exists alone. The character “ / ” generally represents that the associated objects are in an “or” relationship.

[0028] For the purposes of explanation and non-limitation, specific details, such as functional entities, techniques, protocols, and standards, are set forth for providing an understanding of the disclosed technology. In other examples, detailed disclosure of well-known methods, technologies, systems, and architectures are omitted so as not to obscure the present disclosure with unnecessary details.

[0029] Persons skilled in the art will immediately recognize that any network function(s) or algorithm(s) disclosed may be implemented by hardware, software, or a combination of software and hardware. Disclosed functions may correspond to modules which may be software, hardware, firmware, or any combination thereof.

[0030] A software implementation may include computer-executable instructions and / or Artificial Intelligence (AI) / Machine Learning (ML) module(s) stored on a computer-readable medium, such as memory or other type of storage devices. One or more microprocessors or general-purpose computers with communication processing capability may be programmed with corresponding computer-executable instructions and perform the disclosed network function(s), AI / ML module(s), or algorithm(s). The AI / ML module(s) may be implemented with a supervised learning approach, a semi-supervised learning approach, an unsupervised learning approach (e.g., Transductive approach and Inductive approach), a federated learning approach, or a reinforcement learning (RL) approach, but the present disclosure is not limited thereto. The computer-executable instructions associated with the AI module(s) and / or the ML module(s) may include but are not limited to, data management instructions (e.g., collection instructions, validation instructions…etc.), model monitoring and management instructions (e.g., NW key performance indicators (KPIs) monitoring, model input / output monitoring, model selection / switching / update / upload / download, model (de)activation, model identification, functionality selection…etc.), and / or pre-process input instructions.

[0031] The microprocessors or general-purpose computers may include Application-Specific Integrated Circuits (ASICs), programmable logic arrays, Central Processing Units (CPUs), Tensor Processing Units (TPUs), Graphics Processing Units (GPUs), General-purpose computing on GPUs (GPGPU, or less often GPGP), and / or using one or more Digital Signal Processors (DSPs). Although some of the disclosed implementations are oriented to software installed and executing on computer hardware, alternative implementations implemented as firmware, as hardware, or as a combination of hardware and software are well within the scope of the present disclosure. The computer-readable medium may include, but is not limited to, Random Access Memory (RAM), Dynamic Random Access Memory (DRAM), High Bandwidth Memory (HBM), Magnetoresistive Random Access Memory (MRAM), Ferroelectric Random Access Memory (FRAM), Resistive Random Access Memory (RRAM), Read-Only Memory (ROM), Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), flash memory (or other memory technology), Compact Disc Read-Only Memory (CD-ROM) , Digital Versatile Disks (DVD) (or other optical disk storage), magnetic cassettes, magnetic tape, magnetic disk storage (or other magnetic storage devices), or any other equivalent medium capable of storing computer-readable instructions.

[0032] A radio communication network architecture such as a Long-Term Evolution (LTE) system, an LTE-Advanced (LTE-A) system, an LTE-Advanced Pro system, or a 5G NR Radio Access Network (RAN), 5G-Advanced (5G-A) system, or an open radio access network (O-RAN) may typically include at least one base station (BS), at least one UE, and one or more optional network elements that provide connection within a network. The BS and one or more optional network elements enable the UE to access a radio network. The UE may communicate with the network, such as a Core Network (CN), an Evolved Packet Core (EPC) network, an Evolved Universal Terrestrial RAN (E-UTRAN), a Next-Generation Core (NGC), a 5G Core (5GC), or an internet via a RAN established by one or more BSs and the network elements / functions.

[0033] A UE may include, but is not limited to, a mobile station, a mobile terminal or device, or a user communication radio terminal. The UE may be a portable radio equipment that includes, but is not limited to, a mobile phone, a tablet, a wearable device, a sensor, a vehicle, a virtual reality (VR) device, an augmented (AR) device, an Internet of Things (IoT) device, an unmanned aerial vehicle (UAV), or a Personal Digital Assistant (PDA) with wireless communication capability. The UE may be configured to receive and transmit signals over an air interface to one or more cells in a RAN. In some implementations, the UE may be an AI / ML-enabled device and / or an AI / ML capable device that is equipped with AI module(s) and / or ML module(s).

[0034] The BS may be configured to provide communication services according to at least a Radio Access Technology (RAT), such as Worldwide Interoperability for Microwave Access (WiMAX), Global System for Mobile communications (GSM) that is often referred to as 2G, GSM Enhanced Data rates for GSM Evolution (EDGE) RAN (GERAN), General Packet Radio Service (GPRS), Universal Mobile Telecommunication System (UMTS) that is often referred to as 3G based on basic Wideband-Code Division Multiple Access (W-CDMA), High-Speed Packet Access (HSPA), LTE, LTE-A, evolved / enhanced LTE (eLTE) that is LTE connected to 5GC, NR (often referred to as 5G), 5G-A, and / or LTE-A Pro. However, the scope of the present disclosure is not limited to these protocols.

[0035] The BS may include, but is not limited to, a node B (NB) in the UMTS, an evolved node B (eNB) in LTE or LTE-A, a radio network controller (RNC) in UMTS, a BS controller (BSC) in the GSM / GERAN, a next-generation eNB (ng-eNB) in an Evolved Universal Terrestrial Radio Access (E-UTRA) BS in connection with 5GC, a next-generation Node B (gNB) in the 5G-RAN or in the 5G Access Network (5G-AN), or any other apparatus capable of controlling radio communication and managing radio resources within a cell. The BS may serve one or more UEs via a radio interface. Although the gNB is used as an example in some implementations within the present disclosure, it should be noted that the disclosed implementations may also be applied to other types of base stations. In some implementations, the BS may be an AI / ML-enabled device and / or an AI / ML capable device that is equipped with AI module(s) and / or ML module(s).

[0036] The BS may be operable to provide radio coverage to a specific geographical area using multiple cells forming the RAN. The BS may support the operations of the cells. Each cell may be operable to provide services to at least one UE within its radio coverage.

[0037] Each cell (may often referred to as a serving cell) may provide services to one or more UEs within the cell’s radio coverage, such that each cell schedules the downlink (DL) (and optionally uplink (UL) resources) to at least one UE within its radio coverage for DL (and optionally UL packet transmissions from the UE). The BS may communicate with one or more UEs in the radio communication system via the cells.

[0038] A cell may allocate sidelink (SL) resources for supporting the Proximity Services (ProSe), LTE SL services, LTE / NR sidelink communication services, LTE / NR sidelink discovery services, and / or LTE / NR Vehicle-to-Everything (V2X) services. In addition, a cell may allocate DL and / or UL resources for supporting Multicast / Broadcast Service (MBS) services, Non-Terrestrial Networks (NTN) services, positioning services, power serving services and / or Network Energy Saving (NES) services.

[0039] In Multi-RAT Dual Connectivity (MR-DC) cases, the primary cell of a Master Cell Group (MCG) or a Secondary Cell Group (SCG) may be referred to as a Special Cell (SpCell). A Primary Cell (PCell) may include the SpCell of an MCG. A Primary SCG Cell (PSCell) may include the SpCell of an SCG. MCG may include a group of serving cells associated with the Master Node (MN), including the SpCell and optionally one or more Secondary Cells (SCells). An SCG may include a group of serving cells associated with the Secondary Node (SN), including the SpCell and optionally one or more SCells.

[0040] As discussed above, the frame structure for NR may support flexible configurations for accommodating various next generation (e.g., 5G) communication requirements, such as Enhanced Mobile Broadband (eMBB), Massive Machine Type Communication (mMTC), and Ultra-Reliable and Low-Latency Communication (URLLC), while fulfilling high reliability, high data rate, and low latency requirements. The Orthogonal Frequency-Division Multiplexing (OFDM) technology in the third generation partnership project (3GPP) may serve as a baseline for an NR waveform. The scalable OFDM numerology, such as adaptive sub-carrier spacing, channel bandwidth, and Cyclic Prefix (CP), may also be used.

[0041] Two coding schemes may be considered for NR, specifically, Low-Density Parity-Check (LDPC) code and Polar Code. The coding scheme adaption may be configured based on channel conditions and / or service applications.

[0042] At least the DL transmission data, a guard period, and UL transmission data should be included in a transmission time interval (TTI) of a single NR frame. The respective portions of the DL transmission data, the guard period, and the UL transmission data should also be configurable based on, for example, the network dynamics of NR. SL resources may also be provided in an NR frame to support ProSe services or V2X services.

[0043] Any two or more than two of the following paragraphs, (sub)-bullets, points, actions, behaviors, terms, or claims described in the present disclosure may be combined logically, reasonably, and properly to form a specific method.

[0044] Any sentence, paragraph, (sub)-bullet, point, action, behaviors, terms, or claims described in the present disclosure may be implemented independently and separately to form a specific method.

[0045] Dependency, e.g., “based on”, “more specifically”, “preferably”, “in one embodiment”, “in some implementations”, etc., in the present disclosure is just one possible example which would not restrict the specific method.

[0046] According to any two or more than two of the following sentences, paragraphs, (sub)-bullets, points, actions, behaviors, terms, alternatives, aspects, examples, embodiments, or claims described in the present disclosure, “X / Y” includes the meaning of “X or Y”, “X and Y”, and “X and / or Y”.

[0047] One aspect of the present disclosure may be used, for example, in a communication, communication equipment (e.g., a mobile telephone apparatus, a base station apparatus, a wireless LAN apparatus, and / or a sensor device, etc.), an integrated circuit (e.g., a communication chip), and / or a program, etc.

[0048] In some implementations, all the designs / embodiment / implementations introduced within this disclosure are not limited to be applied for dealing with the problems discussed within this disclosure. For example, the described embodiments may be applied to solve other problems that exist in the RAN of wireless communication systems. In some implementations, all of the numbers listed within the designs / embodiment / implementations introduced within this disclosure are just examples and for illustration, for example, of how the described methods are executed.

[0049] Examples of some selected terms in the present disclosure are provided as follows.

[0050] UE: The UE may be referred to as the PHY / MAC / RLC / PDCP / SDAP entity. The PHY / MAC / RLC / PDCP / SDAP entity may also be referred to as the UE.

[0051] Network (NW): The NW may include a network node, a TRP, a cell (e.g., SpCell, PCell, PSCell, and / or SCell), an eNB, or a gNB.

[0052] Serving Cell: A PCell, a PSCell, or an SCell. The serving cell may be an activated or a deactivated serving cell.

[0053] Special Cell (SpCell): For a Dual Connectivity operation, the term Special Cell may include the PCell of the MCG or the PSCell of the SCG depending on whether the MAC entity is associated with the MCG or the SCG, respectively. Otherwise, the term Special Cell may include the PCell. A Special Cell may support the PUCCH transmission and the contention-based Random Access and may be always activated.

[0054] Layer 1 / Layer 2 Triggered Mobility (LTM): LTM is a procedure in which a network (NW) may receive one or more L1 or L3 measurement reports from a UE. Based on the measurement reports, the NW (e.g., a gNB) may change the serving cell of the UE by transmitting a cell switch command (CSC) via a MAC CE. The cell switch command may indicate an LTM candidate cell configuration that the gNB previously prepared and provided to the UE through RRC signaling. The UE may then switch to the target cell according to the cell switch command and apply the target configuration. The LTM procedure may be used to reduce mobility latency.

[0055] (Enhanced) LTM Cell Switch Command: The network may instruct the UE to perform an LTM cell switch procedure by sending an LTM Cell Switch Command MAC CE. If the MAC entity receives an LTM Cell Switch Command MAC CE or an Enhanced LTM Cell Switch Command MAC CE on a serving cell, the MAC entity of the UE may indicate to upper layers that the LTM cell switch procedure is triggered and may provide the Target Configuration ID included in the LTM Cell Switch Command MAC CE or the Enhanced LTM Cell Switch Command MAC CE. In addition, if the Next Hop Chaining Counter (NCC) value is included in the Enhanced LTM Cell Switch Command MAC CE, the MAC entity may indicate the NCC value to upper layers as well.

[0056] When a UE moves from a coverage area of one cell to a coverage area of another cell, a serving cell change may be performed to maintain radio connectivity and radio quality above a certain level. The serving cell change may be triggered based on L3 measurements and executed through an RRC signaling-triggered Reconfiguration with Synchronization for a change of a PCell and a PSCell, as well as release and / or addition of SCells, when applicable. Such L3-based mobility procedures may involve complete L2 and L1 resets, which may result in longer latency, larger overhead, and longer interruption time compared to beam switch mobility. LTM enhancements may enable serving cell changes through L1 / L2 signaling, thereby reducing latency, signaling overhead, and interruption time. Furthermore, when the UE is able to determine whether to switch the serving cell based on some defined conditions, the cell switch latency may be reduced significantly. Accordingly, conditional LTM (CLTM) may be introduced to enhance the handover process. In some implementations, the CLTM may be executed by the UE when one or more L1-based or L3-based LTM cell switch execution conditions are met.

[0057] CLTM Procedure

[0058] FIG. 1 is a diagram illustrating a CLTM procedure 100, according to an example implementation of the present disclosure. The CLTM procedure 100 may involve a UE 151, a source gNB 152, a target gNB-DU 153, another potential target gNB-DU 154, and a UPF 155. The overall CLTM procedure 100 may be divided into several stages, including CLTM preparation / configuration 161, early synchronization 162, CTLM execution 163, and CLTM completion 164.

[0059] Action 101 may correspond to a CLTM preparation procedure, which is further specified in FIG. 2. In action 108, the source gNB 152 may send an RRCReconfiguration message to the UE 151. The RRCReconfiguration message may include the CLTM configurations of candidate cells as well as the execution condition for the initial CLTM. In some implementations, action 108 may be optional while performing LTM or CLTM.

[0060] In action 109, the UE 151 may store the LTM candidate configurations and send an RRCReconfigurationComplete message to the source gNB 152. The UE 151 may start evaluating the execution conditions based on the provided configuration. In some implementations, action 109 may be optional while performing LTM or CLTM.

[0061] Action 110 may correspond to CLTM evaluation and early synchronization. In action 110, the source gNB 152 may trigger early synchronization to the UE 151, for example, based on the L1 measurement reports from the UE 151 in action 110a. The source gNB 152 may send a PDCCH order to the UE 151 in action 110b. Then in action 110c, the UE 151 may perform early synchronization with the target gNB-DU 153 and / or another potential target gNB-DU 154.

[0062] In action 111, the source gNB 152 may receive TA information from the target gNB-DU 153 and / or another potential target gNB-DU 154. In action 111a, the source gNB 152 may provide the TA value for each of the candidate cells with which the UE 151 has performed UL synchronization. In some implementations, the stage of early synchronization 162, including action 110 and / or action 111, may be optional while performing LTM or CLTM.

[0063] In action 113, the CLTM execution condition may be satisfied at the UE 151. On the satisfied candidate LTM cell, the UE 151 may perform the CLTM switch by applying the configuration of the satisfied candidate LTM cell. In some implementations, action 113 may be optional while performing LTM or CLTM.

[0064] In action 114, the UE 151 may send an RRCReconfigurationComplete message to the switched LTM cell (e.g., the target gNB-DU 153). If the UE has a valid TA as part of the UL early synchronization from action 110 and / or action 111, the UE may skip a RACH procedure. Otherwise, the RACH procedure may be performed as part of the CLTM switch. CLTM may be RACH-based or RACH-less. RACH-based CLTM may include Contention-Free Random Access (CFRA) and Contention-Based Random Access (CBRA). Configured grant-based RACH-less CLTM may be supported. Dynamic grant-based RACH-less CLTM may or may not be supported. In some implementations, action 114 may be optional while performing LTM or CLTM.

[0065] FIG. 2 is a diagram illustrating a CLTM preparation procedure 200, according to an example implementation of the present disclosure. In some implementations, the CLTM preparation procedure 200 may involve a UE 251, a source gNB 252, a target gNB-DU 253, a target gNB 254, another potential target gNB-DU 255, an AMF 256, and a UPF 257. The target gNB-DU 253 and the source gNB 252 may be connected to a common gNB-CU. An LTM procedure between the source gNB 252 and the target gNB-DU 253 may be referred to as inter gNB-DU LTM, intra-gNB LTM, or intra-CU LTM. On the other hand, the target gNB 254 and the source gNB 252 may belong to different gNB-CUs. An LTM procedure between the source gNB 252 and the target gNB 254 may be referred to as inter gNB-CU LTM, inter-gNB LTM, or inter-CU LTM.

[0066] Action 210 may correspond to mobility control information provided by the AMF 256. In action 201, the UE 251 may send a MeasurementReport message (e.g., an L3 measurement result) to the source gNB 252 containing measurements of neighboring cells. In some implementations, action 210 may be optional while performing LTM or CLTM. In action 202, the source gNB 252 may determine to configure LTM. In some implementations, action 202 may be optional while performing LTM or CLTM.

[0067] In step 203, the source gNB 252 may request LTM for one or more candidate cells belonging to the source gNB 252 (e.g., target gNB-DU 253) and / or one or more candidate gNBs (e.g., target gNB 254). The source gNB 252 may request the candidate cells to provide conditional execution configurations. For inter-gNB LTM, the source gNB 252 may initiate a handover request message per candidate cell containing a candidate cell ID. For both intra-gNB and inter-gNB LTM, the source gNB 252 may request the candidate cells or gNBs to provide the CSI resource configuration. In some implementations, action 203 may be optional while performing LTM or CLTM. In action 204, admission control may be performed by the candidate cells or gNBs. In some implementations, action 204 may be optional while performing LTM or CLTM.

[0068] In action 205, the candidate cell may prepare and provide the LTM configurations to the source gNB 252. The candidate cells may provide the conditional configuration including their own execution conditions, to be used in subsequent CLTM. For inter-gNB LTM, the candidate gNBs (e.g., target gNB 254) may respond with a handover request acknowledge message to the source gNB 252 including the generated RRC configurations for the accepted candidate cell. For both intra-gNB and inter-gNB LTM, the candidate may also include additional information such as the CSI resource configuration and early synchronization information. In some implementations, action 205 may be optional while performing LTM or CLTM.

[0069] In action 206, the source gNB 252 may send an LTM configuration update message to the candidate gNBs to update the LTM configurations of the candidate cells. The source gNB 252 may include the common CSI resource configuration. In some implementations, action 206 may be optional while performing LTM or CLTM.

[0070] In action 207, the candidate gNBs may send an LTM configuration update acknowledge message to the source gNB 252. The candidate gNBs may also provide the CSI report configuration. In some implementations, action 207 may be optional while performing LTM or CLTM.

[0071] The LTM and / or CLTM procedures over the air interface described in FIG. 1 and / or FIG. 2 may be applicable to intra-gNB-DU LTM, inter-gNB-DU LTM, and inter-gNB-CU LTM.

[0072] In some implementations, the CLTM cell switch procedure may be triggered when the UE (or the MAC entity) determines that the event for CLTM is satisfied based on L1 measurements and / or the event for conditional LTM is satisfied based on L3 measurements indicated by upper layers.

[0073] A new MAC CE, such as an LTM candidate Timing Advance Command MAC CE, may be introduced for CLTM. The MAC CE may include a Timing Advance Command field to indicate a TA index value TAused to control the amount of timing adjustment that the MAC entity of the UE (or the UE) may apply when the UE switches to the candidate cell during CLTM. The length of the field may be 12 bits.

[0074] For CLTM, the UE may not receive an LTM Cell Switch Command (CSC) MAC CE that includes a Timing Advance Command field to indicate the TA index value TAfor the target cell. The UE may transmit a preamble (e.g., associated with the PDCCH order) to one or more candidate cells, so that the one or more candidate cells may acquire, calculate, or measure the TA for each candidate cell. The one or more candidate cells may then transmit the related TA index value TAto the source cell via the new MAC CE, such as the LTM candidate Timing Advance Command MAC CE.

[0075] The UE may calculate the timing advance between downlink and uplink according to NTAand NTA,offset. The uplink frame number i for transmission from the UE may start at TTA= (NTA+ NTA,offset)・Tc before the start of the corresponding downlink frame at the UE, where Tc may be the basic time unit for the system. TTAmay represent the timing advance between downlink and uplink. The UE may be provided with a value NTA,offsetof a timing advance offset for a serving cell by an RRC parameter, such as n-TimingAdvanceOffset, for the serving cell. In some implementations, NTA= TA・16・64 / 2μwhere TAmay be the index value indicated by the timing advance command field, and the parameter μ may be relative to the subcarrier spacing (SCS) of the first uplink transmission from the UE after the reception of the random access response, an absolute timing advance command MAC CE, or the cell switch command.

[0076] However, for CLTM, when the UE receives the new MAC CE (e.g., LTM candidate Timing Advance Command MAC CE) which includes the Timing Advance Command field indicating the TA index value TA, the UE may not be able to calculate NTAwith a parameter μ that is associated with the subcarrier spacing of the first uplink transmission from the UE after the reception of the new MAC CE. This is because, in a CLTM procedure, when the UE receives one or more LTM candidate Timing Advance Command MAC CEs for one or more candidate cells, the UE may not apply or calculate the timing advance right after the reception of the new MAC CE. Instead, the UE may wait until the UE determines which candidate cell the UE would switch to and may then apply only one TA command to the target cell. Alternatively, the UE may store the one or more LTM candidate Timing Advance Command MAC CEs until the UE determines which candidate cell the UE would switch to. As a result, the subcarrier spacing of the first uplink transmission after the reception of the new MAC CE may not be well-defined at the time of reception, and therefore the parameter μ may not be determined for calculating NTAat that point.

[0077] In the present disclosure, how to apply or calculate the timing advance for the new MAC CE (e.g., LTM candidate Timing Advance Command MAC CE) introduced for CLTM is described. Moreover, how to determine the subcarrier spacing (SCS) associated with the NTAis also described.

[0078] Receiving / Determining a Timing Advance Offset

[0079] In some implementations, the UE may be provided with a value NTA,offsetof a timing advance offset for a serving cell by a first RRC parameter (e.g., n-TimingAdvanceOffset) for the serving cell.

[0080] In some implementations, if for a serving cell the UE is provided with two coresetPoolIndex values 0 and 1 for first and second CORESETs, or is not provided with a coresetPoolIndex value for first CORESETs and is provided with a coresetPoolIndex value of 1 for second CORESETs, the UE may be provided with first and second NTA,offsetvalues by the first RRC parameter (e.g., n-TimingAdvanceOffset) and a second RRC parameter (e.g., n-TimingAdvanceOffset2) for transmissions with first and second spatial filters associated with first and second TCI states for the first and second CORESETs, respectively.

[0081] In some implementations, the UE may be provided with a second NTA,offsetvalue for transmissions with second spatial domain filters corresponding to second TCI states or to second SS / PBCH block receptions associated with a physCellId different from the physCellId for the serving cell, in addition to a first NTA,offsetvalue for transmissions with first spatial domain filters corresponding to first TCI states or to first SS / PBCH block receptions associated with the physCellId for the serving cell. In some implementations, the first and second NTA,offsetvalues may correspond to first and second TAGs indicated in respective MAC RARs, in an absolute timing advance command MAC CE, or in a new MAC CE (e.g., LTM candidate Timing Advance Command MAC CE) having an association indicated by tag-Id-ptr with first and second joint TCI states provided by dl-OrJointTCI-StateList or first and second UL TCI states provided by ul-TCI-State-List. In some implementations, if the UE is not provided with the first RRC parameter (e.g., n-TimingAdvanceOffset) for a serving cell, the UE may determine a default value NTA,offsetof the timing advance offset for the serving cell.

[0082] Receiving a MAC CE including a Timing Advance Command

[0083] In some implementations, the UE may receive a new MAC CE (e.g., LTM candidate Timing Advance Command MAC CE) including at least one of a timing advance command field to indicate the index value (e.g., TA) used to control the amount of timing adjustment or timing advance, a candidate configuration ID field, and a TAG indication field.

[0084] In some implementations, the timing advance command field may indicate the index value TA used to control the amount of timing adjustment that the MAC entity of the UE may apply when the UE switches to the candidate cell during CLTM. The length of the field may be 8 or 12 bits.

[0085] In some implementations, the candidate configuration ID field may indicate the index of the corresponding CLTM candidate configuration in the PDCCH order associated with the Timing Advance Command, corresponding to ltm-CandidateID (e.g., ltm-CandidateID minus 1). The length of the field may be 3 bits.

[0086] In some implementations, the TAG indication field, or TI field, may indicate one of two TAGs to which the Timing Advance Command may be applied if two TAGs are configured for the CLTM candidate cell indicated by the latest PDCCH order before the UE receives the new MAC CE (e.g., LTM candidate Timing Advance Command MAC CE). The field set to 0 may indicate the tag2-Id, and the field set to 1 may indicate the tag-Id of the CLTM candidate cell. If two TAGs are not configured for the CLTM candidate cell indicated by the latest PDCCH order before the UE receives the MAC CE, the R bit may be present instead.

[0087] In some implementations, upon reception of a timing advance command for a TAG in the new MAC CE (e.g., LTM candidate Timing Advance Command MAC CE), the UE may not adjust uplink timing for PUSCH / SRS / PUCCH transmission on all the serving cells in the TAG based on a value NTA,offsetand based on the received timing advance command or TAuntil the UE determines which target or candidate cell the UE would switch to.

[0088] In some implementations, upon reception of a timing advance command in the new MAC CE (e.g., LTM candidate Timing Advance Command MAC CE) for a TAG, the UE may store the index value (e.g., TA) indicated by the timing advance command and adjust uplink timing for PUSCH / SRS / PUCCH transmission on all the serving cells in the TAG based on a value NTA,offsetthat the UE expects to be the same for all the serving cells in the TAG and based on the received timing advance command, where the uplink timing for PUSCH / SRS / PUCCH transmissions is the same for all the serving cells in the TAG, until the UE determines which target or candidate cell the UE would switch to.

[0089] In some implementations, upon reception of a timing advance command for a TAG in the new MAC CE (e.g., LTM candidate Timing Advance Command MAC CE), the UE may not adjust uplink timing for PUSCH / SRS / PUCCH transmission on all the serving cells in the TAG based on a value NTA,offsetand based on the received timing advance command or TAuntil the UE transmits the first UL transmission to the target cell after the UE switches to the target cell (e.g., during CLTM).

[0090] In some implementations, upon reception of a timing advance command in the new MAC CE (e.g., LTM candidate Timing Advance Command MAC CE) for a TAG, the UE may adjust uplink timing for PUSCH / SRS / PUCCH transmission on all the serving cells in the TAG based on a value NTA,offsetthat the UE expects to be the same for all the serving cells in the TAG and based on the received timing advance command, where the uplink timing for PUSCH / SRS / PUCCH transmissions is the same for all the serving cells in the TAG, after the UE transmits the first UL transmission to the target cell after the UE switches to the target cell (e.g., during CLTM).

[0091] In some implementations, upon reception of a timing advance command for a TAG in the new MAC CE (e.g., LTM candidate Timing Advance Command MAC CE), the UE may not adjust uplink timing for PUSCH / SRS / PUCCH transmission on all the serving cells in the TAG based on a value NTA,offsetand based on the received timing advance command or TAuntil the UE transmits the CLTM complete message (e.g., to the target cell).

[0092] In some implementations, upon reception of a timing advance command in the new MAC CE (e.g., LTM candidate Timing Advance Command MAC CE) for a TAG, the UE may adjust uplink timing for PUSCH / SRS / PUCCH transmission on all the serving cells in the TAG based on a value NTA,offsetthat the UE expects to be the same for all the serving cells in the TAG and based on the received timing advance command, where the uplink timing for PUSCH / SRS / PUCCH transmissions is the same for all the serving cells in the TAG, after the UE transmits the CLTM complete message (e.g., to the target cell).

[0093] In some implementations, upon reception of a timing advance command for a TAG in the new MAC CE, such as the LTM candidate Timing Advance Command MAC CE, the UE may not adjust uplink timing for PUSCH / SRS / PUCCH transmission on all the serving cells in the TAG based on a value NTA,offsetand based on the received timing advance command or TAuntil the UE applies the RRCReconfiguration or the configuration associated with the target cell (e.g., during CLTM). In some implementations, upon reception of a timing advance command in the new MAC CE for a TAG, the UE may adjust uplink timing for PUSCH / SRS / PUCCH transmission on all the serving cells in the TAG based on a value NTA,offsetthat the UE expects to be the same for all the serving cells in the TAG and based on the received timing advance command, where the uplink timing for PUSCH / SRS / PUCCH transmissions is the same for all the serving cells in the TAG, after the UE applies the RRCReconfiguration or the configuration associated with the target cell (e.g., during CLTM).

[0094] In some implementations, upon reception of a timing advance command for a TAG in the new MAC CE, such as the LTM candidate Timing Advance Command MAC CE, the UE may not adjust uplink timing for PUSCH / SRS / PUCCH transmission on all the serving cells in the TAG based on a value NTA,offsetand based on the received timing advance command or TAuntil the UE applies the CLTM execution. In some implementations, upon reception of a timing advance command in the new MAC CE for a TAG, the UE may adjust uplink timing for PUSCH / SRS / PUCCH transmission on all the serving cells in the TAG based on a value NTA,offsetthat the UE expects to be the same for all the serving cells in the TAG and based on the received timing advance command, where the uplink timing for PUSCH / SRS / PUCCH transmissions is the same for all the serving cells in the TAG, after the UE applies the CLTM execution.

[0095] In some implementations, upon reception of a timing advance command for a TAG in the new MAC CE, such as the LTM candidate Timing Advance Command MAC CE, the UE may not adjust uplink timing for PUSCH / SRS / PUCCH transmission on all the serving cells in the TAG based on a value NTA,offsetand based on the received timing advance command or TAuntil one or more execution conditions for CLTM are satisfied. In some implementations, upon reception of a timing advance command in the new MAC CE for a TAG, the UE may adjust uplink timing for PUSCH / SRS / PUCCH transmission on all the serving cells in the TAG based on a value NTA,offsetthat the UE expects to be the same for all the serving cells in the TAG and based on the received timing advance command, where the uplink timing for PUSCH / SRS / PUCCH transmissions is the same for all the serving cells in the TAG, after one or more execution conditions for CLTM are satisfied.

[0096] In some implementations, upon reception of a timing advance command for a TAG in the new MAC CE, such as the LTM candidate Timing Advance Command MAC CE, the UE may not adjust uplink timing for PUSCH / SRS / PUCCH transmission on all the serving cells in the TAG based on a value NTA,offsetand based on the received timing advance command or TAuntil the UE executes CLTM. In some implementations, upon reception of a timing advance command in the new MAC CE for a TAG, the UE may adjust uplink timing for PUSCH / SRS / PUCCH transmission on all the serving cells in the TAG based on a value NTA,offsetthat the UE expects to be the same for all the serving cells in the TAG and based on the received timing advance command, where the uplink timing for PUSCH / SRS / PUCCH transmissions is the same for all the serving cells in the TAG, after the UE executes CLTM.

[0097] In some implementations, upon reception of a timing advance command that is not in the new MAC CE (e.g., the LTM candidate Timing Advance Command MAC CE) for a TAG, the UE may adjust uplink timing for PUSCH / SRS / PUCCH transmission on all the serving cells in the TAG based on a value NTA,offsetthat the UE expects to be the same for all the serving cells in the TAG and based on the received timing advance command, where the uplink timing for PUSCH / SRS / PUCCH transmissions is the same for all the serving cells in the TAG.

[0098] In some implementations, upon reception of a timing advance command in the new MAC CE (e.g., the LTM candidate Timing Advance Command MAC CE) for a TAG, the UE may store the index value (e.g., TA) indicated by the timing advance command and adjust uplink timing for PUSCH / SRS / PUCCH transmission on all the serving cells in the TAG based on a value NTA,offsetthat the UE expects to be the same for all the serving cells in the TAG and based on the received timing advance command, where the uplink timing for PUSCH / SRS / PUCCH transmissions is the same for all the serving cells in the TAG.

[0099] Storing the index value (e.g., TA) indicated by the timing advance command

[0100] In some implementations, the UE may store the index value (e.g., TA) indicated by the timing advance command field or indicated by the new MAC CE (e.g., LTM candidate Timing Advance Command MAC CE) for the indicated LTM candidate cell (for the indicated TAG) in response to receiving the index value. In some implementations, the UE may store the index value (e.g., TA) indicated by the timing advance command field or indicated by the new MAC CE for the indicated LTM candidate cell (for the indicated TAG) and may not apply the index value in response to receiving the index value.

[0101] In some implementations, the UE may not apply the index value (e.g., TA) indicated by the timing advance command field or indicated by the new MAC CE (e.g., LTM candidate Timing Advance Command MAC CE) for the serving cell.

[0102] In some implementations, the UE may not apply the index value (e.g., TA) indicated by the timing advance command field or indicated by the new MAC CE (e.g., LTM candidate Timing Advance Command MAC CE) after the UE receives the new MAC CE.

[0103] In some implementations, the UE may not apply the index value (e.g., TA) indicated by the timing advance command field or indicated by the new MAC CE (e.g., LTM candidate Timing Advance Command MAC CE) until the UE determines which target or candidate cell the UE would switch to.

[0104] In some implementations, the UE may not apply the index value (e.g., TA) indicated by the timing advance command field or indicated by the new MAC CE (e.g., LTM candidate Timing Advance Command MAC CE) until the UE transmits the first UL transmission to the target cell after the UE switches to the target cell (e.g., during CLTM).

[0105] In some implementations, the UE may not apply the index value (e.g., TA) indicated by the timing advance command field or indicated by the new MAC CE (e.g., LTM candidate Timing Advance Command MAC CE) until the UE transmits the CLTM complete message (e.g., to the target cell).

[0106] In some implementations, the UE may not apply the index value (e.g., TA) indicated by the timing advance command field or indicated by the new MAC CE (e.g., LTM candidate Timing Advance Command MAC CE) until the UE applies the RRCReconfiguration or the configuration associated with the target cell (e.g., during CLTM).

[0107] In some implementations, the UE may store one or more index values (e.g., TA) indicated by one or more timing advance command fields or indicated by one or more new MAC CEs, such as LTM candidate Timing Advance Command MAC CEs, for the indicated LTM candidate cells and for the indicated TAG.

[0108] In some implementations, the UE may determine the LTM candidate cell ID according to the candidate configuration ID field in the new MAC CE, such as the LTM candidate Timing Advance Command MAC CE.

[0109] In some implementations, the UE may determine the TAG of the LTM candidate cell according to the TAG indication field, or TI field, in the new MAC CE, such as the LTM candidate Timing Advance Command MAC CE.

[0110] In some implementations, the UE may stop storing the index value (e.g., TA) indicated by the timing advance command field or indicated by the new MAC CE (e.g., LTM candidate Timing Advance Command MAC CE) for the indicated LTM candidate cell (for the indicated TAG) when the UE receives the (enhanced) LTM cell switch command MAC CE. In some implementations, the UE may release or clear the stored index value (e.g., TA) indicated by the timing advance command field for the indicated LTM candidate cell (for the indicated TAG) when the UE receives the (enhanced) LTM cell switch command MAC CE. In some implementations, the UE may release or clear the stored timing advance command indicated by the new MAC CE for the indicated LTM candidate cell (for the indicated TAG) when the UE receives the (enhanced) LTM cell switch command MAC CE.

[0111] In some implementations, the UE may keep the stored index value (e.g., TA) (or the timing advance command) indicated by the timing advance command field or indicated by the new MAC CE (e.g., LTM candidate Timing Advance Command MAC CE) for the indicated LTM candidate cell (for the indicated TAG) when the UE receives the (enhanced) LTM cell switch command MAC CE. In some implementations, the UE may not release or may not clear the stored index value (e.g., TA) indicated by the timing advance command field for the indicated LTM candidate cell (for the indicated TAG) when the UE receives the (enhanced) LTM cell switch command MAC CE. In some implementations, the UE may not release or may not clear the stored timing advance command indicated by the new MAC CE for the indicated LTM candidate cell (for the indicated TAG) when the UE receives the enhanced LTM cell switch command MAC CE.

[0112] Starting / Restarting a first timer (e.g., ltm-Candidate-TimeAlignmentTimer)

[0113] In some implementations, the UE may start or restart a first timer (e.g., ltm-Candidate-TimeAlignmentTimer, ltm-TimeAlignmentTimer, or ltm-TimeAlignmentTimerTag2) associated with the indicated LTM candidate cell (for the indicated TAG) when a CLTM cell switch procedure is triggered for a CLTM candidate cell or indicated by an upper layer, and / or if the first timer associated with the CLTM candidate cell (for the TAG associated with the selected beam for CLTM) is running, and / or when the UE applies the stored index value or the stored timing advance command associated with the CLTM candidate cell for the PTAG. The indicated LTM candidate cell may be determined according to the candidate configuration ID field in the new MAC CE. The indicated TAG may be determined according to the TI field in the new MAC CE.

[0114] The first timer (e.g., ltm-Candidate-TimeAlignmentTimer, ltm-TimeAlignmentTimer, or ltm-TimeAlignmentTimerTag2) may be configured in each LTM candidate configuration or in EarlyUL-SyncConfig in each LTM candidate configuration. In some implementations, the first timer may be stopped when the UE performs a CLTM execution, when the UE starts to perform a CLTM execution, when the UE determines to switch to a target cell, when the UE switches to a target cell, when the UE performs a CLTM cell switch, when the UE receives the LTM CSC MAC CE, or when one or more conditions for CLTM are satisfied.

[0115] In some implementations, the first timer may control how long the UE (e.g., the MAC entity of the UE) considers the CLTM candidate cells associated with the first timer to be uplink time aligned. Each first timer (e.g., ltm-Candidate-TimeAlignmentTimer, ltm-TimeAlignmentTimer, or ltm-TimeAlignmentTimerTag2) may be associated with one candidate configuration for CLTM. The first timer may be configured on a per-TAG basis if two TAGs are configured for the CLTM candidate cell.

[0116] In some implementations, the UE may release or stop the first timer, such as ltm-Candidate-TimeAlignmentTimer, associated with the indicated LTM candidate cell (for the indicated TAG) when the UE receives the (enhanced) LTM cell switch command MAC CE.

[0117] In some implementations, the UE may not release, may not reset, or may not restart the first timer, such as ltm-Candidate-TimeAlignmentTimer, associated with the indicated LTM candidate cell (for the indicated TAG) when the UE receives the (enhanced) LTM cell switch command MAC CE.

[0118] In some implementations, the UE may keep the first timer, such as ltm-Candidate-TimeAlignmentTimer, associated with the indicated LTM candidate cell (for the indicated TAG) when the UE receives the (enhanced) LTM cell switch command MAC CE.

[0119] In some implementations, if the MAC reset operation is performed when the UE receives an (enhanced) LTM cell switch command MAC CE, the UE may release or clear one or more first timers, such as ltm-Candidate-TimeAlignmentTimer, associated with the indicated LTM candidate cell (for the indicated TAG).

[0120] In some implementations, if the MAC reset operation is performed when the UE receives an (enhanced) LTM cell switch command MAC CE, the UE may not release or clear one or more first timers, such as ltm-Candidate-TimeAlignmentTimer, associated with the indicated LTM candidate cell (for the indicated TAG).

[0121] CLTM cell switch procedure is triggered for a CLTM candidate cell or indicated by an upper layer

[0122] In some implementations, the UE may be triggered with a CLTM cell switch procedure for a CLTM candidate cell, or the UE may be indicated a CLTM cell switch procedure by an upper layer. In the present disclosure, the candidate cell may be either a candidate cell that does not support CLTM or a CLTM candidate cell.

[0123] Setting / calculating / determining the NTAvalue

[0124] In some implementations, the UE may set, calculate, or determine a time alignment value, or NTAvalue, according to at least the stored index value (e.g., TA) and a subcarrier spacing (SCS).

[0125] In some implementations, a timing advance command in a MAC CE (e.g., LTM candidate TA MAC CE), TA, for a TAG may indicate NTAvalues by index values of TA= 0, 1, 2, ..., 3846, where an amount of the time alignment for the TAG with SCS of 2μ・15 kHz is NTA= TA・16・64 / 2μ. NTAmay be relative to the SCS of the first uplink transmission from the UE after the reception of the MAC CE (e.g., LTM candidate TA MAC CE).

[0126] In some implementations, a timing advance command in a MAC CE (e.g., LTM candidate TA MAC CE), TA, for a TAG may indicate NTAvalues by index values of TA= 0, 1, 2, ..., 3846, where an amount of the time alignment for the TAG with SCS of 2μ・15 kHz is NTA= TA・16・64 / 2μ. NTAmay be relative to the SCS of the first uplink transmission to the target cell or the CLTM target or candidate cell from the UE after the reception of the MAC CE (e.g., LTM candidate TA MAC CE).

[0127] In some implementations, a timing advance command in a MAC CE (e.g., LTM candidate TA MAC CE), TA, for a TAG may indicate NTAvalues by index values of TA= 0, 1, 2, ..., 3846, where an amount of the time alignment for the TAG with SCS of 2μ・15 kHz is NTA= TA・16・64 / 2μ. NTAmay be relative to the SCS of the first uplink transmission from the UE after the UE switches to the target cell (e.g., during CLTM) or after the UE switches to one of the CLTM candidate cells.

[0128] In some implementations, a timing advance command in a MAC CE (e.g., LTM candidate TA MAC CE), TA, for a TAG may indicate NTAvalues by index values of TA= 0, 1, 2, ..., 3846, where an amount of the time alignment for the TAG with SCS of 2μ・15 kHz is NTA= TA・16・64 / 2μ. NTAmay be relative to the SCS of the first uplink transmission from the UE after the UE applies or performs a CLTM execution procedure or after the UE performs a RACH-less CLTM cell switch procedure.

[0129] In some implementations, a timing advance command in a MAC CE (e.g., LTM candidate TA MAC CE), TA, for a TAG may indicate NTAvalues by index values of TA= 0, 1, 2, ..., 3846, where an amount of the time alignment for the TAG with SCS of 2μ・15 kHz is NTA= TA・16・64 / 2μ. NTAmay be relative to the SCS of the first configured grant (Type 1 and / or Type 2) PUSCH after the UE switches to the target cell (e.g., during CLTM) or after the UE switches to one of the CLTM candidate cells. Alternatively, NTAmay be relative to the SCS of the first dynamic grant PUSCH after the UE switches to the target cell during CLTM or after the UE switches to one of the CLTM candidate cells.

[0130] In some implementations, a timing advance command in a MAC CE (e.g., LTM candidate TA MAC CE), TA, for a TAG may indicate NTAvalues by index values of TA= 0, 1, 2, ..., 3846, where an amount of the time alignment for the TAG with SCS of 2μ・15 kHz is NTA= TA・16・64 / 2μ. NTAmay be relative to the SCS that the UE used to transmit the CLTM complete message.

[0131] Applying the stored index value (e.g., TA)

[0132] In some implementations, the UE may apply the stored index value (e.g., TA), the NTAvalue, or the timing advance value associated with the CLTM candidate cell (for the PTAG) and may start or restart a second timer (e.g., timeAlignmentTimer) associated with the PTAG with the length of the remaining time till expiry for the first timer when a conditional LTM cell switch procedure is triggered (for a CLTM candidate cell) or indicated by an upper layer and the first timer (e.g., ltm-Candidate-TimeAlignmentTimer, ltm-TimeAlignmentTimer, or ltm-TimeAlignmentTimerTag2) is running.

[0133] In some implementations, the UE may apply the stored index value (e.g., TA), the NTAvalue, or the timing advance value associated with the CLTM candidate cell (for the PTAG) and may start / restart a first timer (e.g., ltm-Candidate-TimeAlignmentTimer, ltm-TimeAlignmentTimer, or ltm-TimeAlignmentTimerTag2) associated with the PTAG when a conditional LTM cell switch procedure is triggered (for a CLTM candidate cell) or indicated by an upper layer and the first timer is running.

[0134] In some implementations, the UE may transmit the UL PUSCH / SRS / PUCCH with a timing advance between downlink and uplink (e.g., TTA). The TTAmay be associated with the timing advance offset (e.g., NTA,offset) and the NTAvalue. In some implementations, TTA= (NTA+ NTA,offset)・Tc.

[0135] In some implementations, the UE may receive, from a serving cell or gNB, an RRC parameter including a timing advance offset. The UE may receive a MAC CE from the serving cell or gNB, the MAC CE including at least one of a timing advance command field to indicate the index value (e.g., TA) used to control the amount of timing adjustment or timing advance, a candidate configuration ID field, and a TAG indication field. In some implementations, when a conditional LTM cell switch procedure is triggered for a CLTM candidate cell or indicated by an upper layer, the UE may store the index value or the timing advance command indicated by the timing advance command field (or indicated by the MAC CE) for the indicated LTM candidate cell (for the indicated TAG), and / or the UE may start or restart a first timer (e.g., ltm-Candidate-TimeAlignmentTimer) associated with the indicated LTM candidate cell (for the indicated TAG). In some implementations, the UE may set, calculate, or determine an NTAvalue according to the stored index value or the stored timing advance command and a subcarrier spacing (SCS). The SCS may be determined based on at least one of the SCS of the first uplink transmission from the UE after the UE switches to the target cell (e.g., during CLTM), the SCS of the first configured grant Type 1 PUSCH after the UE switches to the target cell (e.g., during CLTM), the SCS that the UE used to transmit the CLTM complete message, and the SCS of the first uplink transmission from the UE after the UE applies the configuration associated with the target cell (e.g., during CLTM). In some implementations, the UE may apply the stored index value (e.g., TA), apply the NTAvalue, or apply the timing advance value associated with the CLTM candidate cell (for the PTAG), and may start or restart a second timer (e.g., timeAlignmentTimer) (associated with the PTAG) with the length of the remaining time till expiry for the first timer when a conditional LTM cell switch procedure is executed (for a CLTM candidate cell) or indicated by an upper layer and the first timer (e.g., ltm-Candidate-TimeAlignmentTimer) is running. In some implementations, the UE may transmit the UL PUSCH / SRS / PUCCH with a timing advance between downlink and uplink, TTA, where TTAmay be associated with the timing advance offset and the NTAvalue.

[0136] In the present disclosure, how to determine the SCS associated with the NTAfor the new MAC CE (e.g., LTM candidate Timing Advance Command MAC CE) are described. With the techniques described in the present disclosure, timing advance for CLTM can be achieved.

[0137] In some implementations, a method performed by a UE may include:   receiving, from a serving cell / gNB, an RRC parameter including a timing advance offset;   receiving, from the serving cell / gNB, a MAC CE including at least one of a timing advance command field to indicate the index value (e.g., TA) used to control the amount of timing adjustment (or timing advance), a candidate config ID field, and a TAG indication field;   storing the index value (e.g., TA) indicated by the timing advance command field or indicated by the MAC CE for the indicated LTM candidate cell (for the indicated TAG);   starting or restarting a first timer (e.g., ltm-Candidate-TimeAlignmentTimer) associated with the indicated LTM candidate cell (for the indicated TAG);   setting / calculating / determining a NTAvalue according to the stored index value (e.g., TA) and a subcarrier spacing (SCS),   where the SCS may be determined based on at least one of the SCS of the first uplink transmission from the UE after the UE switches to the target cell (during CLTM), the SCS of the first configured grant (Type 1) PUSCH after the UE switches to the target cell (during CLTM), the SCS that the UE used to transmit CLTM complete (message), and the SCS of the first uplink transmission from the UE after the UE applies configuration associated with the target cell (during CLTM);   applying the stored index value (e.g., TA), applying the NTAvalue, or applying the timing advance value associated with the CLTM candidate cell (for the PTAG) and starting / restarting a second timer (e.g., timeAlignmentTimer) associated with the PTAG with the length of the remaining time till expiry for the first timer when a conditional LTM cell switch procedure is executed (for a CLTM candidate cell) or indicated by upper layer and a first timer (e.g., ltm-Candidate-TimeAlignmentTimer) is running, and   transmitting the UL PUSCH / SRS / PUCCH with a timing advance between downlink and uplink, TTA, where the TTAis associated with the timing advance offset and the NTAvalue.

[0138] FIG. 3 is a flowchart illustrating a method / process 300 performed by a UE for performing a CLTM operation, according to an example implementation of the present disclosure. In the action 302, the process 300 may start by receiving, from a serving cell, a MAC CE including a TA command indicating a TA index (e.g., TA) for a CLTM candidate cell. For example, the serving cell may correspond to the source gNB 152 illustrated in FIG. 1 or the source gNB 252 illustrated in FIG. 2. Transmission of the MAC CE that includes the TA command may correspond to action 111a illustrated in FIG. 1. The MAC CE may be an LTM candidate Timing Advance Command MAC CE. In some implementations, the TA index may be acquired by the candidate cell via a preamble transmission from the UE as triggered by a PDCCH order from the serving cell.

[0139] In the action 304, the process 300 may store the TA index for the CLTM candidate cell in response to receiving the MAC CE. In the action 306, the process 300 may perform a RACH-less CLTM cell switch to the CLTM candidate cell. In the action 308, the process 300 may determine an actual TA value (e.g., NTA) applied in the CLTM candidate cell based on the TA index and an SCS of an uplink transmission that occurs first in time after performing the RACH-less CLTM cell switch. In some implementations, the UE may determine the actual TA value (e.g., NTA) based on the formula NTA= TA・16・64 / 2μ, where TAis the TA index stored in the action 304, and the parameter μ is relative to the SCS (e.g., 2μ・15 kHz) of the first uplink transmission from the UE after the UE switches to the CLTM candidate cell. The process 300 may then end. In some implementations, the first uplink transmission may correspond to a configured grant (e.g., Type 1) PUSCH or a dynamic grant PUSCH, depending on the uplink resource configuration of the CLTM candidate cell.

[0140] The steps / actions shown in FIG. 3 should not be construed as necessarily order dependent. The order in which the process is described is not intended to be construed as a limitation. Moreover, some of the actions shown in FIG. 3 may be omitted in some implementations and one or more actions shown in FIG. 3 may be combined.

[0141] The technical problem addressed by the method illustrated in FIG. 3 is accurately determining the SCS reference for applying a TA command in a CLTM operation, particularly when the TA command is received prior to the UE determining which candidate cell to switch to. In a CLTM procedure, one or more TA commands for one or more CLTM candidate cells may be received well before the UE decides on a target cell, such that the SCS reference for calculating the actual TA value may not be well-defined at the time of reception of the MAC CE. By storing the TA index indicated by the MAC CE in response to receiving the MAC CE, and by determining the actual TA value applied in the CLTM candidate cell based on the TA index together with the SCS of an uplink transmission that occurs first in time after performing the RACH-less CLTM cell switch, the UE may defer the TA calculation to a well-defined reference point tied to the target cell, rather than to the reception time of the MAC CE. This resolves ambiguity in the SCS reference for the actual TA value, avoids unnecessary or premature TA application for non-selected candidate cells, and enables efficient RACH-less cell switching by allowing the TA to be applied directly upon switching to the CLTM candidate cell without a random access procedure. The approach thereby reduces cell switch latency, minimizes signaling overhead, and enhances overall mobility performance during CLTM operations.

[0142] In some implementations, the UE may start or restart a first Time Alignment Timer (TAT) that is associated with the CLTM candidate cell in response to receiving the MAC CE. The UE may consider the TA index for the CLTM candidate cell as valid until the first TAT expires. In some implementations, the first TAT may control how long the UE considers the CLTM candidate cell associated with the first TAT to be uplink time aligned. The first TAT may correspond to an ltm-Candidate-TimeAlignmentTimer configured in the LTM candidate configuration or in the EarlyUL-SyncConfig of the LTM candidate configuration. In some implementations, if the first TAT expires before the CLTM cell switch is performed, the UE may discard the stored TA index and may perform a RACH-based CLTM cell switch instead.

[0143] In some implementations, the UE may further start or restart a second TAT in response to performing the RACH-less CLTM cell switch while the first TAT is running. The second TAT may be associated with a PTAG of the CLTM candidate cell. The second TAT may be set to a duration equal to a remaining time of the first TAT when the RACH-less CLTM cell switch is performed. In this manner, the uplink time alignment validity for the CLTM candidate cell may be seamlessly transferred from the first TAT to the second TAT upon switching. The second TAT may correspond to a timeAlignmentTimer associated with the PTAG of the CLTM candidate cell after the cell switch.

[0144] In some implementations, the MAC CE may further include a TAG indication field that indicates one of the TAGs configured for the CLTM candidate cell, to which the TA command is applied. For example, two TAGs may be configured for the CLTM candidate cell, and the TAG indication field may indicate one of the two TAGs to which the TA command is applied. In some implementations, the TAG indication field may be a TI field, where the field set to 0 may indicate the tag2-Id and the field set to 1 may indicate the tag-Id of the CLTM candidate cell. If two TAGs are not configured for the CLTM candidate cell, the TAG indication field may be replaced by a reserved bit.

[0145] In some implementations, the MAC CE may further include a candidate configuration ID field that indicates a CLTM candidate configuration corresponding to the CLTM candidate cell. In some implementations, the UE may determine the CLTM candidate cell base on the candidate configuration ID field in the MAC CE. For example, the candidate configuration ID field may indicate the index of the corresponding CLTM candidate configuration, corresponding to ltm-CandidateID minus 1. In some implementations, the length of the candidate configuration ID field may be 3 bits.

[0146] In some implementations, the UE may receive, from the serving cell, an RRC parameter indicating a TA offset (e.g., NTA,offset). The actual TA value applied in the CLTM candidate cell may be further determined based on the TA offset. For example, the actual TA value may be determined based on the sum (NTA+ NTA,offset), where NTA= TA・16・64 / 2μ. In some implementations, the UE may be provided with the TA offset by the RRC parameter such as n-TimingAdvanceOffset for the serving cell. If the UE is not provided with the RRC parameter for the serving cell, the UE may determine a default value of the TA offset. In some implementations, the UE may transmit the UL PUSCH, SRS, or PUCCH with a timing advance between downlink and uplink based on the actual TA value and the TA offset.

[0147] It should be noted that the BS may perform methods or actions corresponding to those performed by the UE. For example, the receiving actions performed by the UE may correspond to the transmitting or configuring actions of the BS; the transmitting actions performed by the UE may correspond to the receiving actions of the BS; and the detecting actions performed by the UE may correspond to the broadcasting actions of the BS. That is, the BS and the UE may have reciprocally aligned roles in transmission and reception.

[0148] For example, the BS (e.g., a serving cell or a source cell) may transmit, to the UE, a MAC CE including a TA command indicating a TA index for a CLTM candidate cell. The UE may store the TA index for the CLTM candidate cell in response to receiving the MAC CE. The UE may perform a RACH-less CLTM cell switch to the CLTM candidate cell. The UE may determines an actual TA value applied in the CLTM candidate cell based on the TA index and an SCS of an uplink transmission that occurs first in time after performing the RACH-less CLTM cell switch. In some implementations, the BS may transmit an RRC parameter indicating a TA offset. The UE may determines the actual TA value applied in the CLTM candidate cell further based on the TA offset.

[0149] FIG. 4 is a block diagram illustrating a node 400 for wireless communication, according to an example implementation of the present disclosure. As illustrated in FIG. 4, a node 400 may include a transceiver 420, a processor 428, a memory 434, one or more presentation components 438, and at least one antenna 436. The node 400 may also include a radio frequency (RF) spectrum band module, a BS communications module, a network communications module, and a system communications management module, Input / Output (I / O) ports, I / O components, and a power supply (not illustrated in FIG. 4).

[0150] Each of the components may directly or indirectly communicate with each other over one or more buses 440. The node 400 may be a UE or a BS that performs various functions disclosed with reference to FIGS. 1 through 3.

[0151] The transceiver 420 has a transmitter 422 (e.g., transmitting / transmission circuitry) and a receiver 424 (e.g., receiving / reception circuitry) and may be configured to transmit and / or receive time and / or frequency resource partitioning information. The transceiver 420 may be configured to transmit in different types of subframes and slots including, but not limited to, usable, non-usable, and flexibly usable subframes and slot formats. The transceiver 420 may be configured to receive data and control channels.

[0152] The node 400 may include a variety of computer-readable media. Computer-readable media may be any available media that may be accessed by the node 400 and include volatile (and / or non-volatile) media and removable (and / or non-removable) media.

[0153] The computer-readable media may include computer-storage media and communication media. Computer-storage media may include both volatile (and / or non-volatile media), and removable (and / or non-removable) media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, AI / ML module(s), or data.

[0154] Computer-storage media may include RAM, ROM, EPROM, EEPROM, flash memory (or other memory technology), CD-ROM, Digital Versatile Disks (DVD) (or other optical disk storage), magnetic cassettes, magnetic tape, magnetic disk storage (or other magnetic storage devices), etc. Computer-storage media may not include a propagated data signal. Communication media may typically embody computer-readable instructions (e.g., computer-readable instructions related to AI module(s) and / or the ML module(s)), data structures, program modules, or other data in a modulated data signal, such as a carrier wave, or other transport mechanisms and include any information delivery media.

[0155] The term “modulated data signal” may mean a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. Communication media may include wired media, such as a wired network or direct-wired connection, and wireless media, such as acoustic, RF, infrared, and other wireless media. Combinations of any of the above listed components should also be included within the scope of computer-readable media.

[0156] The memory 434 may include computer-storage media in the form of volatile and / or non-volatile memory. The memory 434 may be removable, non-removable, or a combination thereof. Example memory may include solid-state memory, hard drives, optical-disc drives, etc. As illustrated in FIG. 4, the memory 434 may store a computer-readable and / or computer-executable instructions 432 (e.g., software codes) that are configured to, when executed, cause the processor 428 to perform various functions disclosed herein, for example, with reference to FIGS. 1 through 3. Alternatively, the instructions 432 may not be directly executable by the processor 428 but may be configured to cause the node 400 (e.g., when compiled and executed) to perform various functions disclosed herein.

[0157] The processor 428 (e.g., having processing circuitry) may include an intelligent hardware device, e.g., a Central Processing Unit (CPU), a microcontroller, an ASIC, etc. The processor 428 may include memory. The processor 428 may process the data 430 and the instructions 432 received from the memory 434, and information transmitted and received via the transceiver 420, the baseband communications module, and / or the network communications module. The processor 428 may also process information to send to the transceiver 420 for transmission via the antenna 436 to the network communications module for transmission to a CN.

[0158] One or more presentation components 438 may present data indications to a person or another device. Examples of presentation components 438 may include a display device, a speaker, a printing component, a vibrating component, etc.

[0159] In view of the present disclosure, it is obvious that various techniques may be used for implementing the disclosed concepts without departing from the scope of those concepts. Moreover, while the concepts have been disclosed with specific reference to certain implementations, a person of ordinary skill in the art may recognize that changes may be made in form and detail without departing from the scope of those concepts. As such, the disclosed implementations are to be considered in all respects as illustrative and not restrictive. It should also be understood that the present disclosure is not limited to the particular implementations disclosed and many rearrangements, modifications, and substitutions are possible without departing from the scope of the present disclosure.

Claims

A User Equipment (UE) for performing a conditional Layer 1 / Layer 2 Triggered Mobility (CLTM) operation, the UE comprising:  at least one processor; and  at least one non-transitory computer-readable medium coupled to the at least one processor and storing one or more computer-executable instructions that, when executed by the at least one processor, cause the UE to:    receive, from a serving cell, a Medium Access Control (MAC) Control Element (CE) comprising a Timing Advance (TA) command indicating a TA index for a CLTM candidate cell;    store the TA index for the CLTM candidate cell in response to receiving the MAC CE;    perform a Random Access Channel (RACH)-less CLTM cell switch to the CLTM candidate cell; and    determine an actual TA value applied in the CLTM candidate cell based on the TA index and a subcarrier spacing (SCS) of an uplink transmission that occurs first in time after performing the RACH-less CLTM cell switch.The UE of claim 1, wherein the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to:  start or restart a first Time Alignment Timer (TAT) that is associated with the CLTM candidate cell in response to receiving the MAC CE; and  consider the TA index for the CLTM candidate cell as valid until the first TAT expires.The UE of claim 2, wherein the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to:  start or restart a second TAT in response to performing the RACH-less CLTM cell switch while the first TAT is running, wherein:  the second TAT is associated with a Primary Timing Advance Group (PTAG) of the CLTM candidate cell, and  the second TAT is set to a duration equal to a remaining time of the first TAT when the RACH-less CLTM cell switch is performed.The UE of claim 1, wherein:  the MAC CE further comprises a Timing Advance Group (TAG) indication field that indicates one of a plurality of TAGs configured for the CLTM candidate cell, to which the TA command is applied.The UE of claim 1, wherein:  the MAC CE further comprises a candidate configuration Identifier (ID) field that indicates a CLTM candidate configuration corresponding to the CLTM candidate cell.The UE of claim 1, wherein the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to:  receive, from the serving cell, a Radio Resource Control (RRC) parameter indicating a TA offset, wherein:  the actual TA value applied in the CLTM candidate cell is further determined based on the TA offset.A Base Station (BS) for configuring a Conditional Layer 1 / Layer 2 Triggered Mobility (CLTM) operation:  at least one processor; and  at least one non-transitory computer-readable medium coupled to the at least one processor and storing one or more computer-executable instructions that, when executed by the at least one processor, cause the BS to:    transmit, to a User Equipment (UE), a Medium Access Control (MAC) Control Element (CE) comprising a Timing Advance (TA) command indicating a TA index for a CLTM candidate cell, wherein:  the UE stores the TA index for the CLTM candidate cell in response to receiving the MAC CE,  the UE performs a Random Access Channel (RACH)-less CLTM cell switch to the CLTM candidate cell, and  the UE determines an actual TA value applied in the CLTM candidate cell based on the TA index and a subcarrier spacing (SCS) of an uplink transmission that occurs first in time after performing the RACH-less CLTM cell switch.The BS of claim 7, wherein:  the UE starts or restarts a first Time Alignment Timer (TAT) that is associated with the CLTM candidate cell in response to receiving the MAC CE, and  the UE considers the TA index for the CLTM candidate cell as valid until the first TAT expires.The BS of claim 8, wherein:  the UE starts or restarts a second TAT in response to performing the RACH-less CLTM cell switch while the first TAT is running,  the second TAT is associated with a Primary Timing Advance Group (PTAG) of the CLTM candidate cell, and  the second TAT is set to a duration equal to a remaining time of the first TAT when the RACH-less CLTM cell switch is performed.The BS of claim 7, wherein:  the MAC CE further comprises a Timing Advance Group (TAG) indication field that indicates one of a plurality of TAGs configured for the CLTM candidate cell, to which the TA command is applied.The BS of claim 7, wherein:  the MAC CE further comprises a candidate configuration Identifier (ID) field that indicates a CLTM candidate configuration corresponding to the CLTM candidate cell.The BS of claim 7, wherein the one or more computer-executable instructions, when executed by the at least one processor, further cause the BS to:  transmit, to the UE, a Radio Resource Control (RRC) parameter indicating a TA offset,  wherein the UE determines the actual TA value applied in the CLTM candidate cell further based on the TA offset.A method performed by a User Equipment (UE) for performing a conditional Layer 1 / Layer 2 Triggered Mobility (CLTM) operation, the method comprising:  receiving, from a serving cell, a Medium Access Control (MAC) Control Element (CE) comprising a Timing Advance (TA) command indicating a TA index for a CLTM candidate cell;  storing the TA index for the CLTM candidate cell in response to receiving the MAC CE;  performing a Random Access Channel (RACH)-less CLTM cell switch to the CLTM candidate cell; and  determining an actual TA value applied in the CLTM candidate cell based on the TA index and a subcarrier spacing (SCS) of an uplink transmission that occurs first in time after performing the RACH-less CLTM cell switch.