3GPP TSG RAN WG1 #121	R1-2503423
Malta, MT, 19 - 23 May 2025

Agenda item: 		7
Source:	Nokia
Title:	Discussion on Reply LS on collision between SSB and RA occasion for LTM
Document for:		Discussion and Decision

Conclusion
In this contribution, we provide our views on the potential RAN1 actions based on the RAN4 reply on collision between SSB and RA occasion for LTM. The following proposals have been made:
Proposal 1: For RAN1, it should be sufficient to specify that RACH shall be prioritized over SSB if the collision occurs outside of the MG in TS 38.213.
Proposal 2: RAN1 should inform RAN2 about this reply from RAN4 for any potential RAN2 specification impact. 

3GPP TSG RAN WG1 #121			R1-2503544
St Julian’s, Malta, May 19th – 23th, 2025

Agenda item:	7
Source: 	Samsung
Title: 	Discussion on differentiation of sDCI mTRP, mDCI mTRP and sTRP
Document for:	Discussion and Decision

Conclusion
Proposal. To RAN2, RAN1 can provide the following answers.
Question 2a: RAN2 would like to ask if RAN1 has any concern on the above highlight sentence?
Answer 2a: RAN1 has a concern on the above highlight sentence, because the RRC parameter applyIndicatedTCI-State in ControlResourceSet is optionally present and may not be mandatorily configured for all ControlResourceSets in all BWPs of the serving cell operated as sDCI mTRP, hence it cannot clearly distinguish between sDCI mTRP and sTRP.
Question 2b: If there is any concern on Question 2a, what’s RAN1’s suggestion on how to separate the cells operated as sTRP and sDCI mTRP?
Answer 2b: As mentioned in Answer 2a, the RRC parameter applyIndicatedTCI-State cannot clearly distinguish between sDCI mTRP and sTRP. Instead, it is possible to use all RRC parameters for supporting sDCI mTRP (i.e., relevant RRC parameters for TCI application as well as DL/UL multi-TRP schemes). It is RAN1 consensus that RRC parameter(s) is used to indicate whether a serving cell is in sDCI mTRP operation or sTRP operation. For each serving cell list, the network ensures that either at least one of the following RRC parameters is configured for all BWPs of all serving cells (i.e., the case of single-DCI based multi-TRP) or none of the following RRC parameters is configured in any BWP of any serving cell (i.e., single-TRP).
“applyIndicatedTCI-State-r18” in ConfiguredGrantConfig, ControlResourceSet, PUSCH-Config, SRS-ResourceSet, PDCCH-ConfigCommon, PUCCH-ResourceExt-v1610, or
“applyIndicatedTCI-State-r18” and “applyIndicatedTCI-State2-r18” in CSI-AssociatedReportConfigInfo, or
“applyIndicatedTCI-StateDCI-1-0-r18” in TCI-InDCI-r18.
mappingPattern-r17”, “multipanelSchemeSDM-r18”, “multipanelSchemeSFN-r18” in PUSCH-Config
“repetitionSchemeConfig-r16” in PDSCH-Config
“searchSpaceLinkingId-r17” in searchSpace
“sfnSchemePDCCH-r17” and “sfnSchemePDSCH-r17” in MIMOParam-r17
“cjt-Scheme-PDSCH-r18” in ServingCellConfig
Two SRS resource sets configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 with higher layer parameter usage in SRS-ResourceSet set to 'codebook' or ‘noncodebook’

3GPP TSG RAN WG1 #121			R1-2503545
St Julian’s, Malta, May 19th – 23th, 2025





6.2.1.2	UE sounding procedure for DL CSI acquisition
=============================== Unchanged Text Omitted ===================================
-	For 1T=1R, 2T=2R, 4T=4R or 8T=8R, up to two SRS resource sets each with one SRS resource can be configured, where the number of SRS ports for each resource is equal to 1, 2, 4 or 8 if the UE is not indicating srs-AntennaSwitching2SP-1Periodic. Up to two SRS resource sets configured with resourceType in SRS-ResourceSet set to 'semi-persistent' and one SRS resource set configured with resourceType in SRS-ResourceSet set to 'periodic' can be configured and the two SRS resource sets configured with 'semi-persistent' are not activated at the same time, or up to two SRS resource sets can be configured, if the UE is indicating srs-AntennaSwitching2SP-1Periodic or srs-AntennaSwitching8T8R2SP-1Periodic, where each SRS resource set has one SRS resource, the number of SRS ports for each resource is equal to 1, 2, 4, or 8 or
=============================== Unchanged Text Omitted ===================================

TDoc file conclusion not found

3GPP TSG RAN WG1 #121	        		             R1-2503546
St. Julian’s, Malta, May 19th – 23rd, 2025
Agenda item:	7
Source: 	Samsung
Title: 	Discussions on collision handling between SSB and RA occasion for LTM
Document for:	Discussion and Decision

Conclusions 
In this contribution, we provide our views on potential RAN1’s specification impact(s) regarding how to handle the collision between a RACH occasion and an SSB associated with difference cells according to RAN4’s reply LS.

Proposal: adopt the following TP to clarify corresponding UE’s behaviour when a collision between an SSB and a RACH occasion associated with different cells occur outside a MG.

3GPP TSG RAN WG1 #121	 R1-2503547
Malta, MT, May 19th – 23rd, 2025
Agenda item:	7
Source:	Samsung
Title:	Discussion for HARQ-ACK aspects of Rel-17 multi-PDSCH scheduling
Document for:	Discussion and decision

Conclusions
This contribution considered the issue of counting overlapping DCIs / PDCCHs as related to HARQ-ACK information for multi-PDSCH scheduling, and made the following proposal.
Proposal: Clarify that, when a UE receives multiple DCI formats in a same PDCCH MO, and at least one of the DCI formats schedules multiple PDSCHs on a same serving cell, the UE counts (and runs the Type-2 HARQ-ACK pseudo-code for) the serving cell a same number of times as the number of DCI formats – and not the number of scheduled PDSCH receptions.
Adopt the TP proposed in draft CR [1].

References:
R1-2503980, Draft CR for HARQ-ACK aspects of Rel-17 multi-PDSCH scheduling, RAN1#121, Samsung.
R1-2310666, Correction on multiple DCIs per MO per CC for the Type-2 HARQ-ACK codebook (Rel-17), RAN1#114bis, Moderator (Samsung) and Ericsson.
R1-2310667, Correction on multiple DCIs per MO per CC for the Type-2 HARQ-ACK codebook (Rel-18), RAN1#114bis, Moderator (Samsung) and Ericsson.
R1-2310512, Summary of discussion on the correction on Type-2 HARQ-ACK codebook for receiving multiple DCIs per MO per CC, RAN1#114bis, Moderator (Samsung).

3GPP TSG RAN WG1 Meeting #121	R1-2503645
St Julian’s, Malta, May 19th – 23rd, 2025

Source:	Intel Corporation
Title:	Discussion on correction of RE mapping for UCI only PUSCH
Agenda item:	7
Document for:	Discussion

Conclusions
In this contribution, we discussed potential ambiguity on the resource mapping of PUSCH on DMRS symbols in case of UCI only without UL-SCH. The following is a summary of proposals made.
Proposal 1:
RAN1 to clarify the resource mapping of PUSCH on DMRS symbols in case of UCI only without UL-SCH. 
RAN1 to adopt the draft CR as in R1-2503644.

3GPP TSG RAN WG1 #121                                         R1-2503677 
St Julian’s, Malta, May 19th – 23rd, 2025

Source:	ZTE Corporation, Sanechips
Title:	Discussion on aperiodic CSI reporting configuration for Rel-18 LTM
Agenda Item:	7
Document for:	Discussion and Decision

Conclusion
In this contribution, we elaborate our views on handling the misalignment issue of aperiodic CSI reporting configuration for Rel-18 LTM in TS 38.331 and TS 38.214., and then proposals are provided as below:
Proposal 1: In order to align aperiodic LTM CSI reporting configuration in TS 38.214 and TS 38.331, the following update should be adopted in clause 5.2.1 of TS 38.214.
Change “Each trigger state in CSI-AperiodicTriggerStateList contains a list of associated CSI-ReportConfigs or LTM-CSI-ReportConfigs” in clause 5.2.1 of TS 38.214 to “Each trigger state in CSI-AperiodicTriggerStateList contains a list of associated CSI-ReportConfigs or one associated LTM-CSI-ReportConfig”.

3GPP TSG RAN WG1 #121                                         R1-2503679 
St Julian’s, Malta, May 19th – 23rd, 2025

Source:	ZTE Corporation, Sanechips
Title:	Discussion on collision handling of SSB and RA occasion for LTM
Agenda Item:	7
Document for:	Discussion and Decision

Conclusion
In this contribution, we share our views on spec impact of collision between SSB and RA occasion associated with different cells (including serving cell and candidate cells) for Rel-18 LTM, and then proposals are provided as below:
Proposal 1: RAN1 should capture the following method recommended by RAN4 into Clause 8.1 of TS 38.213-i60 to clarify UE behavior when the collision between a SSB and a valid RO associated with different cells happens.
If the collision is outside MG, RACH shall be prioritized over SSB.
The corresponding draft CR can be found in [2]. 

3GPP TSG RAN WG1 #121	R1-2503682                                                                         
St Julian’s, Malta, May 19th – 23rd, 2025

Source:	ZTE Corporation, Sanechips
Title:	Discussion on transmission power reduction for STxMP in TS 38.213
Agenda Item:	7
Document for:	Discussion and Decision

Conclusion
In this contribution, we elaborate our views on the transmission power reduction for STxMP and have the following observation and proposal.
Observation 1: From the perspective of specifications, RAN4 specification is to capture how to define maximum output power limitation while RAN1 specification is to capture how to specify transmission power reduction based on priority rule when it exceeds such limitation.
Proposal 1: Support to reuse the mechanism on transmission power reduction as specified in TS 38.213 for multiple panel simultaneous uplink transmission of a single carrier of a single serving cell so that the total UE transmit power for PUSCH/PUCCH does not exceed the liner value of .

3GPP TSG RAN WG1 #121	R1-2503743
St Julian's, Malta, May 19th - 23rd, 2025

Source:	Ofinno
Title:	Semi-Persistent SRS Frequency Hopping Discussion 
Agenda item:	7
Document for:	Discussion and Decision

