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

Agenda Item:	9.2.4
Source:	Huawei, HiSilicon
Title:	Enhancements for asymmetric DL sTRP/UL mTRP scenarios
Document for:	Discussion and Decision

Summary #1 on Rel-19 asymmetric DL sTRP/UL mTRP, OPPO, RAN1#120bis.

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

Agenda Item:	9.2.4
Source: 	MediaTek Inc.
Title:	Enhancement for asymmetric DL sTRP/UL mTRP scenarios
Document for: 	Discussion and Decision

Conclusion
In this contribution, enhancement for asymmetric DL STRP/UL MTRP scenarios was discussed. Based on the discussion in the previous sections, we made the following proposals:
Proposal 1: If there are two CLPC adjustment states PUSCH/PUCCH/SRS, and if two TAGs are configured for the Serving Cell in which the PDCCH-order triggered RA procedure is being performed:
UE shall reset the PUSCH/PUCCH/SRS CLPC adjustment state with l = 0 if UE receives RAR with TI field = 0
UE shall reset the PUSCH/PUCCH/SRS CLPC adjustment state with l = 1 if UE receives RAR with TI field = 1
Above apply for both Rel-18 2TA for M-DCI based MTRP and Rel-19 2TA

3GPP TSG RAN WG1 #121	                   	      R1-2503354
St Julian’s, Malta, May 19th – 23th, 2025
Source: 	vivo
Title:	Remaining issues on asymmetric DL sTRP/UL mTRP scenarios
Agenda Item	9.2.4
Document for:	Discussion and Decision

Conclusion 
In this contribution, following proposals are presented:
Support to introduce an RRC parameter to indicate:
When a full set or subset of {two joint TCI states} are mapped to all codepoints for joint TCI state mode, the first joint TCI states can be applied to DL, and both joint TCI states can be applied to UL; 
When a full set or subset of {one DL TCI state, two UL TCI states} mapped to all codepoints for separate TCI state mode, the DL TCI state can be applied to DL, and two UL TCI states can be applied to UL for separate TCI state mode.
Support the following TP for TS 38.214：
There is no need to reset closed-loop power adjustment state for PRACH transmission.
Support to reset the CLPC corresponding to the indicated TCI state when PL offset of the indicated TCI state is updated.
Support to configure separate p0-NominalWithGrant, p0-nominal and p0-NominalWithoutGrant for UL transmission towards UL TRP.

3GPP TSG RAN WG1 #121																    R1-2503436	
Malta, MT, May 19th – 23rd, 2025


Agenda Item:		9.2.4
Source:				InterDigital, Inc.
Title:						Remaining Details of Rel-19 Asymmetric mTRP Operation
Document for:		Discussion and Decision

Conclusions
In this contribution, we presented and discussed our views on the remaing cases for study, including implications of deployment scenario and potential aspects of enhancements. Based on the presented discussion, we make the following observations and proposals:

Observation 1: The multi-TRP realistic deployments are based on Rel-18 with two TA feature, and it is not justified to optimize the case when Rel-17 unified TCI framework is enabled.  

Proposal 1: Support Alt 2 where, 
Alt 2: For a UE configured with two TAGs, one TAG ID is indicated in the RAR
The UE resets the closed loop power control adjustment state associated with a joint/UL TCI state associated with the indicated TAG. 

3GPP TSG RAN WG1 #121		R1-2503511
St Julian’s, Malta, May 19th – 23th, 2025
Agenda Item:     9.2.4
Source:	Spreadtrum, UNISOC
Title:	             Enhancement for asymmetric DL sTRP/UL mTRP scenarios
Document for:	Discussion and decision

Conclusion 
In this contribution, we provide our opinions on enhancements for asymmetric DL sTRP/UL mTRP scenarios:
Proposal 1: Regarding whether/how to reset the CLPC of PUSCH/PUCCH/SRS, no further enhancement is needed.

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

Agenda item:	9.2.4
Source: 	Samsung
Title: 	Views on Rel-19 asymmetric DL sTRP/UL mTRP scenarios
Document for:	Discussion and Decision

Conclusion
In this contribution, the following observation and proposals are given: 

Proposal 1. Support to introduce a functionality of simultaneous update on PL offset among multiple CCs in the CC list via MAC-CE.

Proposal 2. Support to introduce “a TCI state group” which includes a number of TCI states, in order to update PL offset in those TCI states via a single MAC-CE simultaneously.

Proposal 3. Clarify that PL offset update MAC-CE can be only applied to joint/UL TCI state(s) which PL offset value is configured. In other words, PL offset update MAC-CE cannot be applied to joint/UL TCI state(s) which PL offset is not configured.

Proposal 4. Clarify whether PL offset can be applied to PRACH transmission other than PDCCH order triggered PRACH or not (e.g., PRACH for PCell beam failure recovery procedure).

Proposal 5. For asymmetric MTRP scenario in FR2, support SRS as one of MPE resource for beam specific MPE report.

Proposal 6. Adopt the following text proposal expressed by yellow highlight in Clause 7.3.1.1.2 in TS38.213.

Proposal 7. Revise the description and value range for RRC parameter startingBitOfFormat2-3.

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

Source:	ZTE Corporation, Sanechips, China Telecom
Title:		Discussion on enhancements for asymmetric DL sTRP/UL mTRP scenarios
Agenda Item:	9.2.4
Document for:	Discussion and Decision

Conclusion
In this contribution, we present our views of the remaining issue for asymmetric DL sTRP/UL mTRP scenarios with the following proposal.
Proposal 1: Do not support to introduce any enhancements of the existing mechanism on resetting CLPC of PUSCH/PUCCH/SRS in asymmetric DL sTRP/UL mTRP deployment scenarios.

3GPP TSG RAN WG1 #121         						R1- 2503712
Malta, MT, May 19th – May 23rd, 2025

