3GPP TSG-RAN WG2 Meeting #130              			                           R2-2503382
St.Julians, Malta, May. 19th – 23rd, 2025

Agenda Item:	8.6.4
Source: 	Lenovo
Title: 	CLTM Scenarios and remaining points
Document for:	Discussion and decision

Conclusion
This document attempted to develop a basic understanding of “conditional LTM” and proposed some first scenarios for RAN2 consideration. In summary, we have following observations and proposals:
Early TA delivery
Observation 1: After UE receives early TA MAC CE for CLTM candidate cell, UE performs RACH based cell switch upon the reception of LTM cell switch command without early TA value. In this case, UE needs to release the stored early TA which still impact the specification.
Proposal 1: After UE receives early TA MAC CE for CLTM candidate cell, UE performs RACHless cell switch upon the reception of LTM cell switch command without early TA value.
Proposal 2: If an LTM cell switch command is received for a C-LTM candidate, UE initiates mobility execution to the target cell. It maintains the TA value and keeps the early TA timer running for candidate cell(s) other than the target) cell.
Coexistence cases
Observation 2: It seems unnecessary to configure both CLTM candidate configuration and LTM candidate configuration for the same cell since LTM cell switch command can be used to trigger CLTM execution. But it can be up to network implementation.
Proposal 3: Simultaneous configuration of Intra-CU MCG CLTM and Intra-CU MCG LTM is supported.
Proposal 4: Simultaneous configuration of CHO and CLTM is supported.
Candidate cell/beam selection
Proposal 5: If multiple CLTM candidate cells meet the L1 (or L3) execution condition, the target cell for CLTM execution can be selected among the candidate cells for which the UE has a valid TA. If the valid TA is not available for any candidate cell, the UE can select any candidate cell.
Proposal 6: In the case of CLTM candidate cell with MIMO 2TA, UE prioritizes the beam which has valid early TA and also satisfy the execution condition.

Fast Recovery for CLTM
Proposal 7: After RLF, Intra-gNB MCG LTM failure or CLTM failure, UE can perform cell switch to a selected cell if the selected cell is configured with CLTM configuration.
Fallback from RACH-less
Proposal 8: Not to support Fallback from RACH-less CLTM CS to RACH-based CLTM CS when/ if TAT (for the target cell) expires while T304 is still running.

3GPP TSG-RAN WG2 Meeting #130	                                                                                   R2-2503411
St.Julians, Malta, May 19th – 23rd, 2025

Source:	CATT
Title:	Discussion on Conditional Intra-CU LTM
Agenda Item:    8.6.4
Document for:  Discussion and Decision

Conclusion
Based on the analysis in Section 2, our observations and proposals are summarized as follows:
Observation 1: In the CLTM evaluation, if the L1 execution condition of a candidate cell associated with an LTM-CSI-ResourceConfig-r18 which includes RSs from other candidate cells, then the RSs of those other candidate cells are evaluated. This seems unreasonable.

On CLTM TAT handling
Proposal 1: The value of ltm-TimeAlignmentTimer-r19 is determined by the source cell. Send LS about the agreement to RAN3. 

NW triggered LTM to the CLTM candidate with early TA
Proposal 2: (MAC-14) Upon receiving (Enhanced) LTM Cell switch Command MAC CE, UE performs RACH-less LTM cell switch only if the MAC CE includes a valid TA value or UE has performed UE based TA measurement to the target cell, regardless of whether CLTM candidate TAT timer is running for the target cell.

On L1 based CLTM
Proposal 3a: In the CLTM evaluation, only the RSs of the same candidate cell can be evaluated if L1 execution condition is configured for the candidate cell.
Proposal 3b: If P3a is agreed, RAN2 down-selects between the following options,
Option 1: For the LTM-CSI-ReportConfigId configured as L1 execution condition of a candidate cell, NW ensures that the associated measurement resource config could only include the RSs of the corresponding candidate cell;
Option 2: If the L1 execution condition of a candidate cell associated with an LTM-CSI-ResourceConfig-r18 which includes RSs from other candidate cells, the UE only evaluates the RSs of the same candidate cell;
Option 3: UE evaluate all the RSs of candidate cell, not the RSs associated with the L1 execution condition:
Option 3-1: LTM-CSI-ReportConfigId-r18 is configured as the execution condition, UE ignore the ltm-ResourcesForChannelMeasurement-r18 configured in the associated LTM-CSI-ReportConfig
Option 3-2: redesign the event configuration signaling structure to avoid the association between L1 execution condition and measurement resource configuration.

On target beam/cell selection of L3 based RACH-less CLTM
Proposal 4: (RRC-3) For L3 based CLTM, it’s up to UE implementation to select one of the LTM candidate configurations as the target cell if more than one candidate cells satisfy the L3 execution condition.
Proposal 5a: (MAC-10) For L3-based CLTM, it’s up to UE implementation to select the target beam. 
Proposal 5b: (MAC-10) For L3-based CLTM, UE performs RACH-less C-LTM if UE has a valid TA for the selected beam. Otherwise, UE performs RACH-based C-LTM. 

CG resource selection
Proposal 6: (MAC-12) RAN2 assumes the CG resource for RACH-less CLTM can be associated with CSI-RS directly. Send LS to RAN1 for further confirmation. 
Proposal 7: (MAC-9) For L3-based RACH-less CLTM, UE selects the CG resource associated with the selected target beam.
Proposal 8: (MAC-11) If the UE has a valid TA for a target beam but cannot determine a valid CG resource, it shall perform RACH-based CLTM to the target cell.

TCI state determination upon RACH-less CLTM execution
Proposal 9: Send LS to RAN1 to confirm whether UE needs to determine the target TCI state upon the RACH-less conditional LTM execution and indicate it to lower layer. 

On the co-existence of CLTM and other features
Proposal 10a: (MAC-13) Support the co-existence of CLTM and (e)RedCap.
Proposal 10b: (MAC-13) Support the co-existence of CLTM and CovEnh.

3GPP TSG RAN WG2#130	R2-2503455
St Julian’s, Malta, 19th - 23rd May 2025
Agenda Item:	8.6.4
Source:	Lekha Wireless Solutions
Title:	Discussion on Conditional Intra CU LTM 
Document for:	Discussion, Decision

