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

Source:                 CATT 
Title:	                L1 event triggered measurement reporting
Agenda Item:	8.6.3
Document for:	Discussion and Decision

Conclusion
According to the previous analysis in section 2, our observations and proposals are summarized as follows:
Observation 1: RAN1 has not engaged in discussions regarding the possibility of configuring CSI-RS in the absence of a valid ltm-SSB-ResourceSet in the LTM-CSI-ResourceConfig. 

MR MAC CE
Proposal 1a: For event LTM2, UE only evaluates the RS associated with the indicated TCI state(i.e., no need to the RSs of serving cell in the associated LTM-CSI-ResourceConfig). 
Proposal 1b: For event LTM2, UE only performs the evaluation when the RS type of the indicated TCI state matches the candidate RS configured in the associated LTM-CSI- ResourceConfig.
Proposal 2: For an MR triggered by event LTM2, the MR MAC CE includes only the current beam information.
Proposal 3: The triggered MR is only cancelled once the original complete MR for the corresponding ltm-CSI-ReportConfigId has been successfully transmitted.
Proposal 4: For event-triggered periodic measurement reporting, the reporting of the Truncated L1 measurement report MAC CE are not counted as the number of L1 event-triggered measurement reports.

Signaling Configuration aspects
Proposal 5: Send LS to RAN1 to check whether it is allowed to configure CSI-RS in the LTM-CSI-ResourceConfig without a valid ltm-SSB-ResourceSet. 

Support of SP CSI-RS resource for LTM
Proposal 6: Send LS to RAN1 to clarify the granularity of the SP CSI-RS activation/deactivation, with the following options:
Option 1: per LTM-NZP-CSI-RS-ResourceSet-r19 (i.e. all RSs(from same candidate cell or different candidate cells) in one LTM-NZP-CSI-RS-ResourceSet-r19 are activated/deactivated by the new MAC CE).
Option 2: per candidate cell in one LTM-NZP-CSI-RS-ResourceSet-r19 (i.e. all RSs of certain candiate cell in one LTM-NZP-CSI-RS-ResourceSet-r19 are activated/deactivated by the new MAC CE).
Option 3: per RS in one LTM-NZP-CSI-RS-ResourceSet-r19 (i.e. a certain RS in one LTM-NZP-CSI-RS-ResourceSet-r19 is activated/deactivated by the new MAC CE).
Proposal 7: UE continues to measure the activated semi-persistent CSI-RS resources after cell switch.

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

Agenda item:		8.6.3
Source:	Xiaomi
Title:	Remaining issues of L1 event triggered measurement reporting
Document for:		Discussion and Decision

Conclusion
In this contribution, we discuss the remaining issues of the L1 event triggered measurement reporting, and propose the following:
(MAC-5) MAC CE format for LTM2
Proposal 1: For MR triggered by LTM2, whether to include measurement results of LTM candidates is configured by the network (e.g. via field allowReportAnyBeam).

(MAC-6, MAC-7) Truncated Event Triggered L1 MR MAC CE and multiple Event Triggered L1 MR MAC CEs
Proposal 2: (MAC-6) For truncated MR MAC CE, the same principle of regular MR MAC CE applies, i.e., in addition to triggered beams, the truncated MAC CE includes other beams in descending order of measured quantity. The best quality beam among all beams included in the truncated MAC CE is taken as the reference beam.
Proposal 3: RAN2 to discuss how to handle the case that UL grant cannot accommodate all the triggered Event Triggered L1 MR MAC CEs, e.g. whether to prioritize certain Event Triggered L1 MR MAC CEs, or the handling is left to UE implementation.
Proposal 4: (MAC-7) If more than one triggering events are pending and UL grant is not sufficient for two regular L1 MR MAC CEs, UE transmits as much information as possible in one L1 MR MAC CE for one event, and transmits truncated L1 MR MAC CE for the other event if there is space available in the UL grant.

(MAC-1) Event configuration
Proposal 5: (MAC-1) Beam offset for current beam of serving cell, i.e. Obs in the event evaluation inequality, is not needed for the LTM event evaluation.
Proposal 6: RAN2 to clarify whether serving cell in Event LTM 2/3/5 refers to SpCell only. 

(MAC-15, MAC-16) Event triggering / cancellation
Proposal 7: (MAC-15) Triggering of MR is only cancelled when all beams are reported according to configuration (i.e. maxNumberOfReportedBeams-r19, allowReportAnyBeam-r19, reportCurrentBeam-r19).
Proposal 8: A note is added to clarify that “Event Triggered L1 MR MAC CE is considered as regular MAC CE (i.e. not truncated MAC CE) if it contains information of all the remaining beams after truncated MAC CE is sent.”
Proposal 9: (MAC-16) When a beam meets the entering condition and later meets the leaving condition before receiving UL grant, or vice versa, the triggered MR should be cancelled.

(MAC-17) SR of Event Triggered L1 MR MAC CE
Proposal 10: (MAC-17) When L1 measurement is triggered and UL-SCH resource is not available, SR is triggered irrespective of whether dedicated SR configuration is configured or not.
Proposal 11: (MAC-17) If the dedicated SR configuration for L1 measurement report MAC CE is not configured, when L1 measurement is triggered and there is no UL-SCH resource available, SR is triggered, and RACH is triggered consequently. No specification change is needed.
Proposal 12: The dedicated SR for Event Triggered L1 Measurement Report MAC CE has higher priority than the SR for BSR.

3GPP TSG-RAN WG2 Meeting #130	R2- 2503469
St.Julians, Malta, 19th – 23rd May 2025
 	
Agenda Item:	8.6.3
Source:	MediaTek Inc.
Title:	Remaining issues on event triggered L1 MR
Document for:	Discussion, Decision

Conclusion
In this contribution, the following observations and proposals are made:
2.1 Semi-persistent CSI-RS resources after LTM cell switch
Proposal 1: After LTM cell switch, UE continues to measure the activated semi-persistent CSI-RS resources for serving cell and candidate cells, if configured.

2.2	Reporting format of MR MAC CE
Proposal 2: Confirm the previous WS to introduce four codepoints to represent four types {type1, type2, type3, type4}

2.3	Unsatisfied beam selection
Observation 1: It is hard to define specific rules for unsatisfied beam selection, considering the measured quality and stability. Otherwise it will be overcomplicated.
Proposal 3: Add a note in the spec as a guidance for UE to select unsatisfied beams based on measurement quality. RAN2 does not specify detailed rules for this and leave it to UE implementation.
Proposal 4: Introduce a UE capability to indicate the support for reporting unsatisfied beams in event-triggered L1 MR MAC CE.

2.4	The content of L1 MR MAC CE triggered by LTM2 (MAC-5)
Observation 2: RAN1 agreement is only related to the serving cell RS type identification, not for measurement and report requirement.
Proposal 5: For LTM2, only current beam information is included in the MR MAC CE.

2.5	MR cancellation policy (MAC-15 and MAC-16)
Proposal 6: If all newly triggered beams (entry and leaving) have been reported, but the remaining beams (old triggered beams and irrelevant beams) are not reported due to resource limitations, subsequent MR for those beams is unnecessary, and the triggered MR should be cancelled.
Proposal 7: Proposal: If a beam (or multiple beams) meets the entry/leaving condition and an MR is triggered, but before obtaining the UL grant, the leaving/entry condition is met, the MR trigger is cancelled, and no MR is sent.
Proposal 8: for all type of reported beams, if new measured values are acquired before the UL grant is obtained, UE reports the latest measured value of those beams.

2.6	TTT for leaving condition
Proposal 9: RAN2 to discuss whether the TTT for the leaving condition should be always equal to the TTT for the entry condition, i.e., whether the same timeToTrigger should be used for both.

3GPP TSG-RAN WG2 Meeting #130	R2-2503484
St. Julians, Malta, May. 19th – 23rd, 2025
												
Agenda item:		8.6.3
Source:		Lenovo
Title:		Discussion on L1 measurement
Document for:		Discussion and Decision