Agenda item:	      9.2.4
Source:	      Tejas Networks Ltd	
Title:		      Enhancement for asymmetric DL sTRP/UL mTRP scenarios
Document for:     Discussion and Decision

Conclusions
In this section we summarize our observations and proposals.
With the support for one downlink reference timing applied to both TAGs, the UE will monitor a single DL reference timing and apply both TA commands to the same DL reference timing to determine the UL transmission timings toward the two TAGs.

If a UE reports “Overlapping UL transmission reduction” capability, it implies that UE expects two overlapping transmissions and can apply the capability to handle all overlapping UL transmissions with repetition including Type A and Type B.

Regarding two TA enhancement with one downlink reference signal for both TAGs, consider to study the conditions under which UE monitors the reference signal and applies both TA commands for determining two TAs toward two TAGs. 

Regarding two TA enhancement, do not support the need to separately address overlapping intra-slot PUSCH type-B repetition transmissions associated with different TAGs. 

Regarding handling the reset of the CLPC of PUSCH/PUCCH/SRS when UE is configured with 2 TAGs, support Alt3 to not introduce any enhancement. 

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

Agenda Item:	9.2.4
Source:	Ofinno
Title:	Enhancements on asymmetric DL STRP/UL MTRP scenarios
Document for:	Discussion and Decision

Conclusion
In this contribution, we make the following proposals. 
Support the following update in TS38.214 to enable single indicated DL TCI state and two indicated UL TCI states in separate TCI state mode:
When two joint TCI states are indicated, regarding which indicated joint TCI state to apply to downlink receptions:
If only one of the two joint TCI states is associated with PL offset, the joint TCI state which is not associated with PL offset is applied.
If both two joint TCI states are associated with PL offset, down-select from the following Alts:
Alt1: the first indicated joint TCI state is applied.
Alt2: A new RRC parameter indicates which indicated joint TCI state to apply. 
Regarding application time for PL offset by MAC CE, the UE applies the MAC CE command in the first slot that is after slot where  is the slot where the UE would transmit a PUCCH with HARQ-ACK information for the PDSCH providing the MAC CE command.
Regarding 1-bit DCI field for PL offset indication in DCI format 1_0, support the followings:
When there is one indicated joint/UL TCI state in Rel-17 unified TCI,
If the indicated joint/UL TCI state is not associated with PL offset, the UE does not expect the bit field index to be set to one.
When there are two indicated joint/UL TCI states in Rel-18 unified TCI,
If only the first or second indicated joint/UL TCI state is associated with PL offset, the UE does not expect the bit field index to be set to one or zero, respectively.
FFS: Whether both of two indicated joint/UL TCI states are not associated with PL offset
For a UE being not configured with PL offset and not configured with SSB-MTC-AdditionalPCI and configured with Rel-19 2 TAGs, support to reuse the DCI field ‘PRACH association indicator’ in DCI format 1_0 to indicate PL RS for PDCCH-order PRACH:
The bit field index 0 of this field is mapped to the DL RS that the DM-RS of the PDCCH order is QCL-ed, and 
the bit field index 1 of this field is mapped to the SS/PBCH indicated by this DCI format.
This DCI field is present when the corresponding RRC parameter is configured and multi-DCI based mTRP is not configured.
Note: The UE expects that the indicated SS/PBCH block in the PDCCH order is configured as pathlossReferenceRS-Id of an active TCI state
When a UE receives a RAR in response to a PDCCH ordered PRACH and is configured with two TAGs and two CLPC adjustment states for PUCCH/PUSCH/SRS, the indication of the TAG ID in the RAR is used to determine the CLPC to reset for l = 0 or l = 1.
When there is one indicated joint/UL TCI state in Rel-17 Unified TCI:
If the indicated joint/UL TCI state is associated with the indicated TAG in the RAR, the UE resets the CLPC associated with the indicated joint/UL TCI state
If the indicated joint/UL TCI state is NOT associated with the indicated TAG in the RAR, the UE resets the CLPC different from the CLPC associated with the indicated joint/UL TCI state
When there are two indicated joint/UL TCI states in Rel-18 Unified TCI:
The UE resets the CLPC associated with an indicated joint/UL TCI state associated with the indicated TAG. 
After a UE completes a beam failure recovery, for PUSCH/PUCCH/SRS transmissions to the UL TRP, the UE applies the PL offset configured in indicated TCI state of the UL TRP to a pathloss estimate of the candidate reference signal identified for the beam failure recovery. 
After a UE completes a beam failure recovery, for PUSCH/PUCCH/SRS transmissions to the UL TRP, the UE does not update/reset the spatial domain transmission filter of the UL TRP. 

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

Source:	CATT
Title:	Remaining issues on asymmetric DL sTRP and UL mTRP scenarios
Agenda Item:	9.2.4
Document for:	Discussion and Decision

Conclusion
In this contribution, we provided our views on PL RS indication for PDCCH-order PRACH and the resetting of the CLPC of PUSCH/PUCCH/SRS when receiving RAR of PDCCH-order PRACH for a UE configured with two TAGs for asymmetric DL sTRP/UL mTRP deployment scenarios. The following proposals are provided:
Proposal 1: For asymmetric DL sTRP/UL mTRP deployment scenarios, for a UE not provided with SSB-MTC-AddtionalPCI and not configured with multi-DCI based mTRP, legacy PL RS determination schemes for PDCCH-order PRACH transmission is reused.
Proposal 2: Regarding on how to reset the CLPC of PUSCH/PUCCH/SRS when receiving RAR of PDCCH-order PRACH, support the following scheme: 
For a UE configured with two TAGs, one TAG ID is indicated in the RAR
The UE resets the closed loop power control adjustment state associated with a joint/UL TCI state associated with the indicated TAG.

3GPP TSG-RAN WG1 Meeting #121	R1-2503817
Malta, May 19 – May 23, 2025

