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

Agenda Item:	8.12.3
Source:	Ofinno
Title:	Enhancements for UE-initiated/event-driven beam management
Document for:	Discussion and Decision

Conclusion
In this contribution, we make the following proposals. 
(MAC-1) UL skipping is not applicable to mode-B type-1 CG event-triggered beam report.

(MAC-1) For Rel-16 UL skipping (enhancedSkipUplinkTxDynamic is configured), the UCI for mode-A DG-based UE-initiated report follows the existing procedure (i.e., MAC PDU is generated).

(MAC-1) For Rel-15 UL skipping (skipUplinkTxDynamic is configured), MAC PDU needs to be generated for the UCI for mode-A DG-based UE-initiated report.

Outside of cell DRX active period, the UE does not transmit periodic CSI on PUCCH and semi-persistent CSI on PUSCH/PUCCH but transmits aperiodic CSI.
Outside of cell DRX active period, the UE does not transmit SR and does not deliver any configured uplink grant for a new transmission or retransmission. 
In Mode A of UE-initiated CSI reporting, when a serving cell configured/activated with cell DRX is not in a cell DRX active period:
the UE does not transmit the first PUCCH with a new UCI, and
the UE transmits the UE-initiated CSI report in second PUSCH, if DCI scheduling the second PUSCH is received (similar to aperiodic CSI reporting). 

In Mode B of UE-initiated CSI reporting, when a serving cell configured/activated with cell DRX is not in a Cell DRX active period, the UE does not transmit the first PUCCH with a new UCI. As for the Type 1 configured grant PUSCH transmission, down-select one of the following alternatives:
Alt1: After the UE transmits the first PUCCH with a new UCI in a Cell DRX active period, if the first available Type 1 configured grant PUSCH transmission occasion falls outside of Cell DRX active period, the UE transmits the UE-initiated CSI report in the second PUSCH (i.e., to align with Mode A of UE-initiated CSI reporting). 
Alt2: After the UE transmits the first PUCCH with a new UCI in a Cell DRX active period, if the first available Type 1 configured grant PUSCH transmission occasion falls outside of Cell DRX active period, the UE does not transmit the UE-initiated CSI report in the second PUSCH (i.e., legacy behaviour). 
Alt3: If the first available Type 1 configured grant PUSCH transmission occasion falls outside of Cell DRX active period, the UE does not transmit the first PUCCH with a new UCI in Cell DRX active period.
During FR2 UL gap, the UE performs transmission of the first PUCCH with the new UCI for both Mode-A and Mode-B of UE-initiated CSI reporting and the Type 1 configured grant PUSCH transmission for the Mode-B of UE-initiated CSI reporting (that does not carry UL-SCH).

RAN2 waits for RAN1 discussion/clarification on the UE behavior under the two cases below:
Case 1: No valid PUCCH or PUSCH resource is available to transmit UE-initiated report due to expiry of TAT. 
Case 2: The uplink BWP configured with the first PUCCH resource and/or Type 1 CG PUSCH resource for the UE-initiated CSI reporting is not active
For a serving cell configured with cell DTX, after a new UCI for Mode A of UE-initiated beam reporting is sent on first PUCCH, the UE monitors PDCCH on serving cell(s) in the DRX group of the serving cell, regardless of whether the serving cell is in a cell DTX active period. 

Outside of DRX active time, a UE only transmits aperiodic CSI report, and does not transmit periodic CSI report or semi-persistent CSI report on PUCCH/PUSCH. 
In Mode B of UE-initiated CSI reporting, the UE transmits the UE-initiated CSI report outside of DRX active time (i.e., similar to aperiodic CSI reporting). 

(RRC: UEI-BMR) Remove servCellIndex-r19 from resourceForSecondChannelOfModeB-r19.

3GPP TSG-RAN WG2 Meeting #130		R2-2503627
St. Julian’s, Malta, 19th – 23rd May 2025
Source:	vivo
Title:	Discussion on MAC and RRC open issues for UEI BMR
Agenda Item:	8.12.3
Document for:	Discussion and Decision

