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


Agenda Item:		9.2.4
Source:				InterDigital, Inc.
Title:						On Specifications 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. 

Observation 2: The determination of the PL offset and CPLC adjustment state when an SRS resource set is not configured with the followUnifiedTCI-StateSRS should be simple, without optimization for corner cases.

Proposal 2: Support Alt 3 where, 
When the SRS resource with lowest ID is configured with a TCI state, The PL offset and CLPC adjustment state indicated by that TCI state are applied to those SRS resources (i.e., reusing the rule specified in Rel-17) 
Otherwise, one of the two separate SRS CLPC adjustment states and one PL offset are configured in the SRS resource set, and they are applied on the SRS resources. 

3GPP TSG RAN WG1 Meeting #120bis	R1-2501783
Wuhan, China, April 7th – 11th, 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 issues for asymmetric DL sTRP/UL mTRP scenarios with the following proposals.
Proposal 1: For determination of PL offset, SRS CLPC adjustment and TAG ID for an SRS resource set that not configured with ‘followUnifiedTCI-StateSRS’ in asymmetric DL sTRP/UL mTRP deployment scenarios, support that:
The PL offset, CLPC adjustment state and TAG ID indicated by the TCI state configured to the SRS resource with lowest ID, where the SRS with lowest ID is always configured with one joint/UL TCI state, and the ‘referenceSignal’ in an UL TCI state is optional.
Proposal 2: 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 #120bis			R1-2501802
Wuhan, China, April 7th – 11th, 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:
To determine PL offset and CLI for SRS when SRS is configured not to follow unified TCI state or without any TCI configuration, support Alt3:
When the SRS resource with lowest ID is configured with a TCI state, The PL offset and CLPC adjustment state indicated by that TCI state are applied to those SRS resources (i.e., reusing the rule specified in Rel-17) 
Otherwise, one of the two separate SRS CLPC adjustment states and one PL offset are configured in the SRS resource set, and they are applied on the SRS resources. 
The solution agreed to determine for PL offset and CLI for SRS not following unified TCI state or without any TCI state configuration can be reused to determine TAG ID directly.
Reuse 1-bit PL-offset indication field to indicate PL-RS for CFRA-based PRACH:
the bit field index 0 of this field indicates that the PL-RS associated in the first indicated joint/UL TCI state is used for PRACH transmission power calculation 
the bit field index 1 of this field indicates that the PL-RS offset associated in the second indicated joint/UL TCI state is used for PRACH transmission power calculation.
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：

3GPP TSG RAN WG1 #120		R1-2501853
Wuhan, China, April 7th – 11th, 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
Proposal 2: For an SRS resource set not configured with followUnifiedTCI-StateSRS, the PL offset and CLPC adjustment state indicated by the TCI state configured to the SRS resource with lowest ID are applied to the SRS resources if the SRS resource with lowest ID is configured with a joint/UL TCI state. 
The above design is also applied to TAG for SRS when Rel-19 2TA is configured.

3GPP TSG RAN WG1 #120b		R1-2501864
Wuhan, China, April 7th – 11st, 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: For an SRS resource set not configured with followUnifiedTCI-StateSRS, regarding how to determine the PL offset and the CLPC adjustment state:
If the SRS resource with lowest ID is configured with a TCI state, The PL offset and CLPC adjustment state indicated by the TCI state configured to the SRS resource with lowest ID (i.e., reusing the rule specified in Rel-17) are applied on the SRS resources
Subject to UE capability, if the SRS resource with lowest ID is not configured with a TCI state:
One of the two separate SRS CLPC adjustment states and one PL offset are configured in the SRS resource set.
The P0, alphas, PL RS, CPLC adjustment state and PL offset configured in the SRS resource set are applied on the SRS resources.
Note: If the UE does not report such capability, NW will always configure a TCI state to the SRS resource with the lowest ID.
When the UE is configured with Rel-19 2 TA, the above design is also applied to TAG.
Proposal 2: Regarding whether/how to reset the CLPC of PUSCH/PUCCH/SRS, no further enhancement is needed.

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

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

Conclusions
In this contribution, we provided our views on DCI design for indicating PL RS for PDCCH-order PRACH, power control for SRS resource set not configured with followUnifiedTCI-StateSRS 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 a UE not provided with SSB-MTC-AddtionalPCI and not configured with multi-DCI based multi-TRP, the ‘PRACH association indicator’ field is reused to indicate PL RS for PRACH:
The bit field index 0 of this field indicates the DL RS that DMRS of PDCCH order DCI is QCLed with is used as PL RS for PRACH;
The bit field index 1 of this field indicates the SS/PBCH indicated by the SS/PBCH index field is used as PL RS for PRACH.
Proposal 2: For asymmetric DL sTRP/UL mTRP deployment scenarios, on determining the PL offset and the CLPC adjustment state for an SRS resource set not configured with followUnifiedTCI-StateSRS, Alt 3 is adopted:
When the SRS resource with lowest ID is configured with a TCI state, The PL offset and CLPC adjustment state indicated by that TCI state are applied to those SRS resources (i.e., reusing the rule specified in Rel-17).
Otherwise, one of the two separate SRS CLPC adjustment states and one PL offset are configured in the SRS resource set, and they are applied on the SRS resources.
Proposal 3: Regarding on how to reset the CLPC of PUSCH/PUCCH/SRS when receiving RAR of PDCCH-order PRACH, support Alt2:
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 #120-bis         						R1- 2502012
Wuhan, China, April 07th – April 11th, 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 PL offset and CLPC adjustment states for SRS, wherein an SRS resource set is not configured with followUnifiedTCI-StateSRS support Alt1 as a way forward.
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. 

3GPP TSG RAN WG1 #120bis		R1-2502019
Wuhan, China, April 7th – 11th, 2025	
Agenda Item:	9.2.4
Source:	China Telecom, ZTE
Title:	Discussion on enhancements for asymmetric DL sTRP/UL mTRP scenarios
Document for:	Discussion and Decision

