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

Agenda Item:	8.12.2
Source:	NEC
Title:	RACH Procedure for Asymmetric DL sTRP/UL mTRP
Document for:	Discussion, Decision

Conclusion and Proposal
We have the following proposals:
Proposal: 1: UE initiated RACH procedure to UL-only TRP is supported.
Proposal 2: the pathloss offset between anchored downlink TRP and UL only TRP be applied to the final RSRP used for the comparison with the configured RSRP thresholds on top of RSRP measurement of the DL RS.
Proposal 3: To further study how the UE acquires the pathloss offset between anchored downlink TRP and UL only TRP. 

Annex: Relevant RAN1 agreements on PRACH

Agreement
Support applying PL offset on PDCCH-order PRACH towards a UL TRP in FR1.
Note: The DL reference timing determination for PDCCH-order PRACH transmission to an UL TRP is still based on the DL RS defined in current RAN4 specification
Above is subject to a separate UE capability signaling

Agreement
For indicating PL offset for PDCCH-order PRACH, introduce a new 1-bit DCI field in DCI format 1_0:
This DCI field exists when the corresponding RRC parameter (which is a new RRC used to configure the presence of this 1-bit DCI field) is enabled and at least one TCI state is configured with PL offset.
When one joint/UL TCI state is indicated in Rel-17 unified TCI, 
the bit field index 0 of this field indicates that PL offset is not included in the PRACH transmission power calculation 
the bit field index 1 of this field indicates that the PL offset associated with the indicated TCI state is included in the PRACH transmission power.
FFS: Whether the bit field can be used to indicate other information
FFS: When two joint/UL TCI states are indicated in Rel-18 unified TCI

Agreement
For indicating PL offset for PDCCH-order PRACH, when two joint/UL TCI states are indicated in Rel-18 unified TCI, down-select one from the following Alts for the 1-bit DCI field in DCI 1_0 which indicates the application of PL offset on PRACH transmission:
Alt2:
the bit field index 0 of this field indicates that the PL offset associated in the first indicated joint/UL TCI state is included in the PRACH transmission power calculation 
the bit field index 1 of this field indicates that the PL offset associated in the second indicated joint/UL TCI state is included in the PRACH transmission power calculation.
FFS: Whether a restriction that only one of the indicated joint/UL TCI states can be configured with PL offset is needed.
FFS: If other information can be indicated by this same 1-bit DCI field for the PDCCH-order PRACH transmission

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

Agenda Item:	8.12.2
Source:	Ofinno
Title:	Enhancements for Asymmetric DL sTRP and UL mTRP
Document for:	Discussion and Decision

Conclusion
In this contribution, we make the following proposals. 
(MAC-3) Support asymmetric DL sTRP and UL mTRP with no PL offset (i.e. the UL TRP may transmit SSB) for the LTM target cell (i.e., similar to Rel-18 multi-DCI mTRP and no MAC spec impact).

(MAC-3) Support sDCI mTRP 2TA operation for intra-DU LTM, in the same way as Rel-18 mDCI mTRP 2TA, i.e., the TA included in the LTM cell switch command is applied to the TAG configured for the indicated TCI state in LTM cell switch command.


(MAC-3) Regarding PL offset in LTM, the PL offset configured in the LTM configuration for the indicated TCI state in the LTM cell switch command is applied for the first PUSCH transmission in RACH-less LTM cell switch.
The PL offset can be indicated in the LTM cell switch command, e.g., under two cases below:
Case 1: When PL offset is not provided in LTM configuration for the target cell.
Case 2: When PL offset is provided in LTM configuration for the target cell and the NW wants to update PL offset.


(MAC-4) Reuse the Rel-18 TCI State activation/deactivation MAC CE for joint/separate modes for the asymmetric mTRP scenario. 
When separate TCI mode is used in the asymmetric mTRP scenario, the Fi,j fields, j = 2 in the TCI activation/deactivation MAC CE are reserved (e.g., set to 0) and the UE ignores these Fi,j fields.