Conclusion
In this contribution, the following proposals are made:
Beam selection and Valid CG for L3 based RACH Less Conditional LTM:
Proposal 1: UE selects a beam within the target cell where SS-RSRP > rsrp-ThresholdSSB and the beam has an associated CG occasion.
Proposal 2: UE selects the strongest available beam among those with configured CG occasions.
Proposal 3: UE reuses the beam which contributed to satisfying the L3 condition (e.g., best beam at the time of event A3/A5 triggering). 
Proposal 4: Serving gNB provides the preferred beam index(es) for CG access during C-LTM preparation.
Proposal 5: For L3 based RACH less C-LTM, Proposal 1 as the baseline due to its alignment with existing procedures. Proposal 2 to 4 as enhancements to provide robustness in diverse deployment scenarios.
Fall back mechanism in Conditional LTM:
Proposal 6: If a UE considers RACH-less Conditional LTM as ongoing but cannot obtain a valid CG resource, the UE should fall back to RACH-based LTM to complete the mobility procedure. This ensures service continuity and aligns with the robustness principles of LTM. Timer- or failure-detection-based triggers can govern this fallback.
How UE select the CG resource if the selected beam is CSI-RS?:
Proposal 7: The UE knows the CG ↔ CSI-RS beam association for candidate cells because the serving gNB pre-configures these mappings via RRC (e.g., using `spatialRelationInfo` or TCI states). When the UE selects a new beam during mobility, it automatically switches to the corresponding CG resource for seamless UL transmission.
Proposal 8: UE selects the CG resource whose spatial filter matches the best DL CSI-RS beam under the assumption of UL/DL beam correspondence is valid.
Coexistence between CLTM and (e)RedCap, CovEnh:
Proposal 9: CLTM can be applied to (e)RedCap UEs with minimal tailoring, e.g., using fewer measurement events, relaxed filtering, and pre-indicated beams for CG.
Proposal 10:The LTM procedure's flexibility allows adaptation to RedCap’s reduced complexity and CovEnh's repetition-oriented structure. Conditional triggering reduces control overhead, aligns with power/performance limitations, and offers robust handover in weak coverage scenarios. 
Proposal 11: Supporting coexistence between Rel-19 Conditional LTM and both (e)RedCap and CovEnh. 

4 

3GPP TSG-RAN WG2 Meeting #130	R2-2503470
St.Julians, Malta, 19th – 23rd May 2025

Agenda Item:	8.6.4
Source:	MediaTek Inc.
Title:	Further discussion on Conditional LTM
Document for:	Discussion, Decision

Conclusion
In this contribution, the following proposals are made:
2.1 Leftover issues for target beam selection in L1 based RACH-less CLTM
Proposal 1: RAN2 discuss the potential solutions if the triggered beam is NOT associated with any CG resources:
Option 1: The target beam is always the triggered beam. If the triggered beam is not associated with any CG resources, the UE performs CBRA using the triggered beam to send a preamble to the network. 
Option2: Target beam may not be triggered beam. If the triggered beam is not associated with any CG resources and UE has valid TA, UE selects a good beam with CG resource to send the first UL message without RACH. 
Option3: If the triggered beam is not associated with any CG resources and UE has valid TA, UE does not perform C-LTM cell switch and wait for the next triggered beam with CG resource.
Proposal 2: RAN2 to discuss and confirm whether the UE is allowed to use any CG resource and associated target beam to send the first UL message without RACH, if the TA of the target cell is valid (via early UL sync). If yes, it means the network will reserve all CG resources of all candidate cells for one UE throughout the LTM and subsequent LTMs.
Proposal 3: If the answer to Proposal 2 is No, RAN2 should further discuss potential solutions for dynamic resource allocation and UE target beam selection. The use of the R18 Early TCI activation/deactivation procedure or TA MAC CE with UL grant can be considered.

2.2 Target beam selection of L3 based C-LTM
Proposal 4:  For L3 based C-LTM, it is up to UE implementation to select the target beam.

2.3 Target beam selection of RACH-based C-LTM
Proposal 5: For CFRA based C-LTM, RAN2 to discuss the target beam selection after RACH:
Option1: The UE continues to use the CFRA SSB until the next TCI state activation indication.
Option2: Network indicates the target beam (TCI States Activation) to UE right after RACH procedure is complete.
Option 3a: The UE selects the previous triggered beam (before RACH) as the target beam. (This beam may not be associated with CG resource)
Option 3b: UE selects the current best beam of the new serving cell as the target beam (This beam may not be associated with CG resource)
Proposal 6: For CBRA based C-LTM, UE can select the triggered beam for random access procedure.

2.4 Candidate TA maintenance and refresh
Proposal 7: For PDCCH-ordered early TA acquisition, if the candidate TA timer expires before the conditional LTM cell switch is triggered, it is up to the network to initiate a TA refresh by sending another PDCCH order to the UE.

2.5 Co-existence on CLTM and MIMO 2TA
Proposal 8: RAN2 to discuss the scenario for a 2TA candidate cell when the target cell have valid TA but the target beam does not：
Option 1: The UE selects the triggered beam as the target beam and performs RACH-based CLTM.
Option2: The UE selects another beam with valid TA to perform RACH-less CLTM (FFS the condition to choose another beam).
Proposal 9: For CLTM, UE based TA measurement cannot be configured if candidate cell is configured with MIMO 2TA.

2.6 CLTM and LTM co-existence with TA acquisition (MAC-14)
Proposal 10: When the UE receives the LTM CSC MAC CE while the event evaluation for CLTM is ongoing, the UE should prioritize TA acquisition as follows:
The new TA indicated in the LTM CSC MAC CE.
The valid TA with a running CLTM TAT.
RACH-based LTM.

2.7 UE capability issue (ltm-RACH-LessCG-r18)
Proposal 11: Add the condition “at last support one of cltm-EarlyTA-Indication-r19 or ue-TA-Measurement-r18” to determine whether UE support RACH-less conditional LTM. The TP to the UE capability running CR is adopted.

3GPP TSG-RAN WG2 Meeting #130	                                     R2-2503488
St.Julians, Malta, May 19th – 23rd, 2025

Agenda Item:	8.6.4
Source: 	OPPO
Title:  	Open issues for conditional LTM 
Document for:	Discussion and Decision

Conclusion
Based on the discussion above, we have the following proposals:
Proposal 1	For L3 based RACH-less CLTM, UE considers the CG resource as valid if an SSB corresponding to the configured UL grant has the same SSB index as the selected SSB.
Proposal 2	For L3 based RACH-less CLTM, the target cell is the candidate cell fulfilling the L3 execution condition.
Proposal 3	If there are multiple candidate cells fulfil the L3 execution condition, it can leave for UE implementation to choose one as the target cell.
Proposal 4	For L3 based RACH-less CLTM, the selected beam is the beam fulfilling the threshold.
Proposal 5	If there are multiple beams fulfil the threshold, it can leave for UE implementation to choose one as the selected beam.
Proposal 6	UE can fallback from RACH-less CLTM to RACH-based CLTM if there is no valid CG resource.
Proposal 7	Same as Rel-18 intra-CU LTM, Rel-19 intra-CU CLTM could coexist with CovE, (e)RedCap, while couldn’t coexist with NRU.
Proposal 8	Upon reception of LTM cell switch command MAC CE indicating a CLTM candidate configuration index, CLTM TAT for target cell is not stopped if it is running and the PTAG TAT of the target cell is started.
Proposal 9	Before any CLTM execution condition is satisfied, upon reception of HO command or LTM cell switch command MAC CE, the UE executes the HO procedure or LTM cell switch procedure, regardless of any previously received CLTM configuration.
Proposal 10	CLTM and L3 HO coexistence is supported.
Proposal 11	CLTM and DAPS coexistence is not supported.