Conclusions
In this paper we make the following observations and proposals: 
Observation 1: As the positioning SRS frequency hopping configuration is outside of the legacy BWP configuration it is not associated with any BWP ID.  
Observation 2: The SP positioning SRS MAC CE uses Cell ID, BWP ID, and SRS resource set ID to indicate to the UE which SRS resource set is impacted by the MAC CE.
Proposal 1: RAN1 to conclude that the existing MAC CE is not able to trigger SP positioning SRS frequency hopping. 
Proposal 2: RAN1 to select one of the following options for enabling SP positioning SRS frequency hopping and send an LS to RAN2 with the outcome to check the feasibility:
Option 1: Introduce a new MAC CE specifically for activating/deactivating positioning SRS frequency hopping.
Option 2: Repurpose an existing field in the current SP positioning SRS MAC CE to indicate that the MAC CE is for activation/deactivating positioning SRS frequency hopping 

3GPP TSG RAN WG1 Meeting #121                                                            R1-2503744
St Julian’s, Malta, May 19th – 23rd, 2025
Agenda item:	7
Source:	Ofinno
Title:	Discussion on suspending the RRC connection for SDT
Document for:	Discussion and decision

Conclusion
The observations captured are the following: 
Observation 1.	TS 38.213 §19 captures “UE indicated to release a dedicated RRC connection” which would refer to the case which transitions to the UE into RRC_IDLE (as per TS 38.331 §5.3.8.1). This operation in TS 38.213 §19 is not aligned to TS 38.331 and the corresponding Rel-17 SDT WID for which the RRC state of the UE is limited only to RRC_INACTIVE.
Observation 2.	TS 38.331 defines two behaviours (and terminologies): (1) to release the RRC connection when the UE in RRC_CONNECTED receives the RRCRelease message without the suspendConfig IE (which transitions the UE into RRC_IDLE), and (2) to suspend the RRC connection when the UE in RRC_CONNECTED receives the RRCRelease message with the suspendConfig IE (which transitions the UE into RRC_INACTIVE).

The proposals captured are the following: 
Proposal 1.	To correct the inconsistency in RAN1 TS 38.213 for Small Data Transmission (SDT) functionality based on the intended behaviour of the RRC connection defined by RAN2 in TS 38.331 and for this, to agree on the draftCRs R1-2503745/R1-2503746 for Rel-17 and Rel-18 (with TPs of TS 38.213 in §19 “PUSCH transmission in RRC_INACTIVE state”).

3GPP TSG RAN WG1 #121												  R1-2503919
St Julian’s, Malta, May 19th – 23rd, 2025

Agenda item:	7
Source:	NEC
Title:              	Discussion on starting slot for typeII Doppler CSI
Document for:	Discussion and Decision

Conclusion
In this contribution, we provided our views on the definition of starting slot for predicted CSI, and we propose:
Observation: For typeII Doppler CSI, it’s unclear for the slot  and the predictiondelay , there are two options for clarification:
Option 1: slot  is a downlink slot, and the predictiondelay  corresponds to downlink subcarrier spacing.
Option 2: slot  is an uplink slot, and the predictiondelay  corresponds to uplink subcarrier spacing, at least for .  
Proposal 1: UE behavior should be defined in case of reported DO value is ‘out of range’ (i.e. an infinite interval ). For example, the UE can do no pre-compensation or UE can do pre-compensation based on an exact value . 
Proposal 2: For typeII Doppler CSI, clarifying that:
The earliest of the  slot intervals starts at slot , where  corresponds to subcarrier spacing configuration for DL,
  and  and  are the subcarrier spacing configurations for DL and UL, respectively, and  and  are determined by higher-layer configured ca-SlotOffset for the cells transmitting the uplink and downlink, as defined in clause 4.5 of [4, TS 38.211],
 is the uplink slot in which the CSI is reported.
And adopt the following CR.

3GPP TSG RAN WG1 #121									R1-2503941
St Julian's, Malta, May 19th – 23rd, 2025

Agenda item:	7
Source:	NEC
Title: 	Discussion on missing parameter for Rel-18 group based beam reporting
Document for:	Discussion and Decision

Conclusion
Proposal 1: Send LS to RAN2 to ask for adding nrofReportedGroups-r18 in groupBasedBeamReporting-v1800, and clarification that groupBasedBeamReporting-v1710 and groupBasedBeamReporting-v1800 cannot be configured simultaneously.

3GPP TSG RAN WG1 #121									R1-2503942
St Julian's, Malta, May 19th – 23rd, 2025

Agenda item:	7
Source:	NEC
Title: 	Discussion on the support of group based beam reporting in Rel-17 and Rel-18
Document for:	Discussion and Decision

Conclusion
Proposal 1: Adopt the following changes and the changes in draft CR [5].
Proposal 2: Adopt the following changes and the changes in draft CR [6].

3GPP TSG RAN WG1 #121		R1-2504033
St Julian’s, Malta, May 19th – 23th, 2025



6.2.1.3	UE sounding procedure between component carriers

The following prioritization rules shall be applied in case of collision between a transmission of SRS over carrier  and transmission of a physical signal/channel over a carrier of a serving cell in set 
-	the UE shall not transmit SRS whenever SRS transmission (including any interruption due to uplink or downlink RF retuning time [11, TS 38.133] as defined by higher layer parameters switchingTimeUL and switchingTimeDL of SRS-SwitchingTimeNR) on the carrier of the serving cell  and PUSCH/PUCCH transmission carrying HARQ-ACK/positive SR/RI/CRI/SSBRI and/or PRACH on a carrier of a serving cell in set happen to overlap in the same symbol
-	the UE shall not transmit a periodic/semi-persistent SRS whenever periodic/semi-persistent SRS transmission (including any interruption due to uplink or downlink RF retuning time [11, TS 38.133] as defined by higher layer parameters switchingTimeUL and switchingTimeDL of SRS-SwitchingTimeNR) on the carrier of the serving cell  and PUSCH transmission carrying aperiodic CSI on a carrier of a serving cell in set  happen to overlap in the same symbol
-	the UE shall drop PUCCH/PUSCH transmission carrying periodic/semi-persistent CSI comprising only CQI/PMI/L1-RSRP/L1-SINR, and/or SRS transmission on a carrier of a serving cell in set  configured for PUSCH/PUCCH transmission whenever the transmission and SRS transmission (including any interruption due to uplink or downlink RF retuning time [11, TS 38.133] as defined by higher layer parameters switchingTimeUL and switchingTimeDL of SRS-SwitchingTimeNR) on the carrier of the serving cell  happen to overlap in the same symbol
-	the UE shall drop PUSCH transmission carrying aperiodic CSI comprising only CQI/PMI/L1-RSRP/L1-SINR on a carrier of a serving cell in set whenever the transmission and aperiodic SRS transmission (including any interruption due to uplink or downlink RF retuning time [11, TS 38.133]) as defined by higher layer parameters switchingTimeUL and switchingTimeDL of SRS-SwitchingTimeNR) on the carrier of the serving cell  happen to overlap in the same symbol.

 

TDoc file conclusion not found

3GPP TSG RAN WG1 #121                                                                                            R1-2504169
St Julian’s, Malta, May 19th – 23rd, 2025





6.3.1.4	Transform precoding
If transform precoding is not enabled according to 6.1.3 of [6, TS38.214],  for each layer . .
If transform precoding is enabled according to 6.1.3 of [6, TS38.214],  and  depends on the configuration of phase-tracking reference signals.
If the procedure in [6, TS 38.214] indicates that phase-tracking reference signals are not being used, the block of complex-valued symbols  for the single layer  shall be divided into  sets, each corresponding to one OFDM symbol and . 
If the procedure in [6, TS 38.214] indicates that phase-tracking reference signals are being used, the block of complex-valued symbols  shall be divided into sets, each set corresponding to one OFDM symbol, and where set  contains  symbols and is mapped to the complex-valued symbols  corresponding to OFDM symbol  prior to transform precoding, with  and . The index  of PT-RS samples in set , the number of samples per PT-RS group , and the number of PT-RS groups  are defined in clause 6.4.1.2.2.2. The quantity  when OFDM symbol  contains one or more PT-RS samples, otherwise .
Transform precoding shall be applied according to
	
resulting in a block of complex-valued symbols . The variable, where  represents the bandwidth of the PUSCH in terms of resource blocks, and shall fulfil
	
where  is a set of non-negative integers. 

TDoc file conclusion not found

3GPP TSG RAN WG1 #121			           R1-2504280
St Julian’s, Malta, May 19th – 23th, 2025
Agenda Item: 7
Source: MediaTek Inc.
Title: On DCI 1_0/0_0 monitoring with Rel-17 SSSG switching
Document for: Discussion and decision 

Conclusion
To eliminate confusion surrounding the term "is provided," we have the following proposal:

Proposal 1: RAN 1 clarifies the term “provided” in 38.213 Clause 10.1 (as shown above) means Interpretation 2:
Interpretation 1: the term “provided” means “configured within the active BWP”
Interpretation 2: the term “provided” means “configured within the active SSSG”

Figure 1. Different interpretation results in different UE behavior.

3GPP TSG RAN WG1 #121			           R1-2504281
St Julian’s, Malta, May 19th – 23th, 2025
Agenda Item: 7
Source: MediaTek Inc.
Title: On R17 SSSG reset with BWP switch triggered by RA procedure
Document for: Discussion and decision

Conclusion
We have the following proposals for R17 UE power saving with BWP switch triggered by RA procedure:

Proposal 1: RAN 1 to clarify whether UE should reset the PDCCH monitoring due to BWP switch triggered by the RA procedure according to Clause 10.4 of TS 38.213 (as copied below in Proposal 2) for R17 UE power saving.

Proposal 2: To accommodate more general BWP switch cases triggered by higher layers (including BWP switch triggered by the RA procedure), adopt the following revision in TS 38.213.

Observation 1: During the online discussion in RAN1 #120, some companies have doubts on whether initialDownlinkBWP can be configured with multiple search space set groups (SSSGs). To address this, Figure 1 shows the search space switching configurations under initialDownlinkBWP from 38.331. It can be seen that initialDownlinkBWP can be configured with multiple SSSGs.

3GPP TSG RAN WG1 #121			R1-2504295
St Julian’s, Malta, May 19th – 23th, 2025

Agenda Item:	7
Source:	Google, MediaTek Inc.
Title:	Discussion on beam determination in FR1
Document for: 	Discussion

Conclusion
According to the above discussion(s), we have the following proposal(s). 
Proposal 1: RAN1 to clarify which interpretation below is correct for beam determination for receiving PDSCH in FR1, if UE is provided dl-OrJointTCI-StateList-r17:
Interpretation 1
For receiving PDSCH in FR1, when applying beam determination procedure in TS 38.214, UE determines timeDurationForQCL in FR1 as 0;
Interpretation 2
For receiving PDSCH in FR1, when applying beam determination procedure in TS 38.214, the condition with timeDurationForQCL is not applicable to FR1,
Note: This means that UE performs beam determination procedure for FR1 by ignoring the condition with timeDurationForQCL. 
Proposal 2: Agree Text Proposal 1, if Interpretation 1 in Proposal 1 is adopted.   