Conclusion
In this paper, we discuss the issues for asymmetric DL sTRP/UL mTRP scenarios and have the following observations and proposals.
Proposal 1: Support Alt or Alt2, with preference to Alt2 for determination of PL offset and CLPC adjustment state for SRS resource set not configured with followUnifiedTCI-StateSRS, i.e., he PL offset and CLPC adjustment state indicated by the TCI state configured to the SRS resource with lowest ID (i.e., reusing the rule specified in Rel-17), the SRS with lowest ID is always configured with one joint/UL TCI state, the “referenceSignal” in a UL TCI state is optional.
Observation 1: When receiving the RAR of PDCCH-order PRACH in asymmetric DL sTRP/UL mTRP, only the CLPC towards DL TRP is supposed to be reset. 
Observation 2: The legacy mechanism can already guarantee the CLPC of DL TRP will be reset. 
Observation 3: Coupling CLPC and TAG configuration resulted by the new mechanism is not reasonable. 
Proposal 2: Don’t support the CLPC reset enhancement triggered by the RAR of PDCCH-ordered PRACH in Rel-19.

3GPP TSG-RAN WG1 Meeting #120bis                               R1-2502039
Wuhan, China, 07th – 11th April 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. 
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. 

For an SRS resource set not configured with followUnifiedTCI-StateSRS, regarding how to determine the PL offset and the CLPC adjustment state:
If the SRS resource with lowest ID is configured/updated with a TCI state, the PL offset and CLPC adjustment state indicated by the TCI state configured/updated to the SRS resource with lowest ID (i.e., reusing the rule specified in Rel-17) are applied on the SRS resources
Subject to UE capability, if the SRS resource with lowest ID is not configured/updated with a TCI state:
One of the two separate SRS CLPC adjustment states and one PL offset are configured in the SRS resource set.
The P0, alphas, PL RS, CPLC adjustment state and PL offset configured in the SRS resource set are applied on the SRS resources.
Note: If the UE does not report such capability, NW will always configure a TCI state to the SRS resource with the lowest ID.
When the UE is configured with Rel-19 2 TA, the above design is also applied to TAG.

The new 1-bit DCI field for PL offset indication in DCI format 1_0 can additionally indicate the PL RS for PDCCH-order PRACH transmission:
When there is one indicated joint/UL TCI state in Rel-17 unified TCI: 
The bit field index 0 of this field indicates that the DL RS that DMRS of PDCCH order DCI is QCL-ed with is used as PL RS for PRACH
The bit field index 1 of this field indicates that the pathlossReferenceRS-Id in the indicated joint/UL TCI state is used as PL RS for PRACH
Note: 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:
The bit field index 0 of this field indicates that 
The pathlossReferenceRS-Id in the first indicated joint/UL TCI state is used as PL RS for PRACH if PL offset is configured in the first indicated joint/UL TCI state
Otherwise, the DL RS that DMRS of PDCCH order is QCL-ed with is used as PL RS for PRACH
The bit field index 1 of this field indicates that 
The pathlossreferenceRS-Id in the second indicated joint/UL TCI state is used as PL RS for PRACH if PL offset is configured in the second indicated joint/UL TCI state
Otherwise, the DL RS that DMRS of PDCCH order is QCL-ed with is used as PL RS for PRACH

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 #120bis										R1-2502080
Wuhan, China, April 7th – 11th, 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:
Proposal 1:	Consider TRP DTX configuration to support switching between symmetric DL/UL and asymmetric DL sTRP/UL mTRP.
Proposal 2:	Clarify that PL offset can be applied to .
Proposal 3:	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 4:	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 5:	Support UE request to update the configured pathloss offset value.
Proposal 6:	Support UE to reset TPC accumulation as 0 upon reception of the PL offset value update MAC CE
Proposal 7:	Support Alt1 (the new 1-bit DCI field PL offset indication in DCI format 1_0) to reset CLPC.
Proposal 8:	PHR is triggered when the PL offset value update MAC CE provides a PL offset variation larger than a threshold.

3GPP TSG RAN WG1 #120bis	   	 	  	                	      R1-2502104
Wuhan, China, April 7th – 11th, 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.

TDoc file unavailable

3GPP TSG-RAN WG1 Meeting #120bis	 R1-2502106
Wuhan, China, April 7th – 11th , 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.
Observation 3	PL-offset and PL-RS are a pair of parameters associated with TCI state that determines the PRACH transmission power. Updating only PL-offset in PDCCH order without updating corresponding PL-RS causes mismatch on power parameters for PRACH transmission.
Observation 4	Similar to Rel-18 2TA, Rel-19 2TA includes scenarios of non-collocated mTRPs, hence larger than CP timing difference is valid for asymmetric mTRP scenario for intra-DU.
Observation 5	In Rel-18 2TA, n-TimingAdvanceoffset can be configured per TAG ID.
Observation 6	Rel-19 asymmetric mTRP has same synchronization assumption of non-collocated mTRPs as Rel-18 2TA, as the n-TimingAdvanceoffset is used for UL timing, it shall be configurable per TAG ID also for Rel-19 2TA.


Based on the discussion in the previous sections we propose the following:
Proposal 1	RAN1 to clarify when 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	Support that PL-RS of an UL TCI state to be linked with a DL-RS associated with an indicated DL TCI state.
Proposal 5	For intra-cell operation, the new 1-bit DCI field for PL offset indication in DCI format 1_0 can additionally indicate the PL RS for PDCCH-order PRACH transmission.
When there is one indicated joint/UL TCI state in Rel-17 unified TCI:
	The bit field index 0 of this field indicates that the DL RS that DMRS of PDCCH order DCI is QCLed with is used as PL RS for PRACH;
	The bit field index 1 of this field indicates that pathlossReferenceRS-Id in the indicated joint/UL TCI state is used as PL RS for PRACH.