3GPP TSG-RAN WG2 Meeting #130	R2-2503533
St.Julians, Malta, May 19th – 23rd , 2025
 							    

Source: 	Xiaomi
Title:  	Discussion on conditional LTM
Agenda Item:	8.6.4	
Document for:	Discussion and Decision

Conclusions
According to the analysis given above, we have the following observations and proposals:
2.1	Discussion for RRC/MAC open issue list: 
2.1.1	(RRC-3 and MAC-10) Target cell and beam selection for CLTM execution 
Proposal 1: (RRC-3) When multiple candidate cells satisfy the L3 CLTM condition, it is up to UE implementation to select a candidate cell and perform CLTM.
Proposal 2: (MAC-10) For L3 based CLTM, it is up to UE implementation to select a beam and perform C-LTM.
2.1.2	(MAC-9 and MAC-11) CG resource selection for RACH-less CLTM
Proposal 3: (MAC-9) If the selected target beam is associated with valid CG resource, the UE selects the CG resource associated with the selected target beam for CG based RACH-less CLTM.
Proposal 4: (MAC-11) If the selected target beam for CLTM execution is not associated with valid CG resource, the UE performs RACH-based CLTM.
2.1.3	 Open issue: MAC-14
Proposal 5: (MAC-14) The valid candidate TA stored by UE cannot be used for MAC CE triggered LTM.

2.2	Other open issues:
2.2.1	CLTM TA
Proposal 6: When the number of CLTM TAs that the UE stores is up to cltm-EarlyTA-Indication-r19, to adding a new CLTM TA to be maintained by the UE, the following options can be considered.
Option 1: (Network-based method) Before sending the LTM Candidate Timing Advance Command to add a new CLTM TA, the network can trigger one CLTM TA release by setting the TAC field to FFF in LTM Candidate Timing Advance Command MAC CE. 
Option 2: (UE-based method) Upon receiving an LTM Candidate Timing Advance Command MAC CE for adding a new CLTM TA, the UE shall release the oldest CLTM TA and stop associated CLTM TAT.
Proposal 7: For PDCCH-ordered early TA acquisition, if the candidate TAT expires before CLTM trigger, it is up to network implementation to trigger TA refresh by sending another PDCCH order. 

2.2.2 The coexistence of CLTM and other mobility cases
Proposal 8: The coexistence of CLTM and L3 HO is supported in Rel-19.
Observation 1: For the coexistence of LTM/CLTM and CHO, the agreement in RAN2 #127 (Rel-19 MOB) and the agreement in RAN2#128(Rel-18 MOB) are in conflict:
The agreement in RAN2 #127 (Rel-19 MOB): The RRCReconfiguration message to execute an L3 mobility (HO or CHO) procedure may reconfigure inter-CU LTM configurations.
The agreement in RAN2#128(Rel-18 MOB): Clarify in RRC that the conditional reconfiguration cannot include the ltm-config.
Proposal 9: The coexistence of CLTM and CHO is supported in Rel-19 and upon CHO execution, the UE shall stop the CLTM evaluation for all CLTM candidate cells.
Proposal 10: The coexistence of CLTM and DAPS HO is not supported.
2.2.3	 One issue for CLTM with Rel-18 MIMO 2TA
Proposal 11: For CLTM, when 2TAGs are configured, if the UE has no valid TA for the TAG id of the selected candidate beam, the UE performs RACH-based CLTM.

3GPP TSG-RAN WG2 Meeting #130	R2-2503555
St.Julians, Malta, May 19th – 23rd, 2025
Agenda Item:	8.6.4
Source: 	Fujitsu
Title:	Discussion on conditional Intra-CU LTM
Document for:	Discussion and Decision

Conclusion
This document discussed the remaining open issues for Intra-CU CLTM and made the following proposals:
Coexistence with network triggered LTM cell switch 
Proposal 1: When the LTM CSC MAC CE indicating a CLTM candidate and its TA to FFF, the stored TA provided by the early TAC MAC CE can be used if the corresponding early TAT is running. 
Proposal 2: Same UE behaviours will apply to the PTAT, early TA timers for the target cell and candidate cells if the TA provided by the early TAC MAC CE is used for the LTM cell switch triggered by the network.
L3-based CLTM
Proposal 3: Beam information is indicated in the early TAC MAC CE to support L3 based RACH-less CLTM.
Proposal 3bis: Beam information in the early TAC MAC CE takes LTM CSC MAC CE as baseline. 
Proposal 4: RAN2 to discuss whether to include CG information in the early TAC MAC CE. 
CLTM cell switch execution when both L1 and L3 conditions are fulfilled
Proposal 5: RAN2 to discuss whether CLTM triggered by L1 conditions or by L3 conditions should be prioritized or it is up to UE implementation when L1 execution condition for one CLTM candidate cell is fulfilled and L3 execution conditions for another CLTM candidate cell are fulfilled at the same time. 

3GPP TSG-RAN WG2 Meeting #130		R2-2503619
St. Julian’s, Malta, 19th – 23rd May 2025
Source:	vivo
Title:		Discussion on conditional LTM
Agenda Item:		8.6.4
Document for:	Discussion and Decision

Conclusion
In this contribution, we discussed remaining issues on CLTM, including both RRC and MAC open issues.
We have the following Observations and Proposals: 
For L3-based RACH-less CLTM:
Proposal 1: (RRC-3) For L3 based CLTM, when multiple candidate cells satisfy the CLTM execution conditions, it is up to UE implementation to select one of them to be the target cell.
Proposal 2: (MAC-9) If there is at least one beam associated with the configured uplink grant with RSRP above configured RSRP threshold, the concerned beam is selected and CG-based RACH-less CLTM is performed.
Proposal 3: (MAC-9) If there is no beam associated with the configured uplink grant with RSRP above configured RSRP threshold, RACH-based CLTM is performed.
For Max number of maintained TA values
Proposal 4: RAN2 discusses how to handle the case where the maintained TA value number has reached the upper capability limit but an LTM Candidate Timing Advance Command MAC CE for a candidate cell whose TAT is not running is received from the network.
For Co-existence of LTM and CLTM
Proposal 5: (MAC-14) If a UE receives an (Enhanced) LTM Cell Switch Command MAC CE without valid TA and CFRA resource while the CLTM candidate TAT timer for the target cell is running, it shall perform RACH-less LTM.
Proposal 6: (MAC-14) If an LTM Cell switch Command MAC CE with valid TA is received, UE shall store the TA value for the target cell and start or restart the CLTM TAT of the target cell.
For RACH-Less procedure with no CG
Observation 1: The UE’s behaviour is not clear when RACH-less CLTM begins but the transmission on CG occasion fails.
Proposal 7: If UE performs RACH-LESS CLTM but transmission on following CG fails, the UE continue to perform RACH-LESS procedure if the TAT is still running at the next available CG occasion, otherwise the ongoing CLTM is considered failure.
For Co-existence of CLTM and (e)RedCap/ CovEn
Proposal 8: (MAC-13) Co-existence of Rel-19 CLTM and (e)RedCap is supported.
Proposal 9: (MAC-13) Co-existence of Rel-19 CLTM and coverage enhancement is supported.