When the TAT for a TAG is expired and the other TAT is running for a serving cell (i.e., SCell, SpCell), the UE does not clear any configured uplink grant or PUSCH resource for semi-persistent CSI reporting which is associated with both TAGs. 

3GPP TSG-RAN WG2 Meeting #130		R2-2503626
St. Julian’s, Malta, 19th – 23rd May 2025
Source:	vivo
Title:	Discussion on open issues for asymmetric DL sTRP/UL mTRP
Agenda Item:	8.12.2
Document for:	Discussion and Decision

Conclusion
In this contribution, we discuss the RAN2 MAC and RRC open issues for asymmetric DL sTRP/UL mTRP. Based on the discussion above, we have the following proposals:
MAC open issue:
(MAC-4) Send an LS to RAN1 to check whether to design new MAC CE(s) for the TCI States Activation/Deactivation or to extend Rel-18 Enhanced Unified TCI States Activation/Deactivation MAC CE for Joint TCI States and Enhanced Unified TCI States Activation/Deactivation MAC CE for Separate TCI States for the asymmetric DL sTRP/UL mTRP scenarios.

RRC open issues:
(RRC-x) No extra behavior should be defined for handover and resume case.

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

Agenda Item:	8.12.2
Source: 	OPPO
Title:  	Remaining issues of asymmetric DL sTRP and UL mTRP
Document for:	Discussion and Decision

Conclusion
According to the analysis provided above, we have the following observations and proposals:
Observation 1: In 38.331, it can be understood that the “current” pathlossOffset configuration stored at the RRC only refers to the last configuration provided by RRC message.
Observation 2: If the pathlossOffset updated by MAC does not update the value stored in RRC, a complex UE implementation is needed to have two separate internal variables of pathloss offset, i.e. one variable for RRC message configuration and one variable for MAC CE configuration, which are compared with each other to determine the latest configuration.
Observation 3: If the pathlossOffset updated by MAC does not update the value stored in RRC, the absence of the TCI-State and TCI-UL-State (as the parent field for pathlossOffset) due to delta configuration forces the UE to reuse the out-of-date pathlossOffset configured by RRC message, which will be considered as the latest configuration.
Observation 4: According to the WID of Rel-19 MIMO, the Rel-19 asymmetric DL sTRP/UL mTRP deployment is only applicable to intra-band intra-DU non-co-located mTRP scenarios.
Observation 5: The gNB by implementation can indicate the TCI-state of the UL/DL symmetric TRP via LTM Cell Switch Command MAC CE, and the latest pathloss offset can be provided after LTM completion.
Observation 6: When the UE is configured with Rel-17 unified TCI state, Unified TCI state activation/deactivation MAC CE of Rel-17 can be reused to map “one joint TCI state” or “one DL TCI state + one UL TCI state” to one code point.
Observation 7: When the UE is configured with Rel-18 unified TCI state, Enhanced unified TCI states activation/deactivation MAC CE for Joint TCI States can be reused to map “up to two joint TCI states” to one code point, and Enhanced unified TCI states activation/deactivation MAC CE for Separate TCI States can be reused to map “one DL TCI state + up to two UL TCI state” to one code point by setting one Fi,j field to “0”.
Observation 8: According to TS 38.214, it seems that the number of indicated TCI-state cannot be changed.