When there are two indicated joint/UL TCI states in Rel-18 unified TCI:
i.	The bit field index 0 of this field indicates that the pathlossReferenceRS-Id in the first indicated joint/UL TCI state is used as PL RS for PRACH if PL offset is configured in the first indicated joint/UL TCI state,
ii.	The bit field index 1 of this field indicates that the pathlossreferenceRS-Id in the second indicated joint/UL TCI state is used as PL RS for PRACH if PL offset is configured in the second indicated joint/UL TCI state,
Proposal 6	For transmission of SRS resource sets that are not associated with any UL TCI states, support Alt 3:
	When the SRS resource with lowest ID is configured with a TCI state, the PL offset and CLPC adjustment state indicated by that TCI state are applied to those SRS resources
	Otherwise, one of the two separate SRS CLPC adjustment states and one PL offset are configured in the SRS resource set, and they are applied on the SRS resources
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	Send LS to RAN4 to check their opinion on the agreement on n-TimingAdvanceoffset:
i.	if it is workable and compliant with RAN4 understanding and practical deployment.
ii.	If it has impact on timing synchronization requirement that RAN4 need to take into account.
Proposal 9	RAN1 to study how to associate two-TA for transmission of SRS that are not associated with any UL TCI states.
Proposal 10	For transmission of SRS resource sets that are not associated with any UL TCI states:
	When the SRS resource with lowest ID in the SRS resource set is configured with a TCI state, the TAG ID indicated by the TCI state is applied to those SRS resources
	Otherwise, one of the TAG ID is configured in the SRS resource set, and it is applied to the SRS resources of the SRS resource set
Proposal 11	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.

3GPP TSG RAN WG1 #120b		                                         R1-2502110
Wuhan, China, Apr 07th – 11th, 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: Support Alt 1 for an SRS resource set not configured with followUnifiedTCI-StateSRS, regarding how to determine the PL offset and the CLPC adjustment state.
Proposal 4: 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.
Proposal 5: Study whether the power priority of two overlapped UL transmissions associated with a Macro TRP and a Micro TRP respectively should be enhanced considering the priority of the Macro TRP and the Micro TRP.
Proposal 6: Study whether the transmission priority of two overlapped UL transmissions associated with a Macro TRP and a Micro TRP respectively should be enhanced considering the priority of the Macro TRP and the Micro TRP.

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


Agenda item:	9.2.4
Title:	Discussion on enhancement 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: Support Alt3 with modification: When the SRS resource with lowest ID is configured with a TCI state, the PL offset and CLPC adjustment state indicated by that TCI state are applied to those SRS resources (i.e., reusing the rule specified in Rel-17). Otherwise, one of the two separate SRS CLPC adjustment states, PL offset, P0, alpha and PL-RS are configured in the SRS resource set, and they are applied on the SRS resources of the SRS resource set.
Proposal 2: For TAG ID indication, when the SRS resource with lowest ID in the SRS resource set is configured with a TCI state, the TAG ID indicated by the TCI state is applied to those SRS resources. Otherwise, one of the TAG ID is configured in the SRS resource set, and it is applied to the SRS resources of the SRS resource set.

4. 

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

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

Summary and conclusion
Proposal 1: Do not support to modify the CLPC reset mechanism of PUSCH/PUCCH/SRS for a UE configured with two TAGs when the UE receives a RAR of a PDCCH-order PRACH. 
Proposal 2: For an SRS resource set not configured with followUnifiedTCI-StateSRS, regarding how to determine the PL offset and the CLPC adjustment state, support Alt3 in RAN1#119 agreement.
 

3GPP TSG RAN WG1 #120bis		                                      R1-2502296
Wuhan, China, April 7th – 11st, 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. 
Support to reflect the impact of PL offset as above for Tx power calculation for PUSCH/PUCCH/SRS/PRACH in TS 38.213.
When a SRS resource set is not configured with followUnifiedTCI-StateSRS, and for a SRS resource from the SRS resource set
Support Alt1: Applying the PL offset associated with the UL/Joint TCI state of an SRS resource with lowest SRS-ResourceId in the SRS resource set 