3GPP TSG-RAN WG2 Meeting #130	R2-2503683
St.Julians, Malta, May 19th – 23rd, 2025

Agenda item:	8.6.4
Source: 	China Telecom
Title:	Discussion on remaining issues of CLTM
WID/SID:	NR_Mob_Ph4-Core
Document for:	Discussion and Decision

Conclusion
In this contribution, we discuss the remaining issues on CLTM. We kindly ask RAN2 to consider the corresponding proposals listed as below.
Proposal 1: For L3 based C-LTM events, the C-LTM execution is triggered when at least one candidate cell fulfills the C-LTM event condition. When multiple candidate cells satisfy the C-LTM condition, the candidate cell with valid TA shall be prioritized. 
Proposal 2: If there are multiple candidate cells met the condition with valid TAs or all the candidate cells met the condition don’t have valid TA, it is up to the UE implementation to select a target cell among them.
Proposal 3: If there are different candidate cells met the L1 or L3 based conditions, the selection of L1 based or L3 based candidate cell as a target cell could be up to UE implementation.
Proposal 4: Regarding L3-based RACH-less CLTM, the NW could configure a RSRP threshold for beam selection, similar to cg-RRC-RSRP-ThresholdSSB.
Proposal 5: If there are multiple beams meet the thresholds, it is up to UE implementation to select a beam among them. 

3GPP TSG-RAN-WG2 Meeting #130	R2-2503746
St.Julians, Malta, May 19th – 23rd, 2025
Agenda item	:		8.6.4
Source	: 	Sharp
Title	: 	Discussion on issues for supporting conditional LTM
Document for	:	Discussion and Decision

Conclusion
Proposal 1. If there are more than one LTM candidate cell fulfil the LTM cell switch execution, the RRC layer selects one of the triggered cells as the selected cell for conditional LTM execution. And this selection is performed by the UE implementation.
Proposal 2. For L3 based RACH-less LTM, it is up to UE implementation to select the target beam.

3GPP TSG-RAN WG2 Meeting #130		R2-2503773  
Malta, May 19th – 23rd, 2025
Source:	Baicells
Title:		Discussion on Conditional intra-CU LTM remaining issues
Agenda Item:		8.6.4
Document for:	Discussion and Decision

Conclusion
In this contribution, we discussed the issues related to Conditional LTM. We have the following Proposal:
Proposal1: If the CLTM cell switching is triggered by the L3 execution conditions, the beam used by UE for accessing the cell can have the following options:
Option A: UE selects the beam associated with an activated TCI state as the target beam for accessing the target candidate cell.
Option B: If there is no activated TCI state available, UE selects the best beam as the target beam for accessing the target candidate cell.

3GPP TSG-RAN WG2 #130                                             	    R2-2503803                                                             
St. Julian’s, Malta, May 19th – 23rd, 2025                                                 	     
Agenda item:	   8.6.4
Source: 		Qualcomm Incorporated
Title: 	Discussion on conditional intra-CU LTM
Document for:	Discussion
1	

Conclusion
This contribution discussed aspects related to conditional intra-gNB LTM. The following observations and proposals have been made:
Observation 1: Due to the independent operations between CLTM TA timer counting and CLTM execution condition evaluation, UE could run into a situation where PTAG TA timer, which is based on the remaining CLTM TA timer value, expires before UE receives TA command MAC CE from the target cell. And the recovery procedure upon TA expiry would diminish the latency improvement by RACH-less CLTM operation.
Proposal 1: RAN2 to discuss how to avoid unnecessary TA timer expiry upon RACH-less CLTM when the remaining CLTM TA timer value is not long enough for the target cell to send TA command MAC CE and to adopt one of options below. 
Option 1: Extend TA timer for PTAG by a timer offset
This timer offset value can be configured by RRC
FFS whether this timer offset is applied only when TA timer for PTAG is below threshold.
Option 2: Determine TA timer for PTAG as max(TA timer for PTAG, minimum TA timer value)
The minimum TA timer value can be configured by RRC.
Observation 2: Unlike Rel-18 LTM, there could be more than one candidate cell that are indicated by serving cell to monitor CG resources for potential CLTM execution by UE and they have to keep monitoring CG resources until they receive UL signal or another indication from original or new serving cell. Then it would be beneficial to utilize those CG resources for RACH-less CLTM fast recovery.
Proposal 2: RAN2 agree to support RACH-less CLTM recovery for Rel-19 intra-CU CLTM when the following conditions are met:
The selected cell is one of CLTM candidate cell AND
The selected CLTM candidate cell has configured CG resource AND
UE has a valid TA for the selected CLTM candidate cell by either (i) TA from TA MAC CE for which TA timer is running or (ii) UE-measured TA.
Observation 3: For the beam selection in L3-based CLTM, CHO procedure can be used a baseline.
Proposal 3: After detecting L3 event condition(s) fulfilled, the SSB selection for the target candidate cell is up to UE implementation, and RRC informs MAC of the target candidate cell ID and the SSB index.
Observation 4: CG resource reservations from multiple target cells cany lead to significant inefficiency in time/frequency resources due to a large number of resource reservations.
Proposal 4: For RACH-less CLTM, introduce an “early target cell notification” signaling procedure where UE informs the serving cell of potential target CLTM cell(s) and beam(s).
Observation 5: For successful RACH-less CLTM, serving cell may have to trigger PDCCH ordered RACH procedures for all potential target candidate cells, which could become huge overhead and interruptions in data transmission and reception at UE.
Proposal 5: RAN2 to support the candidate cell TA group where UE can assume that a TA value from one candidate cell (acquired either from new TA MAC CE or UE-measured TA) can be applied to all other candidate cells in that TA group.
Observation 6: The TA validation procedure for CG-SDT can be used as a reference for the TA maintenance procedure in CLTM execution.
Proposal 6: RAN2 to agree the following as baseline for TA maintenance at UE:
The TA timer value and RSRP change threshold are configured in RRC (which can be candidate cell specific or candidate cell group specific).
When UE successfully receives the new TA MAC CE or measures UE-measured TA
Start the TA timer 
Store the RSRP value of the candidate beam of the candidate cell
The TA value is considered to be valid when the following conditions are true:
The RSRP change between the stored value and the current value has not increased/decreased by more than RSRP threshold; AND
The TA timer is running.

TDoc file reading error