Proposal 3: Agree Text Proposal 2, if Interpretation 2 in Proposal 1 is adopted.   

3GPP TSG RAN WG1 #121			R1-2504296
St Julian’s, Malta, May 19th – 23th, 2025

Agenda Item:	7
Source:	Google
Title:	Discussion on collision between SSB and RA occasion for LTM
Document for: 	Discussion

Conclusion
According to the above discussion(s), we have the following observation(s) and/or proposal(s). 
Observation 1: Collision handling of SSB and RA occasion associated with different cells should only consider whether the collision is inside measurement gap or outside measurement gap. 
Observation 2: Collision handling of SSB and RA occasion associated with different cells can apply for both intra-band and inter-band cases. 
Observation 3: Collision handling of SSB and RA occasion associated with different cells can be performed upon a SSB and a RO is overlapped in time domain. 
Proposal 1: Endorse the Text Proposal 1 in TS 38.213, according to the reply LS from RAN4 (R1-2501697).  

3GPP TSG RAN WG1 #121		R1-2504306
St Julian’s, Malta, May 19th – 23th, 2025


Source: 	Apple Inc.
Title:                     On TCI-state determination with BWP Switching operation
Agenda item:	7
Document for:	Discussion and Decision
1 

Conclusion 
In this contribution, we discussed an ambigurity relation to TCI-state determination for BWP switching operation. Based on the discussion, we present the following observations and proposals:   
Observation #1: TS 38.133 and TS 38.214 define different rules for determining the TCI-state of a target BWP after a BWP switch, before a TCI-state activation MAC-CE is received for that BWP.

Observation #2: The default QCL rule in TS 38.214 was orginally intended for the period after initial access and before TCI-state are configured by RRC and/or MAC-CE, not for handling BWP switching scenario.

Proposal #1: RAN1 to confirm that the following rule from TS 38.133 is used to determine the TCI-state for a new BWP after a BWP switch: 
‘Provided the UE does not have the required TCI-state information to receive PDCCH and PDSCH in the new BWP, the UE shall use old TCI-states before the BWP switch until a new MAC CE updating the required TCI-state information for PDCCH and PDSCH is received after the BWP switch’. 

Proposal #2: RAN1 to endorse the following CR to TS 38.214 to resolve the identified ambigurity: 

3GPP TSG RAN WG1 #121                                   R1-2504448
St Julian’s, Malta, May 19th – 23th, 2025

Source:	Sharp
Title:	Discussions on AP CSI-RS active time for CSI report configured with ‘none’
Agenda Item:	7
Document for:	Discussion and Decision

Conclusion
In this contribution, we have discussed our views on remaining issues for AP CSI-RS active time and make the following proposals:
Proposal 1: For earlier releases (Rel-15 to Rel-17), draw a conclusion that active time of aperiodic CSI-RS starts from the end of the PDCCH containing the request and ends at the end of the scheduled PUSCH containing the report associated with this aperiodic CSI-RS, if any.
Proposal 2: For Rel-18 NR, adopt the 1st change in R1-2504449.
Proposal 3: For earlier releases (Rel-15 to Rel-17), draw a conclusion that if ‘UL-SCH’ field is set to ‘0’ and the associated reportQuantity in the CSI report indicated by the ‘CSI request’ field is set to ‘none’, active time of aperiodic CSI-RS starts from the end of the PDCCH containing the request and ends at the last symbol between  symbols after the first symbol after the PDCCH and  symbols after the last symbol of the CSI-RS.
Proposal 4: For Rel-18 NR, adopt the 2nd change in R1-2504449.

TDoc file unavailable

3GPP TSG RAN WG1 #121		                                                      R1-2504550
St Julian’s, Malta, May 19th – 23rd, 2025

Source:	CATT
Title:	Discussion on aperiodic triggering offset of CSI-IM for Rel-18 type II Doppler codebook and Rel-18 type II Doppler port selection codebook
Agenda Item:	7
Document for:	Discussion and Decision

Conclusion
In this contribution, we provide our views on aperiodic triggering offset of CSI-IM for Rel-18 type II Doppler codebook. The following proposal is made:
Proposal 1: For the Rel-18 Type-II Doppler codebook and Rel-18 type II Doppler port selection codebook, the aperiodic triggering offset of the CSI-IM, if configured, follows the offset of the associated NZP CSI-RS resource with the lowest resource ID in the CSI-RS resource set for channel measurement.

3GPP TSG RAN WG1 #121		                                                      R1-2504552
St Julian’s, Malta, May 19th – 23rd, 2025

Source:	CATT
Title:	Discussion on CSI-RS resource slot offsets for the Rel-18 Type-II codebook refinement for CJT mTRP
Agenda Item:	7
Document for:	Discussion and Decision

Conclusion
In this contribution, slot offsets of CSI-RS resources for the Rel-18 Type-II codebook refinement for CJT mTRP are discussed. Based on the discussion, we have the following proposals:
Proposal 1: For the Rel-18 Type-II codebook refinement for CJT mTRP, each of the  aperiodic CSI-RS resources can be configured by a higher layer parameter (e.g., additionalOneSlotOffset) with one additional slot offset relative to the slot offset configured by the higher layer parameter aperiodicTriggeringOffset in the resource set.
Proposal 2: Send an LS to RAN2 to ask for adding a new RRC parameter in aperiodicTriggeringOffset to indicate the slot offsets for each of the  aperiodic CSI-RS resources.

3GPP TSG RAN WG1 #121		                                                      R1-2504553
St Julian’s, Malta, May 19th – 23rd, 2025

Source:	CATT
Title:	Discussion on aperiodic CSI-RS resource slot offsets for the Rel-17 CSI enhancements for NC-JT
Agenda Item:	7
Document for:	Discussion and Decision

Conclusion
In this contribution, slot offsets of aperiodic CSI-RS resources for the Rel-17 CSI enhancements for NC-JT are discussed. Based on the discussion, we have the following proposals:
Proposal 1: For the Rel-17 CSI enhancements for NC-JT, each of the aperiodic CSI-RS resources can be configured by a higher layer parameter (e.g., additionalOneSlotOffset) with one additional slot offset relative to the slot offset configured by the higher layer parameter aperiodicTriggeringOffset in the resource set.
Proposal 2: Send an LS to RAN2 to ask for adding a new RRC parameter in aperiodicTriggeringOffset  to indicate the slot offsets for each of the aperiodic CSI-RS resources.

3GPP TSG-RAN WG1 Meeting #121	R1-2504638
St Julian’s, Malta, May 19th-23rd, 2025

Agenda Item:	7
Source:	Huawei, HiSilicon
Title:	Clarification on the starting MO of PEI-O
Document for:	Discussion and Decision 

Conclusions
This contribution discusses the clarification with respect to the determination of the starting MO of PEI occasion. The following is proposed for clarification.
Proposal 1: RAN1 to clarify which alternative should be used for determination of the starting MO of PEI-O:
Alt.1: UE does not expect a configuration of firstPDCCH-MonitoringOccasionOfPEI-O indicating a MO which overlaps with uplink symbol or not aligned with the MO pattern configured by pei-SearchSpace;
Alt.2: If a configuration of firstPDCCH-MonitoringOccasionOfPEI-O indicating a MO which overlaps with uplink symbol or not aligned with the MO pattern configured by pei-SearchSpace, the first PDCCH monitoring occasion for DCI format 2_7 is the first MO configured by pei-SearchSpace which is not overlapped with uplink symbol after the symbol indicated by firstPDCCH-MonitoringOccasionOfPEI-O.

3GPP TSG-RAN WG1 Meeting #121	R1-2504641
St Julian’s, Malta, May 19th – 23rd, 2025

Agenda Item:	7
Source:	Huawei, HiSilicon
Title:	Discussion on maximum transmission power for STxMP in 38.213
Document for:  Discussion and Decision

Summary and conclusion
Proposal 1: Adopt the CR proposed in R1-2504642 to correct the description of PCMAX,f,c,k in 38.213.
Proposal 2: RAN1 sends a LS to RAN2 to inform about the issue in RAN2 specification.

3GPP TSG RAN WG1 #121	                   	      R1-2504720
St Julian’s, Malta, May 19th – 23th, 2025

Source: 	Moderator (vivo)
Title:	Summary on discussion on determination of monitoring occasion of SS#0 associated with CORESET#0 following unified TCI state
Agenda Item:	7
Document for:	Discussion and Decision

Conclusion
Based on the comments received, this CR is only for Rel-17 and no mirror CR for Rel-18 in this meeting. Rel-18 CR can be discussed in future meeting.
For Rel-17 CR, there are two possible ways to address this issue.
Alt1: TP is revised based on option1
If a UE is provided a zero value for searchSpaceID in PDCCH-ConfigCommon for a Type0/0A/1A/2-PDCCH CSS set, the UE determines monitoring occasions for PDCCH candidates of the Type0/0A/1A/2-PDCCH CSS set as described in clause 13, and the UE is provided a C-RNTI, the UE monitors PDCCH candidates only at monitoring occasions associated with a SS/PBCH block, where the SS/PBCH block is determined by the most recent of 
-	an indicated TCI-State of the active BWP that includes a CORESET with index 0 provided with followUnifiedTCI-State, as described in [6, TS 38.214], which includes a CSI-RS quasi-co-located with the SS/PBCH block if the UE is provided followUnifiedTCI-State for the CORESET with index 0; otherwise, a MAC CE activation command indicating a TCI state of the active BWP that includes a CORESET with index 0, as described in [6, TS 38.214], where the TCI-state includes a CSI-RS which is quasi-co-located with the SS/PBCH block, or 
-	a random access procedure that is not initiated by a PDCCH order that triggers a contention-free random access procedure, or
-	configured-grant based PUSCH transmission in RRC_INACTIVE state as described in clause 19.

Alt2: 
If a UE is provided a zero value for searchSpaceID in PDCCH-ConfigCommon for a Type0/0A/1A/2-PDCCH CSS set, the UE determines monitoring occasions for PDCCH candidates of the Type0/0A/1A/2-PDCCH CSS set as described in clause 13, and the UE is provided a C-RNTI, the UE monitors PDCCH candidates only at monitoring occasions associated with a SS/PBCH block, where the SS/PBCH block is determined by the most recent of 
-	a MAC CE activation command or DCI indicating a TCI state of the active BWP that includes a CORESET with index 0, as described in [6, TS 38.214], where the TCI-state includes a CSI-RS which is quasi-co-located with the SS/PBCH block, or 
-	a random access procedure that is not initiated by a PDCCH order that triggers a contention-free random access procedure, or
-	configured-grant based PUSCH transmission in RRC_INACTIVE state as described in clause 19.1