3GPP TSG RAN WG1 #120bis	        	R1-2502314
Wuhan, China, April 7th – 11th, 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 #120bis                                         R1-2502360
Wuhan, China, April 7th – 11th, 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. Not support to further discuss on some cases for study on SRS, e.g., whether/how to apply PL offset for SRS resource set when the SRS resource set is not configured with TCI state, and whether/how to apply one of the two separate SRS CLPC adjustment states on the SRS resource set when the SRS resource set is not configured with TCI state. (i.e., Alt1 in Agreement from RAN1#119).

Proposal 6. Not support to additionally indicate other information via new 1-bit field (Pathloss offset indicator) in DCI format 1_0. 

Proposal 7. Support to reuse PRACH association field in DCI format 1_0 to indicate PL-RS of PRACH by relaxing/updating the condition (e.g., either tag2-Id is provided or not, multi-DCI based multi-TRP is not configured, SSB-MTC-AddtionalPCI is not configured, PL offset is configured)

Proposal 8. Adopt the following text proposal expressed by yellow highlight in Clause 7.3.1.2.1 in TS38.212.

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

3GPP TSG RAN WG1 #120bis	                                                R1-2502437
Wuhan, China, April 7th – 11th, 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: When a SRS resource set is not configured with followUnifiedTCI-StateSRS, we propose the following solution to derive the PC parameters in the asymmetric DL sTRP/UL mTRP scenario.
Alt 1.1: The PL offset and CLPC adjustment state indicated by the TCI state configured to the SRS resource with lowest ID (i.e., reusing the rule specified in Rel-17).
UE may ignore the referenceSignal configured for the joint/UL TCI state when the usage of the SRS resource set is set to ‘beamManagement’ and only the SRS resource with the lowest ID is configured with a TCI state.

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 that the joint/UL TCI state associated with the indicated TAG ID can be the indicated joint/UL TCI state. 

3GPP TSG RAN WG1 Meeting #120bis                               R1-2502507
Wuhan, CN, April 07-11, 2025
Source: 	ETRI
Title:	Discussion on 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 UE 0 is provided with and configured with SSB-MTC-AdditionalPCI and 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 with and configured with SSB-MTC-AdditionalPCI, not configured with EarlyUL-SyncConfig, and 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:    
Study whether/how to support PDCCH-order based PRACH preamble in case when there are a mixture of single DCI based mTRP and multi-DCI based mTRP, and multiple UL TRPs.

Proposal 3: 
For the asymmetric DL sTRP/UL mTRP deployment scenarios, when UE is not configured with PL offset in joint/UL TCI state(s) belonging to UL TRP(s), down-select one from the following alternatives for the association between NCD SSB (for each UL TRP) and related information:
Alt1: The association is sent to UE through RRC(s) from DL sTRP.
Alt2: The association is sent to UE through MAC-CE(s) from DL sTRP.
Alt3: The association is sent to UE through RRC(s) and MAC-CE(s) from DL sTRP.
FFS: related information (e.g., PCI, Tx power, scheduled resource, and NCD SSB measurement report period, etc) and whether the PCI for each UL TRP is identical or not


Proposal 4:
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 to indicate PL RS for PDCCH-order PRACH as follows:
If there is only one indicated joint/UL TCI state configured with a PL offset in Rel-17 Unified TCI, the bit field index 0 of this field indicates that the DL RS that the DMRS of the PDCCH-order DCI is QCLed with is used as the PL RS for determining PRACH preamble transmission power, and the bit field index 1 of this field indicates that the PL RS associated with the indicated joint/UL TCI state is used for determining PRACH transmission power.
The PL RS in the joint/UL TCI state for the bit field index 1 of this field is identical to the PL RS associated with one of the activated joint/UL TCI states corresponding a DL/UL capable TRP not associated with a PL offset.
If there are two indicated joint/UL TCI states each of which is configured with a PL offset in Rel-18 Unified TCI, the bit field index 0 of this field indicates that the PL RS associated with the first  indicated joint/UL TCI state is used for determining PRACH transmission power, and the bit field index 1 of this field indicates that the PL RS associated with the second indicated joint/UL TCI state is used for determining PRACH transmission power.
Each of the PL RSs in the joint/UL TCI states is identical to the PL RS associated with one of the activated joint/UL TCI states corresponding a DL/UL capable TRP not associated with a PL offset.

Proposal 5:
If the UE is provided with tag2-Id and SSB-MTC-AdditionalPCI, and the UE is not configured with coresetPoolIndex or the value of coresetPoolIndex is the same for all CORESETs if coresetPoolIndex is provided, the UE is configured with higher layer parameter PrachAssociationInPrach_InDCI, and the UE receives a RAR of a PDCCH-order PRACH, support to reuse the DCI field ‘PRACH association indicator’ in DCI format 1_0 to reset the closed loop power control adjustment state of PUSCH/PUCCH/SRS:
If there is one indicated joint/UL TCI state associated with SSB-MTC-AdditionalPCI in Rel-17 Unified TCI, the bit field index 0 of this field indicates that the UE resets the CLPC not associated with the indicated joint/UL TCI state, and the bit field index 1 of this field indicates that the UE resets the CLPC associated with the indicated joint/UL TCI state.
If adjusting the CLPC reset behavior is needed, the network may configure the UE via RRC, MAC CE, and/or DCI to interpret the bit field index value of the PRACH association indicator in a reversed manner before transmitting the PDCCH-order DCI containing this PRACH association field.
If there are two indicated joint/UL TCI states each of which is configured with SSB-MTC-AdditionalPCI in Rel-18 Unified TCI, the bit field index 0 of this field indicates that the UE resets the CLPC associated with the first indicated joint/UL TCI state, and the bit field index 1 of this field indicates that the UE resets the CLPC associated with the second indicated joint/UL TCI state.
If adjusting the CLPC reset behavior is needed, the network may configure the UE via RRC, MAC CE, and/or DCI to interpret the bit field index value in the opposite way, or to ignore them and interpret it as resetting the CLPC not associated with the indicated joint/UL TCI states before transmitting the PDCCH-order DCI containing this PRACH association field.

Proposal 6:
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, the UE is configured with higher layer parameter pLOffsetInPrach_InDCI, at least one configured TCI state for the serving cell is configured with plOffset, and the UE receives a RAR of a PDCCH-order PRACH, support to reuse the new 1-bit DCI field (e.g., PL offset indicator) in DCI format 1_0 to reset the closed loop power control adjustment state of PUSCH/PUCCH/SRS:
If there is only one indicated joint/UL TCI state configured with a PL offset in Rel-17 Unified TCI, the bit field index 0 of this field indicates that the UE resets the CLPC not associated with the indicated joint/UL TCI state, and the bit field index 1 of this field indicates that the UE resets the CLPC associated with the indicated joint/UL TCI state.
If adjusting the CLPC reset behavior, the network may configure the UE via RRC, MAC CE, and/or DCI to interpret the bit field index value of the PL offset indicator in a reversed manner before transmitting the PDCCH-order DCI containing this PL offset indicator.
If there are two indicated joint/UL TCI states each of which is configured with a PL offset in Rel-18 Unified TCI, the bit field index 0 of this field indicates that the UE resets the CLPC associated with the first indicated joint/UL TCI state, and the bit field index 1 of this field indicates that the UE resets the CLPC associated with the second indicated joint/UL TCI state.
If adjusting the CLPC reset behavior is needed, the network may configure the UE via RRC, MAC CE, and/or DCI to interpret the bit field index value in the opposite way, or to ignore them and interpret it as resetting the CLPC not associated with the indicated joint/UL TCI states before transmitting the PDCCH-order DCI containing this PRACH association field.

3GPP TSG RAN WG1 #120 bis	R1-2502527
Wuhan, China. 7 – 11 April. 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: For the closed loop power control loop reset 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: For the question, can the UE use a single timing reference towards the two TAGs when UL-Only TRP transmits the SSB and pathloss offset is not configured, the UE shall apply two timing references towards the two TAGs
Proposal 3: Study the impact of pathloss offsets on UL transmissions of RACH procedures, such as PRACH, Msg3 (for the 4-step RACH procedure), and MsgA (for the 2-step RACH procedure).
Proposal 4: Clarify whether the PL-Offset towards UL-Only TRP can be applied to other RACH types.

3GPP TSG RAN WG1 #120bis			                       R1-2502536
Wuhan, China, April 7th – 11th, 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#120bis                               R1-2502539
Wuhan, China, April 7th – 11th, 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: The new 1-bit DCI field in DCI format 1_0 can additionally indicate the PL RS for PDCCH-order PRACH transmission:
the bit field index 0 of the new 1-bit DCI field indicates that DL RS that DMRS of PDCCH order DCI is QCLed with is used as PL RS for PRACH;
the bit field index 1 of the new 1-bit DCI field indicates that pathlossReferenceRS-Id associated with the indicated joint/UL TCI state is used as PL RS for PRACH.
Proposal 2: For an SRS resource set not configured with followUnifiedTCI-StateSRS, regarding how to determine the PL offset and the CLPC adjustment state, support Alt4:
Alt4: 
When the SRS resource with lowest ID is configured with a TCI state, The PL offset and CLPC adjustment state indicated by that TCI state are applied to those SRS resources (i.e., reusing the rule specified in Rel-17) 
Otherwise, one PL offset and one CLPC adjustment state are applied on the SRS resources. 
FFS how to define the PL offset and CLPC adjustment state
Proposal 3: 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 4: 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 5: 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 Meeting #120bis                                           R1-2502601	
Wuhan, China, April 7th – 11th, 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 1: support Alt. 1 if no compelling use case is identified for Alt. 3. 

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

Proposal 3: In LS reply to RAN4, RAN1 replies that 
One downlink reference timing is supported and applied to both TAGs” are applied for the scenario that UE is not configured with PL offset in joint/UL TCI state(s) and UE may expect to receive SSB from UL TRP(s).

3GPP TSG RAN WG1 #120bis	R1-2502670
Wuhan, China, April 7th – 11th, 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:
Observation 1: When PL offset is configured, additional PCI is not configured.
Proposal 1: The new 1-bit DCI field for PL offset indication in DCI format 1_0 should additionally indicate the PL RS for PDCCH-order PRACH transmission.

Proposal 2: When UE is not configured with PL offset, PRACH association indicator can be reused for intra-cell and sDCI base.

Observation 2: Alt3 and Alt4 are not complete solution because PLRS and alpha are not determined when there is no SRS resource with a TCI state in an SRS resource set, which is not configured with followUnifiedTCI-StateSRS.
Observation 3: Alt1 includes an error case that when there is no SRS resource with a TCI state in SRS resource set, which is not configured with followUnifiedTCI-StateSRS, the power control parameters (i.e., PLoffset, CLPC, PLRS and alpha) is not determined.
Observation 4: When an SRS resource set is not configured with followUnifiedTCI-StateSRS, UE shall always use the referenceSignal in the TCI state to determine the Tx beam
Proposal 3: When an SRS resource set is not configured with followUnifiedTCI-StateSRS, the reference RS in the UL TCI state associated with the SRS resource in the SRS resource set should be optional (i.e., Alt2).
Proposal 4: Study to reset the CLPC of UL transmission when UE is configured with 2 TAGs.

3GPP TSG RAN WG1 #120bis			      R1-2502762
Wuhan, China, April 7th – 11th, 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 Alt.1 to reset the closed loop power control adjustment state for PUSCH/PUCCH/SRS in RAN1#120 agreement:
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 2
Reply to RAN4 LS (R1-2501699) as following:
Yes, RAN1 agreements in RAN1#118bis “One downlink reference timing is supported and applied to both TAGs” is applied regardless of whether PL-offset is configured or not.

3GPP TSG-RAN WG1 Meeting #120b	R1-2502813
Wuhan China, April 7 – April 11, 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. 
Study whether to add time restrictions to make sure that the UE uses PLDL and ΔPL (dB) with a matching time stamp.
Alt1: The PL offset and CLPC adjustment state indicated by the TCI state configured to the SRS resource with lowest ID (i.e., reusing the rule specified in Rel-17) and no extra enhancement.
The new 1-bit DCI field in DCI format 1_0 is not used to indicate PL RS for PDCCH-order PRACH.

3GPP TSG-RAN WG1 Meeting #120bis	R1-2502835
Wuhan, China, April 7th – 11th, 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 4: 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 5: 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 6: For Rel.17 unified TCI, support to reuse the 1-bit DCI field in DCI format 1_0 to indicate PL RS for PDCCH ordered PRACH if PL offset is configured for joint/UL TCI state(s):
the bit field index 0 of this field indicates that DL RS that DMRS of PDCCH order DCI is QCLed with is used for PRACH power control.
the bit field index 1 of this field indicates that the PL RS associated with the indicated joint/UL TCI state is used for PRACH power control if the indicated joint/UL TCI state is configured with PL offset; otherwise, DL RS that DMRS of PDCCH order DCI is QCLed with is used for PRACH power control.

Proposal 7: 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 8: For Rel.18 unified TCI, the 1-bit DCI field is used to indicate the PL RS for PDCCH ordered PRACH:
If the 1-bit DCI field is set to 0, the PL RS associated with the first indicated joint/UL TCI state is used as PL RS for PRACH power control if the first indicated joint/UL TCI state is configured with PL offset; otherwise, DL RS that DMRS of PDCCH order DCI is QCLed with is used as PL RS for PRACH power control.
If the 1-bit DCI field is set to 1, the PL RS associated with the second indicated joint/UL TCI state is used as PL RS for PRACH power control if the second indicated joint/UL TCI state is configured with PL offset; otherwise, DL RS that DMRS of PDCCH order DCI is QCLed with is used as PL RS for PRACH power control.

Proposal 9: Regarding CLPC reset for PUCCH/PUSCH/SRS, support Alt.1 if PL offset is configured in joint/UL TCI state:
Alt.1: 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 10: Regarding CLPC reset for PUCCH/PUSCH/SRS, support the following if PL offset is not configured in joint/UL TCI state(s) and if UE is provided with SSB-MTC-AddtionalPCI:
For a UE configured with two TAGs, when the UE receives a RAR of a PDCCH-order PRACH, 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 #120bis			R1-2502889
Wuhan, China, April 7th – 11th, 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: For an SRS resource set not configured with followUnifiedTCI-StateSRS, regarding how to determine the PL offset and the CLPC adjustment state:
If the SRS resource with lowest ID is configured with a TCI state,] The PL offset and CLPC adjustment state indicated by the TCI state configured to the SRS resource with lowest ID (i.e., reusing the rule specified in Rel-17) are applied on the SRS resources
Subject to UE capability, if the SRS resource with lowest ID is not configured with a TCI state:
One of the two separate SRS CLPC adjustment states and one PL offset are configured in the SRS resource set.
The P0, alphas, PL RS, CPLC adjustment state and PL offset configured in the SRS resource set are applied on the SRS resources.
Note: If the UE does not report such capability, NW will always configure a TCI state to the SRS resource with the lowest ID. 
When the UE is configured with Rel-19 2 TA, the above design is also applied to TAG.
Proposal 3: For resetting the CLPC of PUSCH/PUCCH/SRS, support the following alternative: 
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. 