3GPP TSG-RAN WG2 #130	R2-2503860
St. Julians, Malta, May 19th – 23rd, 2025						    	 

Agenda item:	8.6.4
Source: 	Ericsson
Title:  	Open issues for Conditional LTM
Document for:	Discussion and Decision

Conclusion
In the previous sections we made the following observations: 
Observation 1	Reserving network resource in advance for an LTM candidate configuration is not efficient from a resource usage and efficiency perspective.
Observation 2	Due to the scarcity of available resources, network may be able to configure only a few LTM candidate configurations.
Observation 3	The use for a TA value to another candidate cell after a cell switch execution is limited since the network does not know of this TA value.
Observation 4	If the new serving cell does now know which TA values are kept at the UE, the new serving cell will assume that no TA are available at the UE and the early UL synchronization procedure needs to be re-triggered (or done from scratch).
Observation 5	If the new serving cell knows which TA values and TAT for other LTM candidate cells the UE has kept, the early UL synchronization procedure does not need to be re-triggered again, and this saves network resources and signaling.
Observation 6	When the UE has executed CLTM, the target DU needs to be aware if the UE has performed L2 reset or not.
Observation 7	Letting the CU informing the DUs pro-actively would mean the target DU has information about if a L2 reset has been performed or not.
Observation 8	If value “FFF” is included in the LTM cell switch MAC CE and the UE has a valid TA, it would be reasonable to allow the UE to still perform a RACH-less LTM cell switch procedure. This is also in line with the behavior we have in Rel-18 for the case on when the UE is configured with UE-based TA measurements.

Based on the discussion in the previous sections we propose the following:
Proposal 1	The network can activate or deactivate a CG which is part of an (conditional) LTM candidate configuration.
Proposal 2	The UE informs the new serving cell, within the RRCReconfigurationComplete message, which TA values and TAT for other LTM candidate cells the UE has kept.
Proposal 3	For CLTM, the CU shall update the DU(s) of other LTM candidates about the current serving cell for a UE at every LTM cell switch to allow the DU for the LTM candidate to understand whether an L2 reset needs to be done or not. Send an LS to RAN3 to inform them.
Proposal 4	If the network sends a LTM cell switch MAC CE with value “FFF” for the TA value, and the UE has a valid TA (either because previously send by the network or because of UE-based TA), the UE performs a RACH-less LTM cell switch procedure.

3GPP TSG-RAN WG2 #130	R2-2503931
St. Julian's, Malta, 19th – 23rd May 2025
                                               
Source:		NEC
Agenda item:		8.6.4	Conditional intra-CU LTM
Title:	Remaining Open Issues for CLTM
Document for:		Discussion and decision

Conclusion
In this paper, we discussion on the remaining issues of RACH-less CLTM, and have the following proposals:
Proposal 1. In case CG resource is only associated with SSB, if the beam meeting the execution condition is CSI-RS, the UE determines whether a CG resource is valid based on the SSB associated with the CSI-RS.
Proposal 2. In case of timeAlignmentTimer associated with PTAG expiry during RACH-less LTM cell switch, discuss the following options:
Opt1) the UE terminates the CLTM cell switch procedure
Opt2) the UE fallbacks from RACH-less LTM to RACH-based C-LTM 
Opt3) the UE does nothing
Proposal 3. Support co-existence between CLTM and (e)RedCap and CovEnh without additional specification effort.

3GPP TSG-RAN WG2 #130	R2-2503956
St. Julian’s, Malta, May 19th – 23rd, 2025	

Agenda Item:	8.6.4
Source: 	ITRI
Title: 	Discussion on conditional LTM
Document for:	Discussion

Conclusion 
In this contribution, the following observations and proposal are made:
Observation 1: The UE can be simultaneously configured with LTM candidate configurations and CLTM candidate configurations.
Observation 2: Different from the L3-based handover, the LTM cell switch may be triggered based on L1 measurements, in which case it is not as robust as the L3-based handover.
Observation 3: The CLTM cell switch is triggered upon CLTM execution condition fulfilment.
Proposal 1: How to handle the CLTM execution condition evaluation during the LTM cell switch is an essential issue needed to be discussed.

TDoc file reading error

TDoc file reading error

3GPP TSG-RAN WG2 Meeting #130	R2-2504049
St. Julien, Malta, 19th – 23rd May 2025	

1.	

Conclusion
In this paper, we have made the following observations and proposals:
RACH-less CLTM execution procedure
Proposal 1. For L1 based RACH-less CLTM, the UE performs RACH-based CLTM cell switch if CG is not associated with the triggered beam.
Proposal 2. For L3 based CLTM, it is up to UE implementation to select a candidate cell when multiple candidate cells fulfill an L3 execution condition.
Proposal 3. For L3 based CLTM, the UE selects a beam above the threshold if an L3 execution condition is met and if a valid TA for the candidate has been obtained. Then, the UE transmits the first UL signal on the selected beam.
Proposal 4. For L3 based CLTM, the UE performs RACH-based CLTM if there is no beam above the threshold for the candidate fulfilling the L3 execution condition or if there is no valid configured uplink grant.
Proposal 5. For beam selection in L3 based RACH-less CLTM, it is up to UE implementation to select a beam when multiple beams are above the threshold.

Coexistence related issues
Proposal 6. Support coexistence between Rel-19 CLTM and (e)RedCap.
Proposal 7. Support coexistence between Rel-19 CLTM and CovEnh.
Proposal 8. Do not support coexistence between Rel-19 CLTM and DAPS.
Proposal 9. Support coexistence between Rel-19 CLTM and L3 HO (including both the network triggered L3 HO and CHO), and follow the principle of the coexistence between Rel-19 inter-CU LTM and L3 HO. 
Proposal 10. It is up to network implementation whether to simultaneously configure CLTM and CHO for the same candidate cell.

4.	

3GPP TSG-RAN WG2 Meeting #130	R2-2504146
St. Julian's, Malta, 19 - 23 May 2025
Agenda Item:	8.6.4
Source:	Huawei, HiSilicon
Title:	Intra-CU conditional LTM
Document for: Discussion and Decision

Conclusion
This contribution makes the following proposals:
CG-based RACH-less cell switch
Proposal 1: If the L3 execution condition is met, the UE can only select beams above a threshold (FFS whether to reuse an existing threshold or define a new one).
Proposal 2a: If the C-LTM execution condition is met and the UE has a valid TA for the associated candidate cell, to select a beam, the UE prioritizes beams that have associated CG occasions.
Proposal 2b: If no beam with an associated CG occasion meets the L1-based C-LTM execution condition or is above the beam selection threshold (for L3-based C-LTM execution), the UE performs RACH-based LTM cell switch.
Proposal 3: For CG-based RACH-less cell switch, if separate TCI mode is used, the UE indicates a suitable DL TCI state in the initial UL transmission (details FFS).
TA delivery and maintenance
Proposal 4: For LTM candidates with MIMO two TAs, the UE should maintain separate TA values with individual TA timers, provided that the network supplies these two values.
Proposal 5: If the UE selects a beam without a valid TA, it should perform the RACH procedure for the MIMO two-TA scenario of the candidate cell.
Proposal 6: The source DU should maintain the C-LTM TAT and be capable of recognizing when the TAT has expired.
Proposal 7: The source cell should transmit both the TA values and the corresponding remaining time of the C-LTM TATs for the candidate cells to the target cell. This action impacts RAN3.
Proposal 8: We should inform RAN3 that the source cell needs to transmit the remaining time of the C-LTM TAT to the target cell.
4	