Proposal 1: RAN2 is kindly requested to clarify that the pathlossOffset configuration stored in RRC refers to the latest configuration provided by RRC message or MAC CE.
Proposal 2: To clarify in TS 38.321 that the path offset provided by the Pathloss Offset Update MAC CE is indicated to RRC (i.e. upper layer).
Proposal 3: RAN2 is kindly requested to confirm one of the following options for the maximum processing delay requirement of updating pathlossOffset configuration via MAC CE.
Option 1: 10ms, as RRC reconfiguration
Option 2: MAC CE decoding time
Option 2: up to UE implementation
Proposal 4: During handover, the pathlossOffset forwarded from the source node to the target node is the latest configuration provided by RRC message or MAC CE.
Proposal 5: The INACTIVE UE stores the latest pathlossOffset provided by RRC message or MAC CE.
Proposal 6: The gNB can provide the latest pathlossOffset via the CellGroupConfig of the RRCResume message. No specification change is needed.
Proposal 7: Asymmetric DL sTRP/UL mTRP can be configured for LTM without extra enhancements.
Proposal 8: When the UE is configured with Rel-17 unified TCI state, Unified TCI state activation/deactivation MAC CE of Rel-17 is reused, unless the new design of MAC CE is required by RAN1.
Proposal 9: When the UE is configured with Rel-18 unified TCI state, Enhanced unified TCI states activation/deactivation MAC CE for Joint TCI States and Enhanced unified TCI states activation/deactivation MAC CE for Separate TCI States are reused, unless the new design of MAC CE is required by RAN1.
Proposal 10: The PHY specification issue that the number of indicated TCI states cannot be changed should be discussed in RAN1.

TDoc file reading error

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

Source:	CATT
Title:	Discussion on Asymmetric DL sTRP UL mTRP
Agenda Item:    8.12.2
Document for:  Discussion and Decision

Conclusion
Based on the previous analysis in Section 2, our contributions are summarized as follows:
Further details on PL offset
Proposal 1: No further spec impact is needed for delta configuration upon handover or RRCResume procedure even if the PL offset had been updated by the PL offset update MAC CE.
Proposal 2: Upon receiving the LTM command MAC CE, it’s up to UE implementation to determine the PL offset used for first PUSCH of RACH-less LTM by the UL/Joint TCI state in the ServingCellConfig of target configuration which shares the same source RS with the TCI state indicated in the of LTM command MAC CE. There is no spec impact.
Proposal 3: For the co-existence of asymmetric TRP with intra-DU LTM, it’s up to NW implementation to only configure the L1 measurement with the beams associated with the DL/UL TRP, if the candidate cell cannot estimate the PL offset for the UL-only TRP.

TCI state activation for asymmetric TRP
Proposal 4a: RAN2 to confirm the Unified TCI States Activation/Deactivation MAC CE can satisfy the RAN1 requirement. No further MAC impact is needed for the asymmetric TRP with configured R17 unified TCI state framework.
Proposal 4b: RAN2 to confirm the current format of the Enhanced Unified TCI States Activation/Deactivation MAC CE for Separate TCI States and the Enhanced Unified TCI States Activation/Deactivation MAC CE for Joint TCI States can satisfy the RAN1 requirement for the asymmetric TRP configured with R18 unified TCI framework. No further MAC impact is needed.

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

Agenda item:		8.12.2 (NR_MIMO_Ph5-Core)
Source:	LG Electronics Inc.
Title: 	Consideration on Asymmetric DL sTRP/UL mTRP 
Document for:	Discussion and Decision
1.	

Conclusion
In this document, we discuss RAN2 impacts from asymmetric DL sTRP/UL mTRP, and made proposals as follows.
Proposal 1. The inter-operability with Rel-19 2TA and LTM cell switch is discussed in LTM session, not MIMO session.
Proposal 2. Reuse Rel-18 Unified TCI States A/D MAC CE for asymmetric DL sTRP/UL mTRP deployment.

4.	

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

Agenda item:	8.12.2
Source:	Nokia
Title:	Discussion on asymmetric DL sTRP/UL mTRP
WID/SID:	NR_MIMO_Ph5-Core - Release 19
Document for:	Discussion and Decision
1	