3GPP TSG RAN WG1 #120bis                               		                                       R1-2502953
Wuhan, China, April 7th – 11th, 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 4.1: 
Answer the question of RAN4 as follows:
The RAN1 agreements in RAN1#118bis “One downlink reference timing is supported and applied to both TAGs” are NOT applied for the scenario that UE is not configured with PL offset in joint/UL TCI state(s) and UE may expect to receive SSB from UL TRP(s).
Please check the following new RAN1 agreement for further clarification.

Proposal 4.2:
For the scenario that the UE is configured with PL offset in joint/UL TCI state(s), when the UE is configured with rel-19 2 TAs, the UE maintains one single downlink reference timing
For the scenario that the UE is not configured with PL offset in joint/UL TCI state(s) and UE may expect to receive SSB from UL TRP(s), when the UE is configured with rel-19 2 TAs:
The UE maintains two downlink reference timings;
Baseline assumption for this feature is that Rx timing difference between two DL reference timings is no larger than one CP length, while it is subject to optional UE capability that the Rx timing difference between two DL reference timings can be assumed to be larger than CP length.
The reference point for PRACH transmission is indicated as follows:
if “PRACH association indicator” in DCI format 1_0 is 0, the reference timing is the first detected path (in time) of one of the corresponding downlink reference signal(s) of DL TCI state(s) of the reference cell associated with the first TAG.
if “PRACH association indicator” in DCI format 1_0 is 1, the reference timing is the first detected path (in time) of one of the corresponding downlink reference signal(s) of DL TCI state(s) of the reference cell associated with the second TAG