Conclusion
In this contribution, the following proposals are given based on the discussion:
SP CSI-RS resource for L1 measurement
Proposal 1: RAN2 to discuss which option can be used to handle the activated SP CSI-RS resource for L1 measurement:
Option 1: UE changes the state for activated semi-persistent CSI-RS resources to deactivated state and stops measurement once cell switch is triggered.
Option 2: UE continues measuring the activated semi-persistent CSI-RS resources irrespective of if cell switch is triggered. 
Option 3: UE changes the state for activated semi-persistent CSI-RS resources to deactivated state and stops measurement for the ‘remaining’ candidate cells (i.e. other than target cell) once cell switch is triggered. UE continues measuring the activated semi-persistent CSI-RS resources of only the target cell after cell switch is triggered.

SP CSI-RS resource for CSI acquisition
Proposal 2: A single MAC CE is specified to activate/deactivate the semi-persistent CSI-RS resource from candidate cell for both L1 measurement and CSI acquisition purposes.
Proposal 3: UE continues measuring the activated SP CSI-RS resource for CSI acquisition from target cell after L1 CSI information has been transmitted to target cell.
Proposal 4: RAN2 to discuss which option can be used to handle the activated SP CSI-RS resource for CSI acquisition from other candidate cells:
Option 1: UE changes the state for activated semi-persistent CSI-RS resources to deactivated and stops measurement after cell switch is triggered.
Option 2: UE continues measuring the activated semi-persistent CSI-RS resources after cell switch is triggered.

MR MAC CE
Proposal 5: UE can support maximum 16 beams from the candidate cells and one current beam in one MR MAC CE.
Proposal 6a: In a truncated MR MAC CE UE maximizes inclusion of Type1/ 2 beams (i.e., any Type3/ 4 will only be included if all Type1/ 2 have been included).
Proposal 6b-alt1: In a truncated MR MAC CE current beam is never included. 
Proposal 6b-alt2: In a truncated MR MAC CE current beam is included if all Type1/ 2 beams are included.
Proposal 6b-alt3: In a truncated MR MAC CE current beam is included if at least one Type1/ 2 beam is included.
Proposal 7a: Beam with highest RSRP among the event triggering beam(s) (Type1/ 2) is included first in the report.
Proposal 7b: A 1-bit indication to differentiate Absolute or Differential RSRP (AD bit) is included.

Tail Reporting
Proposal 8: No Tail reporting is done. The UE prepares a complete MR MAC CE if any of the ‘remaining’ Type1 or Type2 beams could not be included in the previous truncated MR MAC CE, if the remaining beams still fulfills the event triggering condition.

Useful optimizations
Proposal 9: When UL grant is not sufficient to include all Full MRs (each with many Type3/ 4 beams) and therefore can only include 'm' Full MRs, UE shall rather maximize reporting of triggered beams (Type1/ 2) by including 'n' truncated MRs in the TB (n < m). Exact implementation is left to the UE implementation.
Proposal 10: UE includes a beam(s) once and only in the latest triggering measurement report in a MAC PDU if there are potentially multiple MRs with the same beam. Same applies to the current beam of the serving cell i.e., the current serving beam is included only once in the MAC PDU.
Proposal 11: RAN2 considers means to control amount of MR MAC CE reporting.

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

Agenda Item:	8.6.3
Source: 	OPPO
Title:  	Open issues for event-triggered L1 measurement reporting 
Document for:	Discussion and Decision

Conclusion
Based on the discussion above, we have the following proposals:
Proposal 1	For MR triggered by LTM2, the MR MAC CE can include measurements for LTM candidates.
Proposal 2	For truncated MR MAC CE, the triggered beam takes precedence over the best beam.
Proposal 3	For truncated MR MAC CE, absolute RSRP is used for both triggered beam and best beam.
Proposal 4	Whether one UL TB includes more than one truncated MR MAC CE is up to UE implementation.
Proposal 5	Coexistence of LTM event triggered reporting and mTRP operation at serving cell is supported.
Proposal 6	RAN2 further study how to define the current beam of serving cell for LTM L1 event evaluation if mTRP is configured based on the following options:
-	Option1: current beam corresponds to one of the indicated TCI states that is selected/configured by NW.
-	Option2: current beam corresponds to best beam of the two indicated beams.
-	Option3: current beam corresponds to both indicated beams.
Proposal 7	If no dedicated SR is provided, RACH procedure is triggered to request the UL grant for MR MAC CE transmission.
Proposal 8	The SR triggered for L1 event-triggered measurement report is cancelled if a MAC PDU is transmitted and this PDU includes L1 MR MAC CE or truncated MR MAC CE.
Proposal 9	When the MAC entity has PUCCH resource for pending SR for L1 event triggered MR and the MAC entity has one or more PUCCH resources overlapping with PUCCH resource for “other triggered SR”, UE selects PUCCH resource based on:
-	Option 1: left for UE implementation.
-	Option2: MAC entity considers the PUCCH resource for L1 event triggered MR MAC CE as valid.
-	Option3: if “other triggered SR” is for BFR, the MAC entity considers the PUCCH resource for beam failure recovery as valid.

3GPP TSG-RAN WG2 Meeting #130	R2-2503554
St.Julians, Malta, May 19th – 23rd, 2025
Agenda Item:	8.6.3
Source: 	Fujitsu
Title:	Discussion on L1 event triggered measurement reporting
Document for:	Discussion and Decision

Conclusion
This document discussed the remaining open issues for the L1 event triggered measurement report and made the following proposals:
LTM event evaluation 
Proposal 1: When current serving cell is configured as one of the candidate cells, the UE will perform event evaluation according to the network configuration.
MAC CE for measurement report (MR MAC CE)
Proposal 2: For the MR triggered by LTM2, based on the network configuration, the MR MAC CE can include measurements for LTM candidates in addition to the current beam. The number of beams to be reported N is applied. 
Prioritization/multiplexing of MR MAC CEs 
Proposal 3: To support more than one (truncated) MR MAC CEs to be multiplexed in one UL grant, if available.
BSR for MR MAC CEs 
Proposal 4: RAN2 will not support BSR for MR MAC CEs.
Other
Proposal 5: RAN2 considers T312-like mechanism, e.g. for the event configured for LTM decision.

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