Conclusion
Observation 1: Following resumption from inactive state, the applicable PL offset configuration could be ambiguous or out-of-date. 
Observation 2: During handover, the UE and target gNB could assume that different PL offsets are applicable. 
Observation 3: It is complicated to enhance the LTM cell switch and candidate cell activation MAC procedures for asymmetric TRP; limiting the candidate LTM TCI state enhancements to RRC is feasible, but has questionable benefits if MAC cannot also be enhanced. 
Proposal 1: Network should indicate the applicable PL offset configuration to the UE during the RRC resume procedure. RAN2 to consider the following options:
-	Option 1: Make pathlossOffset-r19 conditionally mandatory during RRC resume so network includes masterCellGroupConfig with pathlossOffset-r19 within the RRCResume message.
-	Option 2: Add a new IE within RRCResume to directly update the PL offsets without requiring masterCellGroupConfig configuration.
Proposal 2: RAN2 to discuss how to handle PL offset during handover, e.g. by making pathlossOffset-r19 conditionally mandatory when masterCellGroupConfig includes ReconfigurationWithSync.
Proposal 3: RAN2 does not specify enhancements to support PL offset for asymmetric TRP during LTM cell switch or candidate cell activation procedures.
Proposal 4: Reuse the Release-18 TCI State activation/deactivation MAC Control Element (CE) to support both joint and separate TCI modes in the asymmetric mTRP scenario. In the case of separate TCI mode, where a UL-only TRP is present without a corresponding DL TCI State, the associated Fi,j field in the MAC CE shall be set to 0, and the UE shall ignore this field.

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

Agenda item:	8.12.2
Source:	Lenovo
Title:	Discussion on PL offset
WID/SID:	NR_MIMO_Ph5-Core - Release 19
Document for:	Discussion and Decision
1	

Conclusion 
In summary, we have following proposals for PL offset:
Proposal 1: UE maintains the PL offset when a timeAlignmentTimer corresponding to a TAG associated with a TCI state expires. 
Proposal 2: It is not allowed to update PL offset by RRC signalling. 
Proposal 3: UL only TRP is selected if both of the UL TRPs can perform a UL transmission. 
Proposal 4: UE stores PL offset(s) when UE is released to RRC_INACTIVE state.
Proposal 5: The stored PL offset(s) is resumed if the UE resumes RRC connection to the same cell as the cell the UE being released to. 
Proposal 6: Support asymmetric DL sTRP and UL mTRP in the case of LTM. 
Proposal 7: To support asymmetric DL sTRP and UL mTRP as a target cell in the case of LTM, the PL offset value are indicated in the cell switch command.
4	

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

Agenda Item:	8.12.2
Source:	Ericsson
Title:	Asymmetric DL/UL mTRP user plane impact from MIMO ph. 5
Release:	19
Document for:	Discussion
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 may need to be updated with RRC signaling, which generates a significant amount of overhead signaling and latency.

Based on the discussion in the previous sections we propose the following:
Proposal 1	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 2	Confirm that PL offset configuration is provided as need R. No PL offset mismatch is expected for handover and resume.
Proposal 3	The field description of tag2 refers to TS 38.213 for configuration restrictions instead of capturing them explicitly in TS 38.331.

4	

3GPP TSG-RAN WG2 Meeting #130	R2-2504100	
Malta, 19 – 23 May 2025
Agenda Item:	 8.12.2
Source:	 Huawei, HiSilicon
Title:	 Discussion on remaining issues on Asymmetric DL sTRP/UL mTRP
Document for:  Discussion and Decision
1	

Conclusion
From the analysis on RAN2 impacts for MIMO, we made the following proposals:
Proposal 1: Reuse the Rel-18 TCI State activation/deactivation MAC CE for joint/separate modes for the asymmetric mTRP scenario. 
Proposal 2: Add a note in TS 38.321 “When the TCI activation/deactivation MAC CE for separate TCI mode is used in the asymmetric mTRP scenario, the Fi,j field for the TCI state of the UL-only TRP is set to 0 and the UE ignores this Fi,j field.”
Observation1: During handover procedure, in case delta signalling is used, the UE may store the latest PL offset value received in MAC CE, while the target gNB is only aware of RRC configured value by the source gNB. 
Observation2: When the pathlossOffset is absent in RRC reconfiguration, the “current” PL offset configuration stored at the UE only refers to the last pathlossOffset configured by RRC, not MAC CE.
Proposal 3a: Select one from the following two options for PL offset update for handover:
Option1: Delta signalling is not supported for PL offset.
Option2: 
Delta signalling is supported for PL offset. 
Before RRC reconfiguration, the latest PL offset should be indicated from DU to CU for handover.
To clarify in TS 38.331 that when the pathlossOffset is absent in RRC configuration, the “current” pathlossOffset configuration stored at the UE refers to the latest configuration provided by RRC message or MAC CE.
Proposal 3b: If Option 2 is adopted, a LS to RAN3 is needed to ask for if any potential impacts.