3GPP TSG RAN WG1 #121                                                                                     R1-2504735
St Julian’s, Malta, May 19th – 23rd, 2025


Source:	Moderator (CATT)
Title:	Summary on LS on differentiation of sDCI based mTRP and sTRP
Agenda Item:	5
Document for:	Decision

Summary on LS on differentiation of sDCI mTRP and sTRP	                         CATT
R1-2503344	Draft reply LS on differentiation of sDCI mTRP, mDCI mTRP and sTRP	vivo
R1-2503676	Discussion on differentiation of sDCI mTRP, mDCI mTRP and sTRP	ZTE Corporation, Sanechips
R1-2503768	Discussion on LS on differentiation of sDCI based mTRP and sTRP	CATT
R1-2503769	Draft reply LS on differentiation of sDCI based mTRP and sTRP	CATT
R1-2503871	Discussion on LS on differentiation of sDCI mTRP and sTRP	Xiaomi
R1-2504186	Discussion on LS on differentiation of sDCI mTRP, mDCI mTRP and sTRP	OPPO
R1-2504452	Discussion on LS on differentiation of sTRP and sDCI mTRP	Ericsson
R1-2503544	Discussion on differentiation of sDCI mTRP, mDCI mTRP and sTRP	Samsung

3GPP TSG RAN WG1#121		R1-2504736
St Julian’s, Malta, May 19th – 23th, 2025
Agenda item:	7
Source:	Moderator (Samsung)
Title:	Summary of discussion on the timeline issue for 8Tx PUSCH
Document for:	Discussion and Decision

Conclusion
The following is proposed based on the discussion.
Proposal: Adopt the following TP for Rel18 TS 38.214 clause 6.4. 

3GPP TSG RAN WG1 #121									R1-2504748
St Julian's, Malta, May 19th – 23rd, 2025

Agenda item:	7
Source:	Moderator (NEC)
Title:              	Summary on draft CR discussion for group based beam reporting 
Document for:	Discussion and Decision

Conclusion
According to companies’ input, the following is proposed.
Proposal 1: For the missing parameter to provide the number of reported resource groups for Rel-18 group based beam reporting, down-select one of the following direction
Direction 1a [1]: Send LS to RAN2 to ask for adding nrofReportedGroups-r18 in groupBasedBeamReporting-v1800, 
FFS: clarification that groupBasedBeamReporting-v1710 and groupBasedBeamReporting-v1800 cannot be configured simultaneously
Direction 1b [5]: Change RRC parameter “nrofReportedGroups-r18” in TS 38.214 to “nrofReportedGroups-r17”. And send LS to RAN2 to ask for clarification that groupBasedBeamReporting-v1800 must be dependent on groupBasedBeamReporting-v1710 configuration and the UE assumption when both groupBasedBeamReporting-v1710 and groupBasedBeamReporting-v1800 are configured.

Proposal 2: Further discuss whether the changes are needed for correcting the conditions for group based beam reporting.
Conditions to enable Rel-15, Rel-17 and Rel-18 group based beam reporting need to be clarified
According to TS 38.331, when groupBasedBeamReporting (without suffix) set to 'enabled', it may suggest either Rel-15 group based beam reporting or Rel-17 group based beam reporting or Rel-18 group based beam reporting. Thus, for UE to adopt Rel-15 group based beam reporting, it shall not be configured with groupBasedBeamReporting-v1710 nor groupBasedBeamReporting-v1800, meanwhile, for UE to adopt Rel-18 group based beam reporting, groupBasedBeamReporting (without suffix) shall set to 'enabled' and groupBasedBeamReporting-v1800 shall be configured.
Conditions to enable Rel-15, Rel-17 and Rel-18 group based beam reporting need to be clarified
According to TS 38.331, when groupBasedBeamReporting (without suffix) set to 'enabled', it may suggest either Rel-15 group based beam reporting or Rel-17 group based beam reporting or Rel-18 group based beam reporting. Thus, for UE to adopt Rel-15 group based beam reporting, it shall not be configured with groupBasedBeamReporting-v1710 nor groupBasedBeamReporting-v1800, meanwhile, for UE to adopt Rel-18 group based beam reporting, groupBasedBeamReporting (without suffix) shall set to 'enabled' and groupBasedBeamReporting-v1800 shall be configured.

Proposal 3: Adopt the following changes for Rel-17 group based beam reporting.

Proposal 4: Adopt the following changes for Rel-18 group based beam reporting.

3GPP TSG-RAN WG1 Meeting #121	 R1-2504759
St Julian’s, Malta, May 19th – 23rd, 2025
Agenda Item:	7
Source:	Moderator (Ericsson)
Title:	Summary of correction on PTRS to PDSCH EPRE ratio
Document for:	Discussion, Decision
1	

Conclusion
Thanks for providing input with such tight time window.
Based on the input on round1, let’s try to conclude to endorse the TP.
Endorse the TP in the tDoc R1-2503979.

3GPP TSG RAN WG1 #121									             R1-2504765
St Julian's, Malta, May 19th – 23rd, 2025

Agenda item:	7
Source:	Moderator (Huawei)
Title:              	Summary on maximum transmission power for STxMP
Document for:	Discussion and Decision

TDoc file conclusion not found

3GPP TSG RAN WG1 #121									             R1-2504766
St Julian's, Malta, May 19th – 23rd, 2025

Agenda item:	7
Source:	Moderator (Huawei)
Title:              	Summary on TCI-state update for mDCI mTRP
Document for:	Discussion and Decision

TDoc file conclusion not found

3GPP TSG RAN WG1 #121                                        R1-2504767
St Julian’s, Malta, May 19th – 23th, 2025

Source:	Moderator (ZTE)
Title:	Summary#1 on startSFN for positioning SRS FH
Agenda item:	8.1
Document for:	Discussion and Decision

Conclusion
Updated proposal 1: 
Answer for Q1: No, parameter start SFN is not needed for UTW for positioning SRS frequency hopping. 
Support: Huawei, vivo, CATT, MediaTek
Not support: Samsung, ZTE, Nokia, Ericsson

3GPP TSG RAN WG1 #121	R1-2504768
St Julian’s, Malta, May 19th – 23rd, 2025

Source:	Moderator (NTT DOCOMO, INC.)
Title:	Summary for discussion of CR on multi-channel transmission within a shared COT
Agenda Item:	7
Document for: 	Discussion and Decision

Summary of 2.2
For Case 2 in 2.1.1, the necessary update is only to add the clause index.


Proposal for Monday online
Proposed conclusion:
It is clarified that a UE cannot use a shared COT and shall initiate a COT if the UE will perform transmission on more than one channels.

Proposal:
Agree the draft CR in x4490 with removal of the addition of “(s)”.
Update the cover page based on the removal above.

3GPP TSG RAN WG1#121		R1- 2504779
St Julian’s, Malta, May 19th – 23th, 2025
Agenda item:	7
Source:	Moderator (Samsung)
Title:	Summary of discussion on HARQ-ACK aspects of Rel-17 multi-PDSCH scheduling
Document for:	Discussion and Decision

Conclusion
TBD

3GPP TSG RAN WG1 #121             	                                          R1-2504780
St Julian's, Malta, 19 - 23 May, 2025

Title 	:  Summary on the reference point for the PDSCH starting symbol determination 
Source 	:  Moderator (NEC)
Agenda item	:  7
Document for	:  Decision

Conclusion
Thank you for the inputs so far. Based on the discussion, for experts who have not been involved with the R-17 NR_FeMIMO-Core discussion, the inconsistent definition of S0 will result in ambiguity and misunderstanding, and the following proposal will be presented:
Proposal 1: Adopt the following change for Rel-17 TS 38.214 Clause 5.1.2.1 to clarify the reference point for PDSCH starting symbol determination. 

3GPP TSG RAN WG1 #121             	                                           R1-2504781
St Julian's, Malta, 19 - 23 May, 2025

Title 	:  Summary on the PDSCH mapping type B starting symbol determination in TS 38.214
Source 	:  Moderator (NEC)
Agenda item	:  7
Document for	:  Decision

Conclusion
Thank you for the inputs so far. Based on the discussion, for experts who have not been involved with the R-16 NR_L1enh_URLLC discussion, the inconsistent definition of S0 will result in ambiguity and misunderstanding, and the following proposal will be presented:
Proposal 1: Adopt the following change for Rel-16 TS 38.214 Clause 5.1.2.1 to clarify the PDSCH mapping type B starting symbol determination. 

3GPP TSG RAN WG1 #121			R1-2504783
St Julian’s, Malta, May 19th – 23th, 2025

Agenda item:	7
Source: 	Samsung
Title: 	Summary of discussion on UE capability for SRS antenna switching
Document for:	Discussion and Decision

Conclusion
It has been agreed on Monday online session (5/19) as follows:

Agreement
The TP in R1-2503545 is agreed for Rel-18 TS38.214. Final CR in R1-250XXXX.

And Final CR is agreed as R1-2504826.

3GPP TSG RAN WG1#121		 R1-2504784
St Julian’s, Malta, May 19th – 23th, 2025
Agenda item:	7
Source:	Moderator (NEC)
Title:	Summary of discussion on UE DM-RS transmission in RACH-less HO
Document for:	Discussion and Decision

Conclusion
Thank you for the inputs so far. Moderator updated the first sentence as “in NTN RACH-less handover” based on DCM's comments, and will present the following proposal based on the discussion.

Proposal 1: Adopt the following change for Rel-18 TS 38.214 Clause 6.2.2 for RACH-less HO in NTN. 

Proposal 2: Merge the CRs of RACH-less handover for NTN and RACH-less LTM cell switch into one paragraph. Adopt the following TP for Rel-18 TS 38.214 Clause 6.2.2.

3GPP TSG RAN WG1#121		R1-2504785
St Julian’s, Malta, May 19th – 23th, 2025
Agenda item:	7
Source:	Moderator (NEC)
Title:	Summary of discussion on UE DM-RS transmission in RACH-less LTM
Document for:	Discussion and Decision

Conclusion
Thank you for the inputs so far. Moderator will present the following proposal based on the discussion.

Proposal 1: Adopt the following change for Rel-18 TS 38.214 Clause 6.2.2 for RACH-less LTM. 