Source:	Panasonic
Title: 	Enhancement for asymmetric DL sTRP/UL mTRP scenarios	
Agenda Item:	9.2.4
Document for:	Discussion

Conclusions
Based on the discussion above, we propose the following:
For the asymmetric DL sTRP/UL mTRP scenarios, support to include PL offset in the calculation of uplink transmission power calculation for PUSCH, PUCCH, and SRS.
For the asymmetric DL sTRP/UL mTRP scenarios, support to include the PL offset in the triggering of the power headroom reporting. 
Send an LS to RAN2 to RAN2 to inform them about including the PL offset in the triggering of the power headroom reporting.
  The quantity “PLDL - as ΔPL (dB)” only represents uplink pathloss when the NW is updating the pathloss offset at the same time scale as the downlink pathloss variation
For the asymmetric DL sTRP/UL mTRP scenarios, support the triggering of the UE by the NW to report power headroom. 
Do not support any enhancement on the legacy TCI framework for asymmetric UL mTRP scenario.
Do not support including SRS resource as one MPE measurement RS resource for beam specific MPE report and wait for input from RAN4 on this matter.
The CLPC is reset for both CBRA/CFRA PRACH. 
The issue of resetting the wrong CLPC is valid however is out of scope regarding agenda item 9.2.4. 

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


Agenda item:	9.2.4
Title:	Discussion on enhancements for asymmetric DL sTRP/UL mTRP scenarios
Source:	CMCC
Document for:	Discussion and Decision

1. 

Conclusion
Based on the above discussions, the proposals are as follows:
Proposal 1: Regarding whether/how to reset the CLPC of PUSCH/PUCCH/SRS, support Alt3: Not introduce any enhancement.

4. 

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

Agenda Item:	9.2.4
Source:	Xiaomi
Title:	Discussion on enhancement for asymmetric DL sTRP/UL mTRP scenarios
Document for:	Discussion and Decision

Conclusion
In this contribution, we provide our views on some issues for the DL sTRP/UL mTRP scenario, and the following are our proposals, 
Proposal 1: For the indication of TCI states, we prefer the following solutions,
when two joint TCI states are indicated, pre-define the first indicated TCI state for DL reception;
when two DL TCI states are indicated, configure the two DL TCI states exactly the same;

Proposal 2: For the resetting of the CLPC after receiving the RAR of the PDCCH ordered PRACH, we support to fix the issue and slightly prefer Alt.2 via using the indicated joint/UL TCI state.

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

Agenda Item:	9.2.4
Source:	Lenovo
Title:	Enhancement for asymmetric DL sTRP/UL mTRP scenarios
Document for:	Discussion

Conclusion
As a summary, we have the following proposals on enhancement for asymmetric DL sTRP/UL mTRP scenarios:
Proposal 1: Support to remove the ‘antenna switching’ restriction for aperiodic SRS resource sets triggered by DCI format 2_3 if two CLPC adjustment states are configured for SRS.
Proposal 2: Support using DCI format 2_3 to trigger aperiodic SRS resource set configured with multiple entries in availableSlotOffsetList in asymmetric DL sTRP/UL mTRP scenario and introduce SRS offset indicator field in DCI format 2_3 in this case.
Proposal 3: If two joint TCI states are indicated for asymmetric DL sTRP/UL mTRP scenarios in FR1, the first joint TCI state is applied for DL channels/signals which follow the indicated TCI state. And the TCI selection field in DCI format 1_1/1_2 as well as higher layer parameter applyIndicatedTCI-State for PDCCH and CSI-RS are not needed.

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

Agenda item:	9.2.4
Source:	NEC
Title: 	Discussion on enhancement for asymmetric DL sTRP and UL mTRP scenarios
Document for:	Discussion and Decision

Conclusion
In this contribution, we provided our views on Rel-19 MIMO work on enhancements for asymmetric DL sTRP/UL mTRP scenarios, and we have the following observations and proposals:
Observation 1: Micro node may not always turn off its DL transmission.
Proposal 1:	Consider TRP DTX configuration to support switching between symmetric DL/UL and asymmetric DL sTRP/UL mTRP.
Proposal 2:	PL offset can be calculated at NW by configuring SRS transmissions to different TRPs with the same Tx power or UE reporting information of transmit power.
Proposal 3:	The separate UL TCI state configured with PL offset value(s) can be regarded for UL only, and the source RS in the separate UL TCI state should only be SRS resource.
Proposal 4:	Support UE request to update the configured pathloss offset value.
Proposal 5:	Support UE to reset TPC accumulation as 0 upon reception of the PL offset value update MAC CE
Proposal 6:	Support updated Alt1 (the new 1-bit DCI field PL offset indication in DCI format 1_0) to reset CLPC.

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

Agenda Item:	9.2.4
Source:	Ericsson
Title:	Remaining issues on asymmetric DL sTRP UL mTRP scenarios
Document for:	Discussion, Decision
1	

Conclusion
In the previous sections we made the following observations: 
Observation 1	For FR2, when a UE moves around in the cell and need to update the serving Anchor TRP beam, the pathloss reference signal configured in an UL-TCI state used for UL transmission towards the UL-only TRP need to be updated with RRC signaling, which generates a significant amount of overhead signaling and latency.
Observation 2	Linking the PL-RS of UL-TCI state with a DL-RS associated with an indicated DL TCI state enables automatic update of the PL-RS of UL transmission when UE changes DL TCI states and thus significantly reduces signaling overhead.