Conclusion
In this contribution, we discuss the RRC and MAC open issues on UE-initiated/event-driven beam management, identified in the email discussion. Based on the above discussion, we have the following proposals.
RRC open issues:
RAN2 supports to extend the legacy CSI report configuration framework to support UE-initiated/event-driven beam management, i.e. not moving UEI BM parameters to CSI-MeasConfig.
Similar to the event-triggered report configuration framework for LTM, a new report type, i.e., UEI-BM could be introduced in the CSI-ReportConfig and the UEI-BM corresponding parameters can be replaced under the parameter of the new report type.
For the parameters of the configured grant in Mode B, ul-BWP-id should be configured, but servCellIndex should be removed.
For the parameters of the first PUCCH channel for UE-initiated/event-driven beam management, besides periodicityAndOffset and resource, ul-BWP-id should also be configured for UE to determine the PUCCH resources.

MAC open issue:
(MAC-4) RAN2 assumes to support dynamic update of the measurement RS in the measurement resource set for new beam(s) by MAC CE, and final decision is up to RAN1.

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

Agenda Item:	8.12.3
Source: 	OPPO
Title:  	Clarification on the UL skipping for event-triggered beam reporting
Document for:	Discussion and Decision

Conclusion
According to the analysis provided above, we have the following observations and proposals:
Observation 1: If the (Rel-15/Rel-16) UL skipping is not enabled, the legacy MAC always generate MAC PDU.
Observation 2: The Rel-15 CG UL skipping is mandatorily enabled without configuration.
Observation 3: The introduction of Rel-16 UL skipping is to fix the UCI multiplexing issue of Rel-15 UL skipping. If the gNB is to multiplex UCI (e.g. HARQ) in PUSCH, the recommended gNB implementation is to configured Rel-16 UL skipping.

Proposal 1: No matter whether Rel-15/Rel-16 uplink skipping is enabled, the MAC does not generate MAC PDU for mode-B CG.
Proposal 2: No matter whether Rel-15/Rel-16 uplink skipping is enabled, the MAC entity does not differentiate mode-A DG from other DG. No specification change is needed.
Proposal 3: If UCI other than aperiodic CSI is to be multiplexed in mode-A DG, it is up to gNB implementation to configure Rel-16 UL skipping or Rel-15 UL skipping or no skipping. No specification change is needed.

TDoc file reading error

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

Source:	CATT
Title:	Discussion on UE-initiated Beam Reporting
Agenda Item:    8.12.3
Document for:  Discussion and Decision

Conclusion
Based on the previous analysis in Section 2, our contributions are summarized as follows:
Proposal 1: To support the mode-A UCI reporting in DG PUSCH multiplexed with the MAC PDU if the R15 skipUplinkTxDynamic is configured, no further change is needed in the current MAC spec, i.e., it is already covered by the “if” condition of no aperiodic CSI requested for this PUSCH transmission.

3GPP TSG-RAN2#130 	R2-2503821
St. Julian’s, Malta, 19th May – 23th May, 2025	
	

Agenda item:		8.12.3 (NR_MIMO_Ph5-Core)
Source:	LG Electronics Inc.
Title: 	Discussion on UEI beam reporting impact
Document for:	Discussion and Decision
1.	

Conclusion
In this document, we analysis RAN2 impacts of UEI beam reporting, and made observations and proposals as follows.
Observation 1. RAN2 has a consensus that Mode-B UEI beam reporting is not considered in the MAC procedure for R15/16 UL skipping during post-email discussion.
Proposal 1. RAN2 treats Mode-A UEI beam reporting as aperiodic CSI reporting. 
Proposal 2. Mode-A UEI beam reporting follows Rel-15 UL skipping procedure, as like aperiodic CSI reporting.
Proposal 3. Mode-A UEI beam reporting can be transmitted regardless Active Time.

4.	

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

Agenda item:	8.12.3
Source:	Nokia
Title:	RAN2 Aspects of the NR MIMO 
WID/SID:	NR_MIMO_Ph5-Core - Release 19
Document for:	Discussion and Decision
1	