3GPP RAN WG2 Meeting #130 	R2-2504180
St.Julians, Malta,  May 19th – 23rd , 2025	

Agenda Item:	8.6.4
Source:	InterDigital, Inc.
Title:	Conditional LTM.
Document for:	Discussion

Conclusion
In this paper we make some suggestions on conditional LTM as follows:

Proposal 1: A condition may be configured to trigger RA on a target cell for TA acquisition.

Proposal 2: For conditional trigger used for performing RACH for UL sync, RAR containing TA is received from the target. 

Proposal 3: RACH-less conditional LTM is executed only if the condition is met AND the UE has a valid TA.

Proposal 4: It is up to the network to configure a separate RACH-based conditional LTM, if necessary, for the same candidate (i.e. no dual RACH-less/RACH-based LTM for the same conditional event).

Proposal 5: CG can be considered as valid for the duration of TA validity.

Proposal 6: Discuss which of the following CG validity options for UE based TA measurement need to be supported:
CG can always be considered as valid, if configured.
CG can be considered as valid after dedicated SR transmission to target (at least for the case of UE based TA measurement)
UE reports TA measurement completion to the source, to enable the CG. 

3GPP RAN WG2 Meeting #130	R2-2504269
St.Julians, Malta May 19th – 23rd, 2025             
Agenda Item:	8.6.4
Source:	Ofinno
Title:	Discussion on open issues of CLTM
Document for:	Discussion, Decision                        

Conclusions
The contribution discussed aspects related to open issues for CLTM. The following observations and proposals are made:
For identified open issues:
Proposal 1: (RRC-3) When more than one CLTM triggered candidate cells exist, a UE selects a candidate cell associated with L3 execution condition.
Observation 1: (MAC-14) If TA of a candidate cell is valid, the LTM cell switch command MAC CE includes the TA value (i.e., Timing Advance Command field is not set as FFF).
Observation 2: (MAC-14) If TA of a candidate cell is not valid, the LTM cell switch command MAC CE does not include the TA value (i.e., Timing Advance Command field is set as FFF).
Proposal 2: (MAC-14) If UE receives LTM cell switch command MAC CE for LTM to a candidate cell while TA timer for the candidate cell is running, the UE uses the TA value indicated in the LTM cell switch command MAC CE and not the TA value received prior to receiving the LTM cell switch command MAC CE.
Proposal 3: (MAC-14) TA timer for candidate cell is continued (not stopped) when MAC reset is performed due to a reconfiguration with sync procedure.
Proposal 4: (MAC-14) Stop TA timer or a candidate cell when the candidate cell configuration corresponding to the CLTM candidate cell is released.
For other open issues:
Proposal 5: RAN2 to discuss whether a UE executing CLTM includes a CLTM indication within the RRCReconfigurationComplete message.
Proposal 6: UE resumes CLTM evaluation after successfully recovery from MCG failure based on one of the following options:
Option 1: resume CLTM evaluation if RRC reconfiguration for MCG is received while T316 is running;
Option 2: executing CLTM only when timer T316 is not running.
Observation 3: a CG resource of a candidate cell for CLTM is wasted until the UE execute the LTM cell switch procedure for the candidate cell.
Proposal 7: RAN2 discuss dynamic management of CG resource of candidate cell for CLTM.
Proposal 8: LTM Candidate Timing Advance Command MAC CE to include more than one TA values.  
Proposal 9: After transmitting RA preamble for early uplink sync, UE waits for a duration of time to receive the MAC CE. The duration of time can be RRC configured.

3GPP TSG-RAN WG2 Meeting #130	R2-2504283
St Julian’s, Malta, 19 – 23 May 2025		

Agenda item:	8.6.4
Source:	Nokia
Title:	Discussion on conditional LTM
WID/SID:	NR_Mob_Ph4-Core - Release 19
Document for:	Discussion and Decision
1	