Conclusion
In this contribution, we discussed a lot of MAC open issues for L1 LTM measurement event evaluation and reporting.
We have the following Observations and Proposals: 
For LTM2:
Observation 1: RAN1 agreed at least one candidate RS shall be configured for LTM2, but it is for RS type determination.
Observation 2: Network can always configure LTM3/4/5 for the UE to report candidate beams.
Observation 3: If we agree to include measurements for LTM candidates in L1 MR triggered by LTM2, some more questions need to be considered, e.g., whether to use truncated MAC CE if the intended candidate beams are not all included, what is the criteria to select candidate beams to be included in the L1 MR MAC CE etc.
Proposal 1: For L1 MR triggered by LTM2, only the current beam information is included in the L1 MR MAC CE.
Proposal 2: For reporting configuration of event LTM2, the UE ignores the candidate beam in the associated LTM CSI resource set (i.e., UE does not measure those candidate beams).
For Triggering status cancelling for Truncated L1 MR MAC CE
Observation 4: According to current MAC running CR, after sending only part of event-triggered beam(s), the triggering status of the corresponding event is not cancelled until the full L1 measurement report MAC CE is reported in following grant.
Proposal 3: RAN2 agrees to only adopt the simple cancelling condition as in current MAC running CR, i.e.  the triggering status of the truncated L1 MR MAC CE is cancelled when the normal (not-truncated) L1 measurement report MAC CE is reported in following grant(s).
For Content of Truncated L1 MR MAC CE
Observation 5: It is not clear how the 4 types of candidates beams and the serving beam should be placed in the L1 MR truncated MAC CE (e.g., in which order).
Proposal 4: RAN2 to agree the priority to include beams in L1 MR truncated MAC CE is as follows (highest priority listed first, FFS whether to capture it in spec):
Type 1 or Type 2 beam;
Type 3 beam;
Current serving beam (if configured to be included);
Type 4 beam (if configured to be included).
Proposal 5: When truncated L1 MR MAC CE is used, if only one octet is left in the UL grant and the network configures the UE to report current beam, the UE places the current beam at the end of truncated L1 MR MAC CE.
Proposal 6: For truncated L1 MR MAC CE, the best quality beam among the candidate beams included in truncated L1 MR MAC CE is taken as the reference beam as the first one.
For Semi-persistent CSI-RS resource activation/deactivation
Observation 6: If the UE continues to measure the activated semi-persistent CSI-RS resources after cell switch, the source serving cell should inform target cell which semi-persistent CSI-RS resources of other candidate cells has been activated and it introduces RAN3 impact.
Observation 7: If the UE stops to measure the activated semi-persistent CSI-RS resources after cell switch, candidate gNB(s) will know that all semi-persistent CSI-RS resources of other candidate cells has been deactivated after receiving LTM CONFIGURATION UPDATE message.
Observation 8: RAN1 agreed to introduce semi-persistent CSI-RS resource for the purpose of CSI acquisition.
Observation 9: Whether the semi-persistent CSI-RS resource is activated/deactivated for beam measurement reporting or for CSI acquisition, can be based on different reporting configuration.
Proposal 7: RAN2 to support option-3 to handle the activated semi-persistent CSI-RS resources after LTM cell switch:
Option 3: UE stop to measure the activated semi-persistent CSI-RS resources of the candidate cells (i.e., other than target cell) after cell switch. UE continues to measure the activated semi-persistent CSI-RS resources of the target cell after cell switch.
Proposal 8: Reuse the MAC CE (SP CSI-RS Resource Set Activation/Deactivation for Candidate Cell MAC CE) to activate/deactivate the semi-persistent CSI-RS resource for CSI acquisition.
For mTRP
Observation 10: The main difference between mTRP and sTRP is the number of the indicated TCI states of serving beam will be 2, and if we agree to select one of the two beams, most agreements for sTRP can be reused for mTRP.
Observation 11: Definition of first indicated TCI can refer to TS 38.214.
Proposal 9: To support mTRP, RAN2 agrees to select one TCI state from the two (e.g., the first indicated TCI state as defined in TS 38.214), when serving cell is configured with mTRP.
For Padding L1 measurement report MAC CE
Proposal 10: Introduce padding L1 measurement report MAC CE

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

Agenda item:	8.6.3
Source: 	China Telecom
Title:	Discussion on remaining issues of L1 event triggered measurement reporting
WID/SID:	NR_Mob_Ph4-Core
Document for:	Discussion and Decision

Conclusion
In this contribution, we discuss the remaining issues on L1 event triggered measurement reporting for Rel-19 LTM. We kindly ask RAN2 to consider the corresponding proposals listed as below.
Proposal 1: RAN2 confirms that the beam specific offset is applied to serving beam as well for LTM event evaluation.
Proposal 2: The granularity of beam specific offset for serving beam is configured in a per-cell level, which means all the beams of a serving cell shares the same beam specific offset.
Proposal 3: The beam specific offset for serving beam could be used to LTM2, LTM3 and LTM5.
Proposal 4: For MR triggered by LTM2, the MR can include measurements for LTM candidates if the NW configures that the beam(s) not satisfying the event could be reported. 
Proposal 5: It is up to UE implementation to select the candidate beam to be reported in MR triggered by LTM2.
Proposal 6: RAN2 clarifies whether to restrict at most one normal MR MAC CE or at most one truncated MR MAC CE to be multiplexed in one UL grant.
Proposal 7: RAN2 considers to support more than one normal or truncated MR MAC CEs to be multiplexed in one UL grant, if available.
Proposal 8: RAN2 clarifies the UE behaviour on how to select the reported measurement event when there are multiple triggered events to be reported.
Proposal 9: RAN2 considers to support padding MR MAC CE.
Proposal 10: The padding MR MAC CE could include one event config ID and at least one triggered beam id (SSBRI or CRI) plus the corresponding L1 RSRP, when there are triggered events to be reported.
Proposal 11: The padding MR MAC CE could include one event config ID and at least one any beam id (SSBRI or CRI) with available L1 RSRP, when there is no triggered event to be reported.
Proposal 12: The padding MR MAC CE with a triggered event is transmitted with a higher LCH priority than padding BSR MAC CE.
Proposal 13: The padding MR MAC CE with a non-triggered event is transmitted with a lower LCH priority than padding SL-BSR MAC CE.

3GPP TSG-RAN-WG2 Meeting #130	R2-2503745
St.Julians, Malta, May 19th – 23rd, 2025
Agenda item	:		8.6.3
Source	: 	Sharp
Title	: 	Discussion on issues for supporting L1 event triggered measurement reporting
Document for	:	Discussion and Decision

Conclusion
Proposal 1. For MR triggered by LTM2, the MR MAC CE can include measurements for LTM candidates.
Proposal 2. The triggered MR should be cancelled if all the triggered beam(s) have been reported.
Proposal 3. The triggered MR should be cancelled when a beam (or multiple beam) meets the entry condition for TTT and before getting the UL grant this beam (or all these beams) meets the leaving condition.
Proposal 4. The triggered MR should be cancelled when a beam (or multiple beam) meets the leaving condition for TTT and before getting the UL grant this beam (or all these beams) meets the entry condition.

3GPP TSG-RAN WG2 Meeting #130		R2-2503772 
Malta, May 19th – 23rd, 2025
Source:	Baicells
Title:		Discussion on L1 event triggered measurement reporting 
Agenda Item:		8.6.3
Document for:	Discussion and Decision

Conclusion
In this contribution, we have the following Observations and Proposals:
Observation 1: The truncated MAC CE can only accommodate only a limited number of beams.
Proposal 1: A priority should be determined between the above four types of beam i.e. type1(type2)>type3>type4.
Observation 2: RAN#2 129 meeting achieves the agreement that common format for normal MR MAC CE and truncated MR MAC CE is used.
Proposal 2: The current beam information of SpCell is always placed at the end of one of the truncated MAC CE which includes the current beam.
Observation 3: UE can transmit serval truncated MAC CE to the gNB and gNB doesn’t know in which truncated MAC CE the current beam is included.
Proposal 3: A certain bit to indicate the occurrence of the current beam is needed.
Observation 4: RAN#2 129 meeting achieves the agreement that common format for normal MR MAC CE and truncated MR MAC CE is used.
Proposal 4: The best quality beam among the beams to be included in a truncated MR MAC CE is taken as the reference beam as the first one
Observation 5:It’s possible that some beams trigger the entering condition, meanwhile some beams trigger the leaving condition.
Proposal 5: Type2 should have higher priority than type1.

3GPP TSG-RAN WG2 #130                                             	    R2-2503802                                                       
St. Julian’s, Malta, May 19th – 23rd, 2025                                                 	     
Agenda item:	   8.6.3	
Source: 		Qualcomm Incorporated
Title: 	Discussion on L1 event-triggered measurement reporting for LTM
Document for:	Discussion
1	