Based on the discussion in the previous sections we propose the following:
Proposal 1	RAN1 to clarify the conclusion when Rel-18 unified TCI is configured and {one DL TCI state + up to two UL TCI states} can be applied, which of the two understanding alternatives is meant by “applied”:
Alt1: {one DL TCI state + up to two UL TCI states} can be configured and indicated
Alt2: separate DL/UL TCI state pairs can be configured and indicated, but only {one DL TCI state + up to two UL TCI states} are used
Proposal 2	If Alt1 is correct, support configuration and indication of {one DL TCI state + up to two UL TCI states}
Proposal 3	If Alt2 is correct, clarify whether or not the asymmetric DL sTRP/UL mTRP deployment can be indicated with two different DL TCI states
Proposal 4	RAN1 agree to support Alt1, i.e., configuration and indication of {one DL TCI state + up to two UL TCI states} and capture the following TP in TS 38.214
Proposal 5	Support that PL-RS of an UL TCI state to be linked with a DL-RS associated with an indicated DL TCI state.
Proposal 6	Support that PL-RS of an UL TCI state associated with a UL-only TRP can be update with the same MAC-CE that updates the path loss offset.
Proposal 7	When a MAC CE containing PL offset is received at slot n, UE shall be able to apply updated pathloss at slot n+.
Proposal 8	Study whether and how to address practical synchronization error between Anchor TRP and UL-only TRP for UL and DL timing control in asymmetric DL sTRP UL mTRP deployment.
FFS: UE can be provided with a DL reference timing offset. DL reference timing for communication with UL-only TRP for the UE is obtained from the DL reference timing of the anchor TRP and DL reference timing offset.
Proposal 9	Agree to the text proposals TP1 and TP2 for 38.213.

3GPP TSG RAN WG1 #121	   	 	  	                	      R1-2503986
St Julian’s, Malta, May 19th – 23th, 2025
Agenda item:	9.2.4
Source:	LG Electronics
Title:	Discussions on asymmetric DL sTRP/UL mTRP scenarios
Document for:	Discussion and Decision

Conclusion
In this contribution, we have discussed enhancements for asymmetric DL sTRP/UL mTRP scenarios, and provided the following proposals.

Proposal #1: Support the following PL-RS determination rule for PDCCH-ordered PRACH:
If the 1-bit bit field indicates not to use PL offset associated with the indicated TCI in Rel-17 unified TCI or if the 1-bit field indicates first or second indicated TCI not configured with PL offset in Rel-18 unified TCI, the legacy PL-RS determination rule can be used for the PDCCH-ordered PRACH
Otherwise, PL-RS configured in the indicated TCI is used for the PDCCH-ordered PRACH
Proposal #2: Further discuss how to define/configure RACH occasion for UL TRP.

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

Agenda Item:					    9.2.4
Source:	Sony
Title:	Enhancement for asymmetric DL sTRP/UL mTRP scenarios
Document for:	Discussion

Conclusions
The following observations and proposals were made in this contribution:
Observation 1: For asymmetric DL sTRP/UL mTRP deployment scenarios, it is assumed that coverage of the UL TRP as UL-only cell overlaps with the coverage of DL TRP as macro cell in heterogeneous network.
Observation 2: S-DCI based mTRP is considered in asymmetric DL sTRP/UL mTRP deployment.
Observation 3: Calculating pathloss offset by using single SRS reception on the same SRS resource may not be accurate especially for FR2 because SRS on the same resource may not be reached to both DL sTRP and UL mTRP because of different Tx beam and SRS resource need to be separated between DL sTRP and UL mTRP which may result in changing SRS transmission power. 
Proposal 1: Study whether/how to facilitate gNB’s determination of the value of PL offset from specification point of view especially for FR2.
Proposal 2: Discuss whether implicit SRS transmit power indication with only one or two SRS sequences can be used for path-loss estimation of the UL-only TRP (Option C). 

3GPP TSG RAN WG1 #121	R1-2504079
Malta. 19 – 23 May. 2025

Agenda item:		9.2.4
Source:	Nokia
Title:	Enhancement for asymmetric DL sTRP/UL mTRP scenarios
Document for:		Discussion and Decision

Conclusion
In this contribution, we make the following proposals. Please consider adopting them.
Proposal 1:When the RAR of the PDCCH Order PRACH is received, we are of the opinion that additional procedures are not necessary. It could be handled within the UE implementation.
Proposal 2: Clarify whether the PL-Offset towards UL-Only TRP can be applied to other RACH types. 
Proposal 3. In the asymmetric DL sTRP / UL mTRP scenario when UE uses one reference timing for two links, the timing error in UE to UL-Only TRP link may be larger. In such a situation, we propose to have an indication of the timing offset value from the DL and UL capable TRP to UE. 
Proposal 4. In the asymmetric DL sTRP / UL mTRP scenario, if the DL/UL TRP and UL-Only TRPs are operating in different frequencies, for example CC or BWP, the corresponding frequency-dependent correction will be applied to the PL-Offset value.

3GPP TSG RAN WG1 Meeting #121                                  R1-2504135
Malta, MT, May 19-23, 2025
Source: 	ETRI
Title:	Remaining issues in asymmetric UL MIMO operation
Agenda Item:	9.2.4
Document for:	Discussion/Decision

Conclusion
In this contribution, we note the following proposals.

Proposal 1: 
If a UE is provided with and configured with SSB-MTC-AdditionalPCI, and the UE is not configured with EarlyUL-SyncConfig and/or multi-DCI-based mTRP, the Cell indicator field can be reused to indicate the cell where the PDCCH-order-based PRACH preamble is transmitted as follows:
This field is present when the corresponding RRC parameter is activated/configured/provided.
A -bit field is used to indicate the cell for PRACH transmission, where  is the number of SSB-MTC-AdditionalPCI cells configured by SSB-MTC-AdditionalPCI.
In this case, bit index 0 of the Cell indicator field is mapped to the serving cell, while the remaining bit indexes are mapped in ascending order to the SSB-MTC-AdditionalPCI cells configured according to the higher-layer parameter xxx (e.g., measConfig) for example. Specifically, bit index 1 is mapped to the SSB-MTC-AdditionalPCI cell with the smallest candidate identity.
In other cases, a 0-bit field is used.

