3GPP TSG RAN WG1 #120bis			R1-2501756
Wuhan, China, April 7th – 11th, 2025

Agenda Item:	9.9.1
Source: 	LG Electronics
Title: 	Discussion on measurements related enhancements for LTM
Document for:	Discussion and decision

Summary
In this contribution, we have discussed on potential enhancements on mobility enhancement phase 4. From the discussion, we obtained following proposals and observations;

Observation 1. The main purpose of the CSI-RS based measurement is to inform network which of the beams are desirable after UE receiving cell switch command, rather than which of the candidate cells are desirable for hand-over.

Proposal 1. Same as Rel-18, association between CSI-RS resources and related candidate cell could be signaled by RRC in LTM-CSI-ResourceConfig explicitly.

Proposal 2. Only the NZP-CSI-RS resources associated to the candidate cells with activated TCI states are valid for the measurement when UE received TCI activation before CSC.

Proposal 3. LTM CSI resources should be counted for the active CSI-RS ports or resources.
FFS: whether it is counted as conventional active CSI-RS ports or resource in active BWP or newly introduced active CSI-RS ports or resource for LTM

Proposal 4. RAN1 assumes the L3 mobility procedure and function based on the associated SSB are reused for timing reference of candidate cell CSI-RS measurement in LTM.
The associated SSB is indicated explicitly in CSI-RS resource configuration.
If there is no associated SSB, the UE is required to measure the CSI-RS resource based on the timing of the serving cell.
If UE failed to detect the associated SSB, UE don’t monitor the related CSI-RS resource.

Proposal 5. Priority rules between LTM CSI report is introduced based on the existing priority rule.
LTM CSI report carrying L1-RSRP is prioritized to the LTM CSI report not carrying L1-RSRP.

Proposal 6. For RS type determination for event LTM2, it is up to RAN2.

Proposal 7. It is sufficient to reuse rule based on the existing CPU occupancy rule for event triggered reporting in Rel-19 LTM.
, for a CSI report with LTM-CSI-ReportConfig.
The CPU(s) are occupied for a number of OFDM symbols
from the first symbol of the earliest one of each CSI-RS resource triggered TTT.
until the last symbol of the configured PUSCH carrying the MAC-CE report.

Proposal 8. LTM CSI-RS resource only dedicated for the CQI acquisition is not supported.

Proposal 9. For CSI acquisition, multiple CSI report configurations and multiple CSI-RS resource configurations is supported for a candidate cell.
Alt 2: Multiple CSI report configurations can be configured
Alt Y: Multiple CSI-RS resources for CMR can be associated with a CSI report configuration

Proposal 10. The aperiodic CSI report triggered by DCI is supported for CSI acquisition on candidate cell.

Proposal 11. For CSI acquisition operation in Release 19, UCI is supported for CSI reporting container.

Proposal 12. CQI-PMI-RI is supported as a report quantity of LTM CSI report.

Proposal 13. Discuss CSI reference resource and UE assumption for CQI/PMI/RI calculation to enable CSI acquisition for LTM.

3GPP TSG RAN WG1 #120bis                                         R1-2501784 
Wuhan, China, April 7th – 11th, 2025

Source:	ZTE Corporation, Sanechips
Title:	Discussion on measurements related enhancements for LTM
Agenda Item:	9.9.1
Document for:	Discussion and Decision

Conclusion
In this contribution, we share our views on measurement related enhancements for Rel-19 LTM, and then proposals are provided as below:
Proposal 1: The following configuration framework should be supported for CSI-RS based early CSI acquisition:
CSI-RS resource/set configuration
A list of NZP CSI-RS resources (e.g., ltm-nzp-CSI-RS-ResourceToAddModList-r19) and a list of NZP CSI-RS resource sets (e.g., ltm-nzp-CSI-RS-ResourceSetToAddModList-r19) are configured per candidate cell, where NZP-CSI-RS-ResourceSet is configured without the higher layer parameters ‘repetition’ and ‘trs-Info’.
CSI-RS measurement configuration
One NZP CSI-RS resource set is configured by ltm-CSI-ResourceConfig-r19 to provide CSI-RS resources for CSI measurement and reporting.
  The maximum number of CSI-RS resources within one CSI-RS resource set can be set to 4 if Rel-19 Type I codebook is supported.
CSI reporting configuration
One LTM CSI Reporting configuration (i.e., LTM-CSI-ReportConfigId-r18) is configured in ServingCellConfig. 
  The LTM CSI reporting configuration ID is associated with a candidate cell identification.
Proposal 2: Semi-persistent (SP) CSI-RS should be supported for early CSI acquisition.
Proposal 3: Aperiodic CSI-RS should be supported for early CSI acquisition for intra-DU case. FFS for inter-DU/CU.
Proposal 4: SP CSI-RS should be activated before reception of LTM Cell Switch Command MAC CE for early CSI acquisition if SP CSI-RS is supported.
Proposal 5: A MAC CE should be used to activate/deactivate SP CSI-RS resource set of candidate cell for CSI measurement, where MAC CE design is up to RAN2.
Proposal 6: CSI-RS resources for CSI measurement should be obtained by ltm-CSI-ResourceConfig-r19 provided per candidate cell if CSI-RS measurement is performed before reception of LTM Cell Switch Command MAC CE.
Proposal 7: CSI-RS resources for CSI measurement should be obtained by the determined CSI reporting configuration based on candidate cell ID same as target cell ID provided by Target Configuration ID field in LTM Cell Switch Command MAC CE if CSI-RS measurement is performed after reception of LTM cell switch command MAC CE.
Proposal 8: For the case of CSI-RS measurement before reception of LTM Cell Switch Command MAC CE, dynamic selection of candidate cell for early CSI acquisition should be supported to reduce measurement overhead at UE side.
Proposal 9: For the case of CSI-RS measurement before reception of LTM Cell Switch Command MAC CE, whether to introduce dynamic selection mechanism of CSI-RS resource set for early CSI acquisition is up to the number of the configured CSI-RS resource set for a candidate cell.
Proposal 10: For the case of CSI-RS measurement after reception of LTM CSC MAC CE, UE can start CSI measurement on the CSI-RS resource after a time interval relative to HARQ-ACK transmission corresponding to LTM Cell Switch Command MAC CE.
 The minimum value of the time interval is 3ms.
Proposal 11: For the case of CSI-RS measurement before reception of LTM Cell Switch Command MAC CE,
If CSI-RS measurement starts to be performed before receiving LTM Cell Switch Command MAC CE, active CSI-RS resources for candidate cells provided by LTM-CSI-SSB-ResourceSet-r18 should be counted. 
If CSI-RS measurement continues to be performed after receiving LTM CSC MAC CE, active CSI-RS resources for candidate cells provided by LTM-CSI-SSB-ResourceSet-r18 and for serving cell provided by CSI-SSB-ResourceSet should be counted until LTM cell switch is completed.
Proposal 12: For the case of CSI-RS measurement after reception of LTM Cell Switch Command MAC CE,
Before receiving LTM Cell Switch Command MAC CE, active CSI-RS resources for candidate cells provided by LTM-CSI-SSB-ResourceSet-r18 should NOT be counted even if CSI-RS measurement configuration for candidate cells has been obtained.
Proposal 13: Regarding determination of CSI reporting configuration using LTM Cell Switch Command MAC CE, at least the following Alt-1 should be supported for early CSI acquisition.
Alt-1: CSI reporting configuration is determined by candidate cell ID same as target cell ID provided by Target Configuration ID field in LTM Cell Switch Command MAC CE.
Note that only one CSI reporting configuration is configured for a candidate cell.
Alt-2: CSI reporting configuration is determined by associated CSI-RS resource set, where one of CSI-RS resource set associated with CSI reporting configuration is same as or associated with RS in TCI state indicated in LTM Cell Switch Command MAC CE.
Alt-3: CSI request field newly added in LTM Cell Switch Command MAC CE is used to indirectly determine CSI reporting configuration.
Proposal 14: Regarding reporting container, UCI is supported to carry single CSI reporting for early CSI acquisition, which is same as legacy CSI reporting.
Proposal 15: For PUSCH to carry single CSI reporting, the following method should be supported for early CSI acquisition:
For RACH-less LTM cell switch case, single CSI reporting is transmitted on DG-PUSCH or CG-PUSCH where RRC reconfiguration complete message is transmitted.
For RACH-based LTM cell switch case, single CSI reporting is transmitted on PUSCH scheduled by RAR UL grant regardless of what MSG 3 content is to be transmitted on the PUSCH, and regardless of contention-free random access (CFRA) or contention-based random access (CBRA) is initiated.
Proposal 16: PUSCH carrying CSI reporting should be a PUSCH after X symbols relative to CSI-RS resource for CSI measurement, where the value of X is up to UE capability.
Proposal 17: For report quantity, it is proposed to support 'cri-RI-PMI-CQI' for early CSI acquisition.
Report quantity of 'cri-RI-CQI' can be considered if SRS transmission is supported for early CSI acquisition.
Proposal 18: For codebook type, at least Rel-15 Type I codebook and Rel-19 enhanced Type I codebook should be supported for early CSI acquisition.
Proposal 19: For event-triggered reporting, it is proposed to support including up to nrOfReportedCells *nrOfReportedRS-PerCell beams in a measurement reporting MAC CE, where
nrOfReportedCells is up to 4.
nrOfReportedRS-PerCell is up to 4.
Whether to include spCellInclusion is configured by NW.

3GPP TSG RAN WG1 #120bis	R1-2501821
Wuhan, China, April 7th – 11th, 2025

Source:	vivo
Title:	Discussion on measurements related enhancements for LTM
Agenda Item:	9.9.1
Document for:	Discussion and Decision

Conclusion
For measurements related enhancement(s) for LTM, we have the following observations and proposals:
RAN2 has agreed to configure the RS type used for LTM event evaluation and it should apply for event LTM2 only, so there is no issue for RS type determination for event LTM2.

Do not support SSB-based L1-SINR measurement for event-triggered reporting.
If L1-SINR measurement is supported for Event LTM2, we prefer it is performed on CMR-only mode, i.e., channel measurement and interference measurement are performed based on the QCL RS, i.e., CSI-RS for BM of the indicated TCI state.
If semi-persistent CSI-RS resources are used for beam management on candidate cell(s), besides the legacy activation/deactivation mechanism by MAC CE, the active semi-persistent CSI-RS resources associated with candidate cell(s) other than the target cell should be deactivated after the reception of LTM cell switch command.
Support the association between the CSI-RS resources and candidate cells is achieved by explicit signaling, i.e., a ltm-NZP-CSI-RS-ResourceList is associated with a ltm-CandidateIdList and the total number of elements included in both lists is the same.
The legacy design of CSI-RS for CSI should be reused for LTM, i.e., the maximum port number of a CSI-RS resource for CSI is 32, and up to 8 CSI-RS resources can be included in the NZP-CSI-RS resource set.
Support semi-persistent CSI resources for CSI measurement on candidate cell(s).
Multiple LTM CSI report configurations for CSI can be configured for a candidate cell and an association between Candidate joint/DL TCI state and LTM CSI report configuration should be introduced to implicitly determine the CSI-RS resources for CSI measurement before or after the reception of LTM CSC MAC CE.    
Support CSI report during LTM cell switch procedure to be carried by UCI.
Support Option-3’, i.e., the CG-PUSCH configured for the first UL message is shared with the initial CSI report, and only when the initial CSI report and the first UL message are transmitted, the CG-PUSCH configuration is released.
The occupied CPU of the initial CSI report starts from the first symbol after the PDSCH carrying the LTM CSC MAC CE, and ends up with the last symbol of the uplink resource carrying the initial CSI report.
Do not support CSI measurement on candidate cells performed outside the active BWP of the serving cell.
Support to define a new UE capability on the maximum number of CSI-RS for CSI across candidate cells that UE can measure before cell switch.
Support wideband Type 1 CSI reporting only, i.e., wideband PMI and CQI as report quantity.     
Activated Candidate TCI state(s), other than the TCI state associated with the triggered beam, should be deactivated upon CLTM procedure being triggered.

3GPP TSG-RAN WG1 Meeting #RAN 120b	R1-2501849
Wuhan, China, 07-11 Apr, 2025

Agenda Item:	9.9.1	
Source:	TCL
Title:	Discussion on measurements related enhancements for LTM
Document for:	Discussion and Decision 

Conclusions
This contribution presents our views on CSI-RS measurements for LTM procedures and CSI acquisition before or during the LTM cell switch. We have following proposals.

: For candidate cells, two CSI report configurations can be configured for aperiodic and semi-persistent CSI reporting respectively.
 : Support aperiodic CSI measurement and reporting for the target cell triggered by the CSC MAC CE.
 : For periodic CSI-RS configuration, support aperiodic CSI reporting for the target cell triggered by the CSC MAC CE.
 : For periodic CSI-RS configuration, a CSI report configuration associated with multiple CSI resources is unnecessary. 
 : For the CSI reports for the target cell, the semi-persistent CSI-RS resource for candidate cells should be supported. 
 : For CSI reports for the target cell, when periodic CSI-RS resource is configured, the UE only requires to measure CSI for these candidate cells with higher probability to be target cells, which depends on the UE’s reporting of L1 measure results based on the event-triggered L1 measure reporting or gNB-scheduled L1 measure reporting. 
 : For CSI reports for the target cell, when periodic CSI-RS resource is configured, the UE measures CSI for these candidate cells with higher probability to be target cells not earlier than the slot when the UE reports L1 measurement results based on the event-triggered L1 measure reporting or gNB-schedule L1 measure reporting. 

3GPP TSG RAN WG1#120bis	                                       	 R1-2501879
Wuhan, China, April 7th – 11th, 2025

Agenda Item:     9.9.1
Source:	Spreadtrum, UNISOC
Title:	             Discussion on measurements related enhancements for LTM
Document for:	Discussion and decision

Conclusion 
In this contribution, we provide our proposals on Rel-19 NR mobility enhancements Phase 4:
Proposal 1:
The association between the candidate cells and the measurement CSI-RS resources can be determined based on the correspondence between the candidate cell and root SSB for the CSI-RS resource or root SSB for QCL source RS of the CSI-RS resource.
Proposal 2:
Support repetition=off for the CSI-RS resource set under candidate cell configuration.
Proposal 3:
For the RS type determination for event triggered reporting with event LTM2, at least one candidate cell RS shall be configured, and the RS type of the serving cell beam is determined based on the RS of the candidate cell.
Proposal 4:
For UE supporting CSI measurement before the reception of LTM CSC, 
before the reception of LTM CSC, the UE shall perform CSI measurements on each candidate cells;
after the reception of LTM CSC, the UE only performs CSI measurement on the target cell indicated by LTM CSC.
Proposal 5:
For UE only supporting CSI measurement after the reception of LTM CSC, when the PDSCH carrying the LTM CSC is received or the PUCCH with HARQ-ACK corresponding to the PDSCH carrying the LTM CSC is transmitted, the UE starts measuring the CSI-RS resource of the target cell.
Proposal 6:
In addition to periodic CSI-RS, support AP-CSI-RS for UE only supporting CSI measurement after the reception of LTM CSC, where the AP-CSI-RS is associated with the CSI report.
Proposal 7:
Support reusing the signaling framework of LTM beam reporting for CSI report configuration, i.e. 
a single CSI report is configured and associated with a single CSI-RS resource configuration that includes a single resource set containing CSI-RS resources corresponding to multiple candidate cells;
in the CSI-RS resource set, only one CSI-RS resource is configured for each candidate cell.
Proposal 8:
Support triggering CSI reporting by LTM CSC MAC CE and the reported measurement results are derived based on the CSI-RS resource from the target cell in the resource set under the CSI report configuration.
Proposal 9:
The CSI report can be included on the Msg3 for RACH-based LTM or the first UL channel for RACH-less LTM.
Proposal 10:
For further UE complexity reduction and power saving, some configuration for CSI acquisition should be limited, e.g.
only Type I codebook is configured, 
the number of CSI-RS ports per CSI-RS resource not exceeds 4,
the number of candidate cells to be measured not exceeds N (e.g. 1 or 2) for CSI-RS measurement before the reception of LTM CSC MAC CE.
Proposal 11:
For LTM CSI acquisition, the periodic CSI-RS resource is active in a duration of time defined as follows:
for UE supporting CSI measurement before the reception of LTM CSC: reuse legacy definition for periodic CSI-RS;
for UE only supporting CSI measurement after the reception of LTM CSC: starting from the end of the PDSCH carrying the LTM CSC or the end of the PUCCH with HARQ-ACK corresponding to the PDSCH carrying the LTM CSC, and ending at the end of the uplink channel resource containing the report associated with this CSI-RS.
Proposal 12:
Define the CSI computation time for LTM CSI acquisition as follows:
the LTM CSI report occupies CPU(s) from the first symbol after the trigger signaling of the report, e.g. LTM CSC MAC CE, until the last symbol of the uplink channel resource carrying the report in target cell.

DOC FILE NOT FOUND

DOC FILE NOT FOUND