Conclusion
This document has made the following observations:
Observation 1: In FR2, after TCI state activation for at least one candidate cell, RAN4 Rel-18 L1 measurement requirements do not apply for candidate cells without active TCI states. RAN4 has agreed to follow such approach in Rel-19 for CLTM as well.
Observation 2: Due to the lack of L1 measurement requirements, it is unclear whether and how the UE will continue L1-based condition evaluation for candidate cells without active TCI states.
Observation 3: TAT-based validation does not consider the actual channel condition between the UE and the candidate cell.
Observation 4: Current specification text mandates the UE to stop and restart CLTM condition evaluation for all the candidate cells, even though nothing was signalled from the NW. 
Observation 5: Upon a conditional cell switch, the TA and the corresponding TAT of the previous serving cell are not maintained, potentially leading to an unnecessary random access procedure, in case that cell is a CLTM candidate.
Observation 6: Autonomous UE’s decision on cell switch causes uncertainty at NW side with regards to timing of the cell switch and consequent preparation for UE admission.
Observation 7: Lack of any cell switch indication to the NW leads to inflexibility in resource management at the NW side.
Observation 8: Early signalling with the source cell prior to cell switching can allow to mimic NW behaviour from Rel-18 LTM with regards to how candidate target cell is informed about cell switch.
Observation 9: Early signalling with the source cell prior to cell switching would be risky as it would need to be performed in potentially very bad radio conditions.
Observation 10: Early indication to the target cell before switching can allow to save PUSCH (CG) resources of target cell to be wasted or kept reserved for too long.
Observation 11: For CSI-RS-based TCI states and RACH-less configured grant-based cell switch, allocating separate configured grants for each CSI-RS may increase network overhead.
Observation 12: Considering the procedural text in the current RRC CR, in case more than one LTM candidate configuration has triggered the LTM procedure, UE would select one of the LTM candidate configurations and execute CLTM towards it. 
Observation 13: configuring CLTM candidate target cell to be also CHO candidate target cell for the same UE requires further discussion, since both features aim to provide robustness gains. 
And proposed the following:
Proposal 1: In FR2, after TCI state activation for a candidate cell, the UE shall stop L1 based condition evaluation for candidate cells without active TCI states.
Proposal 2: When CLTM is configured, for the maintenance of the TA value a maintenance method similar to CG-SDT, i.e., based both on a TAT and measurement-based validation, can be followed.  
Proposal 3: In case CLTM is configured along with UE based TA estimation for given candidate cell(s), RAN2 to confirm that the TA information, which is obtained over the LTM Candidate Timing Advance Command MAC CE for the same candidate cell(s), if valid, will take precedence over UE estimated TA during a CLTM cell switch.
Proposal 4: In case of CLTM cell switch, if the TA provided by the network over the new candidate TAC MAC CE becomes invalid, or set as “FFF”, or no new MAC CE received, if UE is configured with UE based TA estimation and UE has successfully measured the TA, UE can perform RACH-less cell switch.
Proposal 5: UE stops/restarts evaluation only for the candidate cells for which the CLTM execution conditions were updated. For other candidate cells, UE continues evaluation, i.e., UE does not restart the TTT. 
Proposal 6: To allow the UE to use the available TA for a subsequent conditional cell switch, one of the following solutions should be adopted:
Alt. 1: Upon cell switch, the UE stores the TA of the previous serving cell as the TA of the corresponding candidate configuration and starts the corresponding candidate TAT with the remaining time of the TAT of the PTAG of previous serving cell.
Alt. 2: The UE always maintains the TA and corresponding TAT of the candidate configuration corresponding to the serving cell by duplicating the TA and the status of the corresponding TAT of the serving cell.
Proposal 7: RAN2 to decide whether UE shall inform the serving cell or the target cell about the switch before CLTM execution. For example, the following could be considered:
if it is decided that UE informs serving cell about cell switch, it could use:
either PUSCH-based communication e.g., new MAC CE
or PUCCH-based communication e.g., new type of CSI
if it is decided that UE informs target cell about cell switch, it could use:
either PRACH-based communication
or PUCCH-based communication e.g., SRI
Proposal 8: For RACH-less configured grant-based cell switch, when the CandidateTCI-State or CandidateTCI-UL-State indicated by the Cell Switch Command is associated with a CSI-RS, the UE can determine the configured grant based on the SS/PBCH block that is QCLed with the CSI-RS, following the same approach as in Rel-18.
Proposal 9: When conditional cell switch execution conditions for multiple candidate cells have been triggered, the UE should trigger the cell switch to a candidate cell for which Early synchronization steps are completed.
Proposal 10: Upon reception of CSC with TAC equal to “FFF” and if the UE has already acquired a TA value over an LTM Candidate Timing Advance Command MAC CE whose TAT is still running, the UE uses the TA value for RACH-less cell switch and starts the serving cell TAT using the remaining time of the LTM candidate TAT of the target candidate configuration.
Proposal 11: Upon reception of CSC with TAC equal to “FFF”, if no valid network-provided TA is available and the UE is configured with UE-measured TA, UE can use its own TA estimate for LTM execution. 
Proposal 12: Follow similar principle as Rel. 18 LTM, CLTM and CHO can be configured independently for different candidate cells. 
Proposal 13: RAN2 to discuss if co-existence of CHO and CLTM for the same candidate target cell is supported. 
Proposal 14. Support coexistence of Rel-19 CLTM with (e)RedCap and CovEnh.
4	References 
[1]	[POST128][107][MOB] RRC CR for LTM and CLTM (Ericsson), RAN2#128, Orlando, USA, November 18-22, 2024.

3GPP TSG-RAN WG2 Meeting #R2-130		        R2-2504329      St Julians, Malta, May 19-23, 2025	

Agenda Item:	8.6.4
Source: 	Rakuten 
Title:  	Remaining issues of Conditional LTM 

WID/SID:           NR_Mob_Ph4-Core- Release 19

Document for:	Discussion, Decision

Conclusion
We have the following proposals: 
Proposal 1	RAR-based TA acquisition directly from target gNB-DU is supported for conditional LTM.RAR-based TA acquisition directly from target gNB-DU is supported for conditional LTM.
Proposal 2	Delivery of target gNB-DU RAR to the UE via the serving gNB-DU is supported.
Proposal 3	Conditional execution i.e triggered based on an execution condition, of the following is supported for both L1 measurements based CLTM and L3 measurements based CLTM
Proposal 4	UE informs the target gNB-DU of the target cell configuration index sent over RRC, after a successful CLTM cell switch.
Proposal 5	RAN2 discusses and agrees a way forward CLTM handling of a mTRP UE.

3GPP TSG-RAN WG2 Meeting #130	R2-2504390
St.Julians, Malta,  May 19th – 23rd , 2025
Agenda item:	8.6.4
Source:	CMCC
Title:	Discussion on Conditional LTM
Document for:	Discussion, Decision

Conclusion
In this contribution, we discuss inter-CU LTM related issue. Following are the proposals and observations made in this contribution:
Observations:
Observation 1: intra-CU LTM can be used in DC and non-DC scenario.
Observation 2: Network triggered L3 HO, CHO and network triggered PScell change (SN change/SN modification) can be configured with intra-CU LTM, while the coexistence of LTM and DAPS HO is not supported in Rel-18.
Observation 3: If L3 HO and LTM almost triggered simultaneously, DU may refuse CU’s UE CONTEXT MODIFICATION REQUEST message for mobility, which means the priority of LTM is higher than L3 HO.
Proposals:
Proposal 1: Conditional LTM can be supported for PCell change in non-CA scenario and for PCell and SCell(s)  change in CA scenario.
Proposal 2: The coexistence of CLTM and coverage enhancement, and (e)RedCap is supported.
Proposal 3: Fallback mechanism from RACH-less LTM to RACH-based LTM can be supported if RACH resources are preconfigured in CLMT configuration.
Proposal 4: The valid TA related information can be indicated to the target cell via the following ways:
UE reports the valid TA related information after access to the target cell;
The source cell indicate TA related information via Xn interface.
Proposal 5: When multiple candidate cells satisfy the CLM execution condition, it is up to UE implementation to select a cell as target cell and perform CLTM, no matter the execution condition is L1 based or L3 based.
Proposal 6: For L3 based CLTM, similar approach to RACH-less HO can be considered, that the UE selects the beam with CG resources satisfying the RSRP threshold.
Proposal 7:  When multiple candidate beams satisfy the RSRP threshold, it is up to UE implementation to select a beam and perform C-LTM.
Proposal 8: CLTM can coexist with network triggered L3 HO, CHO and network triggered PScell change, while the coexistence of CLTM and DAPS HO is not supported
Proposal 9: If L3 HO command/LTM cell switch command is received when UE is evaluating the execution conditions of conditional LTM or at the same time that an execution condition is satisfied, UE follows L3 HO command or LTM cell switch command.
Proposal 10: If the execution condition of CHO and the execution condition of conditional LTM are satisfied at the same time, LTM may have higher priority than CHO, and UE performs LTM.

3GPP TSG-RAN WG2#130		      					R2-2504412
St. Julians, Malta, May 19 – 23, 2025			 	　　　
Agenda item:	8.6.4 
Source: 	Kyocera 
Title: 	Remaining issue of Conditional intra-CU LTM
Document for:	Discussion