4	

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

Agenda item:	8.12.2
Source:	Samsung
Title:	Open issues on Asymmetric DL sTRP/UL mTRP
WID/SID:	NR_MIMO_Ph5
Document for:	Discussion and Decision

Conclusion
Based on the discussion, we have the following proposals.
Observation 1: RAN1/4 also consider 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), i.e., ICBM. Rel-19 sDCI mTRP 2TA is applied in this scenario.
Proposal 1: 2TA operation is supported for single-DCI mTRP without the restriction that coresetPoolIndex needs to be configured with more than one value, and single-DCI mTRP 2TA is applied to both the scenarios that PL offset is configured (i.e., asymmetric DL sTRP/UL mTRP) and PL offset is not configured (i.e., ICBM).
Proposal 1-1: Discuss how to capture field description for tag2 to keep backward compatibility for Rel-18 mDCI mTRP 2TA and also make the field applicable to Rel-19 sDCI mTRP 2TA. 
Option 1: as a clean solution, introduce a new RRC parameter per BWP that explicitly enables the Rel-19 sDCI-mTRP 2TA, and clarify in FD of tag2 to include all cases where tag2 is configured that “it is optionally configured in a serving cell for mDCI mTRP 2TA if coresetPoolIndex for a BWP is configured with more than one value, and for sDCI mTRP 2TA if [the new parameter is configured].”;
Option 2: use coresetPoolIndex to implicitly enable Rel-18 mDCI mTRP 2TA or Rel-19 sDCI mTRP 2TA, i.e., update the FD of tag2 that “it is optionally configured for a serving cell for mDCI mTRP 2TA if coresetPoolIndex for a BWP is configured with more than one value, and for sDCI mTRP 2TA if coresetPoolIndex for a BWP is not configured or coresetPoolIndex is configured with no more than one value”;
Option 3: use UE capability to distinguish Rel-19 feature, i.e., update the FD of tag2 that “For UE not supporting 2TA for sDCI mTRP, it is optionally configured in a serving cell if and only if the serving cell is configured with more than one value for the coresetPoolIndex for a BWP. For UE supporting 2TA for sDCI mTRP, it is optionally configured in a serving cell for mTRP operation if coresetPoolIndex for a BWP is not configured or configured with only one value.”.
Observation 2: In sDCI mTRP 2TA operation for the scenario PL offset is not configured (UE is configured with SSB-MTC-additionalPCI), UE maintains two downlink reference timings as RAN1 agreed.
Proposal 2: Regarding sDCI mTRP 2TA operation for the scenario PL offset is not configured (UE is configured with SSB-MTC-additionalPCI), discuss how to configure n-TimingAdvanceoffset or n-TimingAdvanceOffset2. 
Option 1: RAN2 assumes both n-TimingAdvanceoffset and n-TimingAdvanceOffset2 are configured unless RAN1 has different agreement. 
Option 2: send LS to ask RAN1.

Observation 3: The existing Rel-18 TCI state activation MAC CEs for sDCI mTRP already support to always activate one joint/DL TCI state for a DCI codepoint.
Proposal 3: Rel-18 TCI state activation MAC CEs for sDCI mTRP are applied for asymmetric DL sTRP/UL mTRP. NW can always set Fi,j field to 0 to activate only one DL TCI state for a codepoint. No enhancement is needed from RAN2 perspective.