Conclusion
This contribution discussed aspects related to measurement enhancements for LTM. The following observations and proposals have been made:
Observation 1: Unlike legacy SP CSI-RS resource configuration, LTM NZP-CSI-RS Resource Set doesn’t have any ID associated, and NZP-CSI-RS Resource Sets under LTM Config are not linked to NZP-CSI-RS Resource IDs under LTM NZP-CSI-RS Resource Set, either. Therefore, {SP CSI-RS resource set id and/or candidate id} could cause unnecessary complications and ambiguities.
Proposal 1: RAN2 agree to use LTM CSI Resource Config ID for LTM SP CSI-RS activation/deactivation MAC CE.
Observation 2: The legacy SP CSI-RS management (i.e., activating/deactivating all NZP-CSI-RS Resources per set) may cause unnecessary activations of all NZP-CSI-RS Resources under the LTM CSI Resource, which could cause increased measurement overhead at UE.
Proposal 2: RAN2 agree to support the selective activation/deactivation of SP CSI-RS resources by introducing an ordinal index to LTM CSI-RS Resource List (ltm-CSI-RS-ResourceList-r19) along with TCI state ID in LTM SP CSI-RS activation/deactivation MAC CE.
Observation 3: Along with the selective activation/deactivation, the delta update of SP CSI-RS resources can provide more flexibility and less signalling overhead for SP CSI-RS resource management.
Proposal 3: RAN2 agree to support the delta activation/deactivation of SP CSI-RS resources, where additional SP CSI-RS resources are newly activated or partial activated SP CSI-RS resources are deactivated while UE keep the activation status for other SP CSI-RS resources than the specified.
Observation 4a: Each cell (serving and candidate) has its own LTM CSI Resource Configs, and they may or may not have overlapping NZP-CSI-RS Resources.
Observation 4b: Any SP CSI-RS that UE continues to measure after LTM cell switch may not be defined as LTM CSI Resource Config, or even if it’s configured, it may not be of interest from the target cell point of view. Then those SP CSI-RS resources of no interest would need to be still measured by UE which causes measurement overhead and potential scheduling restriction.
Observation 4c: When UE continues to measure some SP CSI-RS resources unnecessarily, the target cell may eventually end up sending two different MAC CEs – one for deactivating SP CSI-RS resources of no interest and the other for activating SP CSI-RS resources of interest. This incurs more signalling overhead than sending one activation MAC CE after LTM cell switch (assuming all SP CSI-RS resources are deactivated).
Proposal 4: RAN2 agree to have UE deactivate all activated SP CSI-RS resources after LTM cell switch, and have the target cell send LTM SP CSI-RS activation MAC CE to activate SP CSI-RS resources of target cell’s interest. 
Observation 5: Option 1 is a straightforward way to distinguish between Type 1 and Type 3 beams, and the explicit distinction between them could be beneficial for the truncated MAC CE where Type 1 beams can be prioritized over Type 3 beams.
Proposal 5: RAN2 agree to support Option 1, i.e., to introduce four codepoints to represent one of {type1, type2, type3, type4}.
Observation 6: LTM CSI resource is present for all events, and for Event LTM2 hence Event LTM2 can leverage the concept of implicitly determining the current beam RS based on RS type in LTM CSI resource, which is effectively the same as current beam RS determination for Event LTM3.
Proposal 6: For Event LTM2, the current beam RS is implicitly determined by the RS type of the configured LTM CSI resource:
If the configured LTM CSI resource includes SSB resource, then UE can follow Scheme-2. 
If the configured LTM CSI resource includes CSI-RS resource, then UE can follow Scheme-1 or Scheme-2 depending on gNB configuration (i.e., CSI-RS resource set configured with repetition).
Observation 7a: Current beam measurement only for Event LTM2 in L1 MR MAC CE would serve the same purpose as Event1 in UE-initiated/event-driven beam report, without providing any other information from mobility point of view.
Observation 7b: Given that LTM CSI resource is mandatorily present and also used for the current beam RS determination, then it would be sensible to have the common measurement & reporting procedure between Event LTM2 and LTM3. 
Proposal 7: RAN2 agree to support the same report format for Event LTM2 as LTM3, i.e., candidate RSs under LTM CSI Resource Config are measured and included in L1 MR MAC CE, and the current beam reporting is configured by reportCurrentBeam-r19 (FFS whether reportCurrentBeam-r19 shall be set to TRUE for Event LTM2). 
Observation 8: The differential reporting method (i.e., the first beam which has the highest report metric serves as a reference beam and the rest beams are represented as a differential value) has been used for legacy L1 and L3 RSRP reporting as well as event-triggered L1 MR MAC CE, therefore it can be used for truncated L1 MR MAC CE.
Proposal 8: For truncated L1 MR MAC CE, RAN2 agree to support the same differential L1-RSRP reporting method as regular L1 MR MAC CE.
Observation 9: It is possible that UE detects multiple events triggered but the available grant size is not sufficient to accommodate all triggered events’ report even with the truncated MAC CE hence the prioritization among triggered events needs to be discussed.
Proposal 9: RAN2 to discuss the following event prioritization rule and down-select for truncated L1 MR MAC CE:
Option 1: Define a priority order among Event LTM 2/3/4/5 in the spec.
Option 2: Introduce an RRC parameter for the priority value to be associated with the event configuration
Option 3: Leave it up to UE implementation
Observation 10: Based on 4 different beam types (working assumption) from the last RAN2 meeting, the prioritization among beam types could be discussed to clarify what kind of beams and beam types should be included in L1 MR MAC CE (regular and truncated). 
Proposal 10: RAN2 to confirm above steps (highlighted) as a baseline for L1 MR MAC CE payload generation.
Observation 11: The presence of pending beam results (beam measurements that are dropped via truncation) and/or pending reports (triggered events’ reports that are dropped due to event prioritization) cannot be signalled to gNB, which could take a long time for UE to send all triggered events’ report to gNB.
Proposal 11: RAN2 agree to support explicit indication(s) of pending beam results and/or pending reports in L1 MR MAC CE.
Observation 12a: The traditional measurement report with the ‘snapshot’ of measurement results can cause mobility problems such as handover failures or ping-pong handovers.
Observation 12b: Additional signalling of the L1-RSRP change rate (or “slope”) can help serving cell choose the candidate beam that is expected to remain good after LTM cell switch.
Proposal 12: RAN2 to discuss adding the slope information to the event-triggered L1 measurement report MAC CE.
Observation 13: Per-beam level event evaluation may lead to an event condition being met by different beams several times with a short time interval. Triggering the event-triggered measurement reports in each time instance could lead to too many event-triggered reports transmitted. Therefore, it would be beneficial to control the amount of time between two consecutive event-triggered measurement reports for a particular event.
Proposal 13a: RAN2 to introduce a prohibit timer with the following behavior:
The timer starts after an event-triggered measurement report is triggered based on fulfilling an event condition.
While the timer is running, no new event-triggered measurement report can be reported at least for the same event.
Proposal 13b: RAN2 to discuss whether the granularity of configuration of a prohibit timer for an event can be at 
Option (a): per event
Option (b): per candidate cell
Option (c): per beam
Option (d): Option (a) through Option (c) based on configuration
Observation 14a: For L3 measurement report, the same HYS and TTT are applied to both entering and leaving conditions. Since L3 measurement report and HO deal with the cell level measurement (not beam level), it won’t be sensitive to identifying the leaving condition quicker. 
Observation 14b: For L1 measurement report, keeping track of the best candidate beam is crucial due to the possible TCI state activation and/or early UL synchronization. Therefore, any candidate beam that is not satisfying the better quality than the serving beam (i.e., leaving condition) needs to be identified as quickly as possible.
Observation14 c: In order to achieve rather conservative entering condition but a bit aggressive leaving condition, separate configurations of HYS and/or TTT for leaving condition is desirable. 
Proposal 14: Support the configurability of different HYS and/or TTT values between entering and leaving conditions with following options:
Option 2: Keep two sets of HYS and TTT, one for entering condition and the other for leaving condition
Option 3: Keep one set of HYS and TTT for both entering and leaving conditions as a baseline, but NW can optionally configure another set of HYS and/or TTT for leaving condition (i.e., HYS and/or TTT for leaving condition can be overridden by additional configuration, if provided)

TDoc file reading error

3GPP TSG-RAN WG2 #130	R2-2503859
Malta, May 19th – 23rd, 2025						    	 

Agenda item:	8.6.3
Source: 	Ericsson
Title:  	Discussion on L1 event-based measurements
Document for:	Discussion and Decision

Conclusion
In the previous sections we made the following observations: 
Observation 1	The UE might have already measured other LTM candidates even if it is only configured with LTM2.