Proposal 2:
For a UE provided/configured with SSB-MTC-AdditionalPCI, and the UE is not configured with EarlyUL-SyncConfig, and the UE is not configured with multi-DCI based mTRP, support to reuse the PRACH retransmission indicator field for retransmission of PDCCH-order based PRACH preamble as follows:
This field is present when the corresponding RRC parameter is activated/configured/provided.
If the cell indicated by the Cell indicator field is an additional PCI cell, this field indicates the initial transmission or retransmission of PRACH according to a predefined table.
If the cell indicated by the Cell indicator field is the serving cell but not an additional PCI cell, this field is reserved.

Proposal 3:
For a UE configured with tag2-Id and SSB-MTC-AdditionalPCI in intra-cell mTRP case, when the UE is not configured with PL offset in joint/UL TCI state(s), the UE is not configured with coresetPoolIndex or the value of coresetPoolIndex is the same for all CORESETs if coresetPoolIndex is provided, and the UE is configured with higher layer parameter PrachAssociationInPrach_InDCI, support to reuse the DCI field ‘PRACH association indicator’ in DCI format 1_0 to indicate PL RS for PDCCH-order PRACH:
The bit field index 0 of this field is mapped to the DL RS that the DM-RS of the PDCCH order is QCLed, and 
the bit field index 1 of this field is mapped to the SS/PBCH indicated by this DCI format.
This DCI field is present when the corresponding RRC parameter is configured and multi-DCI based mTRP is not configured.

Proposal 4:
For a UE configured with 2 TAGs, when the UE receives a RAR of a PDCCH-order PRACH:
If the UE is provided with tag2-Id, and the UE is not configured with coresetPoolIndex or the value of coresetPoolIndex is the same for all CORESETs if coresetPoolIndex is provided, and the UE is configured with higher layer parameter pLOffsetInPrach_InDCI and at least one configured TCI state for the serving cell is configured with plOffset, support to reuse the new 1-bit DCI field (e.g., PL offset indicator) in DCI format 1_0:
When there is one indicated joint/UL TCI state in Rel-17 Unified TCI:
If the 1-bit DCI field is 0, the UE resets the CLPC that is different from the CLPC associated with the indicated joint/UL TCI state.
If the 1-bit DCI field is 1, the UE resets the CLPC associated with the indicated joint/UL TCI state.
When there are two indicated joint/UL TCI states in Rel-18 Unified TCI:
If the 1-bit DCI field is 0, the UE resets the CLPC associated with the first indicated joint/UL TCI state;
If the 1-bit DCI field is 1, the UE resets the CLPC associated with the second indicated joint/UL TCI state 
If the UE is configured with tag2-Id and SSB-MTC-AdditionalPCI, and the UE is not configured with PL offset in joint/UL TCI state(s), and the UE is not configured with coresetPoolIndex or the value of coresetPoolIndex is the same for all CORESETs if coresetPoolIndex is provided, and the UE is configured with higher layer parameter PrachAssociationInPrach_InDCI, support to reuse the PRACH association indicator in DCI format 1_0:
If the indicated joint/UL TCI state is associated with the same PCI as indicated by the PRACH association indicator, the UE resets the closed loop power control adjustment state associated with the indicated joint/UL TCI state.
If the indicated joint/UL TCI state is associated with a different PCI from the one indicated by the PRACH association indicator, the UE resets the closed loop power control adjustment state that is different from the closed loop power control adjustment state associated with the indicated joint/UL TCI state.

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

Agenda Item:	9.2.4
Source:	Transsion Holdings
Title:	Discussion on enhancements for asymmetric DL sTRP/UL mTRP scenarios
Document for:	Discussion and decision

Conclusion
In this contribution, we discuss the potential enhancements for asymmetric DL sTRP/UL mTRP. Based on the discussion above, we provide the following proposals:
Proposal 1: When SRS-CarrierSwitching is not configured, the DCI format 2_3 can still be used to indicate TPC commands for separate SRS CLPC adjustment states for a UE configured with two SRS CLPC adjustment states.
Proposal 2: Regarding the CLPC reset of PUSCH/PUCCH/SRS, support Alt1:
Alt1: For a UE configured with two TAGs, when the UE receives a RAR of a PDCCH-order PRACH, according to the new 1-bit DCI field PL offset indication in DCI format 1_0:
When there is one indicated joint/UL TCI state in Rel-17 Unified TCI:
If the 1-bit DCI field is 0, the UE resets the CLPC that is different from the CLPC associated with the indicated joint/UL TCI state.
If the 1-bit DCI field is 1, the UE resets the CLPC associated with the indicated joint/UL TCI state.
When there are two indicated joint/UL TCI states in Rel-18 Unified TCI:
If the 1-bit DCI field is 0, the UE resets the CLPC associated with the first indicated joint/UL TCI state;
If the 1-bit DCI field is 1, the UE resets the CLPC associated with the second indicated joint/UL TCI state.
Proposal 3: Regarding asymmetric DL sTRP/UL mTRP deployment scenarios, 'TCI selection' is not necessary and default TCI state(e.g., first one of two indicated states) can be applied for PDSCH reception.
Proposal 4: Regarding separate DL/UL TCI state mode, up to one DL TCI state and up to two UL TCI states are mapped to the codepoint of TCI field.
4 

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

Source:	OPPO
Title:	Enhancements on asymmetric DL STRP/UL MTRP scenarios
Agenda Item:	9.2.4
Document for:	Discussion

Conclusion
In this section, allow us to repeat our proposals and observations. 
For UE configured with Rel-19 2 TAGs, when the UE is not configured with PL offset in joint/UL TCI state(s), support to reuse the DCI field ‘PRACH association indicator’ to indicate PL RS for PDCCH-order PRACH.

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

Agenda Item:	9.2.4
Source:	Google
Title:	Discussion on enhancement for asymmetric DL sTRP and UL mTRP scenarios
Document for: 	Discussion