Conclusion 
This document has made the following observations:
Observation 1: RAN1 has not concluded on the details of the prohibit timer, or even whether to introduce a timer.
And proposed the following:
Proposal 1: RAN2 waits for further progress from RAN1 regarding prohibit timer for first PUCCH re-transmissions.
Proposal 2: For Rel-15 UL skipping (skipUplinkTxDynamic),  same principle as that of aperiodic CSI reporting can be adopted for mode-A DG-based event-triggered beam reporting. 
Proposal 3: Upon UE initiated beam reporting trigger for  Mode A and Mode B UE initiated beam reporting,  if the UL is not synchronized, the UE shall initiate RACH procedure and cancel the pending SR.
Proposal 4: Not to report UE-IBR (Mode A and Mode B) for the deactivated SCell, and cancel any pending UE-IBR
Proposal 5: UE cannot report UE-IBR on the Serving Cell(s) in the corresponding frequency range of the measurement gap configured by measGapConfig.  No MAC impact 

3GPP TSG-RAN WG2 Meeting #130	R2-2504099	
St.Julians, Malta, 19th – 23th May, 2025
Agenda Item:	 8.12.3
Source:	 Huawei, HiSilicon
Title:	 Discussion on remaining issues of UE-initiated/event-driven beam management
Document for:  Discussion and Decision
1	

Conclusion
In this paper, we have addressed the objective regarding some analysis on RAN2 impact for MIMO. There are the following observations and proposals, and text proposal is attached in Annex.
RRC impacts
Proposal 1: RAN2 should discuss whether to use the CSI-reportConfig or the CSI-MeasConfig. FFS on whether the UEIBM parameters should be moved to the CSI-MeasConfig.
DRX impacts on UEIBM
Observation 1: CSI reporting is not transmitted during DRX active time in the case a CSI-Mask is configured.
Observation 2: In the current MAC specification:
Semi-persistent CSI reporting is not allowed during DRX inactive periods. 
The transmission of periodic CSI during non-active periods is controlled by RRC parameters.
The aperiodic CSI reporting is supported regardless of DRX inactive periods.
Proposal 2: In Mode-A of UEIBM, the second uplink transmission is not subject to the DRX active time. \
Proposal 3: In Mode-B of UEIBM, the second uplink transmission should not be transmitted during the DRX inactive time. 
Deactivation of SCell(s) Impact on UEIBM
Observation 3: UEIBM supports cross-CC beam reporting scenarios, enabling a CSI reporting configuration in CC#A to be linked with a measurement resource configuration in CC#B.
Observation 4: For legacy active, periodic, semi-persistent, and aperiodic CSI reporting, there is no need to transmit a measurement report for a deactivated SCell.
Proposal 4: For mode-B of UEIBM, in the cross-CC beam reporting transmission procedure, if CC#B is deactivated, the UE should release any PUSCH resources allocated for UEIBM of CC#B in CC#A. Additionally, the text proposal is provided in the Annex.
UL skipping
Observation 5: RAN2 should consider the MAC impacts of UL skipping for Mode-A beam reporting, given that it carries the MAC PDU as legacy.
Observation 6: UL grant cannot be skipped for aperiodic CSI reporting on PUSCH.
Proposal 5: The Mode-A beam reporting is more similar to aperiodic CSI reporting, which cannot be skipped if there are no available UL data. The detailed spec impacts are outlined in the TP provided in the Annex.
4	

3GPP TSG-RAN WG2 Meeting #130	Tdoc R2-2504186
St Julian’s, Malta, May 19 – 23, 2025
              
Agenda Item:	8.12.3
Source:	Ericsson
Title:	Impacts from UE-initiated/event-driven beam management
Document for:	Discussion, Decision
1	

Conclusion
In the previous sections we made the following observations: 
Observation 1	No need to address the FFS on “whether UEI BM parameters should be moved to CSI-MeasConfig” in RAN2-130.
Based on the discussion in the previous sections we propose the following:
Proposal 1	As a baseline, the events defined for UEI BM should be captured as a new reportConfigType which can also include parameters applicable only for one event. This can be captured once more parameters for this objective are defined by RAN1.

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

Agenda item:	8.12.3
Source:	Samsung
Title:	Open issues on UE-initiated Reporting and RRC parameters
WID/SID:	NR_MIMO_Ph5
Document for:	Discussion and Decision