Based on the discussion in the previous sections we propose the following:
Proposal 1	The following beams can be included within a event-triggered L1 measurement report:
a.	Type1 beam: a beam that has satisfied the entry condition of the event for the entire TTT, triggers the MR MAC CE, and enters the beamTriggeredList for the first time.
b.	Type2 beam: a beam that has satisfied the leaving condition of the event for the entire TTT, triggers the MR MAC CE, and exit the beamTriggeredList.
c.	Type3 beam: a beam that is neither type1 nor type2 but has remained in beamsTriggeredList (the beam was reported as type1 beam before).
d.	Type4 beam: a beam that is neither type1 nor type2 and not included in beamsTriggeredList (i.e., just extra beam info)
Proposal 2	RAN2 to confirm the working assumption to introduce four codepoints to represent one of {type1, type2, type3, type4} beams.
Proposal 3	UE stop to measure the activated semi-persistent CSI-RS resources after cell switch (Option 1).
Proposal 4	It is up to UE implementation to include measured beams for other LTM candidate cells when reporting a L1 MR MAC CE triggered by a LTM2 event.

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

Agenda Item:	8.6.3
Source:	Panasonic
Title:	Discussion on truncated L1 measurement reporting 
Document for:	Discussion

Conclusion
In this paper, we have discussed differential L1-RSRP reporting for truncated MR MAC CE. We have the following proposal.
Proposal 1. For truncated L1 measurement report MAC CE, the best quality beam among the beams included in truncated L1 measurement report MAC CE is taken as the reference beam as the first one. The differential L1-RSRP value is derived based on the absolute L1-RSRP of the reference beam. 

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

Agenda item:		8.6.3	L1 event triggered measurement reporting
Title:		Remaining issues on MR MAC CE
Source:		NEC
Document for:		Discussion and Decision
1. 

Conclusion
In this contribution we discussed remaining issues for MR MAC CE and made the following proposals.

Event LTM2:
Proposal 1: For MR triggered by LTM2, the UE includes only the current beam information in the MR MAC CE.

Event-periodic reporting:
Proposal 2: RAN2 to agree that the beam triggering the MR MAC CE due to expiry of periodical reporting timer is also the Type1.
Proposal 3: RAN2 to discuss need of clarification for event-periodic reporting, where one example is to add the following text at the end of the NOTE 1: “and the RS that triggers this measurement report MAC CE due to expiry of periodical reporting timer.”

Normal MR MAC CE vs Truncated MR MAC CE:
Note: In this part, we assume the P2 for the Type1 definition.
Observation 1. Type1, 2 beams are essential beams in event-triggered measurement report, while Type3, 4 beams would be less important from network perspective.
Observation 2. Given that only normal MR MAC CE reporting cancels the triggered measurement report, the truncated MR MAC CE is used only when there are some remaining essential beams (e.g. Type1,2). Otherwise, it results in undesirable consequence that a triggered measurement report always includes maximum number of beams (i.e. up to N in total) by one or more MAC CEs.
Observation 3. As an alternative to the current approach in the running CR, following approach may be useful:
Normal MR MAC CE is used only when the MAC CE can include all the Type1, 2 beams, serving beam and the Type3, 4 beams up to N in total. Otherwise, truncated MR MAC CE is used.
UE cancels the measurement report when the normal MR MAC CE is used, or if there is no remaining Type1, 2 beam when the truncated MR MAC CE is used.

Proposal 4: RAN2 to select one of the following two approaches:
Approach 1 (using current running CR as baseline)
Normal MR MAC CE is used only when the MAC CE can include all the Type1, 2 beams and serving beam at least. Otherwise, the truncated MR MAC CE is used.
UE cancels the measurement report when the normal MR MAC CE is used.
Approach 2 (alternative)
Normal MR MAC CE is used only when the MAC CE can include all the Type1, 2 beams, serving beam and the Type3, 4 beams up to N in total. Otherwise, the truncated MR MAC CE is used.
UE cancels the measurement report when the normal MR MAC CE is used, or if there is no remaining Type1, 2 beam when the truncated MR MAC CE is used.

Handling of remaining MR caused by insufficient grant:
Proposal 5: RAN2 to confirm that the UE prioritizes the beams in the order of Type1, Type2, Type3 and Type4 for L1 measurement report. Prioritization among beams of the same type is left to UE implementation.
Proposal 5a: RAN2 to discuss whether to capture the P5 in the specification (e.g. NOTE) or in the Chair notes.

TDoc file reading error

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

Agenda Item:	8.6.3
Source: 	Transsion Holdings
Title:  	Discussion on L1 event triggered measurement reporting
Document for:	Discussion and Decision

Conclusions 
In this contribution we discussed issues related to measurement enhancement for LTM and made the following proposals:
Proposal 1:  The measurement priority for candidate cell or beam can be defined, UE priority measures the candidate cell or beam with high priority.
Proposal 2: The purpose of event triggered L1 measurement can be included in the measurement configuration to avoid repeated triggering early synchronization.
Proposal 3: The TA available information can be included in the measurement report to avoid repeated triggering early synchronization.

4 

3GPP TSG-RAN WG2 Meeting #130	R2-2504115
St. Julian's, Malta, 19th – 23rd May, 2025
Agenda Item:	 8.6.3
Source:	 Huawei, HiSilicon
Title:	 Discussion on L1 event-triggered measurement reporting
Document for:  Discussion and Decision
1	

Conclusion
In this paper, we have addressed the objective regarding improvements in event-triggering reports for LTM. There are the following observations and proposals:
Semi-persistent CSI-RS measurement for LTM
Proposal 1: UE should continue to measure SP CSI-RS resources of target cell after the cell switch and stop to measure the other candidate cells if the target cell is configured with CSI acquisition (Option 3).
Measurement report MAC CE
Proposal 2: There is no need to distinguish between Type 1 and Type 3 beams. Three codepoints should be introduced to represent the following: {Type 3, Type 2, Type 4}.
Proposal 3: In the MR MAC CE, adopt a uniform format for all reported beams, including the current beams.
Event evaluation
Proposal 4: Follow R18 LTM to include SpCell in the LTM candidate configuration if the UE is configured to current beam.
Proposal 5: If the serving cell is configured as an LTM candidate cell in the LTM candidate configuration, for this candidate cell, there is no need to perform event evaluation for EventLTM3/4/5. 
Other open issue list
Proposal 6: (MAC-5) The measurement results of the candidate beams should also be included in the MR triggered by LTM2.
4	

3GPP TSG-RAN WG2 Meeting #130	R2-2504120
St. Julian's, Malta, May 19th – 23rd, 2025
Agenda Item:	 8.6.3
Source:	 Huawei, HiSilicon, Nokia, NTT Docomo, OPPO, ZTE Corporation 
Title:	 Discussion on the support of mTRP in event-triggered LTM
Document for:  Discussion and Decision
1	

Conclusion
In this paper, we have discussed how event-triggering LTM reports coexist with the multiple TRP configuration. The following proposals are presented:
Proposal 0: Confirm that the co-existence between event-triggered measurement report and mTRP is supported.
Proposal 1: When mTRP is configured for the serving cell, UE should use the best beam of the two current beams for event evaluation for LTM2/3/5.
Proposal 2: When mTRP is configured for the serving cell, only the best current beam is reported in the MR MAC CE. FFS whether beam index for the current beam is reported.
4	

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

	

Agenda item:	8.6.3
Source:	Nokia
Title:	Final Details on L1 Measurement Reporting Enhancements for Rel-19 LTM
WID/SID:	NR_Mob_Ph4 - Release 19
Document for:	Discussion and Decision
1	