Proposal 2.1:
For an SRS resource set not configured with followUnifiedTCI-StateSRS, regarding how to determine the PL offset and the CLPC adjustment state, down-select [Alt1] from the following Alts:
Alt1: The PL offset and CLPC adjustment state indicated by the TCI state configured to the SRS resource with lowest ID (i.e., reusing the rule specified in Rel-17) and no extra enhancement.
Alt2: The PL offset and CLPC adjustment state indicated by the TCI state configured to the SRS resource with lowest ID (i.e., reusing the rule specified in Rel-17), the SRS with lowest ID is always configured with one joint/UL TCI state, the “referenceSignal” in a UL TCI state is optional.
Alt3: 
When the SRS resource with lowest ID is configured with a TCI state, The PL offset and CLPC adjustment state indicated by that TCI state are applied to those SRS resources (i.e., reusing the rule specified in Rel-17) 
Otherwise, one of the two separate SRS CLPC adjustment states and one PL offset are configured in the SRS resource set, and they are applied on the SRS resources. The P0, alphas and PL RS, configured in the SRS resource set are applied on the SRS resources.
Alt4: 
When the SRS resource with lowest ID is configured with a TCI state, The PL offset and CLPC adjustment state indicated by that TCI state are applied to those SRS resources (i.e., reusing the rule specified in Rel-17) 
Otherwise, one PL offset and one CLPC adjustment state are applied on the SRS resources. 
FFS how to define the PL offset and CLPC adjustment state
When the UE is configured with Rel-19 2 TA, the above design is also applied to TAG.

Proposal 1.4:
For asymmetric DL sTRP/UL mTRP deployment scenario in FR2, study whether to include SRS resource as one MPE measurement RS resource for beam specific MPE report.

Proposal 3.1:
Regarding whether/how to reset the CLPC of PUSCH/PUCCH/SRS, further study and down-select one from the following alternatives:
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.
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: Introduce one 1-bit DCI field in DCI 1_0 to explicitly indicate which one of the CLPCs to be resetted.
Alt4: Not introduce any enhancement.