Conclusion
Based on the discussion, we have the following proposals.
Proposal 1: For skipUplinkTxDynamic (enhancedSkipUplinkTxDynamic is not configured), MAC PDU should be generated if there is UE-initiated report requested on the PUSCH regardless of UL-SCH data availability.
Proposal 2: The existing rule in MAC that handles the overlapping/prioritization between PUSCH and SR/other PUSCH is applied to handle the overlapping/prioritization between the PUSCH of mode-A report and SR/other PUSCH. 
Proposal 2-1: Discuss whether LS to RAN1 is needed to inform RAN2 agreement on handling the overlapping/prioritization between the PUSCH of mode-A report and SR/other PUSCH.
Proposal 3-1: When UE-initiated reporting is triggered but UE has no valid PUCCH resource or no valid type-1 CG for this report, UE initiates RACH. 
Proposal 3-2: When UE-initiated reporting is triggered but UE has no valid PUCCH resource or no valid type-1 CG for this report, discuss how UE transmits the actual report.
Option 1: in Msg3/MsgA;
Option 2: using the uplink grant scheduled by PDCCH addressed to C-RNTI based on which RA procedure is completed;
Option 3: using the uplink grant scheduled by PDCCH addressed to C-RNTI which is provided after the completion of RA procedure.
Proposal 4: Regardless of whether the MAC entity is monitoring PDCCH or not on the Serving Cells in a DRX group, the MAC entity transmits UE-initiated report on PUCCH and PUSCH.
Proposal 5: Discuss whether “UE-initiated report” belongs to CSI report. 
If yes, “CSI report” is also used to refer to “UE-initiated report” and a clarification (e.g., stage-2) is needed; 
otherwise, specify the rule of transmitting UE-initiated report separately and the rule for CSI report is reused at least in activated/deactivated SCell/SCG (clause 5.9, 5.29), handling of measurement gaps (clause 5.14), FR2 UL gaps (clause 5.30), BWP operation (clause 5.15.1), cell DRX operation (clause 5.34.3). 
Proposal 6: For pusch-ResourceOfModeB, the ServCellIndex is not needed, clarify for the configuredGrantConfigIndex that it indicates a type-1 CG in the serving cell where the report configuration is configured.
Proposal 7: Discuss how to configure additionalOneSlotOffsetDoppler per NZP-CSI-RS-Resource Group.
Option 1:  a sequence of {enabled}, where the sequence size is configured by numberOfResourceGroups-r19.
Option 2: a bitmap of length equal to the value of numberOfResourceGroups-r19.

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

Agenda item:	8.12.3     
Source:	Qualcomm Incorporated
Title:	Discussion on UE initiated beam reporting
WID/SID:	NR_MIMO_Ph5-Core – Release 19
Document for:	Discussion

Conclusion
In this contribution, we discussed UL skipping with UE initiated beam report and concluded with the following observations and proposals.
Observation 1. UL skipping may be triggered if a dynamic grant carries only UE initiated beam report.
Observation 2. MAC is not aware of whether a dynamic grant is for UE initiated beam report or whether PHY has UE initiated beam report to send.
Observation 3. UL skipping is not applied by MAC if PHY can indicate to MAC that PHY has UE initiated beam report to transmit.
Proposal 1. To avoid UL skipping, PHY sends an indication to MAC when there is a UE initiated beam report to be sent. 

3GPP TSG-RAN WG2 Meeting #130		R2-2504249
Malta, MT, 19th – 23rd May. 2025
Source:	China Telecom
Title:	Discussion on UE initiated beam reporting
Agenda Item:	8.12.3
Document for:	Discussion and Decision

Conclusion
Proposal 1: When the UE enters the UL out-of-sync state due to TAT expiry and UE initiated beam reporting is triggered, the UE shall initiate a RACH procedure to re-establish UL synchronization.
Proposal 2: If UE performs beam measurements during measurement gap, it is preferable to perform UE initiated beam reporting; otherwise, it tends to not perform UE initiated beam reporting.

TDoc file reading error