Conclusion
This paper discussed final RAN2 aspects of LTM L1 measurement framework which shall be addressed in Release 19. The following observations have been made: 
Observation 1: The only difference between type1 and type3 beams is that type1 denotes a beam that fulfils the condition for the first time whereas type3 is used to label a beam which has been already reported but remains in the “beamsTriggeredList” (such beam was reported as type 1 beforehand).
Observation 2: If type1 and type3 beams fulfil the entry criteria for reporting then any of these could be a suitable candidate for becoming the target beam (i.e. the differentiation does not make sense).
Observation 3: Option 1 brings additional complexity to the UE, as the UE needs to keep track of the beams previously reported and maintain their status.
Observation 4: L2 filtering for LTM could be optionally configured by the NW and applicable just to certain scenarios. 
Observation 5: TTT and L2 filtering together are important parameters for tuning mobility KPIs.
Observation 6: A prohibit timer could be applied for the LTM event triggered reporting to avoid too frequent measurement reporting.
Observation 7: There is no reason to deviate from the R18 reporting parameters, where reporting of up to 16 beams can configured.
Observation 8: RAN1 confirms the maximum of 16 beams can be reported and that amount is independent of whether the serving beam is included.
Observation 9: RAN1 may introduce the capability to indicate the maximum number of beams that the UE supports.
Observation 10: The number of reported candidate beams that do not fulfil the reporting criteria should be limited.
Observation 11: The offset value configuration and limiting UE measurements per candidate cell are different features and should not be mixed.
Observation 12: Any configuration to limit measurements for certain candidate cells or RS of certain candidate cells, at least in R19 should be done via CSI resource configuration.
Observation 13: Offset value can be configured for a candidate cell as part of the reporting configuration. The candidate ID. 
Observation 14: If the offset value is not configured for the certain candidate cell or the candidate ID is not present it should mean that offset value is not applied for the beams of the candidate cell when evaluating the reporting criteria. 
Observation 15: For Rel-18/19 LTM and Rel-19 CLTM, RAN2 has supported the cell switch to a target PCell with mTRP deployment (i.e., 2 TA).
Observation 16: An ltm-NZP-CSI-RS-ResourceSet contains CSI-RS indices from the LTM-Candidate IE, but it may not directly map to any NZP-CSI-RS-ResourceSet of a candidate cell.
Observation 17: Activating a candidate’s NZP-CSI-RS-ResourceSet may not guarantee activation of all SP CSI-RSs that are actually part of the measurement/reporting configuration.
Observation 18: RAN1 has agreed to support SP CSI-RSs for early CSI acquisition for the target cell and has requested RAN2 to provide the MAC CE design for activation/deactivation of SP CSI-RSs.
Observation 19: The configuration structure for early CSI may differ from that of L1-RSRP measurements, and RAN1 is expected to discuss this further in the next meeting.
And the following has been proposed:
Proposal 1: RAN2 is asked to adopt Option 3 and therefore reject the working assumption taken at RAN2#129bis. 
Proposal 2: RAN2 reconsiders previous decision and specifies L2 filtering of L1 measurements for event triggered reporting.  The L2 filtering at MAC is applied for candidate RS in similar manner as L3 Beam filtering (see TS 38.300, section 9.2.4). 
Proposal 3: The UE uses truncated MR MAC CE when it is not able to report all the beams that triggered the report or beams that have earlier triggered the report (i.e. type1 or type3 if Option 1 is adopted), up to the configured number of beams.
Proposal 4: The truncated MR MAC CE can only include RSRIs of beams that fulfil or have fulfilled the triggering conditions earlier.
Proposal 5: If the triggered beam (the beam or beams that triggered the report) is the type1 the UE includes first the beam or beams that triggered the report:
After that the UE includes the beams that are reported for leaving condition (type2), if these exist
After that the UE includes the beams that are reported as type3 (i.e. still meet the triggering condition but were reported already beforehand).
Proposal 6: If Option 3 is adopted then then type1 and type3 are not differentiated and are reported first in MR MAC CE.
Proposal 7: RAN2 to support a prohibit timer for event triggered reporting. The prohibit timer is applied per reporting configuration.
Proposal 8: For reporting beams in MR MAC CE, up to 16 beams can be included. Potential candidate values for the number of beams are: {1,2,3,4,8,12,16}.
Proposal 9: A maximum limit should be set for the number of candidate beams in the MR MAC CE that do not fulfil the reporting criteria.
Proposal 10: RAN2 to slightly revise the existing agreement to: offset value can be configured in the reporting configuration per candidate cell. If offset value is configured, the offset value is used for event evaluation for the RS included in the CSI resource configuration for that candidate cell. If the offset value is not configured for a candidate cell, the UE does not apply offset value for the candidate cell. 
Proposal 11: Coexistence of LTM event-triggered reporting and mTRP operation at the serving cell is supported in Rel-19.
Proposal 12: If the UE is configured with mTRP operation, one of the following options should be selected for event evaluation:
Option 1: UE may select which of the two TCI states it uses (i.e. left to UE implementation).
Option 2: UE selects the TCI state (beam) with higher RSRP for event evaluation
Proposal 13: If the network configures the UE to report serving beam information when the UE is operating with  mTRP in the serving cell, the MR MAC CE should include an indication of whether the reported serving RSRP is associated with the first or second TCI state.
Proposal 14: Use ltm-NZP-CSI-RS-ResourceSet instead of NZP-CSI-RS-ResourceSet in the MAC CE to indicate the set of SP CSI-RSs to be activated for a candidate cell.
Proposal 15: RAN2 waits for RAN1 to finalize the configuration structure for early CSI before starting the MAC CE design for activation/deactivation of SP CSI-RSs.

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

Agenda Item:	8.6.4
Source:	InterDigital, Inc.
Title:	LCP for LTM measurement report MAC CE.
Document for:	Discussion

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

Proposal 1: Truncated MAC CE for Event Triggered L1 Measurement Report has a higher LCP priority than non-truncated report.

Proposal 2: Truncated MAC CE for Event Triggered L1 Measurement Report has higher LCP priority than any other LCID except MAC CE for C-RNTI, or data from UL-CCCH (as per the current running CR).

Proposal 3: Non-truncated MAC CE for Event Triggered L1 Measurement Report has lower LCP priority than BSR and higher priority than data from any Logical Channel, except data from UL-CCCH.

3GPP RAN WG2 Meeting #130	R2-2504263
St.Julians, Malta May 19th – 23rd, 2025             
Agenda Item:	8.6.3
Source:	Ofinno
Title:	Discussion on L1 event triggered measurement report
Document for:	Discussion, Decision                        

Conclusions
The contribution discussed aspects related to open issues for L1 event triggered MR. The following observations and proposals are made:
Observation 1: (MAC-6) Truncated L1 MR MAC CE indicates to network about more beams that triggered the MR is pending to be transmitted.
Observation 2: (MAC-6) Network can trigger LTM cell switch or initiate early UL sync based on receiving a truncated L1 MR MAC CE.
Proposal 1: (MAC-6) After accommodating the triggered beams, prioritize including the serving beam information in truncated L1 MR MAC CE.
Proposal 2: (MAC-6) In truncated L1 MR MAC CE, introduce a field indicating whether serving beam information is included or not.
Observation 2: (MAC-7) When multiple MRs are triggered and an UL grant cannot accommodate all the triggered MRs, the UE triggers SR for MRs that are not transmitted. 
Proposal 3: (MAC-7) If multiple MRs are triggered and UL grant is not sufficient to accommodate all the MRs, maximize the number of L1 MR MAC CEs (normal and/ or truncated) that is transmitted in the MAC PDU.
Proposal 4: (MAC-7) if multiple MRs are triggered and UL grant is not sufficient to accommodate all the MRs, indicate in one of the normal or truncated MRs that other MRs are triggered and pending for transmission.
Observation 3: (MAC-15) A UE configured to transmit candidate beams not satisfying an LTM event condition, transmits a truncated L1 MR MAC CE when an available UL grant can accommodate all the candidate beams that satisfies an LTM event condition but cannot accommodate candidate beams that does not satisfy the LTM event condition. 
Observation 4: (MAC-15) A UE configured to transmit current serving beam information, transmits a truncated L1 MR MAC CE when an available UL grant can accommodate all the candidate beams that satisfies an LTM event condition but cannot accommodate the current serving beam information. 
Proposal 5: (MAC-15): A normal L1 MR MAC CE is transmitted if available uplink grant is sufficient to accommodate a normal L1 MR MAC CE, comprising beam information of all the triggered beams, plus its subheader.
Proposal 6: (MAC-15) A triggered L1 MR is cancelled when all the triggered beams of the MR are transmitted.
Proposal 7: (MAC-16) When an L1 MR is triggered and not transmitted, and if a beam that triggered an L1 MR upon satisfying an entering condition of an event satisfies a leaving condition of the event, the triggered MR is cancelled.
Observation 5: For a candidate cell, after triggering MR for a first candidate beam satisfying the LTM event, a second candidate beam may satisfy the LTM event.
Proposal 8: Introduce prohibit timer for event triggered L1 MR, with the following behavior: 
The prohibit timer is started after triggering a new MR for a candidate cell satisfying an entry condition of an LTM event for TTT.
While the prohibit timer is running, a new MR is not triggered for the same candidate cell for the same LTM event.
While the prohibit timer is running, a new MR is triggered for the same candidate cell satisfying an entry condition of a different LTM event.
Proposal 9: If UL grant is sufficient to accommodate N candidate beams but is not sufficient to accommodate the serving beam, transmit a normal L1 MR MAC CE without including the serving beam.

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