Contributions in 9.2.4
R1-2501745	On Specifications of Rel-19 Asymmetric mTRP Operation	InterDigital, Inc.
R1-2501783	Discussion on enhancements for asymmetric DL sTRP/UL mTRP scenarios	ZTE Corporation, Sanechips, China Telecom
R1-2501802	Remaining issues on asymmetric DL sTRP/UL mTRP scenarios	vivo
R1-2501853	Enhancement for asymmetric DL sTRP/UL mTRP scenarios	MediaTek Inc.
R1-2501864	Enhancements for asymmetric DL sTRP/UL mTRP scenarios	Spreadtrum, UNISOC
R1-2501988	Discussion on enhancements for asymmetric DL sTRP and UL mTRP scenarios	CATT
R1-2502012	Enhancement for asymmetric DL sTRP UL mTRP	Tejas Network Limited
R1-2502019	Discussion on enhancements for asymmetric DL sTRP/UL mTRP scenarios	China Telecom, ZTE
R1-2502039	Enhancements on asymmetric DL STRP/UL MTRP scenarios	Ofinno
R1-2502080	Discussion on enhancements for asymmetric DL sTRP and UL mTRP scenarios	NEC
R1-2502104	Discussions on asymmetric DL sTRP/UL mTRP scenarios	LG Electronics
R1-2502106	Remaining issues on asymmetric DL sTRP UL mTRP scenarios	Ericsson
R1-2502110	Enhancement for asymmetric DL sTRP/UL mTRP scenarios	Lenovo
R1-2502156	Discussion on enhancement for asymmetric DL sTRP/UL mTRP scenarios	CMCC
R1-2502227	Enhancements for asymmetric DL sTRP/UL mTRP scenarios	Huawei, HiSilicon
R1-2502296	Enhancements on asymmetric DL sTRP/UL mTRP scenarios	OPPO
R1-2502314	Enhancement for asymmetric DL sTRP/UL mTRP scenarios	Sony
R1-2502360	Views on Rel-19 asymmetric DL sTRP/UL mTRP scenarios	Samsung
R1-2502437	Discussion on enhancement for asymmetric DL sTRP/UL mTRP scenarios	Xiaomi
R1-2502507	Discussion on asymmetric UL MIMO operation	ETRI
R1-2502527	Enhancement for asymmetric DL sTRP/UL mTRP scenarios	Nokia
R1-2502536	Discussion on asymmetric DL sTRP/UL mTRP scenarios	TCL
R1-2502539	Discussion on enhancements for asymmetric DL sTRP/UL mTRP scenarios	Transsion Holdings
R1-2502601	Enhancements for asymmetric DL sTRP/UL mTRP scenarios	Apple
R1-2502670	Enhancement for asymmetric DL sTRP/UL mTRP scenarios	Sharp
R1-2502762	Discussion on enhancement for asymmetric DL sTRP/UL mTRP scenarios	NTT DOCOMO, INC.
R1-2502813	Enhancement for asymmetric DL sTRP/UL mTRP scenarios	Panasonic
R1-2502835	Enhancement for asymmetric DL sTRP and UL mTRP deployment scenarios	Qualcomm Incorporated
R1-2502889	Discussion on enhancement for asymmetric DL sTRP and UL mTRP scenarios	Google


Contributions on the LS
R1-2501789	Draft reply LS to RAN4 on DL timing reference to support two TA enhancement for asymmetric DL sTRP/ UL mTRP	ZTE Corporation, Sanechips
R1-2501791	Draft LS reply on DL timing reference to support two TA enhancement for asymmetric DL sTRP/ UL mTRP	vivo
R1-2501857	Draft reply LS on DL timing reference to support two TA enhancement for asymmetric DL sTRP/ UL mTRP	Spreadtrum, UNISOC
R1-2501965	Discussion on LS on two TA enhancement for asymmetric DL sTRP/ UL mTRP	CATT
R1-2502018	Discussion on RAN4 LS of DL timing reference to support two TA enhancement for asymmetric DL sTRP/ UL mTRP	China Telecom
R1-2502061	Discussion on RAN4 LS on DL timing reference to support two TA enhancement for asymmetric DL sTRP/ UL mTRP	ZTE Corporation, Sanechips
R1-2502081	Draft LS reply on DL timing reference to support two TA enhancement for asymmetric DL sTRP UL mTRP	NEC
R1-2502113	Reply LS on DL timing reference to support two TA enhancement for asymmetric DL sTRP UL mTRP	Lenovo
R1-2502146	Discussion on LS on DL timing reference to support two TA enhancement for asymmetric DL sTRP UL mTRP	CMCC
R1-2502147	Draft reply on LS on DL timing reference to support two TA enhancement for asymmetric DL sTRP UL mTRP	CMCC
R1-2502256	Discussion on LS on DL timing reference to support two TA enhancement for asymmetric DL sTRP/ UL mTRP	OPPO
R1-2502349	Draft reply LS on DL timing reference to support two TA enhancement for asymmetric DL sTRP/ UL mTRP	Samsung
R1-2502429	Draft reply LS on DL timing reference issue for Rel-19 MIMO	Xiaomi
R1-2502827	Discussion for LS reply on on DL timing reference to support two TA enhancement for asymmetric DL sTRP and UL mTRP	Qualcomm Incorporated
R1-2502948	Discussion on DL timing reference to support two TA enhancement for asymmetric DL sTRP/ UL mTRP	Huawei, HiSilicon
R1-2501854	Draft reply LS on DL timing reference to support two TA enhancement for asymmetric DL sTRP/ UL mTRP	MediaTek Inc.
R1-2502523	Draft LS reply on DL timing reference to support two TA enhancement for asymmetric DL sTRP/ UL mTRP	Nokia
R1-2502886	Draft reply of LS on DL timing reference to support two TA enhancement for asymmetric DL sTRP and UL mTRP	Google

3GPP TSG RAN WG1 #120bis                               		                                       R1-2502954
Wuhan, China, April 7th – 11th, 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
Revised Proposal 1.1:
If the PL offset associated with the indicated joint/UL TCI state is included in the PRACH transmission power for PDCCH-order PRACH transmission, the pathlossReferenceRS-Id in the same indicated joint/UL TCI state is used to determine PL RS for the PDCCH-order PRACH transmission.

Proposal 1.4:
For asymmetric DL sTRP/UL mTRP deployment scenario in FR2, study whether to include SRS resource as one MPE measurement RS resource for beam specific MPE report.

Updated Proposal 3.1:
Regarding whether/how to reset the CLPC of PUSCH/PUCCH/SRS, further study and down-select one from the following alternatives:
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.
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.
Alt4: Not introduce any enhancement.


Updated Alt1: DOCOMO, NEC, QC, ETRI, 
Alt2: CATT, Sharp, Ofinno, IDC, Fainity, TCL,  
Alt4: Samsung, ZTE, MediaTek, CMCC, OPPO, Ericsson, CATT, Lenovo, Huawei/Hisilicon, LG, Nokia, vivo, Panasonic