3GPP TSG RAN WG2 #130				R2-2504499
Malta, MT, May 19 – 23, 2025	

Agenda Item:	8.12.3 Others (NR_MIMO_Ph5-Core)
Source:		ASUSTeK
Title:				Discussion on RRC impacts for UEI Beam Reporting Mode B
Document for: Discussion and Decision

Conclusion
In this document, we have the following proposals for UEI Beam Reporting Mode B. 
Proposal 1:  Add numOfSymbols-ModeB-r19 in CSI-ReportUE-IBM-r19 to configure time offset, in number of symbols, for determining the first available transmission occasion of PUSCH on CG Type 1 in Mode-B, following the PUCCH transmission of the report notification.
Proposal 2:  Use ConfiguredGrantConfigIndexMAC to indicate Type-1 CG PUSCH resource for the second step of PUSCH transmission in mode-B UE-initiated beam reporting.
Proposal 3:  The UE should ignore nrofHARQ-Processes if it is configured within ConfiguredGrantConfig for UE-initiated beam reporting Mode B.

3GPP TSG RAN WG2 #130				R2-2504500
Malta, MT, May 19 – 23, 2025	

Agenda Item:	8.12.3 Others (NR_MIMO_Ph5-Core)
Source:		ASUSTeK
Title:				Discussion on MAC impacts for UEI Beam Reporting Mode B
Document for: Discussion and Decision

Conclusion
In this document, we have the following proposals for UEI Beam Reporting Mode B. 
Observation:  Initializing CG Type 1 with periodicity is necessary and serves as a common prerequisite for the physical layer to determine the timing for UEI beam reporting.
Proposal:  Add a restriction to clause 5.4.1 to reflect the RAN2 understanding that CG Type 1 PUSCH carrying the Mode-B beam report does not carry a MAC PDU (i.e., UL-SCH).

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

Source:        ZTE Corporation
Title:           Consideration on the Remaining Issues of UEIBM
Agenda item:   8.12.3
Document for:  Discussion and Decision

Conclusion and proposals
With the above analysis, we have the following proposals:
Observation 1: For the UEI mode A CSI report, RAN1 has agreed to reuse CSI request field in DCI format 0_1/0_2 to trigger the transmission of the UEI beam report and thus the UEI mode A CSI report is similar to the legacy aperiodic CSI report.
Proposal 1: The same principle as the aperiodic CSI report for the UL skipping, DRX and dormant BWP shall be adopted for the UEI mode A CSI report. 
Proposal 2: Ran2 to discuss the following 3 options on how to capture the proposal 1 in MAC spec:
Option 1: Add UEI mode A CSI report to every MAC spec chapter (e.g. 5.4/5.7/5.15) that includes aperiodic CSI report;
Option 2: Add a General Note/Description to MAC spec, e.g. the UE’s behaviour for the UEI mode A CSI report is the same as the aperiodic CSI report;
Option 3: No MAC spec impact, and take the UEI mode A CSI report as one kind of the aperiodic CSI report.
Proposal 2a: On how to capture the proposal 1 in MAC spec, select Option 2 as baseline.
Proposal 3: From MAC layer aspect, the similar principle to the legacy semi-persistent CSI report on the PUSCH can be taken as baseline for the UEI mode B CSI report and RAN2 can further discuss some exception cases.
Proposal 3a: As an exceptional case, if the BWP in a SCell is a dormant BWP, the UE can’t perform UEI mode B CSI report for this BWP.
Proposal 4: When UE-initiated report is triggered but there is no valid PUCCH/PUSCH resource to transmit UE-initiated report, the RACH procedure can be triggered without MAC spec impact/or enhancement.

Observation 2: The RAN1 parameters tend to be stable with few FFS on the detail value range, thus RAN2 can start the discussion on the ASN.1 structure.
Proposal 5: Use the choice structure for the Event specific parameters, e.g. 
Event 1: eventThreshold-Event1-r19
Event 2: eventThreshold-r19
Event 7: eventThreshold-r19, valueOfQ-r19
Proposal 6: Move the UEIBM parameters to the CSI-MeasConfig, and take the option 1 as baseline for the UEIBM ASN.1 parameters structure.