3GPP TSG RAN WG1 #120bis		                                             R1-2502006
Wuhan, China, April, 7th – 11st, 2025

Source:	CATT
Title:	Discussions on measurements related enhancements for LTM
Agenda Item:	9.9.1
Document for:	Discussion and Decision

Conclusions
In this contribution, we provide our views on the support of CSI-RS for LTM procedures, event triggered L1 measurement reporting and conditional LTM. We have the following proposals:

Proposal 1: Support the conclusion that the QCLed SSB of each CSI-RS should be reused as the timing reference for candidate cell CSI-RS measurements in LTM.
Proposal 2: Support explicitly configure the association between the measurement CSI-RS resources and candidate cells within a single resource set containing CSI-RS resources.
Proposal 3: Regarding to the RS type determination for event LTM2, support Alt 1-1, i.e. RS type is RRC configured. 
Proposal 4: No need to define CSI reference resource for LTM event-triggered reporting. 
Proposal 5: Reuse the legacy mechanism of CPU occupancy timeline for CSI report for event triggered reporting. Specifically, the CPU occupancy time starts from the first OFDM symbol of the earliest one of each transmission occasion of periodic CSI-RS/SSB resource of all the candidate cells for L1-RSRP measurements, until   symbols after the last symbol of the latest one of the CSI-RS/SSB resource of all the candidate cells for L1-RSRP measurements in each transmission occasion.
Proposal 6: For L1 event-triggered measurement, QCLed SSB of each CSI-RS should be reused as the timing reference for candidate cell CSI-RS measurements. 
Proposal 7: For NR Rel-19 event-triggered LTM beam reporting, for each report instance carried by MAC CE, subject to UE capability, the maximum number of configured/activated cells number should be L = 4 and the maximum number of beams M for each of the L cells should be M = 4. Consequently, the maximum number of beam level measurement results that can be included in the MAC CE should be 16.

Proposal 8: Rx beam refinement with ‘repetition’ set to ‘on’ should be supported for both gNB scheduled reporting and event triggered reporting.
Proposal 9: For each candidate cell, a single CSI report configuration is preferred, where multiple CSI-RS resources for CMR are associated with a CSI report configuration. 
Proposal 10: CSI report configuration is triggered implicitly by CSC MAC-CE.
Proposal 11: For the reporting mechanism of CSI acquisition, CSI should be carried by PUSCH. 
Note: If CSI is not available at the predefined PUSCH, some candidate PUSCH could be used instead. For example, CG-PUSCH could be reserved until CSI has been reported, or Msg5 is used for RACH-based LTM.
Proposal 12: Subject to UE capability, semi-persistent CSI-RS could also be supported for CSI acquisition of candidate/target cell(s).
Proposal 13: Support only aperiodic reporting on PUSCH for CSI acquisition of candidate/target cell(s).
Proposal 14: For CSI acquisition of candidate/target cell(s), support CSI report using Type-I codebook with report quantity configured with ‘CRI-RI-PMI-CQI’.
Proposal 15: No need to define beam application time for NR Rel-19 RACH-less C-LTM.

DOC FILE NOT FOUND

DOC FILE NOT FOUND

3GPP TSG RAN WG1 Meeting #120bis	R1-2502088
Wuhan, China, April 7th-11th, 2025
Source:		Moderator (Fujitsu)
Title:	FL summary 1 of Measurements related enhancements for LTM
Agenda Item:	9.9.1
Document for:	Information

Conclusion]
The discussion of this section is closed without any FL proposal. 