Conclusion 
In this contribution, the issues for supporting conditional intra-CU LTM are discussed. RAN2 is kindly asked to take into account the observations and proposals below:
Observation 1	In CHO, the UE evaluates multiple execution conditions at the same layer (i.e., with L3 measurements), so there is no difference in the evaluation stability.
Observation 2	For CHO, the UE acquires TA values when accessing the target cell.
Observation 3	In CLTM, the UE may evaluate multiple execution conditions at different layers (i.e., with L1 and L3 measurements), so the evaluation for L3 execution condition would be more stable than that for L1 execution.
Observation 4	Rel-19 CLTM supports the early TA acquisition procedure.
Observation 5	CLTM has a significant advantage over CHO in that RACH-less cell switch can be executed by acquiring TA values in advance.
Proposal 1	RAN2 should agree that the UE prioritizes the CLTM candidate cell with the valid TA value over the one without the TA value regardless of execution condition type, if multiple execution conditions are triggered simultaneously.
Proposal 2	RAN2 should agree that the UE prioritizes the CLTM candidate cell triggering the L3 execution condition over the one triggering the L1 execution condition, if multiple different type of execution conditions is triggered simultaneously where the UE has valid TA values (or the UE does not have valid TA values for any of them).
	

3GPP TSG-RAN WG2 Meeting #130	R2-2504424
St. Julians, Malta, May. 19th – 23rd, 2025
Agenda item:	8.6.4
Source:	ETRI
Title:	Remaining open issues on conditional LTM
Document for:	Discussion, Decision

Conclusions
In this paper, we discuss CLTM related issues. Following are proposals made in this paper:

Proposal 1: The network can trigger the UE to perform cell switch to a CLTM candidate cell by transmitting an LTM cell switch command MAC CE.
Proposal 2: The Enhanced LTM Cell Switch MAC CE always contains a NCC value field
Proposal 3: When the UE receives an (Enhanced) LTM CSC MAC CE requesting a cell switch to a CLTM candidate cell for which the CLTM TAT is running, it performs a RACH-less LTM switch only if the (Enhanced) LTM CSC MAC CE contains a valid Timing Advance Command. Otherwise, the UE performs a RACH-based LTM switch.

3GPP TSG-RAN WG2 Meeting #130		R2-2504446
St Julian, Malta, 19th – 23rd May 2025

Agenda item:	8.6.4
Source:	Samsung
Title:	Remaining issues of Conditional Intra-CU LTM
WID/SID:	NR_Mob_Ph4-Core
Document for:	Discussion and Decision

Conclusion
Based on the discussion, we have the following proposals.
Proposal 1: RAN2 is kindly asked to confirm that C-LTM for SCG is not supported in Rel-19.
Proposal 2: RAN2 is kindly asked to discuss whether to support the RACH-less CLTM for the cells in the same TAG. 
Proposal 3: ‘RACH-less CLTM cell switch can be considered ongoing’, only if UE has valid TA and CG resources for LTM cell switch is configured.
Proposal 4: Remove ‘in the first available CG occasion for initial CG transmission according to clause 5.8.2’ in the condition to determine RACH less C-LTM.
Proposal 5: if ltm-Candidate-TimeAlignmentTimer or ltm-Candidate-TimeAlignmentTimerTAG2 (based on which TA is applied during the RACH less C-LTM execution) expires during the RACH less C-LTM execution, UE falls back to RACH based C-LTM. UE stops using the CG resources for RACH less LTM.
Proposal 6: UE stops the ltm-Candidate-TimeAlignmentTimer/ ltm-Candidate-TimeAlignmentTimerTAG2 for a LTM candidate cell A when the LTM candidate cell A configuration is removed in the latest received RRCReconfiguration message.
Proposal 7: Add additional conditions to check whether the reportConfig/measObject/measId is used for CLTM before removing those configurations while executing ReconfigurationWithSync.

3GPP TSG-RAN WG2 Meeting #130	R2-2504473
St.Julians, Malta, May 19th – 23rd, 2025

Agenda Item:	8.6.4
Source:	HONOR
Title: 	Discussion conditional LTM
Document for:	Discussion and decision
1	

Conclusions
In this contribution, we discussed the conditional LTM for Rel-19 mobility WI. Based on the discussion, the following observation and proposals are concluded:
Proposal 1: (MAC-10) For L3 based C-LTM, follow the legacy procedure for beam selection.
Proposal 2: In addition to the new timer for candidate’s TA, TA validity could also be monitored based on the legacy DL RSRP solution at the UE side.
Proposal 3: UE could request the TA acquisition to the NW when it detects the TA of one candidate is invalid/needed.
4	

3GPP TSG-RAN WG2 Meeting #130	R2-2504496
St. Julians, Malta, May 19th – 23rd, 2025             	         

Agenda Item:	8.6.4
Source: 	ASUSTeK
Title:  	Discussion on TA handling for C-LTM
Document for:	Discussion and Decision

Conclusion
We have the following observation and proposal for TA handling on C-LTM:
Observation:	When performing LTM to a target cell, the TA associated with a source cell of the LTM, which could be a C-LTM candidate Cell, can still be valid.
Proposal 1:	Upon execution of a C-LTM to a candidate cell, if the source cell is a SpCell of a C-LTM candidate configuration, the UE stores the TA of the source cell for the C-LTM candidate configuration, and starts the ltm-Candidate-TimeAlignmentTimer associated with the C-LTM candidate with the length of the remaining time of the timeAlignmentTimer of the source cell.
Proposal 2:	When multiple candidate beams satisfy the event for C-LTM on a 2TA candidate cell, the UE prioritizes selecting candidate beams that are associated with a valid TA.

3GPP TSG RAN WG2 Meeting #130	 R2-2504531
St.Julians, Malta, May 19th – 23rd, 2025

Agenda Item:	8.6.4
Source: 	ITL
Title: 	Discussion on Conditional intra-CU LTM
Document for:	Discussion and decision

Conclusion
In this contribution, we discussed the conditional LTM for Intra-CU LTM. According to discussion in section 2, we have the following proposals:
Proposal 1: For L3 measurement-based C-LTM, when multiple candidate cells fulfill the execution condition, the cell for which the UE has a valid Timing Advance should be prioritized; if no valid TA is available or multiple cells have valid TA, the UE may autonomously select the target cell based on implementation
Proposal 2: In L3-based C-LTM, beam selection for RACH-less should be based on a configured RSRP threshold
Proposal 3: In L3-based C-LTM, if multiple beams within the selected candidate cell satisfy the configured RSRP threshold, the UE may select one of them by implementation
Proposal 4: RAN2 is kindly asked to discuss introducing RACH-less based C-LTM attempt after C-LTM failure
Proposal 5: If the selected cell after C-LTM failure is not the originally attempted C-LTM candidate cell, the UE may attempt RACH-less C-LTM toward the newly selected cell, provided it is a configured candidate and valid TA is available