Conclusion
According to the above discussion(s), we have the following observation(s) and/or proposal(s). 
Observation 1: If 2TA for S-DCI is introduced, it is unclear how to transmit an UL transmission with two indicated TCI states applied, and one of indicated TCI states is associated with a TAG with expired TA timer.  
Proposal 1: For the asymmetric DL sTRP/UL mTRP deployment scenarios, if one of the indicated joint/UL TCI state applied for an UL transmission (e.g., UL channel with SDM/SFN scheme) is associated with an expired TA value, UE skips the UL transmission. 
Proposal 2: Adopt the following changes in Clause 5.1.5 in TS38.214: 

Proposal 3: For a UE configured with 2 TAGs and without coresetPoolIndex, when the UE receives a RAR of a PDCCH-order PRACH:
If PL offset is configured in joint/UL TCI state(s), according to the new 1-bit DCI field PL offset indication in DCI format 1_0:
When there is one indicated joint/UL TCI state in Rel-17 Unified TCI:
If the 1-bit DCI field is 0, the UE resets the CLPC adjustment state that is different from the CLPC associated with the indicated joint/UL TCI state.
If the 1-bit DCI field is 1, the UE resets the CLPC adjustment state associated with the indicated joint/UL TCI state.
When there are two indicated joint/UL TCI states in Rel-18 Unified TCI:
If the 1-bit DCI field is 0, the UE resets the CLPC adjustment state associated with the first indicated joint/UL TCI state;
If the 1-bit DCI field is 1, the UE resets the CLPC adjustment state associated with the second indicated joint/UL TCI state. 
If PL offset is not configured in joint/UL TCI state(s) and the UE is configured with SSB-MTC-AddtionalPCI, according to the PRACH association indicator in DCI format 1_0:
If the indicated joint/UL TCI state is associated with the same PCI as indicated by the PRACH association indicator, the UE resets the CLPC adjustment state associated with the indicated joint/UL TCI state.
If the indicated joint/UL TCI state is associated with a different PCI from the one indicated by the PRACH association indicator, the UE resets the CLPC adjustment state that is different from that associated with the indicated joint/UL TCI state 

3GPP TSG- RAN WG1 Meeting #121                                          R1-2504314	
St Julian’s, Malta, May 19th – 23th, 2025
Agenda Item:	9.2.4
Source:	Apple Inc.
Title:	Enhancements for asymmetric DL sTRP/UL mTRP scenarios
Document for:	Discussion/Decision

Conclusion
In this contribution, we provide our views on R19 enhancement for asymmetric DL sTRP/UL mTRP. We have 

Proposal: If enhancement to reset the CLPC of PUSCH/PUCCH/SRS is taken, introduce 1 bit to signal which CLPC is selected for reset.

3GPP TSG-RAN WG1 Meeting #121	R1-2504390
St Julian’s, Malta, May 19th – 23th, 2025
Agenda item:	9.2.4
Source: 	Qualcomm Incorporated
Title: 	Enhancement for asymmetric DL sTRP and UL mTRP deployment scenarios
Document for:	Discussion/Decision

Conclusion 1: Type 3 PHR reporting is supported in a serving cell/BWP where the UE is configured with two separate SRS CLPC adjustment states when two UL carriers are configured for the serving cell/BWP:
If a UE determines that a Type-3 PHR is reported, the UE computes the Type-3 PHR based on existing PHR calculation formula without considering the PL offset.

Proposal 3: When a joint/UL TCI state associated with a PL offset is applied for PUSCH/PUCCH/SRS transmission, the UE expects the PL RS in the joint/UL TCI state is the same as the PL RS associated with one of the activated joint/UL TCI states corresponding DL TRP (e.g., not associated with a PL offset).
Proposal 4: For Rel.17 unified TCI, clarify that the bit field index 1 of the 1-bit DCI field in DCI 1_0 indicates that PL offset is not included in the PRACH transmission power calculation if the indicated joint/UL TCI state is not configured with PL offset.

Proposal 5: For Rel-18 unified TCI, clarify the following for PL offset indication using the 1-bit DCI field in DCI 1_0:
the bit field index 0 of this field indicates that PL offset is not included in the PRACH transmission power calculation if the first indicated joint/UL TCI state is not configured with PL offset.
the bit field index 1 of this field indicates that PL offset is not included in the PRACH transmission power calculation if the second indicated joint/UL TCI state is not configured with PL offset.

Proposal 6: Regarding CLPC reset for PUCCH/PUSCH/SRS, support updated Alt.1: 
Updated Alt1: For a UE configured with 2 TAGs, when the UE receives a RAR of a PDCCH-order PRACH:
If PL offset is configured in joint/UL TCI state(s), according to the new 1-bit DCI field PL offset indication in DCI format 1_0:
When there is one indicated joint/UL TCI state in Rel-17 Unified TCI:
If the 1-bit DCI field is 0, the UE resets the CLPC that is different from the CLPC associated with the indicated joint/UL TCI state.
If the 1-bit DCI field is 1, the UE resets the CLPC associated with the indicated joint/UL TCI state.
When there are two indicated joint/UL TCI states in Rel-18 Unified TCI:
If the 1-bit DCI field is 0, the UE resets the CLPC associated with the first indicated joint/UL TCI state.
If the 1-bit DCI field is 1, the UE resets the CLPC associated with the second indicated joint/UL TCI state 
If PL offset is not configured in joint/UL TCI state(s) and the UE is configured with SSB-MTC-AddtionalPCI, according to the PRACH association indicator in DCI format 1_0: 
If the indicated joint/UL TCI state is associated with the same PCI as indicated by the PRACH association indicator, the UE resets the closed loop power control adjustment state associated with the indicated joint/UL TCI state.
If the indicated joint/UL TCI state is associated with a different PCI from the one indicated by the PRACH association indicator, the UE resets the closed loop power control adjustment state that is different from the closed loop power control adjustment state associated with the indicated joint/UL TCI state.