Proposal 4: Rel-19 sDCI mTRP 2TA is supported for intra-DU LTM, the TA included in the LTM cell switch MAC CE is applied to the TAG configured for the TCI state indicated in LTM cell switch MAC CE (same as Rel-18 mDCI mTRP 2TA, no spec. impact).
Proposal 5: If PL offset is configured in LTM configuration for the target cell, the PL offset configured for the TCI state indicated in the LTM cell switch MAC CE is applied for the first PUSCH transmission in RACH-less LTM for the target cell. No enhancement for the case PL offset is not pre-configured. No spec. impact.
Proposal 6: For the current HO/RRCresume procedure, there is no spec. impact that UE applies the latest PL offset value received in RRC or MAC CE. 

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

Agenda item:	8.12.2     
Source:	Qualcomm Incorporated
Title:	Discussion on UL only mTRP
WID/SID:	NR_MIMO_Ph5-Core – Release 19
Document for:	Discussion

Conclusion
In this contribution, we discussed the remaining design consideration for supporting 2 TAs when PL offset is not configured and concluded with the following observations and proposals.

Observation 1. SSB transmission from ULmTRP is supported if PL offset is not configured.
Observation 2. If SSB transmission from ULmTRP is allowed, each TA of the 2 TAs may have its respective downlink reference. 
Observation 3. If SSB transmission from ULmTRP is allowed, there is still one sTRP transmitting DCI.
Proposal 1. RAN2 support the follows for 2 TAs when PL offset is not configured, based on Rel-18 2TA configuration: 
remove the restriction that RRC field tag2 is configured only if coresetPoolIndex is configured with more than one value;  
keep both single n-TimingAdvanceoffset and n-TimingAdvanceOffset2.

3GPP TSG-RAN WG2 Meeting #130		R2-2504248
Malta, MT, 19th – 23rd May. 2025
Source:	China Telecom
Title:	Discussion on asymmetric DL sTRP/UL mTRP scenarios 
Agenda Item:	8.12.2
Document for:	Discussion and Decision

Conclusion
Based on the discussion, we have the following observations and proposals.
Proposal 1: The Rel-18 legacy activation/deactivation MAC CE can work for asymmetric DL sTRP/UL mTRP with no enhancement.
Proposal 2: It is beneficial to introduce PL offset in the LTM cell switch MAC CE if PL offset does not include in LTM Config but NW can provide it before the LTM cell switch procedure is applied.

TDoc file reading error

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

Source:        ZTE Corporation
Title:           Consideration on the Remaining Issues of Asymmetric TRP
Agenda item:   8.12.2
Document for:  Discussion and Decision

Conclusion and proposals
With the above analysis, we have the following proposals:
Proposal 1: For the scenario 2 (i.e. UE is not configured with PL offset in joint/UL TCI state(s) and UE may expect to receive SSB from UL TRP), remove the restriction that RRC field tag2 is configured only if coresetPoolIndex is configured with more than one value.
Proposal 2: For the scenario 2, it should be allowed to configure the n-TimingAdvanceOffset2 for the 2TA.
Proposal 3: Regarding support R19 MIMO with scenario 1(UE is configured with PL offset in joint/UL TCI state(s)) for intra-DU LTM feature, send an LS to RAN1 to confirm whether it’s possible to get the PL offset in advance for intra-DU case.
Proposal 4: Support R19 MIMO 2TA with scenario 2 (i.e. UE is not configured with PL offset in joint/UL TCI state(s) and UE may expect to receive SSB from UL TRP) for the LTM feature.
Proposal 5: Use need R for the PL offset configuration.
Proposal 6: RAN2 confirm that Rel-18 TCI state activation MAC CEs for sDCI mTRP is applied for asymmetric DL sTRP/UL mTRP with no spec impact (or no enhancement). It’s left to the NW implementation on how Rel-18 TCI state activation MAC is applied for asymmetric DL sTRP/UL mTRP.

TDoc file unavailable