3GPP TSG RAN WG1#121		R1-2504786
St Julian’s, Malta, May 19th – 23th, 2025
Agenda item:	7
Source:	Moderator (NEC)
Title:	Summary of discussion on PUSCH transmission in RACH-less HO
Document for:	Discussion and Decision

Conclusion
Thank you for the inputs. 
RAN2 discussed the related issue today’s morning, and made the following agreements:

According to companies’ input and the above RAN2 agreements, the following is proposed.
Proposal 1: For RACH-less HO in TN or in mobile IAB, selection one of the options:
Option 1: Do not address any content until receiving the LS from RAN2.
Option 2: Agree to capture the RACH-less HO in TN or in mIAB directly in RAN1, and adopt the following change for Rel-18 TS 38.213 Clause 22.

3GPP TSG RAN WG1 #121	R1-2504787
St Julian's, Malta, May 19th - 23rd, 2025

Source: 	Moderator (Ofinno)
Title:	Summary on discussion on SP SRS frequency hopping support 
Agenda Item:	7
Document for:	Discussion and Decision

Conclusion
Proposals for Tuesday Morning Online discussion:

Proposal 1:
Option 1: Send an LS to RAN2 highlighting the issue of activation/deactivation of SP SRS frequency hopping and ask them to fix it if they confirm the issue. 
Option 2: Continue discussion on a particular solution and send an LS to RAN2 with an endorsed solution from RAN1 point of view. 

Proposal 2: 
Option 1: Agree that when positioning SRS FH is configured to the UE in a CC that the UE can’t be configured with other positioning SRS in that CC. 
Option 2: Conclude that when positioning SRS FH is configured to the UE in a CC that the UE can be configured with other positioning SRS in that CC. 

Potential solutions discussed in RAN1: 
Option 1: Introduce a new MAC CE specifically for activating/deactivating positioning SRS frequency hopping.
Supported by: Ofinno 
Option 2: Repurpose an existing field in the current SP positioning SRS MAC CE to indicate that the MAC CE is for activation/deactivating positioning SRS frequency hopping 
Supported by: vivo, Nokia, Ofinno 
Option 3: When the UE is configured with positioning SRS frequency hopping the UE ignores the BWP ID field in the MAC CE. 
Note: this implies that for a CC, the UE can’t be configured with other positioning SRS (e.g., in a “regular” BWP) in the CC when it is configured with positioning SRS frequency hopping in the CC. 
Supported by: QC, vivo, ZTE 

3GPP TSG RAN WG1 #121	R1-2504788
St Julian's, Malta, May 19th - 23rd, 2025

Source: 	Moderator (Ofinno)
Title:	Summary on discussion on PL RS fallback for positioning SRS 
Agenda Item:	7
Document for:	Discussion and Decision

Conclusion
So far it seems that a few companies agree there could be some clarification of the existing behaviour while others don’t see the need for further changes. 

3GPP TSG RAN WG1 Meeting #121	R1-2504789
St Julian’s, Malta, May 19th – 23rd, 2025

Source:	Moderator (ZTE)
Title:	Summary of discussion on transmission power reduction for STxMP in TS 38.213
Agenda Item:	7
Document for:	Discussion and Decision

Conclusion
Conc1usion:
It is RAN1 understanding that there is no need to specify prioritizations for transmission power reductions for operations with STxMP PUSCH/PUCCH transmission with the same priority.
Proposal:
Support the following draft CR for TS 38.213 to specify prioritizations for transmission power reductions for operation with multi-DCI based STxMP PUSCH+PUSCH transmissions with different priorities.

3GPP TSG RAN WG1 Meeting #121	R1-2504790
St Julian’s, Malta, May 19th – 23rd, 2025

Source:	Moderator (ZTE)
Title:	Summary of discussion on SRS frequency hopping with repetition for STxMP in TS 38.213
Agenda Item:	7
Document for:	Discussion and Decision

Conclusion
[TBD]

3GPP TSG RAN WG1 #121												  R1-2504792
St Julian's, Malta, May 19th – 23rd, 2025

Agenda item:	7
Source:	Moderator (NEC)
Title:              	Summary on starting slot for typeII Doppler CSI 
Document for:	Discussion and Decision

Conclusion
Thank you very much for sharing the views and being flexible. According to companies’ input, it is proposed to adopt the TP with update from Ericsson.

3GPP TSG RAN WG1 #121												  R1-2504793
St Julian's, Malta, May 19th – 23rd, 2025

Agenda item:	7
Source:	Moderator (NEC)
Title:              	Summary on SRS hopping for positioning in TS 38.211
Document for:	Discussion and Decision

Conclusion
Thank you for sharing the views. According to companies’ input, it is proposed to 
Adopt the first change “” and third change “”, 
For the second change (highlighted in yellow), with the change, the spec can be complete and more clear. We can also further check other companies’ view online whether this is needed
Based on this, following TP for Rel-18 TS 38.211 is proposed:

3GPP TSG RAN WG1 #121									R1-2504795
St Julian's, Malta, May 19th – 23rd, 2025

Agenda item:	7
Source:	Moderator (NEC)
Title:              	Summary#2 on draft CR discussion for group based beam reporting 
Document for:	Discussion and Decision

Conclusion
Rel-18 TP 
Proposal 1: Adopt the following changes for Rel-18 group based beam reporting. 
5.2.1.4.2	Report quantity configurations

If the UE is configured with a CSI-ReportConfig with the higher layer parameter reportQuantity set to 'cri-RSRP', 'ssb-Index-RSRP', 'cri-RSRP- Index' or 'ssb-Index-RSRP- Index',
-	if the UE is configured with the higher layer parameter groupBasedBeamReporting set to 'disabled', the UE is not required to update measurements for more than 64 CSI-RS and/or SSB resources, and the UE shall report in a single report nrofReportedRS (higher layer configured) different CRI or SSBRI for each report setting. 
-	if the UE is configured with the higher layer parameter groupBasedBeamReporting set to 'enabled', the UE is not required to update measurements for more than 64 CSI-RS and/or SSB resources, and the UE shall report in a single reporting instance two different CRI or SSBRI for each report setting, where CSI-RS and/or SSB resources can be received simultaneously by the UE either with a single spatial domain receive filter, or with multiple simultaneous spatial domain receive filters. 
-	if the UE is configured with the higher layer parameter groupBasedBeamReporting-, the UE is not required to update measurements for more than 64 CSI-RS and/or SSB resources, and the UE shall report in a single reporting instance nrofReportedGroups, group(s) of two CRIs or SSBRIs selecting one CSI-RS or SSB from each of the two CSI Resource Sets for the report setting, where CSI-RS and/or SSB resources of each group can be received simultaneously by the UE.
-	if the UE is configured with the higher layer parameter groupBasedBeamReporting- set to JointULDL, the UE is not required to update measurements for more than 64 CSI-RS and/or SSB resources, and the UE shall report in a single reporting instance , group(s) of two CRIs or SSBRIs selecting one CSI-RS or SSB from each of the two CSI Resource Sets for the report setting, where CSI-RS and/or SSB resources of each group can be received simultaneously and applied for simultaneous  transmission with spatial filters by the UE subject to UE capability.
- 	if the UE is configured with the higher layer parameter groupBasedBeamReporting- set to Only, the UE is not required to update measurements for more than 64 CSI-RS and/or SSB resources, and the UE shall report in a single reporting instance , group(s) of two CRIs or SSBRIs selecting one CSI-RS or SSB from each of the two CSI Resource Sets for the report setting, where CSI-RS and/or SSB resources of each group can be applied for simultaneous  transmission with spatial filters by the UE subject to UE capability.

5.2.1.2	Resource settings

The time domain behavior of the CSI-RS resources within a CSI Resource Setting are indicated by the higher layer parameter resourceType and can be set to aperiodic, periodic, or semi-persistent. For periodic and semi-persistent CSI Resource Settings, when the UE is configured with groupBasedBeamReporting-or groupBasedBeamReporting-, the number of CSI Resource Sets configured is S=2, otherwise the number of CSI-RS Resource Sets configured is limited to S=1, except for periodic CSI Resource Settings, when the UE is configured with TDCP reporting, for which the number of CSI-RS Resource Sets in the CSI Resource Setting for channel measurement is  and all the CSI-RS Resource Sets are configured with the higher layer parameter trs-Info. For periodic and semi-persistent CSI Resource Settings, the configured periodicity and slot offset is given in the numerology of its associated DL BWP, as given by BWP-id. When a UE is configured with multiple CSI-ResourceConfigs consisting the same NZP CSI-RS resource ID, the same time domain behavior shall be configured for the CSI-ResourceConfigs. When a UE is configured with multiple CSI-ResourceConfigs consisting the same CSI-IM resource ID, the same time-domain behavior shall be configured for the CSI-ResourceConfigs. All CSI Resource Settings linked to a CSI Report Setting shall have the same time domain behavior.


5.2.1.4.1	Resource Setting configuration

For aperiodic CSI, each trigger state configured using the higher layer parameter CSI-AperiodicTriggerState is associated with one or multiple CSI-ReportConfig where the CSI-ReportConfig not configured with groupBasedBeamReporting-or groupBasedBeamReporting- is linked to periodic, or semi-persistent, or aperiodic resource setting(s): 
-	When one Resource Setting is configured, the Resource Setting (given by higher layer parameter resourcesForChannelMeasurement) is for channel measurement for L1-RSRP or for channel and interference measurement for L1-SINR computation.
-	When two Resource Settings are configured, the first one Resource Setting (given by higher layer parameter resourcesForChannelMeasurement) is for channel measurement and the second one (given by either higher layer parameter csi-IM-ResourcesForInterference or higher layer parameter nzp-CSI-RS-ResourcesForInterference) is for interference measurement performed on CSI-IM or on NZP CSI-RS.
-	When three Resource Settings are configured, the first Resource Setting (higher layer parameter resourcesForChannelMeasurement) is for channel measurement, the second one (given by higher layer parameter csi-IM-ResourcesForInterference) is for CSI-IM based interference measurement and the third one (given by higher layer parameter nzp-CSI-RS-ResourcesForInterference) is for NZP CSI-RS based interference measurement.
For aperiodic CSI, and for periodic and semi-persistent CSI resource settings, each trigger state configured using the higher layer parameter CSI-AperiodicTriggerState is associated with one or multiple CSI-ReportConfig where the CSI-ReportConfig configured with groupBasedBeamReporting-or groupBasedBeamReporting- is linked to periodic or semi-persistent, setting(s): 
-	When one Resource Setting is configured, the Resource setting is given by resourcesForChannelMeasurement for L1-RSRP measurement. In such a case, the number of configured CSI Resource Sets in the Resource Setting is S=2
For aperiodic CSI, and for aperiodic CSI resource settings, each trigger state configured using the higher layer parameter CSI-AperiodicTriggerState is associated with one or multiple CSI-ReportConfig where the CSI-ReportConfig configured with groupBasedBeamReporting-or groupBasedBeamReporting-is associated with resourcesForChannel and resourcesForChannel2, which correspond to first and second resource sets, respectively, for L1-RSRP measurement.