3GPP TSG RAN WG1 #121	R1-2504458
St Julian’s, Malta, May 19th – 23th, 2025
Source:	Sharp
Title:	Enhancement for asymmetric DL sTRP/UL mTRP scenarios
Agenda Item:	9.2.4
Document for:	Discussion and Decision

Conclusion
In this contribution, we have the following proposal:
Proposal 1: Study to reset the CLPC of UL transmission when UE is configured with 2 TAGs.
Observation 1: CLPC resetting mechanism issue present since R18 2TA
Proposal 2: Reset the closed loop power control adjustment state associated with a joint/UL TCI state associated with the indicated TAG for R18 2TA and R19 2TA (i.e., Alt 2).

TDoc file unavailable

3GPP TSG RAN WG1 #121			                       R1-2504463
Malta, MT, May 9th – 23th, 2025

Agenda Item:	9.2.4
Source:		TCL
Title:			Discussion on asymmetric DL sTRP/UL mTRP scenarios
Document for:	Discussion and Decision
1 

Conclusion
In these contributions, our opinions on asymmetric DL sTRP/UL mTRP scenarios are listed as follows.
The asymmetric DL sTRP/UL mTRP deployment scenario have two modes, complete separation and partial separation.
Introduce a new unified TCI state mode (e.g. named as partialJoint) which is used to indicate partial joint TCI state mode.
SIB1 can carry PL information for msg1, msgA and msg3.
Msg2 can carry PL information for msg3.
In complete separation scenario, network side cannot acquire PL offset.
Network can acquire PL of the UL-only TRP according to the measurement of UL signals and indicates to UE.
Support Alt 2: For a UE configured with two TAGs, one TAG ID is indicated in the RAR.
4 

3GPP TSG RAN WG1 #121			      R1-2504497
St Julian’s, Malta, May 19th – 23rd, 2025
Source:	NTT DOCOMO, INC.
Title:	Discussion on enhancement for asymmetric DL sTRP/UL mTRP scenarios
Agenda Item:	9.2.4
Document for: 	Discussion and Decision

Conclusion
In this contribution, we discussed the enhancements for asymmetric DL sTRP/UL mTRP scenarios. Based on the discussion, we made following observations and proposals.
Proposal 1
Support to reset the closed loop power control adjustment state for PUSCH/PUCCH/SRS.

Proposal 2
For asymmetric DL sTRP/UL mTRP scenarios, support SRS as one of MPE resource for beam specific MPE report.

3GPP TSG RAN WG1 #121                               		                                       R1-2504655
St Julian’s, Malta, May 19th – 23th, 2025
Source:	Moderator (OPPO)
Title:	Summary #1 on Rel-19 asymmetric DL sTRP/UL mTRP
Agenda Item:	9.2.4
Document for:	Discussion and Decision

Proposals for Online Discussion
Proposal 1.4:
When the UE transmits a PUCCH with HARQ-ACK information in slot n corresponding to the PDSCH carrying the MAC CE command updating PL offset of TCI state(s), the updated PL offset(s) shall be applied starting from the first slot that is after  where μ is the SCS configuration for the PUCCH.

Proposal 3.1
Regarding whether/how to reset the CLPC of PUSCH/PUCCH/SRS, down-select one from the following Alt2 and Alt3:
Alt2: For a UE configured with two TAGs, one TAG ID is indicated in the RAR
The UE resets the closed loop power control adjustment state associated with a joint/UL TCI state associated with the indicated TAG.
Alt3: Not introduce any enhancement.

Supporting companies:
Alt2: InterDigital, Ofinno, CATT, Xiaomi, Sharp, TCL, DOCOMO, Xiaomi, QC, IDC,
Alt3: Huawei/HiSilicon, Spreadtrum, ZTE, China Telecom, Tejas, Panasonic, CMCC, OPPO, Lenovo, LG, vivo, Nokia, 

Proposal 1.1:
Support to further reuse the “PRACH association indicator” field in DCI 1_0 to indicate PL RS for PDCCH order PRACH when the UE is provided with 2 TAs, not configured with PL offset in joint/UL TCI state(s), not configured with multi-DCI based mTRP, and not provided with SSB-MTC-AddtionalPCI: 
The bit field index 0 of this field is mapped to the DL RS that the DM-RS of the PDCCH order is QCLed, and 
The bit field index 1 of this field is mapped to the SS/PBCH indicated by this DCI 1_0.


Proposal 1.2
For asymmetric DL sTRP/UL mTRP scenario, support to include SRS as MPE measurement resource for beam specific MPE reporting. 
The mpe-ReferenceSignal can be configured as one SRS resource ID.


Proposal 1.3:
To enable indicating one DL TCI state + two UL TCI states for asymmetric DL sTRP/UL mTRP deployment scenarios, support the following text changes in 38.214:


Contributions in 9.2.4
R1-2503278	Enhancements for asymmetric DL sTRP/UL mTRP scenarios	Huawei, HiSilicon
R1-2503304	Enhancement for asymmetric DL sTRP/UL mTRP scenarios	MediaTek Inc.
R1-2503354	Remaining issues on asymmetric DL sTRP/UL mTRP scenarios	vivo
R1-2503436	Remaining Details of Rel-19 Asymmetric mTRP Operation	InterDigital, Inc.
R1-2503511	Enhancements for asymmetric DL sTRP/UL mTRP scenarios	Spreadtrum, UNISOC
R1-2503558	Views on Rel-19 asymmetric DL sTRP/UL mTRP scenarios	Samsung
R1-2503671	Discussion on enhancements for asymmetric DL sTRP/UL mTRP scenarios	ZTE Corporation, Sanechips, China Telecom
R1-2503712	Enhancement for asymmetric DL sTRP UL mTRP	Tejas Network Limited
R1-2503730	Enhancements on asymmetric DL STRP/UL MTRP scenarios	Ofinno
R1-2503789	Remaining issues on asymmetric DL sTRP and UL mTRP scenarios	CATT
R1-2503817	Enhancement for Asymmetric DL sTRP/UL mTRP Scenarios	Panasonic
R1-2503826	Discussion on enhancements for asymmetric DL sTRP/UL mTRP scenarios	CMCC
R1-2503878	Discussion on enhancement for asymmetric DL sTRP/UL mTRP scenarios	Xiaomi
R1-2503915	Enhancement for asymmetric DL sTRP/UL mTRP scenarios	Lenovo
R1-2503929	Discussion on enhancements for asymmetric DL sTRP and UL mTRP scenarios	NEC
R1-2503978	Remaining issues on asymmetric DL sTRP UL mTRP scenarios	Ericsson
R1-2503986	Discussions on asymmetric DL sTRP/UL mTRP scenarios	LG Electronics
R1-2504063	Enhancement for asymmetric DL sTRP/UL mTRP scenarios	Sony
R1-2504079	Enhancement for asymmetric DL sTRP/UL mTRP scenarios	Nokia
R1-2504135	Remaining issues in asymmetric UL MIMO operation	ETRI
R1-2504173	Discussion on enhancements for asymmetric DL sTRP/UL mTRP scenarios	Transsion Holdings
R1-2504231	Enhancements on asymmetric DL sTRP/UL mTRP scenarios	OPPO
R1-2504298	Discussion on enhancement for asymmetric DL sTRP and UL mTRP scenarios	Google
R1-2504314	Enhancements for asymmetric DL sTRP/UL mTRP scenarios	Apple
R1-2504390	Enhancement for asymmetric DL sTRP and UL mTRP deployment scenarios	Qualcomm Incorporated
R1-2504458	Enhancement for asymmetric DL sTRP/UL mTRP scenarios	Sharp
R1-2504463	Discussion on asymmetric DL sTRP/UL mTRP scenarios	TCL
R1-2504497	Discussion on enhancement for asymmetric DL sTRP/UL mTRP scenarios	NTT DOCOMO, INC.

3GPP TSG RAN WG1 #121                               		                                       R1-2504656
St Julian’s, Malta, May 19th – 23th, 2025
Source:	Moderator (OPPO)
Title:	Summary #2 on Rel-19 asymmetric DL sTRP/UL mTRP
Agenda Item:	9.2.4
Document for:	Discussion and Decision

Proposals for Online Discussion
Proposal 1.5 v2:
In asymmetric DL sTRP/UL mTRP deployment scenarios, after the beam failure recovery is completed successfully, support the following for PCell BFR and SCell BFR (not per-TRP BFR)
The UE does not reset the spatial domain filter and power control parameters on the PUSCH/PUCCH/SRS that follows the indicated TCI state if the indicated TCI state is configured with PL offset or associated with an SSB of additionalPCI.

Contributions in 9.2.4
R1-2503278	Enhancements for asymmetric DL sTRP/UL mTRP scenarios	Huawei, HiSilicon
R1-2503304	Enhancement for asymmetric DL sTRP/UL mTRP scenarios	MediaTek Inc.
R1-2503354	Remaining issues on asymmetric DL sTRP/UL mTRP scenarios	vivo
R1-2503436	Remaining Details of Rel-19 Asymmetric mTRP Operation	InterDigital, Inc.
R1-2503511	Enhancements for asymmetric DL sTRP/UL mTRP scenarios	Spreadtrum, UNISOC
R1-2503558	Views on Rel-19 asymmetric DL sTRP/UL mTRP scenarios	Samsung
R1-2503671	Discussion on enhancements for asymmetric DL sTRP/UL mTRP scenarios	ZTE Corporation, Sanechips, China Telecom
R1-2503712	Enhancement for asymmetric DL sTRP UL mTRP	Tejas Network Limited
R1-2503730	Enhancements on asymmetric DL STRP/UL MTRP scenarios	Ofinno
R1-2503789	Remaining issues on asymmetric DL sTRP and UL mTRP scenarios	CATT
R1-2503817	Enhancement for Asymmetric DL sTRP/UL mTRP Scenarios	Panasonic
R1-2503826	Discussion on enhancements for asymmetric DL sTRP/UL mTRP scenarios	CMCC
R1-2503878	Discussion on enhancement for asymmetric DL sTRP/UL mTRP scenarios	Xiaomi
R1-2503915	Enhancement for asymmetric DL sTRP/UL mTRP scenarios	Lenovo
R1-2503929	Discussion on enhancements for asymmetric DL sTRP and UL mTRP scenarios	NEC
R1-2503978	Remaining issues on asymmetric DL sTRP UL mTRP scenarios	Ericsson
R1-2503986	Discussions on asymmetric DL sTRP/UL mTRP scenarios	LG Electronics
R1-2504063	Enhancement for asymmetric DL sTRP/UL mTRP scenarios	Sony
R1-2504079	Enhancement for asymmetric DL sTRP/UL mTRP scenarios	Nokia
R1-2504135	Remaining issues in asymmetric UL MIMO operation	ETRI
R1-2504173	Discussion on enhancements for asymmetric DL sTRP/UL mTRP scenarios	Transsion Holdings
R1-2504231	Enhancements on asymmetric DL sTRP/UL mTRP scenarios	OPPO
R1-2504298	Discussion on enhancement for asymmetric DL sTRP and UL mTRP scenarios	Google
R1-2504314	Enhancements for asymmetric DL sTRP/UL mTRP scenarios	Apple
R1-2504390	Enhancement for asymmetric DL sTRP and UL mTRP deployment scenarios	Qualcomm Incorporated
R1-2504458	Enhancement for asymmetric DL sTRP/UL mTRP scenarios	Sharp
R1-2504463	Discussion on asymmetric DL sTRP/UL mTRP scenarios	TCL
R1-2504497	Discussion on enhancement for asymmetric DL sTRP/UL mTRP scenarios	NTT DOCOMO, INC.