Agenda Item:	8.6.3
Source: 	Rakuten 
Title:  	Remaining issues of L1 event triggered measurement reporting 

Document for:	Discussion, Decision

Conclusion
We have the following observations:
Error! Reference source not found.	Error! Reference source not found.
Error! Reference source not found.	Error! Reference source not found.
We have the following proposals: 
Proposal 1	Requesting resource allocation using the legacy BSR procedure to send the event-triggered L1 measurements MAC CE is supported.
Proposal 2	UE stops to measure the activated semi-persistent CSI-RS resources after LTM cell switch.
Proposal 3	When LTM event-triggered reporting and mTRP operation coexist in the serving cell, the network configures which of the indicated TCI states of the serving cell is to be used for LTM event-triggered measurements evaluation. This shall be able to be modified subsequently.
Proposal 4	RAN2 discusses the possibility of using event based L1 measurements for the purpose of triggering LTM candidate cell addition and release.
Proposal 5	RAN2 discusses the possibility of avoiding configuring redundant measurements for the same purpose i.e LTM candidate cell addition and release.

3GPP TSG-RAN WG2 Meeting #130	R2-2504402
St.Julians, Malta,  May 19th – 23rd , 2025
Agenda Item:	8.6.3
Source:	CMCC
Title:	Discussion on L1 event triggered measurement reporting
Document for:	Discussion

Conclusions
In this contribution, we analyse for measurement event evaluation, following are the observations and proposals.
Observations:
Observation 1: Due to the beam level TTT, for a certain event, there may be multiple beams satisfying the entry/leaving condition at a certain moment.

Proposals:
Proposal 1: The current beam is not counted in the 16 beams, that is, when the MAC CE carries the measurement results of 16 beams, the UE can carry the current beam measurement results at the end.
Proposal 2: RAN2 follow RAN1's conclusion and make it clear that LTM2 also needs to configure at least one candidate beam resource.
Proposal 3: If there are additional uplink resources available, the UE should be allowed to carry the measurement results of LTM candidate beams in the LTM2 MR MAC CE.
Proposal 4: When multiple beams meet the triggering condition of a configured event at the same time, they will be included in one MR MAC CE.
Proposal 5: When the UL grant can only carry triggered beams, use the triggered beam with the best quality as the reference beam in the truncated MR MAC CE.
Proposal 6: When the truncated MR MAC CE is not enough to carry all triggered beams, the beam that meets the entry condition should be reported first.
Proposal 7: If there is no dedicated SR configuration assigned for L1 measurement report MAC CE transmission, then an uplink grant should be requested through the RACH procedure. In addition, similar to the BFR processing in SpCell, the UE should be allowed to carry the MR MAC CE in the transmitted Msg 3.
Proposal 8: Activate/deactivate semi-persistent CSI-RS resource based on the resource set containing multiple LTM candidate cells.

TDoc file reading error

3GPP TSG RAN WG2 #130       	                            R2-2504422
St Julian’s, Malta, May 19th – 23rd, 2025
Agenda Item:	8.6.3 
Source:	     KDDI Corporation
Title:	Discussion on L1 event triggered measurement reporting 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: Confirm Working assumption Option1: To introduce four codepoints to represent one of {type1, type2, type3, type4} for detailed beam management and future scalability.
Proposal 2: Support mTRP in serving cells for LTM event-triggered reports.

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

Agenda item:	8.6.3
Source:	Samsung
Title:	Remaining Issues of L1 Event Triggered Measurement Report
WID/SID:	NR_Mob_Ph4-Core
Document for:	Discussion and Decision

Conclusion
Based on the discussion, we have the following proposals.
Proposal 1: CSI-RS resources for LTM including semi-persistent CSI-RS resources are reported by UCI, event-triggered L1 measurement report MAC CE, and this resources are used for evaluation of the conditional LTM.

Proposal 2: UE continues to measure the activated semi-persistent CSI-RS resources after LTM cell switch (i.e. support the Subsequent LTM).
Proposal 3: RAN2 send LS to RAN3 for the issue of handling the activated SP CSI-RS resources after LTM cell switch. 

Proposal 4: CSI-RS resource configuration for LTM including semi-persistent CSI resources should be common, i.e. semi-persistent CSI resources for all candidate cells should be configured in LTM-CSI-ResourceConfig.

Proposal 5: For the generalized rule to create the (truncated) event-triggered L1 MR MAC CE, apply the below rules:
Introduce the two group of beams (i.e. triggered beam and non-triggered beam), so there would be two reference beam and RSRP based on the best beam quality.
Group of triggered beam: Type 1 and Type 2
Group of non-triggered beam: Type 3 and Type 4
Priority of Types (Type 1 and Type 2 -> Type 3 -> Type 4)
Based on the above rule, both the event-triggered L1 MR MAC CE and the truncated event-triggered L1 MR MAC CE added the contents
If the truncated event-triggered L1 MR MAC CE is needed, just truncate the MR MAC CE based on the size i.e. no need to re-formulate the MAC CE and contents.
Proposal 6: UE continues to evaluate the event condition for the L1 MR event after UE request SR to the source cell and the L1 MR procedure is completed i.e. L1 event evaluation should be continued during L1 MR procedure.

Proposal 7: UE generates the (truncated) event-triggered L1 MR MAC CE when UE receives the UL grant, and include the latest beam’s measurement result at this time.

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

Agenda Item:	8.6.3
Source:	HONOR
Title: 	Discussion on measurement event evaluation and report
Document for:	Discussion and decision
1	

Conclusions
In this contribution, we discussed the L1 measurement enhancement for Rel-19 mobility WI. Based on the discussion, the following observation and proposals are concluded:
Proposal 1: RAN2 to discuss how to reduce the signalling burden caused by L1 MR: 
prohibit timer, 
event LTM2~5 combined with other conditions (early-sync status),
the number of satisfying beams,
Others.
Proposal 2: RAN2 to discuss the additional criterion for the reported beam not satisfying the condition. FFS the criterion is a pre-configured RSRP/RSRQ threshold, not satisfying the leaving condition, satisfying the entering condition, and so on.
Proposal 3：There is no need to differentiate the Type1 and Type3 beam.
Proposal 4: One bit to indicate the entry triggered beam and one separate bit to indicate the leaving triggered beam. The extra beam (type 4) is neither an entry triggered beam nor a leaving triggered beam then it is a type4 beam. 
Proposal 5: (MAC-8) RAN2 to support the coexistence of the mTRP and L1 MR.
Proposal 6: (MAC-8) If at least one of the current beams met the trigger condition during TTT, then the report could be triggered when the corresponding TTT expires. If all the current beams don’t meet the trigger condition, the TTT stops.
Proposal 7: (MAC-8) The index of current beam is also included in the MR MAC CE if this is mTRP. 
4	

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

Agenda Item:	8.6.3
Source: 	ASUSTeK
Title:  	Discussion on event-triggered L1 MR MAC CE
Document for:	Discussion and Decision