5.2.1.4.3	L1-RSRP Reporting

For L1-RSRP reporting, if the higher layer parameter nrofReportedRS in CSI-ReportConfig is configured to be one, or if the higher layer parameters nrOfReportedCells and nrOfReportedRS-PerCell are both configured to be one, the reported L1-RSRP value is defined by a 7-bit value in the range [-140, -44] dBm with 1dB step size, if the higher layer parameter nrofReportedRS is configured to be larger than one, or if the higher layer parameter groupBasedBeamReporting is configured as 'enabled', or if the higher layer parameter groupBasedBeamReporting-is configured, or if the higher layer parameter groupBasedBeamReporting-is configured, or if any of the higher layer parameters nrOfReportedCells and nrOfReportedRS-PerCell is configured to be larger than one, the UE shall use differential L1-RSRP based reporting, where the largest measured value of L1-RSRP is quantized to a 7-bit value in the range [-140, -44] dBm with 1dB step size, and the differential L1-RSRP is quantized to a 4-bit value. The differential L1-RSRP value is computed with 2 dB step size with a reference to the largest measured L1-RSRP value which is part of the same L1-RSRP reporting instance. The mapping between the reported L1-RSRP value and the measured quantity is described in [11, TS 38.133]. 
When the higher layer parameter groupBasedBeamReporting-or the higher layer parameter groupBasedBeamReporting- in CSI-ReportConfig is configured, the UE shall indicate the CSI Resource Set associated with the largest measured value of L1-RSRP, and for each group, CRI or SSBRI of the indicated CSI Resource Set is present first.



Rel-17 TP
Proposal 2: Adopt the following changes for Rel-17 group based beam reporting. 
5.2.1.4.2	Report Quantity Configurations

If the UE is configured with a CSI-ReportConfig with the higher layer parameter reportQuantity set to 'cri-RSRP', 'ssb-Index-RSRP', 'cri-RSRP- Index' or 'ssb-Index-RSRP- Index',
-	if the UE is configured with the higher layer parameter groupBasedBeamReporting set to 'disabled', the UE is not required to update measurements for more than 64 CSI-RS and/or SSB resources, and the UE shall report in a single report nrofReportedRS (higher layer configured) different CRI or SSBRI for each report setting. 
-	if the UE is configured with the higher layer parameter groupBasedBeamReporting set to 'enabled', the UE is not required to update measurements for more than 64 CSI-RS and/or SSB resources, and the UE shall report in a single reporting instance two different CRI or SSBRI for each report setting, where CSI-RS and/or SSB resources can be received simultaneously by the UE either with a single spatial domain receive filter, or with multiple simultaneous spatial domain receive filters. 
-	if the UE is configured with the higher layer parameter groupBasedBeamReporting-, the UE is not required to update measurements for more than 64 CSI-RS and/or SSB resources, and the UE shall report in a single reporting instance nrofReportedGroupsgroup(s) of two CRIs or SSBRIs selecting one CSI-RS or SSB from each of the two CSI Resource Sets for the report setting, where CSI-RS and/or SSB resources of each group can be received simultaneously by the UE.


5.2.1.2	Resource settings

The time domain behavior of the CSI-RS resources within a CSI Resource Setting are indicated by the higher layer parameter resourceType and can be set to aperiodic, periodic, or semi-persistent. For periodic and semi-persistent CSI Resource Settings, when the UE is configured with groupBasedBeamReporting-, the number of CSI Resource Sets configured is S=2, otherwise the number of CSI-RS Resource Sets configured is limited to S=1. For periodic and semi-persistent CSI Resource Settings, the configured periodicity and slot offset is given in the numerology of its associated DL BWP, as given by BWP-id. When a UE is configured with multiple CSI-ResourceConfigs consisting the same NZP CSI-RS resource ID, the same time domain behavior shall be configured for the CSI-ResourceConfigs. When a UE is configured with multiple CSI-ResourceConfigs consisting the same CSI-IM resource ID, the same time-domain behavior shall be configured for the CSI-ResourceConfigs. All CSI Resource Settings linked to a CSI Report Setting shall have the same time domain behavior.



5.2.1.4.1	Resource Setting configuration

For aperiodic CSI, each trigger state configured using the higher layer parameter CSI-AperiodicTriggerState is associated with one or multiple CSI-ReportConfig where the CSI-ReportConfig not configured with groupBasedBeamReporting- is linked to periodic, or semi-persistent, or aperiodic resource setting(s): 
-	When one Resource Setting is configured, the Resource Setting (given by higher layer parameter resourcesForChannelMeasurement) is for channel measurement for L1-RSRP or for channel and interference measurement for L1-SINR computation.
-	When two Resource Settings are configured, the first one Resource Setting (given by higher layer parameter resourcesForChannelMeasurement) is for channel measurement and the second one (given by either higher layer parameter csi-IM-ResourcesForInterference or higher layer parameter nzp-CSI-RS-ResourcesForInterference) is for interference measurement performed on CSI-IM or on NZP CSI-RS.
-	When three Resource Settings are configured, the first Resource Setting (higher layer parameter resourcesForChannelMeasurement) is for channel measurement, the second one (given by higher layer parameter csi-IM-ResourcesForInterference) is for CSI-IM based interference measurement and the third one (given by higher layer parameter nzp-CSI-RS-ResourcesForInterference) is for NZP CSI-RS based interference measurement.
For aperiodic CSI, and for periodic and semi-persistent CSI resource settings, each trigger state configured using the higher layer parameter CSI-AperiodicTriggerState is associated with one or multiple CSI-ReportConfig where the CSI-ReportConfig configured with groupBasedBeamReporting- is linked to periodic or semi-persistent, setting(s): 
-	When one Resource Setting is configured, the Resource setting is given by resourcesForChannelMeasurement for L1-RSRP measurement. In such a case, the number of configured CSI Resource Sets in the Resource Setting is S=2
For aperiodic CSI, and for aperiodic CSI resource settings, each trigger state configured using the higher layer parameter CSI-AperiodicTriggerState is associated with one or multiple CSI-ReportConfig where the CSI-ReportConfig configured with groupBasedBeamReporting- is associated with resourcesForChannel and resourcesForChannel2, which correspond to first and second resource sets, respectively, for L1-RSRP measurement.
For semi-persistent or periodic CSI, each CSI-ReportConfig is linked to periodic or semi-persistent Resource Setting(s):
-	When one Resource Setting (given by higher layer parameter resourcesForChannelMeasurement) is configured, the Resource Setting is for channel measurement for L1-RSRP or for channel and interference measurement for L1-SINR computation.
-	When two Resource Settings are configured, the first Resource Setting (given by higher layer parameter resourcesForChannelMeasurement) is for channel measurement and the second Resource Setting (given by higher layer parameter csi-IM-ResourcesForInterference) is used for interference measurement performed on CSI-IM. For L1-SINR computation, the second Resource Setting (given by higher layer parameter csi-IM-ResourcesForInterference or higher layer parameter nzp-CSI-RS-ResourceForInterference) is used for interference measurement performed on CSI-IM or on NZP CSI-RS.


5.2.1.4.3	L1-RSRP Reporting

For L1-RSRP reporting, if the higher layer parameter nrofReportedRS in CSI-ReportConfig is configured to be one, the reported L1-RSRP value is defined by a 7-bit value in the range [-140, -44] dBm with 1dB step size, if the higher layer parameter nrofReportedRS is configured to be larger than one, or if the higher layer parameter groupBasedBeamReporting is configured as 'enabled', or if the higher layer parameter groupBasedBeamReporting-is configured, the UE shall use differential L1-RSRP based reporting, where the largest measured value of L1-RSRP is quantized to a 7-bit value in the range [-140, -44] dBm with 1dB step size, and the differential L1-RSRP is quantized to a 4-bit value. The differential L1-RSRP value is computed with 2 dB step size with a reference to the largest measured L1-RSRP value which is part of the same L1-RSRP reporting instance. The mapping between the reported L1-RSRP value and the measured quantity is described in [11, TS 38.133]. 
When the higher layer parameter groupBasedBeamReporting-in CSI-ReportConfig is configured, the UE shall indicate the CSI Resource Set associated with the largest measured value of L1-RSRP, and for each group, CRI or SSBRI of the indicated CSI Resource Set is present first.

3GPP TSG RAN WG1 #121                                             R1-2504796 
St Julian’s, Malta, May 19th – 23rd, 2025

Source:	Moderator (ZTE)
Title:	Summary on aperiodic CSI reporting configuration for Rel-18 LTM in TS 38.214
Agenda Item:	7
Document for:	Discussion and Decision

Summary #1 of discussion
Thanks to companies for the inputs. 
Based on the feedback received from Nokia by in the moderator summary and companies (NTT DOCOMO, Fujitsu, Google, vivo, Huawei) offline discussion in RAN1#120 meeting, we can see that majority of companies agree to change TS 38.214 to resolve inconsistency issue on aperiodic LTM CSI reporting configuration, specific spec changes are as follows:
Change “Each trigger state in CSI-AperiodicTriggerStateList contains a list of associated CSI-ReportConfigs or LTM-CSI-ReportConfigs” in clause 5.2.1 of TS 38.214 to “Each trigger state in CSI-AperiodicTriggerStateList contains a list of associated CSI-ReportConfigs or one associated LTM-CSI-ReportConfig”.

Moderator proposal for online session (Tuesday)
Given the above situation, Moderator recommends the following proposal:
Proposal 1: In order to align aperiodic LTM CSI reporting configuration in TS 38.214 and TS 38.331, the following update is adopted in clause 5.2.1 of TS 38.214.
Change “Each trigger state in CSI-AperiodicTriggerStateList contains a list of associated CSI-ReportConfigs or LTM-CSI-ReportConfigs” in clause 5.2.1 of TS 38.214 to “Each trigger state in CSI-AperiodicTriggerStateList contains a list of associated CSI-ReportConfigs or one associated LTM-CSI-ReportConfig”.
Note: Corresponding draft CR is provided in Appendix.