Contributions in 9.2.4
R1-2501745	On Specifications of Rel-19 Asymmetric mTRP Operation	InterDigital, Inc.
R1-2501783	Discussion on enhancements for asymmetric DL sTRP/UL mTRP scenarios	ZTE Corporation, Sanechips, China Telecom
R1-2501802	Remaining issues on asymmetric DL sTRP/UL mTRP scenarios	vivo
R1-2501853	Enhancement for asymmetric DL sTRP/UL mTRP scenarios	MediaTek Inc.
R1-2501864	Enhancements for asymmetric DL sTRP/UL mTRP scenarios	Spreadtrum, UNISOC
R1-2501988	Discussion on enhancements for asymmetric DL sTRP and UL mTRP scenarios	CATT
R1-2502012	Enhancement for asymmetric DL sTRP UL mTRP	Tejas Network Limited
R1-2502019	Discussion on enhancements for asymmetric DL sTRP/UL mTRP scenarios	China Telecom, ZTE
R1-2502039	Enhancements on asymmetric DL STRP/UL MTRP scenarios	Ofinno
R1-2502080	Discussion on enhancements for asymmetric DL sTRP and UL mTRP scenarios	NEC
R1-2502104	Discussions on asymmetric DL sTRP/UL mTRP scenarios	LG Electronics
R1-2502106	Remaining issues on asymmetric DL sTRP UL mTRP scenarios	Ericsson
R1-2502110	Enhancement for asymmetric DL sTRP/UL mTRP scenarios	Lenovo
R1-2502156	Discussion on enhancement for asymmetric DL sTRP/UL mTRP scenarios	CMCC
R1-2502227	Enhancements for asymmetric DL sTRP/UL mTRP scenarios	Huawei, HiSilicon
R1-2502296	Enhancements on asymmetric DL sTRP/UL mTRP scenarios	OPPO
R1-2502314	Enhancement for asymmetric DL sTRP/UL mTRP scenarios	Sony
R1-2502360	Views on Rel-19 asymmetric DL sTRP/UL mTRP scenarios	Samsung
R1-2502437	Discussion on enhancement for asymmetric DL sTRP/UL mTRP scenarios	Xiaomi
R1-2502507	Discussion on asymmetric UL MIMO operation	ETRI
R1-2502527	Enhancement for asymmetric DL sTRP/UL mTRP scenarios	Nokia
R1-2502536	Discussion on asymmetric DL sTRP/UL mTRP scenarios	TCL
R1-2502539	Discussion on enhancements for asymmetric DL sTRP/UL mTRP scenarios	Transsion Holdings
R1-2502601	Enhancements for asymmetric DL sTRP/UL mTRP scenarios	Apple
R1-2502670	Enhancement for asymmetric DL sTRP/UL mTRP scenarios	Sharp
R1-2502762	Discussion on enhancement for asymmetric DL sTRP/UL mTRP scenarios	NTT DOCOMO, INC.
R1-2502813	Enhancement for asymmetric DL sTRP/UL mTRP scenarios	Panasonic
R1-2502835	Enhancement for asymmetric DL sTRP and UL mTRP deployment scenarios	Qualcomm Incorporated
R1-2502889	Discussion on enhancement for asymmetric DL sTRP and UL mTRP scenarios	Google


Contributions on the LS
R1-2501789	Draft reply LS to RAN4 on DL timing reference to support two TA enhancement for asymmetric DL sTRP/ UL mTRP	ZTE Corporation, Sanechips
R1-2501791	Draft LS reply on DL timing reference to support two TA enhancement for asymmetric DL sTRP/ UL mTRP	vivo
R1-2501857	Draft reply LS on DL timing reference to support two TA enhancement for asymmetric DL sTRP/ UL mTRP	Spreadtrum, UNISOC
R1-2501965	Discussion on LS on two TA enhancement for asymmetric DL sTRP/ UL mTRP	CATT
R1-2502018	Discussion on RAN4 LS of DL timing reference to support two TA enhancement for asymmetric DL sTRP/ UL mTRP	China Telecom
R1-2502061	Discussion on RAN4 LS on DL timing reference to support two TA enhancement for asymmetric DL sTRP/ UL mTRP	ZTE Corporation, Sanechips
R1-2502081	Draft LS reply on DL timing reference to support two TA enhancement for asymmetric DL sTRP UL mTRP	NEC
R1-2502113	Reply LS on DL timing reference to support two TA enhancement for asymmetric DL sTRP UL mTRP	Lenovo
R1-2502146	Discussion on LS on DL timing reference to support two TA enhancement for asymmetric DL sTRP UL mTRP	CMCC
R1-2502147	Draft reply on LS on DL timing reference to support two TA enhancement for asymmetric DL sTRP UL mTRP	CMCC
R1-2502256	Discussion on LS on DL timing reference to support two TA enhancement for asymmetric DL sTRP/ UL mTRP	OPPO
R1-2502349	Draft reply LS on DL timing reference to support two TA enhancement for asymmetric DL sTRP/ UL mTRP	Samsung
R1-2502429	Draft reply LS on DL timing reference issue for Rel-19 MIMO	Xiaomi
R1-2502827	Discussion for LS reply on on DL timing reference to support two TA enhancement for asymmetric DL sTRP and UL mTRP	Qualcomm Incorporated
R1-2502948	Discussion on DL timing reference to support two TA enhancement for asymmetric DL sTRP/ UL mTRP	Huawei, HiSilicon
R1-2501854	Draft reply LS on DL timing reference to support two TA enhancement for asymmetric DL sTRP/ UL mTRP	MediaTek Inc.
R1-2502523	Draft LS reply on DL timing reference to support two TA enhancement for asymmetric DL sTRP/ UL mTRP	Nokia
R1-2502886	Draft reply of LS on DL timing reference to support two TA enhancement for asymmetric DL sTRP and UL mTRP	Google

TDoc file unavailable