Conclusion
We have the following observation and proposals for MR MAC CE for LTM:
Proposal 1:	When generating a truncated or non-truncated Event Triggered L1 Measurement Report MAC CE, the UE decides which beams to be included in the MAC CE, up to the maximum number of reported beams (based on size of UL grant or maxNumberOfReportedBeams), based on the one of the two approaches:
Approach 1: The UE selects the reported beams in decreasing order of beam quality.
Approach 2: the UE selects the reported beams in the following order:
Triggered beam(s) that meets the entering condition, in decreasing order of beam quality. 
Triggered beam(s) that meets the leaving condition, in decreasing order of beam quality.
Beam(s) that does not satisfy any event condition, in decreasing order of beam quality.
Proposal 2:	When generating a truncated or non-truncated Event Triggered L1 Measurement Report MAC CE, the reported beams are included in decreasing order of beam quality.
Observation:	When there are multiple triggered L1 measurement reports for different events, the UE needs to generate and report multiple MR MAC CEs.
Proposal 3:	When multiple MR MAC CEs are to be reported, the UE prioritizes MR MAC CEs containing smaller report ID (ltm-CSI-ReportConfigId).

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

Agenda Item	: 8.6.3
Source	: Fraunhofer HHI, Fraunhofer IIS 
Title	: Discussion on LTM event-triggered measurement reporting 
Document for	: Discussion 

Conclusion

Based on the discussion, we have the following observations.
Observation 1: The NW has the capability to provide explicit signaling to instruct the UE on how to proceed with measuring activated semi-persistent CSI-RS resources following a cell switch.
Observation 2: In the absence of explicit signaling, the UE has two options: it may either continue or stop the measurement of the semi-persistent CSI-RS resources that were active prior to the cell switch.
Observation 3: To allow continued measurement of activated semi-persistent CSI-RS resources post-switch, candidate cells must share their resource configurations. This collaborative approach increases system overhead significantly.
Observation 4: If the UE ceases measurement of active semi-persistent CSI-RS resources after a cell switch, the overhead is minimized. However, this leads to increased latency caused by temporary interruption in communication.

Based on the discussion, we have the following proposals.

Proposal 1: UE is configured to report both CSI-RS and SSB beams within a single measurement report.

Proposal 2: For event-triggered L1 LTM measurement reporting, the number of beams (M) reported can vary for each cell, where N = M × L gives the total number of reported beams.

Proposal 3: For event-triggered L1 LTM measurement reporting, the total number of reported cells (L) can vary, maintaining the total reported beams as N = M × L.

Proposal 4: Configure the UE to report measurements in a differential L1-RSRP format to reduce overhead. 

A single absolute value is reported for the highest RSRP of the SSB and/or CSI-RS beam.
Use differential L1-RSRP values for the remaining measured beams, 
FFS further quantization details, e.g., step size, range, bit width.
Proposal 5: Configure the UE with a prohibit timer that regulates the transmission of measurement reports with the following behavior:
The prohibit timer defines the minimum duration that must pass before a new measurement report can be sent after the previous one.
The timer starts when the first measurement report is triggered, preventing any subsequent event-triggered measurement reports from being transmitted until the timer expires.
Proposal 6: The L1 reporting measured quantity values for SS-RSRP and CSI-RSRP should be utilized for LTM event-triggered measurement reporting at higher layers, e.g., L2. 

3GPP TSG-RAN WG2 #130	R2-2504639
St. Julian, Malta, May 19th – 23rd, 2025
Agenda item:	8.6.3 (NR_Mob_Ph4-Core)
Source:	LG Electronics Inc.
Title: 	Resolving MAC open issues for LTM event triggered MR
Document for:	Discussion and Decision

Conclusion
MAC-LGE1: For given UL grant, multiple LTM MR MAC CEs for the same LTM report config can be included in one MAC PDU? 
Proposal 1: To clarify which option should be used to specify LTM event-triggered reporting
Option1 (multiple MRs triggered, and multiple LTM MR MAC CEs generated): Whenever a new beam satisfies entering condition with TTT for an LTM report config, a new MR is triggered for the LTM report config. If UL grant is received while multiple MRs are triggered for the LTM report config, each triggered MR generates a separate LTM MR MAC CE, i.e., multiple LTM MR MAC CEs are generated. This option is similar to L3 event triggered MR. 
Option2 (multiple MRs triggered, but single LTM MR MAC CE generated): Whenever a new beam satisfies entering condition with TTT for an LTM report config, a new MR is triggered for the LTM report config. Then, if UL grant is received while multiple MRs are triggered for the LTM report config, only one LTM MR MAC CE is generated. The current MAC running CR seems to implement this option.  
Option3: (single MR is triggered, and hence single LTM MR MAC CE generated) If a new beam satisfies entering condition with TTT for an LTM report config, a new MR is triggered if MR has not been already triggered for the LTM report config. Then since at most MR can be triggered for an LTM report config, if UL grant is received, UE generates one MR MAC CE. 
MAC-LGE2: If UE receives UL grant that can accommodate up to M LTM MR MAC CEs while N (>M) MRs have been triggered and all the N MRs are associated with different LTM report configs, how to select M out of N? 
Proposal 2: When UE generates M LTM MR MAC CEs to be included in MAC PDU while N (>M) MR have been triggered and pending, UE selects M LTM events to report by applying FIFO principle based on timing of triggering the concerned MR.
MAC-LGE3: Modification of LTM MR MAC CE structure
Proposal 3: The first octet (Oct1) only includes information common for all the included beams, and R bit for each beam is placed as MSB of the first octet for the beam. The resulting LTM MR MAC CE format is illustrated in Figure 7.

Figure 7. Modified LTM MR MAC CE format
MAC-5 and MAC-LGE4: LTM MR MAC CE triggered by LTM2  
Proposal 4: For LTM MR MAC CE triggered by LTM2, beam measurement results of LTM candidates are included, if configured by network via RRC. For each LTM candidate cell, if included, only one best beam is included, if available, and its beam type is set to 11. RSRI1 and RSRP1 are set to the beam information of the best beam among the included LTM candidate beams.
Proposal 5: For LTM MR MAC CE triggered by LTM2, serving cell beam measurement result is included in RSRPserving field.
Proposal 6: For LTM MR MAC CE triggered by LTM2, RAN2 to decide either one of the following options for the location of RSRPserving. If Option2 is selected, discuss if this structure is also applicable for LTM MR MAC CE triggered by LTM3/4/5 universally.   
Option1: RSRPserving is placed in the last octet 
Option2: RSRPserving is placed in the 2nd octet
Proposal 7: After transmitting truncated LTM MR MAC CE triggered by LTM2, UE cancels the triggered MR.   
MAC-6: Truncated LTM MR MAC CE details. E.g.
Proposal 8: For both regular LTM MR MAC CE and truncated LTM MR MAC CE triggered by LTM 3/4/5, the beams are included in the following order
best quality beam of any type, triggering beam (type00 or type01), type10 beam, and then type11 beam.  
For the beams of the same type, beam of higher quality is included first. 
MAC-7: Whether one UL TB could include more than one truncated MAC CE or only one?
Proposal 9: In case N triggered LTM events are pending, if UL grant is sufficient for including some combinations of L regular LTM MR MAC CEs and M truncated MR MAC CEs with , , but insufficient for including N regular LTM MR MAC CEs, it is up to UE implementation which combination to include. 
MAC-15: Whether the triggered MR should be cancelled if all the triggered beam(s), i.e. Type#00 and Type#01, have been reported, no matter whether truncated MR MAC CE or regular MR MAC CE is used before
Proposal 10: After transmitting truncated MR MAC CE, if there is at least one type00, type01 or type10 beam, triggered MR is not cancelled.  
MAC-16: Whether the triggered MR should be cancelled in the below two cases:
Proposal 11: If a beam which triggered the MR due to entering (or leaving) condition with TTT satisfies leaving (or entering) condition with TTT before receiving UL grant, cancel the triggered MR.