3GPP TSG RAN WG1 #121	R1-250xxxx
St Julian’s, Malta, May 19th – 23rd, 2025
Agenda Item:	7
Source:	Moderator (MediaTek)
Title:	Summary #1 on collision handling between SSB and RA occasion
Document for:	Discussion
1	

Conclusion
TBD

3GPP TSG RAN WG1 Meeting #121                                                            R1-2504800
St Julian’s, Malta, May 19th – 23rd, 2025
Agenda item:	7
Source:	Moderator (Ofinno)
Title:	Summary of discussion on suspending the RRC connection for SDT
Document for:	Discussion and decision

Conclusion
Some companies believe that the clarification is needed in TS 38.213. On the other hand, some companies believe that there is no ambiguity and clarification is not essential. 

3GPP TSG RAN WG1 #121			R1-250xxxx
St Julian’s, Malta, May 19th – 23rd, 2025

Source:	Moderator (ZTE)
Title:	FL summary of transform precoding for a PUSCH with PTRS
Agenda item:	7
Document for:	Discussion and Decision

Conclusion

Proposal:
The following TP is agreed for TS 38.211.

3GPP TSG RAN WG1 #121                                                                                      R1-2504809
St Julian’s, Malta, May 19th – 23rd, 2025


Source:	Moderator (CATT)
Title:	Summary discussion on aperiodic CSI-RS resource slot offsets for the Rel-17 NCJT
Agenda Item:	7
Document for:	Decision/Discussion

Conclusion
For Rel-17 NCJT, aperiodic CSI-RS resources in a Resource Pair can only be configured within the same slot.

3GPP TSG RAN WG1 #121 	R1-2504810
St Julian’s, Malta, May 19 – 23, 2025

Agenda item:	7
Source: 	Moderator (Qualcomm) 
Title: 	Summary on discussion on aperiodic triggering offset of CSI-IM for Rel-18 Type-II Doppler codebook
Document for:	Discussion/Decision

Conclusion
Based on the feedback, companies’ views are summarized as following:
Essentially, all companies agree that aperiodic CSI-IM should be located at the earliest slot comprising aperiodic CMR, and different views are mainly about wording/English:
8 companies are OK to take the wording of CR2 (proposed in [3]);
1 company suggested refined wording;
1 company thinks that existing text in 214 has no ambiguity, thus CR is not needed.
Therefore, we have two possible ways to move forward:
Possible conclusion1: Take the following TP:

Possible conclusion2: RAN1 conclude that for Rel-18 Type-II Doppler and Type-II Doppler Port Selection codebook, aperiodic CSI-IM, if configured, follows the triggering offset of the associated NZP CSI-RS resource with the lowest resource ID for channel measurement.
CR is not needed.

Some online discussion would be beneficial.

3GPP TSG RAN WG1 #121                                         	R1-2504811
St Julian’s, Malta, May 19 – 23, 2025





< Start of change request >
5.2.1.5	Triggering/activation of CSI Reports and CSI-RS
5.2.1.5.1	Aperiodic CSI Reporting/Aperiodic CSI-RS when the triggering PDCCH and the CSI-RS have the same numerology
    
When aperiodic CSI-RS is used with aperiodic reporting, the CSI-RS offset is configured per resource set by the higher layer parameter aperiodicTriggeringOffset or aperiodicTriggeringOffset-r16 or aperiodicTriggeringOffset-r17. The CSI-RS triggering offset has the values of {0, 1, 2, 3, 4, 5, 6, …, 15, 16, 24} slots for  or {0, 4, 8, 12, …, 60, 64, 96} slots for  and , where  is the subcarrier spacing configurations for CSI-RS. If the UE is not configured with minimumSchedulingOffsetK0 for any DL BWP and minimumSchedulingOffsetK2 for any UL BWP and if all the associated trigger states do not have the higher layer parameter qcl-Type set to 'typeD' in the corresponding TCI states, the CSI-RS triggering offset is fixed to zero. The aperiodic triggering offset of the CSI-IM follows offset of the associated NZP CSI-RS for channel measurement. The aperiodic CSI-RS is transmitted in a slot , , if UE is configured with ca-SlotOffset for at least one of the triggered and triggering cell, and in slot , otherwise, and where

TDoc file conclusion not found

3GPP TSG-RAN WG1 Meeting #121	R1-2504812
St Julian’s, Malta, May 19th – 23th, 2025

Agenda item:	7
Source:	Moderator (NEC)
Title:              	Summary of draft CR discussion on suspending of power ramping counter for preamble repetition 
Document for:	Discussion and Decision

Conclusion
Given the lack of concerns raised in the email discussion, we have the following proposal.
Proposal: Draft CR in R1-250394 is endorsed.

3GPP TSG RAN WG1 #121                                   R1-2504815
St Julian’s, Malta, May 19th – 23th, 2025

Source:	Moderator (Sharp)
Title:	Summary of AP CSI-RS active time for CSI report configured with ‘none’
Agenda Item:	7
Document for:	Discussion and Decision

Conclusion
According to Apple’s comments, CSI-RS resources associated with CSI reports for Beam management related are considered active resource in the slot in which the RS is transmitted, as shown in the following.
While according to current 38.214, e.g. for CSI report configured with ‘cri-RSRP’, if the associated CSI-RS resources are periodic, then they are considered to be active upon configuration and end at RRC release. Obviously, they are contrary with each other. Therefore, we believe a conclusion is needed for the proper reference in specs for active CSI-RS resources counting.
Proposal 1(updated_v2): make a conclusion that active resource counting for CSI-RS resources associated with CSI reports with reportQuantity set to 'ssb-Index-RSRP', 'cri-RSRP' or with reportQuantity set to 'none' and CSI-RS-ResourceSet with trs-Info is not configured is specified in TS38.306.

3GPP TSG RAN WG1 #121	R1-2504816
St Julian’s, Malta, May 19th – 23rd, 2025

Source:	Moderator (NTT DOCOMO, INC.)
Title:	Summary#2 for discussion of CR on multi-channel transmission within a shared COT
Agenda Item:	7
Document for: 	Discussion and Decision

Conclusion
Agreement
The draft CR in R1-2504490 with removal of the addition of “(s)” is endorsed in principle.
Update the cover page based on the removal above.
The draft CR in R1-2504817 is endorsed.
Final CR and R1-2504818.

3GPP TSG RAN WG1 #121                                        R1-2504823
St Julian’s, Malta, May 19th – 23th, 2025

Source:	Moderator (ZTE)
Title:	Summary#1 on startSFN for positioning SRS FH
Agenda item:	8.1
Document for:	Discussion and Decision

Conclusion
Proposed draft reply LS:

3GPP TSG RAN WG1 #121                                                                                     R1-2504824
St Julian’s, Malta, May 19th – 23rd, 2025


Source:	Moderator (CATT)
Title:	Summary#2 on LS on differentiation of sDCI based mTRP and sTRP
Agenda Item:	5
Document for:	Decision

Conclusion
RAN1 has no consensus on the down-selection between the alternatives of the below agreement:

3GPP TSG RAN WG1 #121			R1- 2504829
St Julian’s, Malta, May 19th – 23th, 2025

Agenda Item:	7
Source:	Moderator (Google)
Title:	Summary on beam determination in FR1
Document for: 	Discussion and decision

Conclusion: For Text Proposal 1, if timeDurationForQCL is not applicable, UE ignores the condition with timeDurationForQCL. 

3GPP TSG RAN WG1 #121		R1-2504853
St Julian’s, Malta, May 19th – 23th, 2025


Source: 	Moderator (Apple)
Title:                     FL summary of discussion on TCI-state determination with BWP Switching operation
Agenda item:	7
Document for:	Discussion and Decision
1 

Proposal 
Proposal: Capture the following sentence in RAN1 chairman notes as conclusion to clarify the potential ambigurity: 
It is common undestanding that the ‘before reception of the activation command, …’ in the following paragraph of section 5.1.5 in TS 38.214 refers to ‘the activation command for any BWP’. 
If tci-PresentInDCI is set to "enabled" for the CORESET scheduling the PDSCH, and the time offset between the reception of the DL DCI and the corresponding PDSCH is equal to or greater than timeDurationForQCL if applicable, after a UE receives an initial higher layer configuration of TCI states and before reception of  the activation command, the UE may assume that the DM-RS ports of PDSCH of a serving cell are quasi co-located with the SS/PBCH block determined in the initial access procedure with respect to 'QCL-TypeA', and when applicable, also with respect to'QCL-TypeD'.
No CR is needed. 

3GPP TSG RAN WG1 #121                                                                                      R1-2504865
St Julian’s, Malta, May 19th – 23rd, 2025


Source:	Moderator (CATT)
Title:	Summary#2 discussion on aperiodic CSI-RS resource slot offsets for the Rel-17 NCJT and Rel-18 CJT
Agenda Item:	7
Document for:	Decision/Discussion

Conclusion
For Rel-17 NCJT, aperiodic CSI-RS resources in a Resource Pair can only be configured within the same slot.
For Rel-18 CJT, aperiodic CSI-RS resources in a resource set can only be configured within the same slot.

3GPP TSG RAN WG1 #121                                                                                     R1-2504876
St Julian’s, Malta, May 19th – 23rd, 2025


Source:	Moderator (CATT)
Title:	Summary#3 on LS on differentiation of sDCI based mTRP and sTRP
Agenda Item:	7
Document for:	Discussion

Conclusion
RAN1 has no consensus on the down-selection between the alternatives of the below agreement:

Actions
To RAN2
ACTION: 	RAN1 respectfully asks RAN2 to take the information into consideration.

From moderator’s assessment, although a few companies argue that we do not have to send an LS to RAN2 regarding the LS, the other few companies believe we should reply to the answers raised by RAN2. As the moderator, I tend to agree that we should send the reply to RAN2 as they have made changes on the spec and seek the advice from RAN1. We should reply to the questions 2A and 2B raised from RAN2. And of course, please provide your views on whether/how we capture the conclusion in the reply LS.
Q1: Do you agree to have a reply LS? If yes, do you agree with the draft reply LS?

Proposal for online discussion
Since I did not receive any negative comments on sending the reply LS to RAN2, I suggest that we provide such a LS.
Proposal 1: Provide the reply LS to RAN2 for the discussion regarding the differentiation of sDCI based mTRP and sTRP. Final LS is in R1-2504885.

3GPP TSG-RAN WG1 Meeting #121	R1-2504878
St Julian’s, Malta, May 19th – 23th, 2025

Agenda item:	7
Source:	Moderator (NEC)
Title:              	Summary#2 of draft CR discussion on suspending of power ramping counter for preamble repetition 
Document for:	Discussion and Decision