CSI acquisition for candidate cell(s)
[High] Remaining issues for CSI acquisition framework – report container and time domain property of the report considering timeline issue
[Agreements in the previous meetings]
Agreement (RAN1#118bis)
The following alternatives are further studied:
Alt-1: CSI-RS measurement and CSI reporting operations are performed before reception of LTM Cell Switch Command (CSC) MAC CE.
The report is sent to the serving cell and transferred to the candidate/target cell(s)
Alt-2: CSI-RS measurement can start before reception of LTM CSC MAC CE and CSI reporting operation is performed after reception of LTM CSC MAC CE.
The report is sent directly to target cell
Alt-3: CSI-RS measurement and CSI reporting operations are performed after reception of LTM CSC MAC CE.
The report is sent directly to target cell
Companies are requested to provide the details of exact report timing and triggering mechanism in the next meeting

Working Assumption (RAN1#119)
As baseline, CSI-RS measurement and CSI reporting operations are performed after reception of LTM CSC MAC CE.
The report is sent directly to target cell
Introduce UE capability for CSI-RS measurement can start before reception of LTM CSC MAC CE
Other than UE capability, strive for no additional spec impact compared to the baseline (only one triggering mechanism will be specified)

Agreement(RAN1#120)
For target cell CSI acquisition, 
A UE is provided with RRC configurations for periodic CSI-RS resource(s) and CSI report(s) for one or more candidate cell
For a candidate cell,
down-select from the following alternatives:
Alt 1: A single CSI report configuration is configured
Alt 2: Multiple CSI report configurations can be configured
down-select from the following alternatives:
Alt X: A single CSI-RS resource for CMR is associated with a CSI report configuration
Alt Y: Multiple CSI-RS resources for CMR can be associated with a CSI report configuration
FFS : Semi-persistent CSI-RS resource
After the RRC configuration and before the reception of CSC, the UE may measure CSI based on the configured CSI-RS resource(s), which is subject to UE capability
FFS: whether or how to select a subset of CSI-RS resources to measure
FFS: when the UE may start measuring the configured CSI-RS resources
UE determines the CSI report configuration based on the CSC
After the reception of cell switch command, the UE may measure (depending on the timeline) CSI-RS resource(s) associated with determined CSI report configuration 
The latest available measured CSI on target cell resource(s) is conveyed at least by a single report, and the report is sent to the target cell
Option 1: to use UCI
Option 2: to use MAC CE
Note: with this agreement, the working assumption made in RAN1#119 is automatically confirmed.

[Summary of contributions]
This section focuses on the remaining issue on the CSI-acquisition framework, i.e. container and timeline which is related to the yellow highlighted part in the RAN1#120 agreement above. 
Issue 1: Container
Option 1: to use UCI
Supported by 20 companies: LGE, ZTE, vivo, CATT, Lenovo, Fujitsu, CMCC, Huawei, OPPO, SONY, Samsung, Xiaomi, Sharp, ETRI, NEC, Apple, Nokia, KDDI, DOCOMO, Google
Justification: Mechanism has already been specified and no latency due to the processing by higher layer
Concern: potential timeline issue
Option 2: to use MAC CE 
Supported by 5 companies: IDC, SONY, Ericsson, Qualcomm, MediaTek
Justification, there is no issue on timeline
Concern: RAN2 workload to define a new MAC CE format to convey UCI

Issue 2: Whether and how to solve the timeline issue? If timeline is not satisfied when UCI is used, how the CSI is reported? (note: timeline definition will be separately discussed)
Issue 2-1: How to avoid the blind detection at gNB ?
Option 2-1-1: report the lowest CQI index (out of range) when the timeline is unsatisfied
Option 2-1-2: report an indication of if valid CSI is available (by UCI or MAC CE)
Option 2-1-3: report an indication of when valid CSI is available after cell switch (by UCI or MAC CE)
Option 2-1-4: gNB controls the timing of CSC and first PUSCH to avoid the presence of occurrence of blind detection
Issue 2-2: How to provide the second opportunity to report the CSI when the timeline is not satisfied for the 1st occasion?
Option 2-2-1: If valid CSI is not available at the predefined first PUSCH, some additional PUSCHs could be used instead. 
Option 2-2-1-1: CG-PUSCH could be reserved until valid CSI has been reported
Option 2-2-1-2: multiple (CG and/or DG) PUSCHs can be used to convey valid CSI after the 1st occasion, and the number of PUSCHs can be configured by RRC
Option 2-2-2: gNB requests CSI after cell switch completion, i.e. no spec impact
Issue 3: if UCI is adopted, which PUSCH is used to convey first UCI report? (note possibility of second, 3rd … transmission is captured in issue 2-2. 
For RACH-less LTM
DG-PUSCH or CG-PUSCH where RRC reconfiguration complete message is transmitted.
For RACH-based LTM
Option 3-1: DG-PUSCH or CG-PUSCH where RRC reconfiguration complete message is transmitted.
Option 3-2: PUSCH scheduled by RAR UL grant, for both CFRA and CBRA
Option 3-3: PUSCH scheduled by RAR UL grant for both CFRA and DG-PUSCH or CG-PUSCH where RRC reconfiguration complete message is transmitted for CBRA
[FL observation]
FL thinks we can firstly discuss the container and timeline issue in this meeting.
For issue 1: For the container, i.e. UCI vs MAC CE, FL thinks UCI is a good option to reuse the existing RAN1 specifications as much as possible. The potential issue occurring when the timeline is not satisfied needs carefully assessed, and the solution needs to be introduced if necessary. On the other hand, MAC CE has no/less issue on the timeline issue because the UCI can be reported whenever it is ready. Also, blind detection will not be required thanks to MAC CE container. Nevertheless, RAN2 needs to define a new report format, which would be a major concern. 
For issue 2-1 and 2-2, all the options work in some sense, but FL thinks the solutions are for optimization and no strong necessity to have, even though nice to have. 
To simplify the system design and to minimize the workload in RAN1 and RAN2, FL suggestion is to adopt option 1 + option 2-1-1 + option 2-2-2 as a starting point of the discussion in this meeting. 

[FL proposal 5-1-v1]
For the container of LTM CSI report for a target cell, 
Option 1: to use UCI (FL suggestion)
Supported by 20 companies: LGE, ZTE, vivo, CATT, Lenovo, Fujitsu, CMCC, Huawei, OPPO, SONY, Samsung, Xiaomi, Sharp, ETRI, NEC, Apple, Nokia, KDDI, DOCOMO, Google
Option 2: to use MAC CE 
Supported by 5 companies: IDC, SONY, Ericsson, Qualcomm, MediaTek
For the LTM CSI report to the target cell,
Option 2-1-1: a UE reports the lowest CQI index (out of range) when time timeline of CSI measurement and reporting is not satisfied (FL suggestion)
Option 2-1-2: a UE reports an indication of if valid CSI is available (FFS by UCI or MAC CE) together with the CSI report
Option 2-1-3: a UE reports an indication of when valid CSI is available after cell switch (by UCI or MAC CE) together with the CSI report
Option 2-1-4: gNB controls the timing of CSC and first PUSCH timing to avoid the presence of occurrence of blind detection, i.e. no spec impact
FFS: the definition of timeline
If valid CSI is not available at the predefined first PUSCH,
Option 2-2-1:, some additional PUSCHs could be used to convey the valid CSI. 
Option 2-2-1-1: CG-PUSCH could be reserved until valid CSI has been reported
Option 2-2-1-2: multiple (CG and/or DG) PUSCHs can be used to convey valid CSI after the 1st occasion, and the number of PUSCHs can be configured by RRC
Option 2-2-2: gNB requests CSI after cell switch completion, i.e. no spec impact (FL suggestion)


[Comments to 5-1-v1]


[High] Time domain property of CSI-RS resource
[Agreements in the previous meetings]
Agreement(RAN1#120)
For target cell CSI acquisition, 
A UE is provided with RRC configurations for periodic CSI-RS resource(s) and CSI report(s) for one or more candidate cell
For a candidate cell,
down-select from the following alternatives:
Alt 1: A single CSI report configuration is configured
Alt 2: Multiple CSI report configurations can be configured
down-select from the following alternatives:
Alt X: A single CSI-RS resource for CMR is associated with a CSI report configuration
Alt Y: Multiple CSI-RS resources for CMR can be associated with a CSI report configuration
FFS : Semi-persistent CSI-RS resource
After the RRC configuration and before the reception of CSC, the UE may measure CSI based on the configured CSI-RS resource(s), which is subject to UE capability
FFS: whether or how to select a subset of CSI-RS resources to measure
FFS: when the UE may start measuring the configured CSI-RS resources
UE determines the CSI report configuration based on the CSC
After the reception of cell switch command, the UE may measure (depending on the timeline) CSI-RS resource(s) associated with determined CSI report configuration 
The latest available measured CSI on target cell resource(s) is conveyed at least by a single report, and the report is sent to the target cell
Option 1: to use UCI
Option 2: to use MAC CE
Note: with this agreement, the working assumption made in RAN1#119 is automatically confirmed.

[Summary of contributions]
The discussion of this section focuses on the time domain property for CSI-RS resource for CSI acquisition, i.e. support of semi-persistent (SP) CSI-RS and/or aperiodic (AP) CSI-RS resource on top of periodic CSI-RS. 
Support of SP CSI-RS resource 
Support (17): ZTE, vivo, Spreadtrum, CATT, Lenovo, Fujitsu, CMCC, Huawei, Samsung, ETRI, Ericsson, Apple, Nokia, KDDI, DOCOMO, Qualcomm, Google
Justification: the same mechanism as L1-RSRP measurement report with gNB scheduled reporting. Reduction of energy consumption for both UE and network. Avoiding unnecessary inter-cell interference. 
Concern (1): MediaTek
Justification: periodic CSI-RS is sufficient
Support of AP CSI-RS resource
Support: ZTE, TCL
Mechanism to trigger SP CSI-RS resources
SP CSI-RS should be activated before reception of LTM Cell Switch Command MAC CE for early CSI acquisition if SP CSI-RS is supported.
A MAC CE should be used to activate/deactivate SP CSI-RS resource set of candidate cell for CSI measurement, where MAC CE design is up to RAN2.
Semi-persistent CSI-RS measurement after CSC can be automatically activated by CSC
Enhance the existing TCI-State activation/deactivation MAC-CE for Candidate cell to activate the SP-CSI-RS based measurement before reception of CSC MAC-CE.
[FL observation]
Considering the number of supporting companies for SP CSI-RS, FL believes it can be agreed in this meeting. For the detailed mechanism, it is natural to use a MAC CE for activation and deactivation based on the legacy design. RAN1 can ask RAN2 to work on the detailed design of MAC CE.
In addition, it is proposed to introduce automatic activation by Candidate Cell TCI States Activation/Deactivation MAC CE. This might be reasonable if the UE starts CSI acquisition only for the candidate cells associated with the activated TCI states. This can be further discussed, but FL thinks this automatic mechanism is an optimization given the introduction of a new MAC CE. The necessity should be carefully assessed
Finally, it is also proposed to introduce AP CSI-RS resource. FL suggestion is to finalize the basic design using P (and potentially SP) CSI-RS first, and then come back if time allows. 
[FL proposal 5-2-v1]
In addition to periodic CSI-RS resource, semi-persistent CSI-RS resource is supported for candidate/target cell CSI acquisition for intra- and inter- CU/DU scenarios
Support of semi-persistent CSI-RS resource is subject to UE capability.
A new MAC CE is used to activate/deactivate the semi-persistent CSI-RS resource similarly to the legacy mechanism for a serving cell which will be specified in RAN2
FFS the mechanism to automatically activate/deactivate the semi-persistent CSI-RS resource, e.g. by Candidate Cell TCI States Activation/Deactivation MAC CE (FL note: check if this FFS can be kept or not) 
Send an LS to RAN2 and RAN3 to inform this agreement


[Comments to 5-2-v1]

[FL proposal 5-2-v2]
In addition to periodic CSI-RS resource, semi-persistent CSI-RS resource is supported for candidate/target cell CSI acquisition for intra- and inter- CU/DU scenarios
Support of semi-persistent CSI-RS resource is subject to UE capability.
A new MAC CE is used to activate/deactivate the semi-persistent CSI-RS resource similarly to the legacy mechanism for a serving cell which will be specified in RAN2
FFS the mechanism to automatically activate/deactivate the semi-persistent CSI-RS resource, e.g. by Candidate Cell TCI States Activation/Deactivation MAC CE (FL note: check if this FFS can be kept or not) 
Send an LS to RAN2 and RAN3 to inform this agreement


[High] Configuration structure for CSI report and CSI-RS resource
[Agreements in the previous meetings]
Agreement(RAN1#120)
For target cell CSI acquisition, 
A UE is provided with RRC configurations for periodic CSI-RS resource(s) and CSI report(s) for one or more candidate cell
For a candidate cell,
down-select from the following alternatives:
Alt 1: A single CSI report configuration is configured
Alt 2: Multiple CSI report configurations can be configured
down-select from the following alternatives:
Alt X: A single CSI-RS resource for CMR is associated with a CSI report configuration
Alt Y: Multiple CSI-RS resources for CMR can be associated with a CSI report configuration
FFS : Semi-persistent CSI-RS resource
After the RRC configuration and before the reception of CSC, the UE may measure CSI based on the configured CSI-RS resource(s), which is subject to UE capability
FFS: whether or how to select a subset of CSI-RS resources to measure
FFS: when the UE may start measuring the configured CSI-RS resources
UE determines the CSI report configuration based on the CSC
After the reception of cell switch command, the UE may measure (depending on the timeline) CSI-RS resource(s) associated with determined CSI report configuration 
The latest available measured CSI on target cell resource(s) is conveyed at least by a single report, and the report is sent to the target cell
Option 1: to use UCI
Option 2: to use MAC CE
Note: with this agreement, the working assumption made in RAN1#119 is automatically confirmed.

[Summary of contributions]
Number of CSI-RS resource configurations and report configurations
The companies view on the number of report configs / CSI-RS resources are summarized as follows

Justifications for each alternative are summarized as follows:
Alt 1 + Alt X: Simple. Not necessary to have multiple configurations for CSI-RS resource and reporting as the reported CSI is used only for a short period
Alt 1 + Alt Y: Sufficiently flexible. The indication of report configuration can be simplified while sufficient flexibility for beam selection can be provided
Alt 2 + Alt Y: Fully flexible. Choice of report and CSI resource configuration is important for FR2

RRC structure
Even though very detailed proposals are provided by the companies, FL thinks that we can focus on the high-level discussion at this stage to help the rapporteur’s discussion 
CSI report configuration
Alt. 1-1: Provided under ServingCellConfig 
Justification: Same as in legacy report configuration
Alt. 1-2: Provided (somewhere) under LTM-config
Justification: Report configuration is provided/used for each candidate cells, and the report configuration should be kept even after cell switch
Nokia mentioned that outside of the ltm-CandidateConfig, though 
Note that RAN1 assumes the report configuration for CSI acquisition is shared between the source cell, the target cell and the UE, which may have RAN2 and RAN3 spec impact
CSI-RS resources, resource set and resource configurations
Alt. 2-1: LTM-CSI-ResourceConfig provides multiple CSI-RS resource sets for CSI acquisition, where each resource set is associated with different candidate cell
Alt. 2-2: LTM-CSI-ResourceConfig provides a single CSI-RS resource set for CSI acquisition, which includes multiple CSI-RS resources associated with each candidate cells
Resource set configuration for CSI acquisition is provided without repetition and trs-info parameters

[FL observation]
For the number of CS-RS resources and resource configurations, Alt 1 + Alt Y has slight majority support compared with other alternatives. FL understands that this combination gives a good balance between complexity and flexibility considering FR2 operation. 
As for the structure of CSI report configuration, FL agrees the report configuration is shared from target cell to the serving cell (and to UE) because the report is performed to the target cell while the configuration is conducted under the serving cell. With this fact, it would be straightforward to provide report configuration under LTM-config. The details on the structure can be discussed under rapporteur’s RRC parameter session. 
Finally for the relationship between resource set and resource configuration, FL thinks that having different resource set for each candidate cell is a natural interpretation from the agreement in RAN1#120, i.e. only report config(s) associated with the target cell is eventually used. Thus, Alt 2-1 above is proposed as a way forward. 
In summary the following two FL proposals can be made in this meeting. 
[FL proposal 5-3-1-v1]
FL note Alt 1 + Alt Y is chosen from the agreement at RAN1#120 because it has the majority support and good balance between flexibility and complexity
For a candidate cell, 
A single CSI report configuration is configured
Multiple CSI-RS resources for CMR can be associated with a CSI report configuration

[FL proposal 5-3-2-v1]
FL note: Alt 1-2 and 2-1 are chosen from the “Summary of contributions” above
CSI report configuration for LTM CSI acquisition is provided under LTM-config
Note: RAN1 assumes the report configuration for CSI acquisition is shared between the source cell, the target cell and the UE
A LTM-CSI-ResourceConfig configuration provides multiple CSI-RS resource sets for CSI acquisition, where each resource set is associated with each candidate cell
Resource set configuration for CSI acquisition is provided without repetition and trs-info

[Comments to 5-3-1-v1 and 5-3-2-v1]

[High] Subset of CSI-RS resources for CSI measurement before CSC
[Agreements in the previous meetings]
Agreement(RAN1#120)
For target cell CSI acquisition, 
A UE is provided with RRC configurations for periodic CSI-RS resource(s) and CSI report(s) for one or more candidate cell
For a candidate cell,
down-select from the following alternatives:
Alt 1: A single CSI report configuration is configured
Alt 2: Multiple CSI report configurations can be configured
down-select from the following alternatives:
Alt X: A single CSI-RS resource for CMR is associated with a CSI report configuration
Alt Y: Multiple CSI-RS resources for CMR can be associated with a CSI report configuration
FFS : Semi-persistent CSI-RS resource
After the RRC configuration and before the reception of CSC, the UE may measure CSI based on the configured CSI-RS resource(s), which is subject to UE capability
FFS: whether or how to select a subset of CSI-RS resources to measure
FFS: when the UE may start measuring the configured CSI-RS resources
UE determines the CSI report configuration based on the CSC
After the reception of cell switch command, the UE may measure (depending on the timeline) CSI-RS resource(s) associated with determined CSI report configuration 
The latest available measured CSI on target cell resource(s) is conveyed at least by a single report, and the report is sent to the target cell
Option 1: to use UCI
Option 2: to use MAC CE
Note: with this agreement, the working assumption made in RAN1#119 is automatically confirmed.

[Summary of contributions]
Regarding the additional mechanism to indicate the subset of CSI-RS for CSI acquisition (before CSC), companies’ views are summarized as follows: 
Issue 1-1: Whether or not such a mechanism is needed
Option 1-1: Specify a mechanism to indicate subset of CSI-RS resources for CSI measurement
Option 1-2: Can be left to UE implementation:
Option 1-3: Introduce UE capability on the number of candidate cell or CSI-RSs. Up to network configuration on top of that
Issue 1-2: Indication mechanism, if Option 1-1 above is supported
Introduce a new MAC CE
Reuse the existing field in DCI format, e.g. CSI request field
Implicitly indicated by candidate cell TCI state activation/deactivation MAC CE: 
Measure CSI-RS resource(s) associated with activated joint or DL TCI state for candidate cell
SP CSI-RS resource(s) are also implicitly activated
Implicitly indicate by a MAC CE for SP CSI-RS resources activation/deactivation
Implicitly indicated by the cell indicator field in PDCCH order
Another discussion point is the timing to start the CSI measurement before CSC. Related to this, it is also proposed to disable/enable CSI reporting together with CSI measurement 
Issue 2: Timing to start the CSI measurement before CSC
After RRC configuration 
After receiving a MAC CE to trigger CSI measurement 
After receiving candidate cell TCI state activation/deactivation MAC CE
UE implementation 
Issue 3: Activation/deactivation of CSI acquisition (i.e. measurement and reporting) 
a UE can be provided by the network whether a candidate cell is enabled or not for CSI acquisition

[FL observation]
As issue 1-1, 1-2 and 2 has some dependency, FL suggestion is focusing on issue 1-1 first and conclude in this meeting. On top of that, we can try our best to further narrow down the details for issues 1-2, 2 and 3 using the available remaining time.
For issue 1-1, FL analysis for each option is summarized as follows:
Option 1-1: Specify a mechanism to indicate subset of CSI-RS resources for CSI measurement
Justification: measurement overhead reduction at UE side
Concern: Additional spec impact (depending on the solution)
Option 1-2: Can be left to UE implementation:
Justification: simple, UE knows which TCI state is likely be selected from the L1-RSRP measurement results
Concern: gNB cannot control CSI measurement by a UE before CSC 
Option 1-3: Introduce UE capability on the number of candidate cell or CSI-RSs. Up to network configuration on top of that
Justification: This is a usual mechanism, and no specific solution is necessary.
Concern: RRC reconfiguration cannot be expected due to subsequent property for LTM
RAN1 is encouraged to select one option considering the benefit and drawback for each option. 

[FL proposal 5-4-v1]
Companies are encouraged to provide their view on the following proposal. 
For the subset selection of the measurement CSI-RS resource(s) from the configured CSI-RS resources before CSC, down-select one option from the following:
Option 1-1: Specify a mechanism to indicate subset of CSI-RS resources for CSI measurement
Option 1-2: Can be left to UE implementation:
Option 1-3: Introduce UE capability on the number of candidate cell or CSI-RS resources. On top of that gNB can configure appropriate CSI-RSs

[Comments to 5-4-v1]




[Mid] Contents of report and CSI-RS configurations
[Agreements in the previous meetings]
The following figure is provided in the FLS for reference. The issues in this section are equivalent to Open issue 1 below. 

[Summary of contributions]
Restrictions on the CSI configurations
Number of ports for CSI-RS resource
Up to 4: Spreadtrum
Up to 32: vivo
Up to 128 CMCC, Ericsson
Codebook configurations for report configuration
Type I: Spreadtrum, CATT, ZTE, Huawei, vivo, Nokia, OPPO, Ericsson, DOCOMO, Fujitsu, Google, CMCC, Apple
Rel-19 eType I: ZTE
Report quantity for report configuration
cri-RI-PMI-CQI: LG, CATT, ZTE, Huawei, Nokia, OPPO, Lenovo, Ericsson, Fujitsu, DOCOMO, Google, CMCC
cri-RI-PMI-CQI if SRS transmission is supported: ZTE, Fujitsu
CQI for Rank1 only: MediaTek
Report frequency configuration for report configuration
Wideband CQI/PMI: Huawei, CMCC, vivo, OPPO, Lenovo, Fujitsu, Ericsson, Nokia
Subband CQI/PMI: CMCC
Others
Samsung
Regarding the supported CSI reporting modalities (e.g. report quantities and codebooks/codebook configurations) for CSI acquisition for candidate cell(s), RAN1 should do at least the following: 
Feasibility assessment via various aspects of all the supported CSI reporting modalities in relation to the CSI-RS measurement aspects, in the context of the reception/application of LTM CSC and the corresponding RACH procedure before making down-selection
Benefit assessment via the customary system-level simulation with the user perceived throughout (UPT) statistics as the metrics, using L1-RSRP as the baseline, and fully reusing the Rel-19 CSI EVM (cf. AI 9.2.2). 
DOCOMO
Support one CMR in the report, i.e. IMR 
LG: 
LTM CSI-RS resource only dedicated for the CQI acquisition is not supported
[FL observation]
In this meeting, FL would like to suggest focusing on the issues that many companies are interested in. Considering the proposals by the companies, FL understands that the mechanism for CSI acquisition can be simplified to achieve a less complicated system design. Also, many companies proposed that excessive performance optimization is not important as the time period LTM CSI acquisition applied is very short. Given this analysis, it would be good idea to introduce some constraints for report and/or CSI-RS configurations. FL proposal is to take the options majority supports. 
[FL proposal 5-5-v1]
For the number of CSI-RS ports, select one option from the following for LTM CSI acquisition
Option 1. Up to 4: Spreadtrum
Option 2. Up to 32: vivo
Option 3. Up to 128 CMCC, Ericsson
For the codebook configurations in report configuration, only typeI-SinglePanel is supported for LTM CSI acquisition
FL note: Rel-19 eType I (ZTE) is excluded because of the lack of support. This can be discussed further offline/online
For the report quantity in report configuration, only cri-RI-PMI-CQI is supported for LTM CSI acquisition
FFS: whether the rank is limited to 1 (MTK) – This may also have some impact on the number of ports for CSI-RS resource. Can be discussed further online/offline
FL note: cri-RI-PMI-CQI is excluded as SRS is not proposed/supported for CSI acquistion
For report frequency configuration in report configuration, wideband CQI and wideband PMI are supported for LTM CSI acquisition
FL note: Subband CQI/PMI is excluded because of the lack of support. Can discuss further
[Comments to 5-5-v1]


[Low] CSI-RS processing capability
[Agreements in the previous meetings]
The following figure is provided in the FLS for reference. The issues in this section are equivalent to Open issue 7 below. 


[Summary of contributions]
The discussion points for CPU related issues can be categorized before and after CSC:
CSI measurement before CSC
Number of CPUs
No proposals
CPU occupancy time
Start point: 
Alt. 1: one or more symbols starting from the last symbol of the uplink slot carrying the acknowledgment for the LTM configuration 
Alt. 2: SP CSI-RS: the first symbol after 3 msec of the last symbol of HARQ-ACK information for the semi-persistent CSI-RS activation MAC CE
Alt. 3: P CSI-RS: the first symbol of earliest CSI-RS resource after RRC configuration
End point
Alt. 1: the last symbol of the downlink slot carrying the cell switch command
Alt 2: the last symbol of the uplink slot carrying the acknowledgment for the cell switch command
Alt 3: if the CSI-RS is associated with target cell: the last symbol of the UL resource carrying the report
Alt 4: if the CSI-RS is not associated with target cell: the last symbol of HARQ-ACK corresponding to LTM CSC MAC CE.
Note: start and end point may be affected by the triggering mechanism
CSI reference resources
N/A
Active CSI-RS resources
Alt .1: CSI-RS resources for candidate cells provided by LTM-CSI-SSB-ResourceSet should be counted as active. 
Alt. 2: Periodic CSI-RS resources for candidate cells provided by LTM-CSI-SSB-ResourceSet should be counted as active when 
there is an activated TCI state in the cell and,
they are associated with an active CSI report configuration. 
Alt.3: Semi-persistent CSI-RS resources for candidate cells provided by LTM-CSI-SSB-ResourceSet should be counted as active when 
there is an activated TCI state in the cell,
the semi-persistent CSI-RS resources is activated, and 
they are associated with an active CSI report configuration. 
Alt.4: not counted as active
CSI measurement after CSC
Number of CPUs
No proposals
CPU occupancy time
Start point: 
Alt. 1: the first symbol after the PDSCH carrying the LTM CSC MAC CE
Alt. 2: the end of the PUCCH with HARQ-ACK corresponding to the PDSCH carrying the LTM CSC
Alt. 3: the first symbol of earliest CSI-RS resource after 3 msec of the last symbol of HARQ-ACK information for the LTM CSC MAC CE
Alt. 4: no need to be defined 
End point: 
Alt 1: the last symbol of the uplink resource carrying the initial CSI report
CSI reference resources
Alt. 1: Define reduced set of potential CSI reference resources.
If the CSI reference resource is still defined with respect to the uplink slot in which CSI is reported, the UE needs to calculate CSI for multiple potential CSI reference resources which could result in additional computation load. 
To avoid this, it may be necessary to modify the definition of CSI reference resource in time domain (e.g. every N slots) such that the number of possibilities is kept to reasonable level, while avoiding that the CSI report is excessively outdated.
Alt. 2: Define the following CSI reference resource for early CSI report of candidate cell for a CSI reporting in a first PUSCH in uplink slot ‘n’:
For Capability #1 UE (measurement only after CSC), the CSI reference resource is defined in time domain as , where  is the smallest value greater than or equal to  and no earlier than the last symbol of CSC MAC-CE command. 
For Capability #2 UE (measurement before and after CSC) , the CSI reference resource is defined in time domain as , where  is the smallest value greater than or equal to . 
Alt.3: Consider following 2 options
Option 1 – Use existing time constraints defined for DCI-triggered aperiodic CSI reporting by introducing a CSI reference resource associated with the report. FFS: Define CSI reference resource 
Option 2 – If there is at least one measurement RS occasion associated with the CSI reporting configuration after the measurement triggering point (i.e., application of the RRC configuration for early measurement or application of the cell switch command for baseline UE) such that the time gap between the RS occasion and the reporting slot is greater than a predefined duration (e.g., Z’).
FFS: An additional timeline requirement for the minimum duration between the triggering command and the reporting slot.
Definition of active CSI-RS resources
Alt .1: CSI-RS resources for candidate cells provided by LTM-CSI-SSB-ResourceSet and CSI-RS resources for serving cell provided by CSI-SSB-ResourceSet are counted as active
Others
UE Capability
RAN1 to clarify whether the number of active CSI-RS ports or active CSI-RS resources, in both the serving and target cells, for early CSI acquisition measurements should be counted towards the current maximum UE limit of active CSI-RS ports/resources or as a separate limit. 

[FL observation]
Due to the variety of discussion point for CPU related issues on CSI acquisition, FL sees the difficulties to progress the discussion considering other issues that have potential impacts on RAN2, i.e. RRC and/or MAC CE. Thus, no proposal is made for this issue at this meeting. 
[FL proposal 5-6-v1]
No FL proposal is made in this meeting. Companies are encouraged to analyze the proposals by companies until RAN1#121. 
[Comments to 5-6-v1 if any]



[Paused] Information provided by cell switch command
[Agreements in the previous meetings]
The following figure is provided in the FLS for reference. The issues in this section are equivalent to Open issue 4 below. 

[Summary of contributions]
ZTE:
CSI reporting configuration is determined by candidate cell ID same as target cell ID provided by Target Configuration ID field in LTM Cell Switch Command MAC CE.
CSI-RS resources for CSI measurement should be obtained by the determined CSI reporting configuration based on candidate cell ID same as target cell ID provided by Target Configuration ID field in LTM Cell Switch Command MAC CE if CSI-RS measurement is performed after reception of LTM cell switch command MAC CE.
Note that only one CSI reporting configuration is configured for a candidate cell.
CMCC
The Candidate Cell ID in the CSC MAC CE can be reused to activate the CSI report for CSI acquisition.
IDC
UE reports CSI of candidate cell according to the CSI report configuration associated to the TCI state indicated in the cell switch command.
OPPO
The UE can be requested to report the CSI measurement of target cell indicated by the CSC and the CSC indicate one explicit indicator to request the UE to report the corresponding CSI measurement.
Sharp
Support an additional field in the CSC MAC CE to explicitly indicate which CSI report configuration is to be applied.
NEC
The CSI report configuration for the target cell can be determined based on the Target Configuration ID indicated by the LTM CSC.
The CSI-RS resource (i.e., CMR) for the target cell can be determined based on the TCI state ID indicated by the LTM CSC.
Nokia
After the cell switch command, the UE acquires the CSI only associated with the target cell and the indicated TCI state.  
The cell switch command should indicate the report configuration to be used for reporting.
DOCOMO
For the selection of CSI resource(s) for measurement and a CSI report configuration for the report after reception of cell switch command, support the following.
CSI report configuration is associated with target configuration ID in cell switch command MAC CE.
CSI resource is the CSI-RS configured in the TCI state indicated in cell switch command MAC CE.
Qualcomm
Only a subset of CSI-RS resource(s) that are the same or QCLed with the QCL RS(s) in the activated/indicated TCI state(s) should be measured.

[FL observation]
Because the discussion here highly depends on the outcome of the configuration aspect discussed in section 5.5.3:
If Alt 1 (A single CSI report configuration is configured) is adopted
CSI report configuration is determined by candidate cell ID same as target cell ID provided by Target Configuration ID field in LTM Cell Switch Command MAC CE 
i.e. no new field in CSC is necessary
Else if Alt 2 (Multiple CSI report configurations can be configured) is adopted
CSI report configurations are determined by candidate cell ID same as target cell ID provided by Target Configuration ID field in LTM Cell Switch Command MAC CE
A solution to determine one CSI report configuration from the multiple report configurations is needed, e.g. introduce a new filed in CSC 
Then, 
If Alt X (A single CSI-RS resource for CMR is associated with a CSI report configuration) is adopted
A single CSI-RS resource can eventually be selected based on the target cell ID. 
Else if Alt Y (Multiple CSI-RS resources for CMR can be associated with a CSI report configuration) is adopted,
TCI state indicated in CSC can be used to down-select the CSI-RS resources for CSI measurement after CSC
same or QCLed with the QCL RS(s)
Another solution is just to use CRI – no down selection for CSI-RS resources by e.g. TCI state indicated in CSC
For our efficient discussion during the meeting, the discussion of this section is paused until FL proposal 5-3-1 is concluded.

[FL proposal 5-7-v1]
FL proposal will be made after FL proposal 5-3-1 is concluded: the discussion of this section is paused



Conditional intra-CU LTM
[Low] RAN1 spec impact of Conditional intra-CU LTM
[Agreements in the previous meetings]
None

[Summary of contributions]
vivo
Activated Candidate TCI state(s), other than the TCI state associated with the triggered beam, should be deactivated upon CLTM procedure being triggered.
CATT
No need to define beam application time for NR Rel-19 RACH-less C-LTM.
Ericsson
A high-level description of C-LTM should be added to TS 38.213 Section 21. The description should capture at least:
Configuration and evaluation of CLTM execution conditions in the UE,
A UE receiving TA value for the target cell by higher layer signalling or by UE-based TA estimation, applying the TA value in its initial uplink transmissions, if the TA value is valid.
TS 38.213 Section 21 should be updated to describe the following aspects of conditional LTM:
TCI state to be applied upon CLTM execution,
The timeline for CLTM execution.
In one alternative, the application time is defined to start at the time of the RS transmission occasion with which the C-LTM execution conditions are met.
Note that, to update this part in 38.213, RAN4 need to agree on the interruption time requirements for C-LTM

[FL observation]
FL thinks RAN1 needs some discussions how the timeline for C-LTM execution (i.e. beam application time in RAN1) is defined because current description refers to the timing of CSC as the starting point of beam application time. It is also noted that RAN2 may not consider this aspect in their discussion. 
For other part, FL understanding is that the editor of TS 38.214 can take care of capturing the agreement in RAN2. 

[FL proposal 6-1-v1]
Companies are encouraged to provide their views aiming at the consensus in RAN1#121
Whether and how to define the beam application time for C-LTM, especially the start timing
Option 1: beam application time is not defined for C-LTM
Option 2: the start timing (i.e. the timing of C-LTM is executed) is informed from higher layer
Option 3: the beam application time is defined to start at the time of the RS transmission occasion with which the C-LTM execution conditions are met
Other options are not precluded
FL note: this issue will not be treated during online/official offline discussion in RAN1#120bis. 

[Comments to 6-1-v1]

3GPP TSG RAN WG1 Meeting #120bis	R1-2502089
Wuhan, China, April 7th-11th, 2025
Source:		Moderator (Fujitsu)
Title:	FL summary 2 of Measurements related enhancements for LTM
Agenda Item:	9.9.1
Document for:	Information

Conclusion]
The following agreement was made during online discussion on Monda
Agreement
For candidate cell CSI acquisition
In addition to periodic CSI-RS resource, semi-persistent CSI-RS resource is supported 
Support of semi-persistent CSI-RS resource is subject to separate UE capability.
MAC CE is used to activate/deactivate the semi-persistent CSI-RS resource similarly to the legacy mechanism for a serving cell which will be specified in RAN2
Send an LS to RAN2 and RAN3 to inform this agreement
With this agreement, the discussion of this section is closed

[High] Configuration structure for CSI report and CSI-RS resource
[Agreements in the previous meetings]
Agreement(RAN1#120)
For target cell CSI acquisition, 
A UE is provided with RRC configurations for periodic CSI-RS resource(s) and CSI report(s) for one or more candidate cell
For a candidate cell,
down-select from the following alternatives:
Alt 1: A single CSI report configuration is configured
Alt 2: Multiple CSI report configurations can be configured
down-select from the following alternatives:
Alt X: A single CSI-RS resource for CMR is associated with a CSI report configuration
Alt Y: Multiple CSI-RS resources for CMR can be associated with a CSI report configuration
FFS : Semi-persistent CSI-RS resource
After the RRC configuration and before the reception of CSC, the UE may measure CSI based on the configured CSI-RS resource(s), which is subject to UE capability
FFS: whether or how to select a subset of CSI-RS resources to measure
FFS: when the UE may start measuring the configured CSI-RS resources
UE determines the CSI report configuration based on the CSC
After the reception of cell switch command, the UE may measure (depending on the timeline) CSI-RS resource(s) associated with determined CSI report configuration 
The latest available measured CSI on target cell resource(s) is conveyed at least by a single report, and the report is sent to the target cell
Option 1: to use UCI
Option 2: to use MAC CE
Note: with this agreement, the working assumption made in RAN1#119 is automatically confirmed.

[Summary of contributions]
Number of CSI-RS resource configurations and report configurations
The companies view on the number of report configs / CSI-RS resources are summarized as follows

Justifications for each alternative are summarized as follows:
Alt 1 + Alt X: Simple. Not necessary to have multiple configurations for CSI-RS resource and reporting as the reported CSI is used only for a short period
Alt 1 + Alt Y: Sufficiently flexible. The indication of report configuration can be simplified while sufficient flexibility for beam selection can be provided
Alt 2 + Alt Y: Fully flexible. Choice of report and CSI resource configuration is important for FR2

RRC structure
Even though very detailed proposals are provided by the companies, FL thinks that we can focus on the high-level discussion at this stage to help the rapporteur’s discussion 
CSI report configuration
Alt. 1-1: Provided under ServingCellConfig 
Justification: Same as in legacy report configuration
Alt. 1-2: Provided (somewhere) under LTM-config
Justification: Report configuration is provided/used for each candidate cells, and the report configuration should be kept even after cell switch
Nokia mentioned that outside of the ltm-CandidateConfig, though 
Note that RAN1 assumes the report configuration for CSI acquisition is shared between the source cell, the target cell and the UE, which may have RAN2 and RAN3 spec impact
CSI-RS resources, resource set and resource configurations
Alt. 2-1: LTM-CSI-ResourceConfig provides multiple CSI-RS resource sets for CSI acquisition, where each resource set is associated with different candidate cell
Alt. 2-2: LTM-CSI-ResourceConfig provides a single CSI-RS resource set for CSI acquisition, which includes multiple CSI-RS resources associated with each candidate cells
Resource set configuration for CSI acquisition is provided without repetition and trs-info parameters

[FL observation]
For the number of CS-RS resources and resource configurations, Alt 1 + Alt Y has slight majority support compared with other alternatives. FL understands that this combination gives a good balance between complexity and flexibility considering FR2 operation. 
As for the structure of CSI report configuration, FL agrees the report configuration is shared from target cell to the serving cell (and to UE) because the report is performed to the target cell while the configuration is conducted under the serving cell. With this fact, it would be straightforward to provide report configuration under LTM-config. The details on the structure can be discussed under rapporteur’s RRC parameter session. 
Finally for the relationship between resource set and resource configuration, FL thinks that having different resource set for each candidate cell is a natural interpretation from the agreement in RAN1#120, i.e. only report config(s) associated with the target cell is eventually used. Thus, Alt 2-1 above is proposed as a way forward. 
In summary the following two FL proposals can be made in this meeting. 
[FL proposal 5-3-1-v1]
FL note Alt 1 + Alt Y is chosen from the agreement at RAN1#120 because it has the majority support and good balance between flexibility and complexity
For a candidate cell, 
A single CSI report configuration is configured
Multiple CSI-RS resources for CMR can be associated with a CSI report configuration

[FL proposal 5-3-2-v1]
FL note: Alt 1-2 and 2-1 are chosen from the “Summary of contributions” above
CSI report configuration for LTM CSI acquisition is provided under LTM-config inside LTM-Candidate IE (but outside of the ltm-CandidateConfig), 
Note: RAN1 assumes the report configuration for CSI acquisition is shared between the source cell, the target cell and the UE
A LTM-CSI-ResourceConfig configuration provides multiple CSI-RS resource sets for CSI acquisition, where each resource set is associated with each candidate cell
Resource set configuration for CSI acquisition is provided without repetition and trs-info

[Comments to 5-3-1-v1 and 5-3-2-v1]

[FL proposal 5-3-1-v2]

FL note Alt 1 + Alt Y is chosen from the agreement at RAN1#120 because it has the majority support and good balance between flexibility and complexity
For a candidate cell, 
A single CSI report configuration is configured
Multiple CSI-RS resources for CMR can be associated with a CSI report configuration
FL note: introduction of IMR is not the scope of this section, and can be discussed separately

[To Chair: link to the list of online proposals]


[FL proposal 5-3-2-v2]
FL note: Alt 1-2 and 2-1 are chosen from the “Summary of contributions” above
CSI report configuration for LTM CSI acquisition is provided under LTM-config inside LTM-Candidate IE (but outside of the ltm-CandidateConfig), 
Note: RAN1 assumes the report configuration for CSI acquisition is shared between the source cell, the target cell and the UE

[To Chair: link to the list of online proposals]



[High] Subset of CSI-RS resources for CSI measurement before CSC
[Agreements in the previous meetings]
Agreement(RAN1#120)
For target cell CSI acquisition, 
A UE is provided with RRC configurations for periodic CSI-RS resource(s) and CSI report(s) for one or more candidate cell
For a candidate cell,
down-select from the following alternatives:
Alt 1: A single CSI report configuration is configured
Alt 2: Multiple CSI report configurations can be configured
down-select from the following alternatives:
Alt X: A single CSI-RS resource for CMR is associated with a CSI report configuration
Alt Y: Multiple CSI-RS resources for CMR can be associated with a CSI report configuration
FFS : Semi-persistent CSI-RS resource
After the RRC configuration and before the reception of CSC, the UE may measure CSI based on the configured CSI-RS resource(s), which is subject to UE capability
FFS: whether or how to select a subset of CSI-RS resources to measure
FFS: when the UE may start measuring the configured CSI-RS resources
UE determines the CSI report configuration based on the CSC
After the reception of cell switch command, the UE may measure (depending on the timeline) CSI-RS resource(s) associated with determined CSI report configuration 
The latest available measured CSI on target cell resource(s) is conveyed at least by a single report, and the report is sent to the target cell
Option 1: to use UCI
Option 2: to use MAC CE
Note: with this agreement, the working assumption made in RAN1#119 is automatically confirmed.

[Summary of contributions]
Regarding the additional mechanism to indicate the subset of CSI-RS for CSI acquisition (before CSC), companies’ views are summarized as follows: 
Issue 1-1: Whether or not such a mechanism is needed
Option 1-1: Specify a mechanism to indicate subset of CSI-RS resources for CSI measurement
Option 1-2: Can be left to UE implementation:
Option 1-3: Introduce UE capability on the number of candidate cell or CSI-RSs. Up to network configuration on top of that
Issue 1-2: Indication mechanism, if Option 1-1 above is supported
Introduce a new MAC CE
Reuse the existing field in DCI format, e.g. CSI request field
Implicitly indicated by candidate cell TCI state activation/deactivation MAC CE: 
Measure CSI-RS resource(s) associated with activated joint or DL TCI state for candidate cell
SP CSI-RS resource(s) are also implicitly activated
Implicitly indicate by a MAC CE for SP CSI-RS resources activation/deactivation
Implicitly indicated by the cell indicator field in PDCCH order
Another discussion point is the timing to start the CSI measurement before CSC. Related to this, it is also proposed to disable/enable CSI reporting together with CSI measurement 
Issue 2: Timing to start the CSI measurement before CSC
After RRC configuration 
After receiving a MAC CE to trigger CSI measurement 
After receiving candidate cell TCI state activation/deactivation MAC CE
UE implementation 
Issue 3: Activation/deactivation of CSI acquisition (i.e. measurement and reporting) 
a UE can be provided by the network whether a candidate cell is enabled or not for CSI acquisition

[FL observation]
As issue 1-1, 1-2 and 2 has some dependency, FL suggestion is focusing on issue 1-1 first and conclude in this meeting. On top of that, we can try our best to further narrow down the details for issues 1-2, 2 and 3 using the available remaining time.
For issue 1-1, FL analysis for each option is summarized as follows:
Option 1-1: Specify a mechanism to indicate subset of CSI-RS resources for CSI measurement
Justification: measurement overhead reduction at UE side
Concern: Additional spec impact (depending on the solution)
Option 1-2: Can be left to UE implementation:
Justification: simple, UE knows which TCI state is likely be selected from the L1-RSRP measurement results
Concern: gNB cannot control CSI measurement by a UE before CSC 
Option 1-3: Introduce UE capability on the number of candidate cell or CSI-RSs. Up to network configuration on top of that
Justification: This is a usual mechanism, and no specific solution is necessary.
Concern: RRC reconfiguration cannot be expected due to subsequent property for LTM
RAN1 is encouraged to select one option considering the benefit and drawback for each option. 

[FL proposal 5-4-v1]
Companies are encouraged to provide their view on the following proposal. 
For the subset selection of the measurement CSI-RS resource(s) from the configured CSI-RS resources before CSC, down-select one option from the following:
Option 1-1: Specify a mechanism to indicate subset of CSI-RS resources for CSI measurement
Option 1-2: Can be left to UE implementation:
Option 1-3: Introduce UE capability on the number of candidate cell or CSI-RS resources. On top of that gNB can configure appropriate CSI-RSs

[Comments to 5-4-v1]

[FL proposal 5-4-v2]
For the subset selection of the measurement CSI-RS resource(s) from the configured CSI-RS resources before CSC, down-select one option from the following:
Option 1: Specify a mechanism to indicate subset of CSI-RS resources for CSI measurement. Down-select one from the following alternatives in RAN1#121
Alt. 1 The subset is indicated by a new MAC CE 
Alt. 2 The subset is indicated by a DCI (e.g. cell indicator field for PDCCH order, CSI request field) 
Alt. 3 The subset is implicitly indicated by the Candidate cell TCI state activation/deactivation MAC CE 
Support: Fujitsu, Ericsson, IDC, Nokia, Samsung, vivo, ZTE, Lenovo, CATT, Xiaomi, Qualcomm, ETRI, 
Concern: OPPO, Huawei
Option 2: The subset selection can be left to UE implementation:
Option 3: Introduce UE capability on the number of candidate cell or CSI-RS resources. On top of that gNB can reconfigure appropriate CSI-RSs
Note: there are comments that this is always a valid option, but RRC reconfiguration is not aligned with the subsequent LTM concept

FL note: we can focus on whether to introduce Option 1 or not.
Concern was raised for Option 2 because gNB cannot manage CPU
Option 3 is not necessary to discuss as it is up to gNB

[To Chair: link to the list of online proposals]



[Mid] Contents of report and CSI-RS configurations
[Agreements in the previous meetings]
The following figure is provided in the FLS for reference. The issues in this section are equivalent to Open issue 1 below. 

[Summary of contributions]
Restrictions on the CSI configurations
Number of ports for CSI-RS resource
Up to 4: Spreadtrum
Up to 32: vivo
Up to 128 CMCC, Ericsson
Codebook configurations for report configuration
Type I: Spreadtrum, CATT, ZTE, Huawei, vivo, Nokia, OPPO, Ericsson, DOCOMO, Fujitsu, Google, CMCC, Apple
Rel-19 eType I: ZTE
Report quantity for report configuration
cri-RI-PMI-CQI: LG, CATT, ZTE, Huawei, Nokia, OPPO, Lenovo, Ericsson, Fujitsu, DOCOMO, Google, CMCC
cri-RI-PMI-CQI if SRS transmission is supported: ZTE, Fujitsu
CQI for Rank1 only: MediaTek
Report frequency configuration for report configuration
Wideband CQI/PMI: Huawei, CMCC, vivo, OPPO, Lenovo, Fujitsu, Ericsson, Nokia
Subband CQI/PMI: CMCC
Others
Samsung
Regarding the supported CSI reporting modalities (e.g. report quantities and codebooks/codebook configurations) for CSI acquisition for candidate cell(s), RAN1 should do at least the following: 
Feasibility assessment via various aspects of all the supported CSI reporting modalities in relation to the CSI-RS measurement aspects, in the context of the reception/application of LTM CSC and the corresponding RACH procedure before making down-selection
Benefit assessment via the customary system-level simulation with the user perceived throughout (UPT) statistics as the metrics, using L1-RSRP as the baseline, and fully reusing the Rel-19 CSI EVM (cf. AI 9.2.2). 
DOCOMO
Support one CMR in the report, i.e. IMR 
LG: 
LTM CSI-RS resource only dedicated for the CQI acquisition is not supported
[FL observation]
In this meeting, FL would like to suggest focusing on the issues that many companies are interested in. Considering the proposals by the companies, FL understands that the mechanism for CSI acquisition can be simplified to achieve a less complicated system design. Also, many companies proposed that excessive performance optimization is not important as the time period LTM CSI acquisition applied is very short. Given this analysis, it would be good idea to introduce some constraints for report and/or CSI-RS configurations. FL proposal is to take the options majority supports. 
[FL proposal 5-5-v1]
For the number of CSI-RS ports, select one option from the following for LTM CSI acquisition
Option 1. Up to 4: Spreadtrum
Option 2. Up to 32: vivo
Option 3. Up to 128 CMCC, Ericsson
For the codebook configurations in report configuration, only typeI-SinglePanel is supported for LTM CSI acquisition
FL note: Rel-19 eType I (ZTE) is excluded because of the lack of support. This can be discussed further offline/online
For the report quantity in report configuration, only cri-RI-PMI-CQI is supported for LTM CSI acquisition
FFS: whether the rank is limited to 1 (MTK) – This may also have some impact on the number of ports for CSI-RS resource. Can be discussed further online/offline
FL note: cri-RI-PMI-CQI is excluded as SRS is not proposed/supported for CSI acquistion
For report frequency configuration in report configuration, wideband CQI and wideband PMI are supported for LTM CSI acquisition
FL note: Subband CQI/PMI is excluded because of the lack of support. Can discuss further
[Comments to 5-5-v1]

[FL proposal 5-5-v2]
Alt 1: the following restriction is introduced
Supported by Fujitsu, IDC, Ericsson, Nokia, TCL, vivo, DOCOMO, Google, ZTE, Lenovo, NEC, LGE, Xiaomi, Xiaomi, Qualcomm, Huawei, Spreadtrum
For the number of CSI-RS ports for a candidate cell, select one option from the following for LTM CSI acquisition
Option 1. Up to 4: Spreadtrum
Option 2. Up to 32: vivo, Qualcomm
Option 3. Up to 128 CMCC, Ericsson
For the codebook configurations in report configuration, at least typeI-SinglePanel is supported for LTM CSI acquisition
For the report quantity in report configuration, only cri-RI-PMI-CQI is supported for LTM CSI acquisition
FFS: whether the rank is limited to 1 (MTK) – This may also have some impact on the number of ports for CSI-RS resource. Can be discussed further online/offline
For report frequency configuration in report configuration, wideband CQI and wideband PMI are supported for LTM CSI acquisition
Alt 2: no restriction is introduced
Supported by Samsung


[Low] CSI-RS processing capability
[Agreements in the previous meetings]
The following figure is provided in the FLS for reference. The issues in this section are equivalent to Open issue 7 below. 


[Summary of contributions]
The discussion points for CPU related issues can be categorized before and after CSC:
CSI measurement before CSC
Number of CPUs
No proposals
CPU occupancy time
Start point: 
Alt. 1: one or more symbols starting from the last symbol of the uplink slot carrying the acknowledgment for the LTM configuration 
Alt. 2: SP CSI-RS: the first symbol after 3 msec of the last symbol of HARQ-ACK information for the semi-persistent CSI-RS activation MAC CE
Alt. 3: P CSI-RS: the first symbol of earliest CSI-RS resource after RRC configuration
End point
Alt. 1: the last symbol of the downlink slot carrying the cell switch command
Alt 2: the last symbol of the uplink slot carrying the acknowledgment for the cell switch command
Alt 3: if the CSI-RS is associated with target cell: the last symbol of the UL resource carrying the report
Alt 4: if the CSI-RS is not associated with target cell: the last symbol of HARQ-ACK corresponding to LTM CSC MAC CE.
Note: start and end point may be affected by the triggering mechanism
CSI reference resources
N/A
Active CSI-RS resources
Alt .1: CSI-RS resources for candidate cells provided by LTM-CSI-SSB-ResourceSet should be counted as active. 
Alt. 2: Periodic CSI-RS resources for candidate cells provided by LTM-CSI-SSB-ResourceSet should be counted as active when 
there is an activated TCI state in the cell and,
they are associated with an active CSI report configuration. 
Alt.3: Semi-persistent CSI-RS resources for candidate cells provided by LTM-CSI-SSB-ResourceSet should be counted as active when 
there is an activated TCI state in the cell,
the semi-persistent CSI-RS resources is activated, and 
they are associated with an active CSI report configuration. 
Alt.4: not counted as active
CSI measurement after CSC
Number of CPUs
No proposals
CPU occupancy time
Start point: 
Alt. 1: the first symbol after the PDSCH carrying the LTM CSC MAC CE
Alt. 2: the end of the PUCCH with HARQ-ACK corresponding to the PDSCH carrying the LTM CSC
Alt. 3: the first symbol of earliest CSI-RS resource after 3 msec of the last symbol of HARQ-ACK information for the LTM CSC MAC CE
Alt. 4: no need to be defined 
End point: 
Alt 1: the last symbol of the uplink resource carrying the initial CSI report
CSI reference resources
Alt. 1: Define reduced set of potential CSI reference resources.
If the CSI reference resource is still defined with respect to the uplink slot in which CSI is reported, the UE needs to calculate CSI for multiple potential CSI reference resources which could result in additional computation load. 
To avoid this, it may be necessary to modify the definition of CSI reference resource in time domain (e.g. every N slots) such that the number of possibilities is kept to reasonable level, while avoiding that the CSI report is excessively outdated.
Alt. 2: Define the following CSI reference resource for early CSI report of candidate cell for a CSI reporting in a first PUSCH in uplink slot ‘n’:
For Capability #1 UE (measurement only after CSC), the CSI reference resource is defined in time domain as , where  is the smallest value greater than or equal to  and no earlier than the last symbol of CSC MAC-CE command. 
For Capability #2 UE (measurement before and after CSC) , the CSI reference resource is defined in time domain as , where  is the smallest value greater than or equal to . 
Alt.3: Consider following 2 options
Option 1 – Use existing time constraints defined for DCI-triggered aperiodic CSI reporting by introducing a CSI reference resource associated with the report. FFS: Define CSI reference resource 
Option 2 – If there is at least one measurement RS occasion associated with the CSI reporting configuration after the measurement triggering point (i.e., application of the RRC configuration for early measurement or application of the cell switch command for baseline UE) such that the time gap between the RS occasion and the reporting slot is greater than a predefined duration (e.g., Z’).
FFS: An additional timeline requirement for the minimum duration between the triggering command and the reporting slot.
Definition of active CSI-RS resources
Alt .1: CSI-RS resources for candidate cells provided by LTM-CSI-SSB-ResourceSet and CSI-RS resources for serving cell provided by CSI-SSB-ResourceSet are counted as active
Others
UE Capability
RAN1 to clarify whether the number of active CSI-RS ports or active CSI-RS resources, in both the serving and target cells, for early CSI acquisition measurements should be counted towards the current maximum UE limit of active CSI-RS ports/resources or as a separate limit. 

[FL observation]
Due to the variety of discussion point for CPU related issues on CSI acquisition, FL sees the difficulties to progress the discussion considering other issues that have potential impacts on RAN2, i.e. RRC and/or MAC CE. Thus, no proposal is made for this issue at this meeting. 
[FL proposal 5-6-v1]
No FL proposal is made in this meeting. Companies are encouraged to analyze the proposals by companies until RAN1#121. 
[Comments to 5-6-v1 if any]



[Paused] Information provided by cell switch command
[Agreements in the previous meetings]
The following figure is provided in the FLS for reference. The issues in this section are equivalent to Open issue 4 below. 

[Summary of contributions]
ZTE:
CSI reporting configuration is determined by candidate cell ID same as target cell ID provided by Target Configuration ID field in LTM Cell Switch Command MAC CE.
CSI-RS resources for CSI measurement should be obtained by the determined CSI reporting configuration based on candidate cell ID same as target cell ID provided by Target Configuration ID field in LTM Cell Switch Command MAC CE if CSI-RS measurement is performed after reception of LTM cell switch command MAC CE.
Note that only one CSI reporting configuration is configured for a candidate cell.
CMCC
The Candidate Cell ID in the CSC MAC CE can be reused to activate the CSI report for CSI acquisition.
IDC
UE reports CSI of candidate cell according to the CSI report configuration associated to the TCI state indicated in the cell switch command.
OPPO
The UE can be requested to report the CSI measurement of target cell indicated by the CSC and the CSC indicate one explicit indicator to request the UE to report the corresponding CSI measurement.
Sharp
Support an additional field in the CSC MAC CE to explicitly indicate which CSI report configuration is to be applied.
NEC
The CSI report configuration for the target cell can be determined based on the Target Configuration ID indicated by the LTM CSC.
The CSI-RS resource (i.e., CMR) for the target cell can be determined based on the TCI state ID indicated by the LTM CSC.
Nokia
After the cell switch command, the UE acquires the CSI only associated with the target cell and the indicated TCI state.  
The cell switch command should indicate the report configuration to be used for reporting.
DOCOMO
For the selection of CSI resource(s) for measurement and a CSI report configuration for the report after reception of cell switch command, support the following.
CSI report configuration is associated with target configuration ID in cell switch command MAC CE.
CSI resource is the CSI-RS configured in the TCI state indicated in cell switch command MAC CE.
Qualcomm
Only a subset of CSI-RS resource(s) that are the same or QCLed with the QCL RS(s) in the activated/indicated TCI state(s) should be measured.

[FL observation]
Because the discussion here highly depends on the outcome of the configuration aspect discussed in section 5.5.3:
If Alt 1 (A single CSI report configuration is configured) is adopted
CSI report configuration is determined by candidate cell ID same as target cell ID provided by Target Configuration ID field in LTM Cell Switch Command MAC CE 
i.e. no new field in CSC is necessary
Else if Alt 2 (Multiple CSI report configurations can be configured) is adopted
CSI report configurations are determined by candidate cell ID same as target cell ID provided by Target Configuration ID field in LTM Cell Switch Command MAC CE
A solution to determine one CSI report configuration from the multiple report configurations is needed, e.g. introduce a new filed in CSC 
Then, 
If Alt X (A single CSI-RS resource for CMR is associated with a CSI report configuration) is adopted
A single CSI-RS resource can eventually be selected based on the target cell ID. 
Else if Alt Y (Multiple CSI-RS resources for CMR can be associated with a CSI report configuration) is adopted,
TCI state indicated in CSC can be used to down-select the CSI-RS resources for CSI measurement after CSC
same or QCLed with the QCL RS(s)
Another solution is just to use CRI – no down selection for CSI-RS resources by e.g. TCI state indicated in CSC
For our efficient discussion during the meeting, the discussion of this section is paused until FL proposal 5-3-1 is concluded.

[FL proposal 5-7-v1]
FL proposal will be made after FL proposal 5-3-1 is concluded: the discussion of this section is paused



Conditional intra-CU LTM
[Low] RAN1 spec impact of Conditional intra-CU LTM
[Agreements in the previous meetings]
None

[Summary of contributions]
vivo
Activated Candidate TCI state(s), other than the TCI state associated with the triggered beam, should be deactivated upon CLTM procedure being triggered.
CATT
No need to define beam application time for NR Rel-19 RACH-less C-LTM.
Ericsson
A high-level description of C-LTM should be added to TS 38.213 Section 21. The description should capture at least:
Configuration and evaluation of CLTM execution conditions in the UE,
A UE receiving TA value for the target cell by higher layer signalling or by UE-based TA estimation, applying the TA value in its initial uplink transmissions, if the TA value is valid.
TS 38.213 Section 21 should be updated to describe the following aspects of conditional LTM:
TCI state to be applied upon CLTM execution,
The timeline for CLTM execution.
In one alternative, the application time is defined to start at the time of the RS transmission occasion with which the C-LTM execution conditions are met.
Note that, to update this part in 38.213, RAN4 need to agree on the interruption time requirements for C-LTM

[FL observation]
FL thinks RAN1 needs some discussions how the timeline for C-LTM execution (i.e. beam application time in RAN1) is defined because current description refers to the timing of CSC as the starting point of beam application time. It is also noted that RAN2 may not consider this aspect in their discussion. 
For other part, FL understanding is that the editor of TS 38.214 can take care of capturing the agreement in RAN2. 

[FL proposal 6-1-v1]
Companies are encouraged to provide their views aiming at the consensus in RAN1#121
Whether and how to define the beam application time for C-LTM, especially the start timing
Option 1: beam application time is not defined for C-LTM
Option 2: the start timing (i.e. the timing of C-LTM is executed) is informed from higher layer
Option 3: the beam application time is defined to start at the time of the RS transmission occasion with which the C-LTM execution conditions are met
Other options are not precluded
FL note: this issue will not be treated during online/official offline discussion in RAN1#120bis. 

[Comments to 6-1-v1]

3GPP TSG RAN WG1 Meeting #120bis	R1-2502090
Wuhan, China, April 7th-11th, 2025
Source:		Moderator (Fujitsu)
Title:	FL summary 3 of Measurements related enhancements for LTM
Agenda Item:	9.9.1
Document for:	Information

Conclusion]
Only one comment is provided in this meeting. Companies are encouraged to further consider the impact of CLTM in RAN1 until the next meeting. With this, the discussion of this section is closed.

Others
[Super High] Very important & urgent issue for mobility
[FL proposal 7-1-v1]
Observation
Mobility Chair has never joined mobility dinner 
Now there is no reason to decline as RANp election has been finished
Mobility Chair currently tries to allocate an online session on Friday
Mobility people think this is a punishment
With these facts, mobility friends are unsatisfied
Way forward
Mobility Chair to join the mobility dinner on Wednesday in Malta
No mobility session on Friday
Supported by
Rapporteur, Ex-mobility Chair (he has confirmed to join the dinner in Malta), Feature lead
Huawei, Fujitsu, Lenovo, NTT DOCOMO, CATT, vivo, ETRI, ZTE, Ericsson, MediaTek, NOKIA, Google, InterDigital, Samsung, CMCC, Qualcomm

3GPP TSG RAN WG1 Meeting #120bis	R1-2502091
Wuhan, China, April 7th-11th, 2025
Source:		Moderator (Fujitsu)
Title:	Final FL summary of Measurements related enhancements for LTM
Agenda Item:	9.9.1
Document for:	Information

Conclusion]
The following way forward was agreed on Thursday.
Way forward
Mobility Chair to join the mobility dinner on Wednesday in Malta
No mobility session on Friday
FL would like to thank all the mobility friends for the active discussions, constructive attitude and enjoyable dinner event. With this, the discussion in this meeting is closed.

3GPP TSG RAN WG1#120bis                                                             R1-2502111
Wuhan, China, April 07th -11th, 2025

Agenda Item:	9.9.1
Source:	Lenovo
Title:	Measurement related enhancements for LTM
Document for:	Discussion

Conclusion
In this contribution, we have following proposals to support the CSI-RS based beam report for LTM:
Proposal 1: Each CSI-RS resource associated with an LTM-CSI-ReportConfig is QCLed with an SSB associated with a same LTM-Candidate-ID.
Proposal 2: If the QCLed SSB for a CSI-RS from a candidate cell is not detected by the UE, the UE shall not measure the CSI-RS.
Proposal 3: Study the DL synchronization procedure for CSI-RS reception from candidate cells before cell switch command.

Proposal 4: The CSI-RS resources from different candidate cells but associated with a same LTM-CSI-ReportConfig should be configured with a same bandwidth.

Proposal 5: Support group based beam report for LTM CSI report to enable the multi-TRP operation after switch to the new serving cell.
FFS: whether the number of candidate cells is restricted to two.

Further, we provide the following proposals on the early CSI acquisition:
Proposal 6: One or more CSI report configuration can be configured on a serving cell for early CSI acquisition for LTM, where one or more CSI-RS resource sets are associated with a CSI report configuration and each CSI-RS resource set contains CSI-RS resources associated with a candidate cell.
Proposal 7: Support semi-persistent CSI-RS resource for early CSI acquisition for LTM.
Proposal 8: The UE only measure CSI based on the CSI-RS resources associated with activated joint or DL TCI state for a candidate cell when at least one joint or DL TCI state is activated for the candida cell.
Proposal 9: The UE only need to report the CSI corresponding to the CSI-RS resource associated with the indicated TCI state indicated in the CSC for the target cell.

Proposal 10: RAN1 should first determine whether the CSI should be transmitted in the first UL transmission and then discuss the corresponding measurement behavior.
Proposal 11: The LTM CSI report is carried by UCI.
Proposal 12: At least support wideband CSI acquisition including WB CQI, RI and WB PMI acquisition for candidate cells before cell switch for LTM. FFS: support of subband CSI acquisition.

Additionally, we have the following proposals to support event triggered beam report for LTM
Proposal 13: Candidate cell beam set can be configured for the LTM CSI report configuration for Event LTM2, and the UE reports N beam selected from the candidate cell beam set in the MR MAC CE.
Proposal 14: Only one event corresponding to a LTM CSI report configuration is reported in the MR MAC CE. 
Proposal 15: Further study the CSI reference resource for MAC CE based beam report.

3GPP TSG RAN WG1 Meeting #120bis	R1-2502132
Wuhan, China, April 7th – 11th, 2025	
Source:	Fujitsu
Title:	Discussion on measurement related enhancements for LTM
Agenda Item:	9.9.1
Document for:	Discussion

Conclusion
In this contribution, we provide our views as below.
Proposal 1: RAN1 confirms that the network can configure which RS type is used for LTM event evaluation including the event LTM2.

Proposal 2: For CPU occupation duration for the event triggered reporting, the CPU occupation duration starts from the earliest one of each transmission occasion of periodic CSI-RS/SSB resource until symbols after the transmission occasion. 

Proposal 3: For resource and report configuration for CSI acquisition, support 
Alt 1: A single CSI report configuration is configured
Alt Y: Multiple CSI-RS resources for CMR can be associated with a CSI report configuration

Proposal 4: CSI report configuration for each candidate cell is provided under LTM-Config.

Proposal 5: For CSI-RS resource set configuration, CSI-RS resource(s) in a single resource set can be associated with only one candidate cell.

Proposal 6: For CSI acquisition, only support
'cri-RI-CQI' and 'cri-PMI-RI-CQI',
wideband,
limit the number of antenna ports to X, and
codebook type to ‘r15-typeI-SinglePanel’
Proposal 7: Support semi-persistent CSI-RS resource for CSI acquisition

Proposal 8: Support the indication of cell index of the candidate cells to be measured for CSI acquisition before reception of CSC.
No need to introduce the indication of the measurement start.

Proposal 9: Introduce a new signalling with MAC CE to indicate which candidate cell(s) the UE is required to monitor (or not to monitor) for CSI acquisition

Proposal 10: Support UCI to carry CSI report for CSI acquisition.

Proposal 11: For CSI reporting method considering CSI timeline, support to transmit indication to the target cell by reporting Out-of-Range in CQI field, and to transmit CSI report on multiple PUSCHs.
OoR is transmitted on the PUSCH(s) during the timeline is not met
CSI report is transmitted on the rest of PUSCH(s) during the timeline is met
The number of the concatenated PUSCH(s) can be indicated by RRC.

Proposal 12: 
For RACH-less LTM, support the first PUSCH transmission scheduled by CG or DG as a report container of CSI acquisition.
For RACH-based LTM, support at least the first PUSCH scheduled by RAR as a report container of CSI acquisition.

3GPP TSG RAN WG1 #120bis			R1-2502172
Wuhan, China, April 7th – 11th, 2025


Agenda item:	9.9.1
Title:	Discussion on measurements related enhancements for LTM
Source:	CMCC
Document for:	Discussion and Decision

1. 

Conclusion
Based on the above discussions, the proposals are as follows:
Proposal 1: For a candidate cell, support Alt 1: A single CSI report configuration is configured.
Proposal 2: For a candidate cell, support Alt Y: Multiple CSI-RS resources for CMR can be associated with a CSI report configuration.
Proposal 3: Support semi-persistent CSI-RS for CSI acquisition.
Proposal 4: The Candidate Cell ID in the CSC MAC CE can be reused to activate the CSI report for CSI acquisition.
Proposal 5: The CSI report is carried on UCI and transmitted on the first PUSCH carrying RRC reconfiguration complete message.
Proposal 6: Support Type I codebook-based CSI report with CRI, CQI, PMI and RI.
Proposal 7: For CQI and PMI reporting, support both wideband and sub-band report.
Proposal 8: Support up to 128 CSI-RS ports.

4. 

3GPP TSG RAN WG1 #120bis	R1-2502201
Wuhan, China, April 7th – 11th, 2025

Agenda item:	9.9.1
Source:	NEC
Title:              	Discussion on measurements related enhancements for LTM
Document for:	Discussion and Decision

Conclusion
In this contribution, we provided our views on measurements related enhancements for LTM. Specifically, we have the following observations and proposals:
Proposal 1: Support simultaneous configuration of both UE event triggered report and any of NW triggered periodic/semi-persistent/aperiodic report.
Proposal 2: Support simplified event-triggered L1 measurement reporting for LTM candidate cells with limited event types.
Proposal 3: Specify measurement value thresholds for the start or stop of event triggered L1 measurement reporting.
Proposal 4: Support event triggered measurement reporting with optional TCI state indication.
Proposal 5: Support event triggered measurement reporting with optional CFRA resource indication and UL access resource selection.
Observation 1: If a single report quantity (e.g., cri-RI-PMI-CQI) is considered sufficient to acquire CSI for the candidate cell, configuring a single CSI report configuration for a candidate cell should be adequate, i.e., Alt 1: A single CSI report configuration is configured.
Proposal 6: For configuration of CSI-RS resources associated with CSI report configuration, support the following:
Alt Y: Multiple CSI-RS resources for CMR can be associated with a CSI report configuration
Proposal 7: The CSI report configuration for the target cell can be determined based on the Target Configuration ID indicated by the LTM CSC.
Proposal 8: The CSI-RS resource (i.e., CMR) for the target cell can be determined based on the TCI state ID indicated by the LTM CSC.
Proposal 9: Support UCI-based CSI feedback for LTM CSI acquisition.
Proposal 10: For conditional LTM, study the determination of TCI state applied for the target cell.
Proposal 11: Support to introduce MAC CE to activate/deactivate the candidate cells configured in the LTM measurement report.
Observation 2: As an alternative, the existing mechanism (e.g., semi-persistent reporting is associated with different resource set) would require NW to initially configure a huge number of LTM measurement reports to associate with all possible combinations of different candidate cells, which is unnecessary and wasteful.

3GPP TSG RAN WG1 #120bis                         			   		R1-2502206
Wuhan, China, April 7th – 11th, 2025

Agenda Item:	9.9.1
Source:	InterDigital, Inc.
Title:	Measurements related enhancements for LTM
Document for:	Discussion and Decision

Conclusion
This contribution discussed further details of CSI acquisition on candidate cell(s) before or during LTM cell switch. The following proposals are made:
Proposal 1: Multiple CSI report configurations for CSI acquisition can be configured for a candidate cell.
Proposal 2: Multiple CSI-RS resources for channel measurement can be configured can be associated with a CSI report configuration
Proposal 3: Single CSI-RS resource set for channel measurements is associated with a CSI report configuration.
Proposal 4: UE reports CSI of candidate cell according to the CSI report configuration associated to the TCI state indicated in the cell switch command.
Proposal 5: RAN1 assumes that UE starts measurements for a CSI report configuration no later than upon reception of MAC CE activating candidate TCI state associated to this CSI report configuration.
Proposal 6: Support MAC CE as container for CSI in target cell.
Proposal 7: If RAN1 agrees on UCI as container for CSI in target cell, support UE indication of if/when CSI is available in the first transmission after cell switch.
Proposal 8: Specify reduced set of potential CSI reference resources.

3GPP TSG-RAN WG1 Meeting #120bis	R1-2502214
Wuhan, China, April 7th - 11th, 2025

Agenda Item:	9.9.1
Source:	Huawei, HiSilicon
Title:	Measurements related enhancements for LTM
Document for:	Discussion and Decision

Summary and conclusion
In this contribution, we have following proposals: 
Proposal 1: Support to always configure the field of “repetition” as “off” for NZP-CSI-RS resource set configured per candidate cell in LTM-candidate.
Proposal 2: In the resource set configured for candidate cell RSRP measurement, a sequence of CSI-RS resource indices and a sequence of candidate cell indices are included, with each CSI-RS resource index associated with one candidate cell index.
Proposal 3: The time domain property (i.e., periodic or semi-persistent) of CSI-RSs associated with the same LTM CSI report should be same.
Proposal 4: Support to activate or deactivate all the CSI-RS resources from multiple candidate cells configured in LTM-CSI-ResourceConfig associated with the LTM CSI report by MAC CE.
Proposal 5: For a candidate cell, a single CSI report configuration is configured, i.e. Alt 1.
Proposal 6: A single CSI-RS resource for CMR is associated with a CSI report configuration of the candidate cell, i.e. Alt X. 
Proposal 7: Semi-persistent CSI-RS should be supported for CSI acquisition before and duration LTM cell switch. 
Proposal 8: MAC CE-based activation mechanism before CSC can be reused to activate CSI measurement on SP CSI-RS before CSC. 
Proposal 9: The activated semi-persistent CSI-RS resource(s) of cells other than the target cell are deactivated automatically after CSC. 
Proposal 10: Semi-persistent CSI-RS measurement after CSC can be automatically activated by CSC.
Proposal 11: Support UCI-based CSI reporting to target cell after reception of LTM CSC MAC CE.
Proposal 12: For CFRA based LTM cell switch, CSI report can be reported on PUSCH scheduled by RAR UL grant or PUSCH of MsgA to target cell. 
Proposal 13: For CBRA based LTM cell switch, CSI reporting is carried in the first UL channel after RA procedure is successfully completed to target cell.
Proposal 14: For RACH-less LTM cell switch, CSI reporting is carried in the first UL channel (either CG-based or DG-based PUSCH).
Proposal 15: If CSI measurement results is not ready to be transmitted in MSG3/MSGA/first UL channel, UE reports special CQI index in UCI in MSG3/MSGA/first UL channel to inform gNB when UE expects NW to re-schedule another aperiodic resource for valid CSI reporting.
Proposal 16: For the CSI report before or during the LTM cell switch, at least cri-RI-PMI-CQI with wideband CQI/PMI and Type-I codebook should be supported. 
Proposal 17: For CSI measurement before CSC, the start of CPU occupancy time of CSI report associated with semi-persistent CSI-RS can be from the first symbol after 3 msec of the last symbol of HARQ-ACK information for the semi-persistent CSI-RS activation MAC CE.
Proposal 18: For CSI measurement before CSC, the start of CPU occupancy time of CSI report associated with periodic CSI-RS can be from the first symbol of earliest CSI-RS resource after RRC configuration.
Proposal 19: For CSI measurement before CSC, the end of CPU occupancy time depends on whether CSI report is associated with CSI-RS resource from target cell.
If a CSI report is associated with CSI-RS resource from target cell, the end of CPU occupancy time can be the last symbol of the UL resource carrying the report.
If a CSI report is associated with CSI-RS resource from non-target cell, the end of CPU occupancy time can be the last symbol of HARQ-ACK corresponding to LTM CSC MAC CE.
Proposal 20: For CSI measurement after CSC, the occupied CPU can be from the first symbol of earliest CSI-RS resource after 3 msec of the last symbol of HARQ-ACK information for the LTM CSC MAC CE until the last symbol of the UL resource carrying the report.
Proposal 21: To support CSI-RS based measurement and report for R19 LTM, at least the RRC parameters in Table 1 should be introduced.

3GPP TSG RAN WG1 #120bis		R1-2502298
Wuhan, China, April 7th – 11th, 2025

Source:	OPPO
Title:	Discussions on measurement enhancement for LTM
Agenda Item:	9.9.1
Document for:	Discussion and Decision

Conclusions
In this contribution, we present our views on UE-initiated beam reporting and the following proposals are made:
Proposal 1: When the serving cell is configured with mTRP and has two indicated joint/DL TCI states:
The UE derive two RSs for serving cell evaluation and each RS is from the QCL RS or the SSB that the QCL RS is QCLed to of each indicated joint/DL TCI state.
The L1-RSRP measurement of serving cell for event evaluation is the minimum value of the L1-RSRP measurement of those two RSs.
Proposal 2: UE reports one indicator to indicate which LTM event is triggered in LTM event-triggering reporting.
Proposal 3: For event LTM 2, the UE reports the L1-RSRP measurement of the RS corresponding to the indicated TCI state of serving cell.
The reported L1-RSRP measurement can be a differential L1-RSRP measurement with a reference to the corresponding threshold
Proposal 4: For event LTM 3, the UE reports:
The L1-RSRP measurement of all the beam evaluation RSs of candidate cell that satisfy the event LTM 3 trigger condition and their corresponding CRI/SSBRIs
the L1-RSRP measurement of serving cell.
The reported L1-RSRP measurement of candidate cell is differential L1-RSRP with a reference to the L1-RSRP of the serving cell.
Proposal 5: For event LTM 4, the UE reports the L1-RSRP measurement of all the beam evaluation RSs of candidate cell that satisfy the event LTM 4 trigger condition and their corresponding CRI/SSBRI
UE reports the differential L1-RSRP of each reported CRI/SSBRI with a reference to the configured L1-RSRP threshold
Proposal 6: For event LTM 5, the UE reports:
The differential L1-RSRP of each RS of candidate cell that satifies the condition of event LTM 5 with reference to the L1-RSRP threshold configured for candidate cell and the corresponding CRI/SSBRI.
The differential L1-RSRP of serving cell with reference to the L1-RSRP threshold configured for serving cell.
Proposal 7: For a candidate cell, support to configure one CSI report configuration.
Proposal 8: For a candidate cell, the system can configure one or more NZP CSI-RS resources for CMR and also IMR.
Proposal 9: For the UE supporting UE capability of measuring CSI of candidate cell before CSC, the system can use a MAC CE message to request the UE to measure CSI of one candidate cell.
Proposal 10: The UE can be requested to report the CSI measurement of target cell indicated by the CSC and the CSC indicate one explicit indicator to request the UE to report the corresponding CSI measurement.
Proposal 11: For CSI measurement of candidate cell:
Only support Type 1 single-panel codebook
Support wideband PMI, CQI and RI reporting
One NZP CSI-RS resource can be configured for CSI resource for a candidate cell.
Proposal 12: The UE reports the CSI measurement of target cell through a UCI multiplexed in the first PUSCH transmission in target cell.

3GPP TSG RAN WG1 #120bis	        	R1-2502329
Wuhan, China, April 7th – 11th, 2025

Agenda Item:					    9.9.1
Source:	Sony
Title:	Measurements related enhancements for LTM
Document for:	Discussion

Conclusions
The following proposals were made in this contribution.
Proposal 1: Support Alt 2: Multiple CSI report configuration can be configured.
Proposal 2: Both option 1 (to use UCI) and option 2 (to use MAC CE) should be supported.

3GPP TSG RAN WG1 #120bis	        		             R1-2502382
Wuhan, China, April 7th – 11th, 2025
Agenda item:	9.9.1
Source: 	Samsung
Title: 	Views on Rel-19 measurement related enhancements for LTM
Document for:	Discussion and Decision

Conclusions 
In this contribution, we provide our views on various design aspects related to Rel-19 LTM operations, focusing on necessary components to support CSI-RS for LTM measurement/reporting, event triggered L1 measurement reporting and CSI acquisition on candidate cell(s). In particular, we present the following proposals and observations focusing on various design aspects related to the Rel-19 LTM enhancements:

Proposal 1: To support CSI-RS measurements for LTM procedures, specify procedure(s) for associating between the measurement CSI-RS resources and candidate cells.
Alt1 (implicit association): association between the configured CSI-RS resource(s) and the candidate cell(s) can be based on association between the SSBs (QCL’ed with the configured CSI-RS resource(s)) and the candidate cells
Alt2 (explicit association): each of the configured CSI-RS resource(s) is associated to an entry (a candidate cell ID) in the ltm-CandidateIdList – detailed signalling design is up to RAN2

Proposal 2: To support CSI-RS measurements for LTM procedures, support UE to measure the CSI-RS based on the timing of the associated candidate cell if the associated SSB in the candidate cell is provided for the CSI-RS.
	
Proposal 3: For gNB scheduled reporting and event triggered reporting, support shared CSI-RS resource for both LTM and L3 mobility, e.g., the CSI-RS introduced for LTM measurement can be configured for L3 mobility as well.

Proposal 4: For CSI acquisition, 
a UE can be provided by the network whether a candidate cell is enabled or not for CSI acquisition, and
for CSI measurement before CSC MAC CE, study mechanism for limit total CSI acquisition for candidate cell(s) by the same UE before cell switching command. e.g. based on UE capabilities.

Proposal 5: For CSI acquisition for candidate cell during LTM, the UE only needs to keep/store CSI for a limited number of candidate cell(s) before cell switching command, subject to corresponding UE’s capabilities.

Proposal 6: The CSI-RS resource configuration(s) for CSI acquisition can be similarly provided relative to the CSI-RS resource configuration(s) for L1 measurement and reporting for Rel-19 mobility enhancements.

Proposal 7: Regarding CSI acquisition, support semi-persistent, and aperiodic CSI-RS(s) for CSI acquisition in addition to periodic configuration.
For SP/AP CSI-RS(s) for CSI acquisition, at least the following aspects should be specified 
When the trigger/activation would occur relative to the application of the LTM CSC considering the CSI processing timeline (e.g. Z/Z’)
Detailed signalling medium(s) and method(s) for activation/triggering

Proposal 8: For CSI acquisition, 
support the UE to send the CSI report at least a time gap after reception of the LTM CSC,
for both RACH-less and RACH-based LTM procedures, support the first CG/DG PUSCH that carries the RRC completion message to carry the CSI report

Proposal 9: In terms of UL container to carry the CSI report, support UCI (Option-1).

Proposal 10: Supporting CSI acquisition on candidate cell(s) after reception of LTM CSC MAC CE should be based on new UE capabilities.  

Proposal 11: Regarding the supported CSI reporting modalities (e.g. report quantities and codebooks/codebook configurations) for CSI acquisition for candidate cell(s), RAN1 should do at least the following: 
Feasibility assessment via various aspects of all the supported CSI reporting modalities in relation to the CSI-RS measurement aspects, in the context of the reception/application of LTM CSC and the corresponding RACH procedure before making down-selection
Benefit assessment via the customary system-level simulation with the user perceived throughout (UPT) statistics as the metrics, using L1-RSRP as the baseline, and fully reusing the Rel-19 CSI EVM (cf. AI 9.2.2). 

3GPP TSG RAN WG1 #120bis                                     	      R1-2502453
Wuhan, China, April 7th – 11th, 2025

Agenda Item:	9.9.1
Source:	Xiaomi 
Title:                     Discussion on measurements related enhancements for LTM
Document for:	Discussion and Decision

Conclusion
In this contribution, we discuss about the event-triggered measurement reporting for LTM. Based on above discusses, we provide the following proposals.
Proposal 1: Support Alt 1 combined with Alt Y, i.e., A single CSI report configuration with multiple CSI-RS resources for CMR is configured for one candidate cell.
Proposal 2: UE selects the measured candidate cell and measured CSI-RS resource based on the L1-RSRP ordering.
Proposal 3: Event-triggered CSI measurement can be introduced.
Proposal 4: Support aperiodic CSI reporting triggered by LTM cell switch command MAC CE.
Proposal 5: Support to confirm the WA.
Proposal 6: CSI report of target cell can be reported on the PUSCH during random access procedure to target cell at least for LTM cell switch based on CFRA. 
Proposal 7: For RACH-less LTM cell switch, UE reports the CSI report on the earliest available PUSCH on target cell.
Proposal 8: Reuse UCI for CSI report of the target cell.

3GPP TSG RAN WG1 #120bis	R1-2502490
Wuhan, China, 07th - 11th April 2025

Source:	Sharp
Title:	Discussion on measurements related enhancements for LTM 
Agenda item:	9.9.1
Document for: 	Discussion

Conclusions
In this contribution, we discussed the issues regarding enhancement of measurements to support LTM which includes CSI-RS measurements and report for LTM procedures and event triggered L1 measurement report. And we have proposals as follows.
 Alt 2 (i.e., Multiple CSI report configurations can be configured) offers greater flexibility for the gNB compared to Alt 1 (i.e., A single CSI report configuration is configured), as it allows the network to configure different types of report content and different associated CSI-RS resources.
Alt X (i.e., A single CSI-RS resource for CMR is associated with a CSI report configuration) reduces the UE's reporting overhead compared to Alt Y (i.e., Multiple CSI-RS resources for CMR can be associated with a CSI report configuration) since only a single set of CSI-RS resources need to be reported.
Support Alt 2+Alt X (i.e., Multiple CSI report configurations can be configured and a single CSI-RS resource for CMR is associated with a CSI report configuration) for CSI acquisition, as it balances gNB flexibility while minimizing UE reporting overhead. 
Support an additional field in the CSC MAC CE to explicitly indicate which CSI report configuration is to be applied.
Support implementing a strategy that allows the UE to measure only a subset of CSI-RS resources.
Consider one of the following methods to select a subset of CSI-RS resources
MAC CE to activate/deactivate a subset of CSI-RS resources
DCI field to indicate a subset of CSI-RS resources
Support using UCI as the CSI reporting container due to efficiency and consistency.
Whether to multiplex UCI on the first transmission can be explicitly indicated.
The UE does not expect to be configured with both event-triggered LTM L1 measurement report and network-triggered LTM L1 measurement report at the same time to avoid LTM L1 report duplication.

3GPP TSG RAN WG1 #120bis                                       R1-2502518
Wuhan, China, April 7th– 11th, 2025
Source: 	ETRI
Title:	Discussion on measurements related enhancements for LTM
Agenda Item:	9.9.1
Document for:	Discussion/Decision

Conclusion
In this contribution, we note the following observations and proposals.

Observation 1:
In DG-based reporting, separate transmission of the RRCReconfigurationComplete and CSI report may increase latency due to additional UL scheduling. In contrast, CG-based reporting supports both separate and multiplexed transmissions with negligible timing difference.

Observation 2:
Maintaining transmission quality depends on the timing of CSI report reception, not on the reception timing of the RRCReconfigurationComplete. Therefore, multiplexing in DG-based reporting offers a time-efficient solution.

Observation 3:
The Capable UE stores CSI measured before CSC MAC CE reception and multiplexes it with the RRCReconfigurationComplete message on the first available UL resource. In DG-based reporting, the DCI indicates CSI presence by setting the "CSI request" field to '1'.

Observation 4:
The CSC MAC CE can serve as an effective trigger for both initiating and terminating CSI measurement and reporting procedures, reducing the need for additional signaling such as SP CSI-RS activation/deactivation MAC CEs or CG activation DCI.

Observation 5:
Configuring periodic CSI reporting with CG type 1 in the RRCReconfiguration message for multiple candidate cells leads to inefficient UL resource usage, especially when the candidate cells are not ultimately selected as the target.

Observation 6:
UCI-based CSI reporting enables lower latency and reduced complexity, as it aligns naturally with L1 measurement and existing procedures, while MAC CE introduces unnecessary overhead and spec impact without significant benefit for typical CSI content.

Observation 7:
Periodic and semi-persistent CSI reporting after cell switch completion provides limited value due to low-resolution measurements, while aperiodic or a single instance of CSI reporting is sufficient to support early downlink scheduling in the target cell.

Observation 8:
Configuring CSI-RS resource sets for all candidate cells in advance can lead to unnecessary measurement overhead at the UE. A staged or selective activation approach helps reduce UE processing burden while ensuring timely CSI acquisition for likely target cells.

Observation 9:
Periodic CSI-RS transmission from multiple candidate cells can lead to excessive measurement overhead, especially when CSI acquisition requires more ports than beam management. An approach that allows selective activation and flexible timing is needed to balance performance and efficiency.

Proposal 1:
For an Incapable UE, the CSC MAC CE shall act as a trigger for initiating CSI-RS measurement and CSI reporting toward the target cell. This trigger may be explicitly indicated by a field within the CSC MAC CE or implicitly assumed.

Proposal 2:
Support that a Capable UE implicitly treats the reception of the CSC MAC CE as a trigger to stop further CSI measurement and initiate CSI reporting.

Proposal 3:
Support the use of CSC MAC CE as a unified trigger to activate or deactivate CSI measurement and reporting, replacing the conventional SP CSI-RS activation/deactivation MAC CE and CG activation via DCI.

Proposal 4:
Avoid configuring periodic CSI reporting with CC type 1 for all candidate cells in the RRCReconfiguration message to minimize unnecessary periodic UL resource allocation.

Proposal 5:
Support UCI as the preferred container for CSI reporting in LTM procedures, reusing existing CSI report formats and avoiding the introduction of a new MAC CE type.

Proposal 6:
Support aperiodic or a single instance of CSI reporting as the primary method during LTM procedures to reduce overhead and enable timely CSI utilization after cell switch.

Proposal 7:
Support staged CSI-RS configuration for candidate cells by either:
Initially configuring all CSI-RS resources as semi-persistent and selectively activating them via SP CSI-RS activation MAC CE, or
Deferring configuration until likely target cells are identified and configuring only their CSI-RS resources with periodic transmission in a second RRCReconfiguration message.

Proposal 8:
Support semi-persistent CSI-RS for CSI acquisition if the UE declares the capability, as it aligns with the agreed support for L1-RSRP measurement and involves similar inter-cell coordination. This enables consistent design, reduces signaling complexity, and improves measurement efficiency across multiple candidate cells.

3GPP TSG-RAN WG1 Meeting #120-bis	Tdoc R1-2502562
Wuhan, China, April 7th – April 11th 2025

Agenda Item:	9.9.1
Source:	Ericsson
Title:	Measurement related enhancements for LMT
Document for:	Discussion, Decision

1	

Conclusion
In the previous sections we made the following observations: 
Observation 1	By including measurement results for multiple beams from the same LTM Candidate Cell, the network can learn if there are multiple beams with high RSRP in the cell or not.
Observation 2	By including measurements results from additional LTM candidate cells, the network can learn if there is another LTM candidate cell that has several beams with high RSRP.
Observation 3	In legacy, UE measures on active CSI-RS resources and buffers the result so that it can compute and report CSI upon request.
Observation 4	It is not relevant to consider periodic or semi-persistent CSI reporting for early CSI reporting.
Observation 5	Since the target does not know when the UE received the LTM CSC MAC CE was received, the target does not know when the UE has calculated a valid CSI.
Observation 6	If legacy CSI reporting mechanisms are fully reused, the target can only request CSI based on the first CSI-RS after the first UL message.
Observation 7	A UE configured with CSI measurements by the source cell can report the results to the target cell if the report configuration is shared between the source and target cells, just like LTM-CSI-Resource-Configuration is already shared.


Based on the discussion in the previous sections we propose the following:
Proposal 1	For event triggered L1 measurement reports, support UE to include measurement results for up to 4 beams per cell, for up to 4 cells. 
Proposal 2	The NW configures at least one candidate RS for LTM2, and the UE determines the serving cell RS using the already agreed mechanism.
Proposal 3	Just like L1-RSRP on serving cells, the UE implementation filter for LTM L1-RSRP can use up to M measurement samples, where M can take the values 1 and 3 and is configured by the network.
Proposal 4	Reuse LTM-TCI-Info to configure candidate cell CSI-RS resources for beam management
Proposal 5	For an LTM report configuration, specify the single resource set with CSI-RS resources corresponding to multiple candidate cells in LTM-CSI-ResourceConfig. Name the resource set LTM-CSI-NZP-CSI-RS-ResourceSet.
Proposal 6	The CSI-RS resources of an LTM report configuration are explicitly associated with LTM candidate cells, just like SSB resources are.
Proposal 7	For semi-persistent CSI-RS for LTM, keep legacy principles for SP CSI-RS: the LTM-CSI-ResourceConfiguration should indicate the resourceType semi-persistent, the network indicates when transmission is turned ON/OFF with a MAC CE, and reporting is a separate configuration.
Proposal 8	Support CSI acquisition on candidate cells based on periodic and semi-persistent CSI-RS.
Proposal 9	Support reporting of CRI, CQI, PMI and RI for a Type I codebook for a candidate cell before or after LTM cell switch.
Proposal 10	Support wideband CSI reporting but not sub-band CSI reporting.
Proposal 11	Support Type I codebook with up to 128 ports for CSI acquisition on candidate cells.
Proposal 12	Periodic CSI-RS resources for CSI acquisition in an LTM candidate cell are counted as active when there is an activated TCI state in the cell and they are associated with an active CSI report configuration. Semi-persistent CSI-RS resources should additionally be ON.
Proposal 13	UE performs measurement operations on active CSI-RS resources for LTM CSI acquisition, up to UE capability.
Proposal 14	The UE reports the early CSI to target over MAC CE as soon as the CSI has been calculated.
Proposal 15	CSI-RS for CSI acquisition should be configured in LTM-CSI-NZP-CSI-RS-ResourceSet under LTM-CSI-ResourceConfig just like CSI-RS for L1-RSRP measurements but with the repetition field absent.
Proposal 16	Adapt LTM-CSI-ReportConfig to support  - relevant report quantities, including cri-RI-PMI-CQI,  - cqi-Table for CQI reporting
Proposal 17	For a candidate cell, a single CSI report configuration is configured (Alt 1).
On the other hand, multiple CSI-RS resources for CMR can be associated with a CSI report configuration (Alt Y in the proposal). This is needed for example to compute CQI on precoded CSI-RS resources.
Proposal 18	For a candidate cell, a multiple CSI-RS resource for CMR is associated with a CSI report configuration (Alt Y).
Proposal 19	The report configuration for CSI acquisition should be shared between the source cell, the target cell and the UE. The UE should keep it over cell switch execution.
Proposal 20	A high-level description of C-LTM should be added to TS 38.213 Section 21. The description should capture at least: - Configuration and evaluation of CLTM execution conditions in the UE, - A UE receiving TA value for the target cell by higher layer signalling or by UE-based TA estimation, applying the TA value in its initial uplink transmissions, if the TA value is valid.
Proposal 21	TS 38.213 Section 21 should be updated to describe the following aspects of conditional LTM: - TCI state to be applied upon CLTM execution, - The timeline for CLTM execution.

3GPP TSG RAN WG1 #120bis		R1-2502628
Wuhan, China, April 7th – 11th, 2025

Source: 	Apple Inc.
Title:                     Measurement related enhancements for LTM
Agenda item:	9.9.1
Document for:	Discussion and Decision
1 

Conclusion 
In this contribution, we have presented our views on the event-triggered L1 measurement report and CSI-RS based measurement for Rel-19 LTM. We proposed the following: 
Proposal 1: Support the report quantity configuration of ‘CRI-RI-PMI-CQI’ for Type-1 codebook for CSI report of candidate cell
Proposal 2: For a candidate cell, a single CSI report configuration with a single CSI-RS resource for CMR is provided to UE in a LTM-CSI-ResourceConfig IE by RRC signal. 
Proposal 3: Support configuration of semi-persistent CSI-RS resource for a candidate cell. 
Proposal 4: Enhance the existing TCI-State activation/deactivation MAC-CE for Candidate cell to activate the SP-CSI-RS based measurement before reception of CSC MAC-CE.
Proposal 5: Define a UE feature to report the maximum number of RRC-configured candidate cell for intra-frquency and inter-frequency early CSI report. 
Proposal 6: Not support selecting a subset of RRC-configured CSI-RS resources to measure. 
Proposal 7: Implementing the agreement by defining two UE capabilities for early CSI report: 
Capability #1:  A UE performs CSI measurement on the candidate cell after receiving the CSC MAC-CE. 
Capability #2: A UE performs CSI measurement for candidate cell after receiving the periodic CSI-RS resource configuration and before receiving the CSC MAC-CE. 
Proposal 8: The UE reports the early CSI to target cell over UCI bits in the first PUSCH. 
Proposal 9: For each candidate cell, a separate   is configured to determine the number of REs used for early CSI report. 
Proposal 10: The first PUSCH carrying the early CSI report is determined as follows:
If RACH procedure is triggered by CSC MAC-CE, the first PUSCH is the PUSCH scheduled by Msg2 RAR; 
Otherwise, the first PUSCH is the first CG-PUSCH or DG-PUSCH after UE switchs to target cell. 
Proposal 11: Defining the following CSI reference resource for early CSI report of candidate cell for a CSI reporting in a first PUSCH in uplink slot ‘n’:
For Capability #1 UE, the CSI reference resource is defined in time domain as , where  is the smallest value greater than or equal to  and no earlier than the last symbol of CSC MAC-CE command. 
For Capability #2 UE, the CSI reference resource is defined in time domain as , where  is the smallest value greater than or equal to . 

Proposal 12: A UE shall indicate the ‘out of range’ (i.e. CQI index ‘0’) in the CSI report if at least one of the following conditions is NOT met: 
Condition #1: There is no valid CSI reference resource corresponding to CSI report of the candidate cell. 
Condition #2: ‘condition defined in the current specification i.e., the timing between the first uplink symbol of first PUSCH and the last symbol of the PDCCH that schedules the first PUSCH is not smaller than ‘’ value. 

3GPP TSG RAN WG1 #120bis	R1-2502653
Wuhan, China, 7 – 11 April 2025

Agenda item:		9.9.1
Source:	Nokia
Title:	Measurement related enhancements for LTM
Document for:		Discussion and Decision

Conclusion
In this contribution, the following observations and proposal have been made:
For CSI-RS-based measurements, multiple CSI-RSs may be configured in a cell, and different sets of UE-specific CSI-RSs may be assigned to different UEs. Also, there is no specific frequency parameter for a CSI-RS
When SPCellInclusion is configured, it needs to be clarified that which frequency information should be used to determine which CSI-RSs from a measurement RS set belong to the current SpCell.
In Rel-18 LTM for L1-RSRP based measurements, after a candidate TCI activation command, L1 measurement requirements stop applying for candidate cells without active TCI states [Sections 9.14 and 9.15, 38.133].
When the UE starts measurements only after receiving and applying the cell switch command, the target cell may not determine whether a measurement occasion occurred before or after the cell switch command, making it challenging to predict whether a CSI report will be available in the first UL transmission.
Event-triggered reporting requires continuous (periodic) L1 measurements and CSI computation. Therefore, CPU occupancy rules need to be defined.
Allowing the UE to conduct CSI-RS measurements from different LTM candidate and serving cells with different Rx beamwidths/gains could result in suboptimal cell-switch decisions by the network.
When SpCellInclusion is configured, one of the following options can be used to determine the CSI-RSs from the current SpCell:
Option 1: NZP-CSI-RS resources in [ltm-CSI-NZP-CSI-RS-ResourceList] associated with the current SpCell are the entries where PCI (given by ltm-CandidatePCI) and frequency information (given by ssb-Frequency for the SSBs QCLed with NZP-CSI-RSs) of the candidate cell associated with the LTM-CandidateId (given by the corresponding entry in ltm-CandidateIdList) is equal to the PCI and center frequency of cell-defining SSB of the current SpCell.
Option 2: NZP-CSI-RS resources in [ltm-CSI-NZp-CSI-RS-ResourceList] associated with the current SpCell are the entries where PCI (given by ltm-CandidatePCI) and frequency information (absoluteFrequencyPointA) of the candidate cell associated with the LTM-CandidateId (given by the corresponding entry in ltm-CandidateIdList) is equal to the PCI and frequency associated with point A of the current SpCell.

Similar to Rel-18 LTM for SSBs, an ltm-CandidateIdList should be provided to indicate the candidate cells for the CSI-RSs specified in a single resource set.
For early CSI acquisition for a candidate cell:
Multiple CSI-RS resources for CMR can be associated with a CSI report configuration
Multiple CSI report configurations can be configured
The CSI-RS configuration, including the resource sets, and report configurations should be given in the candidate cell’s LTM-Candidate IE (but outside of the ltm-CandidateConfig).  
Support semi-persistent CSI-RSs for CSI acquisition measurements for candidate cells.
For CSI acquisition on a candidate cell, support the reporting of CRI, CQI (wideband), PMI (wideband), and RI, where PMI is based on the Type 1 codebook. FFS: further details on codebookType.
Ater a candidate TCI state activation, the UE keeps/initiates the measurements for early CSI acquisition only for cells/RSs associated with the active TCI states. FFS: whether PDCCH order used for early RACH can be used.
After the cell switch command, the UE acquires the CSI only associated with the target cell and the indicated TCI state.  
The cell switch command should indicate the report configuration to be used for reporting.
CSI report to the target cell is sent using the UCI container. 
The CSI report is sent in the first PUSCH transmission to the target cell, where the first PUSCH is the UL transmission used to send the RRC Reconfiguration Complete message.
An indication is included in the UCI report to indicate whether a valid measurement report is available.
The rules for UE to determine when a valid measurement report is available can be defined using one of the options below:
Option 1 – Use existing time constraints defined for DCI-triggered aperiodic CSI reporting by introducing a CSI reference resource associated with the report. FFS: Define CSI reference resource 
Option 2 – 
If there is at least one measurement RS occasion associated with the CSI reporting configuration after the measurement triggering point (i.e., application of the RRC configuration for early measurement or application of the cell switch command for baseline UE) such that the time gap between the RS occasion and the reporting slot is greater than a predefined duration (e.g., Z’).
FFS: An additional timeline requirement for the minimum duration between the triggering command and the reporting slot.
After sending a UCI report in the first PUSCH indicating that no valid measurements are available, the UE can monitor for a DCI providing a dynamic grant to send the CSI report.
For UEs that can start measurements before the reception of the cell switch command, RAN1 to clarify whether the CPU usage for early CSI measurements should be counted within the existing limit of supported simultaneous CSI calculations or if there will be a separate limit.
For UEs that can start measurements before the reception of the cell switch command, a CSI report for a candidate cell should occupy CPU(s) on one or more symbols starting from the last symbol of the uplink slot carrying the acknowledgment for the LTM configuration to the last symbol of the downlink slot carrying the cell switch command or the last symbol of the uplink slot carrying the acknowledgment for the cell switch command. 
FFS: if additional triggering mechanism is used to trigger the measurements before the cell switch command. 
After the cell switch, in the target cell, a CSI report carrying the CSI performed before or during the cell switch procedure should occupy CPU(s) until the last symbol of the uplink slot carrying the report. FFS: whether the starting time needs to be defined. 
In the target cell, RAN1 to clarify whether the CPU usage for early CSI measurements will be counted within the existing limit of supported simultaneous CSI calculations or if there will be a separate limit.
For UEs that can start measurements before the reception of the cell switch command, in the serving cell:
For periodic CSI-RS, an NZP CSI-RS resource associated with a candidate cell considered active in the current serving cell in a duration of time, starting when the periodic CSI-RS is configured by LTM configuration, and ending when the cell switch command is received. 
FFS: SP CSI-RSs if the SP CSI-RSs are supported.
After the cell switch, in the target cell, a periodic CSI-RS resource should be considered active during a time duration starting when the cell switch command is applied, and ending at the end of the uplink slot containing the report associated with the RS.
RAN1 to clarify whether the number of active CSI-RS ports or active CSI-RS resources, in both the serving and target cells, for early CSI acquisition measurements should be counted towards the current maximum UE limit of active CSI-RS ports/resources or as a separate limit.
CPU occupancy rules should be defined for event-triggered reporting.
RAN1 should clarify whether the number of supported simultaneous CSI calculations should be considered a separate UE capability from those defined for periodic/SP/aperiodic reporting.
The number of CPUs for an event triggered reporting can be defined as the same defined for L1-RSRP reporting in legacy systems, 𝑂𝐶𝑃𝑈 = 1.
The CPU timeline for event-triggered reporting should be defined with the starting point as the first symbol of the earliest RS resource associated with the event-triggered L1 measurement reporting and the endpoint as the deactivation or reconfiguration of the event-triggered report.
For LTM2, at least one candidate RS shall be configured for the determination of the RS type of the serving beam.
To enable CSI-RS-based beam management for LTM, RAN1 should select one of the following options to support UE Rx beam refinement based on CSI-RSs from candidate cells:
Option 1: Support candidate cell CSI-RSs with repetition set to ‘ON’. 
Option 2: Support candidate cell CSI-RSs with repetition set to ‘OFF’ only.
RAN1 should discuss whether/how to ensure appropriate Rx beams (e.g., wide versus refined Rx beams) are consistently used for measurements across serving cell and different LTM candidate cells.

3GPP TSG RAN WG1 #120bis		                            R1-2502749
Wuhan, China, April 7th – 11th, 2025
Agenda Item:	9.9.1 
Source:	KDDI Corporation
Title:	Discussion on measurements related enhancements for LTM
WID:       	NR_Mob_Ph4-Core
Tdoc Type:	Discussion
Document for: 	Discussion and decision

Conclusion
Based on the discussion in the previous sections we propose the following:
Proposal 1: Support mTRP operation for the target cell in Rel-19. 
Proposal 2: Support Alt1: A single CSI report configuration is configured
Proposal 3: Support Alt Y: Multiple CSI-RS resources for CMR can be associated with a CSI report configuration
Proposal 4: Support Semi-persistent CSI-RS resource
Proposal 5: CSI-RS resource configuration is based on RRC measurement configuration.
Proposal 6: Support UCI to carry CSI report as legacy.

3GPP TSG RAN WG1 #120bis			R1-2502778
Wuhan, China, Apr. 7th – 11th, 2025

Source:	NTT DOCOMO, INC.
Title:	Discussion on measurement related enhancements for LTM
Agenda Item:	9.9.1
Document for: 	Discussion and Decision

Conclusion
In this contribution, we discussed the enhancements for Measurements related enhancements for purpose of supporting LTM. Based on the discussion, we made following observations and proposals.
CSI-RS related enhancements
Proposal 1
UE shall base the timing of CSI-RS resource on the SSB QCLed with the CSI-RS resource.
The SSB resource is found in LTM-SSB-Config-r18.

Event-triggered beam reporting
Observation 1
RAN1 needs to discuss how to determine RS type of serving cell RS for event LTM2.

Proposal 2
For RS type determination of serving cell RS for event LTM2, support the following implicit manner.
At least one candidate RS shall be configured.
If the RS(s) for candidate cell(s) are CSI-RS configured in a CSI-RS resource set configured with repetition, QCL RS of the indicated TCI-state is used for the serving cell; otherwise, SSB QCLed with QCL RS of the indicated TCI-state is used for the serving cell.
UE does not expect the following configuration:
CSI-RS resource in the indicated TCI state of serving cell is NOT configured in a CSI-RS resource set configured with repetition, and 
CSI-RS is configured as measurement resource for the candidate cell(s). 

Observation 2
RAN1 needs to decide one value for the maximum number of beam measurement results that can be reported in event-triggered beam report.


Proposal 3
Support 16 beams as the maximum number of beam measurement results that can be reported in event-triggered beam report.

CSI acquisition on candidate cell(s) based on CSI-RS before or during LTM
Proposal 4
For the number of CSI report configuration of CSI acquisition for one candidate cell, support Alt1.
Alt 1: A single CSI report configuration is configured

Proposal 5
For the number of CSI resources for CMR associated with one CSI report configuration of CSI acquisition for one candidate cell, support Alt Y.
Alt Y: Multiple CSI-RS resources for CMR can be associated with a CSI report configuration

Proposal 6
For the periodicity of CSI-RS for CSI measurement of candidate cell, support SP CSI-RS.

Proposal 7
For the selection of CSI resource(s) for measurement and a CSI report configuration for the report after reception of cell switch command, support the following.
CSI report configuration is associated with target configuration ID in cell switch command MAC CE.
CSI resource is the CSI-RS configured in the TCI state indicated in cell switch command MAC CE.
If optional procedure is supported based on UE capability,
CSI measurement for candidate cell can be triggered before cell switch command by ‘CSI request field indication’ in legacy DCI format by enhanced association configuration via RRC signaling.

Proposal 8
For the container of CSI report to the target cell, support UCI.
New MAC CE can be sent from UE to NW to indicate the time duration it requires for CSI reporting from the new MAC CE.

Proposal 9
For the report contents of CSI acquisition for candidate cells,
Support one CMR in the report.
Support configuration of Type I SP codebook only for candidate cell.
Support CRI, CQI, PMI and RI for a Type I SP codebook.

Conditional Intra-CU LTM
Proposal 10
For conditional intra-CU LTM, RAN1 should wait for determination of whole procedure design in RAN2.

3GPP TSG-RAN WG1 #120bis	R1-2502853
Wuhan, China, April 7th – 11th, 2025	

Agenda item:	9.9.1
Source: 	Qualcomm Incorporated
Title: 	Measurements related enhancement for LTM
Document for:	Discussion/Decision

Conclusions
In this contribution, we presented our views on measurement-related enhancement for LTM, focusing on measurement resources and candidate cell CSI acquisition. Specifically, the following observations and proposals were made:
Observation 1: The serving cell RS type for event-triggered L1 measurement reporting can be implicitly determined based on the configured RS type of candidate cell RSs, without any explicit RRC parameters.
Proposal 1: To assist event evaluation in the MAC layer, the PHY layer should provide L1 measurement results for all or MAC-indicated resources within the configured LTM measurement resources for both serving and candidate cells. 
Proposal 2: As both event evaluation and reporting for event-triggered L1 measurement reporting are managed by the MAC layer, no CPU involvement is necessary.
Proposal 3: For event evaluation and measurement reporting for Events LTM2, LTM3, and LTM5, the current SpCell and its corresponding RSs should always be included in the LTM measurement resource configuration associated with the report configuration.
Proposal 4: For CSI acquisition on candidate cells, support periodic and semi-persist CSI-RS.
Proposal 5: Regarding the configuration of CSI acquisition on candidate cells,
A single CSI report configuration per candidate cell should be supported (Alt-1).
Multiple CMR/IMR resources can be associated with the CSI report configuration (Alt-Y).
Proposal 6: For CSI measurement on candidate cells,
The CSI-RS measurement starts only after the TCI state activation/indication for the candidate cell.
Only a subset of CSI-RS resource(s) that are the same or QCLed with the QCL RS(s) in the activated/indicated TCI state(s) should be measured.
Proposal 7: For CSI reporting to the target cell, consider the following alternatives:
Alt-1: CSI reporting is piggybacked on the Msg3 (RACH-based) or the first UL transmission to the target cell (RACH-less).
Alt-2: A 1-bit CSI ready indication is transmitted along with the Msg3 or the first UL transmission to the target cell. Once indicated as “ready”, the CSI report may be subsequently triggered.
Observation 2: When the CSI report to the target cell is not always available, UCI-based reporting may necessitate blind decoding of the presence of the UCI multiplexed in the first PUSCH transmission.
Proposal 8: For CSI reporting to the target cell, MAC CE should be supported as the reporting container.

3GPP TSG RAN WG1 #120bis			R1-2502891
Wuhan, China, April 7th – 11th, 2025

Agenda Item:	9.9.1
Source:	Google
Title:	Discussion on measurements related enhancements for LTM
Document for: 	Discussion

Conclusion
According to the above discussion(s), we have the following observation(s) and/or proposal(s). 
Proposal 1: For CSI-RS sources configuration used for gNB scheduled reporting and event triggered reporting for L1-RSRP, LTM NZP CSI-RS resource set is configured under LTM-config. 
Proposal 2: On CSI acquisition for LTM cell switch, support that multiple CSI report configurations can be configured for a LTM candidate cell.  
Proposal 3: On CSI acquisition for LTM cell switch, support that multiple CSI-RS resources for CMR can be associated with a CSI report configuration.  
Proposal 4: On CSI acquisition for LTM cell switch, support semi-persistent CSI-RS resources can be configured for a LTM candidate cell.  
Proposal 5: On CSI acquisition for LTM cell switch, if periodic CSI-RS resources are configured for LTM CSI acquisition, UE starts to measure the configured periodic CSI-RS resources after the RRC configuration. 
Proposal 6: On CSI acquisition for LTM cell switch, support that the latest available measured CSI on target cell resource(s) is conveyed by UCI. 
Proposal 7: On CSI acquisition for LTM cell switch, Type I codebook is supported. 
Proposal 8: On CSI acquisition for LTM cell switch, UE at least reports CQI, PMI, RI and CRI. 
Proposal 9: On CSI acquisition for LTM cell switch, do not support Type II codebook and subband reporting. 

3GPP TSG RAN WG1 #120bis			R1-2502929
Wuhan, China, April 7th – 11th, 2025

Agenda item:	9.9.1
Title:	LTM measurements related enhancements
Source:	MediaTek Inc.
Document for:	Discussion and Decision

Conclusions
We have the following proposals:
Proposal 1: Support that RS type is RRC configured for LTM2 events (Alt 1-1).
Proposal 2: Do not introduce additional Rx beam refinement procedures. 
Proposal 3: Support Alt 1. A single CSI report configuration is used. 
Proposal 4: Support Alt X. A single CSI-RS resource for CMR is associate with a CSI report configuration. 
Proposal 5: Do not support semi-persistent CSI-RS for CSI acquisition. Only periodic CSI-RS is used. 
Proposal 6: It is up to UE implementation to select a subset of CSI-RS resources to measure before CSC. 
Proposal 7: It is up to UE implementation when to start measuring the CSI-RS resources before CSC. 
Proposal 8:  Periodic CSI-RS resources are configured semi-statically by RRC. Up to UE implementation, UE can perform CSI-RS measurements on a candidate cell based on available CSI-RS resources before CSC is received. 
Proposal 9:  CSI report timeline to target cell shall be decided considering measurement accuracy and delay aspects, which are more in RAN4 expertise. 
Proposal 10: Support MAC-CE (Option 2) as report container. UE sends a single CSI report to target cell via MAC-CE. 
Proposal 11:  CSI configuration to target cell is limited to CQI only, and only Rank=1 case is supported.