Conclusion
There is no comment on the revision of draft CR, so we proposal to endorse the draft CR in R1-2504877.

3GPP TSG RAN WG1 #121			R1-2504902
St Julian’s, Malta, May 19th – 23th, 2025

Agenda Item:	7
Source:	Ad-Hoc Chair (Huawei)
Title:	Session notes for Pre-Rel-19 NR Maintenance (adhoc2)
Document for:	Discussion, Decision

Pre-Rel-19 NR Maintenance
Only essential corrections – a rejected draft CR will be marked in red
Please provide information on relevant release and work item when requesting contribution numbers.
For maintenance on RAN1 specifications, individual draft CRs are to be submitted. Final endorsed CR will be sourced by “Moderator (company name)” and other co-sourcing companies (if any).

[121-NR-Maintenance] To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc – Chair

The discussion on following tdocs for maintenance on NTN, Positioning, IAB, Sidelink, 71GHz, URLLC, SDT, Others will be chaired by David
NTN, Positioning, IAB, Sidelink, 71GHz, URLLC, SDT, Others
Release 18 NR-NTN
R1-2503934	Draft CR for TS 38.214 on UE DM-RS transmission procedure in RACH-less handover	NEC
R1-2504784	Summary of UE DM-RS transmission in RACH-less HO	Moderator (NEC)

R1-2503935	Draft CR for TS 38.214 on UE DM-RS transmission procedure in RACH-less LTM	NEC
R1-2504785	Summary of UE DM-RS transmission in RACH-less LTM	Moderator (NEC)
Moderated by Yingchao MAO (NEC)


Proposal
The TP below is endorsed:

6.2.2	UE DM-RS transmission procedure
*** Unchanged parts are omitted ***
When transmitted PUSCH is scheduled by DCI format 0_1 with CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI or MCS-C-RNTI, or corresponding to a configured grant, or being a PUSCH for Type-2 random access procedure,
-	for a configured-grant based PUSCH transmission in RRC_INACTIVE state, the UE is provided with a set of DM-RS port(s) by sdt-DMRS-Ports. The DM-RS port for the PUSCH is determined by the mapping between SS/PBCH block(s) and a PUSCH occasion and the associated DM-RS resource as described in Clause 19.1 of [6, TS 38.213]. 

-	the UE may be configured with higher layer parameter dmrs-Type in DMRS-UplinkConfig, and the configured DM-RS configuration type is used for transmitting PUSCH in as defined in Clause 6.4.1.1 of [4, TS 38.211]. 
*** Unchanged parts are omitted ***




Release 18 IAB
R1-2503933	Draft CR for TS 38.213 on PUSCH transmission in RACH-less handover	NEC
R1-2504786	Summary of PUSCH transmission in RACH-less HO	Moderator (NEC)
Moderated by Yingchao MAO (NEC)

Agreement
For RACH-less HO in TN or in mobile IAB, RAN1 will wait for RAN2 confirmation of their agreement before agreeing a corresponding CR for RAN1 specifications.


Release 18 Sidelink
R1-2504490	Draft CR on multi-channel transmission within a shared COT	NTT DOCOMO, INC.
R1-2504768	Summary for discussion of CR on multi-channel transmission within a shared COT	Moderator (NTT DOCOMO, INC.)
Moderated by Shohei (NTT DOCOMO)
R1-2504817	Draft CR on transmission within a shared COT with multiple channels	Moderator (NTT DOCOMO, INC.)

Agreement
The draft CR in R1-2504490 with removal of the addition of “(s)” is endorsed in principle.
Update the cover page based on the removal above.
The draft CR in R1-2504817 is endorsed.
Final CR and R1-2504818.


Release 17 NR extension to 71GHz
R1-2503547	Discussion on HARQ-ACK aspects of Rel-17 multi-PDSCH scheduling	Samsung
R1-2503980	Draft CR for HARQ-ACK aspects of Rel-17 multi-PDSCH scheduling	Samsung
R1-2504779	Summary of discussion on HARQ-ACK aspects of Rel-17 multi-PDSCH scheduling	Moderator (Samsung)
Moderated by Kyungjun (Samsung)

Agreement
The TP below is endorsed for Rel-17:
-	if the UE indicates type2-HARQ-ACK-Codebook and receives a number  of PDSCHs on a serving cell c that are scheduled by DCI formatsin PDCCH receptions at a same PDCCH monitoring occasion m, the serving cell c is counted  times for PDCCH monitoring occasion m in increasing order of the PDSCH reception starting time 

R1-2504819	Draft CR for HARQ-ACK aspects of Rel-17 multi-PDSCH scheduling	Moderator (Samsung)
R1-2504820	Draft CR for HARQ-ACK aspects of Rel-17 multi-PDSCH scheduling	Moderator (Samsung)

Agreement
The draft in R1-2504819 is endorsed for Rel-17, and the draft CR in R1-2504820 is endorsed as Rel-18 mirror CR. Final CRs in R1-2504880 and R1-2504881.

Release 16 URLLC 
R1-2504182	Draft CR on the PDSCH mapping type B starting symbol determination in TS 38.214 	NEC Corporation
R1-2504781	Summary on the PDSCH mapping type B starting symbol determination in TS 38.214	Moderator (NEC)
Moderated by Yue Zhou (NEC)

R1-2503948	Draft CR on reference point for the PDSCH starting symbol determination in TS 38.214	NEC
R1-2504780	Summary on the reference point for the PDSCH starting symbol determination in TS 38.214	Moderator (NEC)
Moderated by Yue Zhou (NEC)

Agreement
The TP in section 4 R1-2504780 is endorsed for Rel-17 TS 38.214 Clause 5.1.2.1 to clarify the reference point for PDSCH starting symbol determination.

R1-2504871	Draft CR on reference point for the PDSCH starting symbol determination	NEC
R1-2504873	Draft CR on reference point for the PDSCH starting symbol determination	NEC

Agreement
The draft in R1-2504871 is endorsed for Rel-17 alignment CR, and the draft CR in R1-2504873 is endorsed as Rel-18 mirror alignment CR. 


Release 17 SDT
R1-2503744	Discussion on suspending the RRC connection for SDT	Ofinno
R1-2503745	Draft CR on Suspending the RRC connection for SDT	Ofinno
R1-2503746	Draft CR on Suspending the RRC connection for SDT	Ofinno
R1-2504800	Summary of discussion on suspending the RRC connection for SDT	Moderator (Ofinno)
Moderated by Yunjung (Ofinno)

Release 17 Others
R1-2503957	Draft CR on Pathloss Reference RS for positioning SRS	Ofinno
R1-2504788	Summary on discussion on PL RS fallback for positioning SRS	Moderator (Ofinno)
Moderated by Ryan (Ofinno)

R1-2503549	Draft CR on pseudo-code in Section 9.2.5 of TS38.213	Samsung
Moderated by Kyungjun (Samsung)

Agreement
The draft CR in R1-2503549 is endorsed for alignment CR for Rel-17 and Rel-18, and the spec editor should also include this correction in the Rel-19 CR for TS38.213.

Release 18 Positioning
R1-2503743	Semi-Persistent SRS Frequency Hopping Discussion	Ofinno
R1-2504787	Summary on discussion on SP SRS frequency hopping support	Moderator (Ofinno)
Moderated by Ryan (Ofinno)

Conclusion
Companies are expected to bring contributions to RAN2 to fix the issue described in R1-2504787 in RAN2 specifications.

R1-2503945	Draft CR on SRS hopping for positioning in TS 38.211	NEC
R1-2504793	Summary on SRS hopping for positioning in TS 38.211	Moderator (NEC)
Moderated by Yukai Gao (NEC)
R1-2504846	CR on SRS hopping for positioning in TS 38.211	NEC

Agreement
The draft CR in R1-2503945 is endorsed. Final CR in R1-2504846.
Comeback for final CR - Yukai Gao (NEC)

Release 18 Positioning
R1-2503206	LS on the startSFN parameter for positioning SRS with TX frequency hopping	RAN2, ZTE
RAN2 is requesting RAN1 input on need and interpretation of the parameter startSFN. RAN1 response needed. To be handled under agenda item 7 (Rel-18 positioning).
Moderator: Mengzhen (ZTE).
Relevant tdoc(s):
R1-2503258	Discussion on startSFN for positioning UTW	Huawei, HiSilicon
R1-2503542	Discussion on the startSFN parameter for positioning SRS with TX frequency hopping	Samsung
R1-2503699	Draft reply LS on the startSFN parameter for positioning SRS FH	ZTE Corporation, Sanechips
R1-2503700	Discussion on RAN2 LS on the startSFN parameter for positioning SRS FH	ZTE Corporation, Sanechips
R1-2503345	Draft Reply LS on the startSFN parameter for positioning SRS with TX frequency hopping	vivo
R1-2503807	Discussion on the startSFN parameter for positioning SRS with TX frequency hopping	CATT
R1-2503808	Draft reply LS on the startSFN parameter for positioning SRS with TX frequency hopping	CATT
R1-2504011	Draft Reply LS to RAN2 on positioning SRS frequency hopping	Nokia
R1-2504622	Discussion on LS on the startSFN parameter for positioning SRS with TX frequency hopping	Ericsson

R1-2504767	Summary#1 on startSFN for positioning SRS FH	Moderator (ZTE)
R1-2504823	Summary#2 on startSFN for positioning SRS FH	Moderator (ZTE)

Agreement
The draft LS content in section 4 of R1-2504823 is endorsed.

Answer to Q1: No, parameter start SFN is not needed for UTW for positioning SRS frequency hopping. The parameter periodicityAndOffset-r18 and periodicityAndOffset-Ext-r18 for UTW already covers the startSFN and they indicate the periodicity in slots and the offset of the starting slot with respect to SFN#0 slot#0.

Final LS in R1-2504854.

TDoc file conclusion not found

TDoc file reading error

3GPP TSG RAN WG1 #121			R1-2504910
St Julian’s, Malta, May 19th – 23th, 2025

Agenda Item:	7
Source:	Moderator (Google)
Title:	Summary on CG-PUSCH in RACH-less LTM
Document for: 	Discussion and decision

Conclusion
Proposal 1: Endorse R1-2504295 as a Rel-18 CR in TS 38.214. 

3GPP TSG RAN WG1 #121	R1-2504919
St Julian’s, Malta, May 19th – 23rd, 2025
Agenda Item:	7
Source:	Moderator (MediaTek)
Title:	Final summary on collision handling between SSB and RA occasion
Document for:	Discussion
1	

Conclusion
Draft CR R1-2504917 was endorsed on Thursday online session. Final CR is R1-2504918.